Global Concurrent Engineering Infrastructure for Space Projects Lifecycle (GCE) Kjell Bengtsson, Jochen Haenisch, Ehsan Sadeghi, Sverre Samdal SECESA 2014 - SECESA 2014-08-10 October Vaihingen Campus, University of Stuttgart Germany Kjell Bengtsson Kjell.Bengtsson@Jotne.com
Agenda 1. The Global Concurrent Engineering Infrastructure for Space Projects Lifecycle (GCE) project 2. Collaborations and ISO standards 3. Examples, using the initial GCE platform - ExoMars, Planetary Protection Database (PPDB) - Subsea applications for Oil and Gas projects
Business cases Life-cycle support / Interoperability Phase 0 Mission analysis/needs identification Phase A Feasibility Phase B Preliminary Definition Phase C Detailed Definition Phase D Qualification and Production Phase E Utilization Phase F Disposal 0 A data data data Space Project Data data data data data F D E Data Exchange Specifications ISO 10303 ISO 12006 (RDL) B C Subcontractors and partners
Before GCE : TruePLM - (Background) Product structure tree Project lifetime scope Configuration control tool Presentation of product data in tree structures Versioning of data Search for product data User access control Traceability of the history of data Integration with specific project tools Project plan information TruePLM started as market oriented activity
Before GCE : TruePLM - (Background)
GCE aims at achieving the following objectives To provide a global concurrent engineering platform (GCE Platform) that is a multi-view multi-user project repository for space missions with rich data exchange capabilities for import and export of spacecraft system information; To provide a tool for project system engineering allowing consistency of global data and documentation; To allow adaptation of this GCE Platform also for other Space Agencies (ESA partners) to facilitate interoperability and data sharing; To enable archival and management of space craft system data using international standards to enable long-term data storage and access independent of hardware and software platforms; To design a platform that provides maximum capabilities to projects executing concurrent engineering strategies; To deliver a solution for operational use by ESA missions.
GCE from a user perspective Different user roles with different views on data, especially for partners external to ESA; Domain specific contents validation; Link product data to requirements; Link product data to actions and notifications; Budget related correlations, like mass budget; Traceability and search, especially meta data search, but also Google type search; Integrate with DOORS (Req-IF), Catia, Lotus Notes, Eclipse, DMS, budget tools, MS Projects, ECOS, MAIS; Continuous data exchange and review; Better interoperability of document contents; Support for digital signatures; Tracking of e-mails; Automated notifications.
GCE New capabilities Out of 230 new GCE features, users will benefit in many areas. Only a few example listed here: Import of requirements for each system RIDs handling Reading and writing metadata to and from office documents Enable the storage and reuse of most commonly needed search criteria Browse through deadlines, deliverables and budget Browse through different representations of the same document Browse through ICDs and versions of them To enable knowledge management, allow the user to browse through information from several projects simultaneously. Enable configuration control (baselining) of product data/documents Include ESOC and ESTEC document databases Search by level (product structure, hierarchical) and within there by "nature of information", i.e., requirement, design, testing, verification, general requirement, request for deviation Provide role of document controller Ensure that each released document gets a corresponding pdf-file Check who has downloaded a specific file
Collaborations and ISO standards Tech pubs CSDB Training ILS Data dictionary Material management LSA/LSAR PLCS (ILS) repository RCM/MSG-3 PDM Operational and maintenance data feedback Source: EADS - Saab
Collaborations and ISO standards Requirements Products Serialized items Breakdown Product Data Versions Document Effectivity Change Management Work request Work order Personnel Position Resources (Required) Task Approval Support Engineering Organization Qualification Condition Location Activity Planning State Provide Support Resource management Extensions Operational feedback Resource_as_ realized Activity_ feedback Project Risk Configuration Task_ method/step Facilities Multi linguism Observations
Collaborations and ISO standards DEXs are: (like DEX 1 and DEX 3) Subsets of the AP239 Information model Selected to meet a specific data exchange need Built from relevant modules Supported by usage guidance, capabilities, templates and reference data Can be refined from other DEXs DEXs may be standardized at any level (work group, company, project, organization, national, international) DEXs enable Consistent implementation of AP239 Data consolidation through time 11
Properties in ISO 10303 and ISO 12006 Web Services TEMPLATE A P P L I C A T I O N S Representation of the Information model for assigning_product_property Representation of the Information model for product_property_numeric
Properties in ISO 10303 and ISO 12006 Next page ISO 10303 OWL ISO 12006
Examples using the initial GCE platform - ExoMars, Planetary Protection Database (PPDB) - Subsea applications for Oil and Gas projects
ExoMars, Planetary Protection Database UN Space Treaty (of 1967) states: States Parties to the Treaty shall pursue studies of outer space, including the Moon and other celestial bodies, and conduct exploration of them so as to avoid their harmful contamination and also adverse changes in the environment of the Earth resulting from the introduction of extraterrestrial matter, and where necessary, shall adopt appropriate measures for this purpose. (UN 1967)
ExoMars, Planetary Protection Database The PPDB tool's tasks are: Integration of bioburden data and similar with product structure tree. Integration of several types of data in a single database; bioburden data for components and items, including information on laboratories, certificates, measurements, sensor readings and more. History tracking and versioning across products and projects. Archival and management using international standards to enable long-term data storage and access independent of hardware and software platforms. Provide statistics on item contamination.
Use Case I : Assay Labels Database Query Printer Printing software Lables
Use Case II - Scanner
PPDB properties (examples) For hardware items, calculation is triggered by the Calculate properties context menu item of the hardware item. Table 1: Calculated properties for Hardware item nodes 03 Average surface spore density 04 Total surface spores measured 07 Total spores 08 Total spores allocation Level = ii If HwItem_level (ii) has child node For i =1: total number of Hw_item. Level ii+1 (Σ (HW Item_level(ii+1).03 Average surface spore density * HW Item_level(ii+1).02 Area item))/ Σ HW Item_level(ii+1).02 Area item End For End If Level = ii If HwItem_level (ii) has child node HW Item_level(ii).03 Average surface spore density* HW Item_level(ii).02 Area item; End if Level = ii If HwItem_level (ii) has child node HW Item_level(ii).04 Total surface spores measured + HW Item_level(ii).06 Encapsulated spores; End If Level = ii If HwItem_level (ii) has child node HW Item_level(ii).05 Surface spores allocated + HW Item_level(ii).06 Encapsulated spores End if
Statistics and reports
ESA - IDEAS Use case ESA Prototype ASIC Development for NIR Large Format Sensor Array The project aims at future astronomical science and Earth observation missions, where the ASIC will be used with image sensors based on mercury cadmium telluride (HgCdTe, or MCT). NIRCA is designed to operate from cryogenic temperatures (77 K) to higher than room temperature (328 K) and in a high radiation environment (LET > 60 MeVcm 2 /mg). Management of Design Validation Cryogenic Testing IDEAS develops and manufactures radiation detection systems for a wide range of applications. High channel count integrated systems for image sensors and radiation spectroscopy is at the core of IDEAS business.
Oil and Gas projects Some selected oil and gas projects where GCE results have successfully been utilized; Eldfisk Pig Launcher DRESSER-RAND, Bigfoot, Gas Turbine power module, customer Chevron Njord A Subsea Manifold System, customer Statoil DRESSER-RAND TURK 3, Gas Compression Modules, Customer Türkmengaz SVALIN PLETs and PLRs, Customer Subsea 7 EKOK Aibel Office Module for end Client Conoco Philips BOD ROV Hangar, customer Oceaneering Vigdis Feed Study, customer Statoil Windpower, Anode Tripods, Statoil Future yard planning study
STATOIL Njord A Subsea project Key Figures Video installation Duration: 12 months Engineering hours: 10,000 No. of main suppliers: 6 Number of Documents: 1000 Weight: (*3) : 93,000 kg 3D models: 35 Engineering reports: 10 Project members: Internal 10 External 100
Not an integrated environment Engineering Tools Office Tools Customer Tools Ingest tools FTP Sites eroom ProCoSys ERP
General on the project Product Lifecycle Management Scope To develop a new generation solution for life-cycle data sharing and longterm archiving targeted for adoption by the Sub-sea Industry Main requirements Basic project / system management System lifecycle support Project data sharing / supply chain management Team collaboration Version and configuration control Document and data management Concurrent engineering/ document dependencies Long-term archiving / re-use ECSS Standards Enabling technology International standards for product data
Use cases Summary Product breakdown structure oriented engineering Document and data management E-mails as documents Search History tracking Configuration control Dependencies / sticky notes Concurrent engineering Project cooperation Supply chain management Notifications Review capability Lifecycle support Record data along the life cycle Interoperability Communicate with external formats Import/export using STEP/PLCS DEX Archival Retention over long periods of time Retrieval application independent Customer Engineering Fabrication Suppliers
Project set-up Set-up options: Define from scratch (especially Physical/Product Breakdown Structure- PBS) Import from files (PLCS + RDL), using OWL for Reference data From templates in the application Configurable concepts: Use reference data to define the names for: Scheduled events types (ISO/ECSS / NORSOK) Disciplines (ISO/ECSS / NORSOK) Document content types (from requirements) File formats (dynamically extended) Document status (ISO/ECSS / NORSOK) Properties (dynamically extended) Sources of data (from requirements) User roles and access control User administration May be extended during use of the application to meet customer individual requirements
Project data management NORSOK : ADCB A= Offshore AD= Subsea ADC = Riserbase ADCB = Manifold / Piping Area
Space brings savings to offshore oil and gas http://www.esa.int/our_activities/technology/ttp2/space_brings_savings_to_offshore_oil_and_gas
Conclusions of using TruePLM for Oil&Gas A tool to improve efficiency in engineering, operation and support Implementation of Oil and Gas structuring and standards according to NORSOK in the PBS, SBA and document structure All project data across phases and disciplines collected in one database, from feasibility study to decommissioning. Several organisations can work on the same PBS by managing read/write/delete access Oil and Gas projects have long durations, 20-40 years is common; ISO standard formats important to be able to read the data over time Focus on transparency: History tracking of changes with date and user, every version viewable and downloadable. A must for final documentation and Life Cycle Information (LCI) Management.
Future outlook Use of standards supporting the requirements of interoperability will pave the way by deploying international and open specifications for solutions embodying data and tool independence. Engineers will always need tools and applications to increase the granularity of their problems, and this will require new solutions. In the years to come when data is growing rapidly, one will probably look into the results from on-going research within the Cloud and Big Data domains to make use of large HPC clusters and related data stores. This will be highly relevant for the space industry. http://eu-cloudflow.eu/ Partner and to excute experiments (funded) http://www.eu-cloudflow.eu/open-calls/first-call http://www.velassco.eu/ The GCE project is looking for innovative teams to make a fast track in using the results. Are you interested?