HC1028-08-D-2024-VC04-1.doc

Section B - Supplies or Services and Prices

Cost

$270,096.09

6.1- Task Order Management

CPFF

Task 6.1-Task Order Management - IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I. Travel in support of the DTO PWS. All Travel must be pre-approved by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46. No first class travel is authorized.

FOB: Destination

PURCHASE REQUEST NUMBER: DCCMC34107

ESTIMATED COST

$251,713.82

FIXED FEE

$18,382.27

TOTAL EST COST + FEE

$270,096.09

000101

$0.00

FY13 funding for CENTRIXS project

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000101

$270,096.09

Cost

$423,760.90

6.2- Service Design & Engineering

6.2- Service Design & Engineering- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$390,596.01

$33,164.89

$423,760.90

000201

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000201

$423,760.90

Cost

$179,681.91

6.3- Security Eng Cert and Accreditation

6.3- Security Eng Cert and Accreditation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$165,605.45

$14,076.46

$179,681.91

000301

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000301

$179,681.91

Cost

$54,928.28

6.4- Test and Evaluation

6.4- Test and Evaluation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$50,668.34

$4,259.94

$54,928.28

000401

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000401

$54,928.28

Cost

$6,800.76

6.5- Configuration Change Transition Pla

6.5- Configuration Change Transition Plan. . IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$6,267.98

$532.78

$6,800.76

000501

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000501

$6,800.76

Cost

$25,185.50

6.6- Equipment Acquisition and Supplier

6.6- Equipment Acquisition and Supplier Relationship Management. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$23,212.44

$1,973.06

$25,185.50

000601

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000601

$25,185.50

Cost

$6,979.59

6.7- Configuration Management

6.7- Configuration Management. IAW CACI's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$6,432.80

$546.79

$6,979.59

000701

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000701

$6,979.59

Cost

$6,620.57

6.8-Release and Deployment

6.8-Release and Deployment. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$6,101.91

$518.66

$6,620.57

000801

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000801

$6,620.57

Cost

$248,910.52

6.9-Operational Support

6.9-Operational Support. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$229,410.61

$19,499.91

$248,910.52

000901

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105000901

$6,979.59

000902

$0.00

FY13 funding for CMNT project

FY13 funding for CMNT project

$0.00

$0.00

$0.00

ACRN AB

CIN: DCCMC3410600902

$216,946.57

000903

$0.00

FY13 funding for CMNT project

FY13 funding for CMNT project

$0.00

$0.00

$0.00

ACRN AB

CIN: DCCMC3410600903

$22,376.29

Cost

$42,171.91

6.10- Transition to New Contract

6.10- Transition to new contract. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$38,868.12

$3,303.79

$42,171.91

001001

$0.00

FY13 funding for CENTRIXS project

$0.00

$0.00

$0.00

ACRN AA

CIN: DCCMC34105001001

$42,171.91

Cost

$101,860.00

Other Direct Cost (ODC's)

COST

Other Direct Cost (ODC's) - (1) No profit shall be paid on purchases made under this CLIN. (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31.

001101

$0.00

FY13 funding for CENTRIXS project

COST

ACRN AA

CIN: DCCMC34105001101

$101,860.00

Cost

$135,048.13

CPFF

Task 6.1-Task Order Management - IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I. Travel in support of the DTO PWS. All Travel must be pre-approved by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46. No first class travel is authorized.

$125,856.99

$9,191.14

$135,048.13

Cost

$211,884.40

CPFF

6.2- Service Design & Engineering- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$195,301.64

$16,582.76

$211,884.40

Cost

$89,841.82

CPFF

6.3- Security Eng Cert and Accreditation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$82,803.52

$7,038.30

$89,841.82

Cost

$27,464.14

CPFF

6.4- Test and Evaluation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$25,334.17

$2,129.97

$27,464.14

Cost

$3,400.38

CPFF

6.5- Configuration Change Transition Plan. . IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,133.99

$266.39

$3,400.38

Cost

$12,593.25

CPFF

6.6- Equipment Acquisition and Supplier Relationship Management. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$11,606.68

$986.57

$12,593.25

Cost

$3,489.80

CPFF

6.7- Configuration Management. IAW CACI's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,216.40

$273.40

$3,489.80

Cost

$3,310.28

CPFF

6.8-Release and Deployment. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,050.95

$259.33

$3,310.28

Cost

$124,457.83

CPFF

6.9-Operational Support. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$114,707.67

$9,750.16

$124,457.83

Cost

$0.00

CPFF

6.10- Transition to new contract. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$0.00

$0.00

$0.00

Cost

$50,930.00

COST

Other Direct Cost (ODC's) - (1) No profit shall be paid on purchases made under this CLIN. (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. COST REIMBURSEMENT (CR)- CONTRACT Month 3

Cost

$135,048.13

CPFF

Task 6.1-Task Order Management - IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I. Travel in support of the DTO PWS. All Travel must be pre-approved by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46. No first class travel is authorized.

$125,856.99

$9,191.14

$135,048.13

Cost

$211,884.40

CPFF

6.2- Service Design & Engineering- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$195,301.64

$16,582.76

$211,884.40

Cost

$89,841.82

CPFF

6.3- Security Eng Cert and Accreditation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$82,803.52

$7,038.30

$89,841.82

Cost

$27,464.14

CPFF

6.4- Test and Evaluation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$25,334.17

$2,129.97

$27,464.14

Cost

$3,400.38

CPFF

6.5- Configuration Change Transition Plan. . IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,133.99

$266.39

$3,400.38

Cost

$12,593.25

CPFF

6.6- Equipment Acquisition and Supplier Relationship Management. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$11,606.68

$986.57

$12,593.25

Cost

$3,489.79

CPFF

6.7- Configuration Management. IAW CACI's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,216.40

$273.39

$3,489.79

Cost

$3,310.28

CPFF

6.8-Release and Deployment. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,050.95

$259.33

$3,310.28

Cost

$124,457.83

CPFF

6.9-Operational Support. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$114,707.67

$9,750.16

$124,457.83

Cost

$0.00

CPFF

6.10- Transition to new contract. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$0.00

$0.00

$0.00

Cost

$50,930.00

COST

Other Direct Cost (ODC's) - (1) No profit shall be paid on purchases made under this CLIN. (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. COST REIMBURSEMENT (CR)- CONTRACT Month 4

Cost

$141,110.69

CPFF

Task 6.1-Task Order Management - IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I. Travel in support of the DTO PWS. All Travel must be pre-approved by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46. No first class travel is authorized.

$131,452.95

$9,657.74

$141,110.69

Cost

$219,040.52

CPFF

6.2- Service Design & Engineering- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$201,895.11

$17,145.41

$219,040.52

Cost

$92,808.44

CPFF

6.3- Security Eng Cert and Accreditation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$85,537.73

$7,270.71

$92,808.44

Cost

$27,370.12

CPFF

6.4- Test and Evaluation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$25,244.84

$2,125.28

$27,370.12

Cost

$3,522.57

CPFF

6.5- Configuration Change Transition Plan. . IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,246.61

$275.96

$3,522.57

Cost

$13,239.12

CPFF

6.6- Equipment Acquisition and Supplier Relationship Management. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$12,201.96

$1,037.16

$13,239.12

Cost

$3,451.34

CPFF

6.7- Configuration Management. IAW CACI's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,180.96

$270.38

$3,451.34

Cost

$3,292.62

CPFF

6.8-Release and Deployment. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,034.67

$257.95

$3,292.62

Cost

$129,128.06

CPFF

6.9-Operational Support. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$119,012.04

$10,116.02

$129,128.06

Cost

$0.00

CPFF

6.10- Transition to new contract. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$0.00

$0.00

$0.00

Cost

$50,815.00

COST

Other Direct Cost (ODC's) - (1) No profit shall be paid on purchases made under this CLIN. (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. COST REIMBURSEMENT (CR)- CONTRACT Month 5

Cost

$147,043.61

CPFF

Task 6.1-Task Order Management - IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I. Travel in support of the DTO PWS. All Travel must be pre-approved by the COR prior to the Contractor incurring the cost. Travel shall be in accordance with FAR Subpart 31.205-46. No first class travel is authorized.

$136,928.31

$10,115.30

$147,043.61

Cost

$226,150.57

CPFF

6.2- Service Design & Engineering- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$208,446.11

$17,704.46

$226,150.57

Cost

$95,767.62

CPFF

6.3- Security Eng Cert and Accreditation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$88,265.09

$7,502.53

$95,767.62

Cost

$27,271.02

CPFF

6.4- Test and Evaluation- IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$25,150.84

$2,120.18

$27,271.02

Cost

$3,644.60

CPFF

6.5- Configuration Change Transition Plan. . IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,359.07

$285.53

$3,644.60

Cost

$13,885.81

CPFF

6.6- Equipment Acquisition and Supplier Relationship Management. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$12,797.98

$1,087.83

$13,885.81

Cost

$3,411.11

CPFF

6.7- Configuration Management. IAW CACI's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,143.88

$267.23

$3,411.11

Cost

$3,273.76

CPFF

6.8-Release and Deployment. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$3,017.29

$256.47

$3,273.76

Cost

$133,792.69

CPFF

6.9-Operational Support. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$123,311.23

$10,481.46

$133,792.69

Cost

$0.00

CPFF

6.10- Transition to new contract. IAW Raytheon's proposal dated August 14, 2013. This contract will be incrementally funded IAW 52.232-22- Limitation of Funds clause. See full text in Section I.

$0.00

$0.00

$0.00

Cost

$50,700.00

COST

Other Direct Cost (ODC's) - (1) No profit shall be paid on purchases made under this CLIN. (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. COST REIMBURSEMENT (CR)- CONTRACT Month 6

Section C - Descriptions and Specifications

DTO BRIDGE PWS

ENCORE II TASK ORDER (TO) PERFORMANCE WORK STATEMENT (PWS)

as of 25/Jul/2013

1. Contracting Officer’s Representative (COR).

a. Primary COR.

Department of Defense Activity Address Code (DODAAC):

HC1047

Ft. Meade, MD 20755-0549

b. Alternate COR.

Ft. Meade, MD 20755-0549

2. Task Order Title. Bridge Contract: Multinational Information Sharing (MNIS) Design, Transition and Operations (DTO)

3. Background. The MNIS Program Management Office (MNIS PMO) was established by Department of Defense INSTRUCTION (DoDI) NUMBER 8110.1, SUBJECT: Multinational Information Sharing Networks Implementation, February 6, 2004, to provide standardized network services to Combatant Commands (COCOM), United States (US) coalition partners and Mission Partners (MPs). MNIS provides the infrastructure backbone, centralized network management, common services and core applications, for both MNIS classified and unclassified networks, to support and host COCOM, US coalition and MP communities of interest (COIs) and related activities. The DoDI established the MNIS PMO role of setting and maintaining standards for “networks, software, hardware, and interfaces” in a manner that permits integration into “the operation of existing DoD general service networks” and leverages “existing multinational information sharing system/network capabilities” to allow the COCOMs and other customers to “operate their . . . enterprise networks regionally as an integrated element of the global MNIS . . . network.”

MNIS networks directly support the warfighting commands and consist of three (3) networks:

· Combined Enterprise Regional Information Exchange System (CENTRIXS);

· Pegasus/Griffin Improved Connectivity Initiative (ICI), a Five Eyes cross-domain solution; and,

· Combined Federated Battle Laboratories Network (CFBLNet), which is a Research, Development, Test and Evaluation (RDT&E) network supporting trials and assessments of potential solutions for coalition requirements.

CENTRIXS networks are a combination of global, multilateral and bilateral virtually separate networks supporting multinational efforts including, but not limited to the International Security Assistance Force (ISAF) in Afghanistan, and Overseas Contingency Operations (OCO). These networks form the backbone of what is envisioned to become a global infrastructure, allowing the US to rapidly share information with coalition partners worldwide, in support of local, regional and global combined operations. CENTRIXS is designed to be a global, interoperable, interconnected, inexpensive, and easy-to-use information sharing system.

CENTRIXS is installed in partner nation countries and their military forces after they establish their specific requirements and vet those requirements with the supporting COCOMS. CENTRIXS implementation initially focused on fielding core collaboration services (e.g., email with and without attachments, web-browser-based data access, and file sharing). Other required services to include tactical, near-real-time data access have been enabled as the network has matured. The basic mission of CENTRIXS is to support the secure sharing and exchange of intelligence and operational information through reliable communications connectivity, data manipulation, and automated processes.

CENTRIXS services provide COCOM commanders with:

· Common Operational Picture (COP)

· Common Intelligence Picture (CIP) Electronic mail (email) with attachments

· Web-enabled services, office automation, bulletin boards, and chat service (collaboration services)

· Voice over Secure Internet Protocol (VoSIP)

CENTRIXS uses existing communications infrastructures, such as the Secret Internet Protocol Router Network (SIPRNet), whenever possible. The system employs National Security Agency (NSA)-Approved Type-1 encryption devices and uses an encrypted channel between Area of Responsibility (AOR) locations, strategic or tactical.

On 31 March 2010, the CENTRIXS production baseline was enhanced with CENTRIXS Cross Enclave Requirement (CCER) capability to provide a Net-Centric approach (Global Enterprise) in order to provide cross community of interest (COI) information sharing built on centralized network management, common services and core applications. Legacy coalition networks were cryptographically isolated making it impossible to quickly and accurately move information from one COI to another. CCER enhanced CENTRIXS capability by enabling cross-COI information sharing through tightly controlled relabeling of information controlled and audited via a gateway concept. In October 2011, Department of Defense (DOD) Chief Information Officer (CIO) and Joint Staff senior leadership realigned CCER priorities to first focus on a Common Mission Network Transport (CMNT) capability. CMNT provides improvements to CENTRIXS transport infrastructure and increases efficiencies across the network for management and implementation time.

The Combined Communications Electronics Board (CCEB) Nations changed the name Griffin to Pegasus ICI at the June 2010 principals’ meeting. Pegasus ICI (Griffin) is a framework to provide a permanent, multi-nationally developed, managed, and resourced capability that enables the exchange of information between the classified networks of participating nations at the SECRET level. It encompasses necessary infrastructure, connectivity, applications, services, management, and governance. The reach of Pegasus ICI (Griffin) is directly dependent on the ability of each nation's classified network to extend to the lower levels of the command and control hierarchy. All nations that participate on Pegasus ICI (Griffin) contribute materially and in-kind to the development, operation, and management of the capability. The Pegasus ICI (Griffin) infrastructure is a network of guards allowing email between national systems.

The information communicated between the information systems includes email with attachments. Future capabilities and services of Pegasus ICI (Griffin) will include COP, web services, chat services, national reach-back services, as well as other planned capabilities. Pegasus ICI (Griffin) consists of a standardized set of equipment and applications to provide MNIS Global Information Grid (GIG) services among the national networks of participating nations.

CFBLNet is a flexible and scalable service provider for multinational distributed experimentation. The CFBLNet vision is to provide the infrastructure of choice for international Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) research, development, trials, and assessments to explore, promote, and confirm Coalition/combined capabilities for the participants (US, CCEB and North Atlantic Treaty Organization (NATO)). CFBLNet supports 200-300 coalition initiatives a year including the Multinational Experiment (MNE).

The sustaining vision of the CFBLNet is to provide the infrastructure of choice for international C4ISR research, development, test and accreditation (RDT&A) in order to explore, promote, and confirm coalition/combined capabilities and interoperability for the participants.

Summary of MNIS Functional Baseline:

The MNIS CONOPS describes an information sharing environment enabling combatant commanders to rapidly and effectively share and consume information from US coalition partners and MPs operating across the strategic, operational, and tactical continuum, to include potential federal, state, local, and tribal MPs. This CONOPS integrates joint force actions with agencies, non-governmental organizations (NGO), first responders, and private volunteer organizations within the US as well as in a multinational environment, whether the US is leading the operation or participating as a MP.

The emerging capabilities within MNIS extend US MNIS capabilities to MPs and beyond, thereby allowing US, MPs, and traditional and non-traditional coalition partners the ability to share, collaborate and synchronize information, providing the ability to interoperate with and leverage MPs.

The current program baseline includes the management of the four (4) major classified information sharing components – CENTRIXS, Common Mission Network Transport (CMNT) (a capability that is part of CENTRIXS), Pegasus ICI (formerly Griffin) and CFBLNet – as well as the unclassified capability known as Unclassified Information Sharing Service (UISS). Additional baseline funding accounts for a change in priority from cross-enclave technologies to transport capabilities for CMNT.

The insertion of UISS leverages commercial technologies and infrastructure to provide combatant commands the unique operational capability to support coordination, cooperation and collaboration with MPs, diverse actors and organizations who participate in multi-agency operations, complex humanitarian operations. The MNIS mission is to provide an information sharing environment enabling commanders to rapidly and effectively share and consume information from U.S. coalition partners and MPs operating across the strategic, operational, and tactical continuum, to include potential federal, state, local, and tribal mission partners. This concept integrates joint force actions with agencies, NGOs, first responders, and private volunteer organizations within the U.S. as well as in a multinational environment, whether the U.S. is leading the operation or participating as a mission partner.

4. Objectives. The Government requires network engineering services to directly support the MNIS PMO in the design, transition and operation (DTO) of MNIS’ CENTRIXS, Pegasus and potentially other classified networks, which directly support United States (US) military forces, North Atlantic Treaty Organization (NATO) and US Coalition members with critical war planning and warfighting capabilities. MNIS networks also support mission partner (MP) and international disaster and humanitarian operations.

5. Scope. The Contractor shall provide network engineering and other support services to MNIS PMO’s classified networks, except CFBLNet. The scope of effort under this Task Order (T.O.) includes the capability to perform the full range of requirements outlined below.

a. Network engineering technical capabilities, including network design, transition and operation services. The key capabilities include:

i. Design and integration of MNIS services to meet DoD, DISA or other applicable policies and mandates. This includes design, development, testing, transition, operation, and maintenance of worldwide services

ii. Defense Information Assurance Certification and Accreditation Process (DIACAP) and other Information Assurance requirements

iii. Change management, Engineering Change Proposals (ECPs) development and processing through the MNIS Engineering Review Board (ERB), and Change Advisory Board (CAB)

iv. Transition Planning

v. Familiarity with functional, security and integration testing and testing support at Joint Interoperability Test Center (JITC) and National Security Agency (NSA) laboratories

vi. Configuration Management

vii. Knowledge Management

viii. Tier 3 Support for deployed networks and services 8/5 (tier 3 is located at MNIS PMO central offices at DISA, 6910 Cooper Avenue, Fort Meade, MD, 20755-0549. Tier 3 is 8X5 with a two hour after-hours response time.)

b. Transition of activities described above in 5.a. and technical data to new DTO contractor

i. Transition of any Government-owned technical data to new contractor

ii. Knowledge management engagement with new contractor

The following Encore II task areas apply to this PWS:

· Task Area 1 - Enterprise IT Policy and Planning

· Task Area 2 - Integrated Solutions Management

· Task Area 3 - Performance Benchmarking

· Task Area 4 - Business Process Reengineering

· Task Area 5 - Requirements Analysis

· Task Area 7 - Information and Knowledge Engineering

· Task Area 9 - Product Integration

· Task Area 10 - Test and Evaluation

· Task Area 12 – Communications Engineering

· Task Area 13 – Security Engineering Certification and Accreditation

· Task Area 16 – Web Services

· Task Area 17 – Operations Support

· Task Area 18 – Hardware

· Task Area 19 – Software

· Task Area 20 – Managed Services

6. Performance Requirements.

6.1 Task 1. Task Order Management

6.1.1 Subtask 1 – Program Management. The Contractor shall designate a dedicated Program Manager (PM) to act as the single point of contact with the MNIS PMO. The Government requires the contractor to provide a lead Program Manager (PM) with either an industry certification as a project management professional (PMP) or government certifications in program management (i.e., Defense Acquisition Workforce Improvement Act (DAWIA)). The PM shall keep the Government Task Monitor (TM) and Contracting Officer (KO) informed of the status of the technical and managerial efforts and expenditures on the contract. The PM shall keep the appropriate Government representatives informed by telephone, email and meetings on all issues requiring a timely resolution. The PM shall have latitude in assigning Contractor personnel to the various tasks with prior coordination with TM. The PM shall provide qualified task leads to assist the Government in managing the delivery of required support. The number and assignment of task leads can be changed from time to time to match the majority of the effort with the prior approval of the TM.

The Government will provide space within its facilities as indicated in paragraph 9 below. For other key personnel, the Contractor shall have an established facility that will allow a three (3) hour response to a request for face-to face meeting at DISA’s site. This three (3) hour response shall be required during normal business days within the core hours between 0900 and 1500. Other personnel can be available via conference call or similar electronic means. Many meetings can occur via a conference call or similar electronic means.

6.1.2 Subtask 2 – Monthly Progress Report. The Contractor shall submit a Monthly Progress Report (MPR) (Deliverable 1) that identifies the significant activities and accomplishments, work products delivered, status of satisfying the agreed-to schedule for ongoing deliverables, and current issues. The MPR shall document also any new or revised deliverable schedules. The report shall identify any actions the Government needs to take and the schedule of when they are needed. The MPR shall summarize the progress and status of all work in process on tasks of this PWS. The MPR shall document all of the problems encountered, actions taken to address the problem, minimize further risk and provide the resultant impact. (e.g., changes to the schedule).

The MPR shall also include manpower and cost reporting including Other Direct Costs (ODCs) (e.g. travel), and its expenditure level shall be compared against the financial plan for the task order base and options, if applicable. The cost data shall be reported in dollars and reflect fully burdened costs (inclusive of all overhead costs and fees). Any actual or projected deviation from cost, schedule and performance shall be reported and explained in the report. If necessary, mitigation strategies shall be presented and discussed with the TM. The cost manpower and amount of work completed shall use the Earned Value Management (EVM) methodology. The cost shall be summarized by system (Pegasus/Griffin, CENTRIX, and CMNT) network and release. The costs shall also be separated by equipment, personnel, travel, and ODC. The Government realizes that to support a number of tasks, work is done once to cover all the systems and networks or is small. Where such exists, the costs shall be reported for one system or network and a note included for costs on the other systems/networks as to where the costs are recorded. (One objective of the PMO is that common documents, equipment, and processes will support multiple systems/networks and thus avoid unnecessary costs.)

The MPR shall also report on administrative matters including:

· Personnel reassignments, including all personnel added to or removed from the task order by task

· Trips, technical visits, and related results for the reporting period

· Visit request, DISA picture badge and CAC status for personnel who require each

6.1.3 Subtask 3 – In-Progress Review (IPR) Meetings. The Contractor shall also participate in IPRs on a regular and recurring basis during the term of the task order to address current status of contractual, technical and programmatic requirements. The Contractor shall informally coordinate the agenda and meeting date/time with the TM prior to each meeting to ensure all the topics that Government wants covered are included. The Contractor shall present a formal briefing (Deliverable 2) covering the agreed upon topics.

6.1.4 Subtask 4 – Integrated Master Schedule. The Contractor shall establish an Integrated Master Schedule (IMS) (Deliverable 3) depicting for this task order its planned duration, all phases of equipment lifecycle activities, planned start and finish dates, associated resources, and relationship dependencies to other MNIS service support contracts. An IMS shall be established to ensure that monthly progress reflects a projected timely completion of DTO activities.

6.1.5 Subtask 5 – Contingency Operations Plan. The Contractor shall prepare and submit a Contingency of Operations Plan (COOP) to the Government. The COOP shall be updated on a quarterly basis (Deliverable 4). The COOP shall document Contractor plans and procedures to maintain MNIS support during an emergency. The COOP shall include the following:

· A description of the Contractor’s emergency management procedures and policy

· A description of how the Contractor will account for its employees during an emergency

· Planned temporary work locations or alternate facilities

· How the Contractor will communicate with MNIS during emergencies

· A list of primary and alternate Contractor points of contact, each with primary and alternate

· Work phone numbers

· Home phone numbers

· Cell phone numbers

· E-mail addresses

· Procedures for protecting Government furnished equipment

· Procedures for safeguarding sensitive and/or classified Government information

6.1.6 Subtask 6 – Program Reviews. The Contractor shall plan and conduct monthly Contractor Performance Report (CPR) meetings with the Government, in person or via teleconference, video-teleconference or collaborative software applications as agreed upon by the Government, to review progress and cost, schedule, and performance (C/S/P) status of activities under this contract. The Contractor shall provide insight into expenditures such as: 1) total invoiced; 2) remaining funds; and, 3) anticipated expenditures for both labor and ODCs, staffing, progress, risks, milestones, and status of GFE, including Contractor purchased, Government-owned items. The Contractor shall address cost/price, schedule, performance, and status of each critical task of this contract, noting any problems or risks and alternatives, and recommending solutions and identification of tasks requiring Government decision or interaction.

The Contractor shall ensure that the CPR (Deliverable 5) is provided to Government participants not later than three (3) working days prior to the meeting, and that data presented at program reviews is correct and not more than ten (10) working days old as of the date of the meeting. Meeting Minutes (Deliverable 5a) shall be delivered to the Government within five (5) working days following the CPR Review.

6.1.7 Subtask 7 – Operations During Emergency Situation. Individual contingency operation plans shall be activated immediately after determining that an emergency has occurred, shall be operational within twelve (12) hours of activation, and shall be sustainable until the emergency situation is resolved and normal conditions are restored or the contract is terminated, whichever comes first. In case of a life threatening emergency, the COR will immediately make contact with the Contractor Task Managers to ascertain the status of any Contractor personnel who were located in Government controlled space affected by the emergency. When any disruption of normal, daily operations occurs, the Contractor Task Manager shall promptly open an effective means of communication with the COR and verify:

· Key points of contact (Government and Contractor)

· Temporary work locations (alternate office spaces, telework, virtual offices, etc.)

· Means of communication available under the circumstances (e.g., email, webmail, telephone, FAX, courier, etc.)

· Essential work products expected to continue in production, by priority.

The Contractor Task Monitor shall make use of the resources and tools available to continue MNIS contracted functions to the maximum extent possible under emergency circumstances. The Contractor shall obtain approval from the COR and Contracting Officer prior to incurring costs over and above those allowed for under the terms of this contract. Regardless of contract type and of work location, Contractors performing work in support of authorized tasks within the scope of their contract shall charge those hours accurately in accordance with the terms of this contract.

6.1.8 Subtask 8 – Kick-off Meeting. The Contractor shall schedule a kick-off meeting in coordination with the Government within fifteen (15) days after contract award. The Contractor shall meet with MNIS leadership, as appropriate, to present an overview of their approach and establish schedules, procedures, and points of contact necessary to conduct the tasks outlined herein. The primary outcome of this meeting is to come to an agreement on the cost, schedule and performance baselines.

6.1.9 Subtask 9 – Contract Close-out. At the conclusion of the contract, the Contractor shall support the Government in planning and implementing a complete transition of the tasks contained in this task order to a follow-on vendor. This shall include formal coordination with the Government and follow-on contractor. It shall also include the delivery of copies of existing documentation and transfer of Government owned lab equipment.

Deliverables:

MPR (Deliverable #1) IPR Meeting Formal Briefing (Deliverable #2)

IMS (Deliverable #3)

COOP (Deliverable #4)

CPR Briefing (Deliverable #5)

CPR Meeting Minutes (Deliverable #5a)

6.2 Task 2. Service Design and Engineering

The primary group within the PMO concerned with service design is the Engineering Review Board (ERB), which manages the system engineering process that evaluates new or modified engineering requirements and new capabilities and conducts evaluations. In support of the ERB, the Contractor shall provide expertise in DOD and DISA systems engineering practices and procedures. The Contractor shall establish, execute, and maintain system engineering policies, plans, and processes consistent with the development and maintenance of the proposed system architecture, to include all legacy systems. The Contractor shall provide subject matter experts (SME) in support of MNIS technical reviews (e.g., Integrated Baseline Review, Preliminary Design Review, Critical Design Review), and other capability/service technical reviews as directed by the MNIS PMO. The Contractor shall develop and document systems’ architectures in accordance with the DoD Architecture Framework (DODAF).

The Contractor shall take requirements, consider technical alternatives for addressing them, prepare and submit design solutions for review and Government approval. Normally system designs or changes will use the model or type of equipment already employed in the service unless that equipment is at end of life or cannot satisfy the requirements. In such cases, the Contractor shall ascertain equipment functionality/capability through research or testing as appropriate. The Contractor shall provide input into effort to develop alternatives and business cases, especially relative to equipment costs and transition/deployment strategies.

The contractor’s design shall maximize the use of COTS. Hardware, software, and firmware utilizing cryptographic modules shall meet Federal Information Processing Standards (FIPS) 140-2 (most current version) cryptographic Protection Level 3 or higher and will be validated via Cryptographic Module Validation Program (CMVP). For COTS products used in the contractor design, the contractor shall provide the commercial product documentation.

The contractor must perform systems engineering to select the appropriate hardware and software to satisfy the requirements provided by the PMO. The contractor must also do the detailed installation design to make it operational at the designated site to include racks, cabling, power, HVAC and other mechanical and electrical support systems, and configuring the HW/SW.

Another MNIS support contractor has primary responsibility for working with DISA/Network Services (NS) for DISN network management and communications engineering. For MNIS capabilities over and above what DISN will provide, the other MNIS support contractor will define the requirements. The Contractor shall participate in the development of the defining the network management capabilities not provided by DISN. The Contractor shall include such requirements in its equipment design and other tasks.

The types of hardware include routers, firewalls, servers, storage and test sets. The types of software include authentication, domain name service, intrusion detection and prevention, database, antivirus, email, and network monitoring.

6.2.1 Subtask 1 – Systems Engineering Documentation Support. The Contractor shall provide support to develop, update or maintain the systems engineering documents in Table 1. This list is not all inclusive.