Embed Size (px)
Citation preview
OmegaPS UGM 2010
•Introduction
•Data Flow Process
•Communication
•Questions
Introduction
•Since both industry and DND have traditionally shared Logistics data based
on MIL-STD-1388-2B, it is extremely important that processes and
procedures are in place to execute the movement of data from the vendor to
DND.
•It is essential that vendors and DND share a clear understanding of the
steps involved in the transition and the data requirements associated with
each step.
•Effective direct communication between industry and DND data specialists
is a key element in the reduction of project risk.
•We will explore some of the key processes specific to the Navy Fleet Data
Management transition of data. Many of these processes are common to Air
and Land elements as well as such may be applied accordingly.
Data Flow Process
DA
F
END
End
C
Finalize EFT Migrate to MES-D
Register System
ERN
Receive and
Validate LSAR
Deliverables
Load to OmegaPS
Supportability
Receive and
Validate IPC
PPB Data Set(s)
Perform IP
Activities
Conduct
Supportability
Analysis
Condition MES-D
Master Data
(Fit Definition
Module)
Initiate Naval
Maintenance
Management
System
Transfer MES-D to
SAP
Validate MES-D
Data by TA
Migrate Core LSA
Data to MES-D
Process ESLCN to
DSCO CGCM and
MA
B
E
Data Flow Process
•Register the System Level Equipment in DND and update the Equipment
Family Tree in OmegaPS
END
A
Raise DND 752
Generate Hull/
Platform EFT
Block Diagram
(MES-D)
Install and Identify
ERN on Hull/
Platform (MES-D)
Impact Analysis on
Class/Ship
Configuration
(EFT)
Confirmation/
Validation of 752Process DND 752Yes
No
Data Flow Process
•Register the System Level Equipment in DND and update the Equipment
Family Tree in OmegaPS
END
A
Raise DND 752
Generate Hull/
Platform EFT
Block Diagram
(MES-D)
Install and Identify
ERN on Hull/
Platform (MES-D)
Impact Analysis on
Class/Ship
Configuration
(EFT)
Confirmation/
Validation of 752Process DND 752Yes
No
Data Flow Process
END
A
Raise DND 752
Generate Hull/
Platform EFT
Block Diagram
(MES-D)
Install and Identify
ERN on Hull/
Platform (MES-D)
Impact Analysis on
Class/Ship
Configuration
(EFT)
Confirmation/
Validation of 752Process DND 752Yes
No
Data Flow Process
B
EBS Only
LCMM Template
MS Access
ASCII.txt
Load Data in
SandBox
Receive
Deliverables from
PMO
SOW
Compliancy
Check
No
Load Data 13882B
Compliancy
Module
13882B
Compliancy
Check
Yes
No
EndYes
Data Flow Process
B
EBS Only
LCMM Template
MS Access
ASCII.txt
Load Data in
SandBox
Receive
Deliverables from
PMO
SOW
Compliancy
Check
No
Load Data 13882B
Compliancy
Module
13882B
Compliancy
Check
Yes
No
EndYes
Data Flow Process
B
EBS Only
LCMM Template
MS Access
ASCII.txt
Load Data in
SandBox
Receive
Deliverables from
PMO
SOW
Compliancy
Check
No
Load Data 13882B
Compliancy
Module
13882B
Compliancy
Check
Yes
No
EndYes
Data Flow Process
B
EBS Only
LCMM Template
MS Access
ASCII.txt
Load Data in
SandBox
Receive
Deliverables from
PMO
SOW
Compliancy
Check
No
Load Data 13882B
Compliancy
Module
13882B
Compliancy
Check
Yes
No
EndYes
Data Flow Process
Receive and Validate LSAR Deliverables CSO ILS Workflow
FD
MP
MO
/ T
AO
EM
/ C
on
tra
cto
r
REVISED
16 May 2010
DATE
23 March 2010
PAGE
1 OF 6
DRAWN BY
Pennant Canada
Produce LSAR
DeliverablesSend to PMO / TA
Correct and
Re-Submit LSARSend to PMO / TA
Receive Deficiencies
ReportSend to OEM for Corrections
Validate LSAR
Deliverables FormatSend to +DMMS 3 Fleet Data
Management@ADM(Mat)
DMMS@Ottawa-Hull
Delivery
Compliance CheckLoad Data in Sanbox
Conduct Initial Review of
Deliverables
Pass
Fail
Load Data 13882B
Compliancy Module ENDPass
Fail
PMO / TA may authorize FDM
to liaise directly with the OEM
contractor source of the
deliverable for clarification and
corrections.
Data Flow Process
Receive and Validate LSAR Deliverables CSO ILS Workflow
FD
MP
MO
/ T
AO
EM
/ C
on
tra
cto
r
REVISED
16 May 2010
DATE
23 March 2010
PAGE
1 OF 6
DRAWN BY
Pennant Canada
Produce LSAR
DeliverablesSend to PMO / TA
Correct and
Re-Submit LSARSend to PMO / TA
Receive Deficiencies
ReportSend to OEM for Corrections
Validate LSAR
Deliverables FormatSend to +DMMS 3 Fleet Data
Management@ADM(Mat)
DMMS@Ottawa-Hull
Delivery
Compliance CheckLoad Data in Sanbox
Conduct Initial Review of
Deliverables
Pass
Fail
Load Data 13882B
Compliancy Module ENDPass
Fail
PMO / TA may authorize FDM
to liaise directly with the OEM
contractor source of the
deliverable for clarification and
corrections.
Data Flow Process
Receive and Validate LSAR Deliverables CSO ILS Workflow
FD
MP
MO
/ T
AO
EM
/ C
on
tra
cto
r
REVISED
16 May 2010
DATE
23 March 2010
PAGE
1 OF 6
DRAWN BY
Pennant Canada
Produce LSAR
DeliverablesSend to PMO / TA
Correct and
Re-Submit LSARSend to PMO / TA
Receive Deficiencies
ReportSend to OEM for Corrections
Validate LSAR
Deliverables FormatSend to +DMMS 3 Fleet Data
Management@ADM(Mat)
DMMS@Ottawa-Hull
Delivery
Compliance CheckLoad Data in Sanbox
Conduct Initial Review of
Deliverables
Pass
Fail
Load Data 13882B
Compliancy Module ENDPass
Fail
PMO / TA may authorize FDM
to liaise directly with the OEM
contractor source of the
deliverable for clarification and
corrections.
Data Flow Process
•Expansion of the Equipment Family Tree (sub system equipments)
EndD
Update Hull/
Platform
Definition EFT
(MES-D)
Generate Hull/
Platform EFT
Block Diagram
Register Sub
ERN(s) (DND 752)Yes
Confirmation/
Validation of
DND 752
Process DND 752
No
Reserve
Functional
Locations in SAP
Data Flow Process
•Expansion of the Equipment Family Tree (sub system equipments)
EndD
Update Hull/
Platform
Definition EFT
(MES-D)
Generate Hull/
Platform EFT
Block Diagram
Register Sub
ERN(s) (DND 752)Yes
Confirmation/
Validation of
DND 752
Process DND 752
No
Reserve
Functional
Locations in SAP
Data Flow Process
•Conditioning Data in OmegaPS for DND Navy for ERP and DRMIS
E Build Functional
Structures
Assign Usable On
Codes
ERN/EAC
Assignment of
Material
Map Physical and
Functional
Structures
Build
Configurations
Assign Structure
Codes
Validate Fit
Definition DataEND
Data Flow Process
E Build Functional
Structures
Assign Usable On
Codes
ERN/EAC
Assignment of
Material
Map Physical and
Functional
Structures
Build
Configurations
Assign Structure
Codes
Validate Fit
Definition DataEND
Data Flow Process
•Conditioning Data in OmegaPS for DND Navy for ERP and DRMIS
E Build Functional
Structures
Assign Usable On
Codes
ERN/EAC
Assignment of
Material
Map Physical and
Functional
Structures
Build
Configurations
Assign Structure
Codes
Validate Fit
Definition DataEND
Data Flow Process
•Conditioning Data in OmegaPS for DND Navy for ERP and DRMIS
E Build Functional
Structures
Assign Usable On
Codes
ERN/EAC
Assignment of
Material
Map Physical and
Functional
Structures
Build
Configurations
Assign Structure
Codes
Validate Fit
Definition DataEND
Data Flow Process
E Build Functional
Structures
Assign Usable On
Codes
ERN/EAC
Assignment of
Material
Map Physical and
Functional
Structures
Build
Configurations
Assign Structure
Codes
Validate Fit
Definition DataEND
Data Flow Process
Non Complex
Complex
Depth of Detail
End
F
Build Manually in
SAP
Migrate MDP Data
to SAP
Extract Data Set(s)
From MES-D
Master Data
Condition Data
Set(s)
Merge Oracle BI
Data to Applicable
MDP Tab(s)
Validate SAP DataValidate MDP
Data
Determine Data
Requirements
Notify NEM of
Equipment
Change to
Structure - EC
Process
Data Flow Process
Non Complex
Complex
Depth of Detail
End
F
Build Manually in
SAP
Migrate MDP Data
to SAP
Extract Data Set(s)
From MES-D
Master Data
Condition Data
Set(s)
Merge Oracle BI
Data to Applicable
MDP Tab(s)
Validate SAP DataValidate MDP
Data
Determine Data
Requirements
Notify NEM of
Equipment
Change to
Structure - EC
Process
Communication
•Set up an Integrated project team of LSA data specialists
•DND reps that will be doing the work
•OEM reps that will be doing the work
•Prevents delays in the delivery of data
•Ensures the project objectives are met
•Allows DND and Industry to leverage experience and expertise
•A Simple phone call or e-mail can reduce delays by months. A current DND
Navy project is currently benefiting from this. The DND LSA specialist is
communicating directly with the Vendor LSA specialist in the creation of
compliant data sets.
•A stepped approach is used.
•Structure ---- X and H tables
•Failures ---- B Tables
•Maintenance Tasks --- C tables
•Other tables
•Data at each step is trial loaded into OmegaPS to ensure data
integrity and corrective
•This data represents the fundamental information required for
operations.
Questions?
