MTG Schedule Report template

Size: px

Start display at page:

Download "MTG Schedule Report template"

Mildred Craig
6 years ago
Views:

1 1/13 MTG Schedule Report template [DRL code : ] N/A [AD code : AD-07C-04] [ PT code : I10000/S10000] Written by F.THEVENIN Responsibility + handwritten signature if no electronic workflow tool MTG TAS Schedule controller Verified by T.SCHAEFER A.SMOLDERS T.GRASSIN Approved by OHB Approved by TASF OHB Schedule controller TAS AIV Responsible Satellite PA Manager OHB Project Manager TASF Project Manager Approval evidence is kept within the documentation management system.

2 2/13 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR /11/2011 First issue of the template following BDR action F.THEVENIN

3 3/13 DISTRIBUTION LIST Company ESA OHB Name R.CARLI T.SCHAEFER

4 4/13 TABLE OF CONTENTS 1. INTRODUCTION Applicable Documents Reference documents OVERALL MTG-I/S SCHEDULE Assumptions Main reviews CFI need dates Deliverable dates Satellite models Deliverable elements to Subcontractors Overall summarized barchart SCHEDULE FOR P/F Significant Events & assumptions Milestones Tables Schedule analysis General schedule Platform LLI list SCHEDULE MTG-I/S Instruments SYSTEM PLANNING MTG-I/S Significant Events Milestones Tables Schedule analysis General schedule... 13

5 5/13 LIST OF FIGURES FIGURE 1. SCHEDULE COMMITMENTS... 7 FIGURE 2. SCHEDULE OVERVIEW... 9 FIGURE 3. MILESTONES WITH ASSOCIATED MARGINS FIGURE 4. PROCUREMENT TABLE... 11

6 6/13 1. INTRODUCTION This chapter should describe the aim of the document. This should be the place to explain how the necessary reporting themes are covered (including LLI for MTG-I). 1.1 Applicable Documents This part should give a table recalling the documents that are applicable for the Schedule reporting. ID Title Reference Applicable issue AD1 Schedule Management MTG-TAF-SA-MN-0181 Meeting MoM AD-07C-03 Schedule Architecture MTG-TAF-SA-SC Description Document AD-3 MTG-ESA-SA-RS-0072 MTG Management Requirements (MARD) Reference documents This part should give a table recalling the documents the Schedule report refers to. The table below states the documents that should be present at minimum : ID Title Reference Applicable TAS OHB issue RD1 ECSS Project Planning & Implementation ECSS-M-ST-10C X X RD2 ECSS Cost & Schedule Management ECSS-M-ST-60C X X RD3 MTG-I Satellite AIT Plan MTG-TAF-SA-PL X RD3 MTG-S Satellite AIT Plan MTG-OHB-SAS-PL-0026 X RD4 MTG-I GSE Design and Development Plan MTG-TAF-SA-PL X RD4 MTG-S GSE Design and Development Plan MTG-OHB-SY-PL-0028 X RD5 MTG FCI TA PROGRESS REPORT #n MTG-KT-CI-RP-0013 n X RD5 IRS PROGRESS REPORT #n MTG-KT-IR-RP-0016 n X RD6 LLI list for MTG platforms MTG-OHB-PF-LI-0009 X X RD7 FCI-TA LLI MTG-KT-II-LI-0012 X RD8 Evaluation reports for items in open competition TAS-F proposal V6 part 2 X RD9 MTG Risk Register MTG-TAF-SY-TN X RD9 MTG-S Risk Register MTG-OHB-SAS-LI-0062 X RD10 MTG-I Schedule structure PM-8_MTG-TAF-SAI-SC-0577 X RD10 MTG-S Schedule MTG-OHB-SY-SC-0001 X RD11 PF Schedule MTG-OHB-PF-SC-0002 X X

7 7/13 2. OVERALL MTG-I/S SCHEDULE 2.1 Assumptions This chapter should describe the perimeter used to build the schedule and the schedule report This way, there should give first a short description of the context in which the schedule report is made. Then it recalls the rhythm of work and days off-work foreseen in the schedule : As an example, for MTG-I, it is stated that the plannings have been built with a working rhythm of 5 days per week. In addition the following days are considered off work : Eastern Monday Ascension day Whitsun 14th July 2 weeks break at beginning of August 15th August End of the year break (from Christmas Eve to New Year s day included) The working rhythm is enhanced to 2 shifts by day in AIT Satellite and for FCI (even 3x8 for vacuum tests). Then a paragraph should deal with the technical document used to issue the schedule report : Procurement status (date of revision of the procurement table) P/F schedule issue or simulation Payloads schedules or SOWs revision if no schedule available It should also be the place to make major warnings concerning some slippages (if any). When a discrepancy exists between a date arose by a supplier and a date used in the schedule (for example when a negotiation is in progress at the time of the schedule report edition), a table recalling the date arose by the supplier and the commitment used to perform the planning is necessary. Sub-system 1 event Sub-system 2 event Contractual date (SOW) DRB Date assumed by TAS/OHB Dates given by the supplier Shift from SOW (months) Comment Figure 1. Schedule commitments

8 8/ Main reviews Here are recalled the major review dates at MTG-I or S system level : Review SRR System DP delivery BDR collocation PDR System DP delivery PDR System collocation System Satellite CDR QR Satellite Delta QR Satellite MTG-I/S Customer Request TAS/OHB current T0 + T0 + Date N/A N/A 2.3 CFI need dates Here a recalled the CFI need date with requested date and current/committed date. This chapter should exist but with no table if no CFI are foreseen. 2.4 Deliverable dates Satellite models Here are recalled the major deliverable dates at MTG-I or S system level : Model End of STM-I/S End of EM-I/S FAR MTG-I/S 1 CTS MTG-I/S 2 CTS MTG-I 3 * CTS MTG-I 4 * Customer Request TAS/OHB current T0 + T0 + Date N/A N/A * relevant only for MTG-I Deliverable elements to Subcontractors This chapter should give the view of the deliverable dates of elements as written in the SOWs of subcontractors. This should be the case for MTG-I documents awaited as inputs for the Platform (AD-24PF issues, AD-25PF issues )

9/13 2.5 Overall summarized barchart This chapter should present an overview of the MTG-I or S project. This scheme is given to have a general overview of the program.

9 9/ Overall summarized barchart This chapter should present an overview of the MTG-I or S project. This scheme is given to have a general overview of the program. There should be a sentence to warn that if a discrepancy is found between this scheme and the detailed schedules, the detailed schedules supersede the general overview. Example of overview used for MTG-I : Figure 2. Schedule overview

10 10/13 3. SCHEDULE FOR P/F 3.1 Significant Events & assumptions This chapter should describe the major facts happened in the reporting period that impacts the planning. Moreover, it should give the assumptions used to build the P/F schedule ie AVM development philosophy, recall of technical baseline if different options may be considered 3.2 Milestones Tables This chapter should give the tables of the review dates and delivery dates concerning the Platform. As per ESA request, this should also present in some way the software review dates. Customer Request Review in SOW OHB current in TAS schedule T0 + T0 + Date PDR PF (DP out) /02/2012 Software PDR /04/2012 Software DDR /10/2012 Software DDR2 N/A 28 18/03/2013 Software DDR3 N/A 30 18/05/2013 Software CDR /11/2013 CDR PF /03/2014 Software QR /11/2014 Customer Request P/F Model in SOW OHB current in TAS schedule T0 + T0 + Date PF STM /10/2013 PF EM /06/2014 PF MTGI PFM /05/2015 PF MTGI FM /11/2016 PF MTGI FM /03/2018 PF MTGI FM /05/2019 Then a view of these milestones with the associated margins should be present. (For example a view of the milestone schedule as hereunder).

11/13 Figure 3. Milestones with associated margins 3.3 Schedule analysis This chapter should deal with the critical path for platform models and the trend graph of the reviews and the delivery dates.

11 11/13 Figure 3. Milestones with associated margins 3.3 Schedule analysis This chapter should deal with the critical path for platform models and the trend graph of the reviews and the delivery dates. Any mitigation plan should be presented here in relationship with the Risk Register if relevant. 3.4 General schedule Here are presented : 1) The procurement table related to P/F items. As per ESA request, this table should present the following information : ITT dates KOM date Actual delivery date for each model procured Recall for the delivery date presented at the previous report Recall of contractual date (when KOM preformed) or the SOW date Recall of the need date for the model Example of table presenting these informations for the EPS subsystem : Figure 4. Procurement table

12 12/13 A discussion related to the GSE procurement should also be present. 2) A view of the engineering schedule with a discussion consolidating the P/F PDR date. 3) A section concerning the software development 4) A section dealing with the models development (AVM, STM, EM, PFM and FMs AITs) 3.5 Platform LLI list As for MTG-I DRL, the PA-12 document is merged with the schedule report, this section is specific to MTG-I unless another agreement. 4. SCHEDULE MTG-I/S This part concerns the extract of instrument schedule reports significant at system level. For MTG-I, the schedule reporting of the FCI and the System are merged. Therefore the FCI section is more detailed. 4.1 Instruments Here are described the reporting concerning the instruments. For MTG-S, this should be the reporting of UVN and IRS developments. For MTG-I, this section reports for FCI, LI and DCS/GEOSAR. The sub-sections needed are : Significant Events Milestones Tables Schedule analysis (with critical path discussion and appropriate trend graph). When an important slippage is presented by the supplier, a discussion on the reasons of the slippage and a mitigation plan should be present. If a decision at management level is awaited, the section should present the mitigation scenario and refer to progress report in which the appropriate scenario shall be selected. General schedule (with a view on procurement if relevant containing GSE procurement, the engineering schedule discussion consolidating the instrument PDR date and then a view of models AIT) LLI list (for MTG-I payloads only) 4.2 SYSTEM PLANNING MTG-I/S Significant Events This section deals with the significant progress done at schedule level concerning the System schedules. Here are presented eventual improvements on schedule or modification of perimeters (for example BDR integration in the schedule and explanation why the subsequent milestones don t move) Milestones Tables Here are recalled the tables of reviews and delivery dates for models. The view of the margins is awaited in this section.

13 13/ Schedule analysis This sections should deal with critical paths, delays/margins discussion and trend graphs related to MTG-I/S system schedule General schedule Here is given the view of : 1. the engineering schedule (specification process, progress of analysis, plans ). 2. Then a view of procurement at system level when relevant (System ITTs, GSEs ). 3. By the end, a view of AITs of the different models of satellite should be presented (one page per model in order to have a resolution on tasks) END OF DOCUMENT

CONTROLLED DISTRIBUTION REFERENCE

CONTROLLED DISTRIBUTION REFERENCE ISSUE : 01 PAGE: 2/14 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR 01 26/05/09 First issue MS - PF ISSUE : 01 PAGE: 3/14 TABLE OF CONTENTS 1. PURPOSE... 4 2. DOCUMENTS... 5 2.1 Normative Documents...5