ITSS PWS - Att. 001.pdf

ACQUISITION SENSITIVE

PRODUCT LEAD ACQUISITION, LOGISTICS, AND TECHNOLOGY

ENTERPRISE SYSTEMS AND SERVICES (PL ALTESS)

PERFORMANCE WORK STATEMENT (PWS)

FOR

INFORMATION TECHNOLOGY (IT) SERVICES AND

SUPPORT

06 JUN 2025

Version 0002

PL ALTESS

ATTN: SFAE-PSE-AL

Radford Army Ammunition Plant (RAAP) BLDG 220

RADFORD, VIRGINIA 24143-0004

Table of Contents

1. GENERAL INFORMATION 12

1.1 Scope 12

1.2 Period of Performance (PoP) 12

1.2.1 Transition-In / Transition-Out Period 12

1.2.1.1 Transition-In 13

1.2.1.2 Transition-Out 14

1.3 Background 14

1.4 Technology Baseline 15

1.4.1 Current Support Baseline 16

1.5 Place of Performance 16

1.6 Installation Closure 17

1.7 Travel 17

1.8 Quality Control 17

1.9

Performance Standards and Quality Assurance Surveillance Plan (QASP) 18

1.10 Points of Contact 18

2. GOVERNMENT FURNISHED EQUIPMENT (GFE), PROPERTY &

SERVICES 18

2.1 Facilities, Supplies and Services 18

2.2 Ancillary Information 18

2.3 Physical Security 18

2.4 Data Rights 18

3. CONTRACTOR FURNISHED ITEMS AND SERVICES 18

3.1 General 18

3.2 Materials and Other Direct Costs (ODCs) 19

3.3 Security 19

3.4 Cybersecurity 19

3.5

Conflicts of Interest and Non-Disclosure of Proprietary Information 20

3.5.1 Personal Conflicts of Interest 22

3.5.2 Organizational Conflicts of Interest 22

3.5.3 Personal and Substantial 22

3.5.4 Incidental Construction 23

4. REQUIREMENTS AND TASKS 24

4.1 Objectives 24

4.1.1 Task Area 1 – Operations 25

4.1.1.1 Data Center and IT Infrastructure Support 25

4.1.1.2 Facilities 26

4.1.1.3 Network 26

4.1.1.4 Virtualization 27

4.1.1.5 Storage 28

4.1.1.6 Backup & Recovery 29

4.1.1.7 Operations Center 31

4.1.1.8 Continuity of Operations (COOP), Disaster Recovery 31

4.1.1.9 Desktop Support 32

4.1.1.10 Linux 33

4.1.1.11 Windows 33

4.1.1.12 Citrix 34

4.1.1.13 Microsoft Endpoint Configuration Management (MECM) 35

4.1.1.14 Monitoring 35

4.1.1.15

Development, Security and Operations (DevSecOps) & Automation 36

4.1.1.16 On Premise Edge Infrastructure 37

4.1.2 Task Area 2 – Cloud Management 37

4.1.2.1

Enterprise Resource Planning (ERP) Cloud Infrastructure 37

4.1.2.2 Commercial Cloud Infrastructure 37

4.1.3 Task Area 3 – Cybersecurity 38

4.1.3.1 Cyber Engineering & Incident Response 38

4.1.3.2 Internal Controls 39

4.1.3.3 Network Defense 40

4.1.3.4 Software Assurance 40

4.1.3.5 Cyber Operational Readiness Assessment 41

4.1.4 Task Area 4 – Application Management 42

4.1.4.1 Application Modernization 42

4.1.4.2 Database 43

4.1.4.3 Middle Tier 44

4.1.4.4 IT Services Management (ITSM) 45

4.1.5 Task Area 5 – Services Management 45

4.1.5.1 FinOps & Cost Model 46

4.1.5.2 Agile Center of Excellence (ACoE) 46

4.1.5.3 Customer Relationship Management 48

4.1.5.4 Audit Support 49

4.1.5.5 Budget 50

4.1.5.6 Contracts 51

4.1.5.7 Logistics 51

4.1.5.8 Physical Security 52

4.1.5.9 Administrative Support 52

4.1.4.10 Solutions Architecture 53

4.1.4.11 Technology Evaluations 54

4.1.4.12 IT Governance 54

5. CONTRACT DELIVERABLES 54

5.1 Contract Data Requirements 55

5.2 Transition – In Plan 57

5.3 Transition – Out Plan 57

6. KEY CONTRACTOR PERSONNEL 58

6.1

On-Site Program Manager (PM) (Program Manager - Senior) 59

6.2

Senior UNIX System Engineer (Systems Administrator – Senior) 69

6.3 Senior Windows Administrator (Systems Administrator – 61

Senior)

6.4

Senior Storage Administrator (Systems Administrator – Senior) 62

6.5

Senior Citrix Administrator (Systems Administrator – Senior) 63

6.6 Network Administrator (Network Administrator – Senior) 64

6.7

Common Cloud Environment (C2E) Support Lead (Program Manager – Intermediate 66

6.8 Cloud Engineer (Software Engineer - Senior) 67

6.9 Applications Team Lead (Software Engineer – Senior) 67

6.10

Middleware Team Lead (Web Software Developer – Senior) 68

6.11

Database Team Lead (Advanced Database Analyst/Programmer - Senior) 69

6.12

Senior Cybersecurity Incident Response Administrator (Information Assurance Engineer - Senior) 70

6.13

Senior Cybersecurity Internal Controls Administrator (Information Assurance Engineer - Senior) 71

6.14

Senior Cybersecurity Network Defense Administrator (Information Assurance Engineer - Senior) 72

7. ADVERSARY TACTICS, TECHNIQUES, AND PROCEDURES /

OPERATIONS SECURITY (AT/OPSEC) IN ACCORDANCE WITH

(IAW) AT/OPSEC COVER SHEET 73

7.1 AT Level I Training 74

7.2 Common Access Card (CAC) 74

7.3

Army Training and Certification Tracking for contractor employees 74

7.4 For contracts that require OPSEC training 74

7.5 For Cybersecurity Information Technology (IT) training 75

7.6

For Cybersecurity/Information Technology (IT) certification 75

7.7

For contracts that require handling or access to classified information 75

7.8 Threat Awareness Reporting Program (TARP) 75

8. SERVICE CONTRACT REPORTING 75

9. LEVEL OF EFFORT 76

1. General Information

1.1 Scope

This PWS defines the IT Services and Support (ITSS) requirements for the U.S. Army Product Lead Acquisition, Logistics, and Technology Enterprise Systems and Services (PL ALTESS) requirement, in support of the Program Executive Office Enterprise (PEO Enterprise). PL ALTESS is the PEO Enterprise Agile Center of Excellence (ACoE) identified as the lead organization for this project and product acquisition. This effort will support the following key functional areas: IT Service Operations, IT Service Delivery, Service Operations Center Operations, customer training, full lifecycle IT testing and support, IT Data Center Operations, Network and System Administration, Cybersecurity, Disaster Recovery/Business Continuity Operations, Hardware (HW)/Software (SW) integration and migration, requirements definition and management, Service Level Management (SLM), process design and management, Business Management, Application Services and Modernization, Acquisitions and Procurements, Infrastructure Services (Facilities Operations), Command Group support, and incidental construction to support the PEOs, ACoEs and other agencies within the Department of Defense (DoD) and the Federal Government.

1.2 Period of Performance (PoP)

The PoP for this effort shall consist of a 12-month base period, inclusive of a 30-day transition-in period, and four 12-month option periods.

Base Period – 01 May 2026 to 30 April 2027

Option Period 1 – 01 May 2027 to 30 April 2028

Option Period 2 – 01 May 2028 to 30 April 2029

Option Period 3 – 01 May 2029 to 30 April 2030

Option Period 4 – 01 May 2030 to 30 April 2031 Table One (1) Contract Periods of Performance

1.2.1 Transition-In / Transition-Out Period

To minimize any decreases in productivity and to prevent negative impacts on mission-critical services, the selected contractor shall have key personnel on-board, during the 30-day phase in/phase out periods.

1.2.1.1. Transition-In

All transition activities will be based on a transition period of 30 calendar days. During this time, the selected contractor shall work alongside the incumbent to transfer support. The selected contractor (if other than the incumbent) must address all required documentation, orientation, partnering and training to facilitate the execution of the content identified in the PWS, functional processes, procedures, schedules, and deliverables in a timely and acceptable manner and No Later Than (NLT) the end of the 30-day transition period. During the Transition-In period, the incumbent (outgoing prime contractor) remains responsible for all system sustainment activities and continued support in each of the key functional areas listed in Section 1.1, until full knowledge transfer has been completed for each of the functional areas (can be phased), or through the end of the transition period, whichever occurs first.

The incumbent shall implement adequate measures to coordinate communications with the selected contractor, and their staff to ensure uninterrupted workflow and minimal mission impact during the transition process. The selected contractor shall ensure no service degradation after completion of knowledge transfer, or end of the transition period, whichever occurs first. Throughout this period, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. Key personnel (see PWS section 6 below) are considered essential to successful contractor performance. All key personnel are required to have security clearances and shall be available to work at the start date of the task order. The transition-in period will include hiring and training of contractor personnel, knowledge transfer and obtaining updated or new CACs for all personnel as they are hired or transferred over to the selected contractor (if other than the incumbent).

All badges should be taken into account for the proposed transition in plan to include obtaining CACs, RAAP plant badges, Non-Secure Internet Protocol Router (NIPR) Network, Alternate Smartcard Login (ASCL) tokens (if needed), and Secret Internet Protocol Router (SIPR) Network, user and admin ASCL tokens (as needed). Lead time on ASCL tokens is roughly 60 days. There are no badging offices on RAAP to obtain CACs and the nearest three offices to obtain a CAC are: Abingdon, VA, Charlottesville, VA, and Beckley, WV. Those offices require appointments and frequently book up in advance. All lead times and travel should be reflected in the proposed plan.

1.2.1.2. Transition-Out

During the transition-out period the outgoing prime contractor remains responsible for all system sustainment activities through the end of the transition out period. The outgoing prime contractor shall identify and coordinate with the incoming selected contractor (if other than the incumbent) to transfer knowledge of this requirement. All transition activities, as identified in their Transition-Out Plan (see PWS section 5.3 below), must be approved by the government. At a minimum the outgoing prime contractor shall:

• Provide the status of ongoing functional processes and procedures

• Establish contractor to contractor coordination to ensure a seamless transition

• Transition knowledge and information from key contractor personnel

• Transition knowledge and information regarding risk or problem areas

As part of the transition-out process, the outgoing contractor shall complete all formal invoicing activities in a timely manner and provide to the Contracting Officer Representative (COR) written notice that the final invoice has been submitted, and no future invoices will be submitted. The government understands that the final invoice might not be submitted until sometime after the contract PoP has ended. The transition shall ensure minimum disruption to vital government business. The incumbent shall implement adequate measures to coordinate communications with the selected contractor, and their staff to ensure uninterrupted workflow and minimal mission impact during the transition process.

The selected contractor shall ensure no service degradation after completion of knowledge transfer, or end of the transition period, whichever occurs first.

1.3 Background

PL ALTESS provides Enterprise Class Data Center services from server hosting, SW design and system architecture to lifecycle management, problem solving and Enterprise Service Operations Centers for PL ALTESS hosted customers and associated users. PL ALTESS has a mission to keep systems up and running and serving customers 24 hours a day, seven days a week, and 365 days a year (24x7x365). PL ALTESS supports multiple missions throughout the DoD, Army and Federal workspaces. Data centers supported by this PWS are expansive and integrated across multiple geographical locations, consisting of both physical and virtual architectures, supporting hundreds of programs, thousands of virtual servers, and millions of users worldwide. PL ALTESS supports a diverse range of complex missions

1.4 Technology Baseline

IT is a very dynamic field. No two information systems, networks, or enclaves will require the same level of support due to numerous reasons (size and complexity of the system, network, or enclave; maturity of the system; security posture and data complexity requirements of the system; combination of technologies and vendor uniqueness).

The contractor shall possess the capability and expertise to support a diverse range of server and workstation HW, peripherals, and associated technologies, including but not limited to: Hewlett Packard (HP) and Dell servers and peripherals, Dell and HP workstations, Cisco UCS, thin clients, and peripherals, Linux and Microsoft (MS) Windows Server Editions, Oracle Servers, VMware vSphere virtualization product suite, Army General Funds Enterprise Business System (GFEBS), virtualization management solutions, Citrix XenApp application delivery product suite, SAP business management product suite, Tenable Nessus vulnerability assessment tools (Assured Compliance Assessment Solution), log aggregation/Security Information and Event Management (SIEM), Trellix Security System (Army Endpoint Security Solution), McAfee Intrusion Detection Systems, Defense Information Systems Agency (DISA) Enterprise Mission Assurance Support Service (eMASS), MS Office application product suite, MS System Center Configuration Manager (SCCM), MS SharePoint business collaboration suite, SolarWinds Orion performance monitoring, Cisco network routers and switches, F5 BigIP network load balancers, Wide Area Network (WAN) devices, Cisco ISE, Cisco MDS Fibre Channel Switches, IP Adress Management (IPAM), Pure Storage Systems, International Business Machines (IBM) storage systems, Veritas NetBackup, MS Structured Query Language (SQL), Oracle (Business Intelligence (BI), Development Tools, Service-Oriented Architecture (SOA) Suite, Coldfusion, Adobe, Dreamweaver, Java, JavaScript, WebLogic, ServiceNow, Jira, Confluence, Hashicorp Vault and Zero Trust Security, Red Hat Ansible Automation, Gitlab Ultimate, Terraform Enterprise Platform, vSphere Enterprise Plus, vRealize Automation Enterprise (includes Salt Stack SecOps), vRealize Operations Enterprise, vRealize Log Insight Enterprise, NSX- T, vRealize Network Insight, VMware Software-Defined Data Center(SDDC) Manager, VMware Cloud Director.

It should be understood versions and vendors will change as a part of the IT lifecycle.

The contractor must be capable of supporting all technologies required by the data center.

1.4.1 Current Support Baseline

The contractor shall provide staffing to support the following minimum baselines.

Functional/Technical Area

Current Metric

• Number of physical servers • 250 servers

• Number of virtual servers • 1700 servers

• Number of programs supported • 100+ systems

• Number of end-users

(aggregate)

• 3.62 million users

• Number of Customer Interagency Support Agreements (IAA)

• 80 -100 IAAs per year

• Number of Purchase Requisitions (non- contract) per year

• 400 PRs

• Number of Service Operations Center Incidents Managed

• 1,575+ per month

• Number of changes managed • 450+ per month

• Number of SW assets • approx. 16000

• Number of HW assets • approx. 3800

• Contract staff (all at government sites) reference attachment 0005 – government historical data

• Radford/Ft. Bragg – primary locations with potential staffing at alternate sites CONUS /

OCONUS: 206

Table Two (2) Current Support Baseline

1.5 Place of Performance

Work in support of this PWS shall be performed primarily at the PL ALTESS site on the Radford Army Ammunition Plant in Radford, Virginia with possible work taking place at additional locations both CONUS and OCONUS.

All Service Operations Center operations will be in Radford or other designated Army location CONUS and OCONUS. The contractor may be authorized to telework dependent upon the required tasks of the PWS and the positions’ ability to perform the work offsite, pending the government’s approval.

1.6 Installation Closure

Situational telework may be authorized for any emergency, administrative closing or similar government directed closings. The contractor must always maintain an adequate workforce to ensure uninterrupted performance of all tasks defined within this PWS.

Payment will only be made for authorized hours worked. For example, no payment will be made for hours not worked if the station is closed or inaccessible, or for hours not worked due to early excusal of the government.

1.7 Travel

The contractor will be required to perform local and non-local travel to attend meetings, conferences, demonstrations and working groups to perform the tasks described in this PWS. The contractor shall obtain COR approval for travel, via contractor travel requisition, No Later Than (NLT) five business days prior to undertaking any long-distance travel (travel greater than 50 miles or requiring an overnight stay) to any government site or any site in the performance of the contract. The approval request will provide the following information: purpose of travel, destination, dates of travel and estimated cost. Non-local travel is defined as travel above and beyond the commute to and from the normal worksite; for example, travel to a separate National Capital Region (NCR) site by an employee normally assigned to Radford Army Ammunition Plant in Radford, Virginia. The contractor shall be responsible for ensuring all travel arrangements are made, including reservations, requisite travel documents, etc. Actual expenses are limited by the Joint Travel Regulations (JTR). The government will not process Invitational Travel Orders for the contractor. The contractor shall make available upon request the proposed or actual travel costs, possibly to include receipt and/or other documentation. Federal Acquisition Regulation (FAR) 31.205-46 “Travel Costs” Travel and per diem costs shall be reimbursed at cost, not to exceed the current rates specified in the JTR. This information can be found at the DTMO web site:

https://www.defensetravel.dod.mil/site/perdiemCalc.cfm No profit shall be allowed on travel costs.

1.8 Quality Control

The contractor shall develop and maintain an effective Quality Control Program (QCP) to ensure services are performed IAW this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP is the means by which he/she assures that the work complies with the requirement of the contract. The contractor shall deliver the QCP to the COR via email within 10 days after the contract’s PoP start date.

http://www.defensetravel.dod.mil/site/perdiemCalc.cfm

1.9 Performance Standards and Quality Assurance Surveillance Plan (QASP) Performance standards establish the performance levels required by the government. A QASP will be drafted by the government outlining a systematic method to evaluate performance under the contract issued against this PWS. The QASP is a “living document” and as such, in coordination between the contractor and the government, shall be reviewed and revised on a regular basis. Updates shall ensure that the QASP remains a valid, useful, and enforceable document.

1.10 Points of Contact

The COR, Alternate COR (ACOR), and Technical Point of Contact (TPOC) will be identified at contract award.

2. GFE, PROPERTY & SERVICES

2.1 Facilities, Supplies and Services

The government will provide on-site facilities when necessary to perform work required under this contract. On-site facilities include office space, office supplies, computer equipment, telephone, and reproduction resources when the contractor is working on-site to the extent deemed necessary by the government.

2.2 Ancillary Information

The government will provide access to any ancillary information that may be needed by the contractor to execute the tasks contained in this PWS.

2.3 Physical Security

The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

2.4 Data Rights

The Government will have full ownership of all technical data, reports, and deliverables associated with this contract.

3. CONTRACTOR FURNISHED ITEMS AND SERVICES

3.1 General

Except for those items specifically identified to be government-furnished property, the contractor shall furnish everything required to perform the tasks in this PWS. This may include providing HW, SW, and related items.

3.2 Materials and Other Direct Costs (ODCs)

Materials and ODCs shall be provided by the contractor when essential to the task performance and specifically approved by the government, not to exceed the ceiling price identified in the contract. ODCs are defined in the Federal Acquisition Regulation as costs not previously identified as a direct material cost, direct labor cost, or indirect cost. All materials purchased by the contractor for the use or ownership of the Federal government will become property of the Federal government. The contractor shall document the transfer of the materials IAW the contract requirements.

3.3 Security

Access to classified documents, studies, reports, and other documentation and information may be required. The DD Form 254, "Department of Defense Contract Security Classification Specification," will be provided with this PWS for the purpose of specifying security requirements for all contractor personnel. Furthermore, the contractor will be accessing a Sensitive but Unclassified (SBU) network, Secret network and/or a Top-Secret network. All contractor positions must possess the appropriate background investigation or security clearance level commensurate to the appropriate automated data processing Level 1, 2, or 3 as designated by the Cybersecurity staff and Army Regulation 380-67 (AR 380-67), Personnel Security Program and as specified in the DD 254. Higher security clearance levels may be required. All contractors must hold US citizenship. The contractor will initiate the appropriate level of security clearance background investigation to result in issuance of a Department of Defense appropriate security clearance level (Confidential, Secret, and Top Secret). Information gathered, developed, analyzed, and produced under this PWS remains the property of the US Army and shall be protected from unauthorized or inadvertent modification, disclosure, destruction, or use. Prior to the arrival of any contractor employee to commence work under this contract at any government site, the contractor must provide advance notice to the government for visitor control purposes and verification of security clearance. Contractor employees are required to meet all annual security training requirements according to local policy.

3.4 Cybersecurity

The contractor shall ensure that all staff possess the required qualifications to perform work as required by the U.S. government, and that those qualifications are maintained during the life of the contract. The contractor shall be responsible for approving individual resumes to ensure appropriate assignment of personnel to meet the requirements set forth in DoD 8140. It shall be the sole responsibility of the contractor to staff their team properly and abide by the guidelines set forth in DoD 8140. All personnel holding administrative rights will be designated members of the

Cybersecurity workforce and must meet the additional certification and/or training requirements set forth in DoD 8140 prior to beginning work on the contract.

The contractor shall ensure that Cybersecurity is provided for IT IAW current federal, DoD and other relevant policies, procedures, and statutes, to include The Clinger-Cohen Act; DoD Instruction 8500.01, Cybersecurity; DoD Directive 8140.01, Cyberspace Workforce Management; DoD Instruction 8140.02, Identification, Tracking, And Reporting of Cyberspace Workforce Requirements; DoD Manual 8140.03, Cyberspace Workforce Qualification And Management Program; Army Regulation (AR) 25-1, Army Knowledge Management and IT; and AR 25-2 Army Cybersecurity. These regulations require active-duty military, DoD civilian, DoD consultants, and support contractor personnel performing work on sensitive Automated Information Systems (AISs) to be assigned to positions which are designated at one of three sensitivity levels per AR 380- 67: (Automated Data Processing- Level (ADP-I), ADP-II or ADP-III). The employing contractor will ensure individuals assigned to these sensitive positions have completed the appropriate access request forms.

Per AR 380-67: “DoD military, civilian personnel, consultants, and contractor personnel performing on unclassified automated information systems may be assigned to one of three position sensitivity designations (IAW Appendix K of AR 380-67) and investigated as follows”:

ADP–I: BI/SBI* or T5

ADP–II: DNACI/NACI** or T3

ADP–III: NAC/ENTNAC/NACI*** or T3/SAC

*Background Investigation/Special Background Investigation

**DoD National Agency Check with Inquiries/National Agency Check with Inquiries ***National Agency Check/Entrance National Agency Check/National Agency Check with Inquiries

3.5 Conflicts of Interest and Non-Disclosure of Proprietary Information

a) The contractor and each of its subcontractors and team members are prohibited from participating in the request for proposal preparation process for the PL ALTESS procurement, and performance of the resulting contract, in any capacity, including as a subcontractor or supplier at any tier. The following provisions additionally apply (to the Prime and all subcontractors and teaming partners).

b) The contractor agrees that if it assists in the preparation of non-developmental specifications or of work statements for a system or services under this contract, or assists in the development of acquisition strategies or evaluation criteria or otherwise provides acquisition support under this contract, it will not be allowed to furnish these items or services, either as a prime contractor, a subcontractor or as a consultant (FAR 9.505-2).

c) The contractor agrees that if it gains access to proprietary data of other companies, it will protect such data and it will not use such proprietary data in supplying systems or components in future competitive procurements (FAR 9.505-4).

d) In addition, the contractor agrees to protect the proprietary data and rights of other organizations disclosed to the contractor during performance of this contract with the same caution that a reasonably prudent contractor would use to safeguard highly valuable property. The contractor also agrees that if it gains access to the proprietary information of other companies, it will enter into an agreement with the other companies to protect their information from unauthorized use or disclosure for as long as it remains proprietary and refrain from using the information for any purpose other than that for which it was furnished.

e) The contractor agrees that it will not distribute reports, data or information of any nature arising from its performance under this contract, except as expressly authorized by the Contracting Officer or COR. This provision applies to all contractors, sub-contractors, and teaming partners even after leaving employment under this contract.

f) The contractor agrees that it will neither evaluate nor advise the government regarding its own products or activities. The contractor will objectively evaluate or advise the government concerning products or activities of any prospective competitors.

g) The contractor agrees that any processes, procedures, architecture, equipment configurations, technical documentation, technical specifications, workload and system metrics, facility information, data center capabilities, system and application capabilities and specifications, and ALTESS-specific knowledge shall not be disclosed during employment under this contract. This provision also applies to all contractors, sub-contractors, and teaming partners after employment under this contract has ended.

h) The contractor agrees that all contractors, sub-contractors, and teaming partners cannot disseminate nor leverage to any degree any Points of Contact, phone numbers, email addresses, nor any other non-publicly available information that was discovered while working under this contract. This provision also applies to all contractors, subcontractors, and teaming partners after employment under this contract has ended.

The contractor agrees that it will include the above provisions, including this paragraph, in agreements with teaming partners, consultants or subcontractors at any tier which perform services under this contract. The use of this clause in such agreements shall be read by substituting the word "teaming partner," "consultant," or "subcontractor" for the word "contractor” whenever the latter appears.

3.5.1 Personal Conflicts of Interest

In the course of performance pursuant to this PWS, contractor employees will be participating personally and substantially in duties that have a direct and predictable effect upon other non-Federal entities. The contractor agrees to use its best efforts to ensure such employees and others performing services under this contract avoid conflicts of interest or the appearance thereof.

3.5.2 Organizational Conflicts of Interest (OCI)

The contractor agrees to accept and to complete all requirements identified in this PWS and not to contract with other government contractors in such a way as to create an OCI. To avoid an organizational or financial conflict of interest and to avoid prejudicing against the best interests of the government, the contract may place restrictions on the contractor, its affiliates, chief executives, directors, subsidiaries, and subcontractors at any tier when placing orders. Such restrictions shall be consistent with FAR Part 9.505 and the clause entitled, Organizational Conflict of Interest and shall be designed to avoid, neutralize, or mitigate organizational conflicts of interest that might otherwise exist in situations related to the contract. Examples of situations that may require restrictions are provided at FAR Part 9.508. All contractor personnel directly associated with this contract will be required to sign a non-disclosure agreement that will be furnished at time of award of this contract. Subject non-disclosure agreements, once signed, are to be furnished to the Contracting Officer or designate. Any conflicts of interest or actions detrimental to the best interests of the government may result in immediate termination for the default of this contract.

3.5.3 Personal and Substantial

To participate personally means to participate directly. It includes direct and active supervision of the participation of a subordinate in the matter.

To participate substantially means that the employee's involvement is of significance to the matter. Participation may be substantial even though it is not determinative of the outcome of a particular matter. However, it requires more than official responsibility, knowledge, perfunctory involvement, or involvement on an administrative or peripheral issue. A finding of substantiality shall be based not only on the effort devoted to a matter, but also on the importance of the effort. While a series of peripheral involvements may be insubstantial, the single act of approving or participating in a critical step may be substantial. Personal and substantial participation may occur when, for example, an employee participates through decision, approval, disapproval, recommendation, investigation, or the rendering of advice in a particular matter. No personal services are required under this PWS.

3.5.4 Incidental Construction

a) “Solutions Based Contract” means a contract encompassing the ability to obtain a complete solution under one contract vehicle from the analysis of HW/SW implementations to ongoing operation support of an IT solution. This may include incidental construction as part of the total solution. Incidental construction services and materials shall be provided by the contractor when essential to the task performance.

Pursuant to FAR 22.403-1, Applicability, the Davis-Bacon Act will apply to this PWS. Pursuant to FAR 22.404-2(a), the applicable Davis Bacon wage rate determinations will be provided when Incidental Construction is used through a modification to the contract. This wage determination contains the prevailing wage rates for building construction near Radford, VA and/or at other locations deemed necessary to support this PWS. Additional wage determinations will be included as needed per task. Incidental construction will be reimbursable via the ODC CLIN. Actual labor costs, including indirect costs, IAW the Davis Bacon wage determination will be reimbursed.

Actual material costs, including indirect costs, will be reimbursed.

b) IAW FAR 36.511, the government shall have the right to take possession of or use any completed or partially completed part of the work. Prior to taking possession of or using any work, the Contracting Officer shall furnish the contractor a list of items of work remaining to be performed or corrected on those portions of the work that the government intends to take possession of or use.

c) As prescribed in FAR 52.246-12, Inspection of Construction, the contractor will maintain an adequate inspection system. All work shall be conducted under the general direction of the Contracting Officer and is subject to government inspection before final acceptance.

4. REQUIREMENTS AND TASKS

4.1 Objectives

The Government’s objective for this PWS is to acquire program and technical support services to assist the Product Lead, Acquisition, Logistics and Technology Enterprise Systems (PL ALTESS), and other designated agencies in the delivery of hosting and managed services to the Army, DoD, and Federal agencies. These services shall enable the continued operation and enhancement of critical IT infrastructure and applications. The work will include, but is not limited to, the following organizational areas: Operations, Cloud Management, Cybersecurity, Application Management, and Services Management. Support for all technologies listed in Section 1.4 Technology Baseline shall be provided across the organizational areas.

The contractor shall provide support for a standard, Monday-Friday work week with core hours 0900-1500 Eastern Standard Time. After hours support for critical outages and mission support requirements shall be supported. Contractors may be required to participate in on-call rotations during non-core hours. All contractors should be prepared to respond to the ALTESS Operations Center if contacted after hours for requested assistance. The ALTESS Operations Center contractors will support 24x7x365 staffing requirements that currently involves a first shift 0700- 1730, second shift 1230-2300, and third shift 2200-0830.

The contractor shall support all supported ALTESS networks, currently NIPR and SIPR, and the security clearance levels required will be defined in the DD-254.

The contractor shall be compliant with Department of Defense Manual (DoDM)

8140.03 Cyber Workforce Qualifications requirements for positions that are cybersecurity related and fall under DoDM 8140.03.

All staffing requisitions shall be filled within 60 calendar days from the date the requisition is given to the contractor. The requisition shall be considered filled on the day the contractor reports for duty.

This section of the PWS identifies the PL ALTESS functions and tasks by Functional Area: Operations, Cloud Management, Cybersecurity, Application Management, Services Management and specialized functions that the contractor will be responsible for. In addition, the contractor shall describe their corporate oversight and Quality Assurance/Quality Control methodology to meet the acceptable deliverable requirements identified in the Quality Assurance Surveillance Plan (QASP) and Contract Data Requirement Lists (CDRL). The contractor’s proposal shall also address in their staffing plan their general concept for supporting the contract base year and option years. Work will not be performed by contractor personnel for inherently-Governmental activities.

4.1.1 Task Area 1 – Operations

4.1.1.1 Data Center and IT Infrastructure Support

A Datacenter Cabling Technician is responsible for the installation and maintenance of installing and cabling network, server, and operational technology devices at any of the locations to which PL ALTESS provides service. The technician should adhere to Telecommunications Industry Association/Electronic Industries Alliance Standard TIA-942 while performing their work. The Datacenter Cabling Technician will also support the maintenance of the Operational Technology systems as part of a Datacenter Infrastructure Management Tool.

The contractor shall provide the following, but not limited to:

a) Install and remove network and server equipment

b) Install and remove, terminate, and test copper and fiber optic cabling.

c) Label and document all cabling installations.

d) Configure and install cable management systems, including racks, trays, and conduits.

e) Perform regular inspections and maintenance of cabling infrastructure.

f) Diagnose and resolve cabling issues, including signal loss, connectivity problems, and physical damage.

g) Replace or repair damaged cables and connectors.

h) Provide installation reports detailing the work performed, including cable types, lengths, and test results.

i) Provide maintenance logs documenting routine inspections and any corrective actions taken.

j) Provide incident reports for any cable issues encountered and resolved.

k) Update network diagrams and documentation reflecting current cabling infrastructure.

l) Install and configure Operational Technology systems, including power management, cooling systems, and security controls.

m) Ensure proper integration of Operational Technology systems with existing data center infrastructure management (DCIM) tools.

n) Label and document all installations and configuration to data center infrastructure management tools.

4.1.1.2 Facilities

Functions to be supported in this task area include heating, ventilation and air conditioning (HVAC), electrical, fire suppression, mechanical, building automation system controls and plumbing; and drafting of related acquisition documents for the Agency.

4.1.1.3 Network

A Network Administrator is responsible for the implementation and sustainment of both NIPR and SIPR switches, routers, firewalls, load balancers and network management tools. The Network Administrator role assists in the engineering, implementation, and sustainment of network devices supporting a variety of Commercial Off-The-Shelf (COTS) and Government Off-The-Shelf (GOTS) applications and databases.

The contractor shall provide the following, but not limited to:

a) Design, install, configure, and maintain network equipment, including routers, switches, firewalls, and load balancers including Cisco routers and switches, Palo Alto and Network Virtualization Platform (NSX) firewalls, and F5 load balancers.

b) Perform patch management services.

c) Develop and implement network security measures, including firewalls, intrusion detection/prevention systems, and Virtual Private Networks (VPN) to protect network infrastructure and data. Stay abreast of emerging security threats and implement mitigation strategies.

d) Vulnerability review and remediation.

e) Maintain Security Technical Implementation Guides (STIG) and network

Risk Management Framework (RMF) controls for the ALTESS environment to ensure compliance under RMF 2.0.

f) Assist in Cybersecurity and Financial Audits.

g) Perform Security Operations support.

h) Perform configuration Management Services.

i) Perform Certificate management.

j) Perform User account management.

k) Proactively monitor network performance, troubleshoot connectivity issues, and implement management tools to ensure optimal network uptime, performance, and stability.

l) Perform daily/weekly maintenance via log reviews.

m) Incident Response services to include denial of service, system outages, network connectivity, etc.

n) Develop and maintain comprehensive network documentation, including diagrams, configurations, and policies.

o) Provide technical support to users for network and connectivity issues.

p) Research and recommend new network technologies and solutions.

q) Develop Automated Solutions for manual efforts.

r) Participate in on-call rotation to provide after-hours support.

4.1.1.4 Virtualization

A Virtualization Administrator is responsible for management, maintenance, deployment, troubleshooting and support of physical and virtual servers. The Virtualization Administrator assists in the engineering, implementation, and sustainment of virtualized infrastructure supporting a variety of COTS and GOTS applications and databases.

The contractor shall provide the following, but not limited to:

a) Install, configure, and manage virtualization hosts, clusters, and resource pools including technologies such as VMware vSphere and vCloud director components, Elastic Sky X Integrated (ESXi) hosts, vCenter Server, and vSphere clusters. Manage and maintain virtual networking infrastructure, including vSphere Distributed Switches (vDS), port groups, vSAN, and VMware NSX-T.

b) Manage and maintain virtual networking infrastructure, including virtual switches, port groups, and distributed switches.

c) Perform patch management services.

d) Create, deploy, and manage virtual machines from templates and images.

Perform ongoing maintenance of virtual machines, including patching, updates, and performance tuning.

e) Allocate and manage virtual resources, including central processing unit (CPU), memory, storage, and networking. Monitor resource utilization and optimize allocation for optimal performance and efficiency.

f) Analyze capacity trends and plan for future growth of the virtualized infrastructure.

g) Vulnerability review and remediation.

h) Maintain STIG and network RMF controls for the ALTESS Environment, ensuring compliance under RMF 2.0.

i) Assist in Cybersecurity and Financial Audits.

j) Perform Security Operations support.

k) Perform configuration Management Services.

l) Perform Certificate management.

m) Perform User account management.

n) Proactively monitor virtualization monitoring tools to ensure the health and performance of the virtualized infrastructure. Analyze. performance data and troubleshoot performance bottlenecks.

o) Perform daily/weekly maintenance via log reviews

p) Incident Response services to include denial of service, system outages, network connectivity, etc.

q) Develop and maintain comprehensive documentation for the virtualized environment, including configurations, procedures, and policies.

r) Provide technical support to IT staff and users for virtualization-related issues.

s) Research and recommend new virtualization technologies and solutions.

t) Develop Automated Solutions for manual efforts.

u) Participate in on-call rotation to provide after-hours support.

4.1.1.5 Storage

A Storage Administrator is responsible for management, maintenance, deployment, troubleshooting and support of storage systems. The Storage Administrator role assists in the engineering, implementation, and sustainment of storage systems supporting a variety of COTS and GOTS applications and databases

a) Install, configure, and manage storage area networks (SANs), network-attached storage (NAS) systems, and other storage technologies. This includes storage arrays, disk shelves, fiber channel switches, and related HW and SW.

b) Perform patch management services.

c) Plan, provision, and allocate storage resources to meet the needs of applications and users. Implement and manage storage virtualization technologies to optimize storage utilization and flexibility.

d) Analyze storage capacity trends and plan for future storage needs. Make recommendations for HW and SW upgrades to meet growing storage demands.

e) Vulnerability review and remediation.

f) Maintain STIG and network RMF controls for the ALTESS environment ensuring compliance under RMF 2.0

g) Assist in Cybersecurity and Financial Audits.

h) Perform Security Operations support.

i) Perform configuration Management Services.

j) Perform Certificate management.

k) Perform User account management.

l) Perform daily/weekly maintenance via log reviews.

m) Monitor the performance and capacity of storage systems. Analyze performance data, identify bottlenecks, and implement optimizations to ensure optimal storage performance.

n) Incident Response services to include performance problems, connectivity issues, and HW failures, etc.

o) Develop and maintain comprehensive documentation for the storage infrastructure, including configurations, procedures, and troubleshooting guides.

p) Provide technical support to IT staff and users for storage-related requests.

q) Work with storage vendors to resolve issues, schedule maintenance, and stay informed about new storage technologies and product updates.

r) Research and recommend new storage technologies, solutions, and best practices to improve storage efficiency, performance, and security.

s) Develop Automated Solutions for manual efforts.

t) Participate in on-call rotation to provide after-hours support for critical storage issues.

4.1.1.6 Backup & Recovery

A Backup Administrator is responsible for management, maintenance, deployment, troubleshooting and support of backup and recovery systems.

The Backup Administrator role assists in the engineering, implementation, and sustainment of backup and recovery systems supporting a variety of COTS and GOTS applications and databases.

a) Design, implement, and maintain a comprehensive backup and recovery strategy aligned with business requirements and recovery objectives. This includes full, incremental, and differential backups for critical systems and data.

b) Perform patch management services.

c) Install, configure, and manage backup SW and HW, including backup servers, storage arrays, and tape libraries. Ensure optimal performance and capacity of the backup infrastructure.

d) Perform regular backup and recovery operations, including scheduling, monitoring, and verifying backups. Troubleshoot and resolve backup failures and performance issues.

e) Develop and execute recovery testing plans to validate the integrity of backups and ensure the recoverability of critical systems and data.

f) Perform data restoration operations for individual files, databases, applications, or entire systems as needed.

g) Vulnerability review and remediation.

h) Maintain STIG and network RMF controls for the ALTESS environment to ensure compliance under RMF 2.0.

i) Assist in Cybersecurity and Financial Audits.

j) Perform Security Operations support.

k) Perform configuration Management Services.

l) Perform Certificate management.

m) Perform User account management.

n) Perform daily/weekly maintenance via log reviews

o) Incident Response services to include denial of service, system outages, network connectivity, etc.

p) Develop and maintain comprehensive documentation for the backup and recovery processes, including configurations, procedures, and recovery plans.

q) Assist in developing and maintaining disaster recovery plans and participate in disaster recovery exercises.

r) Provide technical support to IT staff and users for backup and recovery related issues.

s) Research and recommend new backup and recovery technologies, solutions, and best practices.

t) Develop Automated Solutions for manual efforts.

u) Participate in on-call rotation to provide after-hours support for critical backup and recovery issues.

4.1.1.7 Operations Center

An Operations Center Administrator will be responsible for supporting 24x7x365 operations for IT Service Management (ITSM) and Tier 1 System Administration tasks for its functional areas that include Windows, Linux, Virtualization, Storage, Network, Backup, and Monitoring. Operations Centers Administrators Llog incidents, changes, and requests while also responsible for escalation to Tier 2 and Tier 3 support teams for issues not resolved.

Operations Center Administrators are the first point of contact for customers while also responsible for supporting administrative business functions for Services Management, Business Management, and other divisions within

ALTESS.

a) Perform Customer Service for internal and external trouble reporting and escalating inputs to various teams.

b) Actively monitor IT functional areas for health compute, storage, network, application, database and other functions.

c) Input, escalate, and track ITSM system incidents, requests, and changes.

d) Complete Tier 1 administrative tasks for various technology areas.

e) Perform patch management services.

f) Assured Compliance Assessment Solution (ACAS) review and remediation.

g) Maintain STIG Database, RMF controls for the ALTESS Microsoft

Structured Query Language (SQL) environment to ensure compliance under RMF 2.0.

h) Assist in Cybersecurity and Financial Audits.

i) Perform Security Operations support.

j) Perform configuration Management Services.

k) Perform Certificate management.

l) Perform User account management.

m) Perform daily/weekly maintenance via log reviews.

n) Incident Response services to include denial of service, system outages, network connectivity, etc.

o) Perform Application and Database Installation.

4.1.1.8 Continuity of Operations, Disaster Recovery

a) Support Disaster Recovery and COOP operations using scalable, enterprise solutions that leverage virtual technologies.

b) Conceptualize, design, engineer, build, provision and field data replication solutions based on system requirements. Design, deploy and support COOP solutions leveraging virtual technologies.

c) Sections 4.1.1.6.(a) – 4.1.1.6(c) will require support for technologies including the technologies listed in section 1.4 (Technology Baseline).

4.1.1.9 Desktop Support

Desktop Support will support standard desktop HW, peripherals, operating systems, network connectivity, mail and messaging applications, and office productivity tools. The Desktop Support Administrator role assists in the engineering, implementation, and sustainment of Windows Desktops supporting a variety of COTS and GOTS applications.

a) On-site Campus Support – End users receive assistance from support staff based at their on-site office locations.

b) Remote Support – Remote…