1. Slide 1 of 14© 2015 ENGISIS INTEROPERABILITY FOR PRODUCT LIFECYCLE MANAGEMENT Ing. Xenia Fiorentini PLM and Interoperability in the defense sector

2. Slide 2 of 14© 2015 ENGISIS Agenda  The PLM context −Interoperability in the PLM context  The PLM context in the defense sector −Interoperability for the defense  Cases

3. Slide 3 of 14© 2015 ENGISIS The PLM context - recap  PLM stands for Product Lifecycle Management −The product lifecycle includes all the phases of the product life, from concept definition to product disposal and recycle −PLM imposes to manage the lifecycle from its beginning  Why would anybody want to do PLM? −To optimize the cost of the lifecycle (cost of design, production, maintenance, usage...) −To shorten the time to market −To forecast problems that can arise later −To provide services for the product −To maintain the engineering knowledge of the company in an integrated way and reuse it

4. Slide 4 of 14© 2015 ENGISIS The problem (1/2)  Several proprietary software applications manage the product data during its whole lifecycle −Applications for requirements modeling, for engineering design, for manufacturing cycles, for maintenance procedures, customer support, etc.

5. Slide 5 of 14© 2015 ENGISIS The problem (2/2)  The business processes need these applications to communicate and share product data with each other −Internal processes: requirements tracking for certification, integrated logistic support for new types of contracts, reuse of manufacturing capabilities, design for sustainability, engineering changes due to customers complains, etc. −Collaboration with partners, suppliers and customers −Long term archiving  Why is the communication between applications a problem? −The applications are proprietary: few companies know how to “access” them −The versions of the same application are often not compatible −The number of involved applications is high just right now. Plus, new applications can be used in the future −Data are sometimes managed by legacy applications

6. Slide 6 of 14© 2015 ENGISIS How the problem is commonly solved  Migrate legacy applications to a unique application  Implement some sort of application programming interface (API) for each application, and then, in each application, implement "glue code" that exploits the APIs of other applications to link them together  Design a single database to store the data of multiple applications, and implement each of the applications against this database (or repository) THESE OPTIONS ARE EXPENSIVE (see presentation “Interoperabilità: costi e benefici”) “ This report, prepared for NIST by RTI International and the Logistic Management Institute, estimates the cost of inadequate interoperability in the U.S. capital facilities industry to be $15.8 billion per year.” [Cost Analysis of Inadequate Interoperability in the U.S. Capital Facilities Industry, NIST]

7. Slide 7 of 14© 2015 ENGISIS Engisis focuses on Interoperability for PLM Use standards and specifications  PLCS (ISO 10303 AP 239) and DEX  PDM Schema and ISO 10303 AP 233, AP 242, AP 235  ISO 15926  S3000L  NIILS (Italian inter-forces specification for ILS) Assess models against processes We investigate existing product data models and their relationship with the processes. We apply data models to the business context. Deploy common models We apply standard data models for business cases and deploy the product data models to solve your interoperability issues. Use skills and technology  Model-based engineering  Model and ontology for product data  Models transformation  Languages for data and process modeling  Software architecture and programming Train We provide educational services and trainings adapted to each organizational level, from business managers to software implementers. Implement interoperability Assure interoperability between the software applications that manage product data during the whole product lifecycle.  Test cases and data sets  Products

8. Slide 8 of 14© 2015 ENGISIS The PLM context in the defense sector  Doing PLM in the defense sector is challenging −Products are complex −Products have very long lifecycles −Nobody is responsible for the whole product −Acquisition and Deployment are managed as separate phases −Nobody has ever calculated the total cost of ownership of the products −The actors in the lifecycle are numerous −The actors in the lifecycle are not necessarily known

9. Slide 9 of 14© 2015 ENGISIS Interoperability in the defense sector: an example FMECA Analysis Maintenance Tasks FunctionalAnalysis Design From the delivery of a product, to the delivery of capabilities

10. Slide 10 of 14© 2015 ENGISIS Interoperability in the defense sector: an example FMECA Analysis Maintenance Tasks FunctionalAnalysis Design From the delivery of a product, to the delivery of capabilities DATA IN STANDARD FORMAT

11. Slide 11 of 14© 2015 ENGISIS Interoperability in the defense sector: an example FMECA Analysis Maintenance Tasks FunctionalAnalysis Design From the delivery of a product, to the delivery of capabilities DATA IN STANDARD FORMAT The failure effects of the FMECA are derived from the relationships between the product components and hte functional analysis Maintenance tasks are linked to failure modes, which are detected through the failure effects, they are executed over the components and need equipments and tools

12. Slide 12 of 14© 2015 ENGISIS Which standard?  ISO TC 184/SC 4 (Industrial data) created a serie of standards. −ISO 10303-239 is the standard for Product Life Cycle Support (PLCS) Define product requirements and configuration, including relationships between parts and assemblies in multiple product structures (as- designed, as-built, as- maintained). Request, define, justify, approve, schedule and capture feedback on work and related resources. Describe and capture feedback on product properties, states, behavior and usage. PLCS Capabilities Product Description Property, State & Behavior Work Management Support Solution & Environment Define the support for a given set of products in a specified environment and define support opportunity, facilities, personnel and organizations.

13. Slide 13 of 14© 2015 ENGISIS Case 1: MoD/supplier interoperability for LSA  The MoD customizes a commercial tool (SAP) to manage the configuration of both the design of the naval systems and their installation, together with their logistic engineering data  The MoD needs to talk with the suppliers −To sync the configurations of the systems, and their logistics parameters −To sync the maintenance plans  We build a PLCS adapter to this tool (by following, also, the S3000L specification)

14. Slide 14 of 14© 2015 ENGISIS Case 2: PLM Interoperability strategy  A multinational company is deploying a PLM strategy. Interoperability is seen as a means to −Give enough freedom and security to each country −Deploy a step-by-step PLM solution −Implement multinational collaboration −Exchange data with suppliers and partners Single sign-on Forum Management of product structures Project management capabilities Search for product data in TAS Manage organization, projects and workflows Register systems Manage mappings Check Assign Query Browse Print ADMINSYS SHARE OPT USER Synchronize eBOM Transfer Technical baseline Synchronize Change Requests Synchronize CCN Synchronize RFD Transfer the as-designed baseline Synchronize Change Proposals  We plan a standard-based share&exchange strategy −We specify ›Collaboration processes ›Functionalities ›Data modeling ›Architecture −We make a Business Case Analysis with real processes, data and systems

15. Slide 15 of 14© 2015 ENGISIS Case 3: Coalition/Joint Logistics Interoperability  The CLI/JLI project −each military service brings its own assets to repair its weapon systems −assets need to be purchased, stocked, managed and disposed by each military service −we can lower the cost of the repair processes by making the assets shared among the military services in a joint/coalition interoperability logistic scenario  The scenario −items are marked through UIDs (Unique Item Identifications) −one military service requires an item to be repaired −another military service repairs it  We build interoperability between −The ERP of each military service −The UID registry

16. Slide 16 of 14© 2015 ENGISIS Xenia Fiorentini xenia.fiorentini@engisis.com +39 06 80368 947 Engisis S.r.l. www.engisis.com Via G. Peroni 442/444, 00131 Roma, Italy INTEROPERABILITY FOR PRODUCT LIFECYCLE MANAGEMENT Thanks! Grazie!

17. Slide 17 of 14© 2015 ENGISIS HOW: BUSINESS CASE A Customer : power-plant design and operations Project title: Models interoperability and systems architecture for PLM Project duration: 2 years (ongoing) Partners: an engineering school and an university Project data 3 scenarios per year, each including state of the art, technical proposal and demonstration Modeling of catalogues, CAD data and business rules for PLM Usage of meta-modeling techniques, application of ISO 15926, definition of ontologies, selection of languages for rules expression Approach Analysis and application of standards to exchange product data Modeling and mapping of proprietary data Technical benchmarking of existing solutions Software development and application in real cases Achievements PRODUCT DATA MODELING AND DEPLOYMENT

18. Slide 18 of 14© 2015 ENGISIS HOW: BUSINESS CASE B Customer : international defense organization Project title: Coalition logistics interoperability through PLCS Project duration: 6 months Partners: 3 consulting companies Project data Development of use cases, architecture diagrams and test cases Definition of the Business Object model and associated XML schemas Software customization and validation Approach Definition of meta-data for the exchange Use of everyPLM to exchange PLCS data for sharing maintenance capabilities between proprietary tools Software demonstrations in environments with high security requirements Achievements SOFTWARE APPLICATIONS IMPLEMENTATION

19. Slide 19 of 14© 2015 ENGISIS HOW: BUSINESS CASE C Customer : defense prime contractor Project title: S3000L Proof of concept Project duration: 3 months Partners: support from CALS Italy Project data Analysis of data as currently managed by the customer Application of the Logistic Support Analysis (LSA) business processes: as-is and to-be Usage of the PLCS SDK to implement the S3000L PLCS DEXes Support for sharing achievements and obstacles in international industrial communities Approach Educational sessions: LSA processes and data Development of reference data and mappings Development of an S3000L generator and viewer Feedback reporting to the S3000L community Achievements BUSINESS PROCESSES MANAGEMENT