PDM WAND Presentation by Mauro MARCHI February 01, 2006

1. PDM WAND Presentation • by • Mauro MARCHI • February 01, 2006

2. SUMMARY • PDM WAND Description • WAND Functionalities • Processes • CADM Process • Documentation Management • Document Lifecycle and Approval Workflows • NCR Management • Partner Collaborative Environment Description • Implementation Planning

3. PDM WAND Description • WAND is the Product Data Management (PDM) developed by AASI for the management of all projects running within the Company. The heart WAND System architecture is PTC’s Windchillproduct data management software. • WAND, through the functionalities of Windchill, supplies an integrated suite of applications which are dedicated to the management of the entire product and process lifecycle as well as applications necessary to create, review and distribute technical and project information. • WAND has available the change control functionality in support to configuration management processes giving, in real time, the current approved status of a configuration baseline and making it visible to all project actors. • The model implemented is fully compatible with the configuration management international standards (ISO 10007 and ECSS-M-40)

4. WAND Ver. 4.0 • DB’s Company Management • CAD Interoperability • ERP Interoperability • Case Interoperability • WAND Ver.3.0 • Parts Management • Engineering BOM • NCR Management • Req’s Sys Mgt interoperability • WAND ver.1.0 • Data Vault • User Access • Product Structure • Doc. & Conf. Management • Visualization • WAND ver. 2.0 • Document Process Control • Change Management • Collaborative Engineering • Actions Item Management

5. PDM WAND Description WAND is integrated or interoperable with other key running systems, which are including: • Telelogic’sDoors/T-Rekthat provides document requirements, maintaining traceability and tracking tests and verification documents; • Dassault’s Catiathat support design space infrastructures and satellites and are handling assembly and product configurations; • WAND interoperate with EDS VisMockup and ClassicJack that allow engineers to perform virtual prototyping operations simulation on the model, including HFA and operations with digital mannequin; • APS a Visual Manufacturing’s application for production planning and scheduling; • Company’s DBs that provide Material or preferred Parts List; • Microsoft’s Office that provides office applications.

6. DOORS Environment SS-RE-77 GA-SS-ALS-0124 GA-URD-ALS-0053 SS-RE-78 GA-MAN-ALS-985 PRT0138449P SS-RE-79 GA1500E Surrogate & Adapter SR module WAND Environment • DOORS / WAND Interoperability WAND / DOORS adapterallows the interoperability of the two systems

7. Check-out Check-in PN 002 Approved PN 002 Approved 3D Model 3D Model WAND environment Enterprise level PN TOP In work PN TOP In work PN 002 In Work 3D Model Windchill Workgroup Manager Catia environment Department level

8. Product Structure in WAND Check-in from Catia V5

9. Mechanical Parts and Electrical Components

10. WAND implements: • A Product Structure model, Data Vaulting, Document Management and Office environment integration mechanisms, and Configuration Management and Process Control functions. • The Parts, management of the Engineering BOM, integration of the MCADs and visualization by means of Windchill ProductView. • the interfaces with the planning system for production, management of the Manufacturing BOM, the interfaces with the electrical ECAD and the legacy systems by means of Windchill Info*Engine’s mechanisms.

11. Standards ESA/ ECSS ISO 10007 Product Structure Model FM FM CI Tree FM EQM EQM …. FM “As designed” “As built” • WAND Product Structure Model

12. WAND Product Structure Model • The Product Tree Structure describes the relationship and the position of Product Item (PIs), Configuration Item (CIs) and associated Parts in the overall product breakdown. • CIs are the basic units of Configuration Management. They are selected by applying a decomposition process to the product using guidance criteria. • WAND will enable users to create, manipulate and visualize product structures (i.e. “as designed”, “as-built”), according to the user’s role and rules assigned in the company. • With this approach, the Product Tree is the mean from which all the information related to a Project are organized.

13. FM EQM FM EQM AAS CADM JOINT MEETING • Product Tree and documentation

14. Each Parts is defined into WAND by: ECAD Specification Static Attributs MCAD Dynamic Attributs PAD

15. WAND functionalities: WAND functionalities are fully supporting Configuration And Data Management (CADM) processes: • Configuration Identification; • identify the systems architecture; • select Configuration Items concerned and define their descriptive documentation • establish means for identifying products (H/W and S/W) and documentation; • establish configuration baselines for the purpose of requirements- and design- management • Configuration Control; • control of the configuration; • establish and implement change control, and control of interfaces

16. WAND functionalities: • Configuration Status Accounting • recording and follow–up of the configuration; • to record the product’s different configurations, and to permit its use by means of configuration statuses; • to define and maintain the software libraries (or repositories) where software is stored in a controlled environment; to enable access to software libraries according to established privileges. • Configuration Verification • to verify and demonstrate that the product meets its documented functional, performance and physical attributes; • Configuration Audit • to verify that the Configuration Management system is effective and meets the Project Configuration Management requirements.

17. Configuration And Data Management (CADM) outputs The functionalities of WANDautomatically allows the extraction of the following outputs: • Product Tree • Configuration Item List • Baseline report • Configuration Item data List • As Built Configuration List • Change, Deviation and Waiver Status Indexes • Documentation Listing

18. … … • Approved status of requ’s and design of a product at project key milestone • Dynamic page

19. … … • The CIDL is a …… “document generated for reporting the current design status of each product configuration item. This page (doc) is provided at the PDR with the establishment of the development configuration baseline and maintained during the lifecycle of the product CI “ • Dynamic page

20. Documentation Management (Lyfecycle and Approval Workflow) • WAND Project documentation are managed according to their established life-cycle and approval workflow. They have been classified into two different typologies: • Internal • External this because the attributes, Life-cycle and Work-flows applicable to them, will be different. • Documents, related to a Project, are associated to a SOW and relevant DRL. • The external documents are furtherly splitted as “Customer documents” and “Subcontractor documents” being relevant attributes different (i.e. no DRL item ref. for Customer doc.)

21. Program approvers • Configuration Manager • Product Assurance Manager • System Engineer Manager • Contract Manager • Project Control Manager • Subcontractor Manager • AIV Manager • Document Lyfecycle and Approval Workflow

22. The Program Manager receive an email including program’s team comments UTENTE A He can “promote” it or send it to the document Creator

23. Document Lyfecycle and Approval Workflow (Cont.’d) • During the workflow, through specific tasks assigned, it can be possible to identify for each document: • If the document has to be part of a CIDL • Which are the PI’s and CI’s applicable to it • Based on the above selections, the document will be properly inserted by WAND into the relevant structure, baselines and CIDL’s at the end of the workflow.

24. Web page representation WAND Document Data Model Windchill UML model

25. Object visualization: documents

26. Object visualization: 2D drawings Related documents: list of PL and Sheets 2D Drawing

27. Object visualization: models

28. WANDoffers Document Management capabilities, that include: • a data vault to protect information from unauthorized modification by controlling access; • check-in and check-out functions for submitting documents to and obtaining them from the vault; • version control and history functions to keep track of changes and full text retrieval; • Management of configuration baseline at each point in time; • Change process to configuration baseline.

29. Change Management • WAND is managing any change generated on the Project. On this basis, “change”, is therefore anything that modifies the technical configuration of the Product at any step of the lifecycle and generating rework or affecting schedule, cost and quality. • The above definition is considered applicable to: • Documents having the workflow completed (formally released) and part of a configured baseline or: • Documents not formally released yet but used as “preliminary” information for development of engineering, design or manufacturing activities • The WAND functionality, covering this part of the process, is the “Change Management”.

30. Workflow: “Change Management” Need / Problem for a change Change Manager CCB CCB Configuration Control Board Change assignement to discipline Analysis & Preliminary evaluation Change Review Change Request Change Investigation Change Issue Change Propose Change Cancelled Change Completed Change Order Change Activity WP assignement responsibility Change Final Review Change Implementattion AAS CADM JOINT MEETING • Change Management

31. NCR Management When the NCR is generated it is uploaded within WAND and the relevant processing flow activated: • The PA/QA Manager receive an email from WAND relevant to the NCR generation and approve the request • NRB members will receive the NCR and each of them can visualize it with the relevant annexes • The customer\contractor is kept inside the flow of NCR process by email and task • Each NRB user participates to the forum that represents the remote NRB exchanging informations and comments. Formal release of corrective action is authorised by NRB authority signatures • The actionee receive by e mail the notification of the task to be performed • A due date drives notification inside WAND system. A week before the due date the system send an email every day. After the due day the system send two notification a day • NCR closure After the verification of the proper implementation of the corrective action the QA/PA manager closes the NCR

32. INTERNET Common area Product Tree Customers EXTERNAL WAND Partners Sub/Co Application + DB LAN Firewall Data mirroring FEDERATION WAND (Windchill) Load Balancer Product Tree Oracle Metadata Alcatel Alenia Space Project Teams Application Servers Graphics Server Database Server • E - WAND architecture

33. E - WAND architecture • The PDM has the capability to implement a real concurrent environment , through the provision of an external system area, called E-WAND, where data can be exchanged between the Program partners/participants. • On this basis, E-WAND provides capabilities for consulting, uploading and downloading of project data by each partner/participant.

34. WAND WAND EWAND EWAND Product Structure and Documents are shared on the external server External Users can create new documents and link these documents to the Product Structure Step 1: Information Sharing Step 2: External Documents Creation

35. WAND EWAND • Sharing of DATA and PROCESSES New PI/CI and their links to the Product Structure are created by External Users and then loaded into the internal WAND Step 3: External PI/CI Management

36. Implementation Planning • Access to WAND Sytem can be provided very quickly after a verification of the client hardware and software set-up and licences availability. • Partners/Subcontractors Operating personnell will be trained by AAS WAND Business and System Administartors (1 day max) • AAS Help-Desk available to support all the relevant activities