1 DOCUMENT TYPE: PLAN TITLE: INSTRUMENT MANAGEMENT PLAN DOCUMENT No.: TL PAGE: I of V,26 PROJECT Ref.: ISSUE No.: Draft DATE: January, 97 PREPARED BY: G. FUGGETTA CHECKED BY: SYSTEM MANAGER: DATE: PAPM: DATE: PROGRAM MANAGER: G. FUGGETTA DATE: CONFIGURATION: L. E. RONDELLI DATE:
2 Ref: TL Project Ref.: Issue: Draft Page: II Date: January, 97 DISTRIBUTION LIST POS. NAME DEPT. N G. FUGGETTA LABEN 1 P. UBERTINI IAS 1 M. QUADRINI IAS 1 D. LATERZA LABEN 1 Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
3 Ref: TL Project Ref.: Issue: Draft Page: III Date: January, 97 CHANGE RECORD Issue Date Sheet Description of Change Release 1 JAN. 97 ALL FIRST ISSUE OF THE DOCUMENT --- Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
4 Ref: TL Project Ref.: Issue: Draft Page: IV Date: January, 97 TABLE OF CONTENTS 1. ABSTRACT KEYWORDS INTRODUCTION Scope APPLICABLE AND REFERENCE DOCUMENTS Applicable documents IBIS ORGANIZATION Organization description The System Team Institute organization AI&V Industry Relationship with "integral" ACTIVITIES IDENTIFICATION Model philosophy Work Breakdown Structure Baseline documents Configuration management REPORTING AND MONITORING Program review Progress meeting Activities reporting PROGRAM MASTER PLAN Program milestone Master bar chart Schedule discussion ANNEX 1 INSTRUMENT PRODUCT BREAKDOWN STRUCTURE ANNEX 2 INSTRUMENT ACTIVITIES BREAKDOWN STRUCTURE. 15 ANNEX 3 PROGRAM MASTER BAR CHART Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
5 Ref: TL Project Ref.: Issue: Draft Page: 1 Date: January, ABSTRACT Scope of this document is to define the guidelines and the requirements for the IBIS instrument development. The content of in this document is approved by the Principal Investigator, accepted by the involved Institutes and agreed with ESA. 2. KEYWORDS IBIS SYSTEM TEAM P.M.O. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
6 Ref: TL Project Ref.: Issue: Draft Page: 2 Date: January, INTRODUCTION 3.1. Scope The following five main topics are considered mandatory to ensure a successful IBIS development: Effective organization Clear activities identification Successfully oriented Instrument AI&V Periodic reporting and monitoring Operative program master plan In the following chapter details and requirements are stated for each of them. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
7 Ref: TL Project Ref.: Issue: Draft Page: 3 Date: January, APPLICABLE AND REFERENCE DOCUMENTS 4.1. Applicable documents The following documents are considered applicable: IBIS EID part A, issued by ESA IBIS EID part B, issued by IAS IBIS EID part C, issued by IAS 5. IBIS ORGANIZATION 5.1. Organization description The IBIS consortium is leaded by Principal Investigator, P. UBERTINII supported by the CO-I group and, for concern the operative management and development activities, by the System Team. The Instrument flight and ground systems will be developed by the Institutes listed in the EIDC part C. The instrument models assembly, integration and verification (AI&V) will be done by LABEN S.p.A. Vimodrone, Milan Italy The System Team The System Team rule is to coordinate, in accordance with the P.I. directives, all the management, technical and quality aspects related to the program development and relevant milestone achievement. The System Team located a IAS Frascati is leaded by the Instrument Manager and includes the following key person: System engineer Software manager Hardware specialist Software Specialist Calibration Scientist Configuration Manager Mechanical and thermal specialist P.A. Manager with the scope to provide for all the development disciplines the coordination and supervision point for all the instrument systems. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
8 Ref: TL Project Ref.: Issue: Draft Page: 4 Date: January, Institute organization The involved Institute are responsible for the relevant system or unit development, acceptance and qualification in accordance with the applicable requirements. Following the system or unit delivery to the instrument AI&V, the Institute will guarantee an adequate support during the whole integration and testing phase. At each Institute, shall act the Local Project Management Office - P.M.O. lead by the local Project manager. The local PMO composed by the following key person will ensure the system or unit development coordination within the allocated budgets and requirements and an effective interface with the PI and the System Team. System Engineering Configuration control Project planning and control Quality assurance 5.4. AI&V Industry The instrument AI&V will be done at LABEN S.p.A. Vimodrone Milan, Italy. The local PMO will be composed by the following key person. Program Manager System manager AI&V manager Quality assurance manager Project control. Resources, tools facilities and logistic support will be available as necessary in order to allow the activities execution within the allocated time frame. In order to achieve the program milestone and to maintain clear relationship and responsibilities between all the involved parties: System Team, institutes and LABEN, the following guidelines shall be followed: The System Team will generate the Instrument Test Requirements; The System Team shall accept and authorize the local institute to deliver the involved instrument system or unit to LABEN upon successfully completion of the relevant acceptance and or qualification tests. LABEN will generate the Instrument AI&V plan and related test procedure to be approved by the System Team. In order to fulfill this task full visibility and support by the local Institute shall be assured. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
9 Ref: TL Project Ref.: Issue: Draft Page: 5 Date: January, 97 During the AI&V activities any eventual malfunctions will be reported via a dedicated Non Conformance Report to the System Team. Investigations or corrective actions will be implemented only after the System Team approval Relationship with "integral" The relationship between IBIS and INTEGRAL, that means ESA and if any Alenia Spazio, are managed by the P.I. and the System Team. Periodic interface meeting are held in order to verify the delivery milestone achievement in accordance with the agreed requirements and budgets. The interface between INTEGRAL and IBIS are defined in the following documents approved by the parties: EIDC part A prepared by ESA EIDC part B prepared by the System Team EIDC part C prepared by the System Team. In addition to the above, the System Team has issued the Instrument Product assurance plan, this document is approved by ESA and the P.I., defines the quality assurance rules to be used in the instrument development. ESA is providing the following services and item to IBIS: Instrument DPE and common application software. Support to Application Software and HEPI integration into DPE by means of knowledge, resources and tools to the relevant IBIS institute. Spacecraft Interface Simulator to be integrated in the IBIS EGSE. Free access to the ESTEC environmental tests facilities for the Instrument verification activities. Free of charge high reliability E.E.E. parts procurement trough a centralized agency for all the involved institutes. For this scope the System Team, with the input to be issued by the institute, will generate the Instrument Declared Component List, defining quantity and applicable specification for all the envisaged parts. The System Team, via a dedicated procedure, will supervise the procurement activities trough the CPPA in order to guarantee the applicable requirements fulfillment. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
10 Ref: TL Project Ref.: Issue: Draft Page: 6 Date: January, ACTIVITIES IDENTIFICATION 6.1. Model philosophy The IBIS model philosophy, as defined in the following table, has been adopted in order to ensure the following goal achievement: Early mechanical qualification at instrument and satellite level via the Instrument STM. Spacecraft full functional verification via the EM boxes and detectors simulator. End to end test execution on flight fully representative hardware via the Instrument QM. Detectors modules full qualification before flight modules integration via the QM. Pre-calibration activities on Qualification Modlel. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
11 Ref: TL Project Ref.: Issue: Draft Page: 7 Date: January, 97 IBIS MODEL PHILOSOPHY ITEM/TYPE STRUCTURAL. MODEL ENGINEERING MODEL QUALIFICATION MODEL MECHANICAL ITEM MAIN FRAME HOPPER SUPPORT FRAMES FLIGHT MODEL FULLY REPRESENTATIVE N.A FLIGHT MODEL FULLY REPRESENTATIVE, DETECTORS MODULE ISGRI PICSIT VETO ONE MODULE FOR EACH SYSTEM. FLIGHT MODEL FULLY REPRESENTATIVE IN TERM OF: MECHANICAL DESIGN, MASS, THERMAL & CENTER OF GRAVITY, ALL THE OTHERS ARE DUMMY STAND ALONE SIMULATOR ONE MODULE FOR EACH SYSTEM FULLY QUALIFIED BEFORE THE DELIVERY TO INSTRUMENT AI&V. DUMMY FOR ALL THE OTHER MODULES. WITH SSC "B" OR "C" COMPONENTS ISGRI, PICSIT, VETO BOXES & HEPI IBIS AI&V ACTIVITIES INTEGRAL AI&V ACTIVITIES BOTH REDUNDANCIES, FLIGHT MODEL FULLY REPRESENTATIVE IN TERM OF: MECHANICAL DESIGN, MASS, THERMAL & CENTER OF GRAVITY. AI&V AND VIBRATION TESTS INTEGRATION ON STM SPACECRAFT FOR MECHANICAL & THERMAL TESTS ONE REDUNDANCY ONLY, FLIGHT MODEL FULLY REPRESENTATIVE WITH MIL 883B COMPONENTS. FUNCTIONALLY TESTED BEFORE DELIVERY TO INSTRUMENT AI&V INTEGRATION AND FUNCTIONAL CHECK BEFORE DELIVERY TO ESTEC INTEGRATION ON EM SPACECRAFT INSTRUMENT FUNCTIONAL TEST ONE REDUNDANCY ONLY, FLIGHT MODEL FULLY REPRESENTATIVE WITH SSC "B" OR "C" COMPONENTS. QUALIFIED BEFORE DELIVERY TO INSTRUMENT AI&V AI&V, SCIENCE TESTS AND ENVIRONMENTAL TESTS (TBC) INTEGRATION ON EM SPACECRAFT FOR END TO END TESTS (IF ANY) SPARE PHILOSOPHY: MODULES FOR PICSIT, ISGRI, MASK & VETO; QM UNITS REFURBISHED AFTER QUALIFICATION. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved. FLIGHT MODEL FLIGHT MODEL, ACCEPTANCE TESTS DONE BEFORE DELIVERY TO INSTRUMENT AI&V TESTED AT ACCEPTANCE LEVEL BEFORE DELIVERY TO INSTRUMENT AI&V TESTED AT ACCEPTANCE LEVEL AND DURATION BEFORE DELIVERY TO INSTRUMENT AI&V AI&V, ACCEPTANCE TESTS ENVIRONMENTAL TESTS (TBC), CALIBRATION INTEGRATION ON FLIGHT SPACECRAFT AND FLIGHT CAMPAIGN
12 Ref: TL Project Ref.: Issue: Draft Page: 8 Date: January, 97 IBIS INSTRUMENT DELIVERABLE ITEM LIST ITEM BY STM EM QM FM FS MAIN FRAME IAS/LABEN 1 N.A. 1 1 N.A HOPPER ITESRE/LABEN 1 N.A. 1 1 REF. QM PICSIT SUPPORT FRAME (SPIDER) ITESRE/LABEN 1 N.A. 1 1 N.A. DETECTOR MODULES ITESRE/LABEN DUMMY N.A DUMMY 8 1 PEB ITESRE/LABEN REF. QM ISGRI SUPPORT FRAME (SPIDER) IAS/LABEN 1 N.A. 1 1 N.A. DETECTOR MODULES CEA/SAP DUMMY N.A DUMMY 8 1 IEB CEA/SAP REF. QM VETO BGO & HOUSING IAS/LABEN DUMMY N.A DUMMY 16 1 VDE (PMT&FEE) UNIV. BERGEN 2 N.A DUMMY 32 2 VEB SRC/PAS REF. QM CALIBRATION SOURCES UNIV. VALENCIA 1 N.A. 1 1 REF. QM HEPI HEPI H/W A.I.T REF. QM APPLICATION SOFTWARE A.I.T. N.A. ISSUE 1 ISSUE 2 ISSUE 2 PROM SET MASK CASA 1 N.A. 1 1 REF. QM INSTRUMENT TUBE ESTEC/ALENIA 1 N.A. N.A. 1 STM DETECTOR SIMULATOR IAS/LABEN N.A. 1 N.A. N.A. N.A. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
13 Ref: TL Project Ref.: Issue: Draft Page: 9 Date: January, Work Breakdown Structure The Work Breakdown Structure is the matrix having for vector the Product Breakdown Structure, PBS, and the Activities Breakdown Structure ABS at a defined level of details. Within the IBIS product tree the following levels of details have been identified: PBS I.D. TITLE LEVEL LEVEL 0 INSTRUMENT IBIS LEVEL 1 SYSTEM PICSIT, ISGRI, VETO MASK etc. LEVEL 2 MODULE/UNIT PEB, IEB, VEB etc. while for the ABS the levels are the following: ABS I.D. TITLE LEVEL LEVEL 0 PROGRAM IBIS LEVEL 1 FAMILY DESIGN, PROCUREMENT, MAI&T LEVEL 2 ACTIVITIES D.D., INTEGRATION, ACCEPTANCE etc. The work elements identified via the above mentioned process have been utilized to generate the attached IBIS master plan. System or Unit detailed WBS will be generated by the local PMO for their internal planning and control purposes Baseline documents In order to ensure clear interface and responsibility within the IBIS consorzium the following key documents, for all the envisaged Instrument systems, will be issued by the System Team and following the formal acceptance by the relevant institutes kept under control over the program duration. Statement of work System specification System AI&V requirement System Configuration item data list Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
14 Ref: TL Project Ref.: Issue: Draft Page: 10 Date: January, Configuration management Special attention will be paid by all the involved institute and LABEN in the deliverable items configuration control. Each item will have his own configuration control document reporting the applicable documents together with the relevant non conformance and request for waiver. The item configuration control documents will be continuously updated and formally issued for the envisaged program review: MRR, TRR, TRB etc. 7. REPORTING AND MONITORING 7.1. Program review The following internal design review will be held ITEM MODEL MRR MODEL TRR MODEL TRB CDR QDR MECHANICAL ITEM N.A. ISGRI, PICSIT, VETO MODULE IEB, PEB, VEB, HEPI INSTRUMENT N.A. N.A. MRR is the review where the manufacturing dossier of each deliverable item is presented by the Institute to the P.I. and the System Team. Scope of the review is to achieve the P.I. authorization for the manufacturing activities start. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
15 Ref: TL Project Ref.: Issue: Draft Page: 11 Date: January, 97 TRR is the review where each deliverable item acceptance and or qualification tests procedure are presented by the local Institute to the P.I. and the System Team for acceptance. Scope of the review is to achieve the P.I. authorization to start the acceptance or qualification tests. TRB is the review where the acceptance or qualification tests results, for each deliverable items, are presented to the P.I. and the System Team. Scope of the review is to achieve the P.I. preliminary acceptance and the consent to shipment to LABEN for AI&V Progress meeting Bi-monthly progress meeting will be held between the P.I.,the System Team and the institutes to assess the activities status and define the relevant recovery actions if any. Interface meeting with ESTEC will be held each six (6) weeks in order to review and to manage the common area of interest. "Ad hoc" meetings on specific topics will be held when necessary involving time by time the relevant key persons and institute Activities reporting A periodical progress report will be issued by each local PMO to the System Team within the 5 Th. of each months. The actual activities progress w.r.t. to the planned progress will be reported. As part of the progress report the following documents will be attached: System master plan updated in accordance with the progress reached at the end of the month Non conformance status list Each PMO will develop from the information stated in this document his detailed Product Breakdown Structure and Work Breakdown Structure and Master Bar Chart. Any modification to the present baseline will be implement only after the System Team agreement. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
16 Ref: TL Project Ref.: Issue: Draft Page: 12 Date: January, PROGRAM MASTER PLAN 8.1. Program milestone The IBIS program milestone are the following: MILESTONE PLANNED DATE PHASE C/D K.O.M. 1 MARCH 1997 STM DELIVERY 1 MARCH 1998 EM DELIVERY 15 JUNE 1998 QM DELIVERY 1 DECEMBER 1998 FM DELIVERY 15 DECEMBER 1999 FS DELIVERY 1 JUNE Master bar chart The IBIS program bar chart has been developed using for the envisaged level 2 work elements the relevant duration and network logic, with the assumption that all the necessary resources shall be make available from the institute and LABEN in order to complete them within the allocated budget. The program master bar chart, see annex 3, will be continuously updated with the input coming from the institute and LABEN in order to assess the overall program progress and identify any potential problem affecting the program milestone achievement Schedule discussion The INTEGRAL milestone imposes to manage the instrument development in accordance with the following philosophy: The structure of the EM & QM electronic unit will be developed in parallel with the Instrument STM development integration and testing. The QM main frame, Hopper, spiders manufacturing will start immediately after the Instrument STM delivery to ESA. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
17 Ref: TL Project Ref.: Issue: Draft Page: 13 Date: January, 97 The EM electronic units together with the Detector simulator will be delivered to ESA within the end of June 1998 in order to support the spacecraft integration and testing activities. The high reliability part procurement duration is assumed no longer than 12 months. It is assumed the availability of the ICARUS ASIC, MPW2 by the end of March Following the Instrument QM environmental tests completion at ESTEC the possibility to swap, for some weeks, the whole QM instrument with the already available EM electronic units and detector will be investigated with the aim to support the IBIS "end to end" test on the INTEGRAL EM spacecraft. The MASK will be delivered directly from the relevant institute to ESA as defined in the deliverable item list. The STM will be returned to IAS at the time of the Instrument FM integration to support the relevant calibration. The FM modules fabrication will start in parallel with the Instrument QM integration and testing. The above points are considered as "major" topics to be managed very carefully in order to ensure the program goals achievement. Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
18 Ref: TL Project Ref.: Issue: Draft Page: 14 Date: January, 97 ANNEX 1 INSTRUMENT PRODUCT BREAKDOWN STRUCTURE Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
19 PRODUCT TREE IBIS FLIGHT SEGMENT MAIN FRA ME Self standing item MASK TUBE Self standing item by ESA HOPPER Self standing item ISGRI PICSIT VETO DHS CALIBRATION UNIT GROUND SEGMENT ISDC GSE TEST EQUIPMENT SYSTEM LEVEL
20 MASK AND CALIBRATION UNIT PRODUCT TREE IBIS FLIGHT SEGMENT MASK CALIBRATION UNIT STRUCTURE STRUCTURE CODED MASK DETECTOR ELECTRONICS
24 PLATFORM (BY ESA) DPE 1 DPE 2 CSSW DATA HANDLING SYSTEM PRODUCT TREE DHS HEPI ASW HEPI 1 HEPI 2
25 TEST EQUIPMENTS SYSTEM T.E. MODULE T.E. PIXEL T.E. U NIT T.E. IBIS GROUND SEGMENT PRODUCT TREE IBIS GROUND SEGMENT GSE EGSE MGSE SIS ( by ESA ) HANDLING TOOL C-COE RADIOACTIVE SOURCE EXP-COE ISDC ISSW ISG RI SSW PICsIT SSW CALIBRATION SSW MASK SSW VETO SSW EGSE SSW
26 Ref: TL Project Ref.: Issue: Draft Page: 15 Date: January, 97 ANNEX 2 INSTRUMENT ACTIVITIES BREAKDOWN STRUCTURE Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
27 ACTIVITIES BREACKDOWN STRUCTURE IB IS INSTRUMENT ACTIV ITIES SYSTEM & UNITS ACTIV ITIES
28 ACTIVITIES BREACKDOWN STRUCTURE INSTRUMENT LEVEL IBIS ACTIVITIES BREACKDOWN STRUCTURE INSTRUMENT MANAGEMENT SYSTEM TEAM AI&V LABEN ISSW CEA-SAP PROGRAM MANAGEMENT PROGRAM MANAGEMENT REQUIREMENT DEFINITION QUALITIY ASSURANCE QUALITIY ASSURANCE SSW 's DEVELOPMENT TECHNICAL COORDINATION (reqirem ents & performances) AI&V DESIGN ISSW AI&V AI&V SUPERVISION MODELS AI&V CALIBRATION MANEGEMENT EGSE DEVELOPMENT
29 ACTIVITIES BREACKDOWN STRUCTURE SYSTEM AND UNITS LEVEL IBIS ACTIVITIES BREACKDOWN STRUCTURE SYSTEM DEVELOPMENT SYSTEM MANAGEMENT ACTIVITIES UNIT & MODULE DEVELOPMENT ACTIVITIES PRIOGRAM MANAGEMENT TECHNICAL COORDINATION DESIGN PPROCUREMENT M.F.G & INT. QUALITY ASSURANCE CONFIGURATION CONTROL SYSTEM AI&V T.E. DEVELOPMENT ARCHITECTURAL DESIGN DETAILED DESIGN C.P.P.A PROCUREMENT SELF PROCUREMENT MAUNUFACTORING ASSEMBLY ENGENEERING TREATMENT INTEGRATION TESTING ACCEPTANCE TESTS QUALIFICATION TESTS
30 Ref: TL Project Ref.: Issue: Draft Page: 16 Date: January, 97 ANNEX 3 PROGRAM MASTER BAR CHART Any information contained in this document is property of LABEN S.p.A. and is strictly private and confidential. All rights reserved.
31 ID Task Name 1 IBIS K.O.M. Ph. C/D F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 2 IBIS STM TO ESA 3 IBIS EM TO ESA 4 IBIS QM TO ESA 5 IBIS FM TO ESA 6 SYSTEM TEAM 7 Program management 8 Quality assurance 9 Tehnical coordination 10 Ai&v supervision 11 Calibration management 12 AI&V 13 Program management 14 Quality assurance 15 AI&V design 16 EGSE development 17 STM AI&V 18 EM AI&V 19 QM AI&V 20 FM AI&V 21 EGSE Development 22 Architectural design 23 Detailed design 24 Self procurement 25 Manufacturing 26 Assembly 27 Integration 28 Acceptance 29 EGSE Available to IBIS EM AI& 30 MGSE development 31 Architectural design 32 Detailed design 33 Self procurement 34 Manufacturing 35 Assembly 36 Integration 37 Acceptance Page 1
32 ID Task Name 38 MGSE Available to IBIS AI&V F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 39 E.M. Detector Module Simulat 40 Architectural design 41 Detailed design 42 Engineering 43 Self procurement 44 Manufacturing 45 Assembly 46 Integration 47 Acceptance 48 E.M. Detector Module Simu 49 MASK 50 Program management 51 Technical coordination 52 Quality assurance 53 Configuration control 54 STM 55 Architectural design 56 Detailed design 57 Engineering 58 Self procurement 59 Manufacturing 60 Treatment 61 Acceptance 62 MASK STM available to IB 63 QM 64 Self procurement 65 Manufacturing 66 Treatment 67 Acceptance 68 MASK QM Available to IBIS 69 FM 70 Self procurement 71 Manufacturing 72 Treatment 73 Acceptance 74 MAIN FRAME Page 2
33 ID Task Name 75 Program management F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 76 Technical coordination 77 Quality assurance 78 Configuration control 79 STM 80 Architectural design 81 Detailed design 82 Engineering 83 Self procurement 84 Manufacturing 85 Treatment 86 Acceptance 87 MAIN FRAME STM Availab 88 QM 89 Self procurement 90 Manufacturing 91 Treatment 92 Acceptance 93 MAIN FRAME QM Availab 94 FM 95 Self procurement 96 Manufacturing 97 Treatment 98 Acceptance 99 HOPPER 100 Program management 101 Technical coordination 102 Quality assurance 103 Configuration control 104 STM 105 Architectural design 106 Detailed design 107 Engineering 108 Self procurement 109 Manufacturing 110 Treatment 111 Acceptance Page 3
34 ID Task Name 112 HOPPER STM Available to 113 QM 114 Self procurement 115 Manufacturing 116 Treatment 117 Acceptance 118 HOPPER QM Available to 119 FM 120 Self procurement 121 Manufacturing 122 Treatment 123 Acceptance 124 HOPPER FM Available to I 125 ISGRI 126 Program management 127 Technical coordination 128 Quality assurance 129 Configuration control 130 System AI&V 131 T.E. development 132 STM Support Frame 133 Architectural design 134 Detailed design 135 Engineering 136 Self procurement 137 Manufacturing 138 Treatment 139 Integration 140 Acceptance 141 STM Module 142 Architectural design 143 Detailed design 144 Engineering 145 Self procurement 146 Manufacturing 147 Treatment 148 Integration F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D Page 4
35 ID Task Name 149 Acceptance F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 150 STM IEB 151 Architectural design 152 Detailed design 153 Engineering 154 Self procurement 155 Manufacturing 156 Treatment 157 Integration 158 Acceptance 159 ISGRI STM Available to IBI 160 EM IEB Structure 161 Engineering 162 Self procurement 163 Manufacturing 164 Treatment 165 Integration 166 Acceptance 167 IEB EM 168 Architectural design 169 Detailed design 170 Engineering 171 Self procurement 172 Manufacturing 173 Assembly 174 Integration 175 Acceptance 176 IEB EM Available to EM IB 177 IEB QM 189 MODULE QM 201 IEB FM 213 MODULE FM 225 PICSIT 226 Program management 227 Technical coordination 228 Quality assurance 229 Configuration control Page 5
36 ID Task Name 230 System AI&V F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 231 T.E. development 232 STM Support Frame 233 Architectural design 234 Detailed design 235 Engineering 236 Self procurement 237 Manufacturing 238 Treatment 239 Integration 240 Acceptance 241 STM Module 242 Architectural design 243 Detailed design 244 Engineering 245 Self procurement 246 Manufacturing 247 Treatment 248 Integration 249 Acceptance 250 STM PEB 251 Architectural design 252 Detailed design 253 Engineering 254 Self procurement 255 Manufacturing 256 Treatment 257 Integration 258 Acceptance 259 PICsIT STM Available to IB 260 EM PEB Structure 261 Engineering 262 Self procurement 263 Manufacturing 264 Treatment 265 Integration 266 Acceptance Page 6
37 ID Task Name 267 PEB EM F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 268 Architectural design 269 Detailed design 270 Engineering 271 Self procurement 272 Manufacturing 273 Assembly 274 Integration 275 Acceptance 276 PEB EM Available to I 277 PEB QM 289 MODULE QM 301 PEB FM 313 MODULE FM 325 VETO 326 Program management 327 Technical coordination 328 Quality assurance 329 Configuration control 330 System AI&V 331 T.E. development 332 STM BGO & Housing 333 Architectural design 334 Detailed design 335 Engineering 336 Self procurement 337 Manufacturing 338 Treatment 339 Integration 340 Acceptance 341 STM VDM 342 Architectural design 343 Detailed design 344 Engineering 345 Self procurement 346 Manufacturing 347 Treatment Page 7
38 ID Task Name 348 Integration F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 349 Acceptance 350 STM VEB 351 Architectural design 352 Detailed design 353 Engineering 354 Self procurement 355 Manufacturing 356 Treatment 357 Integration 358 Acceptance 359 VETO STM Available to IB 360 EM VEB Structures 361 Engineering 362 Self procurement 363 Manufacturing 364 Treatment 365 Integration 366 Acceptance 367 VEB EM 368 Architectural design 369 Detailed design 370 Engineering 371 Self procurement 372 Manufacturing 373 Assembly 374 Integration 375 Acceptance 376 VEB EM Available to I 377 VEB QM 389 MODULE QM 401 VEB FM 413 MODULE FM 425 CALIBRATION UNIT 426 Program management 427 Technical coordination 428 Quality assurance Page 8
39 ID Task Name 429 Configuration control F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 430 System AI&V 431 T.E. development 432 STM 433 Architectural design 434 Detailed design 435 Engineering 436 Self procurement 437 Manufacturing 438 Treatment 439 Integration 440 Acceptance 441 Calibration Unit STM Availa 442 QM 454 FM 466 DATA HANDLING SYSTEM 467 Program management 468 Technical coordination 469 Quality assurance 470 Configuration control 471 System AI&V 472 T.E. development 473 STM 474 Architectural design 475 Detailed design 476 Engineering 477 Self procurement 478 Manufacturing 479 Treatment 480 Integration 481 Acceptance 482 DHS STM Available to IBIS 483 EM 484 Architectural design 485 Detailed design 486 Engineering 487 Self procurement Page 9
40 ID Task Name 488 Manufacturing F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D 489 Assembly 490 Integration 491 Acceptance 492 DHS EM Available to IBIS 493 QM 505 FM 517 ISSW 518 Requirement definition 519 ISGRI SSW development 520 PICSIT SSW development 521 VETO SSW development 522 Calibration SSW developm 523 Mask SSW development 524 EGSE SSW development 525 ISSW Integration & accepta Page 10
-E-10 Part 1B EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space engineering System engineering Part 1: Requirements and process Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The
Technical Specifications and Documentation Control Victor Billig International Space University Strasbourg email@example.com 2010 1 Baseline Documentation Project Contract (legal terms & definitions) System
Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority
Content of the Study Proposal, rev. 1 Page 1 CONTENT OF THE STUDY PROPOSAL Content of the Study Proposal, rev. 1 Page 2 CONTENT OF THE STUDY PROPOSAL The Study Proposal shall offer to perform preparatory
Space engineering System engineering This ECSS document is a draft standard distributed for Public Review. It is therefore subject to change without any notice and may not be referred to as an ECSS Standard
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
APPENDIX G. (WBS) Space Flight Project Work Breakdown Structure G.1 Introduction G.1.1 The Project Work Breakdown Structure (WBS) is a key element of project management. The purpose of a WBS is to divide
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
Managing The Baseline Schedule Walter Majerowicz Planning & Schedule Manager Polar Operational Environmental Satellites Program Objective Provide an overview of proven baseline schedule control concepts
Remaining DOE Deliverables The following is a statement of work for each of the elements included in the remaining DOE project. 188.8.131.52 Project Controls Provide project control to maintain instrument project
Guide to Preparing the SOFTWARE PROJECT MANAGEMENT PLAN R. Buckley CSc 190 Senior Project Department of Computer Science - College of Engineering and Computer Science California State University, Sacramento
Project Documentation Document SPEC-0064 Revision A System Engineering Plan Rob Hubbard, Jeremy Wagner, Larry Daggert, Larry Stepp, Christoph Keller Systems Engineering / Project Management 5 October 2006
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
ECSS-M-ST-60C Space project management Cost and schedule management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of
r bulletin 111 august 2002 Introducing ECSS Software-Engineering Standards within ESA Practical approaches for space- and ground-segment software M. Jones & E. Gomez Ground Segment Engineering Department
September 25, 2014 EFFECTIVE METHODS FOR SOFTWARE AND SYSTEMS INTEGRATION P R E S E N T E D B Y: D R. B O Y D L. S U M M E R S 1 Software Engineer (Quality) Defense and Space The Boeing Company - Seattle,
: a Project Support Function As stated throughout the Project Planning section, there are fundamental components that are started during the pre-performance stage of the project management life cycle in
C/OSMOS Work Breakdown Structure Summary Version 2.3 January 13, 2011 Version Date Changes 1.8 November 19, 2009 Final version prior to issuing contract 1.9 December 8, 2009 Added documentation control
A Sample contractor Management Plan 1.0 INTRODUCTION 1.1 Identification This is the contractor Management Plan, document number YZ035, for the SYSTEM Z project. 1.2 Purpose The contractor Management Plan
3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification
: A Classroom Nanosatellite for Teaching Space Systems Engineering 1 Introduction The Need The Solution Background System Architecture Applications Conclusions Outline 2 The Need Space Systems Engineering
Technical Baseline Management September 30, 2003 Pat Hascall LAT System Engineering 1 Technical Baseline Management We are required to manage the configuration of our technical baseline What is configuration
Industry Day of the Euclid Spacecraft With the present announcement, the European Space Agency and Thales Alenia Space (Italy) inform the EITS Users (European Companies and Institutes) about a presentation
iss data management system ESA s Data Management System for the Russian Segment of the International Space Station J. Graf, C. Reimers & A. Errington ESA Directorate of Manned Spaceflight and Microgravity,
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
Application Functional Safety IEC 61511 Introduction Functional safety must be an integral part of the project execution if we shall succeed to make safe application program We can t test and audit safety
1. COSIMA Scientific Objectives For the COSIMA investigation the following scientific objectives were established: elemental composition of solid cometary particles to characterize comets in the framework
Project Time Management Study Notes PMI, PMP, CAPM, PMBOK, PM Network and the PMI Registered Education Provider logo are registered marks of the Project Management Institute, Inc. Points to Note Please
SECTION 01800 SYSTEMS INTEGRATION AND INTEGRATOR REQUIREMENTS PART 1 GENERAL DESCRIPTION A. This section specifies the system-wide integration requirements for the Caltrain Electrification system, i.e.
ECSS-E-ST-40C Space engineering Software ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS Standards intended to
-M-30-01A EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space project management Organization and conduct of reviews Secretariat ESA -ESTEC Requirements & Standards Division Noordwijk, The Netherlands
Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality
SOFTWARE DEVELOPMENT PLAN This document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans. This is the controlling document for managing a software project, and it
Page: 1/22 ExoMars CONFIGURATION MANAGEMENT REQUIREMENTS EXM-MS-RS-ESA-00008 Issue 1, Rev. 0 Date and Signature Prepared Agreed HME-CLS P. Provasi 29 June 2007 Approved HME-ME D. McCoy 29 June 2007 Page:
PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager
Develop Project Tasks One of the most important parts of a project planning process is the definition of activities that will be undertaken as part of the project. Activity sequencing involves dividing
EPD: Energetic particle Detector Javier Rodríguez guez-pacheco Martín Grupo de Investigación n Espacial Universidad de Alcalá EPD: Energetic particle Detector STEIN (Supra-thermal Electrons, Ions & Neutrals)
Procurement and Supply Chain In a Work Face Planning Environment COAA Workface Planning Forum Calgary, Alberta December 1 2010 Presented by: Bill Somerville Overview Scope of Discussion Owners and Contractors
Initial Release 1. Overview of Project Paralleling the development of the schedule is the development of a budget. At the initial stages of project planning, budgeting is the determination of costs associated
Introductory Certificate The APM Project Fundamentals Qualification. Examination paper Candidate Number Date Location Examination Paper Sample Paper v1.4 General Notes Time allowed 1 hour. Answer all 60
Hardware safety integrity Comments on this report are gratefully received by Johan Hedberg at SP Swedish National Testing and Research Institute mailto:firstname.lastname@example.org Quoting of this report is allowed
The syllabus provides a summary of the coverage of the qualification, the details are then found in the learning outcomes and assessment criteria. Both the syllabus and the learning outcomes and assessment
Responsive Space System Engineering: methodologies and tools prototype 83230910-DOC-TAS-EN-001 Technical University of Lisbon, Lisbon, Summary This paper reports the activities performed by Thales Alenia
EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Project Phasing and Planning Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:
INL/EXT-09-17022 Rev. 2 Independent Verification and Validation of SAPHIRE 8 Software Project Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance
Page: 1/42 Appendix 3 to /05/NL/GM E X O M A R S Phase B1 Product Assurance & Safety Requirements EXM-MS-RS-ESA-00002 Prepared by: ExoMars PA Team ESTEC Noordwijk The Netherlands Page: 2/42 DOCUMENT CHANGE
Dr. Ernest Wallmüller Wolfgang Höh Rule 8 Configuration Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Software Configuration Management (S) The process of identifying,
CASE GmbH Westendstrasse 125 80339 München Herschel PACS Test Procedure STM 1 Revision: - i Document Approval Sheet Title: Herschel PACS Subtitle: Test Procedure STM Doc. No: 1 Revision: - Prepared:......
EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Cost & Schedule Management Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:
PROCEDURE NONCONFORMANCE MANAGEMENT SYSTEM This document is stored electronically. Printed version might not be the latest. SAOCOM PROJECT COMISION NACIONAL DE ACTIVIDADES ESPACIALES BUENOS AIRES ARGENTINA
What is testing? Testing is the practice of making objective judgments regarding the extent to which the system (device) meets, exceeds or fails to meet stated objectives What the purpose of testing? There
Mission Operation Ground Software Systems Product Assurance @ ESA Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 The European Cooperation for Space Standardisation (ECSS) Established: in 1993 Goal: coherent,
Factory Acceptance Testing Comments on this report are gratefully received by Johan Hedberg at SP Swedish National Testing and Research Institute mailto:email@example.com -1- Summary According to the
The PACS Software System (A high level overview) Prepared by : E. Wieprecht, J.Schreiber, U.Klaas November,5 2007 Issue 1.0 PICC-ME-DS-003 1. Introduction The PCSS, the PACS ICC Software System, is the
ASI EO Info Day 18-19 October 2012 - Rome Danilo Muzi 18/10/2012 EE Missions Overview Contents: Swarm ADM Aeolus EarthCARE ASI Info Day Danilo Muzi 18/10/2012 EOP Slide 2 ASI Info Day Danilo Muzi 18/10/2012
Project Time Management Study Notes PMI, PMP, CAPM, PMBOK, PM Network and the PMI Registered Education Provider logo are registered marks of the Project Management Institute, Inc. Points to Note Please
Lessons Learned during the Refurbishment and Testing of an Observatory after Longterm Storage GSFC 2015 John Hawk, Sharon Peabody, and Richard Stavely NASA Goddard Space Flight Center Background The Triana
STATEMENT OF WORK FOR DESIGN, FABRICATION, INTEGRATION AND TESTING OF THE TELESCOPE STRUCTURE SYSTEM TMT.STR.MGT.12.001.REL01 27 July, 2012 TMT.STR.TEC.12.001.DRF01 Page 2 of 13 Table of Contents 1. INTRODUCTION
ECSS-Q-ST-60-02C Space product assurance ASIC and FPGA development ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of
ISO 26262 Introduction Prof. Christian Madritsch 2012 Table of Contents Structure of ISO 26262 Management of Functional Safety Product Development System Level Product Development Hardware Level Product
IAEA Services Series No. 6 ESRS guidelines for software safety reviews Reference document for the organization and conduct of Engineering Safety Review Services (ESRS) on software important to safety in
Syllabus 2nd Edition 2 Introductory Certificate Syllabus 2nd Edition 2nd Edition Introductory Certificate syllabus All of the syllabus elements should be taken within the context of a project and project.
0 UC Modernization Project Plan 1115 d 1 1 Phase I - Business Case Development and Competitive Procurement 205 d 2 1.1 Complete Initial Feasibility Study 55 d 3 1.2 Prepare and Issue LBR 30 d 2 4 1.3 Competitive
The Implementation Advance Planning Document (IAPD) 1 You are here APD Overview Planning APD Implementation APD RFPs and Procurement APD Updates System Testing Regulation Getting to Go Live Project Management
Date: Aug. 2002 Page: ii Contraves Space AG Schaffhauserstr. 580 CH-8052 Zurich Switzerland CLASS 1 UNRESTRICTED 1 2 INDUSTRY 2 3 RESTRICTED 3 CATEGORY CONFIGURED, FOR APPROVAL NOT CONFIGURED, FOR APPROVAL
ECSS-Q-ST-80C Space product assurance Software product assurance ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS
SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS) 1.0 SEI Product 1.1 SEI Level 2 Product 1.1.1 SEI Level 2 Process 184.108.40.206 Requirements Management Process 220.127.116.11 Software Project Planning Process
VALdriv PLM PLM Glossary Business Workflow Data liaison Business Workflow Data liaison VALdriv PLM : PLM Functionalities Business Project VALdriv PLM referential Product Planning Dashboarding Value Chain
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
REQUEST FOR EXPRESSIONS OF INTEREST (CONSULTANT SERVICES) Consultancy services for Systems Integration and IT project management Client: Central Bank of Yemen Country: Republic of Yemen Project: Financial
Overview Once you've initiated the project and gathered all relevant information, you'll then begin planning your project. The planning stage depends on the size of your project, how much information you
Information Technology Manag gement Framework Roles and Respo onsibilities Version 1.2 Novemb ber 20122 ITM Roles and Version History Version ed By Revision Date Approved By Approval Date Description of
The CMDB at the Center of the Universe Reg Harbeck CA Wednesday, February 27 Session 5331 Purpose Clarify origin of CMDB concept and what it is Understand difference and equivalence between CMDB and Asset
Fernando Aguado-Agelet University of Vigo - INTA August 10th 2008 2008 Cubesat Summer Developer s Workshop 1 Project Presentation GENERAL DESCRIPTION University of Vigo: Leader Spanish university in R+D