Rolls-Royce & Ministry of Defence Pilot for Early Implementation of PLCS Marine Olympus/Tyne

1. Rolls-Royce & Ministry of DefencePilot for Early Implementation of PLCSMarine Olympus/Tyne Summary 3 Feb 04

2. R-R & MoD Early Implementation of PLCS • HISTORY • Meeting held, back in July 02, with MoD, R-R & UKCeB to discuss joint opportunities for “Early Implementation” of PLCS. • This and subsequent discussion agreed Early Implementation would be in the interest of both organisations. • Proposed the Early Implementation should address • The data requirements for operating TC/CLS (Total Care /Contracted Logistic Support) type contracts. • This should include feedback and use of operational data. • Early Implementation would involve a Project and a Software Application. Proposals for the project was • Marine Olympus/Tyne PLCS Inc. (c) 2002

3. R-R & MoD Early Implementation of PLCS • APPROACH • Early Implementation will enable • Understanding of what is involved in applying PLCS • Major problem identification and support positioning for future implementation • Development of a “template” for the implementation process • Opportunity for R-R & MoD to work together to start the process of realising our investment in PLCS • Demonstration, to Government and Industry, of what can be achieved • Actual benefit to current business from application of PLCS • Programme being finalised for Early Implementation to align with PLCS deliverables starting Oct 02 through Mar 03. • Assumes PLCS Modules will be progressively complete by Dec 02 and clear ballot by Mar 03 with Draft IS by May 03 cleared ballot by Oct 03. • Assumes Marine Olympus Tyne contract in place end 03. PLCS Inc. (c) 2002

4. R-R & MoD Early Implementation of PLCS Current Support Arrangements – Olympus and Tyne • 1st Line 4th Line Spares Naval Base Store Engines Commodity Management CRSS Stores (MPS owned) Provisioning Technical Support MPS IPT PDS/ISS Data Waterfront (2nd Line) PLCS Inc. (c) 2002

5. R-R & MoD Early Implementation of PLCS • REVISED PLAN • Initial Meeting held at Abbey Wood, 28 October 02, involving IPT (Paul Denton) MoD (Margaret Christison/Mike Newton) & R-R (Nigel Walker). • While there were concerns on the current operation actions were in hand to achieve Improved performance. • Data availability & exchange was not considered a major driver but it was accepted there is no current automated exchange and much additional data would be required for TC. • Work on data exchange had been undertaken before (previous report) and although not actioned could be used as the basis of the “As Is” situation. • MoD would fund mapping “As Is” to PLCS to understand gaps/opportunities. • R-R would identify “To Be” requirements & map to PLCS. • On completion of mapping agreement would be required on way forward. PLCS Inc. (c) 2002

6. R-R & MoD Early Implementation of PLCS • EI Programme Main Milestones • Phase 0 – Objectives & Approach • Phase 1 - Planning & Set-up • Phase 2 - Implementation • Define the changes, or requirements, for the software interface to achieve standardised export/import capability for each system (implement a DEX/DEX’s) • Develop software, or software changes, necessary to support each DEX • Agree business protocol and processes for data exchange • Test and validate the business exchange processes • Agree adoption of proven exchange capability for program • “AS IS” Report funded by MoD produced by LSC, Aug 03 • “To Be” Report funded by R-R produced by LSC, draft Dec 03 • Now moving to implement recommendation for a e-logbook based on DEX delivery PLCS Inc. (c) 2002

7. R-R & MoD Early Implementation of PLCS One of the deliverables is to put in place an R-R e-logbook • New build ships are being built “electronically” and similar ideas for managing rotables are already emerging for Air vehicles. Concept will be needed by Air, Sea and Land for all Complex equipments • Technical Datum Packs will be delivered in electronic form, thus the new concept of a “Digital Ship” is forming. e-Logbook will be a component of the Digital ship • Thus GTCU APSI +history will slot into the parent ship information model (Digital Ship) when it is installed. Similarly when it is removed for overhaul it is simply un attached. • The e-Logbook would contain exactly the same information as the PLCS Information flow • Contains more information than paper logbook • Collection and maintenance of information becomes easier • Relates to concept of Product Configuration Information in PLCS • May also relate to plan for Equipment Health Monitoring (EHM) • For existing platforms and equipment the e-logbook can be provided as a CD with the product and a laptop, the content is maintained and re-cut to the CD for return to R-R on a regular basis and on equipment removal. • The e- Logbook is seen as essential step if ISO 10303 STEP (PLCS) standard to be realised. PLCS Inc. (c) 2002

8. R-R & MoD Early Implementation of PLCS • E-Logbook Stage 1 • Create and populate an e-logbook by implementing the required sub-set of the total AP239 information schema to support the creation of an e-logbook for Olympus and Tyne marine gas turbine engines • This EI be of a prototype nature and will be created in Oracle • Populate the implemented schema with the information content e-logbooks for a ship set of two actual GTCUs of each type • Provide an initial viewing mechanism of the e-logbook content. • Write the URD and SRD for the necessary software components to Support use of the e-logbook across the extended enterprise. The URD & SRD should specify the requirements for functionality • E-Logbook Stage 2 • Create an initial operational capability • Further Stages Identified in “To Be” Report • R-R order launched Feb 04 for LSC to action Stage 1 PLCS Inc. (c) 2002

9. R-R & MoD Early Implementation of PLCS • DEX’s Data Exchange Sets currently being developed • Product breakdown for support • Product as individual • Support Drivers • Task Set • Work Package Definition • Work Package Reporting • Maintenance Plan • Fault states • Operational feedback PLCS Inc. (c) 2002

10. R-R & MoD Early Implementation of PLCS • a PLCS Inc. (c) 2002