RFP ANNEX B
NPOESS Sensor Payload and Algorithm Development
INTEGRATED MASTER PLAN (IMP) AND INTEGRATED MASTER SCHEDULE (IMS) INSTRUCTIONS
17 March 1997
THIS ANNEX, INCLUDING THE
COVER, CONSISTS OF 10 PAGES
THIS PAGE INTENTIONALLY BLANK
1.0 INTEGRATED PRODUCT DEVELOPMENT (IPD)
The Government is implementing the Integrated Product Development (IPD) approach for managing the NPOES program. The IPD approach provides the Offeror a product orientation to the management of his effort while providing the Government greater visibility into the proposed efforts. To achieve the product orientation of the IPD philosophy the Offeror structures an integrated management system to logically flow down requirements, through broad-level tasking within an event driven Integrated Master Plan (IMP). Two of the major features of the IPD approach are reviewed below.
The first major feature is an approach for planning the contract effort and preparing the contract documentation, see Figure 1. The Government's RFP provides the Offeror with the elements shown in the left column of the figure; i.e., Model Contract (Sections A - K plus attachments), Section L, Section M, Sensor Requirements Document (SRD), Statement of Objectives (SOO), Sensor Work Breakdown Structure (SWBS), Contract Data Requirements List (CDRL), and Contract Line Item Numbers (CLINs). The Offeror is also provided with the following annexes to help in preparing the proposal and contractual documents:
RFP Annex A Sensor Work Breakdown Structure (SWBS)/Dictionary
RFP Annex B Integrated Master Plan/Schedule (IMP/IMS) Instructions
RFP Annex C Statement of Objectives (SOO)
RFP Annex D Cross Reference Matrix
Based on the RFP requirements, the Offeror shall submit a proposal containing the items listed in the center column of the figure; i.e., a completed Model contract, Preliminary Contract WBS (CWBS), an Integrated Master Plan (IMP) and Schedule (IMS), a Cross Reference Matrix, Applicable Documents, CDRL, and CLINs in accordance with the detailed proposal preparation instructions found in this RFP. The definitive contract contains the elements shown in the right hand column of the figure. These Offeror generated documents will be used in the evaluation of the Sensor Payload and Algorithm Development Technical and Management Approaches.
The IMP expands on the CWBS and its dictionary, and establishes, by tasks (replaces the Statement of Work) and key events with selected narratives, the significant accomplishments and corresponding accomplishment criteria for both the products and processes necessary to accomplish the Sensor Payload and Algorithm Development effort. The IMS corresponds to the IMP and shows the schedule necessary to achieve each significant accomplishment. The IMP and IMS will be used by the Government and the contractor as the primary tool to track the program's technical and schedule status. The IMP and IMS will be used in evaluating the other portions of the proposal. The proposed CWBS, SOW, CDRL, and IMP become part of the contract.
Provided in RFP Provided in Proposal On Contract at Award
Figure 1 Procurement Approach
The second major feature of the IPD approach is the use of Integrated Product Teams (IPTs) in implementing the event-driven plan described above. This approach involves a teaming of Government and contractor functional disciplines to integrate and concurrently apply all necessary processes to produce effective and efficient products that satisfy mission requirements.
Under the IPD approach, the program is organized into IPTs that are both empowered and held responsible for the performance of their specific product. Each IPT is given the authority to manage their product and allocate resources within the team. The IPT members represent all functions that have a role in the performance of the product, e.g., engineers, manufacturing, buyers, contracts, inspection, and logisticians. IPT members work together to ensure that an efficient and effective product which satisfies the requirements is delivered. The term “product” under IPD also includes activities and processes as well as a specific product. The Offeror organizes IPTs for the proposed NPOESS sensor “products."
The IMP describes in detail how the work will be accomplished. The task section within the IMP (will take the place of a separate SOW) defines in detail what work is to be accomplished under this phase. The approved IMP is contractually binding and becomes Attachment 2 to the awarded contract. After contract award, the IMP cannot be changed except through normal contract change actions.
In contrast, the IMS is a contract deliverable item under the CDRL and is be updated "as required" (to maintain schedule flexibility) in accordance with the requirements of the Offeror’s CDRL.
A Sensor Work Breakdown Structure (SWBS) and associated dictionary have been provided in Annex A. The proposed CWBS shall be delivered as part of Volume V of the proposal. All tasks in the IMP shall be correlated to the CWBS proposed by the Offeror. There should be a correlation between the CWBS, IMP and the IPTs proposed for the Sensor Development. The IMP and IMS shall use the CWBS numbering system to facilitate contract requirements traceability.
The IMP shall clearly and concisely state the Offeror’s plans for how system engineering efforts will be conducted, how program tasks will be controlled and who, organizationally, will accomplish each task. It should identify key system engineering tasks, their interrelationships with program milestones, and the specific criteria that will be used to track and measure successful task completion. The IMP should provide top-to-bottom traceability from the SOO and SRD to Level 3 of the CWBS. The IMP shall describe: a) key tasks, events and accomplishments to be met by the Offeror under the contract; b) the associated criteria for the events and accomplishments; and c) the processes to be used in performing and reporting the tasks required by the contract. The IMP also groups the contract requirements so that these requirements may be worked by designated IPTs. The Offeror shall prepare the IMP in a format which clearly and succinctly conveys to the Government the information requested above. Contractor format is encouraged for this document.
(1) Task: A Task describes a work effort (to be performed by the Offeror) which singularly, or in combination with other Tasks, satisfies the NPOESS SOO and SRD. (The task section contains summary level tasks that read like a Statement of Work and replaces the effort descriptions usually contained in a Statement of Work). The IMP Tasks section shall contain references to the data items. Block 5 on the DD Form 1423-1, Contract Reference, shall contain the appropriate IMP reference.
(2) Event: An Event is defined to be the initiation/conclusion of an interval of major program activity. It shall represent a decision point related to the system maturity with continued system development. Events identified may be in the format of entry and exit events (e.g. Initiate PDR and Complete PDR) or use entry and exit criteria for each event. Other examples are: a) System Requirements Review, b) Functional Configuration Audit, or c) Low rate initial production.
The minimum Government required events for the Risk Reduction phase are a tailored System Requirements Review (SRR), a System Functional Review (SFR), and a Preliminary Design Reviews (PDR). If data from another sensor is required to meet a primary EDR threshold, these requirements (content, quality, and timeliness) shall be provided to the Government sixty (60) days prior to SRR. The tailored SRR shall be conducted to demonstrate the progress in converging on viable, traceable system requirements that are balanced with program cost, schedule, and risk. The SFR shall be conducted to review and verify the functional design baseline meets sensor requirements. The tailored PDR shall be conducted to confirm that the critical sensor design approach satisfies the functional baseline, risks are mitigated, and these elements are ready for detailed design implementation. The Offeror is encouraged to identify additional Key Events that best reflect the proposed program approach. For each IMP event, there shall be one or more entry or exit significant accomplishments (either entry or exit). The minimum Government required events for the Detailed Design and Fabrication phase is the Critical Design Review (CDR) and sensor unit deliveries.
(3) Significant Accomplishment: A Significant Accomplishment is a specified result substantiating an event that indicates the level of progress or maturity directly related to each product/process. Accomplishment shall be measurable. Significant accomplishments are interim or final critical efforts that must be completed prior to entering or exiting an event. Entry accomplishments reflect what must be complete to initiate an event. Exit accomplishments reflect what must be done in order for the event to be successfully closed and that NPOESS is ready for the next event. For each significant accomplishment, there shall be one or more accomplishment criteria. Significant accomplishments include:
a) A desired result at a specified event which indicates a level of design maturity, (or progress, directly related to each product and process
b) A discrete step in a process,
c) A description of interrelationship between different functional disciplines applied to the program (e.g., Maintainability, Manufacturing, and Reliability - the significant accomplishments of each related to Events by IMP Section).
Some examples of significant accomplishments which support a system Preliminary Design Review Event might be: a) Design implementation trade studies completed, b) System architectural update completed, c) System requirements allocation completed, d) All functional and physical interface requirements identified
(4) Accomplishment Criteria: A definitive measure or useful indicator substantiating the maturity level of an associated Significant Accomplishment. It is the completion of specified work that ensures closure of a specified Significant Accomplishment. Criteria shall be measurable (e.g., "Test plan complete and accepted by the spacecraft IPT" is a measurable criteria, whereas "Test plan 85% complete" is difficult to assess, if at all). Examples of accomplishment criteria are:
a) Architectural trade studies satisfy stated objectives
b) Allocated system requirements specified in segment performance requirement documents
c) Draft Interface Control Documents completed and time critical interfaces identified
d) Design risk assessment updated and risk reduction options
(5) Narratives: A collection of concise summaries providing visibility into the Offeror's key functional and management processes and procedures, how they relate to the integrated product development process, and an overview of the efforts required to implement them. The narratives shall address only the key elements of implementing or developing a process/procedure (i.e. what the process/procedure will be and how it will be implemented and tracked). The narratives facilitate contractor and Government understanding of and commitment to critical processes/procedures prior to contract award.
The narratives shall complement the respective significant accomplishment and accomplishment criteria sections by indicating where in the particular process the criteria apply. Each narratives subject area shall include a brief objective statement of desired results traceable to the SOO, the processes applicable to that objective, a listing of the proposed existing Government, industry, national and international specifications and standards to be used to achieve the objective. The Offeror shall clearly state which of these documents are compliance and which are reference and which of these will be tailored. Compliance documents are contractually binding, while reference documents are for guidance only and are not contractually binding. However, company practices or procedures may only be listed as reference documents. The narratives shall be consistent with applicable technical and management approaches described in the Technical and Management Volumes of the proposal. The narratives section is not the forum for providing supporting information or rationale (i.e., why a particular approach has been taken). The minimum list of essential processes for which the Government requires narratives is listed below. However, the Offeror may discuss any additional areas that he feels are either critical or of a high risk to his approach.
Systems Engineering. Define the processes to be used for conducting requirements analyses, performing functional analyses, allocating performance requirements, synthesizing design solutions, and performing systems analysis and trade-off studies. Describe the methodologies that will be used in measuring progress, evaluating alternatives, selecting preferred alternatives, and documenting data and decisions. Include the following Environmental, Safety, and Health considerations as part of the systems engineering processes:
Environmental Compliance. Define the processes to be used for integrating environmental protection considerations into the overall systems engineering process. Include the procedures for ensuring compliance with existing and potentially new environmental regulations. Describe the methodology and processes that will be used to: define potential environmental impacts, identify required permits and waivers, and identify and implement mitigative measures.
System Safety and Health. Define the processes to be used for implementing a system safety and health program that will ensure that all system safety and health engineering requirements are identified and factored into the design of the NPOESS sensors packages through system engineering, integrated risk management, and life cycle cost analyses, within the regulatory framework.
Hazardous Materials Management. Define the processes to be used for identifying, justifying, minimizing, eliminating, and controlling hazardous materials for the NPOESS sensors, system components, and associated support items. Describe the screening process and methodology for identifying mitigation measures or alternatives for usage of Class II Ozone Depleting Substances, EPA-17 chemicals, and EPCRA Section 313 chemicals. Include all potential pollution sources. Describe how information regarding the use and control of hazardous materials will be provided to the government, so they can fulfill their requirement to ensure the program is consistent with federal, state, local laws and regulations, Executive Orders, policy directives, and international treaties and agreements.
Software Engineering. Define the software development life cycle model to be used for the NPOESS software. Describe the technical and management processes to be used to produce high quality, cost effective software products. Address the processes used to perform the product-specific software development activities and the integral processes that occur throughout the software development life cycle. Describe the relationship between the software development processes and other processes described elsewhere in the IMP narratives. Describe how software development fits in your overall systems engineering process.
Risk Management. Define the processes to be used for risk management. Include in the description how the risk management process fits in with the overall systems engineering process. Describe the processes for identifying, analyzing, prioritizing, obtaining government acceptance, reducing, and monitoring the potential technical, cost, and schedule risk drivers and their interdependence. Address the integration of software into the risk management program.
Design Considerations. Define the processes to be used for developing design criteria and special test requirements for moving mechanical assemblies, explosive ordnance devices, self-locking connections, separable fluid fittings, honeycomb sandwich structures, composite structures and structural bonded joints, and pressurized subsystems if any of these devices will be used in your design approach. Describe the technical approaches to be used for establishing design allowables, conducting dynamic loads analyses, evaluating structural integrity, and determining test plan requirements for the sensor, its subsystems, and component structures. Define the processes to be used for developing design criteria for lightning protection, prevention of electrical overload, and damaging electrical discharge of the NPOESS payload. The SMC Engineering Practices Handbook (formerly the Commander's Policies) has been shown to improve system reliability. If the Offeror chooses to use the Handbook, describe how the Handbook ties in with these processes.
Test and Evaluation. Describe what specs and standards will be used to protoqualify and acceptance test the sensor's components and how, if used, the SMC Engineering Practices Handbook ties in with this. Define the processes to be used for demonstrating and projecting sensor performance, effectiveness, and suitability throughout the program life cycle. Describe the approach for providing Government insight into test planning, execution, and reporting. Describe proposed Measures of Effectiveness (MOEs). Identify test resources planned for use during the Detailed Design and Fabrication phase. Describe what procedures will be used during initial and ongoing demonstrations to validate analytical predictions of EDR performance.
Electromagnetic Compatibility. Define the processes to be used in conducting an overall NPOESS electromagnetic effects program designed to control electromagnetic emission and susceptibility characteristics of electronic, electrical, and electromechanical systems, subsystems, and components.
Contamination. Define the processes that will be used in conducting a contamination control program to deal with environmental control of clean rooms, work stations, sensor suite cleanliness levels and general contamination control during all phases of the hardware's lifetime from initial build, through in-orbit end of life. Describe methods for controlling contaminants and verifying that they have been prevented or abated, such that all hardware elements will meet performance requirements throughout the hardware's lifetime. Specifically address parts, materials, sensor, integration and test, and orbital operational contamination control processes required and levels of outgassing or particulate levels required to meet the EDR requirements. Bake-out of components, such as wiring harnesses and thermal blankets, must be considered. Allowable contamination levels are either the maximum that will ensure that the sensor suite will meet performance requirements and/or those that are necessary to meet mission contamination control considerations, which ever is the more stringent.
Calibration. Define the process that will be used to calibrate the sensor suite and its' internal/external components. Describe the proposed approach for component level evaluations, calibration at the factory, during integration and on-orbit during the operational life of the instrument. Discuss standards to be used, target stability required, and the processing (system) that will be employed to demonstrate that performance to specification is obtained and maintained. The range of temperatures over which component/integrated instrument performance is to be evaluated should also be defined. Procedures for monitoring component performance during calibration procedures shall be described, as should specific environmental parameters associated with each of the tests and any required analyses. The procedure should contain details of components such as instrumentation monitoring, facility control sequences, test article functions, test parameters, quality control check points, pass / fail criteria, data collection and reporting requirements.
Reliability. Define the processes to be used for conducting a sensor reliability program. Data sources, modeling techniques, tools, processes (internal procedures or industry or military standards) intended to be used shall be discussed. Describe how the reliability program is used within the systems engineering processes to influence the design of all components and their integration. Specifically, address the integration of software into the NPOESS reliability program.
Quality Assurance. Define the processes to be used in conducting the quality assurance program for sensor hardware and software during design, development, manufacturing, and test. Identify processes and the approach for hardware and software quality assurance that will contribute to significant risk reduction and cost reduction during the fabrication phase.
Data Management. Define the processes to be used by which all program data (both technical and cost data) will be developed, maintained made available to the Government electronically..
Integrated Logistics Support (ILS). Address ILS planning and functions. Define the processes to be used for identifying sensor supportability design cost drivers and high risk areas. Describe the logistics support analysis approach and how that process will be used in developing supportable sensors that will be interoperable with standard Air Force and NOAA Infrastructure.
Program Protection. Define the processes to be used for supporting the Government in help developing the Single Acquisition Protection Plan (SAPP)--which includes a System Operations Protection Guide, System Protection Guide, Risk Analysis, a Computer Security Plan and a Certification and Accreditation Plan. A System Protection Guide defines the System Security Engineering Program, technology assessment and control, and management and implementation approach for SSE in the acquisition phase. These protection guides and plans are designed to protect critical program features, control technologies, provide for safe and secure computing, and build security into the final products. Protections are to be provided for facilities, data, functions, hardware, software, and valued assets. These protection guides and plans address the processes to be used for conducting ongoing security vulnerability analyses, and implementing system protections to minimize security risks to the program. Due to the international aspect of the NPOESS program, it is essential that there be strict adherence to DOC and Department of State regulations as well as DoD regulations in the formulation of any protection plan.
In addition, the following areas are of interest to the Government at this time only to the extent that the Offeror has these necessary processes in place and that they can be executed at the appropriate time in the future phase(s) of the program. Offeror shall state if the following processes are in place, documented and proven. If not, state how and when you plan to implement, document and prove out these processes and be ready to implement them in the future phase(s) of the program. The Offeror shall add to the list any additional areas that he feels are either critical or of a high risk to his approach.
Maintainability
Manufacturing and Producibility
System Security Engineering
Quality Control
Configuration Management
In support of the IMP, the IMS provides a schedule for all the events, significant accomplishments, and accomplishment criteria described in the IMP. The IMS also outlines the detailed tasks and the corresponding calendar schedules (dates) necessary to show how each significant accomplishment will be achieved. All tasks outlined in the IMS should be related to specific IMP accomplishments.
The IMP and the IMS employ a single numbering system based on the Contract Work Breakdown Structure (CWBS), which is also the cornerstone of the Earned Value Management Systems of both the Government and its contractors. The single numbering system provides traceability between the Significant Accomplishments and Accomplishment Criteria (IMP) and the Detailed Tasks (IMS), and through the Sensor Specification to the IMP Taskings.
The Offeror shall provide a top level IMS in Vol II, Appendix A to their proposal submittal. The more detailed levels of the IMS, as well as updates, shall be maintained and made available to the government during contract performance upon request. The IMS is intended as a tool for day to day tracking of the program/project that rolls up to increasingly higher summary levels. The IMS is an integrated and networked multi-layered schedule of program/project tasks. The IMS identifies all IMP tasks, events, accomplishment, and criteria and the expected dates of each. For all significant activities, events, and milestones provide a task number, task name, duration, predecessor tasks, start date and finish date. Illustrate the proper interdependencies of all activities, events and milestones. Provide the ground rules and assumptions used in estimating the task duration shown in the schedule (e.g., historical data, experience on similar efforts, vendor schedules, number of work days per week, number of shifts, company holidays, etc.). Define the program’s critical path for the period of performance of this contract, and provide supporting narrative that explains the critical path and any unusual program aspects. Any anticipated Government support must be identified.
Identify the proposed schedule management system and how it will be used to control and manage the program schedule. The Offeror shall provide a resource loaded Gantt chart for the identified risk areas identified. The contractor may expand this list to include any additional moderate to high risk areas associated with the proposed concept. The Offeror shall include a separate chart(s) for critical subcontract efforts. These resource loaded schedules shall be consistent with the Offeror's risk mitigation plan. For each of these risk areas, the Offeror shall provide minimum and maximum durations for the summary level activity/WBS. The resource loading shall be represented by functional and skill level hours for labor and by material content. These hours shall be time phased by quarter with a recurring/non-recurring breakout for each quarter using the attached resource loaded Gantt chart.
The IMS network schedule shall contain a sufficient number of activities to provide a detailed understanding of the program This does not, however, preclude the Offeror from developing a more detailed schedule and then providing the government with a summarization of the more detailed schedule and his assessment of schedule risk. The Offeror shall provide a 3 1/2inch floppy disk containing the network schedule. The software and disk shall be compatible with Microsoft Project 4 format for PC computers. In addition to the files submitted on disk, the Offeror shall provide one hard copy of the schedule and Gantt charts for CWBS levels 1 3.