OmegaPS Continued Evolution 8 May2012 OmegaPS Core & Additional - - PowerPoint PPT Presentation

omegaps continued evolution
SMART_READER_LITE
LIVE PREVIEW

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


slide-1
SLIDE 1

OmegaPS Continued Evolution 8 May2012

OmegaPS Core & Additional Modules

Frank Hallam

slide-2
SLIDE 2

B - How will it break? FM FMEC EC A FMECA A - What is it?

Supportability Analysis Data OmegaPS– Core Application

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

slide-3
SLIDE 3

LSAR Database

Structure Manager

FMECA Maint Tasks Parts Data Support Eqpt

RCM Manager Impact Analysis LORA, LCC Sparing ANALYZER Viewer POM

Supportability Analysis Data OmegaPS– Core Capabilities

Normal CORE modules used within OmegaPS. Analyzer is a stand alone product that draws data from the LSAR tables

3

LSAR Reporting

slide-4
SLIDE 4

Structure Manager

Supportability Analysis Data OmegaPS– Core Capabilities

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

  • ne part at a time
slide-5
SLIDE 5

Supportability Analysis Data OmegaPS– Core Capabilities

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

slide-6
SLIDE 6

Supportability Analysis Data OmegaPS– Core Capabilities

6

LSAR Reporting

  • OmegaPS has the ability to generate all the

required LSAR reports in accordance with MIL- STD-1388-2B/A-LM-505-000 as well as DEF STAN 0060 and DEF AUS 5692

  • Pennant is partially compliant with GEIA-

STD-0007/PLCS – full compliance will be achieved with the release of the 0007 product

  • GEIA has only recently re-instated the

requirement for LSAR reports based on requirements from DoD – these reports will be added to the 0007 product following the initial release

slide-7
SLIDE 7

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Maintenance Provisioning Fit Definition Embedded Publications Support Analysis Change Management Publisher

7

Dynamic RCM

slide-8
SLIDE 8

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • DND provisioning specification is CFP 214
  • It defines data requirements for Initial

Provisioning and thus the data required for cataloguing items

  • OmegaPS has a module dedicated to this

specification called Commercial Canadian Provisioning

  • All suppliers to DND will be asked for a PPB

in accordance with CFP 214

8

slide-9
SLIDE 9

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • Canadian Provisioning Data Requirements

are as follows:

  • PPB – Provisioning Parts Breakdown
  • RSPL – Recommended Spare Parts List
  • ISL – Interim Spares List
  • LLTIL - Long Lead Time Item List
  • NSN – NATO Stock Number
  • Ref Des – Reference Designation
  • OEM Drawing ID – Drawing Number
  • GSM – Government Supplied Material
  • Repairable – Set separately from CI
  • Indenture Code – Inherited from LCN structure
  • Unit of Issue
  • Qty/Assembly – inherited from LCN structure
  • Buy Qty – first 24 months of support
  • SMR Code – Source Maintenance Recoverability
  • PLT – Production Lead Time
  • Shelf Life
  • Usage Rate
  • Usage rate MB – Measurement Base
  • Unit Price (CDN)
  • Obsolescence Watch List

9

slide-10
SLIDE 10

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • There are three reports which are enabled by

this module

  • Sequence Number Assignment
  • PPB Report which can be set for PPB,

RSPL, ISL or LLTIL

  • Obsolescence Watch List (not in CFP

214)

10

slide-11
SLIDE 11

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • The reports launch in a separate window and

can be saved as pdf or txt files

11

slide-12
SLIDE 12

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • Commercial Canadian Provisioning is

configured to feed DND Canadian Provisioning

  • DND Canadian Provisioning is also

configured to display CGCS/SAP data

  • This configuration would be used by a vendor

involved in In-Service Support contracts

12

slide-13
SLIDE 13

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • Upload LSAR data with ROMIS (Real Time

Outfitting Management Information System ) extensions – US Navy System

13

  • EA (Support Equipment),

HK (Parts Manual Description) and XI (Tech Manual Code) load forms have also been adjusted

  • HG (Part Application) load

tables have been adjusted with required ROMIS data

slide-14
SLIDE 14

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • Update in accordance with ICAPS

(Interactive Computer Aided Provisioning) – US Navy/Marine Corp provisioning system

14

slide-15
SLIDE 15

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Provisioning

  • R18 Release of OmegaPS will see continued

change to provisioning

  • Key Changes
  • From CGCS update retain old NSNs
  • Improve usability of pass back log
  • Ability to select Parts to be assembled in

maintenance BOM

  • Ability to select a preferred alternate

15

  • Possible future initiatives in provisioning to

include

  • In-Service Support configuration –

allowing commercial clients to receive/view current NSN data

  • Ability to link to industry sources for

tracking obsolescence

slide-16
SLIDE 16

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Maintenance

  • Maintenance definition using FMEA data in

conjunction with configurable RCM

  • Three tiered maintenance definition in

accordance with GEIA 0007 if required

  • Ability to produce maintenance publications if

required in final format

16

slide-17
SLIDE 17

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

  • Maintenance in MIL-STD-1388-2B format was

defined as Tasks and Sub-Tasks

  • GEIA –STD-0007 has adopted DEF-STAN-0060

three tiered structure (Procedure/Task/Sub-Task)

  • This has been used in Canada since 2006 – why?

– better mapping to the Maintenance Management System

17

  • Three tiered definition allows for grouping

tasks (jobs) into major routines such as a periodic inspection

  • Navy configuration in OmegaPS assumes

three tiered maintenance definition – selection to 3 tier is being removed in the next iteration

  • f the DND product -thus assuming all

projects will employ 3 tier structures

slide-18
SLIDE 18

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

18

Procedure Task Sub-Task

  • All maintenance resources can be mapped to Sub-

Task – Provisioned Item, Support and Test Equipment, Skills, Technical Publications

slide-19
SLIDE 19

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

19

  • The product can be configured as required to accommodate

specific user attribution

  • The screen capture shows the product configured for DND/Navy
slide-20
SLIDE 20

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

20

  • Tasks are created through the normal process and they can then

be linked to the Procedure

slide-21
SLIDE 21

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

21

  • Task Details can be modified from within this form set as required.
slide-22
SLIDE 22

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

22

  • Sub-Tasks can be defined within this form set as required to define

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.

slide-23
SLIDE 23

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

23

  • Maintenance Publications can be produced directly from OmegaPS
  • This has been configured for use in Australia for the Australian

Defence Force, as well as in Canada for DND

  • This ensures that the LSAR retains it’s roll as the central repository

for maintenance definition information

  • The Demonstration forms show the product as configured for

Canadian DND

slide-24
SLIDE 24

Supportability Analysis Data OmegaPS– Add On Capabilities

Maintenance

24

  • Process produces an xml file
  • Which can be opened in WORD
  • This process does

not utilize S1000D DMCs since the end product is a complete WORD or PDF document

  • Another

OmegaPS add on called Assembly- Publisher allows for integration of S1000D and use of Data Module Codes and interaction with an IETM solution

  • Either solution re-enforces the

concept of the LSAR being the source for maintenance definition

  • The Document is produced in side by

side English/French

slide-25
SLIDE 25

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Maintenance

  • R18 Release of OmegaPS will see continued

change to maintenance

  • Key Changes
  • Ability to produce and reference common

documents

  • Ability to produce Illustrated Parts “MY”

CFTOs

  • Integrate CTAT/ITAR Warnings

25

  • Future initiatives in maintenance to include
  • Ability to produce the following CFTOs

directly

  • NY – PM Performance Test
  • MM – Corrective Maintenance

Instructions

  • NQ – Refit Specification
  • CD – Modification Instruction
  • Air Force Maintenance Card Deck
slide-26
SLIDE 26

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

  • The Fit Definition Module allows for LSAR

data to be conditioned to incorporate attribution required for interface with a maintenance management system

  • Within the Canadian DND, Master Data

created from OmegaPS resides within SAP (enterprise MMIS) as the objects used to conduct maintenance.

  • Updates to the Master Data are then driven

by the LSAR as changes are made to the baseline.

  • Therefore the LSAR becomes the source for

in-service support.

26

slide-27
SLIDE 27

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

  • Fit definition allows for filtering of the master

data requirements in the following manner:

  • Fit – Fit Definition allows for variance

within overall UOC configurations if required

  • Structure – Fit Definition manages holes

as well as things…

  • Parts – only parts selected as

maintenance significant will be included in the Fit Definition configuration

  • Maintenance – only maintenance that

has been fully defined will be exported to the maintenance management system

27

slide-28
SLIDE 28

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

  • Fit definition - Ship Fit – Variability - UOC

may be used at the class level and Fit Definition Name can be used to differentiate a specific hull fit

28

  • Fit definition - In an Army configuration the

UOC defines the different configurations being delivered/maintained.

slide-29
SLIDE 29

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

  • Configuration - Fit Definition has a slightly

different view on Functional vs Physical LCN structures

  • Functional LCNs are considered holes into

which Physical Equipment is placed

  • Configuration is therefore managed based on

the Functional Structure: therefore, System/End Item is assigned to a Functional LCN and applied to the Physical LCNs

29

slide-30
SLIDE 30

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

  • Fit definition - Parts– Parts can be made

available to Fit Definition by:

  • identifying them as Equipment
  • identifying them as catalogued (has an

NSN) or Non-Catalogued BOM items (assemblies)

  • further filtering can be defined for

maintenance significant items

30

  • Configuration shown is

for Canadian DND with Equipment separated from PIs by ERN designation

slide-31
SLIDE 31

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

slide-32
SLIDE 32

SAP ERP

SAP

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

slide-33
SLIDE 33

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Fit Definition

33

  • R18 Release of OmegaPS will see continued

change to Fit Definition

  • Key Changes
  • Ability to create SAP files for PPA and

Maintenance Plans

  • Ability to assign Frame and Compartment

ID to Naval equipment

  • Ability to identify VIC Weight Group
  • Future initiatives in Fit Definition may include
  • New export for Failure catalogue mapped

to SAP

  • Direct linkage from SAP for repair parts
  • New SAP update capability
  • Revised material identification
slide-34
SLIDE 34

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Embedded Publications

  • Ability to store files of any format in

accordance with GEIA –STD - 0007

  • Ability to link publications to create Illustrated

Parts Catalogues or Views as required

34

slide-35
SLIDE 35

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Embedded Publications

  • OmegaPS is able to store files of any format

within the database

  • These files can be uploaded and identified

with any required set of data

35

  • Show Publication

allows the file to be displayed

slide-36
SLIDE 36

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Embedded Publications

  • Linking files to projects can be done from

within Structure Manager

36

  • Hi-lighted LCN

Nomenclature indicates that a file has been attached

slide-37
SLIDE 37

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Embedded Publications

  • Depending on the file type, some files can be

displayed within a form (files that can be displayed on a single page)

37

  • This capability will be used to enable the

generation of Illustrated Parts Books

slide-38
SLIDE 38

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Embedded Publications

  • R18 Release of OmegaPS will see continued

change to Embedded Publications

  • Key Changes
  • Introduction of IPBS (Illustrated Parts

Breakdown System)

38

  • Future initiatives in Embedded Publication

will include

  • Ability to map to Maintenance objects as

well as Structure -this will enable tagging

  • f CBT to the correct are of the database
  • IPBS Mobile will encapsulate all IPBS

functionality in a mobile product with commercial and DND configurations

slide-39
SLIDE 39

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Support Analysis

  • The OmegaPS Supportability Analysis

Module (OSAM) links modeling and baselining solutions directly into the LSAR

  • Life Cycle Costing, Level of Repair Analysis

and Sparing Analysis now reside directly in the same database.

  • This module replicates

Analyzer but resides within the OmegaPS Application

39

slide-40
SLIDE 40

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Support Analysis

  • As with Analyzer, OSAM is capable of

modeling:

  • Single PE or multi-PE structures
  • Multiple possible support organizations
  • Multiple planned PE distributions
  • The screen shot shows a

support organization with a planned PE distribution

40

slide-41
SLIDE 41

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Support Analysis

  • Analysis is done against a specific selected

scenario which brings together a specific PE configuration and a specific Support Organization and PE distribution

  • Analysis can be

completed with

  • A selected Measure of

Effectiveness

  • A selected Sparing
  • ption
  • A selected LCC Sparing
  • ption; and,
  • A selected Logistics

Cost optimization

  • Note the baseline

selection

41

slide-42
SLIDE 42

Supportability Analysis Data OmegaPS– Add On Capabilities

Support Analysis

42

  • OSAM has a number
  • f ways to source data
  • Import from core

LSAR

  • Import using an

xls Template

  • Import from xml

file (OSAM to OSAM or Analyzer to OSAM

  • OSAM also exports in

xml format

slide-43
SLIDE 43

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Support Analysis

  • R18 Release of OmegaPS will see continued

change to OSAM/Support Analysis

  • Key Changes
  • xml data transfer
  • compatibility mapped to Analyzer dll
  • improved data management

43

  • Future initiatives in Support Analysis will

include

  • Incorporating changes to math models
  • Further integration with LSAR data to

update LSAR data with OSAM results

slide-44
SLIDE 44

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Change Management

  • Change Management allows for the complete

control of any changes to the LSAR data through Engineering Change Requests (ECRs) and Engineering Change Orders (ECOs)

  • One level of management approval can be

invoked before any change is made.

44

slide-45
SLIDE 45

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Change Management

  • Change Management is in use in the

Australian Defence Force (ADF) and DND

  • Specific configurations have been created for

both ADF and DND as well as a Commercial version

  • Change Management is invoked by Project.

45

slide-46
SLIDE 46

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Change Management

  • R18 Release of OmegaPS will see continued

change to Change Management

  • Only minor changes to improve messaging

and work flow

46

  • Future initiatives in Change Management will

include

  • GEIA may introduce Configuration

Management within GEIA STD 0007 - if this occurs OmegaPS Change Management will be modified to adapt to the new standard

slide-47
SLIDE 47

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Publisher

  • Allows for linking to a Content Management

system of your choice

  • LSAR data managed in the product; authoring

and format issues handled by the content management system

  • Allows for S1000D data module management

47

slide-48
SLIDE 48

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Dynamic RCM

  • MIL-STD-1388-2B and GEIA-STD-0007 both

allow for an item to have a single function

  • SAE JA 1011 assumes an item under

analysis has multiple functions

  • What are the functions and associated

desired standard of performance of the asset in its present operating context (functions)?

  • A proposal has been made to Tech America

(owners of GEIA-STD-0007) to expand the data model to include multiple functions

  • This concept was included as a module

within OmegaPS called Dynamic RCM in 2008

48

slide-49
SLIDE 49

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Dynamic RCM

  • Dynamic RCM allows the product to link a

failure mode to a function and link both to a mitigating maintenance action if required/appropriate

49

  • In the DND version this information has been

configured to create SAP Catalogues specific to the ERN (EMR/FLOC) being maintained

slide-50
SLIDE 50

Supportability Analysis Data OmegaPS– Add On Capabilities

OmegaPS Application Dynamic RCM

  • R18 Release of OmegaPS will not include

any changes in this area

50

  • Future initiatives in Dynamic RCM will include
  • GEIA will be introduce the Dynamic RCM

concept to GEIA STD 0007

  • Therefore Dynamic RCM will be

incorporated into the new GEIA 0007 product

slide-51
SLIDE 51

Supportability Analysis Data OmegaPS– Add On Capabilities

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