MPE-S_RFP.pdf

CODE

(Hour)

PAGE(S)

until 08:00 AM local t ime 10 Sep 2018

X

A X B X C

D

EX

X G F 59 - 65

66 - 85 X H 86 - 94 andriani.buck.civ@mail.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 94

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

HC1047 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

ANDRIANI BUCK 301-225-4118

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 6

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

7 - 25 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

27 - 28 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 29 - 35 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 36 - 46 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

47 - 57

PART II - CO NTRACT CLAUSES

DEFENSE INFORMATION SYSTEMS AGENCY

P.O. BOX 549

FT. MEADE MD 20755

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

09 Aug 2018

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HC104718R4012

Section B - Supplies or Services and Prices

SECTION B

B.1. MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

(a) Maximum. The maximum Contract ceiling value of all Task Orders in this single award procurement is established at $998,000,000.00 dollars.

(b) Minimum. The minimum guaranteed award amount for this Indefinite-Delivery, Indefinite-Quantity (IDIQ) Contract is $500.00 dollars for the full term of the Contract.

(c) The Government has no obligation to issue Task Orders to the Contractor beyond the amount specified in paragraph (b).

B.2. TASK ORDER CONTRACT TYPES

This is a single award IDIQ Contract for the Department of Defense (DoD) Mission Partner Environment service-based requirements that allows the utilization of fixed price and cost contract types in Task Orders. Task Order contract types permitted include FAR 16.2 Fixed-Price and FAR 16.3 Cost-Reimbursement. Task Orders may incorporate FAR 17.2 Option periods procuring Commercial items or Non-commercial items. These Contract types can be used individually or in combination within a single Task Order comprising multiple Contract Line Item Numbers (CLINs).

B.3. FIXED PRICE (FP) LABOR RATES

The Fixed Price Labor Rates proposed represent the Offeror’s fully-burdened fixed price hourly labor rates for each skill classification for work performed at Government and Contractor sites both in the Contiguous United States (CONUS) and Outside the Contiguous United States (OCONUS). The rates provided in the pricing template will be used as ceiling labor rates for pricing of all labor proposed under future fixed priced tasks issued under this IDIQ Contract. At time of award, the Contractor’s Fixed Price (FP) ceiling labor rates will be incorporated into the Contract.

B.4. COST PLUS FIXED FEE (CPFF) LABOR RATES

The Cost Plus Fixed Fee Labor Rates proposed represent the Offeror’s CPFF hourly labor rates for each skill classification for work performed at Government and Contractor sites both in the Contiguous United States (CONUS) and Outside the Contiguous United States (OCONUS). All indirect rates must be in accordance with the its current Forward Pricing Rate Agreement (FPRA)

B.5. TRAVEL PRICING (ALL ORDER TYPES)

Contractor personnel may be required to travel to support the requirements of this Contract as stated in individual Task Orders. Local travel and travel outside of the local area may be required both in the CONUS and OCONUS.

For those Task Orders requiring travel, the Contractor shall include estimated travel requirements in the proposal as required by the Task Order instructions. Travel shall not commence without prior written consent in accordance with instructions in the Task Orders.

If authorized in the Task Order, travel will be reimbursed at actual cost in accordance with the limitations set forth in FAR Subpart 31.205-46, Travel Costs. Profit shall not be applied to travel costs. To the extent authorized by the Task Order, Contractors may apply indirect costs to travel in accordance with the Contractor’s usual accounting practices consistent with FAR 31.2.

B.6. OTHER DIRECT COSTS (ODCs) (ALL ORDER TYPES)

ODCs may consist of hardware, software, materials, and Task Order-related items that are fundamental to the services being performed. The cost of general-purpose items required for the conduct of the Contractor’s normal business operations will not be considered an allowable ODC in the performance of this Contract. Profit is not allowed on ODCs for any Task Order; however, applicable burdens are allowed in accordance with Contractor’s accounting practices. If applicable, the Contracting Officer (KO) will identify an estimated ODC ceiling under a separate CLIN on the Task Order.

B.7. WORK OUTSIDE THE CONTIGUOUS UNITED STATES (OCONUS)

Task Orders issued under this IDIQ may require performance outside the Contiguous United States (CONUS).

CONUS means the 48 contiguous States and the District of Columbia. Any applicable clauses for OCONUS work will be added to the Task Orders, as applicable.

OCONUS includes:

1. OCONUS. Outside of the contiguous United States

2. NON-FOREIGN OCONUS AREA. The states of Alaska and Hawaii, the Commonwealths of Puerto Rico and the Northern Mariana Islands, Guam, and U.S. territories and possessions.

3. FOREIGN AREAS. It is anticipated that there may be Task Orders under this Contract for work outside the United States. The Contractor will be compensated for work performed OCONUS pursuant to the Task Order, including any applicable Status of Forces Agreements (SOFA) or Technical Expert Status Accreditation (TESA).

Standard references for OCONUS pricing include:

The U.S. Department of State’s Bureau of Administration, Office of Allowances, (https://aoprals.state.gov/) publishes quarterly report indexes of living costs abroad, per-diem rate maximums, quarter’s allowances, hardship differentials, and danger pay allowances for Contractors to follow when proposing on OCONUS efforts. No allowances, other than those listed by the U. S. Department of State, shall be allowed on Task Orders.

The Department of State Standardized Regulations (DSSR) are the controlling regulations for allowances and benefits available to all U.S. Government civilians assigned to foreign areas; however, for Task Orders issued under the Base Contract, Contractor civilians assigned to foreign areas shall not exceed the allowances and benefits in the DSSR as well.

For OCONUS Task Orders where costs are not specifically addressed in the DSSR, the Government will reimburse the Contractor for all reasonable, allowable, and allocable costs in accordance with FAR 31, Contract Cost Principles and Procedures.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Months Labor - FFP

FFP

All variations of Fixed Price (FP) Labor utilizing any variation of contract type(s).

Ordering Period of Five (5) years from Date of Award.

FOB: Destination

NET AMT

0002 Months Labor - Cost Reimbursable

COST

All variations of Cost Reimbursable (CR) Labor utilizing any variation of contract type(s).

ESTIMATED COST

0003 Lot Travel

COST

Travel in support of the Performance Work Statement (PWS). (1) No profit shall be paid on travel made under this CLIN; however, DCAA approved burden rates are authorized; (2) Travel must be incidental to the work being performed under this contract; (3) Non-local Travel must be pre-approved by the Contracting Officer Representative (COR) prior to the Contractor incurring the cost; (4) Travel will be on a cost reimbursement basis only. 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 and the Joint Travel Regulation (JTR).

0004 Lot Other Direct Costs (ODCs)

COST

ODCs in support of PWS. (1) No profit shall be paid on purchases made under this CLIN; however, DCAA approved burden rates are authorized; (2) ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable; (3) ODCs may be purchased from General Service Administration (GSA) Schedules or Enterprise Software Initiative (ESI), if available and authorized by the Contracting Officer; (4) ODCs must be incidental to the work being performed under this contract; (5) 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.

Ordering Period of Five (5) years from Date of Award.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

0005 1 Each Minimum Guarantee

FFP

The minimum guarantee may be invoiced for and paid after the attendance of the Kick-Off Meeting and the delivery and acceptance of the Supply Chain Risk Management (SCRM) plan. The minimum guarantee is $500.00.

9999 Lot Surge Capacity

FFP

The Government may require surge support during the ordering period or any option period and surge modifications must be in-scope to provide increased support for the defined task areas of the PWS. Surge support is OPTIONAL and is not a guarantee. If the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the Surge Option unilaterally.

The Contracting Officer will provide written notice to the Contractor at least seven

(7) calendar days prior to any unilateral exercise of the Surge Option. In the event the Government does elect to exercise the Surge Option, surge support will be realigned under new or existing CLINs for the relevant task areas identified in the PWS, and an equal amount will be deducted from the Surge CLIN not-to-exceed amount. Surge support will be provided at the same labor rates proposed and found fair and reasonable at time of Task Order award for the applicable period of performance. Surge support over the life of the Contract will not exceed 35% of the Contractor's total proposed price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 18 May 2018

Contract Number: (completed by the KO at time of Contract or TO award) Task Order Number: (completed by the KO at time of TO award or N/A) Contractor Name (completed by the KO at time of Contract or TO award) Tracking Number: (completed by the KO when complete package is received) Previous Contract and Task Order Number:

The effort is new and subsumes ENCORE II Contract number HC1028-08-D-2016; Task Order number VC04

1. Contracting Officer’s Representative (COR). See Section G.5., Points of Contact, which will be included in the awarded Contract.

2. Contract Title. Mission Partner Environment-Services (MPE-S)

3. Background. MPE-S is a new requirement to supply the full-range of Mission Partner Environment (MPE)-compatible services and associated supply items to the Department of Defense (DoD) and its Mission Partners (MPs).

The emergent MPE “connects nations, decision makers, staffs, and people to common information and data resources. It is leader centric and network enabled, reflecting the commander’s decision-making requirements balanced against risk. Operationally, improved information sharing enables the commander’s ability to create unity of effort, possess speed of command and build trust during Mission Partnered operations. It is the essence of our ability to fight as one team with our Mission Partners.” (Source: “Business Case Analysis: Final, Mission Partner Environment – Information System (MPE-IS) V1.0, July 29, 2016).

The MPE utilizes an operational framework to provide the DoD and its Mission Partners (MPs) effective information sharing and data exchange through planning, preparation, training, and execution of operations. The operational framework allows MPE members to develop a network for rapid information sharing and data exchange in a common language and at a prescribed security classification level. MPE facilitates the connection, reception, collection, correlation, gathering, and sharing of information from multiple and often disparate MP networks to the appropriate end users in order to increase situational awareness, informed decision making, collaboration, and successful mission execution, training, testing, experimentation, and operational events.

The MPE information sharing and data exchange environment allows for both: (1) continuous information sharing between the DoD and MPs, and (2) episodic information sharing and data exchange arrangements for specific missions, which may include unanticipated partners. Services and associated supply items related to the “Steady State Operation of the MPE” allow continuous information sharing between the DoD and MPs to occur on an ongoing and uninterrupted basis. Episodic information sharing and data exchange arrangements often require “Design, Development and Transition of MPE Services, Programs, Releases and Projects” to enable short-term episodic arrangements to be established on a rapid basis.

The episodic MPE operational framework requires the rapid establishment of an information sharing and data exchange, tailored to a specific mission, with unanticipated partners, and with minimal notice. The episodic MPE framework employs a federated network model where multiple, different MP networks utilizing different applications and tools are connected in order to share and/or exchange specified information and/or data.

Capabilities available under this Indefinite Delivery/Indefinite Quantity (ID/IQ) Contract include advanced design, prototyping, development, testing and implementation of new technologies and approaches, and Tier 2 and 3 services.

In addition to MPE SECRET//RELEASABLE networks and information systems, MPE also includes an Unclassified Information Sharing Systems (UISS) portfolio, which features the All Partners Access Network (APAN). APAN is the premier unclassified information sharing and collaboration enterprise for the DoD.

4. Objectives.

The Contractor shall supply all services and associated equipment to design, implement and operate the MPE enterprise. The Contractor shall ensure all services and associated equipment conform to, or are compatible with, MPE architecture, standards, and specifications. The Contractor shall interface its activities with other Contractors performing local MPE-S for the Combatant Commands (CCMDs) and other DoD components.

5. Scope.

The scope is to provide full MPE life cycle services at the enterprise level for all legacy and emergent Multinational Information Sharing (MNIS)/MPE networks, systems and projects. This Contract will specifically provide on an on-demand basis, the full array of services and all functional elements such as capabilities and requirements analysis;

engineering; engineering management; software development; business management; program management; the provision of information technology (IT) equipment, interconnected system(s), or subsystem(s) of equipment; life cycle logistics; and, test and evaluation and associated items of supply, equipment, hardware, software, parts, tools and infrastructure to the MPE-IS and any related program, system, project, study, or other efforts, including legacy systems contributing to, or interfacing with, the MPE-IS, which are needed to deploy and operate the worldwide MPE. This Contract will also provide the full-range of services for Command, Control, Communications, Computer and Intelligence, Surveillance and Reconnaissance (C4ISR) Systems and any related or successor systems to the Combatant Command, Service, or Agency (CC/S/A)’s and any other DoD components engaged in any manner in supporting the MPE.

Specific details of task assignments, deliverables, delivery locations, documentation, training, applicable Government/DoD/Customer/Industry standards will be provided within individual Task Orders.

Four task areas constitute the technical scope of this Contract:

Task Area 1: Contract and Task Order Management Task Area 2: Design, Development and Transition of MPE Services, Programs, Releases and Projects Task Area 3: Steady State Operation of the MPE Task Area 4: Supply Chain Risk Management (SCRM)

The Government may require surge support during the base or any option period. Surge modifications will be within the scope of the Contract and any Task Order issued under this Contract and will provide increased services for the defined task areas of this PWS. Surge support over the life of the Contract will not exceed 35% of the Contractor’s total proposed cost/price for the base and all option periods, including a six-month extension of services pursuant to

FAR 52.217-8.

6. Performance Requirements.

6.1 Task 1 – Contract and Task Order Management

6.1.1 Subtask 1 – Service Management Plan (SMP) – The Contractor shall develop an ISO/IEC 20000 SMP tailored to the specific services required under this Contract. The Contractor shall incorporate engineering and business best practices into its management of all services, releases and projects. The Contractor’s overall approach for integrating the two shall be described in the SMP. The Contractor’s adherence to this SMP process shall be reviewed at Contract and Task Order Contractor Performance Reports (CPRs), and shall be incorporated into 90 Day Action Plans and Integrated Master Schedules (IMSs). The content of the SMP shall be in accordance with ISO/IEC 20000- 2:2012. An initial SMP shall be submitted with the Contractor’s proposal, and an updated version 60 days after award of the first Task Order. The SMP shall be updated thereafter in accordance with ISO/IEC 20000-2:2012 and Contractor implementing procedures.

Deliverable: Service Management Plan (SMP)

6.1.2 Subtask 2 – Monthly ID/IQ Progress Report (MPR) – The Contractor shall submit an MPR that addresses all elements of the Contractor’s SMP, in a format mutually agreed upon with the Government. If not specifically addressed in the Contractor’s SMP content, the MPR shall include:

- A brief description of activities and deliverables during the current month by Task Order. This description shall include problem definition and recommendations for program resolution. Particular attention shall be given to risk management and cybersecurity activities

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

- Identification of key personnel and personnel reassignments including personnel added or removed from the ID/IQ, Task Orders and all subtasks the Contractor will or did support

- Cost-reimbursement estimates, estimated date of funds depletion, and the status of invoicing. Status of

Contract line item numbers (CLIN) ceilings, obligations and projected demand.

Deliverable: Monthly Progress Report (MPR)

6.1.3 Subtask 3 – Monthly ID/IQ Contractor Performance Report – The Contractor shall develop a rolling 90 day action plan which shall be updated monthly. The plan, in conjunction with the MPR, shall serve as a baseline for the monthly CPR meeting with the Government program office, and the Contracting Officer, in person or via teleconference, video-teleconference or collaborative software applications as agreed to by the Government, to review progress, schedule and performance under this ID/IQ and all Task Orders. The Contractor shall prepare a CPR PowerPoint briefing to be utilized at the CPR meeting, which shall address staffing, progress, risks, milestones, Task Order owner feedback, invoicing, other direct costs (ODC), and status of Government Furnished Equipment (GFE), including Contractor-purchased, Government-owned items, if any. The Contractor shall address schedule and performance of each Task Order and the ID/IQ as a whole, noting any problems or risks and alternative courses of action (COA), recommending solutions and identifying tasks requiring Government decision or interaction. The Contractor shall proactively identify and prioritize risks and alternative COAs sufficiently in advance to permit Government intervention and action before a risk becomes an issue.

The Contractor shall ensure the CPR and an updated 90 Day Action Plan are provided to Government participants via the COR no less than three (3) days prior to the meeting, and that data presented at program reviews is correct and not more than ten (10) workdays old as of the date of the meeting. Meeting minutes shall be delivered to the Government within five (5) working days following the CPR Review.

Deliverables: Contractor Performance Report (CPR) CPR Meeting Minutes 90 Day Action Plan

6.1.4 Subtask 4 – Monthly Task Order Review – The Contractor shall develop a rolling 90 day action plan which shall be updated monthly. The plan shall serve as a baseline for the monthly CPR meetings with a Task Order holder, in person or via teleconference, video-teleconference or collaborative software applications as agreed to by the Government, to review progress, schedule and performance under a particular Task Order. The CPR shall address staffing, progress, risks, milestones, invoicing, ODCs, and status of GFE, including Contractor-purchased, Government-owned items, if any. For cost-plus-fixed-fee (CPFF) labor, the Contractor shall list all staff assigned to the Task Order by name and function, with the CPFF hours expended by each staff member during the month, and cumulative for the Task Order, against the Work Breakdown Structure (WBS) established in section 6.1.6. The Contractor shall address schedule and performance of the Task Order, noting any problems or risks and alternative COAs, recommending solutions and identifying tasks requiring Government decision or interaction. The Contractor shall proactively identify and prioritize risks and alternative COAs sufficiently in advance to permit Government intervention and action before a risk becomes an issue.

The Contractor shall ensure the CPR and an updated 90 Day Action Plan for the Task Order are provided to Government participants via the COR no later than three (3) days prior to the meeting, and that data presented at program reviews is correct and not more than ten (10) workdays old as of the date of the meeting. Meeting minutes shall be delivered to the Government within five (5) working days following the CPR Review.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverables: Contractor Performance Report (CPR) CPR Meeting Minutes 90 Day Action Plan

6.1.5 Subtask 5 – Transition-out SMP and Contract Closeout – The Contractor shall deliver a Transition-out SMP 120 calendar days prior to the end of this Contract. This SMP shall provide detailed procedures to enable the incoming Contractor to assume MPE-S without interruption or degradation of service. The Contractor shall transfer all operational materials to the Government and to the incoming Contractor including diagrams, user guides, technical topology and architecture, password lists, and programmatic information to ensure that the outgoing transition does not degrade MPE performance.

The Contractor shall conduct a formal Contract closeout process, including transition-out activities, to ensure continuity with the succeeding Contractor.

Deliverable: Transition-out SMP

6.1.6 Subtask 6 – Integrated Master Schedule (IMS) – The Contractor shall develop and update weekly a Microsoft Project (MS Project) IMS for the work required under a Task Order. The Contractor shall use a WBS that aligns to the Task Order PWS.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Integrated Master Schedule (IMS) Work Breakdown Structure (WBS)

6.2 Task 2 – Design, Development and Transition of MPE Services, Programs, Releases and Projects

The Contractor shall design and transition MPE-S, programs, releases and projects. The Contractor shall develop a business case and technical estimate for each new service, release or project, unless waived, in writing, by the Government. The Contractor shall prototype, test and demonstrate the service or project, in cooperation with the lead Operational Test Agency (OTA) and potentially the Joint Interoperability Test Command (JITC). The Contractor shall transition or deploy and operationally test the service or project. The Contractor shall operate and maintain the service or project on an interim or permanent basis as determined by the Government. The Contractor shall provide, on an on-demand basis, the full-range of state-of-the-art hardware and software, and “as-a-service” offerings related to the design, development and transition of MPE services, programs, releases and projects, on a pay-for-use basis.

6.2.1 Subtask 1 – Systems Engineering and Development – The Contractor shall perform systems engineering and software-related tasks in accordance with the latest versions of Institute of Electrical and Electronics Engineers (IEEE) Standards 1220-2005 and 1362-1998, and ISO/IEC 15288. The Contractor shall translate Government-specified requirements into functional and systems requirements, and shall demonstrate the allocation of requirements to the subsystem level using an automated requirements traceability tool. The Contractor shall meet all cybersecurity requirements as part of this allocation process. Specific cybersecurity requirements may be detailed at the Task Order level.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Requirements Traceability Matrix Requirements Traceability Tool

6.2.2 Subtask 2 – Technology Roadmap, Prototyping, Testing, Installation, and Operation – The Contractor shall develop and maintain a roadmap of new technologies, which the Contractor has determined have potential for integration into the MPE within a five-year, rolling timeframe. This roadmap shall consider technologies with a maturity at least equivalent to RDT&E appropriation budget activity 03, “Advanced Technology Development.” The Contractor shall give first consideration to Commercially Available Off-the-Shelf (COTS) technologies and, second, to DoD Government Off-the-Shelf (GOTS) technologies.

The Contractor shall prototype and test new technologies in a sandbox (i.e., non-production) environment, potentially in cooperation with the OTA and JITC. The Contractor shall host engineering reviews to demonstrate performance of the technology at the key stages of its life cycle. The Contractor shall include a technology in the roadmap based on business factors (e.g., return on investment) as well as system technical refresh or performance improvements. The Contractor shall conduct site surveys in order to determine if the use of a site is feasible given space, infrastructure, and other requirements. The Contractor shall install the first article of the technology, and may install any or all of subsequent instances, as determined by the Government, based on the Government’s evaluation of the stability or complexity of the technology. The Contractor shall operate and maintain the new technology until the Government determines the technology meets all requirements and is stable, mature, suitable, effective, and/or ready to be fully deployed to all users. The Contractor shall install, test, and maintain multi-enclave clients (MEC) to support technology roadmaps, prototyping, testing, installation, and operation.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverables: Technology Roadmap

Engineering Review Checklist Site Survey Report Test Plan Test Results

6.2.3 Subtask 3 – Software Development and the Development/Security/Operations (Dev/Sec/Ops) Model – The Contractor shall develop software and applications for MPE systems and projects. The Contractor shall employ a Dev/Sec/Ops rapid or continuous delivery model for software and application development and delivery. This model may also be applied to special projects, products and services. This model shall be integrated with the Contractor’s ISO/IEC 20000 processes.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverables: Software Technical Documentation

Applications Planning and Release Management Plans Story Boards Priority Features List

6.2.4 Subtask 4 – Engineering and Business Management – The Contractor shall develop a business case and a Technical and Cost Estimate for any new service, release or project. The Business Case Analysis (BCA) shall feature an Economic Viability Assessment Methodology (Source: “DoD IT Business Case Analysis Template”) to determine the most favorable business alternative for meeting a technical requirement. The BCA shall take into account Coalition/MPE Future Years Defense Program (FYDP) funding profiles. The Technical and Cost Estimate shall support an integrated MPE, vice a stovepiped architecture. The Technical and Cost Estimate shall be standardized, uniform, and rate-based, for ease of Government review and comparison of successive estimates.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond

Deliverables: Business Case Analysis

Technical and Cost Estimate

6.2.5 Subtask 5 – Mission Partner Environment – Information System (MPE-IS) – The Contractor shall provide services to support the definition, development, testing, deployment and sustainment of the MPE-IS, a prospective Acquisition Category IA (ACAT IA), and any successor or related ACATs. Services shall include systems engineering, information technology architecting, cybersecurity, and systems acquisition documentation development in accordance with DoD Instruction (DoDI) 5000.02, SUBJECT: Operation of the Defense Acquisition System. Associated hardware, software, parts, tools and cloud services shall be procured as ODCs.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverables: DoD Architecture Framework (DoDAF) Views

DoDI 5000.02 Documents

6.2.6 Subtask 6 – Change and Configuration Management – The Contractor shall populate MPE Request for Change (RFC) forms based on its own Technical and Cost Estimates, and for requirements received through authoritative sources such as Chairman of the Joint Chiefs of Staff Instruction 6285.01C (CJCSI 6285.01C), “Multinational and Other Mission Partner (MNMP) Information Sharing Requirements Management Process,” and other CC/S/A requirements processes. The Contractor shall staff and process these forms and associated documentation through the Government’s change management workflow, which may include organizational entities such as the Engineering Review Board (ERB), Change Advisory Board (CAB), and Configuration Control Board (CCB). The Contractor shall conduct, track and manage all such actions. Once approved by the Government, the Contractor shall upload all configuration items (CI) into the MPE configuration management database (CMDB). The Contractor shall develop an Implementation Plan for each change, per individual customer Task Orders.

The Contractor shall keep the CMDB up-to-date. The Contractor shall develop and/or update the Configuration Management Plan (CMP), per individual customer Task Order. The Contractor shall perform a quarterly audit of the CMDB in order to ensure accuracy, consistency, and conformity with accepted practices. The Contractor shall report the results to include discrepancies, recommendations for close out or further action, and the documentation and tracking of action items.

The Contractor shall develop DoDAF views of the MPE/MPE-IS technical baselines. The Contractor shall develop Tactics, Techniques, and Procedures (TTPs) and CC/S/A directives and guidance for change and configuration management, as prescribed by individual Task Orders.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverables: Request for Change (RFC) Form

Change Implementation Plan Change and Configuration Management Tracking Sheet Configuration Management Database (CMDB) Audit Report DoDAF Views

Tactics, Techniques, and Procedures (TTPs)

6.3 Task 3 – Steady State Operation of the MPE

6.3.1 Subtask 1 – Tier 2 and Tier 3 Service Desks, and Knowledge Management – The Contractor shall provide Tier 2 and Tier 3 services. The Contractor shall be a certified Tier 3 Cybersecurity Service Provider (CSSP). The Contractor shall provide Tier 3 engineers who are experts in their fields and are responsible for not only resolving issues escalated by both Tier 1 and Tier 2 personnel, but also for the research and development of solutions to new or unknown issues. The Contractor Tier 3 engineers shall, when highly complex problems are encountered, coordinate troubleshooting and problem resolution activities with the original developers or original equipment manufacturers for in-depth analysis. As needed, the Contractor shall develop a workaround to return the service to operation, and publish the workaround to the Tier 1 and Tier 2 support organizations across all deployed MPE-S by leveraging the knowledge management environment. The Contractor shall verify the workaround complies with test and change management policies, as prescribed in individual Task Orders. The Contractor shall provide Tier 3 services for deployed networks and services during Task Order specified core hours.

The Contractor shall develop and maintain a Problem Management Database, which shall capture and concisely display Mean Time to Restore (MTTR) on all tickets assigned to Tier 3, either by escalation or other means; number of tickets open, pending, and closed; and, MPE network system operational availability (Ao) and reliability.

The Contractor shall develop TTPs for the Contractor’s Tier 3 processes, the devolution process for MPE, and MPE transition and implementation processes, and other MPE areas and processes as the need arises.

The Contractor shall create and operate a knowledge management environment, the primary purpose of which shall be to support Tier 3 services.

The Contractor shall document lessons learned for each Tier 3 incident. The lessons learned shall be delivered to the customer and made available in the knowledge management environment for future reference.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Lessons Learned Problem Management Database Knowledge Management Database Tactics, Techniques, and Procedures (TTPs)

CC/S/A Directives and Guidance Documents

6.3.2 Subtask 2 – Customer Relationship Management (Optional) – The Contractor shall have a Customer Account Representative(s) (CAR) who shall be the primary point of contact for the Contracting Officer’s Representative for Contractor performance under individual Task Order Contract. The CAR shall communicate COR concerns to the Contractor’s top management. The Contractor shall document receipt of these concerns and any remedies taken.

The Contractor shall incorporate these concerns into its Plan-Do-Check-Act (PDCA) cycle to achieve process improvements.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Customer Concerns Resolution Report

6.3.3 Subtask 3 – ISO/IEC 20000 Continuous Improvement – The Contractor shall continually improve its ISO/IEC 20000 Service Management System (SMS) and the services provided under this Contract through the Contractor’s institutionalized, routine exercise of the ISO/IEC 20000 PDCA methodology. The Contractor shall provide the Government with a copy of report(s) submitted to its top management listing continual improvement opportunities identified through the PDCA methodology, and how they may directly or indirectly affect the services provided under this Contract. The report shall also address actions the Contractor shall take to implement these improvement opportunities, with specific quantifiable, demonstrable improvements the Government will realize to services performed under this Contract. The Contractor shall also, on a monthly basis, collect and document recommendations from the Government on process or service issues the Government considers candidates for PDCA review. The Continual Improvement Opportunities Report shall report the Contractor’s disposition of these candidate items. In keeping with ISO/IEC 20000-2, risk to the services provided under this Contract shall be addressed through the PDCA methodology and associated deliverables.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond

Deliverable: Continual Improvement Opportunities Report

PDCA Candidates from the Government

6.3.4 Subtask 4– Other Integrated Product Support Elements – The Contractor shall perform supply tasks. The Contractor shall manage and maintain Bills of Material (BOM). The Contractor shall receive, store, inventory, transfer, issue, redistribute, and dispose of items. The Contractor shall catalogue, manage shelf life and warranties, and assure the integrity of the supply chain. The Contractor shall manage technical data pursuant to the technical data rights strategy specified at the Task Order level. The Contractor shall develop and update MPE product support TTPs. The Contractor shall develop and maintain technical standards and specifications. The Contractor shall develop and maintain technical manuals and drawings. The Contractor shall cleanse, migrate, verify and validate data. The Contractor shall store and backup data. The Contractor shall provide training. The Contractor shall develop and deliver computer-based training/distance learning. The Contractor shall provide classroom training and MPE operations over-the-shoulder instruction.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Bill of Material (BOM)

Training Materials (as required) Product Support TTP Technical Standards and Specifications Technical Manuals and Drawings

6.3.5 Subtask 5 – Information Assurance (IA), Cybersecurity, Computer Network Defense (CND), and Certification and Accreditation (C&A) – The Contractor shall analyze Information Assurance Vulnerability Alerts (IAVA) and Information Assurance/Cybersecurity Vulnerability Bulletins for enclave impacts and provide recommended actions. The Contractor shall ensure enclave, network, and computer design services include the incorporation of DoD-directed IA vulnerability solutions. The Contractor shall ensure enclave systems, networks, and computer environments employ Information Systems Security Engineering and are consistent with MPE and CC/S/A cybersecurity architecture requirements, as prescribed in individual Task Orders. The Contractor shall ensure the design of hardware, operating systems, and software applications address cybersecurity requirements for new services, projects and releases. The Contractor shall apply all cybersecurity/IA vulnerability solutions. The Contractor shall develop and maintain C&A/Risk Management Framework (RMF) documentation. The Contractor shall install, test, monitor, maintain and operate the procedures and tools (e.g., cybersecurity software, hardware and network) required for C&A/RMF activities.

The Contractor shall deploy, test, operate and maintain cross-domain solutions and services.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Risk Management Framework (RMF) Documentation

6.3.6 Subtask 6 – Laboratory Services – The Contractor shall provide test plans, testing requirements, and scenarios to the laboratory. The test plan shall include operational testing, developmental testing, evaluation testing, and JITC certification tests. In coordination with JITC, the Contractor shall conduct testing to ensure interoperability and mission continuity when that system or device is inserted into the operational MPE. The Contractor shall audit the laboratory on a quarterly basis to validate that it has maintained configurations in accordance with the prescribed baseline.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond

Deliverables: Test Plan Test Results Laboratory Configuration Audit

6.3.7 Subtask 7 – Cryptologic and Key Management Services – The Contractor shall manage the life cycle of all controlled cryptographic items (CCI). The Contractor shall receive, inventory, store and ship all CCI devices and equipment. The Contractor shall perform acceptance testing of all incoming CCI.

6.3.8 Subtask 8 – Circuit Provisioning – The Contractor shall provision MPE circuits. The Contractor shall coordinate, monitor, and control circuit provisioning to facilitate quality implementations and minimize disruption to the production network. The Contractor shall perform pre-deployment coordination prior to each installation site visit in order to ensure the highest probability of successful completion of each circuit provisioning task. The Contractor shall develop and update weekly a Circuit Status List.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Circuit Status List

6.3.9 Subtask 9 – Desktop Installation and Maintenance – The Contractor shall install and maintain managed desktop infrastructure and traditional desktops, including Multi-Enclave Clients (MEC), Virtual Desktop Infrastructure (VDI), and thick clients. The Contractor shall also install and maintain phones, printers and all other client-side hardware. The Contractor shall adhere to all applicable international, national and local standards for these installations.

6.3.10 Subtask 10 – Exercise Services – The Contractor shall design and establish episodic enclaves, and nodes, as necessary, for North Atlantic Treaty Organization (NATO), coalition, joint, and an individual military service’s exercises. The Contractor shall provide all services related to these episodic enclaves and/or the MPE national and international exercises. The Contractor shall extend Tier 3 services for these exercises. The Contractor shall disestablish the episodic enclave at the completion of the exercise. The Contractor shall perform on-site engineering and IT management of Tactical Processing Centers and client-side hardware.

All deliverables in this Subtask are Task Order dependent. Individual Task Orders may require deliverables beyond those listed in this PWS.

Deliverable: Episodic Enclave Design

6.4 Task 4 – Supply Chain Risk Management (SCRM) Planning

This Contract and its associated Task Orders are subject to the Federal SCRM policies and regulations including the Defense Federal Acquisition Regulation Supplement (DFARS) 252.239-7017 Notice of Supply Chain Risk, DFARS 252.239-7018 Supply Chain Risk, DoD Instruction 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks, Section 806 of the FY2011 NDAA Requirements for Information Relating to Supply Chain Risk, and internal DISA SCRM Processes and Procedures.

The Contractor shall submit a SCRM plan as part of its Task Order 0001 proposal. Upon Task Order 0001 award, the SCRM plan will be incorporated into the ID/IQ Contract.

Deliverable: Supply Chain Risk Management (SCRM) Plan

7. Performance Standards. Performance Standards will be identified in the Task Order-level PWS and Quality Assurance Surveillance Plan (QASP).

8. Incentives. Both positive and negative incentives may be applied. In general, positive incentives, in the form of favorable Contractor Performance Assessment Reporting System (CPARS) assessments, may be used to recognize outstanding performance on Task Orders. Conversely, negative incentives in the form of negative Contractor Performance Assessment Reporting System (CPARS) assessments, may be utilized to document marginal or unacceptable quality of services or products, which is defined as performance below the AQLs identified in the

QASP.

Negative incentives tied to the Contractor’s inability to meet specified performance standards may be included at the Task Order level as deemed necessary by the Government.

9. Place of Performance. The primary place of performance shall be the Washington, DC metro area, principally Northern Virginia and Fort Meade, MD. Upon the COR’s approval, other potential CONUS/OCONUS work locations include Air Force facilities, Fairfax, VA; AFRICOM (Stuttgart, Germany), CENTCOM (Tampa, FL;

Kuwait; Bahrain; Afghanistan), SOUTHCOM (Miami, FL), NORTHCOM (Colorado Spring, CO), SOCOM (Tampa, FL), JCSE (Tampa, FL), US Forces-Korea (USFK) (Youngsan AB, Osan AB, Kunsan AB, and Camp Humphries). Additional places of performance are to be determined based on customer requirements and real world events. The specific place(s) of performance will be specified in individual Task Orders.

The Government may supply up to 24 onsite seats, desk phones, and DISA laptops at DISA Headquarters, MNIS Division Central Offices, Fort George G. Meade, MD 20755. The Contractor must provide offsite seating for the personnel assigned to this Contract or Task Orders exceeding these 24 seats. Future operational situations and requirements may require the Government to reduce Contractor onsite seats at which time the Contractor shall be responsible for providing additional offsite seating. The seating or office space for these offsite personnel shall be located within 25 miles of DISA Headquarters, Fort Meade, MD. In addition, the place(s) of performance may be subject to change based on future operational situations and requirements.

Frequent local travel within the National Capitol region is anticipated. Local travel within a fifty-mile radius of the individual’s daily duty station is not reimbursable under this effort.

The Contractor may establish a telework program that is similar to DISA Instruction 220-15-57 or customer instructions, and is approved by the COR. The COR does not approve individual Contractor employee telework agreements or activities; rather, the COR will approve the Contractor’s overall telework process to ensure it provides the support required under this PWS. The Contractor’s telework process shall incorporate all DoD and DISA or customer security policies, and include procedures for unplanned telework as a result of contingencies and emergencies. As directed by the COR, the Contractor shall continue performance in emergency or mission essential conditions.