Embed Size (px)
DESCRIPTION
Citation preview
1
Combining Apples and Oranges to Make Juice:NOAA/NASA Cooperation in GOES-R
Barbara PfarrGOES-R Program Systems Engineering Lead
PM ChallengeFebruary 2009
2
Why the World Needs GOES
. . . Sustained Observations of the Atmosphere, Oceans, Land and Sun
3
N
S
SubsatellitePoint
Equator
22,300 Mi
• GOES I-M (8-12)* series operational since 1994– GOES-10 operational at 60º W in support of South America beginning December 2, 2006– GOES-11 operational as GOES West beginning June 21, 2006– GOES-12 operational as GOES East beginning April 1, 2003
• GOES N-P – GOES-13 launched May 24, 2006, storage at 105º W, turned over to NOAA as of January 24, 2007– GOES-O in storage; will launch no earlier than April 2009– GOES-P in temporary ground storage ; will launch no earlier than December 2009
• GOES-R series will replace the GOES-N series no earlier than 2015
Two operational satellites and on-orbit spare
Primary Requirement: Continuity of Capability
GOES-11135° West
GOES-1275° West
GOES-13105° West
(Spare)
* Note: Satellites are labeled with letters on the ground and changed to numbers on-orbit
GOES Constellation
4On-orbit GOES storageOperational
* Launch currently projected for April 2009Satellite is operational beyond design life
Continuity of GOES Operational Satellite Program
Calendar Year
2027202620252024202320222021202020192018201720162015
GOES O *
GOES P
GOES R
201420132012201120102009
GOES 13
GOES 12
GOES 11
2007 2008
GOES 10 Backup
GOES East
GOES West
On-orbit Spare
GOES S
As of January 5, 2009
2028
5
GOES-R Benefits: More than Continuity
• Improved tropical cyclone forecasting will result in an increased ability to protect property and to enable evacuation of individuals residing in the path of the storm, while also reducing losses to the recreational boating industry.
• Enhanced aviation forecasting results in decreased commercial aviation delays and repair costs to aircraft due to volcanic ash.
• More accurate temperature forecasting contributes to improved energy demand expectations and savings in the electricity and natural gas sectors.
• Enhanced forecasts will lead to more efficient irrigation of crops, resulting in water and energy savings.GOES-R Launch NET FY 2015
Program Architecture2 Satellites (GOES R & S), with unfunded options for 2 (GOES T&U); 10 year operational design life
Program Operational Life FY 2017 – FY 2028
Program Life-cycle FY 2009 President’s Budget $7.7 billion
606/19/2008 v2 6
Command and Data Acquisition Station Wallops, VA
NOAASatellite Operations
FacilitySuitland, MD
RemoteBackup Facility
GOES-East75° West
GOES-West137° West
GOES-R System ConfigurationGOESGOES--R System ConfigurationR System Configuration
Command & control, data
Data
Command & control, data
Direct Readout Users
6
Data
7
GOES-R Functional Overview
UserCommunity
Archive and Access(CLASS*; ESPC*)
GOES-R Ground Segment Functional Elements
MissionManagement
Enterprise Management
GOES-R Re-broadcast
GOES East
GOES West
ProductGeneration Product
Distribution
8
GOES-R Program Status
• Spacecraft Contract Awarded
• Ground segment procurement source selection underway
• CONOPS baselined
• Level 1 and Level 2 Requirements Documents baselined
• Management Control Plan baselined
• Systems Engineering Processes established:
– Requirements Management
– Configuration Management
– Risk Management
• Instrument development well underway
9
GOES-R Instruments
Instrument Function Contractor StatusAdvanced Baseline Imager (ABI)
Primary Instrument: Provides imagery of the Earth’s surface, atmosphere and ground cover
ITT, Ft Wayne IN CDR completed, engineering unit in development
Geostationary Lightning Mapper (GLM)
Detects the frequency and location of lightning activity
Lockheed Martin Space Systems
Company, Palo Alto CA
System definition review completed, preliminary design started
Space Environmental In-Situ Suite (SEISS) Monitors the space environment
Assurance Technology Corporation, Carlisle MA
Preliminary design review (PDR) completed, component development underway
Extreme Ultra Violet / X-Ray Irradiance Sensor (EXIS)
Provides real time measurement of solar activity
Observes the sun’s emissions and provides early detection and location of flares
Laboratory for Atmospheric and Space Physics Boulder, CO
PDR completed, component development underway
Solar Ultra Violet Imager (SUVI)
Lockheed Martin Space Systems
Company, Palo Alto CA
PDR completed, component development underway
MagnetometerMeasures the magnitude and direction of the Earth’s magnetic field
Spacecraft Vendor To be procured as part of spacecraft contract
10
Partnership born from Reality
• The unique GOES-R partnership is a recognition of two basic realities:– GOES-R is the largest acquisition ($7.672B) ever undertaken at the
Department of Commerce. NOAA provides 100% of the funding • NOAA has considerable experience operating weather satellite systems, and • NOAA has extensive experience developing user products from satellite
data, yet• NOAA has no experience overseeing a system of this size and complexity
– NASA has the expertise and experience to procure the satellite systems, with time-tested processes that have proven successful
• GOES-R’s unique structure provides NOAA with greater management responsibility and oversight while leveraging NASA’s experience procuring satellite systems
This briefing describes the unique GOES-R partnership between NOAA and NASA and identifies challenges the dual agency management system has created and how we are dealing with them -combining apples and oranges to make juice!
11
GOES-R High Level Acquisition Organizational Relationships
Secretary of CommerceMilestone Decision Authority
Assistant Secretary for AdministrationAcquisition Executive
Under Secretaryfor Oceans and Atmosphere
Milestone Decision Authority (delegated from Secretary)
Deputy Under Secretaryfor Oceans and Atmosphere
PMC Chair
Assistant AdministratorDeputy Assistant Administrator
Deputy Assistant Administrator (Systems)Office of Satellite and Information Services
GOES-R System Program Director
Flight SegmentProject Manager
Ground SegmentProject Manager
GSFC CMC
12
GOES-R Acquisition Strategy Evolution
One SingleSystem Prime
GroundSegment
OriginalNov 2004
NOAA ApprovedDec 2006
TO
NOAA ContractSpace
Segment
NOAA ContractsNASA Contracts
Program System Engineering
NASA LeadNOAA ParticipationNASA processes
Independent Review
Summer 2006
13
NOAA/NASA Roles and Responsibilities Evolution
NOAANOAANOAANOAAGround Systems
NOAANOAANOAANOAASatellite Operations
NASANASA NASA(For GOES N – Boeing)NASALaunch services
Program/Project Office staffed with NOAA & NASA personnel
Program/Project Office staffed with NOAA & NASA personnel
NASA(NOAA Retains Resident Office)
NASA(NOAA Retains Resident Office)
Program Office Composition
NOAANASANASANASAContracting Officer
NOAA NESDIS AANASA GSFC
NASA GSFCDirector of Flight Programs
(None for GOES N -- Firm Fixed Price Contract with Boeing)
NASA GSFCDirector of Flight Programs
Fee Determining Official
NOAA DUS for Oceans and AtmosphereNASA GSFC
NASA HQ: Science Mission Directorate or equivalent
(Delegated to GSFC Code 400)
NASA HQ: Science Mission Directorate or equivalent
(Delegated to GSFC Code 400)
Source Selection Authority
NOAA or DOC(depending on DOC decision)
NOAA or DOC(depending on DOC decision)NASA GSFC or HQSNASA GSFC or HQS
Key Program Decisions (Milestones, Readiness Reviews)
GSFC CMC and NOAA PMCGSFC CMC and NOAA PMCGSFC PMC and NASAHQ’s PMC
GSFC PMC, NASA HQ’s PMC, NOAA PMCOversight
NOAANOAANOAANOAARequirements Authority
GOES-RFlight Project Ground Segment ProjectLegacy GOESLegacy POES Function
14
Co-located NOAA/NASA Program Office is key to Organization Structure
The GOES-R Program, including NOAA civil servants, NASA civil servants, and NOAA and NASA support contractors, is co-located at Goddard Space Flight Center, Building 6
• Better coordination through daily contact between all elements of the Program
• Provides easy access to GSFC experienced management for satellite procurement
• Unique integrated leadership arrangement possible due to co-location
15
Program Management Summary
System Program Director (SPD): NOAADeputy SPD: NOAA
Assistant SPD: NASA
Flight ProjectProject Manager: NASA
Deputy: NOAA
Ground Segment ProjectProject Manager: NOAA
Deputy: NASA
Program Systems Engineering Lead: NASA
Deputy: NOAA
NESDIS
GSFCCenter Management
Council
NOAA Program Management
Council
NOAA
Program ControlLead: NOAA
Ground Segment Project ContractsLead: NOAA
Program ContractsGround Lead: NOAAFlight Lead: NASA
Flight Project ContractsLead: NASA
GSFCCode 400
GOES-R Attorney Lead: DOC
Program ScientistLead: NOAA
Program Mission AssuranceLead: NASA
16
GOES-R Program System Engineering (PSE) – the Glue
Between the Projects•Program System Engineering (PSE) team is responsible for End-to-End systems integration, and planning, coordination, and adjudication of GOES-R Program System Engineering functions
•To accomplish this responsibility, the PSE team will implement system engineering functions and processes, tailored to the specific needs of the GOES-R Program.
Program Systems Engineering Team
•NOAA-NESDIS•GOES-R Program Office•Algorithm Working Group•User Community•GSFC AETD & Center Management
Ground Segment Project Systems
Engineering Team
Flight Project Systems
Engineering Team
17
Overarching Communications
• PSE Lead and Deputy are members of the Senior Management Team which directly reports to the System Program Director (SPD)
• Program System Engineering (PSE) Lead is coordinating and chairing coordination and planning meetings with the systems engineering team
– Weekly PSE team meeting– Weekly Program/Project SE coordination meeting– Monthly PSE Risk Board– Monthly Program risk board– Weekly Program Engineering Change Review Board (ECRB)
• Systems engineering team members also participate in the following project meetings:
– Flight and Ground Project ECRBs– Project Risk Management Boards– Flight Instrument Design reviews and technical meetings– Ground system design and peer reviews– Weekly staff meetings, systems engineering meetings, steering group
meetings
18
Program Standard Processes
• All procured systems:– Will provide traceability of Requirements Verification via DOORS tool in
DOORS database– Verification matrices to be provided by vendor, approved by Projects and
Program– Contractors’ proposed test plans to be based on Verification Matrices and
Government-specified schedules– Flight/Ground Projects will oversee factory and site testing, – including intra-segment interfaces– PSE will maintain visibility in all system activities and interfaces
• Program-wide consistent Configuration Management (CM) Plans and coordinated change review processes
• Program-wide Risk Management database with multiple levels for subsystems, projects and program
• Program-wide Schedule management system will be developed and maintained• Working groups for Program-wide efforts
– Will include PSE, Flight and Ground Projects, and Contractors as required
19
Tailoring of SE to GOES-R
The Classic top-down System Engineering Process must be tailored to address the GOES-R Program
• Because of the Long Lead time required for development of a GEO Imager, the ABI instrument and other instruments’ designs were started well in advance of the spacecraft procurement. Some “bottom up” flow of requirements and capabilities must be carefully woven into the overall system to minimize cost, schedule, and performance impacts.
• Review and approval processes must accurately reflect NOAA/NASA partnership strengths and responsibilities
• Continuity with current GOES operations and data must remain as a top priority
• Decision to acquire two prime contractors, one for Ground and one for Space brings forth some new risk considerations like coordination of interfaces, synchronization of schedules, etc.
20
Critical Inter-Project Dependencies being
monitored by PSE
• Delivery of the Level 1b processing algorithms from the five instrument vendors for subsequent delivery to the Ground Projectcontractor for operational implementation.
• Delivery of telemetry and command design information from the satellite contractor to the ground contractor to support the design of that portion of the ground segment
• Delivery of satellite simulators (from the spacecraft contractor) for use by the ground segment contractor for development and testing.
• Readiness of the telemetry and command portion of the ground segment sufficient to support compatibility testing during the S/C Thermal-vacuum testing.
• Availability of the satellite to conduct end-to-end tests with the ground segment.
21
Processes Affected by Partnership
1. Program/Project Management2. Technical and Management Reviews3. Program Status Reporting4. Approval to Enter Acquisition and Operations Phase5. Configuration Control6. Risk Management7. Schedule Management8. Requirements Management9. System Integration10. System Acceptance
More players require more buy-in
22
Challenge #1 –Defining the Partnership
Defining the GOES-R partnership explicitly required defining the responsibilities of each agency, the program office and each project
NASA and NOAA have fundamentally different cultures: • NASA focuses more on proven processes while NOAA focuses more
on agility/flexibility to support users• NASA focuses more on flight hardware with high reliability for first
time success while NOAA focuses more on evolving science/operational product applications that can change over time.
• The different cultures lead to– different sets of priorities – different concepts of what represent success.
• Having the difference in cultures primarily located across the important boundary that is Flight and Ground enhances the challenge.
Required significant discussion, review, and revision until all parties were in agreement
23
MOU and MCP Define Agency Roles and Responsibilities
• Memorandum of Understanding (MOU) established GOES-R as a NOAA led program with two projects–signed June 15, 2007– Spacecraft: NASA contract– Ground Segment: NOAA Contract– Recognized the strengths of each agency
• Management Control Plan written to implement MOU– Requirements mirror NPR 7120 as much as possible– Deviations from NPR 7120 when similar NOAA process is being
used instead • i.e. NOAA independent cost estimating processes being
utilized
24
On a Dual Agency Program, Documents Require Unique
Approvals• Memorandum of Understanding
(MOU) between NOAA and NASA created GOES-R as a co-located Program Office with Flight and Ground Segment Projects. Approved by:– NOAA Deputy Under Secretary– NASA Associate Administrator
• Management Control Plan (MCP) written to implement MOU. Approved by:– NESDIS Director– GSFC Director
25
Challenge #2 –The Review Process
The GOES-R Review Process is defined in the System Review Plan, coordinated with both agencies – based on NASA standards and processes– NASA and NOAA independent experts on review
panels with joint chairs– NASA and NOAA approvals for program milestones
PSE worked with Goddard’s Systems Review Office to develop a plan that met NASA requirements but tailored to GOES-R
26
Review ProcessPDRR
C-GRRMRRC-GRRC-GRR
System Assembly, Integration & Test
Final Design & Fabrication
Launch / Operations Disposal
PER-BConceptDesign(NESDIS)
PER-CProject Baseline
(NOAA DUS)
PER-DIntegrationReadiness
(NESDIS)
PER-ELaunch
Readiness(NESDIS)
PER-FEnd ofMission(NESDIS)
KDPI
(DOC)KDP
IIProgram Baseline
(NOAA)
PGR-IVMission
Readiness Board
(NOAA DUS)
PGR-VHandover
Review(NESDIS)
PGR-IIIMission
IntegrationReadiness(NOAA DUS)
SDRSCR PDR
CITRB
ASM
SMSR
I-PSR
SIR
C-GRR
PSR LRR
GSFC
NESDIS
PLAR
I-PSR
MORFOR
FRR
CDR ORRSRR
Acquisition and Operations
PMC PMC
C-GRRC-GRR
KDPIA
(NOAA)
27
Challenge #3–The Reporting Process
Multiple levels of both agencies require periodic status reports– Challenge to create reporting templates such that
tailoring for each report is minimizedThreshold reporting required at multiple levels
These requirements are documented in the Management Control Plan.
28
Status Reporting Requirements
Senate: oAppropriations CommitteeoCommittee on Commerce, Science, and Transportation House of Representatives:Appropriations Committee & Committee on Science and Technology
Annually with President’s Budget,Report to Congress
NOAA/NASA Findings reported to DOCAnnualReview of Award Fee Effectiveness
Project Manager, SPD attendsMonthlyProject Monthly Status Review
NESDIS AAMonthlyNESDIS Monthly Status
NESDIS AA, GSFC Deputy Center Director, TechnicalMonthlyGSFC/NESDIS Tag Up
OMBMonthlyProgram Monthly Status Report
NESDIS DAASWeeklyNESDIS Weekly Program Tag Up
NESDIS/GSFC designatedAs requiredStanding Review Board
DUS/NESDIS designatedAs requiredNOAA/NESDIS Independent Review Team
NOAA Administrator / NASA AdministratorYearly or as necessaryNOAA and NASA Administrator meeting to assess status and progress
DOC CFO/ASAQuarterlyDOC Quarterly Program Review
GSFC Director of Flight ProjectsMonthlyNASA GSFC Pre-MSR
Deputy Center Director / GSFC Center Management Council (CMC)Monthly NASA GSFC Monthly Status Review (MSR)
DUS/NOAA PMCMonthlyNOAA Program Management Council (PMC)
SPD or designeeMonthlyGOES-R Monthly Program Review
PSE or designeeAs requiredGOES-R Engineering Review Board
DSPDMonthlyGOES-R Personnel Management Group
SPD or designeeWeeklySenior Management Team (SMT) Weekly
ReviewerDates ScheduledType of Reporting
Regular Reporting
29
Threshold Reporting Requirements
Threshold Reporting
Required Report to:ThresholdType of Reporting
DOC ASA/CFO5% over cost and
schedule of any program element
Department of Commerce Threshold on cost and schedule
DUS, NESDIS AA10% over cost as determined by SPD
NOAA Cost Threshold reporting requirement to Deputy Under Secretary
Under Secretary for Oceans and Atmosphere
20% over cost as determined by SPD
Congressional Cost Threshold reporting requirement to Under Secretary
30
Challenge #4 –Approval to Enter Acquisition and
Operations (A&O) Phase
Approval to Enter A&O Phase, which in our case included permission to spend our money on our development contracts, was a challenge due to:
• Many layers of review and approval• Independent Review Team recommendations that drove
us to a conservative 80 percent budget solution• Challenges reconciling NASA and NOAA independent
cost estimates
GOES-R received formal approval from the Department of Commerce to enter the A&O Phase in December, 2007
31
Challenge #5–Configuration Control
Dual-agency configuration control is a challenge on GOES-R, particularly for the documents “owned” by NOAA, i.e. the Level 1 Requirements and Management Control Plan:
• All elements of the Program as well as both Agencies need to be a part of the review cycle
• Must carefully control requirements yet still allow for necessary changes
Required significant discussion, review, and revision until all parties were in agreement – still being refined
32
Configuration ManagementN
OSC
NO
SCPM
C/ D
US
PMC
/ DU
S
SPD
SPD
NOSC staff Prepares necessary documentation
for NOSC review/Approval
Mod CCR Review(SPD/PMs/PSE/Prog Scientist (GORWG Chair))
NOAAOwnedDoc?
SPD approvesFor release?
SPD approvesFor release?
SPD approvesFor release?
NOSCMemberReview
Changes Required?
PMC staff Prepares necessary documentation
for PMC review/Approval
PMCMemberReview
Changes Required?
NOSCChairs
sign
PMCBriefedDUS signs
CCB Chairapproves
CM makes changes
YES
NO
YES
CM makes changes
CM makes changes
NO
YES
NO
YES
NO
YES
NO
YES
NO
33
Challenge #6 –Risk Management
The GOES-R Risk Management Process follows NASA and DOD requirements as closely as possible while maintaining consistency with other NOAA programs (NPOESS, etc)
• Characteristics of Integrated Risk Approach– Multi-layer approach for risk management that allows cognizant projects,
segment organizations, contractors, teams, groups, and organizations to retain authority and control over risks for their areas of responsibility while supporting existing management and decision making processes.
– Program risks address technical, cost, and schedule impacts related to the:• Successful design, development, fabrication/manufacture, integration, tests,
deployment and operations of the GOES-R system;• Performance and reliability of the GOES-R Series End-to-End System.• Activities and resources including staff, contractors, and facilities, at NOAA
and NASA, at other government agencies, developer organizations – Comprehensive approach allows early identification of potential risks
Risk Management Plan baselined. Required discussion with other NOAA programs to ensure consistency
34
Integrated Risk Management Across the GOES-R Program
ObservatorySpacecraft Vendor RMB
Systems Eng. & Integration
Subsystem RWGs
InstrumentsInstrumentVendorsRMBs
End‐to‐End Verif. & Valid.
Elements Integration
End Product Perf.
Systems Engineering
Working Groups
Segment Devel.
IDTs/IPTs RWGs
Affiliated Orgs.
AWG, OSD, OSDPD, etc.
Program IntegrationRMB
Flight ProjectRMB
Ground Segment ProjectRMB
ProgramRMB
Mission Assurance
ProgramScientist
Product Development & Vendors
Projects & Integration Program
Reporting & CoordinationPrioritization &ResourcesRisk‐Informed Decision Making
35
Challenge #7 –Schedule Management
Having 2 projects each with multiple contractors adds complexity to the problem of developing and maintaining an integrated Program Schedule– Project Schedulers are integrating at Project Level– Program scheduler hired to combine project schedules at
Program Level – at this point a manual effort– PSE responsible for analyzing schedules for technical
inconsistencies and working out conflicts– Program Schedule Management Plan being written
Developing an initial Program Schedule required significant discussion, review, and revision until all parties were in agreement. GOES-R is still
developing its full integrated Program Schedule
36
GOES-R Program Integrated Master Schedule
FY07 FY08 FY09 FY10 FY11 FY12 FY13 FY14 FY15 FY16Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1
Fiscal Year
Program / System
Testing / Dependencies
Launch Vehicle
Spacecraft*
Instrument - ABI (ITT)
Instrument - SEISS (ATC)
Instrument - EXIS (LASP)
Instrument - SUVI (LMSSC)
Instrument - GLM
Ground Segment
L1 Algorithms - Flight
L2+ Algorithms - AWG Baseline / Option 2
Facilities / Antennas Communications
Other GFP and I/Fs
CLASS Upgrades
12/07
KDP I
10/08
Det. of Readinessto Congress
5/09
KDPI IA
12/09
SDR
9/1011/10
PDR KDP II
9/11
CDR
7/12
7/12 8/12
8/12
MOR SIR
6/14 11/14 12/14
FRR LaunchORR MRR Need Baseline
4/15
12/12
1
3/13
2
6/13
3
1/14
--------- End-to-End Tests ---------4
1/15
6/11
Begin LSTOCompetition
6/12
ATP
10/14
Pre-VOS
12/08
CA
4/09
SDR
4/10
PDR
4/11
CDR
4/12
Int.Begins
8/12
BusComp.
S/C I&T 1/13
Array/Yoke Complete
4/13
PER
2/14
PSR
8/14
Launch Vehicle Processing
2/07
CDR
5/09
PTM TRRPTM DeltaRe'q FIN CDR
3/10 4/10 7/11
Early FIN
6/12
Req'dFIN
12/08
PDR
5/10
CDR
12/11
Early FIN
6/12
Req'dFIN
3/07
SDR CA
11/08
PDR
11/09
CDR
Early FIN
2/12 6/12
Req'dFIN
CA
10/08
PDR
12/09
CDR
7/12
Early FIN
10/12
Req'd FIN
CA
7/08
SDR
1/091/09 PDR
3/09 PDR
9/09
CDR
7/10
PTM
4/12
Early FIN
6/12
Req'dFIN
3/09 6/09
CA
12/09
SDR
9/10
PDR
9/11
CDR
8/12
Release MM
3/13
Release 1
9/13
Release 2
12/14
LaunchReadiness
Launch Vehicle Processing
2/10
Initial Deliveries
11/10
12/10 Final Deliveries
4/12
3/07
Start
9/08
Draft
9/09
Draft
80% Delivery 100% Delivery
9/10
80% Delivery
Baseline
9/11
100% DeliveryOption 2
RBU Site Selection 10/08
RBU White PaperSubmitted to OCAO 11/08
3/09
10/10
CA 3/12
Facilities Complete
12/13
AntennasDelivered
12/13
CommunicationsComplete
1/08
Start
10/09
CA
5/12Complete
3/07
Start
6/09
SDR
12/12Ready
Notes:
ATP: Authority To ProceedCA: Contract AwardCDR: Critical Design ReviewDOT Data Operations TestFRR: Flight Readiness ReviewMRR: Mission Readiness ReviewMOR: Mission Operations ReviewMOT Mission Operations TestLSTO: Launch Services Task OrderPDR: Preliminary Design ReviewPER: Pre-Environmental ReviewPre-VOS: Pre-Vehicle On StandPSR: Pre-Ship ReviewPTM: ProtoType ModelSDR: System Definition ReviewTRR: Test Readiness Review
*Actual dates pending IBR
Time Now
As of December 31, 2008
Development Construction Integration & Testing Margin
CurrentMilestone
CompletedMilestone
MilestoneCompleted During Current Period
Major DeliverableMilestone
MilestoneSlip
FY09 ControlMilestone
37
Challenge #8 –Requirements Management
Defining GOES-R requirements was a dual-agency challenge: GOES-R Requirements have come from both agencies– Stakeholder requirements from NOAA
• Science Product requirements• Operations requirements• User interface requirements• Continuity requirements
– Process requirements from NASA• Spacecraft and Instrument design, development, integration
and test requirements• Requirements from NOAA and NASA combined into single set of
requirements documents
ALL program elements using DOORS are part of a unified, multi-level requirements database.
38
Requirements Document Hierarchy and Approval Authority
GOES-R Project ManagersGPO GOES-R Projects
Project Level Interface
Documents and Functional
Specifications
Level IIIa
GOES-R SPDGPOGOES-R ProjectsGOES-R Project Plans Level III
GOES-R SPDGPOGORWGGPO
Mission Requirements
DocumentLevel IIa
NESDIS AA, NASA/GSFC
Center Director
NESDIS AA/DAANASA/GSFC PMCGPO
GOES-RManagement Control Plan
Level II
NOAA DUSNOSC,
NOAA PMC,NESDIS AA/DAA
Final: GOES-R Program Office (GPO)
GOES-R Level I Requirements Documents
Level I
NOAA Executive
Council (NEC)NOSCNOAA Observing
Systems Council (NOSC)
Consolidated Observational Requirements List (CORL)
NOAA Observing
Systems Architecture
(NOSA)
Approving Body
Reviewing BodyDocument Custodian & Control Process
Baseline Document
Requirement Level
39
Challenge #9 –System Integration
Defining the responsibilities and full process for system integration is a challenge in a dual-agency program:
• PSE is responsible for the overall integration of the GOES-R System• The Flight Project is responsible for the integration of the
instruments, spacecraft, launch vehicle, and operation of the spacecraft
• The Ground Project is responsible for the complete integration of the ground system into operations, and all interfaces to the users
• Integration is a build-up process, from subsystems to systems to projects and then to program
Defining System Integration is an on-going PSE challenge. Previous GOES process is the starting point, modified for unique GOES-R
structure.
40
Challenge #10 –System Acceptance
Defining the full process for System Acceptance is a unique challenge:
• Contractors hand over to their projects for Government Acceptance
• Program is integrated then Program Director hands integrated system over to NOAA/Operations.
• Handover will be in stages – product validation will require longer time than spacecraft operations
Defining System Acceptance is an ongoing PSE challenge.
41
Summary
• The Geostationary Observational Environment Satellites (GOES)-R is a $7 billion system of satellites, sensors and data processing and distribution systems being developed by a unique dual-agency partnership.
• This brief discussed how the partnership was formed, the unique challenges it faces and how Program Systems Engineering Group is the glue that integrates the Program as a whole.
42
The World Needs GOES
. . . And a joint NOAA/NASA partnership is the best way to deliver it
43
Questions?
