The ITAMP is an Offeror generated document, describing the taskings, core activities, and processes necessary to satisfy the System Performance Document (SPD) requirements and Low Cost Concept Validation (LCCV) Government List of Objectives (GLO). The ITAMP shall reflect the Integrated Product Development (IPD) approach and be a single plan for the entire Low Cost Concept Validation effort, including associate and/or major subcontractor activities. ITAMP Tasks shall be directly traceable to the Work Breakdown Structure (WBS) and Integrated Master Schedule (IMS).
Applicable Documents
The ITAMP shall contain an Applicable Documents section listing compliance and reference documents. Compliance documents are contractually binding, while reference documents are for guidance only and are not contractually binding. As a minimum, MIL-STD-881B, dated 25 Mar 93, Work Breakdown Structure For Defense Material Items, shall be listed as a reference document to the ITAMP. The Offeror may propose compliance documents, provided such documents are either existing Government or industry/commercial specifications or standards. However, company practices or procedures may only be listed as reference documents.
Additionally, the ITAMP shall contain the following sections: (1) Tasks, (2) Events, (3) Significant Accomplishments, (4) Accomplishment Criteria, and (5) Selected Narratives. The Offeror's proposed ITAMP shall be provided as Attachment 3 to the Model Contract.
Tasks
A Task describes a work effort (to be performed by the Offeror) which singularly, or in combination with other Tasks, satisfies the LCCV module GLO and SPD. (The task section replaces the effort descriptions usually contained in a Statement of Work.)
The ITAMP Tasks section shall contain references to the data items. Block 5 on the DD Form 1423-1, Contract Reference, shall contain the appropriate ITAMP reference.
Event
An Event is 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.
The Offeror shall establish the major contract events and identify the significant accomplishments that must be achieved to satisfy those major contract events. The Offeror is encouraged to identify incremental reviews and milestones as deemed necessary. The minimum Government required events are a tailored System Requirements Review (SRR) occurring no later than four months after contract award and a tailored Preliminary Design Review (PDR) occurring no later than twelve months after contract award. 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 tailored PDR shall be conducted to confirm that the total system design approach satisfies the functional baseline, risks are mitigated, and the total system is ready for detailed design implementation. The Government will formally attend no more than three major program reviews during the LCCV Module. Two of these reviews will be the tailored SRR and the tailored PDR. The third review will be at the discretion of the Offeror. In addition to the formal reviews, smaller groups of the Government reserve the right to meet with the Contractor throughout contract performance.
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. Significant Accomplishments shall be measurable. The Significant Accomplishments shall be sequenced in a manner which ensures a logical, critical path is maintained and tracks against key events. Each Significant Accomplishment shall be a required step to complete an event and not just time coincidental with that event.
Accomplishment Criteria
An Accomplishment Criterion is a definitive measure/indicator substantiating the maturity level of the Significant Accomplishment. It is the completion of specified work that ensures closure of a specified Significant Accomplishment. The ITAMP shall also contain Accomplishment Criteria to be used to demonstrate that each Significant Accomplishment has been successfully achieved. The Accomplishment Criteria shall be tied to the completion of key events. The Accomplishment Criteria shall be definitive and measurable, shall avoid the use of "percent completed" and shall avoid citing data item report numbers rather than reporting results. References to calendar dates in the ITAMP are not permitted.
The Significant Accomplishments and Accomplishment Criteria shall provide a mechanism for planning and evaluating the successful completion of the Tasks. Functional activity directly related to each product shall be integrated into these sections of the ITAMP. This portion of the ITAMP, with its supporting detailed schedule found in the IMS, will provide both the Offeror and the Government a method for evaluating the maturity of the products of the EELV System.
Narratives Content and Format
The ITAMP shall contain Narratives which give the Government a planning and management tool for providing additional insight into the Offeror's total work effort and for addressing how the Offeror will develop, commit, and implement the total contracted effort. The Narratives are concise statements describing the key functional/management processes and procedures that are used to achieve Significant Accomplishments.
These concise narrative statements shall describe their relationship to the IPD process and an overview of the efforts required for their implementation. The Narrative 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), since it will be included in the contract. The Narrative is not the forum for providing supporting information/rationale (i.e., why a particular approach has been taken). Each Narrative subject area shall be arranged in the following format:
A. Objective
B. Governing Documentation
C. Approach
A). The Objective is a brief statement of desired results. B). The Governing Documentation lists the Government, industry/commercial, and/or Contractor documents to be used to achieve the objective. The Offeror shall identify tailoring to Government or industry/commercial compliance documents. This tailoring section shall be attached to the ITAMP and is not part of the 75 page limit. C). The Approach is a concise description conveying specific commitments to the processes and procedures described, as well as the identification of the control/authority responsible for its execution. The use of flow diagrams is encouraged.
The Narrative describes the essential processes for directing an integrated management effort which include, but are not limited to, the following:
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.
Reliability. Define the processes to be used for conducting an EELV system 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 utilized within the systems engineering processes to influence the design of all components and their integration. Specifically, address the integration of software into the EELV reliability program.
Maintainability. Define the processes to be used for conducting an EELV system maintainability program for hardware and software elements. Data sources, modeling techniques, tools, processes (internal procedures or industry or military standards) intended to be used shall be discussed. Describe how the maintainability program is utilized within the systems engineering processes to influence the design.
Integrated Logistics Support (ILS). Address ILS planning and functions. Define the processes to be used for identifying system support design cost drivers and high risk areas. Describe the logistics support analysis approach and how that process will be used in developing supportable systems that will be interoperable with standard Air Force Infrastructure.
Manufacturing and Producibility Program. Define the processes to be used for conducting a manufacturing and producibility program that satisfies program objectives and reduces manufacturing and producibility risk. Define the processes to be used for conducting a Parts, Materials and Processes (PMP) Control program that satisfies EELV program objectives, uses, methods and provisions that have a history of demonstrated effectiveness for achieving mission assurance, and provides the Government with adequate insight. Describe the approach to be used to obtain a balance between performance, new technology, parts obsolescence and standardization. Describe the approach to validating and managing parts control processes so as to ensure that requirements are met. Address manufacturing management's role in design, development, manufacturing planning and key program events. Include in the description how process improvements are incorporated and process variation is controlled and how manufacturing deficiencies will be addressed and corrected.
Quality Assurance. Define the processes to be used in conducting the quality assurance program for hardware and software during design, development, manufacturing, and test. Identify processes and the approach for hardware and software quality assurance, during LCCV, which will contribute to significant risk reduction and cost reduction during the production phase. Include plans and procedures for tracking and reducing "Total Cost of Quality."
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 and monitoring the potential technical, cost, and schedule risk drivers and their interdependence. Address the integration of software into the risk management program.
Software Engineering. Define the software development life cycle model to be used for the EELV 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. Indicate any relationships between the software development processes described here and the systems engineering and other processes described elsewhere in the ITAMP narrative.
Test and Evaluation. Define the processes to be used for demonstrating and projecting systems 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 Low Cost Concept Validation Module. Describe what procedures will be used during initial and ongoing production flights to validate analytical predictions of inflight dynamic loads.
Environmental Protection. Define the processes to be used for integrating environmental protection considerations into the overall systems engineering process. 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.
Hazardous Materials Management. Define the processes to be used for identifying, justifying, minimizing, eliminating, and controlling hazardous materials for the EELV system, 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. Include work tasks and content as described by paragraphs 4.3 and 5.2 of National Aerospace Standard NAS 411.
System Safety. Define the processes to be used for implementing a system safety program that will ensure that all system safety engineering requirements are identified and factored into the design and operational procedures of the EELV system; ensure that all range safety requirements are met and that all sources of energy and toxic materials are identified and analyzed for potential mishap risk and reported to the Government. Address the integration of software into the safety program.
Program Protection Planning (PPP) and System Security Engineering (SSE). Define the processes to be used for supporting the Government in developing the PPP, provided in RFP Annex J, and for updating and implementing the Government developed, EELV security classification guidance, and technology controls. The description must address approaches that will ensure essential program information, technologies, and systems (EPITS) are identified and afforded effective, efficient protection. Define the organization, management and implementation approach for SSE, including software.
Configuration Management. Define the processes to be used in implementing a Configuration Management Program which identifies, documents, and controls the performance and technical requirements of the system.
Data Management. Define the processes to be used by which program data will be collected, formatted, stored, updated and transmitted.
Human Factors Engineering. Define the processes to be used for ensuring that the required technology development, engineering, and management tasks are accomplished during system design to provide for effective and efficient operator and maintainer performance.
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. For system concepts using solid rocket motors, describe the technical approach for establishing design requirements governing interactive gas flow and propellant grain structural deformation analyses. Describe the technical and management procedures to be used for controlling mass properties during the LCCV module of the program. 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 launch vehicle, 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 EELV system and payload.
Electromagnetic Compatibility. Define the processes to be used in conducting an overall EELV electromagnetic effects program designed to control electromagnetic emission and susceptibility characteristics of electronic, electrical, and electromechanical systems, subsystems, and components.
Corrosion Control. Define the processes to be used in conducting a corrosion prevention and control program.
Contamination. Define the processes to be used in conducting a contamination control program to deal with environmental control of clean rooms and work stations, product cleanliness levels and general contamination control.