PLCS Face-to-Face: LSC Group – Lessons from PLCS Activities

1. PLCS Face-to-Face:LSC Group – Lessons from PLCS Activities Huntsville, Oct 2006 Tim Turner, LSC Group

2. LSC Projects • RB199 Prototype Demonstrator- Asset Mgt • Work Package Management – UMMS (v1) • Configuration Management – SDD & VMP • TDP – Technical Datum Pack handover • Def Stan 00-60 – LSAR Mapping for UK MoD • Contractor Logistic Support: Electronic Logbook • Smart Codification • Lean Logistics Model

3. LSC Projects • RB199 Demonstrator- Asset Management • 1st PLCS prototype. RR&MoD(RAF) Sync Asset+CM+Tech Pubs. In-service exchange of fault report & feedback to improve history recording, acc. & speed of tasks for maintenance activities. • Work Package Management V1- UMMS • Exchange work spec between operator & (privatised) dockyards • Configuration Management – SSD – VMP • Exchange CM between operator & (privatised) dockyards • TDP handover: Product Info Explorer • Consistent independent view over many TDP parts/formats; Links AP203/239 i.e. PLCS view links prod struct to 3D,LSAR, Tech Pubs & recently Electrical AP212 • Def Stan 00-60 – LSAR Mapping for UK MoD • Mapped all LSAR elts >500 DED to PLCS. Similarity wth 1388-2B • Contractor Logistic Support: Electronic Logbook • Olympus Marine Gas Turbines. Moving from spares only ->Total Care Package. GTCU+CM+LifeHistory+Feedbk -> Lifing follws item. Operator free of supplier s/w. Component of digital ship; On trial at HMS Sultan • Smart STEP Codification • Open source tools to consistently add/extract catalog data from step files. UK & US NCB, ECCMA CTC, NIST & LSC developing SSC with industry partners. • Lean Logistics Model

4. Lean Logistics Model – LLM CRP PoC Background: • Many independently developed logistic processes and systems evolved to meet single Service requirements Purpose: • DLO needs a view over these system applications • evaluate performance (e.g. asset availability) across the enterprise Challenge: • Different generations of IS • Holding a wealth of logistics data locked in many IS stove-pipes - in different proprietary formats • Increasingly provided by industry in both acquisition and in-service. Need: • Open standards based logistics system integration to create a coherent data repository as the basis for improved E2E business workflow and management • Automation; Standardisation; E2E; Auditable • Filtering; Exception reporting; Decision support; Through Life Management Solution: • AP-239 as central repository to gather data from 10 donor systems using PLCS adaptors as required • Tied PLCS integration with a Collaborative Working Environment to support workflow & business process intelligence • Demonstrated onsite at MoD & Bath STEP meeting 2005

5. the enterprise performance dashboard the enterprise performance dashboard e.g.asset availability = 75% e.g.asset availability = 75% "cloud of magic transformation" analysis driven by business intelligence approaches with a common information model for enterprise integration stove-piped data sources stove-piped data sources Current – Future Context manual transfer of data from various sources into various analysis tools - extensive human intervention to resolve meaning of source data

7. CRP MoD Foxhill Feb to May 2005 • Demonstrated 1yr of activity across 4 sessions over the day; intro faults, feedback, repairs, redesign etc.. -> availability of product • 220 attendees (var.ranks CDL & DCDL, CDP & DCDP, DLO 2/*s, • 211 Directors from ADs/DDs/IPTLs/Desk Officers) • Feedback from Questionnaires: Specifically, what potential benefits can be envisaged from adoption of the LLM? • “Better informed decision-making. Reduction in costs. Delivery of capability” • “Managing new contracts and workflow/ project management in an end-to-end environment” • “Will make TLMP easier” • “Support proper market (supplier) management” • “Better sparing information for future project procurements” • “Benefit is the ability to view different systems in a coordinated and integrated fashion” • Do you see potential “value add” from adoption of an integrated non-proprietary repository: • A. Yes 98.5% : No 0% : Not Sure 1.5%

8. Lessons learned • AP239 mapping • well-defined input information & a holistic view of all of the data elements to be mapped are essential, prior to commencement of any PLCS mapping activity, to allow the efficient development of the conceptual PLCS information model to meet business needs • Enterprise Repository • Oracle object-relational database • Object Relational schema directly from the PLCS long form • Unsupported multiple inheritance from the AP239 schema • EXPRESS STRING limited to VARCHAR2 • name & id = 255 (else huge overhead) • all other fields = 4000 • added common base type • unique identifier & source database identifier attributes • support for EXPRESS SELECT type

9. Lessons learned • Enterprise Repository • Added table to map long names • Oracle limit of 32 characters (AP239 schema includes longer names) • Used de-normalized tables for each business object in the mapping • OASIS Capability business objects • e.g. ‘item of production’, ‘item of supply’ and ‘asset’ • Mapping used (own) templates -> • feedback to OASIS architecture • Data integration • a common reference data library is required to correlate data from different systems to allow consistent reporting of integrated data & the ability to analyse such things as cause & effect relationships between data in disparate systems • the data element "explosion" between source system data elements & their instantiation in the PLCS schema in the context of very large data sets had an impact on data integration performance. Multi-threading processes & the use of de-normalised layers in the database architecture gave significant performance improvements • quality of donor system data is evident -> cleansing rules

10. Conclusions • AP239 suitable for scope of business domain • AP239 suitable as an enterprise integration model • Implementation challenges are not intractable

11. ENDBackground Slides Follow

12. Asset Management • RB199 Tornado Fast Jet Aircraft Demonstrator • Synchronise Asset, CM+Tech Pubs -> improved acc. & speed of tasks for maintenance activities. • Rolls Royce, RAF, CITIS. • Gave first confirmation of PLCS Deliverables • Exchange of in-service configuration, maintenance tasks, feedback of engine fault data, design change, new work instructions, new part and permissable configuration

13. Work Package Management • Unit Maintenance Management System (UMMS) • UMMS • Implements principles of Reliability-Centred Maintenance (RCM) in UK Navy • Inc. UMMS Aboard (ship-based maintenance at sea) & shore-based system • Allows Navy to gather info across fleet • Challenge: • UK Government no longer own a dockyard with capabilities to perform repair & overhaul of Navy vessels, and • Privatised dockyards operate independent work planning systems • Hence MoD face data exchange problem with each dockyard used. • Prime PLCS target • LSC has produced a capability to generate Work Packages in AP239 format to use with yards.

14. Configuration Management - VMP • Challenge: • MoD using Submarine Definition Database (SDD) • Dockyard using Vessel Material Planning system (VMP) • LSC verified PLCS supports all necessary capability to represent the Master Configuration Record of a submarine • AP239 can also represent the complex Fleet Area code • Code is a hybrid of product structure, using physical, zonal and system elements

15. TDP Handover Framework for Interoperability • Prime contractor delivers complex asset to owner, plus large amount of support information (in many formats). • Huge challenge for owner to gain consistent view across the complete & varied data set. • Product Information Explorer (PIE) demonstrated that PLCS has the capability to provide an integrated view across the TDP items and sources. • Included integration of AP203 & AP239 for linking 3D geometry to • Product structure, LSAR, Tech Pubs • Recently integrated AP212 for electrical routing and device information • Info is presented in context of defined product structures – allows easy & consistent method of access to wide breadth of data (e.g DB’s, spreadsheets, text files, xml files, Step files etc.. • Such a range is necessay for typical complex asset

16. Def.Stan 00-60 Mapping • 00-60 – Specifies the Logistic Support Analysis Record (LSAR) – a derivative of 1388-2B • Provides mechanism for extensive definition of Support Solutions, including; • identification of LSI within product • specification of apropriate tasks to maintain product • LSC mapped all elements of the LSAR (> 500 DED) to relevant ones in AP239 for MoD • May also be basis for integrating support engineering into wider enterprise context • E.g. enables MoD to view total set of LSAR’s for all acquisition projects • Also enables Integrated Project Teams (IPT) to import LSAR into other AP239 compliant applications (e.g. PDM or ERP).

17. Electronic Logbook Contractor Logistic Support: PLCS important role when asset owners rely upon contractors for logistic support • Context: Marine Gas Turbine Supplier moving from traditional spares support to a total-care-package. • GTCU+CM+History -> Equipment Health Monitoring • Component of digital ship; • Supplier needs the CLS contract to run efficiently • AP-239 able to replace current physical collection of information accompanying engine • PLCS provides Product Configuration Information, allows history/life info storage • Equipment fitted to slots in the structure; can be removed/refitted as required. • Each operation recorded. • Removed item carries own usage info with it – to next location. • Parent carries record of which equipment fitted, when fitted & how much usage consumed while fitted • Owner gets access to product support info without being tied to supplier’s software • Contractor gets access to product feedback which helps to provide approp. support • Typically 4 turbines per ship • Prototype On trial at HMS Sultan (RN MES)