Draft PWS - Human Performance Assessment and Management Software Support Services - 3Aug26.docx

PERFORMANCE WORK STATEMENT (PWS)

Human Performance, Assessment, and Management Software Support Services United States Army John F. Kennedy Special Warfare Center and School (USAJFKSWCS) Part I General Information

1. GENERAL: This is a non-personal services contract to provide support services for the Human Performance, Assessment and Management Software platform located on the Government network. 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. The Contractor, in turn, shall be accountable to the Government for Contractor or subcontractor personnel.

1.1. Description of Services/Introduction: The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform software license, maintenance, technical support, training of users, overlords, basic administrators, operational administrators and periodic customization for , as defined in this Performance Work Statement (PWS), except for those items specified as Government furnished property and services. The Contractor shall perform in accordance with (IAW) the terms and conditions of the contract and consistently with the established standards in this PWS and contract.

1.1.1. Program Goals and Desired Outcomes: The Contractor shall sustain, optimize, and modernize the USAJFKSWCS force generation mission: the assessment, selection, training, and qualification of Army Special Operations Forces across training pathways comprising five to eight qualification courses each, across thirty-eight configured modules and training support for the 12 non-configured modules. The Government-selected software platform is the system of record for human performance data across the ARSOF training enterprise.

In accordance with Department of War direction to invest in warfighter capability platforms — including the Secretary of War memorandum “Directing Modern Software Acquisition to Maximize Lethality” (March 2025), the “Artificial Intelligence Strategy for the Department of War” and enforcement of the DoD Data Decrees (January 2026), and the “Transforming the Defense Acquisition System into the Warfighting Acquisition System” memorandum (November 2025) — this contract continues the modernization trajectory for human performance data modernization. The requirements in this update sustain that momentum within the existing resourcing structure.

1.1.2. Network Environment:

A successful solution shall operate on the SOCOM Information Enterprise (SIE) NIPR environment and shall demonstrate the ability to scale to the SOCOM SIPR environment. All capabilities delivered under this PWS shall fully support the Government in maintaining the system’s Authority to Operate (ATO) and shall use tools and components from the approved SIE/SOCOM software baseline. Any capability requiring new accreditation action shall be identified to the Government in writing with schedule and cost impact prior to implementation.

1.1.3. Interoperability and API Integration:

Consistent with the DoD Data Decrees requirement for automated, externally accessible, machine-readable data interfaces built on non-proprietary technologies, the Contractor shall:

1.1.3.1. Army Vantage. Develop and maintain documented Application Programming Interface (API) capability between the system and Army Vantage, sufficient to support bidirectional exchange of student demographic, status, and performance data elements defined in the Government data dictionary, using EDIPI/DoDID as the join key.

1.1.3.2. Maven Smart System. Develop and maintain documented API capability to expose Government-designated system data assets to the Maven Smart System ecosystem in accordance with USSOCOM and Department of War data-sharing direction, subject to Government-approved interface control documentation, classification/handling constraints, and the availability of Government-provided Maven ecosystem access.

1.1.3.3. IPPS-A. Develop automated personnel data feeds from IPPS-A (Integrated Personnel and Pay System – Army) into the Student Management module from structured data feeds supporting IPSS-A integration for personnel demographic records, completions, and daily management of personnel assigned to a course or USAJFKSWCS, subject to Government-provided interface specifications and authorization.

1.1.3.4. Approved course systems. Accommodate APIs and/or data upload capability between the system and existing approved data management systems (e.g., SWMG systems for the 18D MOS) to minimize manual data entry.

1.1.3.5. Federated data catalog. Publish interface specifications and data asset descriptions in a format suitable for inclusion in the Department's federated data catalog, delivered as contract deliverables with Technical Data - Unlimited Rights in accordance with DFARS 252.227-7013.

1.1.3.6. All interfaces shall be documented in Interface Control Documents (ICDs) sufficient for third-party integration, consistent with Modular Open Systems Approach (MOSA) direction.

1.1.3.7. Enable connection with an approved and Government-provided SOCOM networked Artificial Intelligence (AI) platform.

1.1.4. Identity, Access, and Data Standards:

1.1.4.1. CAC-enabled login for all user access; username/password-only authentication is not authorized for standard user roles.

1.1.4.2. Use of the DoD ID Number (DoDID/EDIPI) as the primary key for all student records within the data system. The system shall eliminate the use of SSNs as active identifiers, utilizing secure encryption methods for any required historical SSN data mapping to connect legacy student records, thereby ensuring compliance with policy governing the reduction, masking, and elimination of SSNs in DoD Instruction (DoDI) 1000.30, "Reduction of Social Security Number (SSN) Use Within DoD" (incorporating Change 2, November 30, 2022), Army Regulation (AR) 25-22, "The Army Privacy Program," and policies such as Army Pamphlet 600-8-14.

1.1.4.3. Audit logging of system activity by user, retrievable by Government administrators, retained in accordance with Army records management requirements.

1.1.4.4. Compliance with Department of War cybersecurity mandates for Controlled Unclassified Information (CUI), including NIST SP 800-171 safeguarding requirements consistent with CMMC Level 2, given the sensitive human performance and psychological data managed in the system. The Contractor shall provide documentation demonstrating compliance with these standards as a condition of contract performance.

1.1.4.5. Permission roles restricting access to psychological assessment data and Personally Identifiable Information (PII) to authorized users only, consistent with applicable Department of War privacy regulations and PWS Section 1.6.6.

1.1.5 Platform Identity:

The Contractor shall deliver, as a configuration and branding update , a SOF-enterprise-specific platform identity for the USAJFKSWCS instance, to include Government-approved naming, visual identity, and terminology alignment with ARSOF training enterprise conventions. All branding elements, naming conventions, and associated configuration artifacts developed for the Government instance shall be delivered with Unlimited Rights in accordance with applicable DFARS clauses (e.g., DFARS 252.227-7014 / 252.227-7013). This requirement establishes a Government-distinct platform identity for the SOF enterprise and shall not degrade module functionality or interoperability.

1.1.6 User Experience / User Interface Modernization:

The Contractor shall execute a UX/UI modernization of the Government instance , prioritized with and approved by the Government, to include: modernized dashboard visual design; simplified navigation across the thirty-eight configured modules; role-tailored landing views for cadre, unit staff, and command users; and accessibility compliance with Section 508. Modernization shall be delivered incrementally through the Government-approved update and release process, with Government acceptance testing prior to production deployment.

1.1.7. Scheduled and Automated Workflows:

The Contractor shall configure and sustain scheduled workflow capability, to include:

Scheduled generation and distribution of Government-defined standard reports (class starts, completions, attrition, counseling packet status) on Government-approved cycles.

1.1.7.1. Scheduled data refresh of enterprise extracts and structured reporting tables supporting Government analytics on a cadence defined by the Government (see Section 1.1.8).

1.1.7.2. A pilot automated progression rule on one Government-designated pipeline: upon a student status change to Graduate in a course, the system shall automatically generate a reservation or staging action for the next course in the designated pathway sequence, with exception reporting for manual review. The Contractor shall document and deliver lessons learned from this pilot to the Government.

1.1.7.3. Student accountability status maintained at four primary values (In Training, Out of Training, Awaiting Training, Completed Training) with a subordinate detail field for refined status categorization, mapped to the Government-owned status taxonomy.

1.1.8 Data Architecture, Structured Data Tables, and Dashboard Reporting Enablement:

The Contractor shall support the Government's enterprise analytics architecture by ensuring compatibility with the Government-provided hosting and analytics environment and by delivering and sustaining an analytics-ready data layer. The Contractor shall:

1.1.8.1. Structured reporting tables. Design, deliver, and sustain a documented set of structured, normalized reporting tables and/or views for the Government instance covering, at minimum: student demographics; course enrollments and reservations; student status and status history; event-level performance results; attribute scores; counseling and board actions; and class/cohort rollups. Tables shall use consistent, documented naming conventions, defined data types, primary and foreign keys anchored on EDIPI/DoDID, and effective-dating sufficient to support longitudinal analysis.

1.1.8.2. Schema remediation. Execute remediation of legacy schema conditions affecting analytics performance, including row-versioning bloat and normalization deficiencies, in accordance with the Government-approved remediation roadmap, with progress reported in the monthly status report.

1.1.8.3. Automated dashboard enablement. Ensure the structured reporting layer is directly consumable by the Government analytics platform through the Government-provided data gateway, including documented refresh-compatible views, query performance suitable for scheduled refresh windows defined by the Government, and coordination with the Government on incremental refresh strategies for high-volume tables.

1.1.8.4. Semantic layer documentation. Deliver and maintain a data dictionary for the reporting layer that defines each table, field, business definition, source lineage from operational tables, and update cadence, delivered with Technical Data - Unlimited Rights in accordance with DFARS 252.227-7013.

1.1.8.5. Data quality rules. Implement and sustain Government-approved automated data quality checks (completeness, validity, referential integrity, duplicate detection) on the reporting layer, with exception reports delivered to the Government data steward on a defined cadence.

1.1.8.6. Change control. No schema change to the structured reporting layer shall be deployed to production without Government notification; breaking changes require Government approval and a minimum 30-day notice with updated documentation, to protect downstream Government assets.

1.1.9. Data Transformation and Migration Readiness:

In support of Department of War Data Decrees compliance, longitudinal analytics, and Government planning purposes, the Contractor shall provide technical support to:

1.1.9.1. Historical data transformation. Transform and load Government-designated historical student performance data as identified in Technical Exhibit [X] into the structured reporting layer so that longitudinal analysis spans legacy and current records with documented lineage and known limitations.

1.1.9.2. Reference data management. Establish and sustain Government-owned reference tables (course catalog, pathway sequences, status taxonomy, unit structures, attribute definitions) as configuration data modifiable by authorized Government administrators without vendor development action, where technically feasible.

1.1.9.3. Open-schema export. Demonstrate and document an open-schema, non-proprietary, machine-readable export covering all Government student performance data and the structured reporting layer, executable by Government administrators.

1.1.9.4. Metadata tagging. Provide the ability to apply Government-defined metadata tags to data records, accessible to users and preserved in exports.

1.1.10. Documentation and Data Portability Deliverables:

The following are contract deliverables delivered with Technical Data - Unlimited Rights in accordance with DFARS 252.227-7013:

1.1.10.1. Current-state data dictionary and schema documentation for the Government instance, including the structured reporting layer per Section 1.1.8.

1.1.10.2. Interface control documentation for all interfaces delivered under Section 1.1.3.

1.1.10.3. Measurement model documentation (task-to-attribute mappings and scoring logic) for each module, maintained as current, Government-reviewed artifacts.

1.1.10.4. The demonstrated open-schema data export capability per Section 1.1.9.

1.1.10.5. A transition-out plan, delivered in draft within 90 days of contract award and finalized 60 days prior to the end of the period of performance.

1.1.11. Data Rights and Source Code Acquisition Pathway:

The Government holds Technical Data - Unlimited Rights in accordance with DFARS 252.227-7013 in all student performance data, custom-configured modules, Government-instance configurations, report designs, data schemas (including the structured reporting layer), measurement models, and all documents and materials produced under this contract. To the extent that the system utilizes commercial computer software or proprietary baseline architecture, the Government's rights shall be governed by DFARS 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation) or the Contractor's commercial license terms, provided they are consistent with Federal procurement law.

In support of the Government's long-term objective to reduce proprietary dependency — consistent with Modular Open Systems Approach (MOSA) direction and the Department's software acquisition policy — the Contractor shall: (a) maintain a Contractor-provided continuity-of-operations assurance acceptable to the Government; and (b) provide technical data and software documentation sufficient to allow the Government or a third party to operate, maintain, and migrate the system upon contract expiration, subject to the rights defined herein. Nothing in this section obligates the Government to purchase, nor the Contractor to sell, any proprietary software source code.

1.1.12. Platform Database Administration Support and Remediation Scope:

The Government retains sole database administration (DBA) access, hosting control, and ultimate execution authority over the live production database servers. The Contractor shall serve in an advisory, design, and collaborative support capacity, working directly with Government-designated DBAs and infrastructure providers to ensure database performance, schema accuracy, and data integrity.

1.1.12.1. Collaborative Database Support: The Contractor shall not have direct administrative access to live production servers or the underlying database infrastructure. Instead, the Contractor shall partner with the Government-managed DBA team to remediate issues, optimize performance, and maintain the health of the Government instance’s database and structured reporting layer.

1.1.12.2. Schema and Performance Engineering: The Contractor shall design, maintain, and deliver database schemas, index strategies, and query optimizations. The Contractor shall analyze system and reporting-layer performance, identify bottlenecks, and deliver actionable remediation scripts, deployment packages, and configuration recommendations to the Government DBAs for execution.

1.1.12.3. Data Integrity and Backup Collaboration: The Contractor shall establish data integrity auditing protocols and review audit outputs. The Contractor shall collaborate with Government infrastructure providers to define backup verification requirements and analyze verification reports to confirm disaster recovery readiness, without directly executing backup or restore commands on live systems.

1.1.12.4. Database Responsibility Matrix (Deliverable): The precise boundaries, communication workflows, and step-by-step procedures between Contractor engineering support and Government/third-party DBA infrastructure operations shall be documented in a Database Responsibility Matrix (DRM). The Contractor shall deliver the DRM within sixty (60) calendar days of contract award for Government review and approval. The Contractor shall review and update the DRM annually, within thirty (30) calendar days of any option period exercise, as required.

1.2. Background: USAJFKSWCS utilizes a specialized human performance, assessment, and management software platform for data collection and reporting that provides refined information to decision makers to make critical and timely human capital decisions.

1.2.1. Inception. From 2003 to 2004, the 1st Battalion, 1st Special Warfare Training Group (Airborne), United States Army John F Kennedy Special Warfare Center and School (USAJFKSWCS) created a methodology to assess and capture candidate performance data during Special Forces Assessment and Selection (SFAS). This stand-alone platform was designed to integrate all performance data collected on a candidate and provide the command a decision support tool to “select” or “non-select” the candidate based on whole person scores. Over the subsequent years, the scope of the system has expanded from a stand-alone assessment tool to a fully networked, enterprise-wide student management and human performance data system supporting ARSOF training pipelines.

1.2.2. Expansion. In 2021, SWCS expanded use of the Human Performance, Assessment, and Management Software platform from Assessment and Selection, to encompass all ARSOF MOS pipeline training. The platform was updated to support production analytics across all pipelines and provide for comprehensive pipeline management. This expansion and upgrade created an environment that provides a holistic view of performance, fosters student development, and facilitates training management. The software has the capability of integrating a variety of different student performance measures during training and compiling this information into a standardized performance counseling report. These measures include physical events such as ruck marches and physical fitness tests; intellectual aptitude measures; behavioral observations; cadre and peer evaluations; leadership evaluations; land navigation; surveys; and other key SOF-specific skills. This integrated assessment approach allows decision makers to assess multiple dimensions of a Soldier’s performance that can then be used to target specific development needs.

1.2.3. Modernization Trajectory. The Government has achieved online integration of human performance data across multiple training pipelines, establishing a validated decision-support mechanism for senior leadership. This contract is structured to preserve that momentum: compliance with Department of War data and software modernization direction, interoperability with enterprise systems of record (Vantage, Maven, ATRRS, IPPS-A, ), an analytics-ready structured data layer feeding Government Dashboards, and the documentation and data portability posture required for a highly capable, interoperable, and auditable enterprise solution.

1.2.4. Policy Authority Summary:

• Directing Modern Software Acquisition to Maximize Lethality Memorandum (SecDef, 6 March 2025) — Software Acquisition Pathway as preferred pathway; agile, iterative delivery.

• Artificial Intelligence Strategy for the Department of War and DoD Data Decrees enforcement (January 2026) — federated data catalog publication; machine-readable, non-proprietary interfaces; platform-agnostic, decoupled data storage; data as an enterprise resource.

• Transforming the Defense Acquisition System into the Warfighting Acquisition System (7 November 2025) — speed to capability; documentation to statutory minimums; modularity and competition.

• Modular Open Systems Approach (MOSA) direction — documented modular interfaces sufficient for third-party integration; mitigation of vendor lock-in.

• NIST SP 800-171 / Cybersecurity Maturity Model Certification (CMMC) Level 2 — CUI safeguarding human performance and psychological data.

1.3. Objectives: The basic service objective includes the following:

1.3.1. Software License and maintenance for the life of the PoP.

1.3.2. Module Sustainment services (performance model, technical configuration, and reporting) support for thirty-eight context and content unique system modules. This service includes providing sufficient on-site and reach-back personnel to ensure continuous module support and meet the performance standards defined herein.

1.3.3. Training for each module.

1.4. Scope: The scope of this contract is to provide any maintenance, sustainment, software upgrades, and user training for Human Performance, Assessment, and Management software application located on the Government network and ensure that the software is operating as designed. Services include providing the software license to operate the Government-selected system, maintenance of the current platform and any updates, periodic customizations (within the scope of this PWS) based on changes or incorporating improvements to the program of instruction and technical support which include training of users on the following; overlords, basic administration, and operational administration.

1.5. Period of Performance:

Base Year: 12 Months Period, After Contract Award (ACA) Option Years: Four (4) 12-Month Option Periods

1.6. General Information:

1.6.1. Quality Control. Quality Control is the responsibility of the Contractor. The Contractor is responsible for the delivery of quality services to the Government (see FAR 52.246-1 Contractor Inspection Requirements).

1.6.1.1. Quality Control Program. The Government is committed to a highly interactive relationship between quality control by the Contractor and quality assurance by the Government recipient of services. This relationship shall be achieved through an effective Prevention Based Quality Control Program dedicated to ensuring the best possible products and services to end users. The Contractor shall provide their final written Quality Control Plan (QCP) no later than (NLT) fifteen (15) days after contract award and within five (5) calendar days of any proposed changes to the COR and KO.

1.6.1.1.1. The Contractor’s quality program shall demonstrate its prevention-based outlook by meeting the objectives stated in PWS throughout all areas of performance. The QCP shall be developed to specify the Contractor’s responsibility for management and quality control actions to meet the terms of the contract. The QCP as a minimum shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints.

1.6.1.1.2. Within 24 hours of completion, the Contractor shall provide all reports generated as a result of the Contractor’s quality control efforts to the COR. This shall include any summary information used to track quality control, including any charts/graphs.

1.6.1.1.3. The Contractor’s QCP shall be incorporated into and become part of this contract after the plan has been accepted by the KO. Proposed changes made after KO acceptance shall be submitted in writing through the COR to the KO for review and acceptance prior to implementing any revision. The Contractor’s QCP shall be maintained throughout the life of the contract and shall include the Contractor’s procedures to routinely evaluate the effectiveness of the plan to ensure the Contractor is meeting the performance standards and requirements of the contract.

1.6.1.2. Contractor Discrepancy Report (CDR): When the Contractor's performance is unsatisfactory, a CDR will be issued by the KO. The Contractor shall reply in writing within five (5) workdays from the date of receipt of the CDR, giving the reasons for the unsatisfactory performance, corrective action taken, and procedures to preclude recurrence.

1.6.1.3. Quality Assurance. The COR will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the COR must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). When an observation indicates defective performance, the COR will require the Contractor or designated on-site representative to initial the observation to acknowledge the defective performance. The acknowledgement of the observation does not necessarily constitute Contractor concurrence with the observation, only that the Contractor has been made aware of the defective performance.

1.6.2. Property Management System: Not Applicable

1.6.3. Recognized Federal Holidays: The Contractor shall not be required to perform routine, non-emergency services on recognized federal holidays. The recognized federal holidays include:

1.6.3.1. When a holiday occurs on a Saturday, Federal employees are normally granted the previous Friday as the holiday observance. When a holiday occurs on a Sunday, Federal employees are normally granted the following Monday as the holiday. The contractor shall work on the days the Government is scheduled to work.

1.6.3.2. When an unforeseen installation closure occurs on a regularly scheduled day of work, the Contractor will have the following options:

a. Reschedule the work, so it is performed the following day unless the following day falls on a weekend.

b. Reschedule the work on any day that is mutually satisfactory to the Contractor and the COR.

c. Authorized place of performance to telework/remote location on government furnished device only, subject to COR approval.

1.6.4. Hours of Operation:

1.6.4.1. The system shall remain fully operational 24 hours a day, 365 days a year. During nights, weekends, and holidays the contractor shall provide adequate technical support to overcome emergent issues and to ensure that the system can continue to function and support performance attribute collection while courses are being conducted during those time periods. Within two hours of any reported software issue, the Contractor shall respond via phone or email to the COR or other identified Government personnel.

1.6.4.2. The Contractor shall be responsible for providing training services, between the core hours of 0800 to 1700 Eastern Time, Monday through Friday. This is a Firm-Fixed-Price contract; no overtime or compensatory time (CT) is authorized for payment by the Government. The Contractor shall manage its workforce labor hours to meet PWS requirements within the established fixed price, adhering to all applicable federal and state labor laws.

1.6.5. Place of Performance and Hours of Operation:

1.6.5.1. Primary Work Sites: The work to be performed under this contract shall be accomplished at the Contractor’s facilities and Government facilities at Fort Bragg / Camp Mackall, North Carolina.

1.6.5.2. Alternate Worksite (Telework) Authorization: The Government authorizes the use of alternate worksites (telework/remote work) for unclassified tasks, provided that performance requirements, security protocols, and Service Level Agreements (SLAs) are maintained. Alternate worksite performance is not a replacement for primary worksite attendance; Contractor personnel should only exercise this option on a situational or operational basis approved by the COR.

1.6.5.3. Hours of Operation & Flexible Scheduling: The standard duty hours for this contract are 0800 to 1700 Eastern Time, Monday through Friday. However, due to the dynamic operational environment and the requirement to execute software updates, deployments, system patches, and emergency remediations outside of peak usage windows, Contractor personnel may be required to work non-standard, flexible, or extended duty hours (including nights, weekends, and federal holidays).

The Contractor shall manage its staffing and scheduling to ensure coverage for scheduled off-hours maintenance and urgent technical remediations without additional cost to the Government.

1.6.6. Security Requirements: Security will be in accordance with the DD254. Contractor team individual(s) supporting activities on-site will be cleared at the secret level at the start of the contract. Additionally, the contractor will obtain and maintain a SECRET Facility Clearance in accordance with the DD Form 254. The contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting Government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor's management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The Government (the KO and COR) shall be immediately notified if there is any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information

1.6.6.1. 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.

1.6.6.1.1. All data provided to Contractor by the Government and/or updates provided by the contractor for the Government will be protected from disclosure. All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior written approval by the Government Contracting Officer. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nations or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. No data or other deliverables from this project will be printed, distributed, published, briefed, or otherwise used without the expressed written approval of the COR.

1.6.6.1.2. Contractor personnel performing work under this contract shall read and sign a Nondisclosure Statement (NDS) prior to performing work under this contract. The Contractor shall provide these signed forms to the COR within thirty (30) calendar days of contract award and within seven (7) calendar days of any newly hired personnel commencing work.

1.6.6.2. Permission Roles: In addition to user authentication, the application will provide permission roles that control which features, data, and applications each user has access to. Permission role limitations shall include, but are not limited to, protection of data related to psychological assessment and personally identifiable information (PII) from users not authorized to access these types of highly sensitive data.

1.6.7. Special Qualifications. N/A

1.6.8.1. General:

1.6.8.1.1. The Contractor is cautioned that off duty active military personnel hired under this contract may be subject to permanent change of station (PCS), change in duty hours or deployment. Military Reservists and National Guard members may be subject to recall to active duty. Their absence at any time shall not constitute an excuse for nonperformance under this contract.

1.6.8.1.2. Contractor personnel performing work under this contract shall be able to read, write, speak, and understand the English language to effectively carry out all contract requirements. They shall have a command of both the written and spoken English language to properly clearly and effectively communicate in person or via electronic devices (telephone or Email) with co-workers, customers, and the general public.

1.6.8.1.3. Contractor personnel performing work under this contract shall be U.S. citizens unless the provisions of Army Regulation 25-2, Information Assurance have been fully completed, and approval has been granted by the Government for the non-U.S. citizen to perform the required support.

1.6.8.1.4. Information Assurance (IA) / Cyber Awareness / Information Technology (IT) training. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training (IAT Level 1) before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD, Army, USSOCOM and USASOC training requirements in DoD Directive 8140.01 (Cyberspace Workforce Management), DoD 8570.01-M / DoD 8140.03-M, AR 25-2 and published USSOCOM and USASOC requirements within 180 calendar days of employment.

1.6.8.1.5. Handling / access to classified information. The Vendor shall comply with FAR 52.204-2, Security Requirements for access to information classified "Confidential", "Secret", or "Top Secret". The Vendor must execute a Security agreement (DD Form 441), IAW the National Industrial Security Program Operating Manual ( NISPOM, 32 CFR Part 117) and any revisions (Note: A DD Form 254 will be required for any contract that requires access to classified information and/or a security clearance.)

1.6.8.1.6. Vendor to obtain Facility Clearance and individual clearances at the appropriate level. The Vendor must possess or obtain a Facility Clearance at the appropriate level (IAW the NISPOM 32 CFR Part 117) in accordance with the DD Form 254. Contractor personnel performing work under this contract must have the required security clearance at the appropriate level at the start of the period of performance or upon commencing work. Security clearances and Facility Clearance (FCL) requirements are required to be maintained for the life of the contract in accordance with the DD254 attached to the contract.

1.6.8.1.7. Access and General Protection/Security Policy and Procedures: All Contractor personnel performing work under this contract shall comply with applicable installation, facility and area commander installation/facility access, local security policies and security procedures provided by the Security Manager Government representative. Contractor personnel shall provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor personnel shall comply with all personal identity verification requirements as directed by Department of Defense (DoD), HQ Department of Army (DA) or local policies. In addition to the changes otherwise authorized by this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Contractor and subcontractor security matters or processes.

1.6.8.1.8. Anti-Terrorism (AT) Level I training. All contractor employees, including subcontractor employees, requiring access to an Army or USSOCOM controlled installation, facility, or area shall complete AT Level I Awareness Training within 60 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies. The contractor shall submit certificates of completion for each affected contract employee and subcontract employee to the COR (or to the contracting officer, if a COR is not assigned) within 90 calendar days after completion of the training by all employees and subcontractor personnel. This is an annual training requirement. AT Level I training is available at: https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam.

1.6.8.1.9. iWATCH Training: The Vendor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the Government requiring activity Antiterrorism Officer (ATO)). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR or the designated security office. Training shall be completed within 60 calendar days of contract award and within 30 calendar days of new employees' commencing performance with the results reported to the COR no later than 90 days after contract award and new employees' commencing performance.

1.6.8.1.10. Contractor Employees Requiring Access to Government Information Systems: Contractor shall have access to Government-controlled information systems during performance of work under this contract. All contractor employees and associated subcontractors who require access to a Government information system shall be registered in the ATCTS (Army Training Certification Tracking System) at commencement of support services and must successfully complete the DoD Information Assurance Awareness prior to access to the information systems. Training shall be required annually after the initial training. Completion certificates shall be submitted to the COR within fifteen (15) calendar days from date of commencing performance under this contract.

1.6.8.1.11. OPSEC Training: Per AR 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within 30 days of reporting for duty. All contract employees must complete annual OPSEC Awareness Training.

1.6.8.1.12. Additional OPSEC training. In accordance with current DoD policy, the following additional security training courses are required for each on-site contractor under this requirement:

1. OPSEC Awareness,

2. Unauthorized Disclosure of Classified Information for DoD and Industry,

3. Insider Threat Awareness,

4. Introduction to Information Security.

Training for the four additional courses is located at; https://securityawareness.usalearning.gov/2020-dodsecurity-stand-down ~ the applicable DoD or Army learning portal (e.g., CDSE, JKO). The Contractor shall provide confirmation that all training has been completed to the COR within thirty (30) days of commencing work and annually thereafter.

1.6.8.1.13. OPSEC SOP/Plan requirements. If discretionary GFE computer and software are provided (see PART 3, GFE), the Contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan to be reviewed and approved by the responsible government OPSEC Officer, per AR 530-1 Operations Security, prior to receipt of GFE. This SOP/Plan will specify the government's critical information, why it must be protected, where it is located, who is responsible for it, and how to protect it. In addition, the Contractor shall train an individual as a certified OPSEC Level II Coordinator, IAW AR 530-1, prior to receipt of GFE.

1.6.8.2. Other Qualifications: The Contractor is responsible for providing fully trained personnel. Contractor personnel shall be trained and functional prior to performing services. The Contractor shall possess the necessary technical qualifications, certifications, and experience required to manage, configure, sustain, and integrate the Government's Human Performance, Assessment, and Management Software platform as defined in this PWS. The Contractor shall be responsible for ensuring all personnel possess and maintain current certifications as indicated within this PWS and all security requirements during the execution of this contract.

1.6.9. Post Award Conference/Periodic Progress Meetings: The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation (FAR) Subpart 42.5. The post-award conference will also be utilized to ensure contractor understands all requirements. The KO, COR, ACOR, and/or Technical Evaluator (TE) may meet periodically with the Contractor, at a minimum monthly or at the discretion of the KO, to review the Contractor's performance. At these meetings the KO, COR, ACOR, and/or TE 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 experienced. The Contractor shall document all progress meetings and deliver official meeting minutes to the COR and KO within three (3) business days of the meeting for review and approval. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.6.10. Contracting Officer’s Representative (COR)/Alternate COR (ACOR), and Technical Evaluator (TE): The COR and ACOR will be nominated and officially designated by the KO via separate letters of appointment in the Procurement Integrated Enterprise Environment (PIEE) / Joint Appointment Module (JAM). A Government-designated Technical Evaluator (TE) may also be assigned to monitor and evaluate specific technical, operational, and database performance metrics. The COR, ACOR, and TE monitor all technical aspects of the contract and assist in contract administration. The COR, ACOR, and TE are authorized to perform the following functions: Assures that the Contractor performs the technical requirements of the contract; performs inspections necessary in connection with contract performance; maintains written and oral communications with the Contractor concerning technical aspects of the contract; issues written interpretations of technical requirements, including Government drawings, designs, specifications; monitors Contractor's performance and notifies both the KO and Contractor of any deficiencies; coordinates availability of Government furnished property, and provides site entry of Contractor personnel. A letter of designation issued to the COR and ACOR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR and ACOR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR, ACOR, and TE are not authorized to change any of the terms and conditions of the resulting contract. Any technical direction or interpretation of the requirements provided by the COR, ACOR, or TE shall not constitute a change to the contract. Only the KO possesses the authority to modify this contract. Any unauthorized work performed by the Contractor in response to direction from personnel other than the KO is done at the Contractor's own financial risk.

1.6.10.1. In no event will the COR, ACOR, or TE by virtue of their designation be empowered to execute or agree to any contract changes thereof or authorized to obligate the Government. If the work is not written in the contract, neither the COR, ACOR, nor TE are authorized to request new work. The KO retains the ultimate responsibility for the administration of the contract. Any discrepancy resulting from coordination with or advisement from the COR, ACOR, or TE shall be addressed, in writing, to the KO.

1.6.10.2. As defined in the official Letter of Designation, the COR and ACOR are authorized to perform the following functions: Assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; and maintain written and oral communications with the Contractor concerning technical aspects of the contract. The COR and ACOR can also issue written interpretations of technical requirements, including government drawings, designs, and specifications, monitor Contractor's performance; notify both the KO and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel.

1.6.10.3. Performance Issues. The Contractor shall inform the COR, ACOR, and KO of any critical system outages or operational degradation immediately, but no later than two (2) hours after identification. For general performance issues that do not impact immediate operations, the Contractor shall inform the COR and ACOR in writing within 24 hours of identifying those issues. Verbal reports regarding any performance issue shall be followed up by written reports within three (3) business days..

1.6.10.4. Nonconformance Report (NCR). Nonconformance occurs when a Contractor fails to meet Contract or Task Order terms, conditions and/or specifications; the Contractor’s quality control system is found to be inadequate; or the Contractor’s noncompliance has led to substandard performance requiring corrective action. All instances of nonconformance identified by the Government will be documented via a Nonconformance Report. The Contractor shall reply to the KO and COR in writing within five (5) business days from the date of receipt of the NCR, giving the reasons for the unsatisfactory performance, corrective action taken, and procedures to preclude recurrence. An NCR will not normally be issued if the Contractor has self-identified a nonconforming condition and has implemented effective corrective actions. However, this does not apply in cases where a Contractor has issued an internal corrective action based on a nonconformance previously identified by the Government.

1.6.11. Key Personnel: Key personnel shall not be added to or removed from the contract without express written approval of the KO. Any changes to the working status of these key personnel shall be transmitted (in writing) to the KO/COR/ACOR at least ten (10) business days prior to the proposed change. If, for any reason, any of the key personnel becomes, or is expected to become, unavailable for work under this contract for a continuous period exceeding 30 workdays, the contractor shall promptly replace personnel with personnel who possess qualifications equal to or better than that of the original employee. The Contractor shall ensure all key personnel terminated or released from employment under this contract are replaced within ten (10) business days of the termination. All replacement candidates must be approved by the KO in writing prior to performing work under this contract.

1.6.11.1. The following are considered key personnel by the Government: The Contractor shall provide a Program Manager (PM) who shall be responsible for the performance of the work under this contract. The name of this person, and an Assistant Program Manager (APM), who shall act for the Contractor when the PM is absent, shall be designated in writing to the KO at the post award conference. The PM or APM shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The PM or APM shall be available between the hours of 8:00 AM to 5:00 PM, Monday through Friday, except federal holidays or when the Government facility is closed for administrative reasons.

1.6.11.2. Additionally, the contractor shall provide an adequate number of on-site Human Performance and Student Management System (HP-SMS) SMEs (referred to as Field Support Representatives or FSRs) necessary to ensure the continuous management and support of the Government's Human Performance, Assessment, and Management system in accordance with the Service Delivery Summary metrics. These SMEs shall be physically co-located and perform all daily duties within the 1SWTG S3 office footprint to provide direct, face-to-face operational support across the USAJFKSWCS footprint. These personnel must possess the following minimum qualifications:

1.6.12. Contractor Personnel:

1.6.12.1. Identification of Contractor Personnel: All Contractor personnel attending meetings, answering Government telephones, utilizing Government email systems,…