PWS CLASS compliance.docx

PERFORMANCE WORK STATEMENT (PWS)

CRYPTOLOGIC LOGISTICS AUTOMATED SUPPORT SYSTEM (CLASS) SOFTWARE MODIFICATIONS

28 April 2025

1. General: This is a non-personnel services contract to provide software modifications for the Cryptologic Logistics Automated Support System (CLASS). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1. DESCRIPTION OF SERVICES/Introduction: The contractor shall provide all personnel, equipment, supplies, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform software modifications as defined in this performance work statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract for the Cryptologic and Cyber Systems Division (AFLCMC/HNC) at Joint Base San Antonio-Lackland (JBSA-Lackland). The contractor must use software from the Air Force approved list of products and vendors to conform to JBSA-Lackland computer network standards. The server used for development must be STIG (Security Technical Implementation Guide) compliant. All compliance standards/direction will be provided by the Government.

1.2. Background: CLASS are multi-user personal computer-based software packages developed for the management of inventory and supportability needs. Leidos designed CLASS with the flexibility to adapt to almost any supply support concept of operation. CLASS provides automated, real-time capability to control and account for all categories of assets. The system’s characteristics are:

Terminology based on the standard Department of Defense Data Element Dictionary Commercial hardware and software used for the operating system Military Standard Requisitioning and Issue Procedure compliant LOGMARS (bar code) compatible Compatible with standard DOD logistics systems

1.3. Objectives: Add the requested functionality approved by the configuration control board as listed in para 1.4.1 CLASS Software changes.

1.4. Scope: Provide a new version of CLASS, develop functionality, perform installation of the software at AFLCMC/HNC and update user manual documentation.

1.4.1. CLASS software changes: Modify CLASS for the requested functionality approved by the CCB.

25-007 Security enhancements to meet risk management framework standards 25-008 Add long item description 25-009 Add Column sorting 25-010 RVP – Allow user to select document when multiples 25-011 Display “kill” message 25-012 Update Job monitor 25-013 Update EOD process 25-014 Add copy button to alternate ship address screen 25-017 Add CMOS shipment data to CLASS

1.4.3. Travel: Contractor will be required to travel to JBSA-Lackland, during the performance of this contract to attend meetings, install/test software updates, and provide training. Contractor is required to protect all Controlled Unclassified Information (CUI) they come in contact with during the course of this contract. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the program representative.

1.4.4. Monthly Status Reports: The contractor will provide monthly status reports the 15th of each month, or first business day after, per CDRL A001 for each system.

1.4.5. Software Test Cases: The contractor will provide software test cases/plans for any software modifications that need to be installed in the production environment at AFLCMC/HNC per CDRL A002 for each system.

1.4.6. Participate in Software Requirements Specification (SRS) and Software Design Document (SDD). Provide appropriate design documents per CDRLs A003 and A004.

1.4.7. Deliver the US Government Software Rights/Ownership for CLASS within 15 days of Government acceptance and/or the end of the Period of Performance of the contract by electronic or hard copy in accordance with CDRL A005.

1.4.8. Deliver new functionality, to include user manual per CDRL A006 no later than September 2026.

1.4.9. Period of Performance: The period of performance shall be for one (1) year of twelve (12) months.

1.5. General Information

1.5.1. Place of Performance: The work to be performed under this contract will be performed at contractor facility other than travel periods that may be required at government facilities at JBSA-Lackland.

1.5.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

Provides appropriate level of technical support, software fixes, or training timely manner to address system failures

Provide status updates monthly

1.5.3. Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, program representative and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor’s performance. At these meetings, the contracting officer will apprise the contractor of how the Government views the contractor’s performance and the contractor will apprise the Government of problems, if any, being experience. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.5.4. Key Personnel: No Key Personnel required; however, the contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to the daily operation of this contract.

1.5.5. Identification of Contractor Employees: All contract personnel attending meetings, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.5.6. Other Direct Costs: This category includes travel (outlined in 1.4.3) associated with training activities and visits to the Government facility.