1. JPSS Common Ground System Block Build Plan Eric Ort IDPS Build Manager June 3 2011 JPSS CGS Form J-110 10/22/2010

2. JPSS Common Ground System Page 2 Assumptions: ▫ Functionality in earlier sub-blocks (ie., 1.2.1, 1.2.2) will be inherited by later sub- blocks (1.2.3) ▫ Functionality that is in an earlier block (1.2) will be inherited by later blocks (1.5) ▫ Block 1.2.1 is pre-launch but post Mx5 so is not tied to a particular Mx release, Sub-block 1.2.2 is going into Mx6, Sub-block 1.2.3 is going into Mx7 ▫ Sub-block 1.2.3 will overlap sub-block 1.5.1 ▫ Development in sub-blocks (within a block) overlaps and requires separate branches. Notes: ▫ After every block release to the shared_csi_b1.5 branch for inclusion in an Mx release, there will be a migration of work down to the remaining blocks to keep them up-to-date and to avoid migration issues when releasing to the shared_csi_b1.5 branch.. ▫ There will be shared SI level branches off of the shared_csi_blk branches and developer private branches off of the shared SI level branches. ▫ Work that has already been done on the “i2.1” and “shared_csi_i2.1” branches prior to ATP for Block 1.5 will be migrated on functionality basis to the appropriate shared_csi_blk1.5.x branch. Assumptions, Constraints & Notes 2/2/2011

3. JPSS Common Ground System Page 3 Block 1.2/1.5 Branching Plan 2/2/2011 Time i1.5 shared_si_blk1.2.1 Block 1.2.3 Release shared_csi_b1.5 Mx5 shared_csi_blk1.2.2 shared_csi_blk1.2.3 Mx6Mx7 shared_csi_blk1.5.3 shared_csi_blk1.5.2 shared_csi_blk1.5.1 Block 1.2.2 Release Block 1.2.1 Release Block 1.5.1 Release Block 1.5.2 Release Block 1.5.3 Release Mx8Mx9 shared_csi_i2.1 i2.1 Migrate and re-use State 2 code

4. JPSS Common Ground System Page 4 Backup 2/2/2011

5. JPSS Common Ground System Page 5 –Schedule Notes from Block Summary –Block 1.2 Timeline –Assumptions, Constraints and Notes –Questions –Block 1.2 Branching –Block 1.5 Branching –Block 2.0 Branching Content of Presentation 2/2/2011

6. JPSS Common Ground System Page 6 –Block 1.1 is what will be launched. –Block 1.2.1 is prior to NPP launch –Block 1.2.2 is planned for post NPP launch; initial sustainment releases following launch freeze lift (apprx L+3mth to L+7mths) –Block 1.2.3 is planned for post NPP launch; subsequent sustainment releases post launch (approx L+12mth to L+18mths) Depends on when TPI ends –Block 1.2 7/11 - 1/13 ATP Block 1.2 - Mid August –Block 1.5 1/13 - TBD Fuzzy where Block 1.2 ends and Block 1.5 begins –Block 1.5.1 is implemented by L+18 months (note overlap with end of Block 1.2) –Block 1.5.2 is implemented by L+24 months –Block 1.5.3 is implemented by L+36 months Schedule 2/2/2011

7. JPSS Common Ground System Page 7 –ECP #1 (Block 1.2 – Near term changes) ECP Request for 6 items received 3 May Block 1.2 Contents review held May 23, 2011 Proposal submittal planned NLT 31 May –ECP #2 (Block 1.2 – Remaining changes) Prioritized list of candidate content reviewed with NASA on 27 April Block Content Review planned for 23 May ECP following Block Content Review (~7 June) –ECP #3 (Block 1.5) Prioritized list of candidate content to be reviewed w/ NASA during May PMR Block Content Review planned for ~Nov. ECP schedule is TBD but recommend NLT July for long-lead changes followed by final changes after Block Content Review Schedule 2/2/2011

8. JPSS Common Ground System Page 8 Block 1.2 Timeline 8

9. JPSS Common Ground System Page 9 Assumptions: ▫ Sub-block 1.2.3 is Mx7, Sub-block 1.2.2 is Mx6, Block 1.2.1 is pre-launch but post Mx5 so is not tied to a particular Mx release. ▫ Development in sub-blocks overlaps requiring separate branches. Questions: ▫ Does shared_csi_b1.5 and i1.5 continue with PCRs from NPP/Sustainment or does it merge into and become Block 1.2 ? Notes: ▫ Since blk1.2 is similar to i1.5 as a deployed branch, we want to keep its content pristine. Therefore, we will initially branch blk1.2 off of i1.5 which will contain Mx5. ▫ Work on shared_csi_b1.5 as part of Mx6 will be merged directly to shared_csi_blk1.2.1 and then included with the other sub-block 1.2.1 content when merged up to the blk1.2 branch as a candidate for release. »This is to keep the content of the blk1.2 branch pristine. ▫ There will be shared SI level branches off of the shared_csi_blk branches and developer private branches off of the shared SI level branches. Block 1.2 Assumptions, Constraints & Notes 2/2/2011

10. JPSS Common Ground System Page 10 Assumptions: ▫ Sub-block 1.2.3 is Mx7, Sub-block 1.2.2 is Mx6, Block 1.2.1 is pre-launch but post Mx5 so is not tied to a particular Mx release. ▫ Sub-block 1.2.3 overlaps with Sub-block 1.5.1, but will be finished before Sub-block 1.5.1 ▫ Development in sub-blocks overlaps requiring separate branches. Questions: Notes: ▫ Since blk1.5 is similar to blk1.2 as a deployed branch, we want to keep its content pristine. Therefore, we will initially branch blk1.5 off of blk1.2 which will contain the content of sub-block 1.2.2. ▫ When shared_csi_blk1.2.3 is promoted to blk1.2 indicating the code is stable, it will be migrated to shared_csiblk1.5.1 and then included with the other sub-block 1.5.1 content when merged up to the blk1.5 branch as a candidate for release. »This is to keep the content of the blk1.5 branch pristine. ▫ There will be shared SI level branches off of the shared_csi_blk branches and developer private branches off of the SI level branches. Block 1.5 Assumptions, Constraints & Notes 2/2/2011