OmegaPS Continued Evolution 8 May2012
OmegaPS Core & Additional Modules
Frank Hallam
OmegaPS Continued Evolution 8 May2012 OmegaPS Core & Additional - - PowerPoint PPT Presentation
OmegaPS Continued Evolution 8 May2012 OmegaPS Core & Additional Modules Frank Hallam Supportability Analysis Data OmegaPS Core Application A - What is it? Structure Manager Goals Top Down Breakdown Identification B - How will it
Frank Hallam
B - How will it break? FM FMEC EC A FMECA A - What is it?
C - How is it repaired?
Personnel & Training Mai aint nten enan ance ce Tas ask Ana naly lysis sis Facilities Technical Documentation Support and Test Equipment Reference Spares & Inventory
Structure Manager
Top Down Breakdown
Goals Identification
2
Structure Manager
FMECA Maint Tasks Parts Data Support Eqpt
RCM Manager Impact Analysis LORA, LCC Sparing ANALYZER Viewer POM
Normal CORE modules used within OmegaPS. Analyzer is a stand alone product that draws data from the LSAR tables
3
LSAR Reporting
Structure Manager
4
Structure Manager enables a view of allowed alternates (ALCs) as well as defined configurations (UOCs) Structure Manager can build structure automatically where parent/child parts are re- used OR build structure
5
RCM Manager RCM Manager allows for identifying when a PM task is required. RCM logic can be created to suite - MSG3 is the default logic
6
LSAR Reporting
required LSAR reports in accordance with MIL- STD-1388-2B/A-LM-505-000 as well as DEF STAN 0060 and DEF AUS 5692
STD-0007/PLCS – full compliance will be achieved with the release of the 0007 product
requirement for LSAR reports based on requirements from DoD – these reports will be added to the 0007 product following the initial release
OmegaPS Application Maintenance Provisioning Fit Definition Embedded Publications Support Analysis Change Management Publisher
7
Dynamic RCM
OmegaPS Application Provisioning
Provisioning and thus the data required for cataloguing items
specification called Commercial Canadian Provisioning
in accordance with CFP 214
8
OmegaPS Application Provisioning
are as follows:
9
OmegaPS Application Provisioning
this module
RSPL, ISL or LLTIL
214)
10
OmegaPS Application Provisioning
can be saved as pdf or txt files
11
OmegaPS Application Provisioning
configured to feed DND Canadian Provisioning
configured to display CGCS/SAP data
involved in In-Service Support contracts
12
OmegaPS Application Provisioning
Outfitting Management Information System ) extensions – US Navy System
13
HK (Parts Manual Description) and XI (Tech Manual Code) load forms have also been adjusted
tables have been adjusted with required ROMIS data
OmegaPS Application Provisioning
(Interactive Computer Aided Provisioning) – US Navy/Marine Corp provisioning system
14
OmegaPS Application Provisioning
change to provisioning
maintenance BOM
15
include
allowing commercial clients to receive/view current NSN data
tracking obsolescence
OmegaPS Application Maintenance
conjunction with configurable RCM
accordance with GEIA 0007 if required
required in final format
16
Maintenance
defined as Tasks and Sub-Tasks
three tiered structure (Procedure/Task/Sub-Task)
– better mapping to the Maintenance Management System
17
tasks (jobs) into major routines such as a periodic inspection
three tiered maintenance definition – selection to 3 tier is being removed in the next iteration
projects will employ 3 tier structures
Maintenance
18
Procedure Task Sub-Task
Task – Provisioned Item, Support and Test Equipment, Skills, Technical Publications
Maintenance
19
specific user attribution
Maintenance
20
be linked to the Procedure
Maintenance
21
Maintenance
22
the task. Note the existence of SE and PI at this lower level – the roll-up toggle allows for the item to roll-up to the task and be exported in a MIL-STD-1388-2B/A-LM-505-000 format and enable 1388 reports.
Maintenance
23
Defence Force, as well as in Canada for DND
for maintenance definition information
Canadian DND
Maintenance
24
not utilize S1000D DMCs since the end product is a complete WORD or PDF document
OmegaPS add on called Assembly- Publisher allows for integration of S1000D and use of Data Module Codes and interaction with an IETM solution
concept of the LSAR being the source for maintenance definition
side English/French
OmegaPS Application Maintenance
change to maintenance
documents
CFTOs
25
directly
Instructions
OmegaPS Application Fit Definition
data to be conditioned to incorporate attribution required for interface with a maintenance management system
created from OmegaPS resides within SAP (enterprise MMIS) as the objects used to conduct maintenance.
by the LSAR as changes are made to the baseline.
in-service support.
26
OmegaPS Application Fit Definition
data requirements in the following manner:
within overall UOC configurations if required
as well as things…
maintenance significant will be included in the Fit Definition configuration
has been fully defined will be exported to the maintenance management system
27
OmegaPS Application Fit Definition
may be used at the class level and Fit Definition Name can be used to differentiate a specific hull fit
28
UOC defines the different configurations being delivered/maintained.
OmegaPS Application Fit Definition
different view on Functional vs Physical LCN structures
which Physical Equipment is placed
the Functional Structure: therefore, System/End Item is assigned to a Functional LCN and applied to the Physical LCNs
29
OmegaPS Application Fit Definition
available to Fit Definition by:
NSN) or Non-Catalogued BOM items (assemblies)
maintenance significant items
30
for Canadian DND with Equipment separated from PIs by ERN designation
Vendor Master Data OmegaPS Supportability Baseline
SAP
Material– Cataloguing FMECA Maintenance Task Analysis Select material for Provisioning Map additional in-service attribution Map additional in-service attribution – Create Functional, Physical, Logistics structure Supportability Analysis Review Sparing, LORA, LCC
LSAR to Maintenance Management – Example - SAP
Structure – Baseline Map additional in-service attribution MMRs FLOCs EMRs Nodes & FIDs MERs PPAs GMTLs PRTs Measurement Pts Counters BOMs Maint Plans Failure Catalogues SAP Master Data Objects
31
Omega produces files for the creation of the Master Data
FI
Financial Accounting
CO
Controlling
AM
Fixed Assets Mgmt.
PS
Project System
WF
Workflow
IS
Industry Solutions
MM
Materials Mgmt.
HR
Human Resources
SD
Sales & Distribution
PP
Production Planning
QM
Quality Manage- ment
PM
Plant Main- tenance
Primary LSAR & SA Data Interfaces
Pennant is an SAP partner and has an interface that was certified to SAP version 4.5b and 4.6c
32
OmegaPS Application Fit Definition
33
change to Fit Definition
Maintenance Plans
ID to Naval equipment
to SAP
OmegaPS Application Embedded Publications
accordance with GEIA –STD - 0007
Parts Catalogues or Views as required
34
OmegaPS Application Embedded Publications
within the database
with any required set of data
35
allows the file to be displayed
OmegaPS Application Embedded Publications
within Structure Manager
36
Nomenclature indicates that a file has been attached
OmegaPS Application Embedded Publications
displayed within a form (files that can be displayed on a single page)
37
generation of Illustrated Parts Books
OmegaPS Application Embedded Publications
change to Embedded Publications
Breakdown System)
38
will include
well as Structure -this will enable tagging
functionality in a mobile product with commercial and DND configurations
OmegaPS Application Support Analysis
Module (OSAM) links modeling and baselining solutions directly into the LSAR
and Sparing Analysis now reside directly in the same database.
Analyzer but resides within the OmegaPS Application
39
OmegaPS Application Support Analysis
modeling:
support organization with a planned PE distribution
40
OmegaPS Application Support Analysis
scenario which brings together a specific PE configuration and a specific Support Organization and PE distribution
completed with
Effectiveness
Cost optimization
selection
41
Support Analysis
42
LSAR
xls Template
file (OSAM to OSAM or Analyzer to OSAM
xml format
OmegaPS Application Support Analysis
change to OSAM/Support Analysis
43
include
update LSAR data with OSAM results
OmegaPS Application Change Management
control of any changes to the LSAR data through Engineering Change Requests (ECRs) and Engineering Change Orders (ECOs)
invoked before any change is made.
44
OmegaPS Application Change Management
Australian Defence Force (ADF) and DND
both ADF and DND as well as a Commercial version
45
OmegaPS Application Change Management
change to Change Management
and work flow
46
include
Management within GEIA STD 0007 - if this occurs OmegaPS Change Management will be modified to adapt to the new standard
OmegaPS Application Publisher
system of your choice
and format issues handled by the content management system
47
OmegaPS Application Dynamic RCM
allow for an item to have a single function
analysis has multiple functions
desired standard of performance of the asset in its present operating context (functions)?
(owners of GEIA-STD-0007) to expand the data model to include multiple functions
within OmegaPS called Dynamic RCM in 2008
48
OmegaPS Application Dynamic RCM
failure mode to a function and link both to a mitigating maintenance action if required/appropriate
49
configured to create SAP Catalogues specific to the ERN (EMR/FLOC) being maintained
OmegaPS Application Dynamic RCM
any changes in this area
50
concept to GEIA STD 0007
incorporated into the new GEIA 0007 product
Support Analysis Change Management
Publisher OmegaPS Application
Maintenance Provisioning Fit Definition Embedded Publications
Dynamic RCM
Summary The Add –On Capabilities enable OmegaPS to be utilized to control logistics data and enhance the usability of the product for both the Acquisition phase and In-Service Support phase of any project