PWS_VRV_IT Support.docx

09/01/2025/02/28/2031 performance work statement (pws) Range Management (RM) Launch and Test Range Systems (LTRS)

INFORMATION TECHNOLOGY (IT) SUPPORT

23 January 2025

1.0 Introduction: Work is to be accomplished for the Space Launch Delta 30 Range Management (SLD30/RM) and Space Launch Delts 45 Range Management (SLD45/RM) Program Offices. This work supports the business processes for the Launch and Test Range System.

2.0 Background: SLD30/RM and SLD45/RM are the Program Offices for the Unites States Space Force (USSF) LTRS enterprise at Vandenberg SFB, CA and Patrick SFB, FL performing technical interface coordination, test direction, integration and transition, and other systems engineering and acquisition services for sustainment, maintenance, and capability modifications to LTRS assets. SLD30/RM and SLD45/RM serves as the coordinator and liaison to SLD 30 and SLD 45 for all such projects, programs, and contracts throughout the life-cycle of all Eastern and Western Range (ER/WR) systems, subsystems, Line Replaceable Units (LRU), Hardware and Computer Software Configuration Items (HWCI/CSCI) and infrastructure categories such as communications.

3.0 Period of Performance:

f. Option Year Four: 09/01/2029-08/31/2030

g. FAR 52.217-8 09/01/2030-02/28/2031

3.1 General Transition Goals: Perform a smooth and orderly transition between the Successor and Incumbent without interruption of services IAW the PWS. An orderly transfer of current corporate knowledge of Information, Technology and operations is required to establish familiarity with local processes.

3.2 Transition Period: The transition period is from 01 September 2025 through 14 September 2025.

3.3 Transition Plan and Activities: The contractor shall provide a Transition Plan no later than five days after award, addressing all necessary actions to ensure transition goals are met to the maximum practicable extent for approval to the government. Upon government approval of transition plan and activities contractor shall coordinate with the Incumbent and the government before any transition efforts begin

4.0 Scope: Develop/Maintain enterprise business processes, using the Visual Requirements View (VRV) Applications. Provide IT Support, consisting of network administration, maintenance, software development/maintenance, application/software training, Automated Data Processing Equipment (ADPE) inventory, IT analysis, hardware/software procurement support, and audio/visual support and maintenance for RM range network sustainment at Patrick SFB (PSFB), and Vandenberg SFB (VSFB), and its mission partners. Support shall include: General IT Operations and Management Support, System Administration and Help Desk Support, and Software Development and Development of Database Applications. Provide the option to transition to a DOD approved IL5 Cloud Platform as a Service Capability.

5.0 General IT Operations and Management Support. Provide IT Management and Coordination to include; Site Management in Application Systems Analysis and Program Management. The Contractor Shall:

5.1 Ensure that all Patrick SFB (PSFB), and Vandenberg SFB (VSFB), IT systems/servers are maintained in compliance with the USAF Cyber Security and Standard Desktop/Server Configuration environments and coordinate with local base IT/Cyber Security personnel as required to ensure compliance.

5.2 Recommend system changes to the Government for approval as technology and systems evolve.

5.3 Execute the establishment and revision of data interfaces and office automation standards with SLD30/RM and SLD45/RM LTRS customers and other organizations within RM; and the design of interfaces and/or selection of products to transmit and receive data from contractors.

5.4 Coordinate with RM and other DOD agencies to implement IT solutions and strategies for inter-related systems.

5.5 Function as the unit Information System Security Officer (ISSO) and Cybersecurity Liaison for all systems hosted on the Host Base Network to include all NIPR-hosted laptops, desktops and servers.

5.6 Review and access AFI and guidance updates for Automated Data Processing Equipment (ADPE) security and integrate updates into computer systems security posture as required. Coordinate with the host base information security and assurance office and evaluate/implement necessary requirements.

Performance Standard:

a) IAW AFMAN 17-1203 - IT Equipment Custodian (ITEC) and Inventory of Hardware Assets

6.0 Cybersecurity Support

6.1 Provide new, or maintain, the Authority to Operate (ATO) and continuous ATO (cATO) A&A package in accordance with the Space Authorizing Official memo, “Required Artifacts for Space Risk Management Framework (RMF) Authorization Decisions. Review and analyze cybersecurity control compliance status to meet both ATO and cATO. Maintain ATO and cATO packages consistent with DoDI 8510.01 and all added guidance from the ISSM and AO. Artifact uploads must meet the published schedule for authorization creation and renewals. Cyber artifacts must meet AO requirements and delivered in the approved AO templates. Draft POA&Ms for non-compliant Cybersecurity controls. Develop and manage System Security Plans (SSPs) and provide any changes to the Information System Security Manager (ISSM) or designee. Provide technical input for updates and mitigations to POA&M items for ATO and cATO packages.

6.2 Apply cybersecurity services to secure data at all classification levels. Comply with DoD 8500 Series instructions, NIST SP-800 Series, Air Force Instruction (AFI) 10-701, and proper cybersecurity standards and procedures per AFI 17-130. Obtain COR approval for use of software or hardware not on the approved products list. Manage the security of classified and unclassified DoD information, Critical Program Information (CPI), and Controlled Unclassified Information (CUI) in Reference Libraries per assigned DoD Impact Levels.

6.3 Meet all RMF cybersecurity requirements on new and existing software platforms managed by the RM IT Support contract. Perform risk assessments and vulnerability mitigations. Provide Cybersecurity recommendations including, but not limited to, the development of Cybersecurity policies, procedures, strategies, processes, and plans, as well as the translation of the strategic Cybersecurity posture into specific Cybersecurity requirements. Manage future Cybersecurity architecture, roadmaps, cyber risk posture and cyber hygiene.

6.4 Perform Cybersecurity Program Assessment. Assess RM IT Support system design requirements, topologies, and non-compliant cyber controls for cybersecurity engineering analysis and recommend solutions, mitigations, alternatives, or corrective actions. Develop POA&M reports and deliver to the Government Information System Security Manager (ISSM) and Chief Information Security Officer (CISO). Assess and verify that Cybersecurity requirements are addressed, at an acceptable level of risk. Assessments must confirm RM IT Support systems comply with the assigned Confidentiality, Integrity, and Availability (CIA) levels. Support the Cybersecurity program for all information systems identified in the RM IT Support Authorization Boundaries that are operated and maintained under this contract per Cybersecurity compliance documents.

6.5 Develop RM IT Support Incident Response Plan. Participate in incident response exercises, deliver incident responses, and coordinate root cause assessment and recommend solutions, mitigations, alternatives, or corrective actions to the Government ISSM and CISO.

6.6 Analyze and deliver proposed component level or higher changes to the Government ISSM. Develop and perform test conductor activities to test delivered system changes and validate cybersecurity compliance. Use NSA and DISA hardening guidance to configure hardware and software.

6.7 Apply Government approved systems engineering processes for any Cybersecurity required changes to system configuration.

6.8 Provide evidence of current ATO/cATO or any additional information required for connectivity to the NIPR/SIPR enclaves to the Government upon request. This includes whitelisting RM IT Support web sites and servers.

6.9 Perform credentialed Cybersecurity scans, vulnerability and compliance scans, for operational systems assigned to RM IT Support as requested by Government. Make results of scans available to the Government.

6.10 Use Government approved penetration testing tools. All penetration testing must be approved by the Government ISSM, CISO, or both prior to start.

6.11 Perform GENADMIN, TASKORD, OPORD, FRAGORD, and other 5-paragraph orders for all systems per Government direction. Apply security patches to RM IT Support information systems as directed. Evaluate RM IT Support information systems and create a schedule/plan to test and validate security patches prior to applying to the operational systems.

6.12 Support Cybersecurity audit activities as requested by the Government.

6.13 Develop and conduct annual systems specific Cybersecurity training for RM IT Support team members. Make sure that all personnel requiring access to any DoD information systems maintain currency with Advanced Distributed Learning System (ADLS) DoD Cybersecurity training

7.0 System Administration and Help Desk Support. Provide System Administration and Support services, operation and maintenance (including inputs to the Government on items needing to be procured; and replacement and integration of hardware and software as needed) of the SLD30/RM and SLD45/RM system servers, user computers, docked/traveling laptops, hand-held devices/mobile phones and SLD30/RM and SLD45/RM owned networking infrastructure components. The Contractor Shall:

7.1 Perform operations and maintenance on the system to ensure a system availability is maintained at or above 90 % level.

Performance Standard:

a) IAW: TO 00-33A-1106 - Network Management Mission Areas, Base Area Network Management, and Geographically Separated Units Virtual Private Network (GSU VPN)

b) AQL: Maintain an email, web, file/print, and network infrastructure availability rate of 90% or above

c) AQL: Respond immediately and begin restoral actions within one (1) hours of the reported failure

7.2 Perform and monitor system administration functions on the organizations’ workstations (which includes various hardware configurations such as tower, mid-tower, micro and mini) and laptops to include power up and shut down, loading and configuring software or systems, monitoring telecommunications, and performing scheduled system backups.

7.3 Perform and monitor system administration functions on the organization’s virtual and physical data center servers which includes the VRV Web, SQL and file servers.

7.4 Perform System Administrator tasks including server builds, hardware refreshes, power management, software configuration, patch management, troubleshooting, monitoring network connectivity/communications, performing scheduled system backups and file, database, and server restorations and administering the virtual environment.

Performance Standard:

a) 99% of patches are successfully implemented within 3 days of receipt of Information Assurance Vulnerability Management (IAVM) orders, the remaining 1% are successfully implemented within 7 days of receipt of IAVM. Government emergency patching will be successfully implemented within 1 day of receipt of IAVM.

7.5 Perform virtualization tasks including technical refreshes, hardware refreshes, patch management, server builds, migrations, backups and recovery, virtual network device management/configuration, license management, resource management, planning, disaster planning/recovery, business continuity planning/management, testing and research, auditing, and incident management.

7.6 Provide help desk support for the customer and their authorized mission partners, including entering, updating and closing all support requests in the VRV and REMEDY trouble ticket databases, troubleshooting problems, and/or providing guidance via telephone and/or in person. Products supported by the help desk include, but are not limited to, computers, electronic equipment, software applications, audio/visual requests, video telecommunications equipment and user access to authorized DoD websites and data shares. Help desk requests can be submitted via email, instant messaging, and calling the help desk phone number. The contractor’s help desk personnel shall interface with local Communication Squadron personnel and INOSC personnel to enter, status and update change requests to network configurations, and troubleshoot network related issues such as, but not limited to, policy updates/changes, routing issues, adding servers/workstations, DNS, DMZ, DISA white lists, and PKI requirements.

Performance Standard:

a) 95% of trouble tickets resolved within 3 days of receipt, remaining 5% resolved within 30 days.

b) Notify users upon trouble resolution within 15 minutes of completion.

7.7 Provide escort to base personnel and other contractors who must gain access to equipment/server rooms, communications closets, etc. within the SLD30/RM and SLD45/RM building/office areas.

7.8 Develop documentation to define computer operations and maintenance procedures. Define procedures for the control, reception, storage and retrieval of data and recommend and implement approved changes to IT operating procedures based on revisions in AFI and guidance.

7.9 Provide inventory management of computer equipment, Commercial of the Shelf (COTS) Software Registrations, and COTS software licensing and assume the responsibility of Automated Data Processing Equipment (ADPE) Custodian for the SLD30/RM and SLD45/RM organizations.

7.10 Submit prioritized lists of hardware and software items to be procured by the government, install and integrate hardware and software as required to maintain the network solution.

7.11 Establish and maintain configuration control of user workstations and servers. Develop and maintain document libraries on ADPE Hardware and COTS software manuals and track the distribution of manuals to associated government organizations and Network/Application Support Personnel as required.

8.0 Software Development and Development of Database Applications. Develop and maintain web-based Intranet/Extranet information sources to provide on-base and off-base access to data that is essential in executing the LTRS mission. The Contractor Shall:

8.1 Build and maintain all web applications to run on current and approved USAF Standard Desktop/Server Configuration environments and utilize standard HTML authoring applications to create web pages.

8.2 Be responsible for the design and development of dynamic and static web interfaces using graphical development applications. Applications utilized by development team may include Microsoft Visual Studio variants, Microsoft Team Foundation Server, Microsoft SQL Server, Eclipse IDE, Adobe Photoshop, and others as required.

8.3 Implement all web applications to require CaC authenticated access through secure socket layers, using Federal Information Processing Standards (FIPS) approved encryption algorithms, and will be served on USAF standard server configurations, e.g. Windows Servers running Microsoft IIS.

8.4 Implement all web applications served outside of the AF Non-Secure Internet Protocol Router (NIPRnet) in accordance with DoD policies, which require web servers be located in the DMZ, and develop reporting and data presentation modules from various data sources as identified by SLD30/RM and SLD45/RM.

8.5 Work with Database Administrators and end-users in the design of interactive interfaces, and assist the IT staff in testing; evaluating and implementing new and emerging Web based server services and technologies.

8.6 Maintain, enhance, and deploy the VRV application software to resolve problems, add features, and add item types as required by SLD30/RM and SLD45/RM.

8.7 Develop and maintain databases to support the VRV application using USAF approved and supported Microsoft SQL Server versions. Develop web interfaces, business logic, and the required database queries to access and maintain the stored VRV application data in support of management, customer, and software development requirements. The Contractor Shall:

8.7.1 Identify, recommend, develop, and test enhancements to the VRV application and the VRV processes in support of their mission and/or customers.

8.7.2 Integrate system modifications recommended by the working groups and from other VRV using organizations.

8.7.3 Maintain the software code repository, system documentation, and tracking of issues and requirements for implementation.

8.7.4 Develop, modify, and administer process state diagrams, states, actions, permissions, and user accounts.

8.7.5 Enhance VRV to support existing and future types and other operational requirements as required/needed.

8.7.6 Support the deployment and use of VRV at other United States Space Force (USSF) sites as required to process SLD 45 (Eastern Range) and SLD 30 (Western Range) requirement records, and document processing and deficiency records. Support the use of the VRV application to implement viewing, editing, and action processing of new types of data items, which require process management and/or revision tracking.

8.7.7 Provide administration and support of the VRV server and associated applications (Operating system, SQL database, and developed applications).

8.7.8 Support and prepare agendas and minutes as required for the VRV Working Groups. Contractor format is acceptable.

Deliverable:

D002 – VRV Working Group Minutes

8.7.9 Provide telephonic, on-site (as required), and help desk support for VRV and its associated item types for all SLD30/RM, SLD45/RM and LTRS customers

8.7.10 Develop, implement, modify and support VRV training for SLD30/RM, SLD45/RM and LTRS customers as required. Training is to be delivered Quarterly/Biannually by various means to include in-class, CBT, audio visual, manuals, FAQs, newsletters, digests, etc. Training for Vandenberg SFB, and Peterson AFB personnel will be provided both on-site at those locations and at Patrick SFB as required by SLD30/RM and SLD45/RM.

8.7.11 Provide engineering, programming, and analysis services to include: the design and development of dynamic and static web interfaces using server-side scripting (e.g. Asp, ASP.net, JAVA, etc.), and client-side scripting using HTML, JAVA, JavaScript and VB Script.

8.7.12 Optimize web applications to run on USAF approved Standard Desktop Configurations and optimize server applications to run on USAF Standard Server configurations. Web applications will interface with various data sources including Oracle, SQL Server, MS Access, JSON/XML APIs, etc., as mission dictates.

8.7.13 Interface with database administrators and end-users in the modeling, normalizing, and tuning of data structures. This area of support will have the oversight of designing, developing, documenting, and implementing web based applications.

8.7.14 Develop and provide user training and support in the use of COTS software and applications developed for SLD30/RM and SLD45/RM as required. The format of training will be as required, but can include instructor-led classes, one-on-one assistance, development of computer based training (CBT), and the preparation of tutorials and user guide documents. Training locations may include Patrick SFB, Vandenberg SFB, and Peterson AFB.

8.8 The following requirements, practices, and procedures apply for software development;

8.8.1 Implement DevSecOps principles for all software development performed by RM IT Support. For the purposes of this PWS the term software development refers to the creation or acquisition of new software, the modification of existing software, or the maintenance of existing software. Make sure that all new software, major upgrades, or modifications to existing software follow AFI 63-101/20-101; AFI 20-101/63-101; and SLD45I 91-701 (also ref. DoD SW Modernization Strategy and DoD Enterprise DevSecOps Reference Design). The RM IT Support contractor shall be responsible for performing all tasks necessary to fulfill this requirement to include cybersecurity and the delivery of technical reports to the Government upon formal request.

8.8.2 Perform Corrective, Adaptive, and Perfective (CAP) software maintenance activities as defined below:

8.8.2.1 Corrective maintenance refers to the diagnosis and correction of latent errors in the operational code.

8.8.2.2 Adaptive maintenance refers to the modification performed to keep software usable when running in a new system environment (i.e., a new hardware platform).

8.8.2.3 Perfective maintenance refers to the modification of software after operational acceptance of a Range asset to improve its performance or maintainability.

8.8.3 Provide Unlimited Rights for the source code for developed software or Commercial Off-The-Shelf (COTS) software modified exclusively for LTRS, consistent with AFI 63-101/20-101, DAFMAN 17-1203, and SMCI 63-104.

8.8.4 Integrate cybersecurity into all RM IT Support software development using guidance contained in AFI 17-130 and AFI 17-101.

8.8.5 Perform cost-benefit-analysis and life-cycle-cost trade-offs between recommended software development approaches. Provide analysis for the software development approach approval.

8.8.6 Develop and maintain the Software Continuity of Operations Plan (COP) and subsequent processes, procedures, and capabilities specifically for software version builds, images, source code, associated data-backup, and recovery media.

8.8.7 Manage software licenses, subscription, maintenance, and agreements required for software development and maintenance on RM IT Support equipment. At a minimum, the Contractor shall:

8.8.7.1 Conduct and maintain current inventory of all Government-owned licenses, subscriptions, and maintenance agreements to include renewal dates and cost estimates for renewal or upgrades. Make this information available to the Government.

8.8.7.2 Provide detailed justification to the Government for the purchase of any subscriptions or maintenance agreements necessary to support and sustain the operational system.

8.8.7.3 Present a cost-benefit analysis comparing the development of in-house expertise with the purchase of subscription and maintenance agreement costs if COTS vendor training is available.

8.8.7.4 Make sure that any license containing a built-in expiration date is renewed and updated before expiration to prevent system lockouts, shutdowns, or operational system impacts.

8.8.7.5 Make sure that all legal requirements for the authorized use, distribution, and copying of software products are documented, monitored, and audited to make sure compliance, including ensuring that software user manuals, test procedures, training documents, etc. (including points of contact, processes, or procedures) are continually monitored for verification of legal compliancy.

8.8.7.6 Obtain Government approval prior to purchasing software.

8.8.8 Dispose of or redistribute excess or old versions of COTS software according to licensing agreements.

8.8.9 Conduct and maintain a detailed inventory of all software programs and applications. Make a list of this information available to the Government. Maintain physical and logical source lines of code counts for all developed software.

8.8.10 Set up a monitoring capability to efficiently track the status of reported RM IT Support deficiencies discovered in vendor or in-house developed products.

8.8.11 Perform Urgent Software Actions (USAs) to resolve software deficiencies as directed by the Government. Use either the USA process or software release process to carry out GENADMIN, TASKORD, OPORD, FRAGORD, and other 5-paragraph orders, Information Assurance Vulnerability Alert (IAVA), Zero-Day Vulnerabilities and anti-virus patching.

9.0 OPTION CLIN: Transition to cloud platform plan. Develop and provide a plan for the transition to a DoD approved IL5 Cloud Platform as service capability. The Contractor Shall:

9.1 The transition Plan to the Cloud Platform Services will include;

9.1.1 Migration of VRV from dedicated hardware at PSFB to a cloud-based solution to ensure continuous VRV availability legacy stored data and services at all locations.

9.1.2 Migration of the VRV capability from dedicated hardware to a Cloud-based solution and provide a proposed schedule to include the following actions:

9.1.2.1 Recommendation of a DoD-approved Cloud-hosting provider

9.1.2.2 Provide Business Case Analysis on the Cloud Migration.

9.1.2.3 Migration planning from dedicated hardware to Cloud-hosting.

9.1.2.4 Test planning to include any period of parallel operations.

9.1.2.5 Cybersecurity planning to include the System Categorization, Control Selection, negotiation of Service Level Agreements with Cloud-provider for inherited security controls, Control Implementation, Control Assessment, Control Validation, Authorization to Operate (ATO) submission to SLD30/RM and SLD45/RM Cyber representatives.

9.1.2.6 User transition to Cloud-based capability to include validation of users transitioned to Cloud access.

9.1.2.7 Planned program management support to ensure that the requirements of this PWS are accomplished, including participating in meetings, reviews, and briefings associated with this requirement, as related to overall program administration and/or management during cloud transition.

9.1.2.8 Responsibility for IT Systems, Cloud Migration and Administration, and Software Development for SLD30/RM and SLD45/RM requirements.

9.1.2.9 Provided IT resource plan to support transition to Cloud capability.

10.0 Work Requirements: The contractor shall provide IT resource support, and integration services (support personnel), software, and hardware as required in the areas of computer programming/analysis and information management specialist areas. Establish, manage, coordinate and conduct VRV Working Groups. The following are some characteristic metrics to aid in estimating services that will be required in the performance of this contract:

11.0 The following Service Summary (SS) identifies the performance objectives and performance thresholds for critical tasks associated with providing support services for SLD30/RM and SLD45/RM. The SS and the contractor’s Quality Control Program (QCP) (see Para. 11.2.) provide information on contract requirements, and the expected level of contractor performance. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success. These do not excuse the contractor from performance of other responsibilities identified in the PWS. The CO can change the SS items at any time during the life of the contract. SS’ can be added or deleted, and performance thresholds raised or lowered. The CO shall notify the contractor in writing of any changes by a modification to the contract.

Services Summary

Maintain Network Availability Rate of 90%

Patch Management

b) Notify users upon trouble resolution within 15 minutes.

Monthly Status/Technical Report (MSTR)

b) No more than 1 monthly report per year returned for re-work

12.0 Initial Business and Technical Meeting: Within ten (10) business days following the award date, contractor shall meet with the Client to review goals and objectives of this requirement, discuss technical requirements, and review transition plans. The contractor shall take meeting minutes in contractor format and provide to the COR.

12.1 Unsatisfactory Work: Performance by the contractor to correct defects identified by the Government as a result of quality assurance surveillance and by the contractor as a result of quality control, shall be at the contractor’s own expense without additional reimbursement by the Government. Unless otherwise negotiated, the contractor shall correct or replace all non-conforming services or deliverables not later than five (5) workdays after notification of non-conformance.

12.2 Quality Control Plan (QCP): The contractor shall provide and maintain a Quality Control Plan (QCP) that contains, as a minimum, the items listed below to the COR and PM for acceptance not later than ten (10) calendar days after award. The PM will notify the contractor of acceptance or required modifications to the plan. The contractor shall make appropriate modifications and obtain acceptance of the plan within thirty (30) calendar day from the date of award.

12.2.1 The QCP shall include the following minimum requirements:

12.2.1.1 A description of the inspection system to cover all major services and deliverables. The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, frequency of inspections, and the title inspectors.

12.2.1.2 A description of the methods to be used for identifying and preventing defects in the quality of service performed.

12.2.1.3 A description of the records to be kept to document inspections and corrective or preventive actions taken.

12.2.1.4 All records of inspections performed shall be retained and made available to the government upon request throughout the task order period of performance, and for the period after task order completion, until final settlement of any claims under this task order.

13.0 Quality Assurance: The Government will evaluate the contractor’s performance of this requirement. For those tasks listed in the Services Summary Table (PWS paragraph 10), the COR will follow the method of surveillance specified in this PWS. The COR will record all surveillance observations. When an observation indicates defective performance, the COR, will require the contractor manager or representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation. It acknowledges that the contractor has been made aware of the non-compliance. Government surveillance of tasks not listed in the Services Summary Table may occur during the performance period of this task order or by methods other than those listed in the Services Summary Table (such as provided in the Inspection of Services clause) Such surveillance will be done according to standard inspection procedures or other task order provisions. Any action taken by the CO as a result of surveillance will be according to the PWS requirements.

14.0 Place(s) of Performance: Performance locations shall be at Patrick SFB, FL and Cape Canaveral Air Station, FL, and Vandenberg SFB, CA.

14.1 Provide an OPTION for IT performance location at Peterson AFB, CO.

15.0 Hours of Work: Normal work hours will be eight hours a day, five days per week, Monday through Friday excluding holidays. The Contractor workday schedules will be established to begin and end between 0630EST and 1800PST, all IT support work is to be conducted on site and telework is not authorized.

16.0 Federal Holidays: The contractor shall be in observances of federal holidays for this contract. Accordingly, the Government will not be billed for such holidays, except when services are required by the Government and are performed on a holiday. Holidays in addition to those reflected in this contract, which are designated by the Government, will be billable provided the assigned Contractor employee was available for performance and was precluded from such performance. The following days are contract holidays:

e. Junteeneth 18 June

17.0 Extended Hours: Special Technical Requirements such as testing of programs and database releases may require additional support after normal business hours to avoid impacts on daily operations.

18.0 Personnel Qualifications: Contractor personnel supporting this effort shall:

18.1.1 Have effective written and verbal communication skills in English.

18.1.2 Software Programming: The contractor’s software programming personnel assigned to this effort in support of Section 8.0 shall possess a Bachelor’s degree or higher in Computer Science and a minimum of 5-7 years of programming experience, most preferably with experience in the technology areas described in this PWS.

18.1.3 System Administration, Network Administration, and Information Assurance: These functions shall have at least one individual with a minimum of 5-7 years of experience. A Bachelor’s degree or higher in Computer Science for at least one of these individuals is desired. Cybersecurity, Cyber IT, Software Engineering, Cyber Enablers, Cyber Effects, and Data/AI roles identified within DoDM 8140 must meet cyberspace workforce Foundational qualification requirements within 9-months of being assigned into the role and Residential qualification requirements withing 12-months of being assigned into the role, per DoDD 8140.01, DoDI 8140.02, DoDM 8140.03 or current DoD Cyberspace Workforce Qualification and Management Program at the basic/intermediate/advanced work role level. Information Systems Security Engineer’s (ISSEs) and Information System Security Officer’s (ISSOs) are mandated to meet the “Advanced” level (541) Vulnerability Assessment Analyst and (612) Security Control Assessors roles identified within DoDM 8140 and AFMAN 17-1303 paragraph 3.2.9.

18.1.4 Program Management: The contractor’s program manager shall possess a Bachelor’s degree or higher and have a minimum of 5-7 years of experience leading similar efforts. The individual performing this function can do so along with other functions dictated under this PWS, if desired and qualified.

18.1.5 General IT Operations and Help Desk Personnel: The General IT Operations and Help Desk Personnel performing this function shall possess a minimum of 3-7 years of experience.

18.1.6 Government Furnished Resources: The government will provide workstations, phones, personal computers, and other typical office supplies for the duration of this task.

19.0 Government Furnished Equipment (GFE): For on-site support, the Government will provide workspace, computer hardware, telephones, reproduction services, and routine office supplies necessary to perform the task identified in this PWS. FAR 52.245-1.

20.0 Government Furnished Information (GFI): The Government will provide software necessary to perform the task identified in this PWS. The contractor will follow standard security policy and procedures while handling all GFI. This security policy will be tailored to meet any requirements directly affected by the GFI security policy.

21.0 Travel: Travel may be required to fulfill the requirements of this task. The contractor shall ensure that the requested travel costs will not exceed what has been authorized in the task order. Contractor incurred actual expenses resulting from Government directed travel are cost reimbursable but are limited by the Government Joint Travel Regulations (JTR) and must be pre-approved by the COR.

22.0 Estimated travel of one roundtrip annually to Vanderburg SFB, CA for one week duration each contract year.

23.0 Workload History: Historical records from previously performed similar work are provided as a guideline to assist offerors in preparing quotes. This estimate is the Government’s current workload and is not intended to be binding on either party or to be the only possible solution to the requirements. However, because the current/typical workload requires prioritization of these resources while other work is stretched out, it would be viewed as very high risk to carry less than this level of staffing.

24.0 Privacy Act: The contractor shall ensure that employees assigned to this task understand and comply with DoD Regulation 5400.7/Air Force Supplement, DoD Freedom of Information Act Program, and AFI 33-332, Privacy Act Program. These directives set policy and procedures for the disclosure of records to the public and for making, handling, transmitting, and safeguarding Controlled Unclassified Information (CUI) IAW DODI 5200.48. In addition, they set guidelines for collecting, safeguarding, maintaining, using, accessing, amending, and disseminating personal data kept in systems of records.

25.0 Clearances: Contractor personnel shall possess, at time of award, a current SECRET (S) clearance based on a National Agency Check (NACLAC) completed within the last ten (10) years. Specific security details for personnel associated with this contract. The Contractor shall submit completed clearance packages within ten (10) calendar days of identification of any increased security requirements. The contractor is governed by DOD 5220.22S, COMSEC Supplement to the Industrial Security Manual.

26.0 Monthly Report: Each monthly report shall be due on the tenth (10th) business day following the close of the calendar month. The report shall be submitted to the Contracting Officer, Program Manager and Contracting Officer Representative (COR). Contractor format is acceptable.

27.0 Monthly Status/Technical Report (MSTR): The contractor shall provide a MSTR for each task that describes the major activities accomplished during the month. The report shall list the individual names of personnel who worked on each task. The MSR should also include any current or anticipated problems and briefly summarize the activity planned for the next reporting period. A copy of the monthly report shall be provided to the government Program Manager no later than the 10th workday of every month. The contractor shall identify and report all program management actions in the MSTR and additional information as requested by the government. This report shall be delivered to the COR, and contain the following information:

a. Brief description of requirements

b. Brief summary of accomplishments during the reporting period and significant events regarding the task order

c. Any current or anticipated problems and the resolution

d. Summary of all major events and other pertinent information

e. Summary of associated travel completed

f. Summary of planned travel

g. Brief summary of activity planned for the next reporting period

h. Summary of personnel compliance with 8570.01-M requirements.

Standard:

100% of reports delivered timely No more than 1 monthly report per year returned for re-work

28.0 Other Reports: The contractor shall write quick-look, interim, and final test reports, investigation and study reports, travel reports, and conference minutes as required. Contractor format is acceptable.

29.0 Phase Out: The contractor shall develop a “Phase-Out Plan” to facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor/government personnel at the expiration of this task order. The contractor shall provide a Phase-Out Plan NLT ninety (90) calendar days prior to expiration of the task order. The contractor shall identify how it will coordinate with the incoming and or government personnel to transfer knowledge regarding the following: project management processes, points of contact, location of technical and project management documentation, status of ongoing technical initiatives, appropriate contractor to contractor coordination to ensure a seamless transition, transition of key personnel, identify schedules and milestones, identify actions required of the government, establish and maintain effective communication with the incoming contractor/government personnel for the period of the transition via weekly status meetings.