PWS - ModEL BPA - 10292024.pdf

DRAFT

Controlled By: DISA

Controlled By: PSD/PL21

CUI Category: PROCURE

Distribution/Dissemination Control: FEDCON

POC: disa.meade.pld.mbx.pl21-policy-branch@mail.mil

Performance Work Statement (PWS)

Award/Mod Effective Version Date

Award

Contract Number: TBD

Task Order Number: TBD

Contractor Name: TBD

Tracking Number: TBD

Follow-on to Previous Contract and

Task Order Number:

TBD

1. Contracting Officer’s Representatives (CORs).

a. Primary COR. See Points of Contact in Contract Administration Data

Name:

Organization: Defense Information Systems Agency (DISA) J6 Command, Control, Communications, and Computers (J6 C4E) JP81

DODAAC: HC1086

Address: 7010 Defense Pentagon, 3B288, Washington, DC 20301

Phone Number:

E-Mail Address:

b. Alternate COR. See Points of Contact in Contract Administration Data

Name:

Organization:

DODAAC:

Address:

Phone Number:

E-Mail Address:

c. Property Administrator

Name:

Organization:

DODAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Task Order Title. Modernization, Engineering, Lifecycle Refresh (ModEL) Blanket Purchase Agreement (BPA)

3. Background. The Defense Information Systems Agency (DISA) J6 Command, Control, Communications, and

Computers (J6 C4E) provides a full range of information technology products, services, solutions, and customer support to customers that include: Army, Office of the Secretary of Defense (OSD), Joint Chiefs of Staff, Pentagon

Force Protection Agency (PFPA), and Chief Digital and Artificial Intelligence Officer (CDAO).

CUI

J6 C4E seeks to deliver responsive IT services and support to its customers in the most effective manner possible.

As the centralized IT service provider of the Pentagon and other locations around the National Capital Region

(NCR), J6 C4E can bring to bear the full capability of OSD and supported military branches to realize their mission and vision in order to support J6 C4E’s commitment to be the creative catalyst for solutions that guarantee mission success. To achieve this state, J6 C4E applies the following five strategies to all of its business operations: (1)

Reduce Complexity; (2) Sustainment; (3) Rapid Provisioning; (4) Enable the Enterprise; and (5) Improve Security.

The execution of J6 C4E’s mission over the next five (5) years will require organizational flexibility and scale to effectively respond to change. These changes will include transforming the Government environment into a software-defined network (SDN), evolving its data center capabilities to a hybrid community cloud, adopting

DevSecOps and infrastructure as code methodologies to streamline and automate IT provisioning, and embracing zero trust principles to better secure the Government environment. It will be essential for the Contractor to be flexible, agile, and responsive to support J6 C4E in executing its strategic goals and objectives.

4. Objectives:

The objective of this blanket purchase agreement (BPA) is to enable the timely and effective acquisition of software, hardware, and technical labor necessary to resource, plan, and execute any and all strategic efforts and initiatives outlined as tasks in Section 6 of this document. Given the size, scope, and breadth of many of these tasks, J6 C4E is seeking a BPA that enables the acquisition of one or more of the outlined services from a vetted list of contractors with specialized experience in delivering services to the DoD and public sector.

Ultimately, the Government is seeking to shorten product/service delivery acquisition from time of formal call order on this BPA to forty-five (45) days or less. Once a call order has been awarded, the Contractor shall have no more than thirty (30) days to onboard and in-process its call order resources to begin formal project planning and execution. At the conclusion of a call order, the Contractor shall complete full operational transition and sign-off of new project/capability to the Government designated J6 C4E sustainment owner in order to achieve formal close-out and completion of a call order.

Over the duration of the BPA, annual performance reviews of the selected contractors will be conducted to validate the timeliness and performance of existing contractors in meeting the Government’s objectives. If existing contractors demonstrate a pattern of subpar or unsatisfactory performance over the period of this contract, the

Government reserves the right to remove deficient contractors from being awarded future call orders in favor of new contractors with similar but competitive experience and technical expertise.

5. Scope.

5.1. The Contractor shall provide all project planning, design, hardware/software, and execution support necessary to deliver the Government’s technical and mission requirements outlined in a given call order. Overall, the

Contractor shall be assigned work on a call order to perform in one or more of the four main IT service areas: (as further detailed in Section 6 of this document)

Task Area 1 – Program Management

Task Area 2 - Solutions Development

Task Area 3 - Customer Engineering Projects

Task Area 4 - Telecom and Networking Professional Services

5.2. Program Management task (Task 1) on this BPA pertains to work integrating and overseeing this BPA and subsequent Call Orders. This task may include managing cost, schedule, and scope of multiple concurrent projects occurring under the BPA by multiple Contractor Team Arrangement (CTA) members.

5.3. The Solutions Development task (Task 2) on this BPA pertains to work in support of modernizing the

Government’s enterprise IT infrastructure to support current and emerging mission requirements. This task may include conducting lifecycle refresh (LCR) efforts to reduce J6 C4E technical and cybersecurity debt, optimization, and rationalization of existing Government IT architecture, tools, and technical configurations, as well as the design and implementation of new concepts and systems in the environment to support key J6 C4E strategic imperatives such as cloud, zero trust, and IPv6.

5.4. The Customer Engineering Projects task (Task 3) on this BPA pertains to work in support of customer-based mission requirements. This task may include the design and deployment of commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS) applications in the Government environment, the establishment of network connectivity from a customer environment to the Government environment (e.g. Site-to-Site VPN, cloud connectivity), as well as the lifecycle refresh (LCR) upgrade of customer-owned IT equipment.

5.5. The Telecom and Networking Professional Services (Task 4) on this BPA pertains to work in support of onboarding a new customer agency or organization to the Government IT environment and transition to J6 C4E as its new IT service provider. This task may include the migration of accounts, applications and technical configurations from the customer’s legacy environment, the extension of physical network connectivity to a new office location, as well as the distribution and deployment of J6 C4E workstation equipment to new users.

5.6. The contractor shall be onsite as required. The Contractor shall provide on-site support at Government locations and/or contractor-owned spaces, as approved by the Government, to support ongoing activities in an efficient and cost-effective manner. Details about the place of performance will be provided for each call order, as they may vary depending on the specific requirements.

5.7. Contractor shall follow current, accepted J6 C4E lifecycle governance processes and procedures. Contractor shall be responsible for managing the logistics, storage, transportation of equipment, and decommissioning legacy equipment. The contractor shall be responsible for following best DoD practices when transitioning projects to the

Operations and Maintenance (O&M) team/phase. Additional information and guidance will be provided at the call order level.

5.8. It is the intent of the government, as requirements are defined, to issue Call Orders (COs) or projects against this

BPA contract within the scope identified in this PWS. Call orders or projects may span several Task Areas, or a single Task Area, depending on government need.

5.9. Call Orders to be released via this BPA will vary in scope, start date, and duration. Task order duration will vary depending on the scope and complexity. Specific details on tasking, deliverables, documentation, training, applicable government/departmental/industry standards, etc., will be provided in individual Call Orders.

5.10. Individual Call Orders may include additional constraints specific to the work performed.

5.111. The contractor will be required to provide procurement services for the acquisition of hardware, software and network equipment required to support system development, sustainment, technical refresh, and expansion of services and/or projects as defined by the individual Call Orders. The contractor will be required to procure hardware, software, and Other Direct Costs (ODCs) to perform the work specified in individual call orders as necessary. The contractor shall provide estimated costs, including any quotes, when requesting approval for ODCs.

Government approval from the COR is required for all ODCs, prior to them being incurred. The Contractor shall provide three (3) quotes and justification for the purchase with its approval request. All equipment purchased to support a Call Order must be in compliance with the Buy American Act and Trade Agreements Act. The contractor shall track the status of all procurements until the capability is deployed in the production environment and transitioned to O&M and support Government asset management processes through the system life cycle. As specified by the applicable Call Order, the contractor shall provide temporary to long term storage/staging facilities to accomplish the receipt, inventory, integration and shipping as/when needed to accommodate the receipt and protection of materials being received pending the receipt of further material. All documentation supporting material procurements must be provided to the government for record and asset management purposes.

5.12. The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the BPA and subsequent Call Order and provide increased support for the defined task areas of the Call Order. Surge support over the life of the BPA will not exceed 10% of the contractor’s total proposed cost/price for the base and all option periods of each Call Order, excluding any six-month extension of services pursuant to FAR 52.217-8.

6. Performance Requirements.

6.1 Task 1 - Program Management

6.1.1 Kick-off Meeting. The CTA Team Leader shall plan and conduct a contract kick-off meeting within ten calendar days after award at the Government site location in the NCR to be determined at the time of award. The

CTA Team Leader shall prepare and provide an agenda and presentation. The CTA Team Leader shall prepare meeting minutes, in addition to record, distribute, and report status of kick-off meeting action items.

6.1.2 Status Reporting. The CTA Team Leader shall submit a bi-weekly status report that reports contractor’s activity and progress during that period to the COR. The CTA Team Leader’s status report shall provide updates of contractor performance and summarize tasks, including metrics, accomplishments, new efforts and future efforts planned for the next reporting period, challenges or problems encountered, and actions or involvement needed by the Government.

6.1.3 In-Progress-Review (IPR). The CTA Team Leader shall conduct a monthly, formal IPR to report overall project performance and contract status to the COR. In the IPR, the CTA Team Leader shall discuss issues and recommend courses of action pertaining to tasks specified in the PWS. The IPR is intended to address information and issues at a higher level than the Monthly Status Report (MSR) and provides the contractor the opportunity to present and discuss topics that may require decisions by the COR and/or contracting officer. Following each IPR, the contractor shall prepare and distribute minutes with an Action Item Status Report.

6.1.4 Project Schedule. The CTA Team Leader shall provide a Project Schedule for all MODEL projects. The CTA

Team Leader’s Project Schedule shall contain all major milestones (project milestones and Call Order deliverables), with planned and actual dates for each project.

6.1.5 Project Risk Register. The CTA Team Leader shall track risks associated with all active projects and provide the consolidated Project Risk Register. The CTA Team Leader’s Project Risk Register shall contain risks for each project, with impact and severity scores with corresponding avoidance or mitigation strategies.

6.1.6 Project Transition to Operations. The CTA Team Leader shall ensure a smooth transition from the project provider to Operations. The CTA Team Leader shall work with the requirement owner, project provider, and operations to ensure all activities are tracked and completed on the Transition Checklist. Any risks associated with the transition to operations shall be identified on the Project Risk Register.

6.2 Task 2 – Solution Development.

The contractor shall execute work to support J6 C4E and its customer base’s IT infrastructure modernization efforts for current and emerging mission requirements. In support of this area, the contractor shall perform activities including, but not limited to:

• Conducting lifecycle refresh (LCR) efforts to reduce technical and cybersecurity debt

• Optimization and rationalization of existing IT architecture, tools, and technical configurations

• Design and implementation of new concepts and systems in the environment to support key strategic imperatives such as cloud, zero trust, and IPv6

6.2.1 Subtask 1 – SD LAN.

DISA is currently deploying a Software Defined Network (SDN) to all supported network classifications. While the solution currently is an integration of two specific hardware vendors, the design developed can be vendor agnostic to the edge device equipment.

In support of this subtask, the contractor shall perform activities including, but not limited to:

• Move legacy, non-SDN, sections of the network to the new SDN solution

• Conduct life cycle replacement (LCR) of SDN sections of the network as the equipment approaches end of support to include both physical installation and software configuration, managing the logistics, storage, decommission of legacy equipment and transportation of equipment, and transitioning to the O&M team for support.

6.2.2 Subtask 2 – VRF Collapse Management (O&M)

The Government network consists of multiple VRFs (Virtual Routing and Forward) and VLANs (Virtual Local Area

Network) throughout the Pentagon, Mark Center, and other facilities. With the deployment of SDN many of these smaller VLANs (e.g. /25 & /26 IP scopes) need to be consolidated into large IP scopes supporting a single entity rather than the legacy solution. These efforts will range from smaller consolidation efforts to potentially larger IP scopes.

In support of this subtask, the contractor shall perform activities including, but not limited to:

• Determining a new IP schema for an organization,

• Requesting via the appropriate channels new IP scope

• Coordinating with the DHCP server operators for necessary changes

• Scheduling Authorized Service Interruptions (ASIs)

• Working through DISA review boards and processes

• Making changes to the Government infrastructure to support new IP scopes,

• Transitioning to the O&M team for support

6.2.3 Subtask 3 – IPV6 Migration

The DoD has a mandate to migrate all IP space to native IPV6 only IP space. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Determining a new IPV6 schema for DISA

• Requesting via the appropriate channels new IPV6 IP scope

• Coordinating with system owners any necessary changes that are impacted by these tasks, but not in scope of the task (i.e. transport only customers)

• scheduling ASIs

• Working through DISA review boards and processes

• Making changes to the Government infrastructure to support new IP scopes which may include network devices, firewalls, servers, load balancers, wi-fi systems, desktops, printers, and any other IP connected equipment

6.2.4 Subtask 4 – 802.1X

The Government’s SDN environment is providing 802.1X port security via media access control (MAC) authentication bypass (MAB) only. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Support 802.1X deployments using MAB and deploy certificate-based authentication.

• Coordination with the customer environment (e.g. Navy, Air Force, J6 C4E, etc)

• Certificate deployment

• Scheduling ASIs

• Working through DISA review boards and processes

• Making changes to the Government infrastructure to support 802.1X deployments,

• Transitioning to the O&M team for support.

6.2.5 Subtask 5 – Load Balancers.

J8 has F5 load balancers deployed throughout the Government network at multiple classifications levels. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Assess the current environment and determining the best design for future load balancer requirements

• Replacement of load balancers to include both physical installation and software configuration

• Coordinating the ASIs and review boards required to modernize the Government infrastructure

• Managing the logistics, storage, and transportation of equipment, decommission of legacy equipment, and transitioning to the O&M team for support

6.2.6 Subtask 6 – Cyber Security Devices and Software

J8 has a variety of security appliances and applications to maintain the cyber security and cyber assessment of all of the Government networks. Some of these services are in place because they are industry recommended solutions while others are mandated by various government organizations. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Assessing the current environment and determining the best design for future security needs that meets the mandatory software and hardware requirements of the department

• Modernization of Government cyber systems

• Replacement of the devices or software

• Coordinating the ASIs and review boards required to modernize the Government infrastructure

• Managing the logistics, storage, and transportation of equipment

• Decommission of legacy equipment and

• Transitioning to the O&M team for support

• Development of custom dashboards and reports as needed by the assessment teams

6.2.7 Subtask 7 – Deploy Zero Trust.

J8 is participating in a limited pilot of DISA’s Thunderdome Zero Trust solution, but at this time it is limited in scope and not a complete Pentagon Enterprise solution. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Performing physical and virtual network and firewall changes to support DISA’s Zero Trust solution and any DoD organization’s solutions

• Installing and configuring hardware and software to support zero-trust solutions

• Requesting and deploying necessary certificates to support solutions

• Coordinating the ASIs and review boards required to deploy a zero-trust solution

6.2.8 Subtask 8 – Cloud Connectivity

The Government operates and maintains its own data center infrastructure, with multiple data center locations established for redundancy and failover. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Include extending the Government’s data center presence into both commercial and private clouds to establish a Government hybrid cloud that consists of multiple cloud service providers

• Enable the Government to adopt various cloud service models (IaaS, PaaS, SaaS) from various cloud service providers (Azure, AWS, Oracle, DoD, etc.)

• Enable the Government to achieve the scale and elasticity required to provision compute, network and storage resources in an agile manner

Contractor shall coordinate all ASIs and review boards required to deploy a zero-trust solution and transitioning to the O&M team for support. Additional requirements under this sub-task include:

• Design and implementation Government cloud network connectivity to applicable DISA cloud access points and/or commercial cloud points of presence.

• Design and implementation of virtual cloud networking architecture across one or more cloud environments

• Design and implementation of a Government Cloud Brokering model to enable rapid provisioning and connection of new cloud services to the Government enterprise for Government enterprise or customer-specific use cases

• Provide cloud migration planning and support services to migrate applicable J6 C4E and supported customer workloads from on-premises to an appropriate cloud service model (SaaS, PaaS, IaaS)

6.2.9 Subtask 9 – COMSEC Modernization

J6 C4E has a variety of legacy (General Dynamics and Viasat) COMSEC devices deployed in the environment at multiple classifications levels. These devices range from enterprise level encryption devices that are deployed for large bandwidth efforts to small portable devices that are configured and deployed at residences and with travel teams worldwide. In support of this subtask, the contractor shall perform activities including, but not limited to:

Assessing the current environment and determining the best design for future COMSEC requirements

• Replacing COMSEC devices to include both physical installations and network/software configurations

• Requesting and installing key material

• Coordinate ASIs and review boards required to modernize the Government infrastructure, managing the logistics, storage, and transportation of equipment, decommission of legacy equipment, and transitioning to the O&M team for support

6.2.10 Subtask 10 – Layer 1 Network Infrastructure Modernization

J6 C4E s supported cable plant consists of primarily single and multi-mode fiber, RJ-45 CAT5E/CAT6 cable, RJ-11 cable, and RJ-6 cable, but it is not limited to only these types. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Assessing the current environment and determining the best design for future cabling requirements both inside the various J6 C4E supported buildings as well as between these facilities in the National Capital

Region

• Installing new cables and conduit needed to support design requirements

• Replacement of existing cable to new cable standards

• Coordinate the ASIs and review boards required to modernize the Government infrastructure, managing the logistics, storage, decommission of legacy equipment, and transportation of equipment, and transitioning to the O&M team for support.

6.2.11 Subtask 11 – Local Server Modernization

J6 C4E has on premise server infrastructure for host systems. This infrastructure consists of physical hardware that hosts virtualized and physical workloads on all classifications. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Assessing current physical and virtual server utilization and estimating future performance requirements for new infrastructure

• Installing new physical infrastructure, configuring new virtual infrastructure, configuration of host systems and connecting systems to storage infrastructure

• Coordinating the ASIs and review boards required to modernize the Government infrastructure, managing the logistics, storage, decommission of legacy equipment, and transportation of equipment, and transitioning to the O&M team for support.

6.2.12 Subtask 12 – Local Storage Modernization

J6 C4E has local SSD storage arrays providing data storage for host systems and backup systems on all classifications. In support of this subtask, the contractor shall perform activities including, but not limited to:

• Assessing current storage utilization and estimating storage growth of a LCR of the storage arrays

• Installing new storage, migrating existing data to new storage, configuration of host systems, when applicable to access the new storage

• Coordinating the ASIs and review boards required to modernize the Government infrastructure, managing the logistics, storage, decommission of legacy equipment, and transportation of equipment, and transitioning to the O&M team for support.

6.3 Task 3 - Customer Engineering Projects

The Customer Engineering Projects task (Task 2) on this BPA pertains to work in support of customer-based mission requirements. In support of this task, the contractor shall perform activities including, but not limited to:

• Design and deployment of commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS) applications in the Government environment

• Establishment of network connectivity from a customer environment to the Government environment (e.g.

Site-to-Site VPN, cloud connectivity)

• Lifecycle refresh (LCR) upgrade of customer-owned IT equipment

6.3.1 Subtask 1 – Application Development

J6 C4E hosts a number of custom developed applications that support various parts of the J6 C4E customer base.

These applications have been developed over the past 15 – 20 years using coding and development practices from the time they were developed. These applications interface with both Windows and Linux environments and SQL and Oracle database servers. The J6 C4E supported customers may request that these applications be modernized to support on premise or cloud-based solutions in the future. Special exceptions would need to be provided for future on-site hosting of customer applications as all should be moved to the cloud and developed with that end state in mind.

In support of this sub-task, the contractor shall perform activities including, but not limited to:

• Assessing the current application and determining the best strategy

• Application design and development

• Application testing

• Cyber compliance and customer acceptance

6.3.2 Subtask 2 – Application Upgrade

Applications that are developed in Subtask 6.2.1 or other customer developed applications will need to be deployed.

• Developing the upgrade strategy for the application

• Upgrading the application to include new requesting all necessary connectivity and firewall requirements

• Connecting the new application to the appropriate database servers

• Data migration from legacy applications into the new application, which may include migrating the data to the cloud

• Coordinating the ASIs and review boards required to modernize the application, managing the logistics, storage, decommission of any legacy equipment, and transportation of equipment, and transitioning to the application to the O&M team for support.

6.3.3 Subtask 3 – SharePoint development

J6 C4E customers have on-premise SharePoint instances that may require custom development. While they may still need on-premise SharePoint for some requirements, most of the development should be focused on using the cloud for hosting and exceptions would need to be made to keep it on premise. In support of this sub-task, the contractor shall perform activities including, but not limited to

• Assessing the current SharePoint instance and determining the best strategy for a new instance,

• Building and testing the new instance,

• Connecting the new instance to the appropriate databases and requesting the correct firewall settings,

• Obtaining cyber acceptance of the development.

• Migrating the existing instance and its data to the new instance, coordinating the ASIs and review boards required to modernize the instance, and transitioning this to the O&M team for support.

6.3.3.1 Subtask 3.1 – Collaboration Applications

J6 C4E and its customers require technical support for all phases of system planning and design through deployment and decommissioning to ensure that SharePoint and CRM platforms enable J6 C4E customers to meet their mission, goals, and objectives.

• Contractor shall build SharePoint and CRM roadmap in relation to the overarching J6 C4E customer technologies roadmaps to ensure alignment

• Contractor shall manage IT service dependencies; translate strategic initiatives into functional capabilities and corresponding IT requirements; define capability gaps; manage the technical plans for IT engineering, enterprise architecture projects

• The contractor shall coordinate infrastructure development efforts; and ensure quality tools and technologies are delivered according to Government cost, schedule, and performance objectives

• The contractor shall formulate, regulate and implement SharePoint governance and ensure alignment with overarching J6 C4E governance.

• The contractor shall translate J6 C4E’s and/or customer strategic initiatives into functional capabilities and corresponding IT requirements and define capability gaps with the SharePoint and Dynamics CRM architectures.

• The contractor shall coordinate infrastructure development activities between the various SharePoint and

Dynamics CRM support teams within J6 C4E.

• The contractor shall lead SharePoint and Dynamics CRM migration planning.

6.3.3.2 Subtask 3.2 – Application and System Engineering Service Delivery

J6 C4E and its customers require specialized engineering support and administration of J6 C4E customers’

SharePoint and CRM, supporting certification and accreditation, approved tools, and application delivery. In support of this sub-task, the contractor shall perform activities including, but not limited to:

• Planning, building, modifying and deploying new virtual infrastructure and support infrastructure changes, patching, upgrades for the contractor delivered development, test, and staging and production environments successfully while minimizing interruptions to customers.

• Performing the onboarding, off-boarding, migrations, and upgrades relevant to J6 C4E supported customers and ensure capacity management, backups, and high availability throughout the lifecycle of the platforms.

6.3.3.3 Subtask 3.3 – Dedicated Customer Support

J6 C4E and its customers require SharePoint site administration, which can minimally include: user administration, access control, content management, and training for J6 C4E customers for Microsoft SharePoint and CRM platforms; and mission configured portals, built, maintained, or delivered as a service. These tasks include delivering focused on-site support to end-users, site-owners and administrators with the tools, materials, documentation, and capability to fully utilize Microsoft SharePoint and CRM platforms and enhance successful adoption after new releases and migrations. J6 C4E requires delivering support to sustain knowledge, cultivating data environments, and fostering usage of the supported Platforms Services throughout the lifecycle. These efforts include delivering SharePoint business processes and technical support to facilitate day-to-day operations and collaboration with mission partners while continuously working to improve, streamline, automate, and integrate content and business operations into the Portal environment.

6.3.4 Subtask 4 - Applications Services Engineering

The contractor shall provide engineering services for core applications services, implementation, and modernization to meet the needs of the nation’s warfighters, national level leaders, and mission and J6 C4E partner organizations and customers. Core applications shall be developed for cutting edge DISA applications (e.g., web-based apps, mobile apps) and discoverable enterprise services; the customization, configuration, and integration of Commercial-

Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) software products and services; end-to-end managed service capabilities; and professional services (e.g., help desk, network management and operations, program management, leased data circuits and transport, and operating equipment and facilities).

6.3.5 – Subtask 5 - System Engineering and Design Support.

The objective of this task is performance of System Engineering & development of a Design plan associated with J6

C4E customers for the NCR to include, but not limited to, the J6 C4E portion, for J6 C4E customers, of the Joint

Information Environment (JIE)/Joint Regional Security Stacks (JRSS ) transport and/or IP network architectures. In support of this sub-task, the contractor shall perform activities including, but not limited to:

• Analyzing existing and planned Government transport architectures and recommend appropriate actions or changes for the best alternatives.

• Providing network designs, trade-off analyses, and technical solutions to resolve network transition issues.

• Defining/describing the Government transport goal architecture, services, and how J6 C4E will provide, operate, and manage consolidated information system networks and services in System Modeling

Language.

• Coordinating emerging requirements with user representatives and appropriate DISA staff members, ensuring user requirements and associated milestones are met.

6.3.6 – Subtask 6 - Test and Development Environment.

The contractor shall provide overall Program and Project Management and Operations & Maintenance (O&M) support to J6 C4E Test environments by providing services to the organization’s demonstration, piloting, development, testing, and deployment needs.

The contractor shall provide engineering expertise in the analysis, design, development, testing, and implementation process of special initiatives and proposed enhancements and modifications for inclusion in J6 C4E Test and

Evaluation Environments (JTEE). Design plans shall be developed based on the results of the analysis of network requirements and provided in report format.

6.3.7 – Subtask 7 - Software Engineering and Development

The contractor shall provide application software development, application maintenance, and implementation services. This includes providing enterprise approach to application development and maintenance utilizing agile methodologies that deliver timely, reliable, and secure solutions that meet customer expectations.

The software release life cycle primarily addresses the design and implementation of source code, through software test and integration, to operational fielding and software services. Software development includes background research and analysis; proof-of-concept, prototyping and piloting for new development; incremental enhancements and upgrades; integration of commercial and Government products; reuse and re-engineering; migration of services and operations from systems; and software maintenance to address corrective actions, security measures and continual functionality improvements.

Software development employs the core sub-disciplines of software construction; software development methodology; software process design; software CM; software test and integration; software migration; software safety, security and information assurance; software deployment; and software supportability, scalability and extensibility.

6.3.7.1 – Subtask 7.1 – Customers’ Requirement Gathering and Design.

• Schedule meetings with customers to discuss and resolve software requirements and performance issues.

• Conduct analysis and research on established software requirements, functional baselines, technical planning documents, and Software Development Library (SDL).

• Develop Levels of Effort estimates for an entire work project or by Sprint for customer requirements.

• Ensure legal and regulatory compliance

• Provide all solutions compliant with all DoD and Agency Directives and best practices, including 508 compatibility

• Ensure that C&A is established and maintained for applications and solutions

• Create mockups/wire frame models for design verification of addressing customer or J6 C4E requirements

• Create and maintain Requirement Traceability Matrix/Product Backlog

• Schedule and conduct a design kick-off meeting to provide an overview of the design phase and the design methodology to be used. Review the schedule for completion of preliminary design and the assigned responsibilities of each design team member. For preliminary design phase activities, discuss preliminary results obtained during the requirements analysis phases. The deliverable being a Systems Design Document monthly.

• Submit technical planning documents to Configuration Approval Board for configuration control and deliver them for review and approval.

• Conduct Software Requirements Review (SWRR).

6.3.7.2 – Subtask 7.2 - Integration & Deployment

The contractor shall integrate component subsystems and ensuring that those subsystems function as a whole.

• Develop and apply strategies to integrate the system according to the priorities of the system requirements.

• Develop criteria to verify compliance with the system requirements allocated to the system elements, including the interfaces between system elements.

• Verify integration results using well-defined and appropriate criteria and identify and correct deficiencies.

• Develop and apply regression strategies for retesting the system when changes are implemented.

• Verify and ensure consistency and traceability are established between the system design and the integrated system elements.

• Demonstrate that the system built complies with the system design, develop, and verify a complete set of usable deliverable system elements.

• Develop and ensure that all software components are integrated with hardware configuration items, manual operations, and other systems as necessary, into the system.

• Perform successful software integration processes that combines the software units and software components, producing integrated software items, consistent with the software design, that demonstrate that the functional and nonfunctional software requirements are satisfied on an equivalent or complete and unified operational platform.

• Develop integration strategies that are consistent with the software design and prioritized software requirements.

• Develop and use verification criteria for software items that ensure compliance with the software requirements allocated to the items.

• Define and align software items with integration strategy

• Develop and apply appropriate test and strategy for re-verifying software items when a change in software units

(including associative requirements, design, and code) occur.

• Develop an integration plan to integrate the software units and software components into the software item.

• Collaborate with Government to identify procurement, licensing, and other requirements for proposed software.

• Coordinate with System Administrators for deployments.

• Provide recommendations for implementing Agile Development Operations within Government environment.

6.3.8 – Subtask 8 - Cloud Engineering

The contractor shall execute J6 C4E’s approved Cloud Engineering’s models for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction for consumers and producers. Efforts associated with this task include deploying cloud engineering in at least four environments (Private cloud, Community cloud, Public cloud, and Hybrid cloud). Key enabling technologies in the cloud include: (1) fast wide-area networks, (2) powerful, inexpensive server computers, and (3) high-performance virtualization for commodity hardware.

6.3.8.1 – Subtask 8.1 - Cloud Migration and Transition.

The contractor shall integrate new applications into cloud environments and transitioning existing applications into virtualized/cloud environments. These services include the entire cycle of transition events, from acquiring cloud service provider enclaves for the customer, including market research and piloting efforts, to creating the design and architectures, transitioning data, testing activities. These services can be provided for applications to be hosted by all types of cloud service providers, including commercial, Government, and hybrid solutions.

6.3.8.2 – Subtask 8.2 – Application Cloud Analysis Services.

The contractor shall, based on customer’s mission application requirements, evaluate, assess, and recommend if service is a cloud candidate, and provide an optimal migration strategy to the cloud (as applicable).

The contractor shall assist customers in developing tailored action plans to move existing workloads to the Cloud to include high-level timelines, and estimated costs. Efforts associated with this subtask include providing recommendations for potential Cloud Service Provider (CSP) based on the CSP’s under the Joint War Fighter Cloud

Capability contracts.

Efforts associated with this subtask include reviewing and assessing the application using a pre-defined methodology to determine the application cloud-fit score. As part of this methodology, activities include working with the Customer to answer key information like the organization mission, application business requirement, application technical information, infrastructure requirements, storage requirements and other data for consideration in the analysis. Based on this information, activities include conducting analysis and evaluating the application’s cloud fit score to determine if a good candidate for the cloud and then determines the CSP with the best value and meets the business need. If the application is not a good candidate for the cloud, efforts include providing recommendation of potential way forward. The analysis is shared with the Customer to get agreement on the CSP option recommendation, based on the selection a high-level migration plan is developed along with a rough order of magnitude (ROM) cost to complete the migration.

6.3.8.3 – Subtask 8.3 – Cloud Migration Advisory Services.

The contractor shall advise Customers on design compliance and adherence with DoD cloud security architecture in accordance with the Cloud Computing (CC) Security Requirements Guide (SRG).

Activities associated with this subtask include supporting customers in securing key implementation providers (e.g., CSP, Cyber Security Service Providers (CSSP), Operations and Maintenance (O&M) support partners, etc.). The contractor will not provide CSSP services directly. Security scanning of the network traffic which are required at the Internet Access Point (IAP) juncture of NIPR/Internet. The contractor will not provide Secure Cloud Computing

Architecture (SCCA) services directly; the objective is to provide advisory on SCCA. SCCA is a suite of enterprise-level cloud security and management services providing boundary and application-level security to include: Cloud

Access Point (CAP); Virtual Data Center Security Stack (VDSS); Virtual Data Center Managed Services (VDMS);

and Trusted Cloud Credential Manager.

The objective includes working with the Customer and with their designated Customer Account Manager (CAM) to support completion of a Business Requirement Document (BRD) for submission through the J6 C4E Governance process for review and approval.

6.3.8.4 – Subtask 8.4 – Cloud Engineering Services.

For Customers who are on the Government network and require reach back to J6 C4E on-premise services have identified and selected a Cloud Software as a Service (SaaS) solution that is FedRAMP certified, the objective of this subtask is to provide Engineering Services for identification, authentication, and access control credentials. The efforts associated with this subtask includes providing some data migration support for applications hosted on the

Government network.

The efforts include working with the Customer and with their designated Customer Account Manager (CAM) to support completion of a Business Requirement Document (BRD) for submission through the J6 C4E Governance process for review and approval.

6.4 Task 4 –Telecom and Networking Professional Services

J6 C4E has a variety of efforts initiated by customers to both join the Government network as well as stand-up a new facility or office that needs to be joined to the Government network.

In support of TELECOM and Network requirements, the contractor shall perform activities including, but not limited to:

• Provide basic network transport services and complete end-to-end solution including end-user devices.

determining the customer’s requirements at the network level (port capacity, bandwidth requirements, network protection requirements)

• Installation and configuration of all equipment necessary to meet the network requirements.

• Coordinating the ASIs and review boards required to modernize the Government infrastructure, managing the logistics, storage, and transportation of equipment, and transitioning all equipment to the requisite

O&M teams for support.

6.4.1 EIS Spillover.

In support of TELECOM and Networking requirements and activities, J6 C4E and its customers require voice services and data services along with related technical support and customer premises equipment (CPE). The efforts require commercially available telecom and IT products and services in the following areas:

• VoIP

• Data

• ISDN PRI/BRI

• Analog/Digital Trunk

• Equipment/CPE

• Conferencing

• Professional Services

6.4.2 – Subtask 4 - J6 C4E Customer and Mission Partner Requirements Analysis.

The contractor shall develop engineering analysis plans and designs for all network architectural requirements. In support of this sub-task, the contractor shall perform activities including, but not limited to:

• Evaluate requirements for existing/future optimization and planning initiatives and provide recommendations and solutions to expand the transport to meet customer demands.

• Develop detailed engineering plans detailing the transport bandwidth for unclassified, secret, and top-secret requirements.

• Develop engineering design documentation to meet future customer transport requirements. The contractor shall develop a network design functional database and design documentation for the Government fiber architecture.

• Develop and review of project Bill of Materials; to include input for inclusion in the SED.

• Develop weekly status on current and future engineering activities; the development of quarterly updated engineering plans and designs; and the development of current engineering diagrams for all J6 C4E missions.

• Conduct at internal/external project management meetings with Government project leads, develop briefing slides for Senior Leadership/project leads, develop white papers and develop transport related engineering studies.

6.4.3 – Subtask 3 - Infrastructure & Network Engineering.

The contractor shall provide engineering services to sustain existing Government terrestrial, and wireless transport infrastructures and their approved architectures in the NCR Metropolitan Area Network (MAN) and Wide Area

Network. The goal of Infrastructure Network Engineering is to develop and maintain functional and secure networks ensuring the protection and availability of data & voice networks in all classifications.

The efforts associated with this task include providing expertise in the areas of LANs, MAN, WANs, firewall services, network monitoring tools, router, and switch configuration. Network engineers must analyze communications, create plans for the network, present it to senior management, be up-to-date on the latest technology, understand, and determine the hardware and wiring needs. Activities include providing technicians with expertise in local and wide area network design and analysis, disaster recovery planning and implementation, storage technologies (i.e., Storage Area Network), AD design, implementation, and optimization; technical designs, implementation and optimization and other services related to system, software, and network engineering.

Desired Skill Sets:

1) Basic Server administration

2) Disaster Recovery Planning/Execution

3) Juniper Firewalls

4) Palo Alto Firewalls

5) Cisco Firewalls

6) Cisco Virtual Private Network devices

7) Load Balancers

8) Data and Voice Circuit

9) Basic Telecommunications

10) Remote Access Technologies

11) Switching

12) Routing

13) Voice Over Internet Protocol

14) Video Teleconferencing

15) Adaptive Security Appliance

16) Multi Router Traffic Grapher/Paessler Router Traffic Grapher/Cacti software.

17) TCP/IP

18) IPv6

19) Network Monitoring Tools

20) Solar Winds

21) LAN/WAN

22) Storage Area Networking

23) Backup and Recovery Operations

24) CM and Change Control

25) Firewall Configuration and Administration

26) Intrusion Detection Systems/Intrusion Prevention Systems Configuration and Administration

27) Access Control Technologies

28) Vulnerability Assessment

29) Forensics

30) Malicious Software Remediation

31) Penetration Testing

32) Risk Acceptance Analysis

33) Metropolitan Area Networks

34) Wide Area Networks

35) Microsoft desktop/server operating systems

36) Data Centers

37) JRSS

38) Virtual Desktop Infrastructure (VDI)

39) Virtual Machine (VM) technologies

40) Hosting Platforms

41) Aruba Access Points (APs)/RP

42) Clouds (MilCloud 2.0, Amazon Web Services [AWS], Azure)

43) DISA Enterprise E-mail

44) Arista Switches

6.4.4 – Subtask 4 - Engineering Assessments.

The contractor shall assess the systems engineering activity or problem in the context and operational environment in which the solution be embedded. This comprehensive viewpoint enables the ability to develop and apply solutions that consider all aspects of a problem, their relationships, and interactions with other project or services.

The assessment includes current and future needs of the user, customer, and sponsor as well as Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel and Facilities and technical issues. This task area requires a very high-level of skill and breadth and depth of senior expertise to assess the technical domain and solution space, designs, and architecture.

The engineering assessments shall be performed proactively and intended to provide an early look into what potential problems may be on the horizon.