N00024-18-R-5200-0005.docx

N0002418R5200

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 29-Jun-2018 03:00 PM to 13-Jul-2018 03:00 PM.

The depository location (See Section L) has been added.

SECTION B - SUPPLIES OR SERVICES AND PRICES

The following have been deleted:

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

1.0 Scope

This Statement of Work (SOW) establishes the Design Agent and Engineering Services requirements that the Contractor shall accomplish under this contract to support the Cooperative Engagement Capability (CEC) System. This SOW describes the required support of CEC systems and software baselines outlined in the Technical Data Package (TDP).

As the CEC Design Agent, the Contractor shall design, develop, integrate, test, and maintain system capabilities for all baselines applicable to the CEC System to support the evolution and maintenance of the CEC System and Single Source Library. The Contractor shall deliver the source code, objects, scripts, and executables required to build, install, load, operate, maintain and update the application, as well as provide Integrated Logistics Support (ILS) source material and applicable documentation for the capability.

The Contractor shall furnish all efforts and resources necessary (including but not limited to labor, materials, travel, and facilities) to accomplish the requirements described in this SOW. The Contractor shall provide the development environment infrastructure that supports the complete CEC System development, verification, and support. The Contractor shall maintain the CEC hardware and Software Development Environment (SDE) and testing infrastructure and provide requisite facility and security infrastructure to support existing CEC baselines. Support provided by the Contractor under this contract shall include Program Management, Systems Engineering, Software Development, System Tech Refresh and Obsolescence Update Support, Test and Analysis, Quality Assurance (QA), Configuration Management (CM), ILS, Reliability and Maintainability (R&M), System Safety, System Security, and Cost Estimation.

1.1 Background

The CEC program provides a composite track management and sensor netting capability in support of Integrated Fire Control that significantly improves strike force air and missile defense capabilities by combining measurement data from strike force air search sensors on CEC-equipped units into a single, integrated real-time, composite track air picture. The CEC sensor netting system improves Naval Carrier Strike Groups and Expeditionary Strike Groups Area Air Defense capabilities.

1.1.1 CEC Evolution

PEO IWS 6.0 is currently partnered with the Government Science and Technology (S&T) and Research and Development (R&D) communities to develop enabling technologies that address warfighter needs. An overview of ongoing S&T efforts is provided as GFI. The Government S&T and R&D communities will oversee the development of technologies in these areas until they are mature enough to be inserted into the CEC program. Technologies developed by these communities must demonstrate TRL 6 functionality prior to transitioning to CEC. Once the transition TRL is demonstrated, the CEC Design Agent will oversee the maturation and testing of these technologies until they are fully integrated into the CEC system and fielded to the warfighter at TRL 9.

2.0 Applicable Documents

The following documents are applicable to the tasks described herein and are for use by the Contractor in the fulfillment of those tasks as described. These documents may be updated periodically; therefore, the Contractor shall comply with the latest versions unless instructed otherwise by the Government. In the event of any conflict between this SOW, the System Specification, and the documents cited therein, the order of precedence defined in FAR 52.215-8 shall govern.

2.1 CEC Related Documentation

CEC Documentation is listed in the documentation tree, provided as GFI.

2.2 NAVSEA and PEO IWS Regulations, Directives, and Instructions

Including PEO LS, AC2SN CMP and CTN addendums

23 May 2014

Reliability and Maintainability Engineering (R&ME) Manual

2.3 Military Standards (MIL-STD)

2.4 Joint Chiefs of Staff, Department of Defense (DoD) and DoD Services Documents

2.5 Handbooks

2.6 Non-Government and Commercial Standards, Specifications and other applicable publications

Processes, Software Development, Acquirer-Supplier Agreement, 1 September 1995

2.7 Availability of Documents

Copies of military specifications and standards and DoD adopted non-Government standards may be obtained as described in Federal Acquisition Regulation (FAR) 52.211-1 through 52.211-4. Copies of non-Government publications not listed in the Department of Defense Single Stock Point (DODSSP) for Military Specifications, Standards and Related Publications may be obtained from the respective industry association. Requests for copies of documents not available from either source should be directed to the Procuring Contracting Officer (PCO).

3.0 Requirements

The requirements of this contract are organized as follows: Section C, paragraph 3.1 describes Common tasks ; Section C, paragraph 3.2 describes Level of Effort (LOE) tasks; and Section C, paragraph 3.3 describes completion tasks.

3.1 Common Tasks (LOE and Completion) (All CLINs)

The Common tasks described herein apply generally across efforts under all line items of this contract, identified in either LOE Technical Instructions (TI) or completion tasks. Additionally, the LOE and completion tasks have differing functional area requirements that are addressed separately in paragraphs 3.2 and 3.3. The Common tasks under this contract include the following:

3.1.1 Program Management (All CLINs)

The Contractor shall establish and maintain program management practices that provide the Government visibility into the Contractor’s organization and techniques used in managing the program, specifically subcontractor and data management. The Contractor shall establish and maintain a program management process that ensures all work associated with this contract is clearly and efficiently accomplished and meets all technical objectives within the established contract cost and schedule baselines. The Contractor shall communicate and document its plans, processes and approaches to meet all program requirements. The Contractor shall use a metrics-based management approach for planning, scheduling, technical, cost, risk/opportunity, and quality monitoring/reporting with program-wide visibility of planned versus actual efforts under this contract. The Contractor shall provide a Data Accession List (DAL). The Contractor shall provide and update the Contract Work Breakdown Structure (CWBS) throughout the life of the contract in accordance with MIL-STD 881C. The CWBS shall detail all work to be performed under this contract.

The Contractor shall prepare and deliver a monthly progress and status report, including expenditure profiles. Monthly reports shall be submitted with noted deficiencies in any Government Furnished Information or equipment to meet the requirement.

The Contractor shall continually evaluate planned and ongoing efforts, including design, development, analysis, and test, and search for areas for process improvement. The Contractor shall provide feedback to the Government at Quarterly Program Reviews (QPR) describing proposed methods, processes, procedures, and courses of action to improve business or engineering efforts and solicit feedback from the Government to ensure that the Government is receiving best value. The Contractor shall deliver a Government Furnished Information Deficiency Report.

CDRL A001 – DATA ACCESSION LIST

CDRL A002 – CONTRACT WORK BREAKDOWN STRUCTURE

CDRL A003 – CONTRACTOR’S PROGRESS AND STATUS REPORT, MONTHLY PROGRESS AND STATUS REPORT

CDRL A004 – GOVERNMENT FURNISHED INFORMATION DEFICIENCY REPORT

3.1.1.1 Program Manager (All CLINs)

The Contractor shall appoint one individual as Program Manager (PM) for the management of all efforts under the contract. The PM shall ensure all work conducted within this contract is planned and executed in a manner that achieves all management, technical, logistics, budget, and schedule objectives.

3.1.1.2 Technical Director (All CLINs)

The Contractor shall appoint one individual as the Technical Director for the technical management of all efforts under this contract. The Technical Director shall oversee all technical aspects of the CEC Program to ensure that all technical requirements are met and that proper resources are available to ensure the successful completion of all program milestones. This individual shall act as the Contractor’s technical liaison when collaborating with other Government programs and their respective program offices.

3.1.1.3 Coordination with Other Organizations (All CLINs)

The Contractor shall provide CEC program support by coordinating with other organizations (including PEO IWS 1.0, 2.0, 4.0, 7.0, 9.0, 10.0, 11.0, Naval Air Systems Command (NAVAIR), United States Marine Corps (USMC), ONR, Naval Surface or Undersea Warfare Centers (NSWC or NUWC), other prime contractors and subcontractors) involved in the development, verification, support, maintenance, production, and training for CEC software and hardware and organizations (or their cognizant prime contractors) developing or having interfaces with CEC systems.

3.1.1.3.1 Coordination with Other Organizations – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall participate in CEC-related Integrated Product Teams (IPT) and working groups, and supply CEC-related technical information. Other organizations, IPTs, and working group members may include Government personnel or contractor personnel, which may require the establishment of Memorandum of Agreement (MOA) with contractor organizations.

The Contractor shall maintain an interface with Government project personnel; the Technical Direction Agent (TDA), Johns Hopkins University/Applied Physics Laboratory (JHU/APL); NSWC Corona Division; NSWC Crane Division; NSWC Dahlgren Division; NSWC Port Hueneme Division; Space and Naval Warfare Systems Command (SPAWAR); Marine Corps Logistics Command (MCLC); PEO Land Systems, Program Manager for Air Command and Control and Sensor Netting (PM AC2SN), Marine Corps Systems Command; Naval Air Systems Command, interfacing programs and contractors; users; sponsors; software quality and logistics; CM personnel; and the Independent Verification and Validation (IV&V) and Test and Evaluation Agents throughout the execution of this SOW.

3.1.1.3.2 Coordination with Other Organizations – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For all LOE tasks, the Contractor shall participate in meetings and meet with the organizations outlined in Section C, paragraph 3.1.1.3.1 as directed by each approved TI.

3.1.1.4 Metrics Requirements and Reporting (All CLINs)

The Contractor shall develop, propose, and track metrics for program management, including cost, schedule, and performance.

3.1.1.4.1 Metrics Requirements and Reporting – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For all completion tasks, the Contractor shall develop and maintain a metrics database. The metrics shall be linked to Earned Value reporting requirements and those applicable to task exit criteria. The Contractor shall apply metrics to the entire process including management, planning, scheduling, technical, cost, risk/opportunity, and quality monitoring/reporting. Metrics shall be established at the Post-Award Kick-Off Meeting and the Contractor shall report on the metrics at Program Management Reviews (PMR).

The metrics reports shall include both underlying data and a graphical representation of the metrics. The metrics reports shall contain risk/opportunity alert levels to support risk/opportunity management assessment. The Contractor shall analyze the metrics collected. These analyses shall identify risks and opportunities to be addressed by the risk and opportunity management program. The reports shall also include a narrative of any important issues that will explain the behavior of the metrics.

CDRL A003 – CONTRACTOR’S PROGRESS AND STATUS REPORT, MONTHLY PROGRESS AND STATUS REPORT

CDRL A005 – TECHNICAL REPORT – STUDY/SERVICES, SOFTWARE METRICS REPORT

3.1.1.4.2 Metrics Requirements and Reporting – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For all LOE tasks, metrics established under the completion tasks identified and established in Section C, paragraph 3.1.1.4.1 shall be reported as directed by each approved TI.

CDRL A003 – CONTRACTOR’S PROGRESS AND STATUS REPORT, MONTHLY PROGRESS AND STATUS REPORT

CDRL A005 – TECHNICAL REPORT – STUDY/SERVICES, SOFTWARE METRICS REPORT

3.1.1.5 Earned Value Management System (EVMS) (CLINs 0001-0002, 1002, 2002, 3002, 4002) The Contractor shall establish, maintain and use in the performance of this contract, an integrated performance management system. Central to this integrated system shall be a validated Earned Value Management System (EVMS) that conforms with the requirements of DFARS 252.234-7002 and the EVMS guidelines contained in ANSI/EIA-748.

3.1.1.5.1 EVMS – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, in establishing the integrated performance management system, the EVMS shall be linked to and supported by the Contractor's management processes and systems to include the Integrated Master Schedule (IMS), CWBS, change management, material management, procurement, cost estimating, resource loading and accounting. The Contractor shall ensure that the correlation and integration of these systems and processes provide the Government early indication of cost and schedule problems, and their relation to the completion of contract requirements. Required variance reporting will be presented at the PMR, as described in Section C, paragraph 3.1.1.11.1.3.

CDRL A006 – INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

3.1.1.6 Integrated Program Management Report (IPMR) (All CLINs) The Contractor shall develop, implement, manage to, update, and maintain a single, contract-wide Integrated Program Management Report (IPMR) for all CLINs. The Contractor shall clearly delineate between completion tasks and LOE tasks (unplanned work) in the IPMR per ANSI/EIA-748. All Contractor cost and schedule information delivered or presented at program reviews shall originate from the IPMR. The Contractor shall ensure that the IPMR is fully automated and shall submit it to the Defense Cost and Resource Center website (http://dcarc.cape.osd.mil).

3.1.1.6.1 Integrated Program Management Report (IPMR) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall clearly delineate between completion tasks and LOE tasks (unplanned work) in the IPMR per ANSI/EIA-748.

CDRL A006 – INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

3.1.1.6.2 IPMR – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall update the contract IPMR for unplanned LOE work identified as directed by each approved TI.

CDRL A006 – INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

3.1.1.7 Schedule Management (All CLINs)

The Contractor shall develop and maintain an IMS by logically networking detailed program activities including: Drawing Schedule, Software Production Schedule, Testing Schedule, planned events and milestones, accomplishments, and activities from contract award to the completion of the contract for completion tasks and LOE tasks (unplanned work). The Contractor shall update the IMS as new tasks are added via approved TI over the course of the contract. The Contractor shall include in the IMS the efforts of all activities, including Government, Contractor, industry, supplier, and subcontractor, and shall present a current, integrated view of the contract that is consistent with resource plans, IPMR, and other approved documentation. The Contractor shall schedule Technical Reviews and Audits in the IMS. The IMS shall be aligned to the PEO IWS 6.0 IMS, provided as GFI. The Contractor shall provide an IMS and a risk adjusted IMS as part of the IPMR.

The IMS shall be detailed sufficiently such that critical and high-risk efforts are identified and planned realistically to assure executability.

CDRL A006 – INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

3.1.1.8 Performance Measurement Baseline (PMB) (All CLINs)

The Contractor shall establish a PMB.

3.1.1.8.1 Integrated Baseline Review (IBR) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall conduct an Integrated Baseline Review (IBR) within six (6) months of contract award with active Government participation for the purpose of evaluating the risks and opportunities inherent in the contract’s planned Performance Measurement Baseline (PMB). The IBR shall verify that the Contractor is using a reliable PMB which includes the entire scope of the effort, is consistent with contract schedule requirements, and has adequate resources assigned. The prime Contractor shall lead the subcontractor IBRs, with active participation by the Government.

3.1.1.8.2 Rolling Wave Planning – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) As TIs are executed and LOE tasks are planned, the Contractor shall conduct Rolling Wave Planning events with active Government participation for the purpose of evaluating the risks and opportunities inherent in adding work to the contract’s planned PMB as directed by each approved TI. Rolling Wave Planning events are dependent on approval of TIs, but may be held every six (6) months. The Rolling Wave Planning events shall verify that the Contractor is using a reliable PMB that includes the entire scope of the new effort, is consistent with contract schedule requirements, and has adequate resources assigned to the effort, including assessment and recommendation of Trouble Report (TR) backlog burndown opportunities. The prime Contractor shall lead the subcontractor Rolling Wave Planning events, with active participation by the Government.

3.1.1.9 Cost Reporting (All CLINs)

The Contractor shall provide cost reporting as defined below.

3.1.1.9.1 Cost Reporting – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall generate and provide the Contract Cost Data Reports (CCDR): Cost Data Summary Report (CDSR) (DD Form 1921), Functional Cost-Hour Report (DD Form 1921-1), and Sustainment Functional Cost-Hour Report (DD Form 1921-5) in accordance with DoD 5000.4-M-1 and DoD 5000.4-M-2.

CDRL A007 – COST DATA SUMMARY REPORT (DD FORM 1921)

CDRL A008 – FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-1)

CDRL A009 – SUSTAINMENT FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-5)

3.1.1.9.2 Cost Reporting – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall provide inputs to the reports identified in Section C, paragraph 3.1.1.9.1 as unplanned work is planned and baselined as directed by each approved TI.

CDRL A007 – COST DATA SUMMARY REPORT (DD FORM 1921)

CDRL A008 – FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-1)

CDRL A009 – SUSTAINMENT FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-5)

3.1.1.10 Cost Estimation (All CLINs)

The Contractor shall provide Life Cycle Cost (LCC) projections, cost and schedule estimates, and reporting as described in the following paragraphs.

3.1.1.10.1 Life Cycle Cost Model and Baseline – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall develop and maintain a single LCC model that includes detailed cost estimates for each CEC product configuration in base year dollars and then-year then year dollars. The Contractor shall deliver the LCC model in a LCC and Independent Schedule Assessment (ISA) Report. The LCC model will be used to identify LCC initiatives and impacts to the CEC Program cost as changes to the baseline are implemented. The LCC model shall include all Contractor costs associated with the development, production, operations and sustainment, and disposal of the CEC system over its full life. Identifying LCC initiatives require establishing a cost baseline, identifying cost drivers within the baseline, developing specific reduction initiatives, and developing metrics which measure progress towards achieving established thresholds and objectives. The LCC model shall support trade studies and LCC Reduction efforts at the total program level, system level, and major sub-systems level. The Government will provide LCC Baseline information for product configuration, host platform, and system fielding schedule as GFI. The LCC model shall follow the element structure from the approved Contractor Work Breakdown Structure (CWBS) in CDRL A002.

The Contractor shall identify the top ten cost drivers to the lowest level of the LCC element structure. In addition, the Contractor shall identify the factors contributing to those cost drivers at the PMR. Upon receipt of a written request from the Contractor, the Government will provide specific standard cost factors, mission hour data, equipment installation costs, and other Government controlled LCC factors.

The Contractor shall document the LCC baseline cost estimate as well as LCC estimates reflecting potential LCC reduction initiatives in the LCC and ISA Report. The report shall include all assumptions, type of analyses performed, methodologies, equations and algorithms used. The Contractor shall include in the report cumulative changes and modification documents and support change costs. The report shall describe LCC element costs by fiscal year and by LCC element structure at the total program and system level. The report shall identify major changes in the LCC Baseline since the previous report and the rationale for the changes. The report shall consider current End Item R&M projections at the system and subsystem levels; LCC initiative reduction efforts to include baseline cost estimates, proposed initiatives and the cost to implement them, projected cost avoidance by year, metrics, and a development schedule; Baseline software requirements changes or refinements; Trouble Reports pending resolution; number and duration of Baselines to be maintained; hardware maintenance for CEC Land Based Test Sites (LBTS); and any other factors that would impact cost and schedule.

CDRL A0010 – LIFE CYCLE COST (LCC) AND INDEPENDENT SCHEDULE ASSESSMENT (ISA) REPORT

3.1.1.10.2 Life Cycle Cost Model and Baseline – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall update the LCC ISA Report as directed in Section 3.1.1.10.1 as directed by each approved TI.

CDRL A010 – LIFE CYCLE COST (LCC) AND INDEPENDENT SCHEDULE ASSESSMENT (ISA) REPORT

3.1.1.10.3 Cost and Schedule Estimates for Engineering Change Proposals (ECP) (All CLINs) The Contractor shall provide detailed cost and schedule estimates for all products or services provided by the Contractor pertaining to Engineering Change Proposals (ECP) submitted to the Change Control Board (CCB). Schedule estimates shall include updates of associated technical documentation, logistics products, and maintenance software.

CDRL A010 – LIFE CYCLE COST (LCC) AND INDEPENDENT SCHEDULE ASSESSMENT (ISA) REPORT

3.1.1.10.4 Cost and Schedule Estimates for New CEC Functionality/Interfaces – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, The Contractor shall provide cost and schedule estimates for new CEC interfaces and related functionality as directed by each approved TI. The cost estimates shall be separated from other Baseline costs to support the distribution of charges to programs requiring interfaces with CEC or platform managers requiring new interfaces or functionality.

CDRL A010 – LIFE CYCLE COST (LCC) AND INDEPENDENT SCHEDULE ASSESSMENT (ISA) REPORT

3.1.1.11 Meetings, Briefings, Presentations, Reviews and Audits (All CLINs) The Contractor shall participate in and host CEC program meetings, briefings, presentations, reviews and audits as required in the paragraphs below.

3.1.1.11.1 Meeting, Briefing, Presentations, Review and Audits – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall support and attend program meetings, including preparing presentation material, providing subject matter expertise, sharing of pertinent data and work products, and performing analyses. The location of the meetings may include Government facilities, Contractor’s facilities, other locations designated by the Government, or via teleconference or Video Teleconference (VTC). In-person meetings, teleconference, and VTC meetings may be held up to the SECRET level (See Section C, paragraph 3.3.2.2 for TOP SECRET requirements). When meetings are held at the Contractor’s facilities, the Contractor shall provide adequate conference space to accommodate the planned attendance and provide administrative support as determined by the purpose and nature of the meetings. The Contractor shall conduct and participate in Technical Reviews and Audits as described in Section C, paragraphs 3.1.2.13, Technical Reviews and Audits – Completion and its subparagraphs and 3.1.2.14 Technical Reviews and Audits – LOE and its subparagraphs.

3.1.1.11.1.1 Post-Award Kick-off Meeting – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall conduct a contract-wide Post-Award Kick-off Meeting no later than two (2) weeks after contract award. At that meeting, the Contractor shall provide a detailed briefing on its management, contract execution, and transition strategies, and the Contractor shall coordinate with the Government to develop or update charters for IPTs. The Contractor shall plan for a three-day Post Award Kick-off Meeting.

CDRL A0011 – PRESENTATION MATERIAL

3.1.1.11.1.2 Contract Requirements Review – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, within sixty calendar days after the start date of each completion task, the Contractor shall host a Contract Requirements Review (CRR) at the Contractor’s facility for a period not to exceed five business days. This review shall address contract requirements and the Contractor’s plans to implement and accomplish those requirements. The Contractor shall accomplish the following actions as part of the CRR:

· Identify and prioritize risks/opportunities and drivers, and review the Contractor’s risk/opportunity management approach

· Review Government Furnished Property (GFP), GFI, or other Government resources required for contract performance as stated in Attachment 2 GFI List and Attachment 3 GFP List

· Review the Integrated Product and Process Development (IPPD) team structure and responsibilities

· Review the Systems Engineering Management Plan (SEMP), Software Development Plan (SDP), Test Plan, Risk/Opportunity Management Plan, Configuration Management Plan (CMP), Quality Assurance Program Plan, R&M Program Plan, System Safety Program Plan (SSPP), Systems Security Management Plan (SSMP), Packaging, Handling, Storage, and Transportation (PHS&T) Plan, and CWBS

· Review the requirements and process (e.g., Technical Review entry and exit criteria contained or referenced in the SEMP) for authorizing Contractor efforts for the CEC System Baselines development

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.1.3 Program Management Review (PMR) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall conduct a monthly PMR in person, via teleconference, or via video telecommunications. The PMR shall last no more than five days per month. The Contractor shall provide a summary of the status for each task in a Progress, Status and Management Report. The report shall contain the following main sections: Summary, Accomplishments, Current Status, Problem Areas, Risks/Opportunities, Issues, and Mitigation, Cost and Schedule Data, and Future Plans. The reporting period shall cover the duration of the contract. The PMR shall address, at a minimum:

· Status of significant/major design, development, testing, qualification, certification, production, logistics efforts, system accreditation status, and/or issue resolution

· Modular Open System Architecture (MOSA) and Risk/Opportunity assessment

· Environmental, Safety and Occupational Health (ESOH) hazard status

· Status of significant program events (e.g. Program Reviews)

· Schedules for individual tasks, delivery orders, and equipment production/deliveries

· Program management metrics

· Software metrics as described in Section C, paragraph 3.1.1.4.1

· Technical Interchanges, including sidebars and splinters

· TPM results

· Task Summary Report

· Resolution status of obsolescence issues and their associated risk

· Completion task status updates

· TI status updates

· Failure Reporting

· Action item status

CDRL A003 – CONTRACTOR’S PROGRESS AND STATUS REPORT, MONTHLY PROGRESS AND STATUS REPORT

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.1.4 Technical Interchange Meeting (TIM) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall hold Technical Interchange Meetings (TIM) prior to technical reviews defined in the NAVSEA Technical Review Manual (TRM). During these TIMs, the Contractor shall work with the respective technical IPTs and/or Working Groups to focus on specific engineering discussions, including interface designs, MOSA, Cybersecurity, and training materials. TIMs shall also include meetings such as the CM Summit Meeting and Data Analysis Working Group (DAWG) meetings.

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.1.5 Quarterly Program Review (QPR) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall support Quarterly Progress Reviews (QPRs), which shall consist of face-to-face meetings to provide the Government with a detailed assessment of the Contractor’s progress. The QPR agenda items shall include management, technical support services (if any), risk/opportunity management, ILS, administrative, assurance of compliance with contract requirements, program status, funding, problem identification and resolutions. The Contractor shall address actual-versus-expected performance of each of the aforementioned agenda items. The Contractor shall prepare presentation materials for each review and deliver them to the Government.

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.1.6 Software Baseline Definition Review (BDR) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall support the Software Baseline Definition Review (BDR) by coordinating with the Government to help define the scope of the meeting, providing current SDPs, and participating in planning discussions. The Contractor shall provide presentations to support discussion for ongoing software and capabilities development. The annual BDR shall be held prior to the start of development for each CEC software baseline to establish the program SDP. The meeting shall reaffirm ongoing software baselines development and fielding (completion tasks) as well as define the composition of the next program software baselines (LOE tasks). The meeting shall solicit guidance from the CEC Program Office and input from external element stakeholders. The forum shall facilitate collaboration from all CEC activities to develop approaches to satisfy program obligations.

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.2 Meeting, Briefing, Presentations, Review and Audits – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the requirements of Section C, paragraphs 3.1.1.11.1 and 3.1.1.11.1.1 through 3.1.1.11.1.6 apply as directed by each approved TI.

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.2.1 Post-Award Kick-off Meeting – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall support additional kick-off meetings following exercise of contract options or issuance of TIs as directed by each approved TI.

CDRL A011 – PRESENTATION MATERIAL

3.1.1.11.3 Integrated Product and Process Development (IPPD) (All CLINs) The Contractor shall support and collaborate with the Government, other contractors, and other applicable organizations in the performance of the efforts required by this contract.

3.1.1.11.3.1 Integrated Product and Process Development (IPPD) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor and its subcontractors shall implement an IPPD team approach for the performance of this contract using Capability Maturity Model Integration (CMMI) Maturity Level 5 methodologies as referenced in CMMI-DEV+IPPD V1.2 or higher. The Contractor shall fully support the Navy’s Peer Review Team and IPT processes. The Contractor shall participate in the applicable Working Groups, IPTs, and Boards as described in the CEC SEP. The Contractor shall all support temporary or new working groups as deemed necessary by the Government to address specific processes or products required for the development, support/maintenance, technology management and training for CEC hardware and software. The Contractor shall attend the CEC IA Working Group. The Contractor shall propose cybersecurity changes based on Information Assurance Vulnerability Alerts (IAVA) scans and implement changes as directed by the Government. Contractor participants shall be subject matter experts in the appropriate areas and have sufficient decision making authority to expedite process and product changes within the scope and terms of this contract. Efforts shall include activities such as contributing to meetings, preparation of presentation material, providing subject matter expertise, sharing of pertinent technical data and work products, sharing of cost data (as appropriate) and performing design analyses and trade studies for the respective Contractor’s area(s) of responsibility and providing recommended Plan of Action and Milestones (POAM). The Contractor shall obtain written Government authorization from the COR prior to chartering new IPTs . All IPTs shall deliver work products to Government.

Neither the IPT nor an individual member thereof is authorized to change the terms and conditions, scope, or any aspect of this contract. Nothing in the IPPD process shall relieve the Contractor of the responsibility to meet the contract requirements.

3.1.1.11.3.2 Integrated Product and Process Development (IPPD) – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall provide support to the IPPD process as directed by each approved TI.

3.1.1.12 Risk and Opportunity Management (All CLINs)

The Contractor shall develop, update, maintain, and implement a formal joint Contractor/Government Risk/Opportunity Management program in accordance with the Risk Management Plan for Program Executive Office Integrated Warfare Systems Command and Control Directorate (PEO IWS 6.0) Revision 5.0, November 2014. The Contractor shall track risks and opportunities for both Completion and LOE tasks.

3.1.1.12.1 Risk Management – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall describe the procedures to be used for managing areas of risk and opportunity in a Risk/Opportunity Management Plan. The risk/opportunity management methodology shall: 1) Allow anyone involved in the CEC program to identify risks/opportunities, 2) Complement the IPT structure, 3) Provide for monthly reporting, and 4) Identify Contractor Risk/Opportunity Managers responsible for evaluation of, mitigation planning for, and status reporting of program risks and opportunities.

The Risk/Opportunity Management Plan shall include an Risk/Opportunity Management Tracking database. The Contractor shall update and manage the Risk/Opportunity Management Tracking database to include new and modified CEC risks/opportunities and mitigation/capture plans.

CDRL A0012 – CONTRACTOR’S RISK MANAGEMENT PLAN, RISK/OPPORTUNITY MANAGEMENT PLAN

3.1.1.12.2 Risk/Opportunity Management – LOE Tasks (CLINs 0100, 0300, 1100, 1300, 2100, 2300, 3100, 3300, 4100, 4300) For LOE tasks, the Contractor shall update and manage the Risk Management Tracking database to include new and modified CEC risks and mitigation plans as directed by each approved TI.

CDRL A012 – CONTRACTOR’S RISK MANAGEMENT PLAN, RISK/OPPORTUNITY MANAGEMENT PLAN

3.1.1.13 Subcontractor Management and Control (All CLINs)

The Contractor shall flow down to its subcontractor(s) all documents and requirements applicable to this SOW that are required to accomplish the subcontractor’s work efforts. The Contractor shall be responsible for the performance and quality of Subcontractor work governed by this contract. The Contractor shall monitor and control performance, quality, cost, and schedule according to the Contractor’s established subcontractor management techniques to ensure that CEC program schedules are not adversely impacted.

3.1.1.13.1 Subcontractor Test and Reviews (All CLINs)

The Contractor shall provide Government representatives the opportunity to attend reviews and observe tests performed by subcontractors. The Contractor shall notify the Government in writing thirty (30) working days prior to any subcontractor tests or reviews.

3.1.1.14 Integrated Development Environment (All CLINs)

The Contractor shall use the Government-approved Integrated Development Environment (IDE) to deliver all data (CDRL) deliverables under this contract. The Contractor shall provide the Government access to all technical data and information required in the Technical Manual/Electronic Technical Manual development process. The Contractor shall use the Government approved IDE for the delivery of all data products for review and distribution by the Government.

Instructions for accessing the unclassified IDE are provided as GFI. Access to the classified side requires an unclassified account. To obtain classified access, the Contractor shall visit https://ipdm.navy.smil.mil and complete the form requesting access to 'IWS6' on the iPDM main menu.

3.1.2 Systems Engineering (All CLINs)

The Contractor shall provide CEC Systems Engineering required to maintain, update, and upgrade the CEC System to meet current and future requirements in conformance to the specifications listed in this SOW.

The Contractor shall develop, execute, update, and maintain a Systems Engineering process to perform requirements analysis, functional analysis and allocation, synthesis, integration, validation and verification, systems analysis, and program planning, and control. The Contractor shall utilize a System of Systems Engineering approach to manage the development, integration, and sustainment of software and hardware for multiple platforms, sensors, and warfare areas. The Contractor shall apply this process to all activities performed under this contract, including all software and system tech refresh and obsolescence update development.

The Contractor shall propose and implement solutions for existing design defects and future requirements related to the integration and development of CEC Capabilities.

3.1.2.1 Systems Engineering Management Plan (SEMP) – Completion Tasks (CLINs 0001-0002, 1002, 2002, 3002, 4002) For completion tasks, the Contractor shall develop and update a SEMP that describes its Systems Engineering process based on the CEC SEP, provided as GFI, and using EIA/IS-632 and IEEE 1220 as guidance. The Contractor shall fully describe how all tasks identified in EIA/IS-632 and IEEE 1220 will be performed, or provide an alternative approach with supporting rationale, including the exclusion of tasks which add unnecessary cost, data, or other factors that do not add value. The SEMP shall define management and technical processes to a sufficient level of detail such that two different people or teams, independently following the SEMP, will implement each process in the same manner and with the same detail with high leverage over cost, schedule, quality, user satisfaction, and predictability. The SEMP may include references to Contractor internal processes and procedures that shall be part of the SEMP by reference and shall be made available for review at the Contractor’s facility. Subsequent changes to these references shall be identified to the Government and made available for review within 14 calendar days . Anticipated technical reviews or audits shall be listed in the SEMP. The SEMP shall include explicit descriptions of the Contractor's approach/methods for the following processes:

· Systems Engineering process and the activities as they are applied to the total systems engineering effort of the CEC program, including organization responsibilities and authority; control of subcontractor/supplier engineering; definition of tasks needed to satisfy each entry and exit criteria for each critical event technical review and key program milestone; and identification of planned increments, if applicable, including the objectives and the systems engineering activities to be performed in each increment

· Systems engineering process planning to include descriptions of major deliverables and results, process inputs, technical objectives, System Breakdown Structure (SBS), training, standards and procedures, resource allocation, constraints, work authorization, verification planning, IMS and subcontractor/supplier technical effort

· Requirements analysis and validation to analyze mission/operations and environments, identify functional and performance requirements, determine constraints related to quality factors and engineering specialty areas, and ensure both upward and downward traceability to higher level requirements

· Functional analysis, allocation, and verification to determine lower-level functions, allocate performance and other limiting requirements to lower-level functions, define functional interfaces, define the functional architecture, and ensure both upward and downward

· Synthesis and verification to transform the functional architecture into a physical architecture, define alternative system concepts, define physical interfaces, select preferred product and process solutions, and ensure both upward and downward traceability to the verified functional architecture

· Systems analysis efforts needed including methods, procedures, and tools required for trade studies, systems and cost effectiveness analysis, and risk/opportunity management

· Control mechanisms needed including methods, procedures, and tools required for CM, interface management, data management, event-based scheduling, calendar-based scheduling, Technical Performance Measurement (TPM), technical reviews, subcontractor/supplier control, and requirements traceability

· TPM using EIA/IS-632 and IEEE 1220-1994 for guidance. The SEMP shall define the set of critical technical parameters identified from sources such as risk/opportunity analyses and specifications that will be tracked as part of the TPM. The SEMP shall also include TPM update frequencies, tracking depth and response time to generate recovery plans and planned profile revisions.

· Identifying, assessing, selecting, and integrating critical technologies to meet requirements

· Integration of engineering specialties and various inputs into the systems engineering efforts

· Tailoring of EIA/IS-632 and IEEE 1220-1994 as appropriate for each major developmental effort to document the participation of Government and designated Contractors in the development process

· Additional systems engineering activities essential to engineering a total systems solution Inclusion of a Reliability Growth process that evolves developmental item/system reliability consistent with design maturity at different points in the systems engineering process, including…