14.03.2015 Views

GOES-R MANAGEMENT CONTROL PLAN (MCP)

GOES-R MANAGEMENT CONTROL PLAN (MCP)

GOES-R MANAGEMENT CONTROL PLAN (MCP)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

System integration is defined as the integration of flight and ground systems for observatory level end to<br />

end testing. Interface milestones are outlined in the Program Master Schedule.<br />

5.2.3 Programmatic Thresholds<br />

The <strong>GOES</strong>-R Risk Management Plan outlines specific thresholds for cost, schedule, and technical risk<br />

reporting.<br />

Thresholds for the cost impact for a particular segment are based upon projected percentage overrun for<br />

that segment in combination with the availability of prudent cost reserves. Total cost risk is determined<br />

by a combination of impact and probability of occurrence.<br />

At the project level, <strong>GOES</strong>-R follows the Goddard Space Flight Center guidelines for healthy<br />

contingency (20% contingency on unliened cost-to-go). This metric is tracked monthly by the program<br />

office. Similarly, schedule risk is based on the critical path and schedule contingency health.<br />

Risk thresholds are designed to communicate cost and schedule risk and mitigations far in advance of<br />

impacting budget and schedule control thresholds outlined in the Level I Requirements.<br />

5.2.4 Technical Thresholds<br />

The Program Systems Engineering Lead will identify system level metrics to monitor and track. Each<br />

Project Systems Engineering Lead is responsible for identifying and managing the mission resources<br />

allocated for their respective system and subsystem segment. Each Project Systems Engineering Lead<br />

and Program Systems Engineering Lead will identify resources that need to be monitored.<br />

The Program Systems Engineering Lead defines acceptable resource margins and establishes a margin<br />

management philosophy based on various stages of the mission lifecycle. As the system architecture<br />

matures, the precision of the resource estimates will improve, as will the method of estimating the<br />

resources requirement. Resource margins shall be met in accordance with GSFC-STD-1000. Both the<br />

Flight Project and Ground Segment Project will track technical resource margins at their level and report<br />

margin status to the program.<br />

5.3 Oversight and Reporting<br />

The major reporting bodies for <strong>GOES</strong>-R are summarized in the figure below:<br />

Page 47 of 75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!