INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 1/17
Schedule Architecture Description Document For MTG
[DRL code : ] [AD code : AD-07C-03] [ PT code : I10000/S10000]
Written by
Responsibility
+ handwritten signature if no electronic workflow tool F.THEVENIN
TAS MTG Schedule Manager
Verified by T.SCHAEFER
OHB MTG Schedule Manager
A.SMOLDERS
AIV Manager
Thierry GRASSIN
Product Assurance Manager
Approved by OHB M.KESSELMANN
OHB Project Manager
Approved by TASF Alain LAMOTHE
TASF Project Manager
Approval evidence is kept within the documentation management system.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 2/17
CHANGE RECORDS ISSUE
DATE
§ CHANGE RECORDS
AUTHOR
01
24/08/2010 First Issue
F.THEVENIN
02
14/01/2011 Update of the descriptive synoptic according to industry sharing
F.THEVENIN
03
04/02/2011 Update according ESA comments
F.THEVENIN
04
20/01/2012 Update following 2011 Schedule Working Group
F.THEVENIN
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 3/17
DISTRIBUTION LIST Company
Name
ESA
R.CARLI
OHB
T.SCHAEFER
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 4/17
TABLE OF CONTENTS 1.
SUBJECT ............................................................................................................................................................5
2.
REFERENCE DOCUMENTS...............................................................................................................................5
3.
APPLICABLE DOCUMENTS..............................................................................................................................5
4.
SCHEDULE ARCHITECTURE ............................................................................................................................6
5.
4.1
Descriptive synoptic .................................................................................................................................6
4.2
Methodology ..............................................................................................................................................9
4.3
Margins definition ...................................................................................................................................10
4.4
Awaited deliverable table .......................................................................................................................12
SCHEDULE REPORTING .................................................................................................................................12
TABLE OF ANNEX APPENDICES 1 APPENDICES 2 APPENDICES 3
PROCUREMENT TABLE TEMPLATE.....................................................................13 SCHEDULE TEMPLATE .........................................................................................14 MTG-I SCHEDULE STRUCTURE ...........................................................................16
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 5/17
1. SUBJECT The aim of this document is to provide the description of the architecture for the overall MTG schedule. It shall establish the general principles valid for the overall MTG program. The intended goal is to give guidelines to the different schedules provided by subcontractors in order to ease the understanding of plannings and tables. The perimeter of this architecture contains the global system, the S/C and subsystem plannings and the procurement tables. The structure of the schedule will be based in accordance with the Product Tree [AD-3] and the DDVP [RD-4]. These pieces of information lead to synthesize the system planning, the global procurement table and the trend graph for the MTG project.
2. REFERENCE DOCUMENTS RD
ID
Title
Rev
RD-1
MTG-TAF-SA-SC-0761
MTG schedule report template
RD-2
MTG-ESA-SA-RS-0074
ECSS E-Series Tailoring
RD-3
MTG-TAF-SY-PT-0138
Product Tree
5
RD-4
MTG-TAF-SA-PL-0246
MTG System Satellite Development & Verification Plan
2
1
3. APPLICABLE DOCUMENTS AD
ID
Title
[AD-26C-01]
MTG-TAF-SY-TN-0033
MTG Definitions, Terms and Acronyms
AD-2
ECSS-M-ST-10C
Project Planning and Implementation
AD-3
ECSS-M-ST-60C
Cost and Schedule Management
[AD-07]
MTG-ESA-SA-RS-0072
MTG Management Requirements (MARD)
Rev
1
1
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 6/17
4. SCHEDULE ARCHITECTURE The architecture presented hereafter is applicable to each main subcontractors. The different elements present in the Product Tree shall be represented in the schedule. The ITTs of flight and ground equipment will be represented in the procurement tables and in the Schedule structure (see APPENDICES 3 for a template of schedule files structures). Even if the Schedule architectures would be similar, there should be one implementation for MTG-I schedules and one for MTG-S schedules.
4.1 Descriptive synoptic The synoptic shown hereafter describes the logic and links between the overall documents awaited from the different contractors to build the system documents. A template for the procurement table (see dedicated box in the scheme below) is shown in APPENDICES 1. This table should be followed by procurement responsibles and updates shall be periodically streamed to the Customer. The dates presented shall reflect the current dates for each review or DRB. The development time shall be the one agreed with the contractor (if already discussed) or realistic evaluation.
The different elements in yellow represent the documents edited by OHB, in blue are the documents written by TAS-F. In orange, the IRS planning is delivered by KT. In green are represented the documents edited by other contractors.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE
Procurement Table
REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
Procurement Table
FCI Planning
LI Planning
S/S Milestones Planning for B 2/CD phase Critical pathes
S/S Milestones Planning for B 2/CD phase Critical pathes
Page : 7/17
Procurement Table Phase B2 Phase C/D
PF Planning S/S Milestones Planning of the phase Critical pathes
Phase B2
Launcher Milestones
Phase C/D
MTG-I Planning
Preparation Milestones (PMAR …) Launch dates
S/S Milestones Planning of the phase Critical pathes DCS & GeoSAR
IQT Milestones Planning & Trend graphes PDG
SatSim
TTC Suitcase
Procurement Table Including LLI details Procurement type (ITT, RFQ, PO, DN) Key dates (From data package to KOM) Lead Time Need dates
System milestones (Sat level +PF) MTG-I milestones (FCI, LI, DCS&GEOSAR level) such as PDR , CDR, QR, main TRR , DRB of models (EM, STM …) Deliverables (IQT, PDG, SatSim)
Legend : TAS Responsibility OHB Responsibility
AOCS Simulator
Subco Responsibility
Figure 1.
MTG-I schedule descriptive scheme
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE
Procurement Table
REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
Procurement Table Phase B2 Phase C/D
IRS Planning PF Planning
S/S Milestones Planning for B2/CD phase Critical pathes
S/S Milestones Planning of the phase Critical pathes
Phase B2
Launcher Milestones
Phase C/D
MTG-S Planning
Preparation Milestones (PMAR …) Launch dates
S/S Milestones Planning of the phase Critical pathes DCS & GeoSAR
IQT
PDG
SatSim
TTC Suitcase
Milestones Planning & Trend graphes
Procurement Table Including LLI details Procurement type (ITT, RFQ, PO, DN) Key dates (From data package to KOM) Lead Time Need dates
System milestones (Sat level+PF) MTG-S milestones (IRS level) such as PDR, CDR, QR, main TRR, DRB of models (EM, STM …) Deliverables (IQT, PDG, SatSim)
Legend : TAS Responsibility OHB Responsibility
AOCS Simulator
KT Responsibility Subco Responsibility
Figure 2.
MTG-S schedule descriptive scheme
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
Page : 8/17
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 9/17
4.2 Methodology The methodology adopted is derived from the AD-3 and Erreur ! Source du renvoi introuvable. documents. In TAS understanding, the Schedules shall reflect the items present in the Product tree and the logic of development shown in the Design & Development Plan. Yet, the schedule structure shall answers to the following requirements of Erreur ! Source du renvoi introuvable. :
MARD 8.1f : The supplier shall create the MTG schedules using MS Project Note : The exchanged plannings are awaited in MS Project 2007 format (and printed as PDF file from a MS Project planning specifically to check the dates when MS Project 2010 is used). It should also follow the template given in APPENDICES 2.
MARD 8.2.h The supplier shall accept that the customer will request, at times of intense activity or in critical situations, more frequent or detailed schedule reporting of the relevant activities
MARD 8.2.i During the execution of the AIT programme, the supplier shall provide in addition to the normal schedule, a schedule of daily activity for the next four weeks that shall be updated on a weekly basis based on DRD PM-8.
MARD 8.3.a The supplier shall provide a schedule report in conformance with Annex C, Schedule Progress Report DRD as part of overall project progress report (Annex E of ECSS-MST-10C, Rev 1)
MARD 8.3.b The GANTT chart package shall consist of three levels Project Summary Bar Chart (Level 1) Summary Bar Charts (Level 2) Master Control Bar Charts (Level 3 and 4) Detailed AIV bar charts (Level 1,2,3 and 4) Note : Level 1 : Overall satellite and GSE Level 2 : System, Instruments , GSE and major tasks Level 3 : Subsystems, Equipments , GSE and associated tasks Level 4 :Subassemblies and GSE forming level 3 elements
MARD 8.3.c Level 1 and 2 bar charts shall be updated and submitted to the Agency together with each Progress Report
MARD 8.3.d The Project Summary Bar Chart shall be established by the supplier and shall summaries all the activities of each relevant Management Summary Bar Chart. Note : Project Summary Bar Chart identifies amongst other : The Contractual agreed milestones The due dates for Customer Furnished Equipment The use of ESA and/or other test facilities And the interfaces with Third parties such as Launcher authorities, Ground Segment developers
MARD 8.3.e The Summary Bar Chart shall be established for each element identified at Level 2 of WBS summarizing all the activities of each relevant Master Control Bar chart of that particular level 2 constituent.
MARD 8.3.f The Master Control Bar Chart shall be established for each element identified at Level 3 of WBS summarizing all the relevant activities at level 4 of WBS
MARD 8.3.g Detailed AIV Bar Charts shall be established on all levels, including GSE and any other deliverable element of the contract
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 10/17
MARD 8.3.h The method and form of bar chart presentation shall follow the state of the art concerning planning and scheduling techniques, e.g. showing the current baseline schedule against the current working schedule. Note : A selection of milestones shall be agreed by the Customer, the contractor and the relevant subcontractors. These milestones should be present in the Milestone Schedule with the baseline date and the current date. The evolution of these milestones should be traced by trend graphs.
MARD 8.3.i Trend Charts shall show each significant milestone for MTG as agreed between the customer and the supplier. Note : The trend charts are implemented in the “Milestones & Trend graphes” box of the chapter 4.1 synoptic. They are represented in the schedule report as a table (see template in ) and a visual graph.
The procurement tables are intended to be in Excel files following the template given in APPENDICES 1. The information awaited are the procurement type (ITT or RFQ or PO), the key dates for ITT/RFQ for each element, the lead time and the agreed need date for each delivery. The order of the sections in all schedules should be the same as given in APPENDICES 2 to facilitate the reading of the planning. Therefore, the planning should be separated in 4 main sections : • Milestones : this should count the reviews and delivery dates but also FAR dates and launch dates for System level • Engineering activities : a summary of main activities supporting the reviews • Development activities : a summary of main activities supporting the reviews linked with the development models • AIT activities : This should be sub divided for each model to be delivered The first section should be related to the Milestones of the subsystem (T0, PDR, CDR, QR, main TRR and DRB of models) followed by the planning itself. These milestones shall be automatically linked to the overall milestones schedule. For the main subsystems (MTG-I and MTG-S spacecrafts or PlateForm planning), the planning for detailed engineering activities should be in separate file(s) from the main planning. For equipments, the C/D phase planning should be given in a separate section from the B2 phase planning. Moreover, a procurement file shall be separated from the main schedule in case of numerous procured items (e.g Plateform, FCI, IRS …). The main critical path should be emphasized in red. As the schedules are dispatched on multiple files, the DRB/need dates shall be electronically linked between the relevant files in order to echo any evolution or shifts (i.e any shift in phase B2 planning (for example the procurement of item that arrives later than foreseen) that has impact on CD phase should be represented in the CD phase planning). The files are expected at each progress report and major reviews (SRR, PDR, …).
4.3 Margins definition In a matter to have the same definition of the different notions of margins, floats and contingencies, the following scheme represents the way to understand these words.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 11/17
It may be implemented in the Milestones Schedule only as the following template :
In order to compute the Margin (or float depending if we discuss as level N or N+1), the contract date should be copied with link in the field called “Recall for contractual date”. Then the Margin/Float is calculated as the difference between the field “Recall for contractual date” and the field “Beginning date”. In order to compute the Contingency, the need date found in the detailed activities schedule should be copied with link in the field called “Recall for Need date” of the milestones planning. Then the Contingency is calculated as the difference between the field “Recall for Need date” and the field “Recall for contractual date”. In the end the Total Margins is the sum of the Margin/Float field and the Contingency field. In that way, any modification of activities impacts the need date and then the contingency. And any DRB slippage impacts the float. These 2 modifications may be counter-balanced to keep the same Total Margin. For the example here above, the item 1 is late by 1 day even if the contingency is positive.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 12/17
4.4 Awaited deliverable table
Subsystem
Procurement table
MTG-I FCI LI PF DCS&GEOSAR MTG-S IRS Common IQT PDG SatSim TTC Suitcase AOCS Simulator
X X X X
Planning Phase B2
Planning Phase C/D
X
X
Global Planning X X
X
X
X
X
X
X
X
X
X X X X X
5. SCHEDULE REPORTING A template for the schedule report is given in RD1. This should be given in a MS Word document and presented with a MS Powerpoint file. The document should describe first : The overall schedule with : 1. The assumptions Calendar used for the schedules, version of subcontractors schedules used to build the Schedule Report. This should also be the place to make major warnings (ie slippages) if any. 2. The main dates 3. The CFI dates if any 4. The deliverable dates 5. A summarized barchart of the project that shows the main activities and their sequences.
Then for each subsystem : 1. The significant events of the period 2. The Milestones Tables T0, reviews, need dates, Deliverables 3. A Schedule analysis containing and elaborating on o The Critical path per satellite model (STM, EM, PFM, FMs) o The slippages wrt the schedule of the previous Progress Report o The margins (for each satellite model) o A Trend Graph o A list, planning and status of the Actions needed to de-criticize issues, mitigate risks and recover adverse trends (as appropriate) 4. The General schedule o Phase B2 o Phase C/D The Schedule report is awaited in a 8 week periodicity before the PDR and 10 weeks after.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE
APPENDICES 1
REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
Page : 13/17
Procurement table template
Processed as : KOM+Dev duration
Gives the status and eventual delay in weeks between the actual DRB date and the contractual date
Note that the contractual date is the one given by the S-SOW of the ITT when the KOM with the supplier is not performed. Otherwise this date should be the one agreed for the contract.
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE
APPENDICES 2
REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
Page : 14/17
Schedule template
These long bars are given for example only. The procurement of elements shall be given with details in the appropriate schedule file and only the relevant milestones shall be reflected in the overall schedule when needed (ie STM DRB dates at the start of the STM section, etc …)
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
Page : 15/17
Nota : For each model, a set of milestones shall represent the DRB awaited to perform the task that is collapsed in the above template As “Satellite Model xx”. The reference of the file should be given in the title bar. The date of the planning should also be present in that bar
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
INTERNAL THALES ALENIA SPACE
APPENDICES 3
REFERENCE :
MTG-TAF-SA-SC-0388
DATE :
20/01/2012
ISSUE :
04
MTG-I Schedule structure
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
Page : 16/17
INTERNAL THALES ALENIA SPACE REFERENCE : MTG-TAF-SASC-0388 DATE : 20/01/2012 ISSUE :
04
Page : 17/17
END OF DOCUMENT
All rights reserved, 2012, Thales Alenia Space
INTERNAL THALES ALENIA SPACE– COMMERCIAL IN CONFIDENCE
100181547K-EN-3
