Solution Baselines
We use a systems engineering process to develop solution baselines and program architecture. We begin by bursting the Statement of Work (SOW) and creating a matrix that extracts the relevant information by identifying the ‘shalls,’ meetings, and reviews, timeframes and dates, and deliverables. Once complete, the resulting matrix provides the data we use to build the Integrated Master Plan and Integrated Master Schedule (IMP/IMS). We also highlight items to distinguish scope, Contract Data Requirements List (CDRL)/Data Accession List (DAL) deliverables, and reviews to be included in the schedule. This data is mapped to the Contractor Work Breakdown Structure (CWBS) and the Integrated Product Teams (IPTs).
Our program architecture approach integrates four key elements to preparing a comprehensive program architecture. It is important to note that your program architecture may take different forms depending on the program, end-customer requirements, and your organization’s processes:
After analyzing the solicitation documents and creating your matrix, begin developing the program architecture by documenting the program objectives and vision, identifying differentiators, defining the product structure, developing the organization structure, and identifying program-level events:
- 1.Program Architecture Mission: Program objectives and vision integrate the win strategy, capture plan, the concept of operations (CONOPS), budget forecasts, strategic plans, capabilities development document, and the technical baselines into the program architecture.
- 2.Program Products and Services: The product structure leverages the technical baseline, hardware, software, services, facilities, and equipment. The WBS, SOW, and specification tree are critical resources for defining the product structure.
- 3.Program Execution Organization: The organizational structure describes the functional organization of the project and is commonly defined through the IPT structure, including the staff, charter, and requirements of each team.
- 4.Program Summary Schedule: Program-level events (PLEs) include the Key Events, Significant Accomplishments, and Accomplishment Criteria. Also, the PLEs identify programmatic ground rules and assumptions, including critical processes and any required tailoring. The master phasing schedule is a good source of this information.
When complete, the program architecture becomes the roadmap for subsequent modules.
Our Books
The Essential Guide to Program Architecture
A structured guide to developing the program architecture early in the proposal process.