Program Management & Control
One schedule, one set of numbers, and a management rhythm that surfaces a problem while there is still time to solve it.
Policy Statement
Monarch Space Systems, Inc. manages federal work against a single set of numbers. The schedule the customer sees is the schedule the team works to, the cost reported externally reconciles to the accounting system that produced it, and a variance is reported when it is detected rather than when it is unavoidable. Program control exists so that a problem is visible while it is still small enough to solve, and so that a customer is never surprised by information the institution already had.
- One integrated schedule per program. Side schedules that contradict the baseline are not tolerated.
- The performance measurement baseline changes only through a controlled change process with documented authorization.
- Internal and external reporting derive from the same source data, reconciled before either is issued.
- A variance beyond threshold produces a written analysis of cause, impact, and corrective action, with an owner and a date.
- Estimates at completion are updated from current performance rather than held at the number that was promised.
- Bad news travels at the same speed as good news, and reaches the customer before it reaches the customer's leadership from elsewhere.
Program Architecture
Four domains, one program. Each has a written scope, an accountable owner, and a review cadence.
Scheduling and the Integrated Master Schedule
One schedule, logically linked, resource-loaded where it matters, with a critical path that is calculated rather than declared. Margin is held visibly and consumed by decision.
Read the detailPerformance Measurement and Earned Value
Work is broken down to a level where progress is objectively measurable, baselined, and measured against that baseline. A variance produces analysis and corrective action, not a narrative.
Read the detailDeliverables and Data Management
Contract deliverables are tracked from requirement to submission to customer disposition. Nothing is late because nobody was watching the list.
Read the detailProgram Reviews and Customer Reporting
A fixed management rhythm: internal reviews that surface problems, monthly reporting that reconciles to the same data internally and externally, and escalation that reaches the customer while options still exist.
Read the detailControl Authority and Accountability
Chief Executive
Sets the reporting standard, approves baseline changes above defined thresholds, and is accountable for the accuracy of what the institution tells its customers.
Program Manager
Owns the integrated baseline, the management rhythm, variance response, deliverable performance, and the customer relationship on execution matters.
Program Control Function
Maintains the work breakdown structure, schedule, performance measurement data, and reporting products, independent of the pressure to make a period look better than it was.
Control Account Managers
Own scope, budget, and schedule for their accounts; take credit only for work actually accomplished; and explain their own variances.
Chief Engineer / Technical Authority
Provides the technical assessment that turns a schedule status into an honest forecast, particularly where remaining work is uncertain.
Finance & Contracts Function
Reconciles reported cost to the accounting records, manages funding and limitation-of-funds notification, and controls contractual deliverable obligations.
Standards We Align To
The program is written against the regulations, agency handbooks, and consensus standards a NASA contracting officer, a program analyst, or a prime's program management office expects to see. Alignment is stated as alignment; no system validation or performance result is claimed.
EIA-748 — Earned Value Management Systems
The 32 guidelines used as the structural reference for performance measurement
DFARS 252.234-7002 / 252.242-7005
Earned value management system criteria and business system administration expectations
NPR 7120.5 — NASA Space Flight Program and Project Management
Life-cycle phases, key decision points, and program control expectations
NASA Schedule Management Handbook
Agency practice for integrated master schedule construction, health, and analysis
NASA Cost Estimating Handbook
Estimate-at-completion methodology and joint cost and schedule confidence practice
GAO Schedule Assessment Guide (GAO-16-89G)
The ten best practices used to assess schedule quality and credibility
GAO Cost Estimating and Assessment Guide
Characteristics of a reliable estimate and its maintenance through execution
FAR 52.232-22 / 52.232-20 — Limitation of Funds and Cost
Notification obligations when funding or estimated cost thresholds are approached
NASA Data Requirements Descriptions (DRD) practice
Contract deliverable definition, format, and submission control
PMI Practice Standards for WBS and Scheduling
Consensus practice for decomposition, network logic, and schedule maintenance
Alignment Disclosure
Monarch Space Systems describes its program planning, scheduling, performance measurement, and reporting practices as aligned with the cited federal regulations, agency directives, and consensus standards. Alignment is not a determination. The institution does not claim a validated or government-accepted earned value management system, a compliant system determination under DFARS 252.234-7002, a scheduling assessment result, or any specific contract cost or schedule performance. Program schedules, cost data, and reports are contract-controlled and are not published.
Policy documentation, procedures, and control descriptions are available to customers and prospective teammates through the confidential engagement pathway or by request through institutional contact.
Questions We Are Asked
Does Monarch Space Systems have a validated earned value management system?
No such determination is claimed. Performance measurement practices are structured against the EIA-748 guidelines and the DFARS business system criteria, and are applied proportionately to contract size and type. Where an acquisition requires a system review or an integrated baseline review, the institution supports that review rather than asserting a result in advance.
Is full earned value applied to every contract?
No, and applying it indiscriminately would be a cost the customer should not pay for. Contract type, dollar value, and risk determine the level: milestone-based progress measurement on small firm-fixed-price work, and the full EIA-748 structure where the contract requires it or the risk justifies it. The scaling rule is written down rather than decided case by case.
How is an estimate at completion kept honest?
By deriving it from performance rather than from intent. The estimate is rebuilt from actual cost incurred, an assessment of remaining work by the people who will do it, and efficiency observed to date. Where the resulting estimate exceeds the target, it is reported as it stands. A forecast that returns to plan without a change in the plan is treated as a finding, not a recovery.
When does the customer hear about a problem?
When the institution knows about it. Threshold breaches, funding exposure under the limitation-of-funds clauses, deliverable slips, and technical issues with cost or schedule consequence are communicated on discovery through the contracting officer and the technical point of contact, with the analysis and the proposed response presented together where possible.
Are program schedules and cost data published?
No. Schedules, cost data, and performance reports are contract-controlled and provided through the channels the acquisition defines. What is published is the discipline: how a baseline is built, how progress is measured, how variance is answered, and how quickly the customer hears.
Why publish program control practice at all?
Because the management volume of a proposal is where credibility is won or lost, and a reviewer reads it looking for evidence of a real system rather than an intention. A prime evaluating a subcontractor and an acquirer evaluating an operating discipline are looking for the same thing.
Public References
Related Institutional Documentation
Program control connects to the cost management program, cost control and overrun prevention, mission assurance and systems engineering, program execution, the contract surge model, and contract transition and continuity.