Attach 9 TO 0001 SOO 12032020.docx
DOCX document 54 KB Posted
- Attached to
- Defense Enclave Services (DES) RFP
- Solicitation number
- HC104720R0014
- Issued by
-
Defense Information Systems Agency
About this file
This document outlines requirements for the Defense Enclave Services (DES) program. The Defense Information Systems Agency seeks to award an indefinite-delivery, indefinite-quantity contract with a ceiling of $11.2 billion over 10 years to provide integrated, standardized information technology services for 22 Defense Agencies and Field Activities. Key services include network operations, engineering support, asset management, desktop configuration, and cybersecurity support across Non-classified Internet Protocol Router Network and Secure Internet Protocol Router Network domains. The agency aims to consolidate disparate local area network support contracts to optimize capabilities and reduce costs. The minimum small business participation requirement is 25% of the ceiling value. The base period is four years with three two-year option periods. The solicitation number is HC1047-20-R-0014 with questions due via email. The award is expected in the first quarter of fiscal year 2022.
View the file
Other files
Show 40 more
Latest 50 of 73 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Defense Information Systems Agency (DISA)
Defense Enclave Services (DES)
Statement of Objectives (SOO) Task Order #001
03 December 2020
1. Overview
DISA desires to partner with industry to provide commercial Information Technology (IT) services, decrease redundant IT costs, enhance cybersecurity posture, and standardize IT services across disparate networks. Defense Enclave Services will unify the 4th Estate’s Common Use IT systems, personnel, functions, and program elements associated with the support of those systems and technologies under a Single Service Provider (SSP) architecture managed, operated, and supported by DISA.
2. Purpose
The specific purpose of Task Order #001 is to receive standardized, responsive and innovative IT services focused on mission value and user network experience, while improving security, network availability, and reliability.
3. Scope
DES will provide all required transition, infrastructure, network operations and management, engineering and innovation, cybersecurity, and technical refresh support services for a SSP network environment with Defense Agency and Field Activities (DAFA) mission partners. The network will consist of Non-classified Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Router Network (SIPRNet) domains, and will use the DISA DoDNet as the technical baseline for standardization between agencies upon transition.
A total of five (5) 4th Estate agencies have been identified to be included in this Forth Estate Network Optimization (4ENO) effort. Three (3) agencies (Defense Technical Information Center (DTIC) and Defense Prisoner of War/Missing in Action Accounting Agency (DPAA) and DISA Headquarters (HQ) will require only sustainment services, as migration will be completed under a separate DoDNet Services contract awarded in FY2020.
4. Constraints and Risks
a. Cable Plant and Wireless Infrastructure Support services within DISA facilities in the National Capitol Region (NCR) will require Top Secret (TS)-Sensitive Compartmented Information (SCI) clearance since network equipment is located in Sensitive Compartmented Information Facilities (SCIF).
b. All planning, migration, and sustainment activities shall be priced separately. The activities are defined as follows:
· Planning activities: site survey, BOM development, network design, physical/Layer 1 analysis, service design package
· Planning exit criteria: site survey(s) completed, network and equipment requirements defined, service design package complete
· Migration activities: deploy and configuration equipment, migrate domain and identity management services, conduct successful pre-IOC pilot
· Migration exit criteria: network built and operational, ATO change request completed/approved, Initial Operating Capability achieved (ready to image user workstations)
· Sustainment activities: image workstations, sustain cybersecurity posture, operate network and services
c. Planning, Migration and Sustainment of the Defense Microelectronics Activity (DMEA) shall be priced as a separate Optional CLINs.
d. Planning, Migration and Sustainment of the Defense Media Activity (DMA) shall be priced as a separate Optional CLINs.
e. Current operations across the 4th Estate environment include a disparate mixture of government/contractor owned IT hardware (HW) (e.g., servers, desktops, laptops, routers, thin clients, printers) and IT software (SW) (e.g., desktop and application SW) as well as a combination of government and contracted operated services. Some Government locations may use thick clients, Virtual Desktop Infrastructure (VDI) environments, or kiosk/shared workstations in their respective facilities.
f. Sample DAFA enterprise architecture is included in Appendix C; the accuracy of this information may change between the Request for Proposal and actual start of DAFA migrations.
g. The 4th Estate Common Use IT services are required to be 24x7 with core hours M-F, 8 am to 5 pm local time. Some Common Use IT services may require a Continuity of Operations Plan, which includes surge support requirements for Disaster Recovery and reconstitution activities.
h. Network operations and service availability are paramount to migration; DISA and its mission partners shall not experience delays or degradation of services in the SSP environment.
i. Network architecture shall not contain proprietary elements or closed architecture; the overall architecture must be open to allow for the rapid integration of new and cost-efficient technologies.
j. The procurement of end devices, peripherals, network equipment, and software is not in scope of this DES task order. The DES provider will plan for the lifecycle and technical refresh of all infrastructure and endpoint nodes, which the Government will procure through competitive means. The provisioning and maintenance of the Government-procured devices are within the scope of the DES contract .
k. Service Desk Support is not in scope of this task order.
l. Physical site attributes (such as Layer 1 cabling, etc.) may impact whether NIPR and SIPR networks have concurrent or separate migration schedules.
m. At the direction of DISA, additional 4th Estate agencies may be identified and included in this effort.
5. Schedule
Within ten (10) business days of task order award, the Contractor shall deliver to the Government a schedule in a format that is typically used in commercial network migrations such as this at high velocity. This schedule shall be reviewed at the Kick Off meeting, “baselined” and incrementally evolved per the Contractor’s recommended process.
At a minimum, the schedule shall identify major project capability milestones, dependencies, communication and related activities associated with the project. In addition, the Contractor shall provide management plans and reports, technical issues, resolutions, and mitigation strategies for the base period at the Kick Off meeting.
6. Transition
A. The Contractor shall begin the phase-in efforts immediately after contract award. The Contractor shall submit a Transition Plan as part of their proposal. In this plan, the Contractor shall specify how it will phase in seamless personnel staffing and support so that no delays or degradation of services is experienced by DISA and its mission partners. In the plan, the Contractor shall include adequate time to hire appropriate personnel, conduct inventories, assume network control, issue subcontracts, etc. after Task Order award. The contractor shall commence implementation of the proposed Transition Plan immediately upon contract award. During the phase-in period, the contractor shall be responsible for finalizing all employee clearance requirements. The contractor shall complete the necessary steps for assumption of the operation during the phase-in period and shall meet all requirements as specified in the SOO with the beginning of full performance. The phase-in period shall be no more than 90 calendar days.
B. To ensure a smooth phase-out to the next service provider at the conclusion of the task order, or in the event an Option Period is not exercised, and to prevent possible decreases in productivity or service quality, the Contractor shall provide a 90 calendar day phase-out period prior to the task order conclusion date. During this period, the Contractor shall make available to the incoming contractor representatives who are versed in the established operation of the functions to be performed to key incoming contractor personnel. This service shall be made available to explain procedures for conducting government business, show the next contractor various work sites, introduce the contractor to customer representatives, etc. During this period, the incumbent contractor shall provide required training pertaining to the current status and pending transactions and conduct material, equipment, and tools transfers. Inventories shall be conducted jointly with the Government representatives and representatives of the incoming contractor.
7. Objectives
DES is a Government-owned contractor-operated service model. The objectives of DES include providing singular Command and Control (C2) focus across DAFAs for Common Use IT operations, decreasing redundant costs and enhancing cybersecurity:
A. Consolidate, integrate and optimize disparate Local Area Network IT Support Services.
· Provide a single flexible contract vehicle that includes end-user technical support, engineering, asset management, and operational project support;
· Implement an integrated network operations center management of services across all aspects of the environment;
· Manage desktop engineering and image configuration management;
· Report service performance metrics in real time, identify root cause of service outages, scope areas of service improvement and reduce user downtime.
B. Reduce contract overhead through the consolidation of multiple support contracts.
· Implement a program that incorporates the full management of HW and SW provisioning and service operations leveraging industry best practices;
· Eliminate redundant SW and HW assets;
· Generate innovative service delivery techniques that will increase cost savings;
· Utilize industry best tools, processes, and procedures to enhance customer services, reliability and efficiencies to reduce the number of needed service technicians.
C. Generate and identify opportunities for new technology insertion to enhance the cybersecurity posture of DISA and its mission partners.
· Promote innovation and delivery of new technology, including executing pilots and proof of concepts on emerging technologies related to Common Use IT services;
· Ensure solutions proposed operate in a compatible, non-vendor lock-in, competitive environment.
8. Performance Metrics The Contractor shall deliver services in accordance with Table 2 - Network Operations below.
| Performance Standard (Network Operations) |
| Acceptable Quality Levels (AQLs) |
| System and Tool Availability for High Performing Sites |
| >=99.99% system uptime for supported systems, not to include Authorized Service Interruptions (ASI)/routine maintenance or higher level outages |
| System and Tool Availability for Standard Sites |
| >=99% system uptime for supported applications, not to include Authorized Service Interruptions (ASI)/routine maintenance or higher level outages |
| Change and Release without Incident |
| >=95% of changes and releases result in no adverse impact on production services, or require significant re-work with the application of additional resources/time |
| Alert detection and escalation |
| >=90% 24 x 7 x 365; Priority 1 alerts detected and reported (via trouble ticket) to the service desk within 30 minutes of initial occurrence |
| Decrease customer interactions |
| >=5% decrease in customer interactions, to begin after the first year and reported every 6 months thereafter |
| Cybersecurity Support |
| RMF documentation will be maintained and updated daily, to include cybersecurity architecture, requirements, objectives and policies, and maintaining DoDNet security posture with minimal re-work at least 95% of the time |
Table 2 - Network Operations
9. Deliverables The Contractor shall deliver data items in accordance with Table 4 below. All deliverables shall be provided to the Government for review and approval. Furthermore, the Contractor shall propose additional documentation they believe will help the program operate effectively.
| Deliverable |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
Non- Disclosure Agreement
| GOV Format |
| 5 business days after award and at the inclusion of a new FTE. |
| Emailed to Contracting Officer’s Representative (COR)/Contracting Officer (KO) |
| As required |
| Project Management Plan |
| Approved Contractor Format |
| 10 business days after award |
| Emailed to COR/KO |
| Kick Off Meeting |
| Integrated Master Schedule |
| MS Project |
| 10 business days after award |
| Emailed to COR/KO |
| Kick Off Meeting |
| Phase-In Transition Plan |
| Approved Contractor Format |
| 10 business days after award |
| Emailed to COR/KO |
| Kick Off Meeting |
DoD Contract Manpower Report (Former ECMRA Contract Record)
| GOV Format (online) |
| 15 business days after contract award |
| Email confirmation to COR/KO |
| Initial; Annual updates as required by DFARS |
| Employee Roster & Certification Status Report |
| Approved Contractor Format |
| 30 business days after award |
| Emailed to COR/KO |
| Monthly |
Monthly Status Report
| Approved Contractor Format |
| 7 business days after end of month |
| Emailed to COR/KO |
| Monthly |
| Quarterly Program Review (QPR) Presentation |
| Approved Contractor Format |
| 10 business days after end of quarter |
| Emailed to COR/KO |
| Quarterly, based on DoD fiscal year |
Quality Control Plan
| Approved Contractor Format |
| 30 calendar days after award |
| Emailed to COR/KO |
| Once 30 days after award and then every year within 30 calendar days of start of option period. |
| Life-cycle Management Plan |
| Approved Contractor Format |
| 45 calendar days after award. |
| Emailed to COR/KO |
| 45 days after award and then once a month with monthly updates |
Knowledge Management Plan
| Approved Contractor Format |
| 45 calendar days after t award. |
| Emailed to COR/KO |
| 45 days after award and then updated every quarter |
| Risk Management Framework Plan |
| Approved Contractor Format |
| 75 calendar days after award. |
| Emailed to COR/KO |
| 75 days after award and then once a month with monthly updates |
Migration Plan
| Approved Contractor Format |
| NLT 30 calendar days prior to start of task |
| Emailed to COR/KO |
| As required for each agency |
Sustainment Plan
| Approved Contractor Format |
| NLT 30 calendar days prior to start of task |
| Emailed to COR/KO |
| As required for each agency |
| Phase-Out Transition Plan |
| Approved Contractor Format |
| Meet with the Government within 120 calendar days of the end of the last option period; written plan due 90 calendar days prior to the end of last option period |
| Emailed to COR/KO |
| Once |
Site Survey Report
| Approved Contractor Format |
| NLT 15 business days after task completion |
| Emailed to COR/KO |
| As required for each agency |
| Architecture Diagrams (DoDAF Compliant) |
| Visio |
| NLT 30 calendar days prior to start of successor task |
| Emailed to COR/KO |
| As required for each agency |
| Audit and Accountability Plan |
| Approved Contractor Format |
| NLT 30 calendar days prior to start of successor task |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to Authority to Operate (ATO) expiration |
| Identification and Authentication Plan |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| HW/SW List |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| RMF Access Control Plan |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| Network Diagram/Topology |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| Security Assessment Report (SAR) |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| Security Plan (SP) |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| Documents/artifacts required for accreditation packages |
| Approved Contractor Format |
| 90 calendar days prior to submitted date for new system |
| Emailed to COR/KO, Cyber Lead |
| As required for each agency / Prior to ATO expiration |
| Accreditation Packages for NIPRNet and SIPRNet |
| eMass |
| NLT 180 calendar days prior to existing ATO expiration; or 90 calendar days prior to submitted date for new system |
| Emailed to COR/KO, Cyber Lead |
| Required for NIPRNet and SIPRNet |
| Cybersecurity Status Report |
| Approved Contractor Format |
| Weekly |
| Emailed to COR/KO/Cyber Lead |
| Weekly |
| STIGs |
| Approved Contractor Format |
| 90 calendar days prior to submitted date for new system |
| Emailed to COR/KO/Cyber Lead |
| Maintenance - Weekly |
| ACAS Scan |
| Approved Contractor Format |
| 90 calendar days prior to submitted date for new system |
| Emailed to COR/KO/Cyber Lead |
| Maintenance - Daily |
| BURP Scan (if applicable) |
| Approved Contractor Format |
| 90 calendar days prior to submitted date for new system |
| Emailed to COR/KO/Cyber Lead |
| System and Interface Design Specifications |
| Approved Contractor Format |
| NLT 30 calendar days prior to start of successor task |
| Emailed to COR/KO |
| As required for each agency |
DoDNet Status & Outage Update Report
| Approved Contractor Format |
| Within 30 minutes of event or notification of event |
| Emailed to COR/KO |
| As required; rolled up to Monthly Status Report and QPR |
| EVIF Validation Report |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO |
| 30 calendar days after Task Order award with weekly updates |
| Operational Performance Metrics & Analysis Report |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO |
| 30 calendar days after Task Order award with daily updates |
| Asset Report |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO |
| 30 calendar days after Task Order award with weekly updates |
Incident, Problem, and Change Trend Analysis Report
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO |
| 30 calendar days after Task Order award with weekly updates rolled up to Monthly Status Report and QPR |
| PKE/PKI Status Report |
| Approved Contractor Format |
| 30 calendar days after Task Order award |
| Emailed to COR/KO |
| 30 calendar days after Task Order award with weekly updates rolled up to Monthly Status Report and QPR |
| Final Asset Report |
| Approved Contractor Format |
| Report due NLT 90 calendar days prior to the end of task order performance |
| Emailed to COR/KO |
| Once |
| Change & Request Fulfillment Management TTP |
| Government determined format. |
| 60 calendar days of Contract award |
| Emailed to COR/KO |
| Once 60 days after award, then quarterly updates. |
| IdM TTP |
| Government determined format. |
| 60 calendar days of Task Order award |
| Standard Distribution |
Once 60 days after award, then quarterly updates.
| Daily Operational Performance Brief |
| Government determined format. |
| 60 calendar days of Task Order award |
| Standard Distribution |
The first one will be 60 days after award, then daily after that.
| Incident Management TTP |
| Government determined format. |
| 60 calendar days of Task Order award |
| Emailed to COR/KO |
| Once 60 days after award, then quarterly updates. |
| Problem Management TTP |
| Government determined format. |
| 60 calendar days of Task Order award |
| Emailed to COR/KO |
| Once 60 days after award, then quarterly updates. |
| Lifecycle Management Project Plan |
| Government determined format. |
| 60 calendar days of Task Order award |
| Emailed to COR/KO |
| Once 60 days after award, then monthly |
| Configuration Management Data Base (CMDB) SOP |
| Contractor determined format with COR approval. |
| 60 calendar days of Task Order award |
| 1 copy/ |
Standard Distribution* Once 60 days after award, then quarterly updatehs.
| Patch Deployment for all Devices TTP |
| Contractor determined format with COR approval. |
| 60 calendar days of Task Order award |
| 1 copy/ |
Standard Distribution* Once 60 days after award, then quarterly updates.
| Quarterly DEPS Site Update |
| DEPS SharePoint |
| 30 calendar days after Task Order award |
| Standard distribution and then uploaded to the DEPS site after COR approval. |
| 30 calendar days after task order award, then 1st business day of each quarter month (Jan, Apr, Jul, Oct). |
Table 4 - Deliverables
10. Reserved
11. Government Furnished Material and Equipment The Government shall provide access to requisite program and technical information that is necessary to carry out the requirements of this SOO. The Government shall provide access to facilities, equipment, software tools, and technical information necessary for the performance of this task order. Items may include office space, desk, telephone, printer, access to electronic mail, and computers, when deemed appropriate by the Government. In addition, the Government shall provide access to appropriate systems. Contractor personnel will not use government resources in violation of any federal, State, or Local statute, regulation or policy.
12. Travel Requirements The Contractor shall support government directed meetings as needed. All travel costs (lodging, per diem, airfare, rental car etc.) shall be reimbursed at cost via the travel contract line item. Contractors shall be responsible for making their own travel and lodging arrangements as necessary to support requirements. Contractors shall plan to support travel to CONUS and OCONUS locations, as necessary.
13. Place of Performance The contractor may utilize their own facilities when planning the work associated with this SOO.
Appendix B contains location information for 4th Estate mission partners. The Contractor shall identify the Contractor’s place(s) of performance in their PWS. At the direction of the DISA, additional 4th Estate agencies and locations may be identified and included in this effort.
14. Period of Performance
The task order will consist of a 1-year base period and four, 12-month option periods.
15. Data Rights The Government will have unlimited rights to use/modify/share all information, technical data, computer software, and computer software documentation utilized under this task order. The Contractor shall deliver to the Government all databases, scripts, source code, configuration documentation, and any information relevant and pertinent to host, manage and support new, modified and/or existing systems or applications under this task order.
16. Security DES will provide standardized delivery and management of NIPRNet and SIPRNet services; reference the pre-solicitation DD Form 254, Contract Security Classification Specification. The nature of this acquisition requires access to, handling, receiving and storing classified (Secret and Confidential) and Controlled Unclassified Information (CUI), Personally Identifiable Information, Personal Health Information, unclassified information, documents, hardware and software using the applicable standards of DoD 5220.22-M National Industrial Security Program (NISPOM).
The nature of this task order requires access to Secret and unclassified data, information, and spaces. The Contractor shall be required to attend meetings at classified and unclassified levels.
The work to be performed under this task order is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility for personnel assigned to cable plant and wireless infrastructure support at DISA. Cable plant support requires access into all SCI Telecommunication Rooms (TRs) at DISA HQ Fort Meade, the JWICS Computer Equipment Room (C3J58), and SCI areas in Command Building for cable survey, installation, repair, and maintenance. After-hours/weekends access to the TRs are also required in order to troubleshoot network connectivity issues (from the wall jack to the patch panels) during network outages.
The work performed by the Contractor will require access to Secret and Controlled Unclassified Information facilities and workspaces, as well as Sensitive Compartmented Information Facilities (SCIF). The Contractor must have an interim Top Secret Facility Clearance from the Defense Counterintelligence and Security Agency. Appendix E provides a PWS template with current security language.
17. Cybersecurity Maturity Model Certification (CMMC) The Government reserves the right to require CMMC Level 3 certification once the standards are available. The certification timeline will be established by the Government at the task order level.
STATEMENT OF OBJECTIVES APPENDICES
Appendix A: Solicitation HC1047-20-R-0014 Services Summary Appendix B: Places of Performance Appendix C: Agency Size Designations and Sample IT Architecture Appendix D: DES Task 1 Quality Assurance Surveillance Plan Appendix E: DISA PWS Template Appendix F: DAFA Data Calls Appendix G: Glossary image1.emf
File details come from the government source that posted it. Updated .