HC1047-18-R-4008-RFP_Amendment_01.DOCX

HC104718R4008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM , BLOCK 9

The required response date/time has changed from 30-Mar-2018 04:00 PM to 05-Apr-2018 04:00 PM.

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 $385,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 Department of Defense (DoD), Defense Information Systems Agency (DISA) Multinational Information Sharing (MNIS) Division that allows for the use of Task Orders. Task Order Contract types permitted include FAR 16.2 Fixed-Price and FAR 16.3 Cost-Reimbursement. Task Orders may include FAR 17.2 Option periods.

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 CONUS and 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 Task Orders issued under this IDIQ Contract. At time of award, the Contractor’s FP ceiling labor rates will be incorporated into the Contract.

B.4. 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 Contiguous United States (CONUS) and Outside the Contiguous United States (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.5. OTHER DIRECT COSTS (ODCs) (ALL ORDER TYPES)

ODCs may consist of hardware, software, materials, and Task Order-related items that are incidental 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.6. 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.

Months

Labor - FFP

FFP

Fixed Price (FP). All Variations. This CLIN applies to all variations of Contract types under FP.

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

FOB: Destination

NET AMT

Lot

Travel

COST

Travel in support of 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) All Travel must be pre-approved by the 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). Ordering Period of five (5) years from Date of Award.

ESTIMATED COST

Lot

Other Direct Costs (ODCs)

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.

ESTIMATED COST

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 SCRM plan. The minimum guarantee is $500.00.

Lot

Surge Capacity

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 Contract/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.

ESTIMATED COST

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 15 November 2017

1. Contracting Officer’s Representative (COR). For Primary and Alternate COR detail, see DARS 52.204-9000 “Points of Contact” which will be included in the awarded contract.

a. Primary COR.

b. Alternate COR.

2. Contract Title.

Mission Partner Environment (MPE) Network Engineering Services for the Combatant Commands (CCMDs)

3. Background.

This requirement provides a complete array of technically advanced, network engineering and related services to the CCMDs and other Department of Defense (DoD) entities to support MPE requirements. These services were initiated in 2012 with the award of contract number HC1047-13-D-4000, Defense Information Systems Agency (DISA) Network Engineering Support for the Multinational Information Sharing Capabilities for the U.S. Combatant Commands (COCOMs). In compliance with Defense Procurement and Acquisition Policy (DPAP) memorandum, Subject: Contracting Support of Deployed DoD Personnel and Units, November 30, 2015, these services are contractually arranged and administered by the DISA, Procurement Services Directorate (PSD), and Infrastructure Directorate, Multinational Information Sharing (MNIS) Division, on behalf of the CCMDs and other DoD MPE-engaged entities.

The MPE is a set of capabilities that enable DoD to execute its assigned missions with external partners through timely and secure sharing of mission information. MPE is the top operational requirement from the Combatant Commanders. DoD engages daily with a wide range of external mission partners and our mission success is often highly dependent on our ability to effectively share information and conduct operations with these partners.

MPE will help DoD extend its enterprise to improve information sharing with mission partners without added equipment, expensive investments, or additional expenses. It will also strengthen the Department’s ability to accommodate unanticipated partners and events in real time, and securely use commercial solutions where appropriate and feasible.

The MPE programs extend US MNIS capabilities to (MPs) and beyond; thereby, allowing the 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. Some of the Programs currently supporting MPE are:

Combined Enterprise Regional Information Exchange System (CENTRIXS): Allows US and coalition Nations and their forces to securely share operational and intelligence information in mission enclaves; Bi-lateral and Multi-lateral enclaves connecting organizations 24/7/365; and provides Chat, Email and other Commercial-off-the-Shelf (COTS) services.

Combined Federated Battle Laboratories Network (CFBLNet): Evaluates shortfalls in Multinational Infor-mation Sharing capabilities by providing continuously available network infrastructure to test technologies with mission partners and ease transition into an operational coalition network environment

Common Mission Network Transport (CMNT): Provides a transport for coalition information sharing (Replaces the use of SIPR) and is available at any Defense Security Service location.

Mission Partner Environment (MPE) Virtual Data Center (VDC): A multi-enclave virtualization system that de-livers the same functions as a physical data center and can host multiple discreet mission enclaves, and provides services such as Chat, Directory Services, Email, Video teleconference of Internet Protocol (IP), Voice of IP, File sharing, Web portal and Office automation.

Pegasus (formerly known as Griffin): Provides the means for disseminating classified information between Five Eye Nations (FVEY- US, UK, CAN, AUS, NZ); FVEY services include Web browsing, Emails, SharePoint, Unified Communications and, Chat.

Unclassified Information Sharing- All Partners Access Network (APAN): Provides the single enterprise solution for sharing non-classified info supporting DOD Exercises and Humanitarian Assistance and Disaster Recovery Mission; >125K+ users, 100+ nations and 4K+ Communities of Interest (COIs); Services include Blogs, Wikis, Conferencing, language translation, chat, and email.

As the MPE mission requirements expand, grow, mature or require new capabilities current programs may evolve, combine or be replaced by new capabilities.

4. Objectives:

4.1 Provide network engineering and related services to support the MPE program and in support of DoD partners.

4.2 Rapidly deploy quality Information Technology Service Management (ITSM)-disciplined MPE network engineering and related services to worldwide CCMDs and other DoD locations.

4.3 Fully comply with, and implement, MPE principles, objectives, architecture, standards and specifications.

4.4 Continuously improve the delivery of MPE network engineering and related services to CCMDs and other DoD MPE-engaged entities.

4.5 Rapidly master and apply the latest technological advancements, including virtual and software-defined services.

4.6 Supply the hardware integral to these network engineering and related services.

4.7 Provide CCMDs and other DoD organizations a mechanism for ordering MPE-compatible services at equitable and reasonable prices.

5. Scope.

This requirement shall provide the CCMDs and other DoD MPE-engaged organizations with the complete array of network engineering and related services, integral hardware to support all MPE, MNIS and related networks, information systems, capabilities, and projects. The integral hardware requirement includes installation, purchases and maintenance in support of the network engineering and related services. These network services will be MPE-enterprise compatible and in accordance with DoD Instruction (DoDI) 8110.0, “SUBJECT: Mission Partner Environment, (MPE) Information Sharing Capability Implementation for the DoD,” November 25, 2014 and shall ensure the continuity, integration, security, integrity and standardization of MPE networks, nodes and mission enclaves. The services shall execute DoD CIO guidance for the interoperability and security of MPE information sharing capabilities and shall implement prescribed MPE interface specifications and standards for the exchange of DoD information with Mission Partners (MP).

The scope of IT services includes systems administration; security services; MPE enterprise management services; Supply Chain Risk Management (SCRM); and, Research, Development, Test, & Evaluation (RDT&E).

Section 5 – Scope and Section 6 – Performance Requirements of the PWS convey the span of requirements the Contractor shall provide under this contract. However, specific details of task assignments, deliverables, delivery locations, documentation, training, applicable Government/DoD/Customer/Industry standards will be provided within individual Task Orders.

Six task areas constitute the technical scope of this contract:

Task Area 1: Contract and Task Order Management Task Area 2: Systems Administration Task Area 3: Security Services Task Area 4: MPE Enterprise Management Services Task Area 5: Supply Chain Risk Management (SCRM) Task Area 6: Research, Development, Test, & Evaluation (RDT&E)

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 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, excluding any six-month extension of services pursuant to FAR 52.217-8.

6. Performance Requirements.

6.1 Task 1 – Contract and Task Order Management – Firm-Fixed-Price (FFP); Operations and Maintenance (O&M)

6.1.1 Subtask 1 –Contract Management- FFP; O&M.

The Contractor shall provide a Contract Management Plan (CMP) and control process to ensure management visibility and effective coordination from contract startup through the cost-effective delivery of high quality services, contract transition and close-out, and shall adhere to all DoD, DISA, CCMD, and other customer directives. The CMP shall include all elements and processes to be used for successful execution of this contract to include Transition-In, Startup, Schedule Management, Subcontractor Management, Quality Control, Financial Control, Issue Escalation, Risk Management, Transition-Out, and Closeout. A draft CMP shall be submitted with the Contractor’s proposal and a final version 30 calendar days after contract award.

Deliverable: CMP

6.1.2 Subtask 2 – Monthly Progress Report (MPR) - FFP; O&M.

The Contractor shall submit an MPR that addresses adherence to the Best Management Practices (BMP), in a format mutually agreed upon with the Government. The MPR shall describe tasks, progress, quality, risks, customer feedback, any potential problems, accomplishments and issues from the reporting period of the MPR. At a minimum, this data 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 cyber security 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 Contract, Task Orders and all subtasks they will or did support.

· Cost-reimbursement estimates and the status of invoicing. Evaluation of contract line item numbers’ (CLIN) ceilings, obligations and projected demand.

· Self-assessment of performance with respect to the PWS Acceptable Quality Levels (AQL).

Deliverable: Monthly Progress Report (MPR)

6.1.3 Subtask 3 – Monthly Contract Program Reviews - FFP; O&M.

The Contractor shall develop a rolling 90-day action plan which shall be updated monthly. The plan, in conjunction with the MPR, will serve as a baseline for the monthly Contractor Performance Report (CPR) meeting with MNIS Division staff, 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 Contract and all Task Orders. The CPR shall address staffing, progress, risks, milestones, Task Order owner feedback, invoicing, ODCs, 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 Contract 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 Contracting Officer’s Representative (COR) no 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) 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.

6.1.4 Subtask 4 – Monthly Task Order Review – FFP; O&M.

The Contractor shall develop a rolling 90-day action plan which shall be updated monthly for the Task Order. The plan will serve as a baseline for monthly Contractor Performance Report (CPR) meetings with Task Order holders (e.g., CCMD personnel), 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 Task Order. The CPR shall address staffing, progress, risks, milestones, invoicing, ODCs, and status of Government Furnished Equipment (GFE), including Contractor-purchased, Government-owned items, if any. 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, as well as identify best practices and lessons learned.

The Contractor shall ensure the CPR and an updated 90-day action plan are provided to Government participants via the Contracting Officer’s Representative (COR) no 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) 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.

6.1.5 Subtask 5 – Transition-out Plan and Contract Closeout - FFP; O&M.

The Contractor shall deliver a Transition-out Plan 120 calendar days prior to the end of this Contract. This plan shall provide detailed procedures to enable the incoming contractor to assume MPE network support without interruption or degradation of service. The Contractor shall transfer all operational materials 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 successor contract continuity. As part of best practices, the Contractor shall capture lessons-learned throughout the life of this contract and analyze, consolidate, and provide that information to the Government for use in this Contract as well as for application to relevant new or ongoing contracts or Task Orders.

Deliverable: Transition-out Plan

6.1.6 Subtask 6 – Integrated Master Schedule (IMS) – FFP; O&M.

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 Work Breakdown Structure (WBS) that aligns to the Task Order PWS.

Deliverable: Integrated Master Schedule (IMS)

6.2 Task 2 – Systems Administration – FFP; O&M

The Contractor shall perform systems hardware and software engineering, requirements analysis, site evaluations, configuration management, test and evaluation, operations and maintenance and technical services at facilities in the Continental United States (CONUS) and Outside CONUS (OCONUS) locations. The Contractor shall provide on-site systems engineering and technical support necessary to achieve and maintain the full operational capability of MPE/MNIS networks and capabilities.

The Contractor shall perform systems engineering in accordance with Institute of Electrical and Electronics Engineers (IEEE) standards and industry best practices. The Contractor shall perform requirements analyses in accordance with MNIS Division guidance.

6.2.1 Subtask 1 – Systems Engineering and Development Support –FFP; O&M.

The Contractor shall perform engineering and software-related tasks at customer sites, which include designated software systems and operational locations. The Contractor shall review system engineering analyses and monitor system operations to recommend procurement and maintenance requirements for life cycle support and equipment recapitalization.

Deliverable: Life Cycle Support and Recapitalization Report

6.2.2 Subtask 2 – Installation and Operations Testing – FFP; O&M.

The Contractor shall perform installation and operations testing, which shall include facilitating the requirements management process described in Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6285.01C, Multinational and Other Mission Partner (MNMP) Information Sharing Requirements Management Process and any updates.

6.2.3 Subtask 3 – New System Capabilities Implementation and Support - FFP; O&M.

The Contractor shall implement new system capabilities or functionalities in support of special technology projects. These efforts shall be documented in the form of a technical report and documented within the required MPR. The Contractor shall perform demonstrations of MPE Capabilities. This will include demonstrations connected to military exercises. The Contractor shall document results in a technical report. The Contractor shall analyze the technical impacts of software/hardware maintenance enhancements or modifications to the system product baseline and provide technical support to mitigate any potential impacts. Any actual impacts or baseline changes shall be documented in the MPR.

Deliverable: New Capabilities Demonstration Technical Report

6.2.4 Subtask 4 – Technical System Software and Training Support - FFP; O&M.

The Contractor shall provide on-site personnel direct training and/or computer-based training.

6.2.5 Subtask 5 – Technical Documentation – FFP; O&M.

The Contractor shall maintain a technical library for all system and unit/component documentation procured under this contract. Materials shall include: technical manuals, computer network exploitation reports made available to the Contractor, drawings, engineering sketches, test procedures, and any other pertinent documentation relevant to the system and or equipment.

The Contractor shall review and validate manufacturers’ hardware documentation to ensure that the appropriate documentation for the configured hardware system is available and current. This documentation shall be maintained in a library and shall be in conformance with the appropriate hardware documentation standards identified on individual Task Orders. The documentation shall include hardware system specifications and any drawings produced for the hardware system.

The Contractor shall support engineering and other technical reviews and meetings. The Contractor shall prepare technical briefing and presentation materials to support meetings and conferences.

6.2.6 Subtask 6 – Test and Evaluation –FFP; O&M.

The Contractor shall verify and validate the performance of various operational testing activities. The Contractor shall support the MNIS Division in analyzing, designing, developing, testing, coding, integrating, documenting, installing, operating, evaluating, maintaining, and supporting improvements to MPE capabilities. The Contractor shall support the documenting of technical procedures and tracking of hardware and software. The Contractor shall perform activities to assist in maintaining accurate system status and use statistics during test. This may include the actual monitoring of system network management tools. The Contractor shall prepare Engineering Change Proposals (ECPs) to reflect proposed baseline changes identified during development, operational testing, sustainment and operations support to customers.

6.2.7 Subtask 7 – Systems and Software/Hardware Interface Requirements – FFP; O&M.

The Contractor shall provide systems engineering and technical analysis services in support of defining the operational requirements for systems and software/hardware interfaces for applicable systems. As required, the Contractor shall design and connect network systems utilizing National Security Agency (NSA)-approved cryptographic equipment to provide secure communications paths for the transmission of classified information.

6.2.8 Subtask 8 – Network Management - FFP; O&M.

The Contractor shall monitor the quality of network communications and information processing. The Contractor shall perform network configuration management to identify, control, collect data for, and provide data to, networks for the purposes of status accounting and auditing. The Contractor shall perform network fault management to detect, isolate, and correct problems in, or abnormal operation of, the network or network components. This includes performing tasks on the network or researching and analyzing information about the network provided to MNIS Division.

The Contractor shall support the propagation of MPE/MNIS systems and technology to other national and international environments and locations. This will include network engineering tasks, systems drawings, site surveys, equipment procurements, communications design, and network installation, as well as ad hoc briefing and meeting participation. This shall also include supporting system capability demonstrations, evaluations, and exercise support.

The Contractor shall perform support functions for the centralized management of Global Crytographic Keying Material (KEYMAT) MPE/MNIS networks at applicable locations. Support includes ability to write, review and analyze communications security (COMSEC) message traffic and documents to ensure they are in accordance with current joint COMSEC management procedures.

6.3 Task 3 – Security Services – FFP; O&M.

6.3.1 Subtask 1 – Network Security – FFP; O&M.

The Contractor shall perform network security management, to include restricting access to network facilities/resources, as well as protecting the confidentiality, authenticity, and integrity of network management data (e.g., routing tables, access lists, and audit data protection). The Contractor shall provide the services required to support network hardware and software maintenance to include patches, preventive maintenance, modifications, and in network emergency repair. If the Contractor is not allowed by the MPE customer to perform these duties on the network, the Contractor shall support the customer in the performance of these duties.

The Contractor shall support system security certification and accreditation work, including the development of relevant documentation and test procedures, conduct of risk analysis, information assurance accreditation documentation, and the conduct of security engineering activities as required to meet security and operational requirements.

As prescribed in the DFARS paragraph 239.7103(b) and 252.239-7001 (Information Assurance Contractor Training and Certification (JAN 2008)), the Contractor shall:

(a) Ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including:

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

(b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

6.3.2 Subtask 2 – Integration – FFP; O&M.

The Contractor shall provide integration services to connect users to the networks and provide technical assistance to ensure operational status of users after the connection process. This includes: user systems integration, network component installations and de-installations, and the management information services required to support those tasks.

The Contractor shall provide webmaster and web management services as required for each network. This support may be required to be executed on either NIPRNet or SIPRNet websites. At the time of contract award, the Contractor must be able to, and be eligible to request, with Government process assistance, SIPRNet connectivity at the Government site.

6.4 Task 4 – MPE Enterprise Management Services – FFP; O&M

The Contractor shall facilitate the MNIS Division governance of the MPE enterprise to include the management of electronic information-sharing capability in accordance with applicable statutory, regulatory, and DoD policies and procedures.

6.4.1 Subtask 1 – Operations – FFP; O&M.

The Contractor shall provide on-site software/hardware maintenance, operations support and systems familiarization for applicable system(s). This support shall provide for day-to-day assistance with MPE capability operations and operations support. All activities performed related to this task shall be documented in a format specified by the CCMD, Service or Agency to capture trending, analytics, and reporting data. This report shall be included in the MPR monthly deliverable.

The Contractor shall assist the Government in enforcing guidelines for network, interface, and standard operating procedure (SOP) standardization at the customer location. This task shall include feedback on recommended improvements or deviations from the standards to meet customer requirements.

The Contractor shall develop, based on Government requirements, and coordinate technical procedures for the DoD components to follow in managing and using electronic MPE information-sharing capability. This shall include the writing, review, and publishing of MPE/MNIS Technical Bulletins after Government review and approval. The Contractor shall provide technical briefings to ensure customer awareness of published information and strategies.

6.4.2 Subtask 2 – Testing – FFP; O&M.

The Contractor shall execute pre-planned test scenarios designed to validate the performance of MPE enterprise services at the customer location as required. These tests may be conducted on a monthly basis. Test results shall be uploaded to a designated repository.

Deliverable: Test Results

6.4.3 Subtask 3 – Connection Approval Process – FFP; O&M.

The Contractor shall liaise with the customer on requests for network connection-approvals and user registrations. This includes working with the CCMD, Service or Agency to facilitate questions and answers with customers. The Contractor shall submit a monthly “Report on Connection Approval and User Registration Actions,” to document the Contractor’s specific actions in support of the customer on network connection approvals and user registrations.

Deliverable: Report on Connection Approval and User Registration Actions

6.4.4 Subtask 4 – Certification and Accreditation (C&A) – FFP; O&M.

The Contractor shall liaise with the customer on the C&As of their environment supporting electronic MPE information-sharing capability, their interfaces to each other, and their interfaces to U.S. networks, in accordance with published guidance. The Contractor shall submit a monthly “Report on Certification and Accreditation Actions,” to document specific actions in support of the customer on C&A.

Deliverable: Report on Certification and Accreditation Actions

6.5 Task 5 – Supply Chain Risk Management (SCRM) –FFP; O&M

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 technical proposal, finalized after award and maintained and updated as required, that describes how the Contractor will reduce and mitigate Supply Chain Risk using the security controls outlined below (further described in CNSSI 1253, Appendix D and NIST SP 800-53), as applicable to your contract.

Control Number

*Not required if there will be no procurement of hardware, firmware, or software systems.

6.6 – Task 6 - Research, Development, Test, & Evaluation (RDT&E); FFP; RDT&E

6.6.1 Subtask 1 - Systems Engineering and Development Support – FFP; RDT&E.

The Contractor shall identify and perform engineering and software-related tasks at customer sites, which include designated software systems, research and development centers and operational locations. The Contractor shall review system engineering analyses and monitor system operations to determine procurement and maintenance requirements for life cycle support and equipment recapitalization. The Contractor shall require access up to Top Secret /Sensitive Compartmented Information (TS/SCI), JWICS network, for installation, network engineering, enterprise management, and security services. The Contractor shall also routinely access SCI facilities for installations and troubleshooting.

6.6.2 Subtask 2 – System Functionality Improvements – FFP; RDT&E.

The Contractor shall independently analyze systems and equipment to recommend alternative technical approaches to MPE/MNIS networks and capabilities. The Contractor shall analyze hardware tradeoff requirements for upgrades and technical refreshes. The Contractor shall perform data analyses, computer program assessments, modeling, software engineering, and other engineering analyses to recommend program implementations required to diagnose and correct problems and improve performance of existing and developmental MPE/MNIS capabilities. The Contractor shall require access up to Top Secret /Sensitive Compartmented Information (TS/SCI), JWICS network, for installation, network engineering, enterprise management, and security services. The Contractor shall also routinely access SCI facilities for installations and troubleshooting.

Deliverable: Test Results

6.6.3 Subtask 3 – Test and Evaluation – FFP; RDT&E.

The Contractor shall verify and validate the performance of various testing activities. The Contractor shall support the MNIS Division in analyzing, designing, developing, testing, coding, integrating, documenting, installing, operating, evaluating, maintaining, and supporting improvements to MPE capabilities. The Contractor shall support the documenting of technical procedures and tracking of hardware and software. The Contractor shall perform activities to assist in maintaining accurate system status and use statistics during test. This may include the actual monitoring of system network management tools. The Contractor shall prepare ECPs to reflect proposed baseline changes identified during development, operational testing, sustainment and operations support to customers. The Contractor shall require access up to Top Secret /Sensitive Compartmented Information (TS/SCI), JWICS network, for installation, network engineering, enterprise management, and security services. The Contractor shall also routinely access SCI facilities for installations and troubleshooting.

6.6.4 Subtask 4 – Systems and Software/Hardware Interface Requirements – FFP; RDT&E.

The Contractor shall provide research and development, systems engineering and technical analysis services in support of defining the enhanced operational requirements for systems and software/hardware interfaces for applicable systems. As required, the Contractor shall design and connect network systems utilizing National Security Agency (NSA)-approved cryptographic equipment to provide secure communications paths for the transmission of classified information. The Contractor shall require access up to Top Secret /Sensitive Compartmented Information (TS/SCI), JWICS network, for installation, network engineering, enterprise management, and security services. The Contractor shall also routinely access SCI facilities for installations and troubleshooting.

Deliverable: New Capabilities Demonstration Technical Report

7. Performance Standards.

Performance Standards will be identified in the Task Order-level PWS and QASP.

8. Incentives. Both positive and negative incentives will 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 may be utilized to penalize marginal or unacceptable quality of services or products in performance of Task Orders, which is defined as performance below the AQLs in the Quality Assurance Surveillance Plan (QASP).

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

9. Place of Performance. The places of performance for support will be at CONUS and OCONUS designated CCMD support sites including: STRATCOM (Tampa, FL, Suffolk, VA), EUCOM (Stuttgart, Germany), PACOM (Oahu, Hawaii), PACOM PACAF (Hickam AFB), 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), and Joint Staff J6 (The Pentagon). Additional CCMD and other DoD MPE customer facilities/locations not identified in this PWS may require support. Specific places of performance will be specified at the Task Order level. All travel shall be approved in writing by the COR prior to travel and all travel shall support the task areas described above. All travel requirements shall be in accordance with both Federal Acquisition Regulation (FAR) Part 31.205-46, “Travel Costs,” and Joint Travel Regulation (JTR) requirements and limitations. Reimbursement for FAR 31.205-46 ”Travel Costs” will be made in accordance with the Federal Travel Regulations. Reimbursement for FAR 31.205-35 “Relocation Costs” may be made. Frequent local travel between the Contractor’s facilities, DISA HQs, and 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.

Alternate Place of Performance - Contractor staff may telework based on a Contractor proposed schedule 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 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. Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Additionally, the Contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR.

Letter of Authorization. Some travel to duty locations shall require a Letter of Authorization (LOA). As noted in DFARS PGI 225.7402-3(e), a LOA is necessary to enable a contractor employee to process through a deployment processing center; to travel to, from, and within a theater of operations; and to identify any additional authorizations and privileges. As required by modification, the contractor shall initiate a LOA for each prospective traveler. The contractor shall use the Synchronized Predeployment & Operational Tracker (SPOT) web-based system, at http://www.dod.mil/bta/products/spot.html, to enter and maintain data with respect to traveling/deployed personnel, and to generate LOAs. When necessary and if in the Government’s interest, the contractor may also initiate a LOA request to provide an official traveler access to Government facilities and to take advantage of travel discount rates in accordance with Government contracts and/or agreements. All privileges, services, and travel rate discount access are subject to availability and vendor acceptance. LOAs shall be signed/approved by the Contracting/Ordering Officer for the contract/order who is registered in the SPOT system.

OCONUS Immunization Requirements. Contractor employees who deploy to locations that require immunizations shall do so in accordance with Department of Defense Instruction (DoDI) 6205.4.

As mandated by the Federal Republic of Germany, all Contractor personnel working in Germany under this contract shall obtain a Technical Expert Status Accreditation (TESA). TESA Memorandum of Instructions will be provided upon contract award.

Invited Contractor (IC) and Technical Representative (TR) status shall be governed by the U.S. – ROK (Republic of Korea) Status of Forces Agreement (SOFA) as implemented by United States Forces Korea (USFK) Reg. 700-19, which can be found under “publications” tab on US Forces Korea homepage http://www.usfk.mil

(a) Definitions. As used in this clause— “U.S. – ROK Status of Forces Agreement” (SOFA) means the Mutual Defense Treaty between the Republic of Korea and the U.S. of America, Regarding Facilities and Areas and the Status of U.S. Armed Forces in the Republic of Korea, as amended “Combatant Commander” means the commander of a unified or specified combatant command established in accordance with 10 U.S.C. 161. In Korea, the Combatant Commander is the Commander, United States Pacific Command. “United States Forces Korea” (USFK) means the subordinate unified command through which US forces would be sent to the Combined Forces Command fighting components.

“Commander, United States Forces Korea” (COMUSK) means the commander of all U.S. forces present in Korea. In the Republic of Korea, COMUSK also serves as Commander, Combined Forces Command (CDR CFC) and Commander, United Nations Command (CDR UNC). “USFK, Assistant Chief of Staff, Acquisition Management” (USFK/FKAQ) means the principal staff office to USFK for all acquisition matters and administrator of the U.S.-ROK SOFA as applied to US and Third Country contractors under the Invited Contractor (IC) and Technical Representative (TR) Program (USFK Reg 700-19). “Responsible Officer (RO)” means a senior DOD employee (such as a military E5 and above or civilian GS-7 and above), appointed by the USFK Sponsoring Agency (SA), who is directly responsible for determining and administering appropriate logistics support for IC/TRs during contract performance in the ROK.

(b) IC or TR status under the SOFA is subject to the written approval of USFK, Assistant Chief of Staff, Acquisition Management (FKAQ), Unit #15289, APO AP 96205-5289.

(c) The Contracting Officer will coordinate with HQ USFK/FKAQ, IAW FAR 25.8, and USFK Reg 700-19.