N00024-18-R-6200_RFP_Amendment_1.docx

N0002418R6200

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 18-Jul-2018 03:00 PM to 30-Jul-2018 03:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

The following have been added by full text:

COMPOSITE RATE TABLE

Composite Rate Table

Year 1

Year 2

Year 3

Year 4

Year 5

Year 1

Year 2

Year 3

Year 4

Year 5

This table will be completed at the time of contract award and is inclusive of all labor categories for each calendar year.

The following have been modified:

NOTE D

1. The target cost and target fee pool amounts of the contract are set forth in the below table entitled Fee Schedule for LOE Items. The final target cost and target fee pool amounts shall be based upon the actual level of effort the Contractor provides as explained in paragraphs 2 through 5 of this Note D.

2. The final CPIF target cost for Items 0001 and (if option is exercised) 1001 shall be determined by multiplying the allowable hours worked, including subcontractor hours, not to exceed the hours authorized by Technical Instructions (TIs), under Items 0001 and (if option is exercised) 1001 by the rate in the TC Hourly Rate column including cost of money, of the preceding table. The final CPIF target fee for each Item shall be determined by multiplying the allowable hours worked, including subcontractor hours, not to exceed the hours authorized by TIs, under each Item by the rate in the TF Hourly Rate column of the preceding table.

3. The share ratio for the CPIF portion of the fee structure is fifty/fifty (50% Government/50% Contractor) for both underruns and overruns. The fee earned under the CPIF portion of the fee structure will be based on the total allowable cost incurred by the Contractor in comparison to the final target cost for each of the aforementioned CLINs. See paragraphs 4 and 5 of this Note D and the Incentive Fee clause (FAR 52.216-10) in Section I of this contract for further information on how the target cost and target fee are determined and the fee earned is calculated.

4. The following examples illustrate how the final target cost and target fee amounts for Items 0001 and (if option is exercised) 1001 are determined and how the actual fee earned thereof is calculated (all rates used in the following examples are from the preceding table):

Example 1 – Slight Underrun Actual Hours Worked Not to Exceed Hours Authorized by TIs. Example: 300,000 under CLIN 0001 Actual Cost Incurred: $31,000,000 (excluding Cost of Money) Rate A = $110 Rate B = $8

Final Target Cost: 300,000 X $ 110= $33,000,000 (excluding Cost of Money) Final Target Fee: 300,000 X $ 8 = $2,400,000 Actual Fee earned under CPIF portion of fee structure for CLIN 0001:

$2,400,000 + (50% X ($33,000,000- $31,000,000)) =$3,400,000 (Subject to the Minimum and Maximum Fees)

Total Cost plus Fee paid by Government for CLIN 0001:

$31,000,000 + 3, 400,000 = $34,400,000

Example 2 – Slight Overrun Actual Hours Worked Not to Exceed Hours Authorized by Tis. Example: 300,000 under CLIN 0001 Actual Cost Incurred: $34,000,000 (including Cost of Money) Rate A = $110 Rate B = $8

Final Target Cost: 300,000 X $ 110= $33,000,000 (including Cost of Money) Final Target Fee: 300,000 X $ 8 = $2,400,000 Actual Fee earned under CPIF portion of fee structure for CLIN 0001:

$2,400,000 + (50% X ($33,000,000 - 34,000,000)) = $1,900,000 (Subject to the Minimum and Maximum Fees)

Total Cost plus Fee paid by Government for CLIN 0001:

$34,000,000 + $1,900,000 = $35,900,000

Example 3 – Big Overrun Actual Hours Worked Not to Exceed Hours Authorized by Tis. Example: 300,000 under CLIN 0001 Actual Cost Incurred: $37,000,000 (including Cost of Money) Rate A = $110 Rate B = $8

Final Target Cost: 300,000 X $ 110= $33,000,000 (including Cost of Money) Final Target Fee: 300,000 X $ 8 = $2,400,000 Actual Fee earned under CPIF portion of fee structure for CLIN 0001:

$2,400,000 + (50% X ($33,000,000 - $37,000,000)) = $400,000 (Subject to the Minimum and Maximum Fees)

Total Cost plus Fee paid by Government for CLIN 0001:

$37,000,000 + $400,000 = $37,400,000

5. Separate Target Fee pools have been established at the CLIN level; each Task Order under Items 0001 and (if option is exercised) 1001 will have Target Fee pools further defined. The Government will complete the table at time of award. Accordingly, the cost performance on one (or more) of the Items in the above table cannot be used by the Contractor to offset the cost performance on one or more of the other CLINs in the above table. If, for example, the Contractor underruns Item 0001, this underrun cannot be used by the Contractor to offset an overrun on Item 1001.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

FOR

AN/BLQ-10 (Submarine Electronic Warfare System)

1.0 SCOPE

This Statement of Work (SOW) defines the efforts required to upgrade and modernize AN/BLQ-10, the Submarine Electronic Warfare System. These upgrades will cover Advanced Processor Builds/Technology Insertion (APB/TI) cycles TI20, TI22, and TI24. Efforts hereunder include program management, systems engineering, engineering, software development, logistics and supportability engineering, configuration management, hardware and software integration (including material procurement or fabrication, and integration of Government-Furnished Material (GFM), as applicable), testing, evaluation, and installation. The AN/BLQ-10 is designated for all submarine classes except existing ballistic missile submarines (SSBN). Production units shall be built for VIRGINIA, COLUMBIA, LOS ANGELES, SEAWOLF, and OHIO SSGN Class submarines.

The work shall be performed as specified in the Contract Schedule and as identified in individual Task Orders and Technical Instructions, as applicable. This procurement specifically includes the following:

· For TI20: Design, develop, test, and integrate an upgraded AN/BLQ-10 for installation on VIRGINIA and COLUMBIA new construction, and In-Service VIRGINIA modernization. This task shall include the preparation of platform variants, including installation drawings, for VIRGINIA and COLUMBIA new construction, and the In-Service VIRGINIA Modernizations.

· For TI22: Design, develop, test, and integrate an upgraded AN/BLQ-10 for installation on In-Service LOS ANGELES, SEAWOLF, and OHIO SSGN class submarines. This task shall include the preparation of platform variants, including installation drawings, for In-Service LOS ANGELES, SEAWOLF AND OHIO SSGN modernization.

· For TI24: Design, develop, test, and integrate an upgraded AN/BLQ-10 for installation on VIRGINIA and COLUMBIA new construction and In-Service VIRGINIA Modernization. This task shall include the preparation of platform variants, including installation drawings, for VIRGINIA and COLUMBIA new construction, and In-Service VIRGINIA Modernization.

· Provide “end-to-end” system engineering development, integration, testing, environmental qualification, and life cycle support for the AN/BLQ-10.

· Provide production capabilities for the timely production of new construction and modernization variant AN/BLQ-10 systems for delivery to modernization alteration installation teams and for delivery and installation on new construction ships.

· The initial delivery of each platform variant shall include all baseline engineering documentation, product lists, logistics support products, curriculum and support materials, spares, and INCO (installation and checkout) as necessary to provide the “as developed” product support, including Contractor personnel to provide training onboard the submarines.

· Support the management, oversight, and execution of evaluation plans and system level testing as part of the Command, Control Communications, Computers, Combat, and Intelligence (C5I) system platform integration design/build team for all platform variants.

· Define and depict the optimum balance of simulation and simulation equipment needed to execute subsystem level testing and integration.

· Define the interface baseline, including all requirements necessary, to connect to the Imaging System, Carry On Equipment, and the Submarine Warfare Federated Tactical System (SWFTS) network and share information.

· Participate in the integration efforts, including technology refresh/insertion planning and validation testing and integrations across SWFTS boundaries. Transition new technologies and capabilities to production and integrate into future APB/TI baselines.

· Support platform level Installation and Checkout planning requirements, including participation in Installation Integrated Project Teams, new construction and modernization planning meetings, and various reviews and working group meetings.

· Develop source material for Logistics Data, Interactive Electronic Technical Manuals (IETM), Interactive Courseware (ICW)/Computer Based Training (CBT) and Interactive Multimedia Instruction (IMI) using common authoring systems and formats to ensure efficient integration with SWFTS. This includes integrating source material as delivered by the interfacing shipboard-subsystems contractors for integration for a complete AN/BLQ-10 delivery.

· Support installation, field integration, repair, and refurbishment efforts as required.

· Procure spares/repair parts, technology refresh/insertion kits, pre-production/production hardware, engineering change kits, and associated hardware including spares.

· Include cybersecurity considerations in system design and engineering and correctly implement cybersecurity measures and design characteristics in the AN/BLQ-10 system. Provide support to the Government for all tasks required to achieve cyber security certifications and obtain Authority to Operate for all installed systems.

1.1. Navy Organization

Program Executive Officer, Submarines (PEO SUB) is the acquisition executive for this procurement. The Submarine Electromagnetic Systems Program Office (PMS435) is responsible for the acquisition, development, production, fleet introduction, and support of the AN/BLQ-10 for all classes of submarines and appropriate Joint Program Office efforts.

1.2. Program Background

In a joint collaborative development environment, the Submarine Combat Systems Program Office (PMS425) and PEO IWS 5 Advanced Science and Technology Office (ASTO) established a Combat Systems Research and Development Model to facilitate the rapid transition of advanced science and technology products to the fleet in Certified Operational Combat Systems. This concept was first instituted in acoustics systems with dramatic, successful results. A pre-requisite to achieving this success was the development of an open system architecture Commercial-Off-The-Shelf-based “landing pad” to introduce advanced development products. Additionally, open business practices and processes in an Integrated Product and Process Development culture were formed to allow for streamlined cooperative development strategies and efficient transition activities to apply Advanced Development, Advanced Processing Builds (APB) product integration with baseline systems.

Following on the success of the acoustic systems program, Advanced Submarine Support Equipment Program (ASSEP) was established to develop advanced submarine electronic warfare and image processing technologies. Developing these technologies is critical to improving submarine operational effectiveness in the increasingly dense and sophisticated electromagnetic environment caused by the proliferation of complex radar, communications, and navigation equipment of potential adversaries. Specifically, improvements are necessary for submarine electronic warfare to be effective in supporting the following mission areas: Joint Littoral Warfare, Joint Surveillance, Space and Electronic Warfare, Intelligence Collection, Maritime Protection, and Joint Strike.

The Submarine Electronic Warfare program consists of the inboard AN/BLQ-10 being procured under this contract, as well as the outboard components being procured separately, such as the AN/BSD-4 Multifunction Modular Mast (MMM), the Coherent Electronic Attack - Submarine (CEAS) payload, and other outboard devices as specified in the Performance Specification. AN/BLQ-10 shall have the flexibility to address rapid shifts in the threat environment, budget, capability requirements, and technology.

AN/BLQ-10 shall provide core tactical capabilities and hotel services for integration with national assets. When national assets are integrated into the AN/BLQ-10 under operational conditions, the AN/BLQ-10 system shall be operated at the same Top Secret (TS)/Sensitive Compartmented Information (SCI) level as the national assets. The AN/BLQ-10 system then becomes a national asset, which allows for the rapid deployment of national asset capability with the use of software apps. The Contractor shall be required to support interface design, full system testing and troubleshooting, and repair of AN/BLQ-10 systems in a TS/SCI configuration.

The Contractor shall provide development of electronic warfare technologies and support integration of development by third party. Development of these new technologies as required by this contract will require the Contractor to utilize real-world TS/SCI recorded data throughout the design, build, test, and acceptance stages. The Contractor shall be required to include progressively new technologies in each Technology Insertion build.

1.3. The Collaborative Development Environment

A collaborative development environment among a consortium of the Contractor, Navy Program Office(s), Navy laboratories, academia, and other industry partners is necessary to ensure continued success of the AN/BLQ-10 program. In addition, support for the “Open Source Initiative” will allow for the efficient integration of improvements into AN/BLQ-10.

Specifically, during development of advanced submarine electronic warfare technologies, the Contractor shall collaborate with PMS435, ASSEP, IWS5, the SWFTS Systems Engineering (SE) Integrated Product Team (IPT), the Technology Insertion IPT (TI-IPT), and other organizations as necessary for all aspects of the APB and Carry on Equipment. Advanced submarine electronic warfare technologies and developments include procurement of hardware, systems engineering, software development, testing, supportability, logistics products, training, program reviews, design reviews, management of baselines, and delivery, acceptance and field installation of the TI Upgrade kits across all platform variants.

1.4. Open Systems Architecture Approach

Naval Open Architecture is the confluence of business and technical practices yielding modular, interoperable systems that adhere to open standards with published interfaces. AN/BLQ-10 systems shall have an open system architecture and corresponding components. As part of this contract, the Contractor shall define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards. The Contractor shall develop, maintain, and use an Open System Management Plan to support this approach and shall demonstrate compliance with open systems architecture during all design reviews.

As part of an open system architecture approach, the Contractor shall identify to the Government all Commercial-Off-the-Shelf/Non-developmental Item (COTS/NDI) components as defined in IEEE STD 610.12-1990, their functionality and proposed use in the system, and provide copies of license agreements related to the use of these components for Government approval prior to use.

In addition, the Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated digital (or development) environment (IDE) and the ability to download artifacts throughout the term of the contract. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes. The Contractor shall provide 30 calendar days’ advance notice of any events, tests, or activity that the Government identifies as a specific item of interest.

2.0 APPLICABLE DOCUMENTS

The Contractor shall use the following specifications, standards, handbooks, and reference documents if marked mandatory in the table below. If a conflict exists between the stated and referenced requirements, the order of precedence shall be in accordance with FAR Clause 52.215-8.

2.1 Incorporation by Reference

All specifications, exhibits, drawings or other documents which are referenced in this contract, but are not attached hereto, are hereby incorporated by reference.

2.2 Issue of Documents

The following documents listed in the Department of Defense Index of Specification and Standards (DODISS) form a part of this SOW to the extent specified herein.

2.2.1 Government Documents

DoDM 5205.02M IMP-IMS-Guide DoD Operations Security Manual Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide N

Y

2.2.2 Non-Government Documents

3.0 GENERAL REQUIREMENTS

The work required by this contract shall be performed in accordance with the AN/BLQ-10 System Specification (Attachment J-5) and this SOW. Unless stated otherwise, the work required by this section 3.0 of the SOW is applicable to all requirements (engineering services and production) under this contract. This SOW contains the requirements applicable to the hardware and software upgrade and modernization of the AN/BLQ-10 Electronic Warfare (EW) System for Technology Insertion (TI) cycles TI20, TI22, and TI24. These upgrades and modernization requirements include the design, development, testing, systems and production engineering, technology insertion / refreshment, engineering services, field engineering services, and system support for the AN/BLQ-10 lifecycle.

There are specific circumstances during all phases of this contract including design, development, integration and testing that will require personnel to be cleared for access to (TS/SCI. The Contractor will need to support this TS/SCI level configuration in all phases of this contract, design, development, integration, test, production, installation, and field support.

3.0.1 Waiver of Requirements

Notwithstanding the requirements of any of the clauses or provisions of this contract, if the Contractor discovers during performance of the work under this contract that the requirements of any of the clauses or provisions are in conflict with security instructions issued to the Contractor by the Contracting Officer, the Contractor shall notify the Contracting Officer of the conflict. At such time, the Contracting Officer shall either (i) modify or rescind the conflicting security requirements or (ii) issue written instructions to the Contractor regarding compliance with the requirements of the conflicting clauses or provisions. Any waiver of compliance with the clauses or provisions of this contract issued by the Contracting Officer shall be in writing.

3.0.2 Security Clearance Requirements

In performance on this contract, the Contractor will:

· Require to maintain a Top Secret/ Sensitive Compartmented Information (TS/SCI) facility security clearance level. When national assets are integrated into the AN/BLQ-10 Electronic Warfare System under operational conditions, the AN/BLQ-10 system as a whole becomes TS/SCI. The contractor will support interface design, full system testing and troubleshooting, and repair of AN/BLQ-10 systems in a TS/SCI configuration.

· Require to maintain a level of safeguarding for classified information, material, and data at the TS/SCI security clearance level.

· Require COMSEC to accommodate the use of secure communications and will be required to maintain a COMSEC account for SIPRNET equipment, STE telephone equipment and associated keying material.

· Require access to non-SCI since this contract relates to the development and integration of submarine stealth technology to counter the threat of potential adversaries. Contractor’s personnel may be exposed to Non-SCI information material during troubleshooting operations of electronic warfare equipment aboard ship.

· Require to have access to Controlled Unclassified Information (CUI) with developers and integrators,

· Receive, store, and generate classified information. The contractor will assist in modernizing systems that are classified. Techniques to modernize this equipment, testing of this equipment and overall system performance could be classified and the subject to email and written reports. In this capacity, the contractor will generate and be in receipt of classified material.

· Fabricate, modify, or store classified hardware: The contractor will fabricate and modify classified component in support of this contract and then store this hardware until completion of all requirements

3.1 Contract Line Item Number (CLIN) Descriptions

3.1.1 CLINs 0001 and (IF OPTION EXERCISED) 1001: Engineering Services

(a) The Contractor shall provide services of qualified engineers to meet the requirements of the contract and achieve the AN/BLQ-10 System Performance Specification (Attachment J-5) and this SOW. Engineering services will be issued by Task Order and may be further specified in accordance with Section H clause, NAVSEA 5252.242-9115, TECHNICAL INSTRUCTIONS. The general objective of these efforts shall be the common development, modernization, maintenance and technology upgrade of the undersea electronic warfare systems or components which meet the performance requirements of the various U.S. Navy platform missions, where commonality offers the greatest cost and technical benefits.

The Contractor shall provide qualified engineers to perform engineering technical services tasks related to AN/BLQ-10 development, upgrade, technology insertions, or installation for all platform variants (VIRGINIA, SSBN/COLUMBIA, LOS ANGELES, SEAWOLF, and OHIO SSGN Class submarines). These services shall include, but are not limited to, software/hardware design, development, modification, integration and checkout, test and evaluation, training, repairs, installation and checkout, inspection, technical issues resolution, trade studies, engineering change development, documentation, logistics analyses, and troubleshooting. Technical services shall include software and hardware enhancements using emerging technologies, when feasible.

The Contractor shall provide qualified electrical/electronic, mechanical and software engineers and technicians where required for field engineering or maintenance repair to support the fleet. Field engineering and maintenance support shall include on-site assistance to submarine platforms for Electronic Warfare System troubleshooting and repair. The Contractor shall provide engineering and technical services related to platform variant delivery, installation, and maintenance VIRGINIA, SSBN/COLUMBIA, LOS ANGELES, SEAWOLF, and OHIO SSGN Class submarines.

The Contractor shall provide scientists or engineers to conduct studies and analyses of the AN/BLQ-10 Performance. The Contractor shall document the results of special studies and analyses.

3.1.2 CLINs 0002 and (IF OPTION EXERCISED) 1002: Incidental Material, Travel, and Subsistence Support for Engineering Services

The Contractor shall provide incidental material, travel, or subsistence to meet the requirements of the contract and achieve the AN/BLQ-10 System Performance Specification (Attachment J-5) and this SOW. The Contractor shall provide incidental materials, supplies and travel necessary for the completion of Task Orders (TOs) or Technical Instructions (TIs) issued in accordance with the Special Contract Requirement entitled "Technical Instructions" within the Government’s estimated amount. The Contractor shall be reimbursed for actual, allowable, and allocable costs less any discounts taken, plus applicable burdens, incurred in the performance of these items.

In order to minimize travel costs, the Contractor and its subcontractors at all tiers shall comply with DoD Joint Travel Regulations (JTR) in conducting travel of employees. In any instance in which recurring travel to one location for more than 180 days is planned for personnel at any tier, the Contractor shall obtain prior written approval from the Contracting Officer’s Representative (COR), and the request for approval shall include a cost comparison addressing permanent change of station and long-term temporary duty assignment (TDY).

(a) Travel time necessary for performance of such services shall be included in computing the man days of service. When services are performed at sea and the engineer(s) is unable to leave the vessel when work is completed, the remaining time aboard the vessel shall be considered travel time for purposes of computing the man days of services. However, the Contractor shall be paid for no more than one man day of service per calendar day for each engineer while in travel status.

(b) Passports, visas, inoculations and other medical requirements necessary for performance of engineering services shall be at the sole responsibility and expense of the Contractor.

3.1.3 CLIN 0005: Data Requirements

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A attached hereto.

3.1.4 CLIN 0006: Technical Data Rights (IF OPTION EXERCISED)

The Contractor shall remove or revise markings and legends and resubmit previously submitted Exhibit A CDRLs to be consistent with the rights provided for each item of Technical Data, Computer Software, and Computer Software Documentation in which the Contractor is willing to provide Government Purpose Rights or greater than Government Purpose Rights pursuant to Terms of Use Agreement (Attachment J-6).

3.1.5 CLINs 0003, 0004, and (IF OPTION EXERCISED) 1003, and 1004: AN/BLQ-10 EW Systems Production

The AN/BLQ-10 EW Systems Production requirements are specified in Section 4.0 of Section C.

3.2 Integrated Program Management

The Contractor shall designate a Program Manager who shall have responsibility for all aspects of this contract and the authority to commit the Contractor to specific courses of action. The Contractor shall perform all administrative, technical, and financial management functions required to support this effort and shall maintain the status, including all technical activities, problems or deficiencies, and recommended solutions. The Contractor shall be responsible for those activities assigned to subcontractors, to ensure the delivery of all supplies and services specified in this contract. The deliverable for this work shall be the Contractor's Progress, Status, and Management Report [CDRL A040].

3.2.1 Contractor Performance Management System

The Contractor shall establish, maintain, and use in the performance of this Contract, an integrated performance management system. The Contractor’s shall include the following management processes and systems in the established integrated performance management system: the integrated master schedule, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement. The deliverable for this work shall be included in the Integrated Program Management Report (CDRL A033).

3.2.2 Contract Work Breakdown Structure (CWBS)

The Contractor shall expand as necessary upon the Contract Work Breakdown Structure (CWBS) (CDRL A031) provided in Co-Plan for Procurement DD 2794 (Attachment JS-4) and Co-Plan for RDT&E DD 2794 (Attachment JS-5), the development and production Contract Cost Reporting Plans respectively, DD Forms 2794, to provide lower-level WBS indenture for specific Prime Mission Product elements under WBS 1.1, while remaining consistent with MIL-STD-881C. In particular, the Contractor shall provide level five and lower indentured functional elements for Common AN/BLQ-10 EW System Hardware Kits subsystems 1 through n associated with WBS elements 1.1.1.1.1 through 1.1.1.1.n; and for level four and lower indentured functional elements for AN/BLQ-10 EW System Computer Software Configuration Items (CSCI) 1 through n associated with WBS elements 1.1.2.1 through 1.1.2.n. The WBS elements added by the Contractor must be identical in both the development and procurement WBS plans, Co-Plan for Procurement DD 2794 (Attachment JS-4) and Co-Plan for RDT&E DD 2794 (Attachment JS-5). The CWBS in Co-Plan for Procurement DD 2794 (Attachment JS-4) and Co-Plan for RDT&E DD 2794 (Attachment JS-5) can be added to, but not rearranged or deleted without Government approval. The Contractor shall develop the CWBS dictionary based on the definitions in MIL-STD-881C. The CWBS shall be to the lowest level necessary to reach manageable units of functional tasks that reflect the work being performed while ensuring the correlation of these lower levels to the specification, contract line items, data items, and work statement tasks. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements specified in the SOW and system specification and translate them into a structure representing the products and services that comprise the entire work effort under the Contract.

3.2.3 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) The Contractor shall develop and maintain an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) using the DOD Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the Contract. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The IMP and IMS shall be included in the Integrated Program Management Report (CDRL A033).

3.2.4 Reserved

3.2.5 Post Award Conference (PAC)

The Contractor shall host and conduct a PAC with the Government within thirty (30) calendar days of contract award. The PAC shall be held no longer than two business days. The Contractor shall develop the PAC structure and agenda. Contractor shall make available read-ahead material and presentation material ten (10) calendar days prior to the PAC. The Contractor shall generate and record minutes, attendance list, and action items of the PAC, and produce copies of all information presented. The Conference shall be held at the Contractor’s facility. Representatives from each significant subcontractor on the Contractor's team shall attend. Minutes of the meetings shall be kept by the Contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and be distributed electronically. The deliverables for this work shall be Design Review Information Package (DRIP) (CDRL A023), Conference Agenda (CDRL A021), and Report, Record of Meeting/Minutes (CDRL A022).

The purpose of the PAC is as follows:

a) Review the Contract and Technical requirements

b) Discuss the roles and working relationships between the Contractor and the Government

c) Discuss the Contractor’s planned management effort and requirements verification process

d) Discuss required meetings, periodicity, and reporting requirements

e) Review the Contractor’s facility plans

f) Review the Contractor’s recommendations for AN/BLQ-10 EW System Integration and Test

g) Identify the Integrated Product Teams and their respective roles and responsibilities

h) Management and Contract Mechanics

1) Contract Administration

2) Team Introductions

3) Review GFI/GFP utilization plans

4) Integrated Baseline Review (IBR)

5) Cost and Software Data Reporting (CSDR)

6) Quarterly Program Reviews (QPR)

7) Quarterly Financial Reviews (QFR)

i) Technical Discussions

1) Requirements Traceability overview

2) Configuration Management processes

3) Major Technical Risk Areas

4) Design Review execution and schedule

5) Configuration Management processes

3.2.6 Integrated Baseline Reviews (IBRs)

The Contractor shall host an IBR no later than 180 calendar days after contract award. The Contractor shall work with the Government to develop the IBR agenda. The Contractor shall make available read-ahead material and presentation material ten (10) calendar days prior to the IBR. The Contractor shall generate and record minutes, attendance list, and action items of the IBR, and produce copies of all information presented. The prime Contractor shall lead the IBRs, with active participation by the Government. The IBR shall be held at the Contractor’s facility and shall be no longer than two business days. The deliverables for this work shall be Design Review Information Package (DRIP) (A023), Conference Agenda (CDRL A021), and Report, Record of Meeting/Minutes (CDRL A022).

Minimum IBR Entry Criteria

a) CWBS and CWBS Dictionary approved

b) Control Accounts established and Control Account Managers (CAMs) assigned

c) Initial IMS submitted in Integrated Program Management Report (CDRL A033).

As determined by the COR, the Contractor shall conduct an IBR assessment for any major change to the contract, after the exercise of significant contract options, and/or the incorporation of major design modifications. The Government will use IBRs throughout the life of the AN/BLQ-10 EW System program to facilitate and maintain mutual understanding of:

a) The scope of the Program Management Baseline (PMB) consistent with authorizing documents

b) Management control processes

c) Risks in the PMB associated with cost, schedules, and resources

d) Corrective actions where necessary

3.2.7 Progress Reporting

The Contractor shall prepare and deliver monthly Progress, Status, and Management Reports to provide status of all assigned tasks, report progress against milestones, and identify technical or schedule problem areas or risks along with recommendations for resolution Contractor's Progress, Status, and Management Report (CDRL A040). The Contractor shall provide monthly Contract Funds Status Report (CFSR) (A042). Reports shall be tailored to provide required Cost, Technical, and schedule information. The financial status shall include the Estimate at Completion (EAC), Actuals to Date (ATD), Estimate to Complete (ETC), amount funded and outlooks for when additional funding is required, as necessary, for tasks as identified in Technical Instructions.

3.2.8 Cost Reporting

The Contractor shall prepare and deliver Cost Reports to provide actual contract direct labor hours, direct labor costs, direct material costs, other direct costs, and actual burdening costs in the Cost Data Summary Reports (CDRL A032) and Functional Cost-Hour Reports (CDRL A030). Cost Reports shall be submitted at frequencies as specified in contract Cost And Software Data Reports (CSDR) plans DD Forms 2794, Co-Plan for Procurement DD 2794 (Attachment JS-4) and Co-Plan for RDT&E DD 2794 (Attachment JS-5). The Cost Reports shall meet the requirements in the development and procurement Cost Reporting Plans, DD Forms 2794, contract Co-Plan for Procurement DD 2794 (Attachment JS-4) and Co-Plan for RDT&E DD 2794 (Attachment JS-5), respectively, as modified by paragraph 3.2.2. The Contractor shall also deliver the raw accounting data from their accounting system of each TI-20, TI-22, and TI-24 manufacturing lot, at the completion of that lot, with the following modifications, in Enterprise Resource Planning (ERP) Reports (CDRL A072). It shall include an additional field identifying each database record with the corresponding lowest WBS element that those costs were reported under Cost Data Summary Reports (CDRL A032).

3.2.9 Subcontract Management and Control

The Contractor shall identify and monitor subcontractor technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor’s own established subcontract management techniques. The Contractor shall report subcontractor status in the Contractor's Progress, Status, and Management Report (CDRL A040).

For the purposes of this contract, a significant subcontractor is defined as a subcontractor or supplier whose effort is proposed to be 10 percent (10%) or greater of the total hours in Section B. In addition, a significant subcontractor is any subcontractor whose production efforts exceed $5 million per production year .However, if the minor subcontractors propose over 20% of the total hours, all proposed subcontractors will be considered significant.

3.2.10 Program Risk Analysis

The Contractor shall identify significant program issues and raise them to the Program Office so that they can be monitored and resolved. The Contractor shall perform a continuing analysis of program, technical, performance, cost and schedule risks following the AN/BLQ-10SEP -Systems Engineering Plan (SEP) for Electronic Warfare (EW). Risks shall allow for the identification of both technical and non-technical risks, risk assessment, the development of appropriate actions and mitigations to effectively manage these risks, and tracking of potential impacts to cost, schedule, or performance impacts. The analysis shall identify the risks associated with each area, identify the impact of each risk on the overall program, and proposed approaches for reducing identified risks. Risk analysis status shall be reported in the Contractor's Progress, Status, and Management Report [CDRL A040] and presented during Program and Technical Reviews.

3.2.11 Program Reviews

The Contractor shall prepare agendas for Contractor-hosted meetings, program reviews, IPTs and all other meetings/reviews. The agendas shall be reviewed jointly between the Government and Contractor and distributed electronically via e-mail by the Contractor. Minutes of the meetings shall be kept by the Contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and be distributed electronically. The deliverables for this work shall be Conference Agenda (CDRL A021), and Report, Record of Meeting/Minutes (CDRL A022). The Contractor shall conduct quarterly program reviews (QPR) and Quarterly Financial Review (QFR) every three (3) months, at its facility or alternate Government facility for a period not to exceed one (1) day. An informal “read-ahead” brief shall be provided electronically to the Government 10 calendar days prior to the review.

3.2.11.1 Quarterly Program Review (QPR)

The purpose of the QPR is to ensure the Contractor’s approach and progresses are technically sound, meet the requirements, and are mutually understood and properly documented. At each QPR, the Contractor shall report status, issues, risks, and recommendations for the following items (at a minimum):

a) Schedule progress against the IMS (3 month history and 6 months projected)

b) Contract deliverables completed and projected (3 month history and 6 months projected)

c) Design and technical issues

d) Test and evaluation activities, plans, results

e) Logistics source data…