Download to read offline
Uploaded byDr Nicolas Figay
Sip@iPLM 2016
The document discusses the Standard Interoperability PLM (SIP) project. The SIP project aims to: 1. Develop a methodology and associated testing platform for PLM standards. 2. Create an open community and shared knowledge base around PLM standards. 3. Validate the methodology on real business cases through experimentation. The SIP project has yielded positive results including validation on a business case with Dassault Aviation, a simulation and testing environment, and an open community. Going forward, the project will focus on applying the methodology to other processes, standards, and defining recommended practices.
More Related Content
![[Capella Days 2020] MBSE and the High-Tech Equipment Industry, how do they ma...](https://cdn.slidesharecdn.com/ss_thumbnails/20201013-esi-capelladaysv3a1-external-201016140956-thumbnail.jpg?width=640&height=640&fit=bounds)
Sip@iPLM 2016
- 1. IRT-SystemX@iPLM2016 PLM Interoperability andSystem Engineering – A new challenge Building a secured collaboration for PLM and System Engineering with standards as network protocols Dr Nicolas Figay – SIP Project leader Airbus Group Innovation Nicolas.figay@irt-systemx.fr
- 2. SIP objectifs etresultats 2
- 3. SIP objectives andresults With SIP, let’s create and use the PLM open standards of the future for digital collaboration! Project SIP@SystemX 1- A methodology with an associated testing platform 2- Creation of a community of interest with a shared knowledge base 3- Validation on business cases relying on experimentation within an open environment 1- Apply on a real business case Very positive feedback from Dassault Aviation 2- A simulation and test environment factory for the next phase, many scientific publications 3- Open community creation 1- Application to other process, disciplines and standards 2- Usage for definition of recommended practices by implementor forum 3- Next of the PLM interoperability research roadmap: SIP2 Results Perspectives
- 4. SIP: Aggregation andsharing or research results Standards Interoperability PLM 4 4 Industrial Partners Academic Partners Research projects RISESTEP, SAVE, IDEAS, ATHENA, CRESCENDO, OPENDEVFACTORY, IMAGINE Academic Research network LIRIS, LAAS, NIST, UNINOVA cPlatform DMN methodology FIF DMN: Dynamic Manufacturing Network FIF: Federative Interoperability Framework • Collaboration N to N between organizations, application and software/hardware systems • Open standards + open source • Experimentation and knowledge sharing for end to end collaboration
- 5. Product Lifecycle Management A strategic business approach that applies a consistent set of business solutions that support the collaborative creation, management, dissemination, and use of product definition information • Supporting the extended enterprise (customers, design and supply partners, etc.) • Spanning from concept to end of life of a product or plant • Integrating people, processes, business systems, and information Définition de CIMDATA Supplier Lev. 2 Airlines Manuf . Supplier Civil Airlines Airlines Manuf . Supplier Mil. agency Manuf. Supplier Supplier Lev. 1 Engine Supplier Lev. 3 Equipments Supplier Lev. 3 Global Supplier Lev. 3 Mil. agency Manuf . Supplier Supplier Lev. 2 E M S Airlines Manuf. Supplier L2 Engine Supplier Lev. 3 Configured & Controlled Product Data for: - Design, - Simulation, - Manufacturing, - & Support Military Agencies Engine Suppliers Global Supplier Risk-Sharing Partner Engine Supplier Lev. 2 Equipments Supplier Lev. 2 Global Supplier Lev. 2 Equipment Supplier L.1 Supplier Lev. 1 L.-T. Archiving International Product Data Standards Service Suppliers OEM PRODUCT DATA E M S Engineering Manufacturing Support Supplier Lev. 2 Airlines Manuf . Supplier Civil Airlines Airlines Manuf . Supplier Mil. agency Manuf. Supplier Supplier Lev. 1 Engine Supplier Lev. 3 Equipments Supplier Lev. 3 Global Supplier Lev. 3 Mil. agency Manuf . Supplier Supplier Lev. 2 E M S Airlines Manuf. Supplier L2 Engine Supplier Lev. 3 Configured & Controlled Product Data for: - Design, - Simulation, - Manufacturing, - & Support Military Agencies Engine Suppliers Global Supplier Risk-Sharing Partner Engine Supplier Lev. 2 Equipments Supplier Lev. 2 Global Supplier Lev. 2 Equipment Supplier L.1 Supplier Lev. 1 L.-T. Archiving International Product Data Standards Service Suppliers OEM PRODUCT DATA E M S Engineering Manufacturing Support About Process for Product & Process date exchange, sharing and long term retention between disciplines and within supply chain, all along the duration of an industrial program P&P DATA CENTRIC Link with software solution vendors Open standards: ISO STEP – AP233, AP242, AP239, AP209, AP210, ILS ASD Suite, etc.
- 6. System Engineering SystemsEngineering is an engineering discipline whose responsibility is creating and executing an interdisciplinary process to ensure that the customer and stakeholder's needs are satisfied in a high quality, trustworthy, cost efficient and schedule compliant manner throughout a system's entire life cycle. This process is usually comprised of the following seven tasks: State the problem, Investigate alternatives, Model the system, Integrate, Launch the system, Assess performance, and Re-evaluate. These functions can be summarized with the acronym SIMILAR: State, Investigate, Model, Integrate, Launch, Assess and Re-evaluate. Définition de l’INCOSE About Interdisciplinary Process related to System of interest and supporting systems (ISO15288) PROCESS CENTRIC Open standards: ISO 15299, 15289, 24748, 15504SysML, UML2, UPDM, AP233, etc.
- 7. System Engineering andLife cycle Management Design Phase Industrial Program Production Phase Operation Phase Evolution Phase Design Product system and supporting systems Retrofit Changes Retrofit Changes Retrofit Changes Milestone SE processes are not sequential! The V cycle is reused during the different phase, with close collaboration between designers of the product and the supporting systems. Through lifecycle Interoperability (over the time) CrossProcess interop What about supply chain and sub-systems Equipment, standard parts? What about supporting ICT and information system dealing with Product and Process data management? What about the different CAx systems used by the different disciplines CrossProcess interop CrossProcess interop CrossProcess interop
- 8. SIP - DynamicManufacturing Network = system of systems PLM standards used for interoperability are network protocols
- 9. Dynamic Manufacturing Network= system of systems EnoviaThinkworks 3D Experience PLM standards used for interoperability are network protocols
- 10. Challenge of SIPproject Defining a consistent set of standards for covering PLM interoperability needs Assessing the standards, their implementation and their usage To define a community For developing the know how For involvement at national level on international standards In order supporting and developing the network of French international experts For sharing of resources Technological challenges Test oriented and Model Based Methodology with for PL M standards development driven by enterprise (motivation, drivers, value creation) Mastering implementation of standards Managing the complexity of emerging digital eBusiness ecosystem related to PLM. Governance of standards for preparing SoS operational interoperability Architecture of reference for building continuous an operational interoperability Security + Interoperability + Agility + Robustness at an acceptable price Secured and efficient collaboration Mastering the complexity
- 11. SIP methodology Duringthe standardization project Modeling the standard and its usage using Collaborative Modeling Environment based on UML2/SysML SIP capture and assessment of current practices and standards under development • AP242ed1, AP242ed2, - PLCS DEXLIB ,PLCSLIB and AP239ed3, MOSSEC Collaborative Modeling Environment for Standard and associated process modeling in closed connection to the DMN software factory for test bed component generation, assembly, deployment and monitoring During Implementation Forum and Benchmark Definition of Generic Business Scenario, test cases and test data for PDM Implementor forum and AP242 Benchmark (AFNET, PROSTEP) for AP242ed1 SIP capture and assessment of current practices for testing implementation of the standard by vendors Testbed environment and associated blueprint and workflow models for supporting inclusion of automated tasks where it will bring the more added value During deployment within Enterprise Capture of the current practices (Airbus Group, Automotive, Energy) and needs Enrichment of Generic Business Scenarios with collaboration context specific rules, test cases and test data Reuse and enrichment of a shared knowledge base Early involvement in implementation forum, for defining networked collaboration with different stakeholders and delivering specifications to the vendors that can be more easily validated and tested Demonstration on assessment of usage of AP242BO XML with DA Datapack Assessment and test of a PLM standards all along the life cycle an ISO standard 11
- 12. SIP Methodology Usage ofstandardized System Engineering Process Framework for contextualization of collaboration scenarios 12 ISO 15288 Processes Engineering Processes PLM Business Cases Related to Urbanization of the information system and governance of the supply chain as a Dynamic Manufacturing Network Open Standard = ArchiMateCOTS=Archi Contextualization based on standardized processes such as ISO 15288
- 13. SIP methodology Developing testbed platform from ArchiMate Business Collaboration Blueprint Template 13 Plan Design Generate Deploy Change Open Standard = ArchiMateCOTS=Archi DMN blueprint based methodology for governance of PLM standards within enterprise and networked enterprises
- 14. SIP methodology Designing testbed platform – UML Business Collaboration Composite Model 14 Open Standard = UML2 + MDACOTS=Papyrus Plan Design Generate Deploy Change Usage of an innovative approach for federation of language: modeling over SysML/UML2 Part of the Collaborative Modeling Environment for PLM standards proposed by SIP
- 15. SIP methodology Developing testbed platform - ArchiMate Business Collaboration Blueprint Template 15 Open Standard = UML2 + MDA Model 2 TextCOTS=Acceleo Plan Design Generate Deploy Change Set of chained transformation , Model to Model and Model to text
- 16. SIP methodology Developing testbed platform - ArchiMate Business Collaboration Blueprint Template 16 COTS=Archi, Papyrus, Acceleo, Maven, Vagrant, Ansible Plan Design Generate Deploy Change Software factory with as targeted platform (MDA PM) the cPlatform including ProxMox, Enterprise Portal, Enterprise Server, Enterprise Service Bus, Models repositories and Testing services
- 17. SIP methodology Developing testbed platform - ArchiMate Business Collaboration Blueprint Template 17 Open Standard = MDA,SPEMCOTS=Eclipse Process Framework Plan Design Generate Deploy Change Continuous change process based on SPEM, aiming at continuous interoperabilit y and evolutionary platform
- 18. SIP methodology DMN Softwarefactory usage Automation and generation on demand of the SIP testbed 18 Division by 4 of the time for set up and deployment of the test infrastructure Sharing and continuous evolution
- 19. Assessment and testof the usage of a PLM standard in operation Within an industrial program – for the extended enterprise 19
- 20. Conclusion Results Scientificpublications Short term exploitations Impacts Perspectives Not restricted to Aeronautic as multi-domain required for connected systems of tomorrow PLM or SE? No, more PLM + SE + Manufacturing+ Support/Operation + Recycling Digital transition • To prepare the path to the future • Integrate all the problems and issues still not addressed today • Continuous interoperability within a dynamic environment with a growing role of internet and digitalization • Impact of « makers » and 3D printing on PLM and SE – Digital twins support • Trade off between short term results that can be exploited fast and a longer time vision to be implemented for a community of interest Results & Perspectives 20
- 21. How to participate? Interested enterprise to contact SIP Nicolas Figay –SIP Project leader – nicolas.figay@irt-systemx.fr Jean Brangé – AFNET liaison – jean.brange@irt-systemx.fr Bernard Boime (bernard.boime@airbus.fr ) David Tchoffa (d.tchoffa@iut.univ-paris8.fr) Benoit Eynard (benoit.eynard@utc.fr ) Etienne DE POMMERY (etienne.depommery@irt-systemx.fr ) Face to face meetings for preparing contribution to the SIP2 roadmap SIP2 Consolidation Workshop SIP2 the in June the 30th, 2016 at IRT SystemX Planned start: January 2017 Next steps 21
- 22. Some references SIP@Future2016IRTSystemxdemonstration on youtube (v=7EfUFVK6Gi4) « Projet IRT SystemX : L'orientation académique de la plateforme SIP* », Dr. Nicolas Figay, Airbus Group Innovations, détaché IRT SystemX, IPLM2015 SIP in English: http://www.eads-iw.net/public/standard-interoperability-plm SIP en Français : http://www.irt-systemx.fr/project/sip/ IMAGINE: http://www.eads-iw.net/public/imagine AFNeT Standardization Day 2016 : Digital threads in industry based on PLM open standards « Presentation of Standard Interoperability PLM (SIP)”, By Dr Nicolas Figay Airbus Group Innovations, SIP Project Leader at IRT-SystemX 22
Editor's Notes
- #7 SE Standards Home/ About Systems Engineering/ SE Standards Standards Update The International Council on Systems Engineering Standards Initiatives group is one of the most active communities within INCOSE. Its members are working to advance and harmonize systems engineering standards used worldwide. INCOSE liaises with existing standards developing organizations, contributing to the development of standards and technical reports and participating in the planning for new work items related to systems engineering standards. Questions, ad-standards@incose.org Back to Top Current SE Standards ISO/IEC 15288: 2015 – System Life Cycle Processes Available for purchase from the International Organization for Standardization (ISO). See http://www.iso.org/iso/catalogue_detail?csnumber=63711 for a description. IEEE 15288.1-2014 – IEEE Standard for Application of Systems Engineering on Defense Programs Available for purchase from Institute of Electrical and Electronic Engineers (IEEE). See https://standards.ieee.org/findstds/standard/15288.1-2014.html for a description. IEEE 15288.2-2014 – IEEE Standard for Technical Reviews and Audits of Defense Programs Available for purchase from Institute of Electrical and Electronic Engineers (IEEE). See https://standards.ieee.org/findstds/standard/15288.2-2014.html for a description. ISO/IEC/IEEE 15289:2015 - Content of systems and software life cycle information products The 3rd edition of this standard was just published, but immediate revision is needed because an updated version of ISO/IEC/IEEE 15288, System and software engineering—system life cycle processes, was also published in May 2015. See https://standards.ieee.org/findstds/standard/15289-2015.html or http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66422for a description. ISO/IEC TR 24748-1:2010 – Guide for Life Cycle Management Available for free from the International Organization for Standardization (ISO). See http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50502 for a description. This document is available in electronic form at no charge at http://standards.iso.org/ittf/PubliclyAvailableStandards/c050502_ISO_IEC_TR_24748-1_2010.zip. ISO/IEC TR 24748-2:2011 – Guide for Application of 15288 Available for purchase from the International Organization for Standardization (ISO). See http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=54994 for a description. Note that this technical report is based on ISO/IEC 15288:2008. ISO/IEC TR 24748-3:2011 – Guide for Application of 12207 Available for purchase from the International Organization for Standardization (ISO). See http://www.iso.org/iso/catalogue_detail.htm?csnumber=54995 for a description. ISO/IEC 15504: 2004 - Information Technology - Process Assessment JTC1/SC7/WG10 Available for purchase from the International Organization for Standardization ISO/IEC 15504-1:2004 Information technology — Process assessment — Part 1: Concepts and vocabulary http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38932 ISO/IEC 15504-2:2003 Information technology — Process assessment — Part 2: Performing an assessment http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37458 ISO/IEC 15504-2:2003/Cor 1:2004 http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40192 ISO/IEC 15504-3:2004 Information technology — Process assessment — Part 3: Guidance on performing an assessment http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37454 ISO/IEC 15504-4:2004 Information technology — Process assessment — Part 4: Guidance on use for process improvement and process capability determination http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37462 ISO/IEC 15504-5:2012 Information technology — Process Assessment — Part 5: An exemplar Process Assessment Model http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=60555 ISO/IEC TR 15504-6:2013 Information technology — Process assessment — Part 6: An exemplar system life cycle process assessment model http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=61492 ISO/IEC TR 15504-7:2008 Information technology — Process assessment — Part 7: Assessment of organizational maturity http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50519 ISO/IEC PDTR 15504-8 Information technology — Process assessment — Part 8: An exemplar process assessment model for IT service management http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50625 ISO/IEC TS 15504-9:2011 Information technology — Process assessment — Part 9: Target process profiles http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=51684 ISO/IEC TS 15504-10:2011 Information technology — Process assessment — Part 10: Safety extension http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=54537 ISO/IEC 29110 (multi-part) See http://profs.etsmtl.ca/claporte/English/VSE/index.html ISO/PAS 19450:2015(en) - Automation systems and integration — Object-Process Methodology (OPM) ISO TC184/SC5/WG1 Available for purchase from the International Organization for Standardization (ISO) athttps://www.iso.org/obp/ui/#iso:std:iso:pas:19450:ed-1:v1:en ISO 10303-AP233, Industrial automation systems and integration -- Part 233: Systems engineering data representation TC184/SC4/WG3/T8 (http://www.iso.org/iso/en/CatalogueListPage.CatalogueList?ICS1=25&ICS2=40&ICS3=40&scopelist=PROGRAMME) Additional information available on the AP-233 website (http://www.ap233.org/) ANSI/GEIA EIA-632, Processes for Engineering a System, 01 Sept 2003 Available for purchase from Techstreet. See http://www.geia.org/ANSI-EIA-632-Standard--PROCESSES-FOR-ENGINEERING-A-SYSTEM for table of contents. Under revision by GEIA G-47 to align with ISO/IEC 15288; early stage of development (current status unknown). After publication will be fast tracked as an ISO standard. EIA/IS 731.1, Systems Engineering Capability Model, Electronic Industries Alliance (Interim Standard), 01 Aug 2002 Available for purchase from Techstreet. See http://www.geia.org/EIA-731.1-Standard---SYSTEMS-ENGINEERING-CAPABILITY-MODEL for description and table of contents. IEEE 1220-2005, IEEE Standard for Application and Management of the Systems Engineering Process, Institute of Electrical and Electronics Engineers, 09 Sept 2005 Available for purchase from Techstreet. See http://standards.ieee.org/reading/ieee/std_public/new_desc/se/1220-2005.html for a description and table of contents. Revision from 1998 version to align IEEE 1220 with ISO/IEC 15288 and to provide a lower level of detail than 15288. In process of being fast-tracked to become an ISO Technical Report. Back to Top Other Standard ANSI/AIAA G-043-1992, Guide for the Preparation of Operational Concept Documents Being upgraded now by INCOSE and AIAA partnership (http://www.aiaa.org/content.cfm?pageid=313) IEEE 1471, 2000: IEEE Recommended Practice for Architectural Description of Software-Intensive Systems Available for purchase from IEEE (http://standards.ieee.org/reading/ieee/std_public/description/se/1471-2000_desc.html) Capability Maturity Model Integration (CMMI) All you need to know is available from the Carnegie Mellon Software Engineering Institute's CMMI website at http://www.sei.cmu.edu/cmmi/ Merger of SW-CMM (from SEI) and SECM (EIA/IS 731) Released in July 2000 (Combined SE/SW model) Later release with IPPD elements (version 1.1), Jan 2002 Unified Modeling Language (UML) Available for download from the Object Management Group (OMG) athttp://www.omg.org/spec/UML/2.3/. An older version was approved as an ISO standard: ISO/IEC 19501:2005 Information technology - Open Distributed Processing - Unified Modeling Language (UML) Version 1.4.2 As of March 2011, there is a final draft international standard ISO/IEC 19505, comprising OMG Unified Modeling Language (OMG UML) Version 2.1.2 -- Part 1: Infrastructure and Part 2: Superstructure For additional information, refer to http://www.omg.org/spec/UML/index.htm. OMG Systems Modeling Language (OMG SysML™) The OMG released SysML Version 1.2 as a formal specification in June 2010. Latest information is available at the official OMG SysML site at http://www.omgsysml.org UML Profile for DoDAF/MODAF (UPDM) Unknown beta draft version was released in November 2010. Latest information is available at the UPDM site at http://www.updm.com/index.htm