RFP ANNEX A

EELV PROGRAM
INTEGRATED TASK AND MANAGEMENTPLAN (ITAMP) INSTRUCTIONS THIS ANNEX, INCLUDING THE
COVER, CONSISTS OF 7 PAGES
RFP ANNEX A © INTEGRATED TASK AND MANAGEMENT PLAN (ITAMP)INSTRUCTIONS.

The ITAMP is an Offeror generated document, describing the taskings, core activities, andprocesses necessary to satisfy the System Performance Document (SPD) requirements and LowCost Concept Validation (LCCV) Government List of Objectives (GLO). The ITAMP shallreflect the Integrated Product Development (IPD) approach and be a single plan for the entireLow Cost Concept Validation effort, including associate and/or major subcontractor activities. ITAMP Tasks shall be directly traceable to the Work Breakdown Structure (WBS) and IntegratedMaster Schedule (IMS).

Applicable Documents

The ITAMP shall contain an Applicable Documents section listing compliance and referencedocuments. Compliance documents are contractually binding, while reference documents are forguidance only and are not contractually binding. As a minimum, MIL©STD©881B, dated 25 Mar93, Work Breakdown Structure For Defense Material Items, shall be listed as a referencedocument to the ITAMP. The Offeror may propose compliance documents, provided suchdocuments 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. TheOfferor'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 incombination with other Tasks, satisfies the LCCV module GLO and SPD. (The task sectionreplaces 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 Form1423©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 adecision point related to the system maturity with continued system development.

The Offeror shall establish the major contract events and identify the significantaccomplishments that must be achieved to satisfy those major contract events. The Offeror isencouraged to identify incremental reviews and milestones as deemed necessary. The minimumGovernment required events are a tailored System Requirements Review (SRR) occurring nolater 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 conductedto demonstrate the progress in converging on viable, traceable system requirements that arebalanced with program cost, schedule, and risk. The tailored PDR shall be conducted to confirmthat the total system design approach satisfies the functional baseline, risks are mitigated, and thetotal system is ready for detailed design implementation. The Government will formally attendno more than three major program reviews during the LCCV Module. Two of these reviews willbe the tailored SRR and the tailored PDR. The third review will be at the discretion of theOfferor. In addition to the formal reviews, smaller groups of the Government reserve the right tomeet with the Contractor throughout contract performance.

Significant Accomplishment

A Significant Accomplishment is a specified result, substantiating an event, that indicates thelevel of progress or maturity directly related to each product/process. SignificantAccomplishments shall be measurable. The Significant Accomplishments shall be sequenced ina manner which ensures a logical, critical path is maintained and tracks against key events. EachSignificant Accomplishment shall be a required step to complete an event and not just timecoincidental with that event.

Accomplishment Criteria

An Accomplishment Criterion is a definitive measure/indicator substantiating the maturity levelof the Significant Accomplishment. It is the completion of specified work that ensures closure ofa specified Significant Accomplishment. The ITAMP shall also contain AccomplishmentCriteria to be used to demonstrate that each Significant Accomplishment has been successfullyachieved. The Accomplishment Criteria shall be tied to the completion of key events. TheAccomplishment 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 forplanning and evaluating the successful completion of the Tasks. Functional activity directlyrelated to each product shall be integrated into these sections of the ITAMP. This portion of theITAMP, with its supporting detailed schedule found in the IMS, will provide both the Offerorand 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 managementtool for providing additional insight into the Offeror's total work effort and for addressing howthe Offeror will develop, commit, and implement the total contracted effort. The Narratives areconcise statements describing the key functional/management processes and procedures that areused to achieve Significant Accomplishments.

These concise narrative statements shall describe their relationship to the IPD process and anoverview of the efforts required for their implementation. The Narrative shall address only thekey elements of implementing or developing a process/procedure (i.e., what theprocess/procedure will be and how it will be implemented), since it will be included in thecontract. The Narrative is not the forum for providing supporting information/rationale (i.e., whya particular approach has been taken). Each Narrative subject area shall be arranged in thefollowing format:
A. Objective
B. Governing Documentation
C. Approach

A). The Objective is a brief statement of desired results. B). The Governing Documentationlists the Government, industry/commercial, and/or Contractor documents to be used to achievethe objective. The Offeror shall identify tailoring to Government or industry/commercialcompliance documents. This tailoring section shall be attached to the ITAMP and is not part ofthe 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/authorityresponsible for its execution. The use of flow diagrams is encouraged.

The Narrative describes the essential processes for directing an integrated management effortwhich 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 designsolutions, and performing systems analysis and trade©off studies. Describe the methodologiesthat 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 militarystandards) intended to be used shall be discussed. Describe how the reliability program isutilized within the systems engineering processes to influence the design of all components andtheir integration. Specifically, address the integration of software into the EELV reliabilityprogram.

Maintainability. Define the processes to be used for conducting an EELV systemmaintainability program for hardware and software elements. Data sources, modelingtechniques, tools, processes (internal procedures or industry or military standards) intended to beused shall be discussed. Describe how the maintainability program is utilized within the systemsengineering processes to influence the design.

Integrated Logistics Support (ILS). Address ILS planning and functions. Define the processesto be used for identifying system support design cost drivers and high risk areas. Describe thelogistics support analysis approach and how that process will be used in developing supportablesystems that will be interoperable with standard Air Force Infrastructure.

Manufacturing and Producibility Program. Define the processes to be used for conducting amanufacturing and producibility program that satisfies program objectives and reducesmanufacturing 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 usedto obtain a balance between performance, new technology, parts obsolescence andstandardization. Describe the approach to validating and managing parts control processes so asto ensure that requirements are met. Address manufacturing managements role in design,development, manufacturing planning and key program events. Include in the description howprocess improvements are incorporated and process variation is controlled and howmanufacturing deficiencies will be addressed and corrected.

Quality Assurance. Define the processes to be used in conducting the quality assuranceprogram 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 productionphase. 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 thedescription how the risk management process fits in with the overall systems engineeringprocess. Describe the processes for identifying, analyzing, prioritizing and monitoring thepotential technical, cost, and schedule risk drivers and their interdependence. Address theintegration of software into the risk management program.

Software Engineering. Define the software development life cycle model to be used for theEELV software. Describe the technical and management processes to be used to produce highquality, cost effective software products. Address the processes used to perform the product© specific software development activities and the integral processes that occur throughout thesoftware development life cycle. Indicate any relationships between the software developmentprocesses described here and the systems engineering and other processes described elsewhere inthe ITAMP narrative.

Test and Evaluation. Define the processes to be used for demonstrating and projecting systemseffectiveness and suitability throughout the program life cycle. Describe the approach forproviding Government insight into test planning, execution, and reporting. Describe proposedMeasures of Effectiveness (MOEs). Identify test resources planned for use during the Low CostConcept Validation Module. Describe what procedures will be used during initial and ongoingproduction flights to validate analytical predictions of inflight dynamic loads.
Environmental Protection. Define the processes to be used for integrating environmentalprotection considerations into the overall systems engineering process. Describe themethodology and processes that will be used to: define potential environmental impacts, identifyrequired 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, systemcomponents, and associated support items. Describe the screening process and methodology foridentifying 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 AerospaceStandard NAS 411.

System Safety. Define the processes to be used for implementing a system safety program thatwill ensure that all system safety engineering requirements are identified and factored into thedesign and operational procedures of the EELV system; ensure that all range safety requirementsare met and that all sources of energy and toxic materials are identified and analyzed for potentialmishap risk and reported to the Government. Address the integration of software into the safetyprogram.

Program Protection Planning (PPP) and System Security Engineering (SSE). Define theprocesses to be used for supporting the Government in developing the PPP, provided in RFPAnnex J, and for updating and implementing the Government developed, EELV securityclassification guidance, and technology controls. The description must address approaches thatwill ensure essential program information, technologies, and systems (EPITS) are identified andafforded effective, efficient protection. Define the organization, management andimplementation approach for SSE, including software.

Configuration Management. Define the processes to be used in implementing a ConfigurationManagement Program which identifies, documents, and controls the performance and technicalrequirements 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 requiredtechnology development, engineering, and management tasks are accomplished during systemdesign to provide for effective and efficient operator and maintainer performance.

Design Considerations. Define the processes to be used for developing design criteria andspecial test requirements for moving mechanical assemblies, explosive ordnance devices, self© locking connections, separable fluid fittings, honeycomb sandwich structures, compositestructures and structural bonded joints, and pressurized subsystems. For system concepts usingsolid rocket motors, describe the technical approach for establishing design requirementsgoverning interactive gas flow and propellant grain structural deformation analyses. Describe thetechnical and management procedures to be used for controlling mass properties during theLCCV module of the program. Describe the technical approaches to be used for establishingdesign allowables, conducting dynamic loads analyses, evaluating structural integrity, anddetermining test plan requirements for the launch vehicle, subsystems, and component structures. Define the processes to be used for developing design criteria for lightning protection, preventionof electrical overload, and damaging electrical discharge of the EELV system and payload.

Electromagnetic Compatibility. Define the processes to be used in conducting an overallEELV electromagnetic effects program designed to control electromagnetic emission andsusceptibility characteristics of electronic, electrical, and electromechanical systems, subsystems,and components.

Corrosion Control. Define the processes to be used in conducting a corrosion prevention andcontrol program.

Contamination. Define the processes to be used in conducting a contamination control programto deal with environmental control of clean rooms and work stations, product cleanliness levelsand general contamination control.