Attachments1SOW_2ComplexityTable_4QASP.pdf

N00039-17-R-0039 Attachment No. 1

CONSOLIDATED AFLOAT NETWORKS AND ENTERPRISE SERVICES

(CANES)

BASELINE ANALYSIS OF ALTERNATIVES SERVICES

(BAAS)

STATEMENT OF WORK (SOW)

21 September 2017

Department of the Navy (DoN) Program Executive Office (PEO)

For Command, Control, Communications, Computers and Intelligence (C4I)

Program Management, Warfare Tactical Networks (PMW 160)

4301 Pacific Highway

San Diego, CA 92110-3127

DISTRIBUTION STATEMENT A:

Approved for public release. Distribution is unlimited.

1.0 SCOPE

1.1 Introduction

1.2 Background

1.3 Description of Services

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS

3.1 Post Award Conference (PAC) (CLIN 0001: FFP)

3.2 Component-Level - Analysis of Alternatives (AoA) (OPN) (CLINs 0002/0003/0004: FFP)

3.2.1 Program Management

3.2.1.1 Progress, Status and Management Reporting

3.2.2 Technical Interchange Meetings

3.2.3 Configuration Management

3.2.4 Component Level - Analysis of Alternatives (AoA) Framework

3.2.4.1 Section I: Market Research & Replacement Component List

3.2.4.2 Section II: Design Description

3.2.4.3 Section III: Evaluation Criteria

3.2.5 Component Level – Section IV: Analysis of Alternatives (AoA)

3.3 Material (OPN)(CLIN 0006: FFP)

3.3.1 Equipment/Material Procurement

3.3.2 Procurement of Software Products. Hardware and related Services

3.3.2.1 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program

3.4 Engineering Services and Technical Support (OPN) (CLIN 0007: CPFF)

3.4.1 Program Management

3.4.1 Post Award Planning Meeting (PAPM)

3.4.2 Program Management Reviews (PMR)

3.4.3 Meeting and Integrated Product Team (IPT) Support

3.4.4 Progress, Status and Management Reporting

3.4.5 Configuration Management

3.4.6 Market Research (OPN)

3.4.7 Design Effort

3.4.8 Analysis of Alternatives Framework

3.4.9 Analysis of Alternatives

3.4.10 System Engineering Technical Review

3.4.11 Material

3.4.11.1 Product Validation and Supply Chain Risk Management

3.4.11.2 Equipment/Material Procurement

3.4.11.3 Procurement of Software Products. Hardware and related Services

3.4.11.4 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program

4.0 GOVERNMENT FURNISHED INFORMATION

5.0 OTHER DIRECT COSTS/travel (CLIN 0009: Cost Only)

6.0 SECURITY

6.1 Operations Security (OPSEC) requirements

7.0 Enterprise-Wide Contract Management Application (ECMRA)

1.0 SCOPE

1.1 Introduction

The purpose of this Statement of Work (SOW) is to outline requirements for the Baseline Analysis of Alternatives (AoA) Services (BAAS) contract for the Consolidated Afloat Networks Enterprise Services (CANES) program. The program is assigned to the Tactical Networks Program Office, PMW 160, within the Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I).

The CANES program is the Navy’s only Program of Record (POR) to consolidate existing and standalone afloat Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) networks and provides the necessary infrastructure for applications, systems and services to operate in the tactical domain.

CANES is the programmatic, technical, and infrastructure consolidation of existing, separately managed afloat networks including Integrated Shipboard Network System (ISNS), Combined Enterprise Regional Information Exchange System – Maritime (CENTRIXS-M), Sensitive Compartmented Information (SCI) Networks and Submarine Local Area Network (SubLAN).

1.2 Background

The Under Secretary of Defense for Acquisition, Technology, and Logistics (USD (AT&L)) approved the CANES alternative in the Materiel Development Decision (MDD) Acquisition Decision Memorandum (ADM) on 12 December 2008. CANES was identified as an Acquisition Category (ACAT) IAM, Major Automated Information System (MAIS) on 29 March 2010 with USD (AT&L) designated as the CANES Milestone Decision Authority (MDA). CANES was formally approved for program initiation at Milestone (MS) B on 10 January 2011 and achieved MS C on 14 December 2012. Full Deployment Decision (FDD) was achieved on 13 October 2015 designating the program as ACAT IAC and delegating oversight to ASN (RD&A).

CANES is a Commercial-Off-The-Shelf (COTS) systems integration effort that utilizes state-of-the-industry networking hardware and core services software. CANES provides complete infrastructure, inclusive of hardware, software, processing, storage, and end user devices, for Unclassified, Coalition, Secret and SCI network services (email, web, chat, collaboration) to a wide variety of Navy surface combatants, submarines and Maritime Operations Centers. In addition, hosted applications and systems, inclusive of C4ISR, Information Operations, Logistics and Business domains, require the CANES infrastructure to operate in the tactical environment. The program implements a 2-year software and 4-year hardware rolling baseline approach to network upgrades and logistics that mitigates obsolescence issues and provides a stable configuration roadmap.

The CANES program awarded the Full Deployment Multiple Award Contract (MAC) in FY15 for the production of CANES production units. CANES production units are procured on a build-to-print basis though delivery order competitions under the CANES MAC. The Government controls, maintains and updates the CANES product baseline for the various afloat platforms. Successive CANES baselines will incorporate new hardware and software technology to expand the capabilities delivered with CANES. The CANES BAAS contract is an effort to complete market research, analysis, and procurement required to be replaced within the CANES baselines to address Security, End of Life (EOL) and End of Sale (EOS) products, emergent engineering issues, new requirements, system/sub-system redesign, and future baseline updates.

1.3 Description of Services

The CANES BAAS contract is an Indefinite Delivery – Indefinite Quantity (IDIQ) contract for the purpose of providing engineering and technical support with respect to the CANES baseline to include new design efforts, market research, component-level AoA and recommendations, component and subsystem procurement, technical documentation updates and delivery of components to be incorporated into the CANES baseline. The contractor will be responsible for reviewing the CANES component level specifications provided as Government Furnished Information (GFI) and conducting market research and AoA for recommending hardware and software replacement solution sets that are form, fit, and functionally interchangeable with the CANES Production Baseline (PBL) to address Security, EOL and EOS issues. In addition, the contractor shall be responsible for market research, AoA, design and product selection and /or future upgrades to the CANES baseline, to include both hardware and software.

Objectives for the CANES baseline AoA services include: market research to ensure state-of-the-art technologies are explored as potential updates to EOL/EOS components for production modification of CANES Baseline; market research to ensure potential impacts related to configuration changes are minimal within specified timeframes; AoAs justifying product selections that provide information of sufficient depth and complexity to support successful integration into the baseline and a product delivered in such a manner that the Government may integrate them into the CANES Baseline, e.g., the (i) CANES Configuration Item Configuration Document (CICD), (ii) Production/Installation/Sustainment software media (source code, executables, scripts) and configuration management documentation, and (iii) the IETM.

Specific requirements will be defined in individual Task Orders (TOs). TOs for CANES BAAS may be both firm-fixed priced (FFP) and cost plus fixed fee (CPFF). Firm-fixed prices for delivery of AoAs and associated recommendations for component-level product selection will be established at award (see SOW section 3.3). Cost reimbursement orders will be issued for system/subsystem-level product selection (to include design efforts, emerging engineering issues or new system requirements). If required, procurement of software and/or hardware products will be on either a FFP (under CLIN 0006) or CPFF basis (under CLIN 0007) (see SOW section 3.3 and 3.4).

2.0 APPLICABLE DOCUMENTS

Documents referenced herein are listed in Table 2. The contractor shall comply with the following documents, as applicable, and as directed by the basic contract SOW and individual TO SOW. In the event of a conflict between the text of this document and the applicable documents cited herein, the text of this document takes precedence.

Military Standards (MIL-STD) can be located on the Defense Logistics Agency (DLA) Assist website at http://quicksearch.dla.mil/. PMW 160 and PEO references will be provided electronically as Government Furnished Information (GFI) on the Government’s CMPro – Reference Folder.

TABLE 2 - APPLICABLE DOCUMENTS

ID Reference ID Reference Name SOW Reference

1 PMW 160 CANES CANES Software Production Specification

(SPS)

As specified on each individual task order

2 PMW 160 CANES CANES Software Version Description (SVDD) As specified on each individual task order

3 PMW 160 CANES CANES Configuration Item Configuration Document (CICD)

As specified on each individual task order

4 PMW 160 CANES CANES Physical Architecture As specified on each individual task order

5 PMW 160 CANES CANES System/Subsystem Specification As specified on each individual task order

6 PMW 160 CANES CANES Interface Requirements Specification As specified on each individual task order

7 PMW 160 CANES Interactive Electronic Training Manual

(ITEM) 3.2

8 PMW 160 Hosted Application Connected Systems Integration Manual (HACSIM) 3.2

9 PEO C4I LCCMIM PEO C4I Life Cycle Configuration Control Implementation Manual (LCCMIM) 3.1.5

10 PMW 160 CMP Tactical Networks Program Office Life Cycle Configuration Management Plan (CMP) 3.1.5

11 PMW 160 SEIG

Version 1.0

PMW 160 Systems Engineering Implementation Guide (SEIG)

As specified on each individual task order

PMW 160 Tactical Networks

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.3.6 and as specified on each individual Task Order

13 PMW 160 CANES CANES Functional Specification As specified on each http://quicksearch.dla.mil/

ID Reference ID Reference Name SOW Reference individual task order

14 PMW 160 CANES CANES Architecture Specification As specified on each individual task order

15 PMW 160 CANES Afloat Network Family of Systems Environment Specifications (ANFOS) v 1

As specified on each individual task order

16 MIL-HDBK-61A Configuration Management 3.1.6

17 MIL-STD-129P (4)

dated 19SEP07

Packaging, Handling, Storage, and Transportability Requirements 3.3.1

18 MIL-STD-2073-IE

dated 23MAY08

Packaging, Handling, Storage, and Transportability Requirements 3.3.1

19 AN-FOS-ENV-

REQS-0203

Afloat Networks (AN) Family of Systems (FOS) Environmental Requirements 3.2.4.3

3.0 REQUIREMENTS

3.1 Post Award Conference (PAC) (CLIN 0001: FFP)

The contractor shall participate in a Post Award Conference (PAC) to be held in San Diego, CA, within thirty (30) calendar days after award of contract. The contractor shall provide video teleconferencing capability for the PAC as requested by the Government. The PAC shall be a one (1) day event at which the contractor shall demonstrate to the Government overall contract and TO management procedures, a review of technical and other specialty areas status, and establish schedule dates for near term critical meetings/actions. The contractor shall present management, essential personnel, a Production Plan, and program implementation processes. The contractor shall document and perform action item follow-up and resolution activities. (CDRLs: A001 and A002)

3.2 Component-Level - Analys is of Alternat ives (AoA) (OPN) (CLINs 0002/0003/0004:

FFP)

The contractor shall perform product analysis, evaluation and make replacement and/or new product recommendations for production modifications in the CANES Baseline through delivery of an AoA Framework and an AoA for specified components which will be identified within each TO. Firm Fixed priced orders will be based on the number of products to be included in the AoA Framework and AoA and the complexity of the Government-provided component-level specification as provided in Attachment No. 2, Complexity Table, and deliverables shall include the following:

I. AoA Framework (PWS 3.2.4)(CDRL A005):

Section I –Market Research & Replacement Component List (SOW 3.2.4.1) Section II – Design Description (SOW 3.2.4.2) Section III – Evaluation Criteria (SOW 3.2.4.3)

II. AOA (SOW 3.2.5)(CDRL A006)

3.2.1 Program Management

The contractor shall designate a Program Manager (PM). The PM shall have responsibility for all aspects of this contract and each TO. The PM shall have the authority to commit the contractor to specific actions within the scope of this contract.

The contractor shall provide overall program management to ensure work conducted within this contract is planned and executed in a manner that achieves management, technical, cost, and schedule objectives. The contractor shall manage these objectives for each individual awarded TO and for the contract as a whole. The contractor shall ensure coordination and integration of all supporting production disciplines. The contractor shall document and deliver lessons learned concerning all aspects of the program, such as cost, schedule, quality, production, delivery, etc.

3.2.1.1 Progress, Status and Management Reporting

The contractor shall provide a Progress, Status and Management Report. The report shall contain all aspects of the contract addressing cost, schedule, and performance for all TOs. The report shall specifically identify the following items: schedule status, progress against major milestones, status of, cost/funding status, risk management, manpower, configuration management, Supply Chain Risk Management (SCRM), systems and software engineering, logistics, quality assurance, safety status, identification and status of technical issues, lower tier supplier accomplishments and issues, action item status, and TO questions. (CDRLs: A003, A004)

3.2.2 Technical Interchange Meetings

The contractor shall conduct a Technical Interchange Meeting (TIM) five (5) business days prior to delivery of the AoA Framework. The contractor shall provide video teleconferencing capability for the TIM. The contractor shall document each meeting’s significant events, results, and action items. (CDRLs: A001, A002)

3.2.3 Configuration Management

The contractor shall maintain and manage a Configuration Management (CM) Program using Military Handbook:

Configuration Management MIL-HDBK-61A as guidance. The contractor’s CM efforts shall include configuration identification, configuration change control, configuration status accounting, configuration verification and audits, and configuration data management. The contractor shall maintain a CM process capable of processing configuration changes from identification through Government approval and implementation, without impact to production schedules. The contractor shall participate in the Government bi-weekly CCB meetings.

3.2.4 Component Level - Analysis of Alternatives (AoA) Framework

The contractor shall deliver an AoA Framework. The AoA Framework establishes the weighted evaluation criteria and the set of candidate replacement components for evaluation within the AoA. See Attachment No. 2, Complexity Table. (CDRL: A005)

3.2.4.1 Section I: Market Research & Replacement Component List

In Section I the contractor shall conduct market research in order to identify an initial set of component product candidates that will be used for detailed data collection and evaluation during the conduct of the AoA. The contractor shall list and identify each candidate product within the AoA Framework with sufficient descriptive detail to enable an independent third party to uniquely identify and procure the product. The quantity of candidate products shall be sufficient to represent effective market research and shall fall within the required product candidate quantity ranges listed in Attachment 2 Complexity Table. In the case of a replacement component product due to EOL or EOS status, the set of candidate replacement products shall include the product that is recommended by the original equipment manufacturer (OEM). The contractor shall include a summary of the rationale that was used to identify the set of candidate replacement components.

The market research shall consider, at a minimum, Gartner analysis of suppliers within the related technology field, suppliers from GSA schedules, and products deployed within existing and planned Navy and Joint systems similar to CANES. In the event that market research reveals candidate product quantities that exceed the ranges listed in Attachment No. 2, Complexity Table, the contractor shall reduce the list of component quantities to comply with the Complexity Table using the following ordered down-selection method:

a) The OEM-recommended product-line follow-on (from previous CANES baselines/releases) shall always be retained within the candidate component product list.

b) Products that do not meet at least 75% of component functional requirements shall be removed from the candidate product list.

c) If additional down-select is required after (b), Products that do not meet physical dimensional requirements shall be removed from the candidate product list.

d) If additional down-select is required after (c), products that are neither tracked/reported by Gartner, on GSA schedules, nor deployed within existing or planned Navy/Joint systems shall be removed from the candidate product list.

e) In the event that additional down-select is required after (d), or that the application of rule (b) or (c) eliminates too many candidate products at once, cost (list cost plus 2 years of support/maintenance cost) shall be used as a final discriminator.

The contractor shall provide pricing data to procure under CLIN 0006 for the candidate replacement components. To expedite the material ordering process, the pricing data will be used to establish a not to exceed price for any future “material” procurements under CLIN 0006 as described in SOW Section 3.3. The contractor shall include at least three (3) quotes and the supporting data for each candidate replacement component. Each quote shall include the cost for the contractor to procure a single component product set plus support maintenance for one year.

Each quote shall be valid for procurement via a CLIN 0006 Task Order for no less than sixty (60) days. The quote shall be presented as a singular procurement of sufficient product quantities to satisfy a single component; however, quotes must be valid to support larger quantities, if directed under CLIN 0006.

3.2.4.2 Section II: Design Description

Section II of the AoA Framework for each specified component shall contain a design description of each candidate replacement component to include:

(a) A Bill of Materials (BOM) with sufficient detail to enable a third party to independently identify the proposed component. The BOM shall clearly identify and delineate the product variations in accordance with the component level specifications (e.g. variations for different platform types). The BOM shall identify all independently procurable equipment/modules (e.g. peripherals, incidentals or subcomponents and/or any applicable items that complete the configuration) that are contained within a component (e.g. in the event that the component consists of multiple separately-procured parts that require integration at a CANES production facility).

(b) A diagram that identifies all external physical and logical interfaces between the candidate component and CANES to illustrate how the component will be connected and integrated into CANES. The external interfaces shall include, where applicable, physical mounting interfaces (e.g. rack mounts and kits), physical cabling and interconnections, logical software interfaces to CANES computing hosts and Operating Systems, and logical software interfaces to the CANES management subsystem and other affected CANES subsystems/components. The contractor shall include a diagram for each proposed component variant in the event that the proposed component includes multiple different integration approaches (for example, across different CANES security enclaves and/or platform types).

(c) A diagram that identifies all internal physical and logical interfaces within the component. This diagram shall be required only in the event that the candidate replacement component includes multiple parts. Internal interfaces include, where applicable, physical mounting interfaces (e.g. mounting kits), internal physical cabling and interconnections, and logical software interfaces within component modules. The internal interface diagram shall include a description of each information flow across the component part interfaces. The contractor shall include a diagram for each proposed component variant (for example, variants across different CANES security enclaves and/or platform types).

3.2.4.3 Section III: Evaluation Criteria

Section III of the AoA Framework for each specified component shall identify the weighted evaluation criteria that will be used in the AoA in order to select the optimal replacement component. The contractor shall recommend a rating approach for each evaluation criteria. The contractor shall document the scoring rule sets for numerical ratings, adjectival ratings (such as excellent, good, fair, poor) and/or pass/fail ratings, for each evaluation criteria. Scoring rule sets shall be documented at a level of fidelity that will facilitate both unambiguous categorization of candidate components and effective discrimination across candidate components. The contractor shall identify the weighting of importance across all factors and describe how the selection will be made, e.g. Best Value Trade - Off. Scoring rule sets shall be documented at a level of fidelity that will facilitate both unambiguous categorization of candidate components and effective discrimination across candidate components. The tradeoff recommendation shall consider the combination of numeric, adjectival, and pass/fail ratings in conjunction with the relative risks.

The weighed evaluation criteria shall include, at a minimum:

(a) The extent to which the proposed replacement component meets the component-level requirements. The component-level requirements are defined in the CANES specifications as described in individual TOs. The contractor shall use numerical ratings for this evaluation criterion.

(b) The extent to which the proposed replacement component meets form, fit, and functional interchangeability requirements. The contractor shall use numerical ratings for this evaluation criterion.

(c) The extent to which the proposed replacement component will minimize the risk of repeating CANES Environmental Qualification Testing (EQT) in accordance with AN- FOS-ENV-REQS-0203, Afloat Networks Family of Systems Environmental Requirements. The contractor shall use adjectival ratings for this evaluation criterion.

(d) The extent to which the proposed replacement component will impact the current CANES design. The contractor shall include the details outlining how the proposed replacement component may impact / change the existing installation instructions and/or installation media, including the CANES CICD, SPS, Technical Data Package (TDP), and Installation Requirements Drawings (IRDs). The contractor shall include a rationale on how the impacts will be minimized to the stated installation instructions and/or media.

The contractor shall use adjectival ratings for this evaluation criterion.

(e) The extent to which the proposed replacement component will minimize the need for future EOL replacements. The contractor shall use market research as a projection for EOL/EOS predictions based on vendor history and/or openly published vendor EOS/support dates. The contractor shall use adjectival ratings for this evaluation criterion.

(f) The extent to which the proposed replacement component will minimize supply chain risk. The contractor shall use adjectival ratings for this evaluation criterion.

(g) The extent to which the proposed replacement component is common across similar Navy and Joint systems. The contractor shall use adjectival ratings for this evaluation criterion.

(h) The contractor shall provide the prices of the candidate replacement components and the lifecycle maintenance costs. The contractor shall provide the extent to which the proposed replacement component reduces the price per unit and lifecycle maintenance costs. The contractor shall use numerical ratings for this evaluation criterion.

3.2.5 Component Level – Section IV: Analysis of Alternatives (AoA)

The contractor shall execute the AoA in accordance with the established framework identified in section 3.2.4 upon receipt of Government approval of the AoA Framework. (CDRL A006)

The contractor shall identify the score of each candidate component for each evaluation criteria in accordance with the scoring rule sets defined in the AoA Framework. In Section IV of the final report, the contractor shall document rationale for each score as follows:

(a) Suitable evidence from qualified sources that substantiates the performance of the candidate component against each evaluation criteria. Acceptable qualified sources include (i) information from publically available websites and product specification sheets published by the product manufacturer; (ii) data from common independent sources that regularly publish and maintain databases of product performance data (e.g. Gartner, Spec.org); (iii) observed, measured, or tested data directly collected by the contractor under the TO from loaned or procured products within contractor or Government facilities; (iv) historical observed, measured, or tested data from Government labs or reports; and/or (v) data received as a result of a direct contact with product manufacturers. In the event that the contractor directly queries the product manufacturer for product data, the contractor shall provide independent substantiating evidence that describes in detail how the product meets evaluation criteria requirements.

(b) Scoring justification. The contractor shall include scoring justification that describes in detail why each score was assessed based on the substantiating evidence, and the scoring criteria for the rating.

The contractor shall provide a recommendation, based on a tradeoff analysis, for the final proposed replacement component. The tradeoff recommendation shall consider the combination of numeric, adjectival, and pass/fail ratings in conjunction with the relative evaluation weights for each criterion.

3.3 Material (OPN)(CLIN 0006: FFP)

The contractor shall procure component(s) recommended as a result of the approved AoA(s) under SOW section

3.2.5 as specified on individual TOs. The contractor shall deliver components to SSC PAC and/or LANT, or other Government facilities as defined in individual TOs. In the case of software and/or hardware that may include firmware the contractor shall deliver Software License Keys (CDRL A008).

3.3.1 Equipment/Material Procurement

Pursuant to SPAWARINST 4440.12, the contractor shall procure items listed under the Contractor Acquired Property (CAP) paragraph. The contractor shall ensure acquisition selection factors include price, availability, reliability, and supportability within current supply system. The contractor shall keep source selection records and make it available for government review as needed. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status per task order and per item. After receipt, the contractor shall have an adequate property management system to track the item location per task order per item. Unless otherwise noted, all items procured by the contractor shall be utilized or staged at the contractor’s facility, transported by the contractor to the installation, integrated or consumed in a system, or returned to the government at the completion of the contract/TO.

Contractor shall recommend items that conform to applicable product validation, identification, and tracking requirements.

(a) Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. Unless otherwise specified, the contractor shall warrant that the products are new, in their original box.

The contractor shall obtain all manufacturer products submitted in task/delivery order offers from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies at the time of purchase. The contractor shall provide the Government with a copy of the End User license agreement, and shall warrant that all manufacturer software is licensed originally to Government as the original licensee authorized to use the manufacturer software. The contractor shall track the licensing information and have it available for government review as needed.

(b) Cybersecurity/Computer Security Requirements – The contractor shall ensure that all products recommended and/or procured that impact cybersecurity or Information Assurance (IA) shall be selected from the NIAP Validated Products List. The contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level (EAL) for the network involved, and utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for government review as needed.

(c) Item Unique Identification (IUID) – In accordance with DFARS clause 252.211-7003/7007 and SECNAVINST 4440.34, the contractor shall ensure that an item manufactured, integrated, or purchased with a unit cost equal to or exceeding $5,000 (or less if item is serially managed or if government specifies items on individual task/delivery orders) is labeled with an item unique identification number or Unique Item Identifier (UII). (CDRL A010 & A011)

3.3.2 Procurement of Software Products. Hardware and related Services

Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

3.3.2.1 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program

Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA) dtd 22 Feb 12, contractors that are authorized to use Government supply sources per FAR 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the TO/contract level.

3.4 Engineering Services and Technical Support (OPN) (CLIN 0007: CPFF)

The contractor shall provide engineering services and technical support to address system/subsystem product selection for emergent engineering issues, new requirements for production modification of the CANES Baseline, analysis of alternatives and system/sub-system redesign. Individual task orders may include the following efforts:

3.4.1 Program Management

The contractor shall designate a Program Manager (PM). The PM shall have responsibility for all aspects of this contract and each TO. The PM shall have the authority to commit the contractor to specific actions within the scope of this contract.

The contractor shall provide overall program management to ensure work conducted within this contract is planned and executed in a manner that achieves management, technical, cost, and schedule objectives. The contractor shall manage these objectives for each individual awarded TO and for the contract as a whole. The contractor shall ensure coordination and integration of all supporting production disciplines. The contractor shall document and deliver lessons learned concerning all aspects of the program, such as cost, schedule, quality, production, delivery, etc.

3.4.1 Post Award Planning Meeting (PAPM)

As directed by individual TO, the contractor shall participate in a Post Award Planning Meeting (PAPM) in San Diego, CA, or at a location mutually agreed upon between the Government and the contractor. The contractor shall provide video teleconferencing capability for the PAPM as requested by the Government. The PAPM shall be no more than a one (1) day event at which the Contractor shall demonstrate to the Government the management procedures, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings/actions. The Contractor shall present management, manpower, an Integrated Master Schedule (IMS), and program implementation processes. The Contractor shall document and perform action item follow-up and resolution activities. (CDRLs: B001, B002 and B004)

3.4.2 Program Management Reviews (PMR)

As directed by individual TO, the contractor shall conduct Program Management Reviews (PMRs). The contractor shall provide selected viewgraphs and graphic materials to support program office briefing requirements for documenting program activities. The PMR content shall contain all aspects of the contract addressing cost, schedule, and performance for all TOs (e.g. schedule status, progress against major milestones, status of, cost/funding status, risk management, manpower, configuration management, Supply Chain Risk Management (SCRM), systems and software engineering, logistics, quality assurance, safety status, identification and status of technical issues, and lower tier supplier accomplishments and issues). (CDRLs: B001, B002, B004, and B007)

The contractor shall document significant events, outcomes, and action items resulting from the PMR. The contractor shall perform action item follow-up and resolution activities. The contractor shall provide teleconferencing or video teleconferencing capability for the PMR, as requested by the Government.

The contractor's functional leads shall report on the status of their respective tasks. The Government may schedule additional reviews or working groups if issues arise or significant events or changes occur.

3.4.3 Meeting and Integrated Product Team (IPT) Support

The contractor shall coordinate, schedule, prepare, conduct, facilitate, and participate in meetings and IPTs, as directed by individual TOs, to discuss and / or present engineering analysis, assessment, related issues and recommended resolutions. (CDRLs: B001, and B002)

3.4.4 Progress, Status and Management Reporting

The contractor shall provide a Progress, Status and Management Report as directed by individual TO. The report shall contain all aspects of the contract addressing cost, schedule, and performance for all TOs. The report shall specifically identify the following items: schedule status, progress against major milestones, status of, cost/funding status, risk management, manpower, configuration management, Supply Chain Risk Management (SCRM), systems and software engineering, logistics, quality assurance, safety status, identification and status of technical issues, lower tier supplier accomplishments and issues, action item status, and TO questions.

As directed by individual TO, the contractor shall provide status of small business utilization and subcontracting activities. (CDRLs: B003 and B007)

3.4.5 Configuration Management

The contractor shall maintain and manage a Configuration Management (CM) Program using Military Handbook:

Configuration Management MIL-HDBK-61A as guidance, as directed by individual TO. The contractor’s CM efforts shall include configuration identification, configuration change control, configuration status accounting, configuration verification and audits, and configuration data management. The contractor shall maintain a CM process capable of processing configuration changes from identification through Government approval and implementation, without impact to production schedules. The contractor shall participate in the Government CCB meetings.

3.4.6 Market Research (OPN)

As directed by individual TO, the contractor shall perform market research with original equipment manufacturers, and third party suppliers /vendors. The market research may include white paper research and/or Industry Day-like events to be hosted by the BAAS contractor, and/or CANES Baseline component/product End of Life, End of Sale, End of Support, and/or new product or capability, hardware or software, tracking and reporting. Both Government and industry partners shall be invited to market research events. (CDRL B012).

As directed by individual TO, the contractor shall implement a Diminishing Manufacturing Sources and Material Shortage (DMSMS) reporting plan complying with the PMW 160 DMSMS Policy. (CDRL B013)

3.4.7 Design Effort

The contractor shall conduct design activities as directed in the individual TOs to include (i) the creation of component-level specifications that may be derived from an existing product within the CANES baseline or derived and allocated as a new component within the CANES baseline, (ii) detailed design activities resulting in the creation/update of iPBL design documentation to include the CANES Topology Diagram, Rack Elevation Diagram, Cable Table, Bill of Material, Computing Resource Allocation (CRA), and/or the Software Deployment Map. The contractor shall define the physical form, fit and function characteristic of the new assembly, subsystem assemblies and component level specifications as defined in individual TOs. (CDRLs: B014, B016,B017, B018, B019, B020, and B021)

3.4.8 Analysis of Alternatives Framework

The contractor shall deliver an AoA Framework. The AoA Framework establishes the weighted evaluation criteria and the set of candidate replacement components for evaluation for the AoA. AoA Frameworks may include but is not limited to requirements noted in SOW paragraph numbers 3.2.4 (CDRLs: B005)

3.4.9 Analysis of Alternatives

The contractor shall conduct the AoA by evaluating each candidate replacement component against each evaluation criteria as identified and established in the approved AoA Framework. The contractor shall provide a tradeoff recommendation for the final proposed replacement component. AoAs may include but is not limited to requirements noted in SOW paragraph numbers 3.2.5. (CDRLs: B006)

3.4.10 System Engineering Technical Review

The contractor shall prepare for, and/or participate in, System Engineering Technical Review (SETR) events. The contractor shall present the AoA and recommended selected products to meet the emergent engineering issues, new requirements and/or system/sub-system redesign requirements as defined in individual TO. (CDRLs: B001, & B002)

3.4.11 Material

When directed by the Government, the contractor shall procure component(s) recommended as a result of the approved AoA(s) under SOW section 3.4.9. The contractor shall deliver components to SSC PAC and/or LANT, or other Government facilities as defined in individual TOs. In the case of software and/or hardware that may include firmware the contractor shall deliver Software License Keys (CDRL B008)

3.4.11.1 Product Validation and Supply Chain Risk Management

The contractor shall comply with Product Validation and SCRM requirements as directed by individual TO. The contractor shall deliver and maintain a SCRM plan detailing contractor processes and procedures for implementing and sustaining SCRM activities for the CANES FRP Contract. Product Validation and SCRM activities shall include, but are not limited to: SCRM plans, product validation reports, certification of component authenticity, and post notification alerts. (CDRLs: B009, B010, B011)

The contractor shall provide engineering services to complete component specifications for replacement components. The Government will provide the contractor with existing component implementation and the CANES Functional Specification. The contractor shall submit component specifications as defined in individual TO.

(CDRLs: B016)

3.4.11.2 Equipment/Material Procurement

Pursuant to SPAWARINST 4440.12, the contractor shall procure items listed under the Contractor Acquired Property (CAP) paragraph. The contractor shall ensure acquisition selection factors include price, availability, reliability, and supportability within current supply system. The contractor shall keep source selection records and make it available for government review as needed. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status per task order and per item. After receipt, the contractor shall have an adequate property management system to track the item location per task order per item. Unless otherwise noted, all items procured by the contractor shall be utilized or staged at the contractor’s facility, transported by the contractor to the installation, integrated or consumed in a system, or returned to the government at the completion of the contract/TO.

Contractor shall recommend items that conform to applicable product validation, identification, and tracking requirements.

(a) Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. Unless otherwise specified, the contractor shall warrant that the products are new, in their original box.

The contractor shall obtain all manufacturer products submitted in task/delivery order offers from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies at the time of purchase. The contractor shall provide the Government with a copy of the End User license agreement, and shall warrant that all manufacturer software is licensed originally to Government as the original licensee authorized to use the manufacturer software. The contractor shall track the licensing information and have it available for government review as needed.

(b) Cybersecurity/Computer Security Requirements – The contractor shall ensure that all products recommended and/or procured that impact cybersecurity or Information Assurance (IA) shall be selected from the NIAP Validated Products List. The contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level (EAL) for the network involved, and utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for government review as needed.

(c) Item Unique Identification (IUID) – In accordance with DFARS clause 252.211-7003/7007 and SECNAVINST 4440.34, the contractor shall ensure that an item manufactured, integrated, or purchased with a unit cost equal to or exceeding $5,000 (or less if item is serially managed or if government specifies items on individual task/delivery orders) is labeled with an item unique identification number or Unique Item Identifier (UII). (CDRLs:

B010)

3.4.11.3 Procurement of Software Products. Hardware and related Services

Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

3.4.11.4 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program

Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA) dtd 22 Feb 12, contractors that are authorized to use Government supply sources per FAR 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec

05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the TO/contract level.

4.0 GOVERNMENT FURNISHED INFORMATION

GFI will be identified, as required, at the task order level. (CDRL: A003 and B003)

5.0 OTHER DIRECT COSTS/TRAVEL (CLIN 0009: COST ONLY)

Other Direct Costs/Travel may be required under CFPP CLIN and will be specified on each individual TO.

6.0 SECURITY

The nature of this task requires access up to SECRET information as designated within the DD 254. The work performed by the contractor will include access up to Secret data, information and spaces. The contractor will be required to attend meetings classified up to the Secret level. All work shall be performed in accordance with DoD and Navy Operations Security (OPSEC) requirements and in accordance with the OPSEC attachment to the DD254.

Some Engineering Support Services will require contractor access to Secret data, information, and spaces at Government facilities. Some installation tasks will require contractor access to Secret data, information, and spaces at the installation site.

6.1 Operations Security (OPSEC) requirements

OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities;

assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process command(s) Critical Information or Critical Program Information, and therefore all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the

DD254.

7.0 ENTERPRISE-WIDE CONTRACT MANAGEMENT APPLICATION (ECMRA)

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address:

https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at: https://doncmra.nmci.navy.mil.

For the purposes of CMRA reporting, the Federal Supply Code/Product Service Code applicable to the contract is R425.

https://doncmra.nmci.navy.mil/ https://doncmra.nmci.navy.mil/

N00039-17-R-0038 Attachment No. 2 - Complexity Table Master List

Item No. Subsystem Component HW/SW AoA LOE Subs/FL/UL and/or Enclave Deviation?**

Functional / Interoperability Requirements

Environmental Requirements

Expected Candidate

1 NETSEC Port Security/Network Access Control Server Either Device or Software* High Possibly Multiple Solutions Many/Complex Possible (If HW) Several (4-5) 2 AIR Automated System Installation/Deployment Software High Single Solution Variant Expected Many/Complex No Several (4-5) 3 AIR Automated System Configuration Audit Software High Single Solution Variant Expected Many/Complex No Several (4-5) 4 CDS CDS Access Server Either Device or Software* High Single Solution Variant Expected Many/Complex Possible (If HW) Several (4-5) 5 CDS CDS Transfer Guard Device High Single Solution Variant Expected Many/Complex Yes Few (1-3) 6 CDS CDS Access Clients Device High Single Solution Variant Expected Many/Complex Yes Several (4-5) 7 CI Software Defined Storage Software High Possibly Multiple Solutions Many/Complex No Few (1-3) 8 NETSEC Port Security/Network Access Control Server Either Device or Software* High Possibly Multiple Solutions Many/Complex Possible (If HW) Several (4-5) 9 NI Switch - Backbone Device High Likely Multiple Solutions Moderate Yes Many (6-8)

10 NI Switch - Datacenter/TOR Device High Possibly Multiple Solutions Moderate Yes Many (6-8) 11 SMS Data Backup and Recovery Manager Either Device or Software* High Single Solution Variant Expected Many/Complex Possible (If HW) Several (4-5) 12 SMS Network Manager Software High Single Solution Variant Expected Many/Complex No Several (4-5) 13 SMS Provision Manager Software High Single Solution Variant Expected Many/Complex No Several (4-5) 14 SMS Configuration Manager Software High Single Solution Variant Expected Many/Complex No Several (4-5) 15 NI Software Defined Networking Components Either Device or Software* High Possibly Multiple Solutions Many/Complex Yes Several (4-5) 16 CI Printer/Scanner…