RFP_Amend_0001_EST_II_060713.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

RFP Amendment 0001 is issued to incorporate the following changes:

- Change the proposals due date from 2:00 PM EST, 11 June 2013 to 2:00 PM EST, 24 Jun 2013.

- RFP Section B.1 - Range Pricing has been updated to provide clarification for the pricing of Technical Refresh of EST systems and simulated weapons.

- RFP Section B.2 - T&M Rates Applicable to CLINs 0039, 0040, 0041 and 0043 has been clarified to reflect that the T&M rates FY is the Offeror's FY. Offerors are to identify the period of performance that their FY covers.

- Revise RFP Section C, 1.0 - Scope, 4th paragraph from: “The GFI will include all available Government Purpose Rights (GPR)/releasable data, to include...a revised ICD for simulated weapons (produced by FATS) ...”to “The GFI will include all available Government Purpose Rights (GPR)/releasable data, to include ... a redacted ICD for simulated weapons (produced by FATS)...”

- Revise RFP Section C, paragraph 3.4.5 - System Operational Test (SOT) from: “The Contractor shall support a Government test event at FT Benning to test the Technology refresh baseline system in an operational environment, with actual users, to ensure the system will meet its intended function, including reliability and maintainability, in the environment in which it will be used.” to “The Contractor shall support a Government test event at FT Benning to test the Government controlled baseline system for all new and technology refresh functionality that effect the Government controlled baseline (Example, Tech Refresh of EST (DO1), new weapon). This SOT shall be conducted in an operational environment, with actual users, to ensure the system will meet its intended function, including reliability and maintainability, in the environment in which it will be used.”

- Revised Section C, paragraph 3.6 - Interim Contractor Support (ICS), from: “The Contractor shall provide one month of Interim Contractor Support (ICS) services for each new system or weapon; or for each technical refresh system or weapon fielding to successfully transition the system Operation and Maintenance (O&M) to PM Field Ops life cycle support contractor.” to “The contractor shall provide one month of Interim Contractor Support (ICS) services for each new system and its simulated weapons and/or for each technical refresh system and its simulated weapons prior to successfully transitioning the system(s) Operation and Maintenance (O&M) to PM Field Ops life cycle support contractor. If the upgrade/refresh is for the weapons on an existing fielded system(s), then ICS is not required.”

- Revise RFP Section C, paragraph 3.7.1 - Site Survey and Legacy Equipment Pickup from: “The contractor shall conduct a site survey and legacy equipment pickup at each installation site at least three months prior to the commencement of the system installation.” to: “The contractor shall conduct a site survey and legacy equipment pickup at each installation site at least three months prior to the commencement of the system installation, if required.

- Revised Section C, paragraph 3.8 - System Technical Support from “The contractor shall provide support for defined mission support requirements that include training, logistics functions, hardware and software engineering functions, software maintenance, support services, spare parts, travel overtime, maintenance, supply, replacement of non-fair wear and tear parts, contractor activity and facility relocations, adding and deleting training devices, transportation of equipment, development, productions, installation of SW upgrades, re-host and modifications kits as authorized by individual delivery orders or contract work directives. For contract work directives, the contractor shall document the description of each task, the man-hours spent, cost of materials and services, and the results of each service(s).” to: “The contractor shall provide support for defined mission support requirements that include training, logistics functions, site surveys (actual travel costs only, i.e. air fare, per diem, rental car, hotel), hardware and software engineering functions, software maintenance, support services, spare parts, travel overtime, maintenance, supply, replacement of non-fair wear and tear parts, contractor activity and facility relocations, adding and deleting training devices, transportation of equipment, development, productions, installation of SW upgrades, re-host and modifications kits as authorized by individual delivery orders or contract work directives. For contract work directives, the contractor shall document the description of each task, the man-hours spent, cost of materials and services, and the results of each service(s).”

- Revise RFP Section F, clause 5152.245-5005, paragraph a) from “The initial Government Furnished Equipment (GFE) that will be provided to the awardee is identified in Attachment 4 RFP Section J. The GFE delivery will start within sixty days after the basic contract award. For Tech Refresh efforts, the Government will provide the applicable GFE systems and simulated weapons that will require the refresh. For new systems development, the Government will provide GFE expended AT4 tubes, expended BDM tubes, M320s, and M26s.” to “The initial Government Furnished Equipment (GFE) that will be provided to the awardee is identified in Attachment 4 RFP Section J. The GFE delivery for DO 0001 will start within sixty days after the DO award. For Tech Refresh efforts, the Government will provide the applicable GFE systems and simulated weapons that will require the refresh sixty days after the respective DO is awarded. For the AT4, BDM, M320s, and M26 development, the Government will provide GFE expended AT4 tubes, expended BDM tubes, M320s, and M26s commencing sixty days after the respective DO award. Depending upon the amount of GFE needed for these weapons, the delivery of the GFE may be staggered. If GFE is staggered, then delivery will also be staggered, i.e. weapons due twelve months after receipt of the GFE. Furnishing of the GFE and subsequent delivery schedule will be specified in each DO.”

- Revise RFP Section F1 from:

“F.1. SHIPPING ADDRESSES for Systems and Weapons:

Range pricing for CONUS shipping and travel shall include shipping and travel costs using a midpoint in U.S.: St. Louis, MO.

OCONUS shipment and travel costs will be for the difference between the U.S. midpoint and the OCONUS location. The cost differential for OCONUS shipments and travel will be covered under a T&M Work Directive.”

to:

“F.1. SHIPPING ADDRESSES FOR SYSTEMS AND OR SYSTEMS WITH SIMULATED WEAPONS

The Range pricing for CONUS/OCONUS shipments for systems and systems with simulated weapons shall not include shipping costs as well as travel costs for installs, site surveys, and initial training (excluding labor) as this will be covered under a T&M Work Directive. The labor costs for install, site surveys, and initial training shall be included in the range pricing.

F.2. SHIPPING ADDRESSES FOR SIMULATED WEAPONS THAT ARE NOT ORDERED WITH A SYSTEM:

F.2.1. The Range pricing for CONUS shipments for simulated weapons that are not ordered with a system shall include shipping costs using a midpoint in U.S.: St. Louis, MO. This average shipping cost will be utilized for all CONUS shipments of simulated weapons.

F.2.2. The Range pricing for OCONUS shipments for simulated weapons that are not ordered with a system will be for the difference between the U.S. midpoint (average shipping costs) and the OCONUS location. The cost differential for OCONUS shipments will be covered under a T&M Work Directive.”

- Incorporate Clause 52.251-1, Government Supply Sources, under the RFP Section I.

- Update RFP Section J to reflect the addition of RFP Attachment 12 - Current Fielded EST Locations, RFP Attachment 13 - M320 Simulated Weapon Documentation, and RFP Attachment 14 - Industry Questions/Government Answers to EST RFP W900KK-13-R-0007.

- Update RFP Section L.1.1 and L.1.18 to reflect the proposals due date revision from 2:00 PM, EST, 11 Jun 2013 to 2:00 PM, EST, 24 Jun 2013.

- Revise RFP Section L.3.3 from: “...An Executive Summary shall be provided as a top-level overview of the proposal, and included in the proposal before the individual volumes (The foregoing is excluded from the page count).” to: “...An Executive Summary shall be provided as a top-level overview of the proposal, as part of Volume I (see L.5.1.1), and included in the proposal before the individual volumes (The foregoing is excluded from the page count).”

- Revise RFP Section L.5.1.5 from: “The Offeror shall populate the Cross Reference Matrix, provided as RFP Section J Attachment 7, with the requested proposal reference information as well as whether the Offeror’s solution meets, does not meet, or exceeds, the corresponding Government requirement. The matrix will be used by the Government for evaluation in the Technical and Performance Risk Assessment Volumes.” to “The Offeror’s Proposal shall include a populated Cross Reference Matrix (RFP Section J Attachment 7), which is excluded from the page count. The intent of the Matrix is to ensure that an Offeror has provided evidence of compliance for the RFP requirements (not all requirements are listed in the Matrix). The matrix will not be used by the Government for evaluation in the Technical and Performance Risk Assessment Volumes. Proposal documents must identify all instances of deviations from the RFP/PWS/SOW. Deviations from the RFP/PWS/SOW should clearly articulate the benefit to the Government for accepting the deviation. Please note that a deviation from any of the documents contained within the RFP may render an offeror ineligible for award. Format/structure of the Matrix is open to interpretation but must be made available via electronic media as part of the Volume I proposal submittal. Offeror's shall certify that they meet/do not meet/exceed a given RFP requirement. If an offeror proposes to exceed a given requirement that is being evaluated in Factor 1-4, then they should identify the page and paragraph # in their proposal for that Factor/Subfactor. Their response to the respective Subfactors should state how they plan to exceed the requirement and the benefit to the Government as well as the information requested in the Subfactor.”

- Revise RFP Section L.5.2.5 a) from: “....The white paper shall support the Offeror’s proposed physics-based ballistic model, the white paper shall be included with the technical volume as an appendix and shall not count against the technical volume page limit.” to “The white paper and the modified excel spreadsheet (RFPAttachB_Ballistic Data Collection) with the Offeror’s ballistics model data shall support the Offeror’s proposed physics-based ballistic model. The white paper and the submitted excel spreadsheet (RFPAttach2B_Ballistic Data Collection) shall be included with the Offeror’s proposal Technical Volume as an appendix and shall not count against the Technical Volume page limit.”

- Revise RFP Section L.5.3.1.b from: “Major subcontractors are those subcontractors whose annual subcontract revenue is expected to exceed 10 percent of the anticipated annual effort.” to “Major subcontractors” are those subcontractors whose subcontract is for more than 10 percent of the total proposed price.”

- Revise RFP Section L.5.4 from: “All Offerors, both small and large businesses, are required to submit a Small Business Participation Plan that clearly demonstrates a viable plan for meeting or exceeding the Small Business Participation goal of no less than 30% of the ID/IQ $100,000,000 total contract value in each 12 months of performance beginning upon contract award.’ To “ All Offerors, both small and large businesses, are required to submit a Small Business Participation Plan that clearly demonstrates a viable plan for meeting or exceeding the Small Business Participation goal of no less than 30% of the ID/IQ $99,000,000 estimated total contract beginning upon contract award. However, the awardee's actual goal will be based on 30% of the Delivery Orders value awarded in each 12 months of performance.”

- Revise RFP Section L.5.5.3 from: “For T&M CLINs: Submit a schedule for each calendar year of T&M fully burdened labor rates for all the labor categories you propose, as well as the factors that are applied for travel and material.” to: “For T&M CLINs: The Offeror shall identify its Fiscal Year Accounting Period (ex. 1-Jul to 30-Jun), submit a schedule for each Offeror Fiscal Year of T&M fully burdened labor rates for all the labor categories proposed, as well as the factors that are applied for travel and material.”

- Revise RFP Section M.3.3 from: “The Government will evaluate the Offeror’s technical approach to meet the overall requirements of the ID/IQ, including how it describes and demonstrates meeting the requirements and specifications of DO 0001.” to “The Government will evaluate the Offeror’s technical approach to meet the overall requirements of the ID/IQ, including how it describes and demonstrates meeting the requirements and specifications of DO 0001. The Government will evaluate the Offeror’s plan for providing the solution with open architecture (SRD 6.1.8)) and coordinating and managing their hardware and software baseline activities, to include providing and receiving multiple software baseline drops, while demonstrating a thorough understanding of the EST II system to include legacy EST necessary to meet the full breadth of the requirements of the ID/IQ.”

- Revise RFP Section M.3.5.1 from ”...The awardee will be responsible for meeting the Government’s Small Business Participation goal of not less than 30% of the ID/IQ $100,000,000 total contract value in each 12 months of performance beginning upon contract award.” to “...The awardee will be responsible for meeting the Government’s Small Business Participation goal of not less than 30% of the Delivery Orders value awarded in each 12 months of performance, beginning upon contract award.”

- Revise RFP Attachment 2A - Data Collection and Demonstration Plan.

- Revise RFP Attachment 2B - Ballistic Data Collection.

- Revise RFP Attachment 11 - Pricing Spreadsheet to update format, allow Offerors to identify their company’s Fiscal Year accounting period, and provide applicable T&M rates, ODCs, and Travel Factors for FY 14 thru FY19.

- Add RFP Attachment 12, which identifies the current fielded EST locations. The list is provided for Offerors information only - the Government will identify the specific sites to be retrofitted in accordance with requirements of future Delivery Orders.

- Add RFP Attachment 13, M320 Simulated Weapon Documentation. RFP Attachment 13 is Sensitive but Unclassified data that is subject to export control. Attachment 13 has been loaded into Federal Business Opportunities (FBO) website as an export controlled, explicit access document package “file” link (U.S. Contractors Only). When the FBO “file” link is clicked, the user is taken to the “packages” sub-tab for the opportunity. To review this controlled Sensitive but Unclassified package, a user is required to have a valid Marketing Partner Identification Number (MPIN) entered in the system. The MPIN is part of the Central Contractor Registration (CCR) profile for an entity. The ‘FBO.GOV Vendor Guide’, located in the Federal Business Opportunities ‘www.fbo.gov’ homepage, provides detailed instructions for the access ad review of controlled packages associated with an opportunity. The M320 Simulated Weapon Documentation is provided “As Is”. The Goverment does not warrant the drawings suitability for use.

- As indicated in the RFP Section L.1.16, publish Government answers to questions submitted by prospective Offerors. The queastions and answers are added as RFP Attachment 14.

- All other terms and conditions of RFP W900KK-13-R-0007 remain unchanged and in full force and effect.

SECTION B - SUPPLIES OR SERVICES AND PRICES

The following have been modified:

B.1. Range Pricing.

THE CLINs PRICING SUBMITTED BY OFFERORS (RFP ATTACHMENT 11) WILL BE USED TO ESTABLISH CLIN PRICING FOR DO 0002 and SUBSEQUENT DOs.

Offerors shall provide range pricing for the systems and simulated weapons listed above for DOs -0002 and subsequent in RFP Section J, Attachment 11.

The pricing for the Technical Refresh of EST systems, and Fire Team EST II systems, shall reflect all the applicable efforts required for the supplies and services required to: manufacture; test; deliver; install (See Section F) each system/weapon; provide system training (Operator and initial Maintainer Training courses (PWS 3.5.6)); provide interim contractor support (PWS 3.6); system/weapon warranties, if any; COTS component warranties, if any, and requisite documentation.

The pricing for Technical Refresh of EST simulated weapons and/or simulated weapons procured separately from an EST system shall reflect all the applicable efforts required for the supplies and services required to manufacture, test, and deliver the simulated weapons (Also, see Clause F.1.).

DOs for the priced supplies may be unilaterally placed at the prices and ranges stated in the RFP Section J, Attachment 11, which will become part of B.1 in the awardee’s contract. Please note, if the Government issues an order for an additional quantity within 30 days of a previous order, the first order will be modified to determine range pricing applicable to the combined quantity, and will be priced accordingly. For example: an order is issued on 15 October for 25 ea. M16A4 Simulated Weapons against range priced CLIN 0005 Attachment 11; then an order is placed for an additional 26 ea. M16A4 Simulated Weapons on 11 November. Since both actions were executed within 30 days, the Government would obtain a discount as if it acquired 51 systems altogether. Second scenario: an order is issued on 15 October for 25 ea. M16A4 Simulated Weapons against range priced CLIN 0005 Attachment 11; then an order is placed for an additional 26 ea. M16A4 Simulated Weapons on 18 November. Since the actions were executed 34 days apart, each DO will reflect the price for range quantity 1-50 for both orders.

B.2 T&M Rates Applicable to CLINs 0039, 0040, 0041, and 0043.

Offerors shall provide their proposed fully burdened labor rates for the Time and Material (T&M) CLINs identified in the RFP Attachment 11 for each Offeror Fiscal Year. All T&M fully burdened rates shall be effective and binding for the duration of the contract. Profit may only be applied to labor, and may NOT exceed 10%. No profit is allowed on materials and travel.

Based on a mutual agreement between both parties, the agreed-to-price of any T&M rates proposed for the CLINs 0039, 0040, 0041, and 0043, as indicated in Section B, are subject to an adjustment based on the final results of a DCAA audit. Any DCAA audit of the T&M rates will be conducted after award, but prior to the exercise of the CLINs (CLINs 0039, 0040, 0041, and 0043). The Government reserves the right to request a downward adjustment to the T&M rates upon completion and receipt of the DCAA audit review, if DCAA determines that the T&M rates should be less than proposed. The proposed T&M rates shall remain in effect until such time as a DCAA audit is requested and a recommendation is rendered. Any T&M rates specifically proposed for this effort may only be adjusted downward as a result of an audit review.

If requested by the Contracting Officer, the contractor shall submit revised T&M rates within 30 days of the Government's request taking into consideration the final DCAA recommended rates. Should the contractor fail to submit revised rates or no agreement can be reached, then the Contracting Officer may make a unilateral determination and modify the contract accordingly. Failure to agree with such change in the contract price shall be resolved in accordance with the Disputes clause of this contract.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT NO. PEO-STRI-12-W023 FOR THE ENGAGEMENT SKILLS TRAINER II (EST II)

1. SCOPE.

The U.S. Army Program Executive Office Simulation, Training and Instrumentation (PEO STRI) has a requirement to provide a technical refresh of EST for marksmanship training to the U.S. Army. The program shall use a five (5) year Period of Performance (POP) Indefinite Delivery/Indefinite Quantity (ID/IQ) contract effort with Firm Fixed Price (FFP) range pricing for retrofit, as well as the procurement of new systems and simulated weapons. The contract also contains CLINs for minor Time and Materials (T&M) provisions. This Performance Work Statement (PWS) describes the work to be accomplished by the contractor in providing the technology refresh and production of the Engagement Skills Trainer (EST) II, including the simulated weapons, and configured systems to comply with the System Requirements Document (SRD) PRF-PT-00581.

This PWS defines efforts required for the EST II program under a five-year ID/IQ contract. Contract Data Item Requirement Lists (CDRLs) called out in the PWS identify consolidated requirements for the EST II program. Delivery Orders (DO) issued under this ID/IQ are standalone contract actions. Each DO Statement of Work (SOW) shall have the same paragraph structure as in the PWS.

Individual Delivery Orders (DOs) shall identify: any additional scope of work, scope of work relationship to the program baseline, updates to program baseline CDRLs, potential new stand-alone CDRL requirements based on scope of work, and all funding requirements for the scope of work to be executed under the individual DO.

The awardee will receive two (2) 10-lane heavy legacy EST systems with simulated weapons and available Government Furnished Information (GFI). The GFI will include all available Government Purpose Rights (GPR)/releasable data, to include operator and maintenance manuals, Interface Control Document (ICD) for simulated weapons (produced by Cubic), a redacted ICD for simulated weapons (produced by FATS), M320 drawing packages, the M141 Bunker Defeat Munitions (BDM) drawing package, and LAGS II drawings (unstabalized gunnery). These EST systems are for verification of the technology refresh. The contractor will develop a production representative prototype system and supporting documentation for the Verification, Validation & Accreditation (VV&A) of training capabilities In Accordance With (IAW) the SRD. Upon Government approval, the upgraded systems will become the U.S. Army baseline EST II system.

After Government approval of the baseline EST II system, the contractor will plan for the retrofit of approximately 925 5-lane Program of Record (POR) EST systems (281 Light sub-systems, 593 Heavy sub-systems, 51 Hybrid sub-systems = 925 sub-systems) and approximately 150 5-lane customer-funded EST systems currently supported by PEO STRI PM Field OPS into the approved baseline configuration. Refresh may be required on all or some of these systems and simulated weapon types (See SRD Section 6.1.14 for weapon configuration mix definition)). The contractor may do a retrofit or produce their own simulated weapon dependent upon their approach. Additionally, the contractor will support Post Deployment Software Support (PDSS) after the VV&A phase for bi-annual software (SW) updates containing new training scenarios and system SW updates under this ID/IQ contract. This paragraph shall not be interpreted to limit the Government’s maximum quantities or ceiling price established in the Section B clause, “CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE.”

1.1 Background.

The U.S. Army currently primarily trains soldiers using actual weapons on ranges. Prior to the legacy EST, there were no devices which were multipurpose and support individual and crew served weapons training in an indoor environment with U.S. Army validated ballistics and accuracy. The EST simulated weapons support all U.S. Army small arms and allow for realistic target presentations in varying environments such as desert, forest and military operations in urban terrain. There is a continuing need in active and reserve component units for the EST as a small arms simulator which can:

a. Simulate weapon training events which lead to live fire individual and crew weapon qualification.

b. Simulate training events currently not resourced that contribute to increased weapon, crew, fire team, and squad combat effectiveness, namely, reflexive fire, engagement of moving targets, firing machine guns in pairs and Escalation of Force (EOF) decision training.

c. Simulate squad collective gunnery and tactical tasks for defense and ambush missions.

d. Provide the medium for training leaders of fire teams and squads in command, control, and distribution of fires while in a realistic collective mode.

e. Save current required ammunition resources, travel time and cost to and from ranges, other range support resources, while simultaneously providing meaningful, effective training to soldiers.

f. Support the functional gunnery training strategies and standards in weapons training.

2. APPLICABLE DOCUMENTS.

The following documents of issue shown on the document summary list form a part of this PWS to the extent specified herein. .

2.1 Government Documents.

Stand-alone System IA Process

Mission Assurance Category (MAC) III, Confidentially Level

Sensitive. The Standalone PIT DIP has 32 controls.

System Requirements Document (SRD)

2.2 Availability of Government Documents.

Unless otherwise indicated, copies of the documents listed above are available from PEO STRI, 12350 Research Parkway, Orlando, FL 32826-3275.

2.3 Order of Precedence.

In the event of conflict between documents referenced herein and the contents of this PWS, the contents of the PWS shall be the governing requirement, followed by the SRD and then the referenced documents, exhibits and attachments.

3. REQUIREMENTS.

This PWS defines the effort required for technology refresh of the EST as well as the manufacturing, testing, managing, documenting, and delivering EST II systems, weapons and scenarios. The Contractor shall produce an EST II Training System that meets the performance requirements as defined in the EST II SRD, PRF-PT-00581.

The Contractor shall track and account for all requirements, including decomposed and derived, for the program using a Requirements Traceability Matrix (RTM) tool. Contractor shall update and maintain RTM throughout the life of the contract.

3.1 Program Management.

The contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished.

3.1.1 Integrated Master Plan (IMP).

The contractor shall implement, manage to, update, and maintain a contract Integrated Master Plan (IMP). The contractor shall develop the EST II system IAW the IMP. The contractor shall report on work in progress IAW the IMP at each program review, and at technical reviews at Government discretion.

3.1.2 Integrated Master Schedule (IMS).

The contractor shall develop, implement, manage and update the contract Integrated Master Schedule (IMS). Schedule information delivered or presented at program reviews shall originate from the IMS. The IMS shall be traceable to the IMP and the CWBS. The IMS shall address and identify total program activities including activities performed by subcontractors. The IMS shall address interdependencies within a DO and across DOs. The IMS shall track to CWBS level III and lower levels as required, to date accomplishments, program milestones, contractor manpower and resources, Government Furnished Equipment (GFE and GFI), etc. The contractor shall conduct critical path analysis of tasks and identify problem areas and corrective actions required to eliminate or reduce schedule, cost, and performance impacts to the program.

3.1.3 Contractor’s Progress, Status and Management Report.

The contractor shall deliver a Progress, Status, and Management Report covering management, technical, logistics, and administrative support. The report shall address overall program status IAW the IMP, and IMS. The report shall provide the status risk areas and corrective actions for each DO.

3.1.4 Contract Invoice and Payment Report.

The contractor shall document and track the status of all funds to include obligations, payments, cancellations, invoice, disbursements, and progress payments traceable to the IMP, IMS, CWBS, and Contract Line Item Number (CLIN). The Contract Invoice and Management Report shall provide a description of each obligations, payments, cancellations, invoice, disbursements, and progress payments for each reporting period. Funds expenditures shall be traceable to a specific DO for specific requirements (i.e. DO requirements for new simulated weapon development will fund applicable CWBS elements).

3.1.5 Configuration Management (CM).

The contractor shall use industry standard best practices, processes, and tools to establish and maintain consistency between system requirements, system configuration information, and all other relevant information about the system. The Configuration Management (CM) process shall ensure that the system conforms to the SRD, System/Subsystem Specification (SSS), and lower level requirements; that all requirements and components (both hardware and software) are identified and documented in sufficient detail to support the system life cycle; ensure component interchangeability; ensure accurate system information; and facilitate system maintenance. The contractor shall define the performance, functional, and physical attributes in configuration documentation. As the configuration information becomes more detailed and definitive throughout the life cycle, the contractor shall define configuration baselines. The contractor shall archive the defined attributes for each baseline in a CM integrated database. Both the system baseline and its associated information shall be verified for consistency. The contractor shall identify and evaluate the impact of all proposed changes through the configuration change management process, including verification that the system baseline and all associated component information have been updated and continue to be consistent. The Government will maintain control of the Functional Baseline (FBL) defined by SRD, the system performance specification, ICD, and software requirement specifications. Separate baseline configurations shall exist for both U.S. and Foreign Military Sales (FMS) components. Baseline information shall not be shared between US and FMS baselines.

3.1.5.1 Configuration Management Planning and Management

The contractor shall:

a. Plan implementation of the CM functions for the context and environment in which they are to be performed and managed.

b. Determine the specific CM value-adding functions and levels of emphasis.

c. Document how the contractor organization will implement CM functions to provide the consistency between the systems attributes definition information and the system’s configuration information, throughout the applicable phases of the life cycle.

d. Identify resources required to implement the CM functions and ensure they are applied throughout the systems life cycle.

e. Assess the effectiveness of CM plan implementation and performance of the CM functions with performance measurements.

f. Flow down responsibility for CM performance to subcontractors.

g. Ensure all data products transmitted to the Government are usable.

3.1.5.2 Configuration Identification.

The contractor shall create unique identifiers for each Configuration Item (CI) at the system, subsystem, and component level and for both Computer Software Configuration Items (CSCI) and Hardware Configuration Items (HWCI) at each level, i.e. system, subsystem, and component. The contractor shall:

a. Define the functional, performance, interface, and physical attributes of the system and components.

b. Determine the systems’ composition using its product definition information.

c. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved.

d. Assign unique unit identifiers to individual components of the system.

e. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier.

f. Uniquely identify information so that it can be correctly associated with the applicable configuration of the system.

g. Apply information identification rules to maintain representation and version relationships.

h. Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval.

i. Establish complete, valid and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed.

j. For each CI, CSCI, and HWCI Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to the system or within the system.

3.1.5.3 Configuration Control Board (CCB).

The contractor shall establish and maintain a single, unified Configuration Control Board (CCB) responsible for configuration control of all CIs and related products. The CCB shall be responsible for management of Government Off-The-Shelf (GOTS) and Commercial Off-The-Shelf (COTS) (including open source) configuration items. The contractor shall obtain approval from the system Integrated Product Team (IPT) prior to committing to use any version of COTS product that negatively impact open architecture. All GOTS and COTS software products shall be independently tracked as separate CSCIs. The contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported.

3.1.5.4 Configuration Change Management (CCM).

The contractor shall use their established systematic and measurable Configuration Change Management (CCM) process for managing product configuration changes and variances. Once the system requirements have been approved by the CCB, the contractor shall effect changes to the baseline. The contractor shall:

a. Document and uniquely identify each change.

b. Classify requested changes to aid in determining the levels of review and approval.

c. Clearly and completely document request for change.

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment as to whether the change should be approved for implementation and incorporation in the system and its documentation.

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility.

f. Determine the affectivity for each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit.

g. Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements.

h. Document variances, when authorized by the appropriate level of authority.

3.1.5.5 Configuration Verification and Audit.

The contractor or its subcontractor responsible for configuration management shall utilize Capability Maturity Model Integration - Development (CMMI-DEV) Level 3 or higher standards. The contractor or its subcontractor responsible for configuration management shall provide these procedures to the government for review and audit purposes on the IDE. At this level, processes are well characterized and understood, and are described in standards, procedures, tools, and methods. The Contractor shall maintain surveillance over the configuration management process in support of the contractor’s CMMI Level 3 established processes or higher. All verifications and audits conducted in accordance with these plans shall be documented within the Integrated Digital Environment (IDE).

The Contractor shall be responsible for identifying opportune timeframes to the Government to witness the Contractor’s in-process verifications of the documentation and hardware components. At different intervals throughout the build process, the Contractor shall make the hardware available to the Government for their own reviews and verifications of all technical documentation, hardware, and software. The Contractor shall be responsible for identifying in the IMS recommended viewing times during the development process that allow components to be easily viewed prior to assembly.

The contractor shall ensure that the IDE contains the latest CM versions of all technical documentation on their IDE. The Government will utilize the IDE technical documentation to perform their verifications by reviewing a representative number of drawings, associated technical manuals, software versions, logistics management information, and manufacturing instructions to confirm the accuracy of the final product configuration design.

3.1.5.6 Request for Deviation (RFD).

The contractor shall document the rationale and obtain the Government’s written approval before deviating from any Government approved baseline.

3.1.5.7 Software Configuration Management (SCM).

The contractor shall establish a Software Configuration Management (SCM) Control Board under the program CCB. The contractor shall identify the SCM tool and document a SW CM process for configuration control of the SW configuration items and related software products throughout the duration of this contract.

3.1.5.8 Data Management.

The contractor shall develop, manage, and deliver acceptable contractually required data. This requirement includes all data deliverables cited in the CDRL and all source documents required to develop and prepare the CDRL items and equipment. The contractor shall ensure that all data items to be delivered to the Government meet the quantity and quality requirements of the CDRL. Procedures and policies shall be established to provide control and configuration management of all contractually required data during the life of the contract. The contractor’s development and storage media should be compatible with the Government’s requirements for the format and media of the deliverables. The final format and media for the deliverables shall be as stated in the CDRL. Data management systems will be the subject of Government in-process reviews to determine if the data management requirements are being met. The contractor shall include the status of data deliveries in the Contractor’s Progress Status and Management Report.

3.1.6 Risk Management (RM).

The contractor shall use their already developed Risk Management (RM) process. This shall include risk detection and identification, assignment of risk categories, action triggers, and corrective action, tracking of compliance, reporting of status and planning for risk mitigation. The contractor shall:

a. Identify and document moderate and high-risk items for each risk assessment area.

b. Identify and implement risk handling approaches and track over time each moderate and high-risk item.

c. Document risk issues that have been successfully resolved and schedule each open item into the program IMS.

d. Develop mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified.

3.1.7 Management Reviews, Meetings and other Events.

The contractor shall conduct, attend, and participate in management reviews, meetings, and other events to be held at contractor and/or Government facilities IAW the IMS. The contractor shall prepare the agenda, all data required for presentations, document and track action items until closure, and prepare minutes of the event. The contractor shall have key personnel and key subcontractors required to support and carry out the event. The contractor shall make available facilities for Government only meetings for events at the contractor’s facility. The event shall be considered fulfilled when topics required for discussion are covered, all action items are documented, and the Government has accepted the event’s minutes.

3.1.7.1 Video Teleconferencing.

The contractor shall have the capability to communicate with different Government facility locations via video desktop teleconferencing with data sharing.

3.1.7.2 Reserved.

3.1.7.3 Start of Work/Post Award Meeting (SWPAM).

A SWPAM shall be held at the contractor’s facility within 45 calendar days After Contract Award (ACA). The SWPAM shall introduce the key IPT participants, identify points of contact, discussion of the understanding of the SOW, contract issues, and establish the framework of the contractor and Government interaction during contract performance. This conference shall cover: Introduction, informal and formal Procurement Contracting Officer (PCO) contract actions, action item reporting and status, IPTs and team contact list (names, work location, IPT memberships, phone numbers, and email addresses, etc), IMS and critical paths, CDRL delivery schedule and Data Item Descriptions (DIDs), Systems engineering (SE), Integrated Logistics Support (ILS), CM (to include data management), Quality Assurance (QA) management, Reliability and Maintainability (RAM), metrics analysis and reporting, financial management, and GFI & GFE. The SWPAM shall be considered a successful event with the Government concurrence that all required SWPAM topics have been satisfactorily presented, discussed, and documented; the submittal and Government acceptance of the SWPAM minutes and presentation materials; and all action items have been assigned with suspense dates for closure.

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.1.7.4 Program Management Reviews (PMR).

The contractor shall conduct formal Program Management Reviews (PMRs) every 3 months IAW the IMP and IMS. The location of the reviews shall be mutually agreed upon. The PMR shall provide a program overview and a detailed discussion of pre-selected topics. Status and information at the review shall reflect currency since the previous review.

3.1.7.5 Information Assurance (IA).

3.1.7.5.1 Information Assurance (IA) Process Review.

The contractor shall establish an Information Assurance (IA) process IAW the PEO STRI Basic Accreditation Manual (BAM). The contractor shall develop and maintain a robust information assurance process to guide the system’s design, document IA decisions, and identify and implement IA requirements. The contractor shall assist the Government in the preparation of IA system documentation. The contractor shall implement operational system security control measures, and support IA certification testing. The contractor shall identify and use IA approved solutions to include IA approved operating systems, IA approved network devices, and IA approved SW.

3.1.7.5.2 IA Controls.

The contractor shall implement IA controls and take action to address inherent system vulnerabilities and weaknesses. The contractor shall ensure that all Port Protocol Service (PPS) not required in the operation of the system have been disabled or shut down and implement “Deny All, Permit by Exception (DAPE)” enforcement for all PPS not being used by the system. The contractor shall plan and implement IA e.g. using Security Technical Implementation Guides (STIG), and Government approved IA scanning tools, as required for Standalone, Mission Assurance Category (MAC) III Confidentiality Level (CL) of Sensitive, along with the corresponding IA Controls as identified in the Platform Information Technology (PIT) Standalone DIP.

3.1.7.5.3 IA Controls Review/DOD Information Assurance Certification and Accreditation Process (DIACAP) Implementation Plan Review (DIPR).

The contractor shall support an IA Control Review/DOD IA Certification and Accreditation Process (DIACAP) Implementation Plan Review (DIPR) held at least 10 working days prior to the Critical Design Review (CDR). The IA Control Review/DIPR shall address at a minimum:

a. Update on DIP

b. Update Preliminary Data Flow and Accreditation Boundary Diagram

c. Update on the HW/SW lists

d. Update on contractor IA training as applicable and the use of IA Scanning tools

e. Update on design and system integration schedule

3.1.7.5.4 IA Scan(s).

During system development the contractor shall periodically scan the system using the latest DOD approved scanning tools. The contractor shall maintain Information Assurance Vulnerability Alert (IAVA) compliance of the system baseline(s), and provide software patch updates to the Government as required throughout the life of the contract.

3.1.7.6 Test Readiness Review (TRR).

The contractor shall address the following key issues at the Test Readiness Review (TRR) prior to the start of each Government witnessed test event to ensure that documentation is complete, test facilities are ready and prior test(s) were successful or open issues have been addressed:

a. Test procedures comply with plans and descriptions, and are adequate to accomplish test requirements and satisfy requirements for verification.

b. Pre-test predictions and informal tests indicate testing will confirm performance.

c. New or modified test equipment, facilities, and procedure manuals required to accomplish planned test and evaluation are available and satisfy the test requirements.

3.1.7.6.1 TRR Entry Criteria.

a. Configuration of System Under Test (SUT) has been defined and agreed to. All interfaces have been placed under CM or have been defined IAW an agreed to plan and a Version Description Document has been made available to TRR participants.

b. All applicable functional, unit level, subsystem, system, and qualification testing has been conducted successfully.

c. All TRR specific materials such as Government approved test plans, cases, and procedures have been available to all participants prior to conducting the review.

d. All known system discrepancies have been identified and resolved IAW an agreed to plan.

e. All previous design review exit criteria and key issues have been satisfied IAW an agreed to plan.

f. All required test resources (people, facilities, test articles, test instrumentation) have been identified and are available to support required tests.

g. Roles and responsibilities of all test participants are defined and agreed to.

h. Interim Authority to Test (IATT) approved.

The following shall be reviewed during the TRR:

1. Evidence that the test management system as required under the contract is ready to accept the qualification tests and their results.

2. Evidence that the requirements in the SRD have been traced to Government approved test procedure RTM.

3. A list of outstanding problem reports, both external and internal cross-referenced to the CDRL items or development HW and SW products.

4. Test requirements.

5. Requirements changes pending.

6. Design changes since the last design review.

7. Test constraints based on previous testing or test HW limitations.

8. Test configuration (review of test article configuration verification and audit, instrumentation and support equipment).

9. Detailed test procedures including Government resources required to conduct the test.

10. Plans for collection, reduction, and analysis of the test data.

11. Calibration plan and status.

12. Problem areas and their resolution (proposed HW and SW changes).

3.1.7.6.2 TRR Exit Criteria.

The TRR is considered complete when:

a. Acceptance of the CDRL items

b. Government concurrence that all required TRR topics have been satisfactorily presented, discussed, and documented

c. Government concurrence that the IMS and detailed schedule are complete, accurate, and realistic

d. Status or closure for all discrepancy report items

e. Government approval to go to test

f. Acceptance of the RTM

g. Any outstanding test discrepancies have been documented and resolved or accepted

3.1.7.7 IA Certification Test and Evaluation (CT&E).

The contractor shall address the following IA events. The contractor shall notify the Government 30 days in advance if a scheduled IMS IA event is projected to slip.

3.1.7.7.1 Certification Test and Evaluation (CT&E) Readiness Review and IA Scan Reports.

The contractor shall support a Certification Test and Evaluation (CT&E) Readiness Review held no more than 7-14 working days prior to the CT&E Event. The CT&E Readiness Review shall address at a minimum:

a. Final IA scans of the system

b. Corrective actions taken and written analysis of any open deficiencies

c. Update of IA system documents

d. Finalization of travel…