Attachment 2 Draft PWS.docx

Draft Performance Work Statement (PWS) For

Space Systems Command (SSC) Command Staff Support

Systems Warfighting Architecture Navigator (SWAN) Operations, Sustainment, and Decision Support Services

Solicitation No. FA8802-26-Q-0003 Task Order No. FA8802-26-F-XXXX

01 June 2026

Revision Control

Performance Work Statement (PWS) SWAN Support Services Contract No. FA8802-26-Q-0003

Table of Contents

1. Description of Service

The contractor will support SSC by providing non-personal services for the continued operations, maintenance, and sustainment of the Systems Warfighting Architecture Navigator (SWAN) capability. The existing SWAN capability is a fully fielded Special Access Program (SAP) database, data model, and web application used by the Department of the Air Force (DAF) to evaluate mission threads, identify critical paths to closure, and model investment trades during Program Objective Memorandum (POM) and other budget planning activities. This contract will transition the SWAN capability from its prototype development phase into a full-scale enterprise operations and sustainment effort.

1.1. Scope of Services

The Contractor shall provide all necessary personnel, supervision, and other non-personal services required to sustain the SWAN capability and provide critical decision support analysis for both the United States Space Force (USSF) and United States Air Force (USAF). The scope includes system and database sustainment, mission thread analysis, decision support for the POM cycle, agile software development, and ensuring compliance with all security and data rights requirements.

1.2. Kick off Meeting and Transition-In

A Transition-In period of at least 90 days is required. The incoming Contractor shall implement transition activities beginning on the first day of performance to minimize impact to schedules, cost, performance, and risk. The Contractor shall be fully performing all PWS requirements no later than ninety (90) days from the performance start date. The Contractor shall participate in organizational, system, process, and information knowledge and data transfer from the Government team and the incumbent Contractor to ensure a seamless handover of the SWAN SAP environment, codebase, and data models without disrupting ongoing budget cycle support or deliverables. The contractor’s Program Manager (PM) shall schedule and coordinate a Project Kick-Off Meeting at a location approved by the Government, or virtually, within ten (10) business days after date of task order start. The kickoff meeting will be with the members of the Government, the Contracting Officer’s Representative(s) (COR(s)), and other officials as designated by the Government. It shall provide the opportunity to discuss technical, management, security issues, and reporting procedures.

2. Performance Summary

2.1. General

The Contractor shall perform the work and services described herein to the standards set forth in this PWS. The Government shall not exercise any supervision or control over the contract service providers. Such contract service providers shall be accountable solely to the Contractor, who, in turn, is responsible to the Government.

2.2. Performance Evaluation

Performance of a service shall be evaluated to determine whether it meets the performance requirements of this task order. The contractor shall meet with the COR and other government personnel, as directed by the COR on an as-needed basis, but no less than once a month. Contractor shall provide meeting agenda at least a day in advance. Re-performance of unacceptable services at no additional cost is the preferred course of action in the case of issued Corrective Action Reports (CARs).

2.3. Project Management and Scheduling

In the kickoff meeting, the contractor shall provide a unified program management approach to successfully integrate and coordinate all activities needed to execute the requirements of the PWS. To that end, the contractor shall develop project schedule activities, timelines, and outcomes with dependencies and risks identified. The project schedule shall be developed in coordination with government stakeholders, including the COR. The project schedule shall include measurable interim milestones and target final remediation of relevant audit findings, and all other outcomes and key goals.

The contractor shall utilize its project schedule to manage the timeliness, completeness, and quality of all work assignments and deliverables. To promote accountability and establish interim measures for success, the contractor shall propose specific types of measures, definition of success, and periodic updates to the measurement in the project schedule.

The contractor shall establish clear organizational lines of authority and responsibility to enable effective management of the resources assigned to the requirement. Except for GFE that may be required for contractor resources to perform duties under this contract, the contractor shall furnish all work, management, supervision, labor, and materials necessary to help enable the effective and efficient performance of functions identified throughout the PWS. If non-compliant, see section 5.5.1. nonconformance notification.

2.3.1. Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute this requirement including but not limited to:

A. Management of the timeliness, completeness, and quality of all services, work products, and deliverables B. Effective resource loaded program planning C. Corrective action plans for identified audit deficiencies D. Timely identification of issues, risks, and dependencies E. Effective management of subcontractors F. Customer satisfaction and professional and ethical behavior of all contractor personnel

2.3.2. Monthly Activity Reporting

The contractor shall provide a Monthly Activity Report (MAR) that provides an executive- level review of accomplishments, deliverables, projected major tasks, and identified risks for each task order and all applicable tasks outlined in the PWS.

2.3.3. Change Management and Communications

The contractor shall establish effective change management and strategic communication activities that leverage a practical change management methodology that supports the intended outcomes of the PWS. The contractor shall make use of industry standard tools. The contractor will have 10 calendar days from the notification by the COR that change management and strategic communication activities shall be instituted.

2.3.4. Task Order Management Plan (TOMP)

The contractor shall prepare a TOMP recommending the “best” (optimum) method for completing each PWS task over the period of performance of the task order. This TOMP shall be issued with the greatest level of detail and estimation of need available at the time of issuance. Efforts of cooperation between the Government and the contractor/team members shall consider government concerns identified in task meetings, and Task Order (TO) priorities.

The contractor shall develop a Quality Control Plan (QCP) as part of the TOMP that demonstrates how the contractor shall maintain an inspection system acceptable to the Government that covers the services under this task order. The QCP shall demonstrate the contractor’s documented processes and procedures to monitor and control objectives in the services summary; subcontractor relationship management; non-conformance identification, mitigation plans, and prevention; and Contractor employee qualifications and certifications management (Expertise, Experience, Education, and Training). The contractor shall provide the TOMP within 30 calendar days after task order start date. If the Government and the contractor concur on needed document updates, the contractor shall provide an updated version to the Government within ten (10) business days of the agreement date. The QCP will be reviewed initially and again every six months of the task order, to evaluate the plan and ensure that it is operating as intended. If non-compliant, see section 5.5.1. nonconformance notification. (See Appendix B - Deliverable 06) The contractor’s QCP shall include but not be limited to, a description of the following items:

A. The inspection system to cover all services. Description shall include specifics as to the areas to be inspected on a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspector(s).

B. The methods to be used for identifying and preventing defects in the quality of service performed.

C. How the records will be kept. Records must document all inspections and corrective or preventive actions taken.

2.4. Performance Tasks

2.4.1. TASK 1: Operations, Maintenance, And Sustainment of the SWAN Capability The Contractor shall sustain the fully fielded SWAN SAP database, data model, and web application.

2.4.2. TASK 2: Expand and Maintain Mission Thread Analysis

The contractor shall expand mission thread analysis based on priorities established by HQ USSF and HQ USAF.

2.4.3. TASK 3: Decision Support & Rapid Response Analysis

The Contractor shall provide analysis-informed justifications for budget actions and POM advocacy.

2.4.4. TASK 4: Agile Software Development & Backlog Management The Contractor shall utilize Agile methodologies (e.g., Scrum, Kanban) to execute all system upgrades, collaborating with the Government Product Owner to manage the feature backlog. The Contractor shall conduct sprint planning, reviews, and retrospectives, delivering functional, tested software updates via periodic code drops into the secure SAP environment (typically monthly sprints).

2.4.5. Transition Out Plan

The Contractor shall participate in organizational, system, process, and information knowledge and data transfer to the Government team and any incoming follow-on Contractor. This transition personnel overlap period is for a period of at least 90 days prior to the end of the contract PoP. The Contractor shall facilitate this knowledge transfer and establish procedures with the successor to ensure a smooth transition of all requirements and data without any degradation in service.

2.5. Authority of Government Personnel

2.5.1. Task Order Administration

The task order will be administered by SSC/PKA. Only the PCO is authorized to make changes to this task order. The PCO is the sole interpreter of task order terms and conditions. All contractual agreements, commitments, or modifications which involve price, quantity, quality, or delivery schedules shall be made by a mutual agreement of the parties. The contractor shall not take direction from individuals or organizations not authorized and designated by the PCO. Doing so may result in an unauthorized commitment for which the contractor may be held personally liable for any costs incurred.

2.5.2. Contracting Officer's Representative

The COR will be appointed under a separate letter. The COR will act as the PCO’s representative for receipt and acceptance, gather information on technical matters, discuss SWAN supporting issues as necessary with respect to the specification or statement of work, and monitor the progress and quality of contractor performance. It is emphasized that only a PCO has the authority to modify the terms of the contract; therefore, in no event will any understanding, agreement, modification, change order, or other matter deviating from the terms of the basic contract between the contractor and any other person be effective or binding on the Government. When/if, in the opinion of the contractor, an effort outside the existing scope of the task order contract is requested, the contractor shall promptly notify the PCO in writing. No action shall be taken by the contractor under such direction unless the PCO has issued a contractual change or otherwise resolved the issue.

3 General

3.1 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute, personal services, the contractor shall notify the PCO immediately in writing.

3.2 Inherently Governmental Functions

The contractor shall immediately stop work and provide written notification to the PCO regarding situations where the contractor believes, or has reason to believe, it has been tasked to perform an inherently governmental function as defined in Federal Acquisition Regulation (FAR) 2.101 and detailed in FAR Subpart 7.5. The contractor shall not make judgments, discretionary decisions, nor perform any other activities related to inherently governmental functions, including supervision of Government personnel.

3.3 Period of Performance

The Period of Performance (PoP) shall consist of one (1) 12-month Base Period and four (4) 12-month Option Periods that may be exercised at the discretion of the Government.

3.4 Place of Performance

The work shall be performed at Government-provided facilities. Primary operating locations will be split between Los Angeles Air Force Base (LAAFB), CA, and the National Capital Region (NCR), including but not limited to the Pentagon and Joint Base Anacostia-Bolling (JBAB). No specialized contractor facilities are required.

3.5 Type of Contract

The Government anticipates awarding a Firm-Fixed-Price (FFP) type contract.

4 Government Workplace

4.1 Government Furnished Property and Services

The Government will provide the workspace, laptops, desks, chairs, telephones, and general office supplies (e.g. pens, paper, notepads). All Government-Furnished Property (GFP) and services shall be used only for performance of this task order. The contractor shall manage GFP in accordance with FAR 52.245-2 Alternate I Government Property (Fixed- Price Contracts). At the close of each work period, government facilities, property, and materials shall be secured. The contractor shall complete a government-furnished property inventory with ATLAS IT government representative within 20 workdays of the receipt of said property.

4.2 Government Furnished Information (GFI)

The Government will provide the Contractor with access to all relevant Government-owned data, documentation, and systems required to perform the work, including access to the complete SWAN codebase, data models, repositories, taxonomy, and associated analytical products.

4.3 Contractor Identification in the Workplace

In all situations where contractor personnel status is not obvious, all contractor personnel are required to identify themselves to avoid creating a false impression to agency officials, that such contractor personnel are government officials. This shall occur during meeting attendance, through written (letter or email) correspondence or verbal discussions (in person or on Teams), when making presentations, and in other situations where their contractor status is not obvious.

The contractor employees shall:

A. Clearly always identify themselves as “contractors” as indicated on their badge at all times when in the office working location, including conference rooms.

B. Identify themselves by name, their company name, if they are a subcontractor the name of the prime contractor their company is supporting, as well as the government office they are supporting when participating in meetings, conference, and other interactions in which all parties are not in daily contact with the individual contractor employee.

C. Be able to provide, when asked, contract name/number, and the name of the COR.

4.4 Communication

4.4.1 Government Telephone

The Contractor shall be allowed the use of the government telephone for contacting the PCO, Civil Engineer, Fire Department, and Security Forces; receiving customer complaints; and any other directly contract related communications.

4.4.2 Local Area Networking (LAN)

The Government will provide for official use only Internet access through the government-provided Local Area Net (LAN). The Contractor shall obtain network access using local procedures. All access to the LAN must be approved by the Government.

4.4.3 Communication Security (COMSEC)

All DoD communications are subject to COMSEC review. Use of DoD telephones and telephone systems constitutes consent to COMSEC monitoring. The contractor shall comply with relevant Government procedures and rules.

4.5 Refuse Collection

Waste generated by the Contractor in performance of the services specified with this PWS shall be deposited in government dumpsters, excluding hazardous materials in which proper disposal instructions shall be complied with. The Contractor shall comply with base recycling regulations.

4.6 Emergency Medical Service

Emergency medical treatment and emergency patient transportation service is only available through the local community.

4.7 Security Forces

The Government will provide general security service. Security Forces phone extensions are 911 for emergencies.

4.8 Forms and Publications

The Contractor is responsible for obtaining and maintaining all forms and publications needed to perform the contract.

4.9 Data Rights

The Government has full rights to all data, work products, and deliverables under this task order. All data received, processed, evaluated and/or generated in the execution of this task order shall become the property of the Government unless specific exception is granted by the PCO. The Government will retain custody of all records associated with contractor deliverables and shall have exclusive control in the distribution of all written deliverables.

No documents shall be marked “Contractor Proprietary.” The contractor shall not use any system, software, or other means that are proprietary and not authorized by the Government.

The contractor shall ensure that government-furnished IT systems are maintained separately from the contractor's furnished commercial systems, such as its financial management, personnel and other operating systems. The Government's furnished source programs, databases, operating systems and all modifications shall remain as government property. The contractor shall maintain and protect the systems and data for the duration of the task order; therefore, at the task order end date return all current source and compiled programs, documentation, and data in a useable format consistent with the way it was originally furnished or modified during the performance period, including any approved Contractor applications with databases. The contractor shall ensure data is current, complete and readily accessible.

5 General Information

5.1 Firm Fixed Price

The firm-fixed-price contract provides for a price that is not subject to any adjustment based on the contractor’s cost experience in performing the contract. (See FAR 16.202-2) A firm- fixed-price contract is suitable for acquiring commercial products or commercial services or for acquiring other supplies or services based on reasonably definite functional or detailed specifications.

5.2 Travel

For travel costs, the Contractor shall submit a travel request to obtain approval from the COR prior to execution of travel and submit invoices for travel expenses after the completion of travel within 60 days. Following official travel, the Contractor shall prepare a trip report detailing the purpose of the trip, the individuals contacted, any agreements that were reached during the trip or any other significant issues that were identified during the travel. The Contractor shall provide this trip report to the COR within five (5) days after the completion of travel. Invoices must include copies of all receipts and shall be submitted to Wide Area Workflow (WAWF). The Government will reimburse the contractor for allowable transportation, lodging, meals, and incidental expenses in accordance with FAR 31.205- 46--Travel Cost, and the Joint Travel Regulation (JTR), or company policy, whichever is most cost effective for the Government. Reimbursements for lodging, meals, and incidental expenses may be based on either per diem or actual expenses but will only be allowed to the extent that they do not exceed the maximum per diem rates in effect at the time of travel set forth in the JTR. (See Appendix B - Deliverable 14) Travel to operational sites may be required. Travel will be reimbursed in accordance with the JTR and FAR Part 31.205-46. Private/Commercial parking services, laptops, cellular phones, and other items of convenience are not reimbursable. Travel associated with the cost of business must be communicated to the COR in advance for consideration and approval. Commuter and/or parking expenses within the commuting range of the LAAFB area are not reimbursable. The LAAFB area is defined to be a commute within 50 miles of LAAFB. Travel that is not expressly approved in advance by the COR is unallowable.

5.3 Contractor Personnel

The Contractor shall provide qualified personnel to accomplish all tasks and functions described in this PWS. The Contractor shall provide a Senior Operations Analyst and a Full-Stack Developer as Key Personnel. These individuals are considered essential to the work being performed hereunder.

• Senior Operations Analyst: Responsible for leading mission thread decomposition, executing tradespace analysis, and synthesizing complex SWAN data into senior-leader decision support products. Must demonstrate a strong history of supporting DoD/DAF POM cycles and capability analysis.

• Full-Stack Developer: Responsible for the O&M of the SWAN web application, SAP database, and data model. Must demonstrate historical performance in maintaining, upgrading, and deploying code within secure/SAP environments.

5.3.1 Contractor Program Manager

The contractor shall appoint a contractor PM to provide daily supervision and quality control, and who shall represent the contractor and be responsible for the performance of the work throughout the term of the contract. The name of this person, and an alternate(s) who shall act for the contractor when the manager is absent, shall be designated in writing to the PCO and the COR. The PM and their alternate shall be able to speak, read, write, and understand English. The PM and their alternate shall be able to effectively communicate with contractor and government employees.

5.3.2 Contractor Employees

The Government reserves the right to restrict the employment, under this contract, of any contractor employee, or prospective contractor employee who is identified as a potential threat to health, safety, security, general well-being, or the operational mission of the installation and its population. Contractor shall perform background checks, at contractor's expense.

5.3.3 Key Personnel

The Contractor shall retain the Key Personnel identified in its quote for, at a minimum, the entire base period of performance. Substitution of Key Personnel is not permitted unless necessitated by circumstances beyond the Contractor’s reasonable control, such as an individual's protracted illness, disability, or voluntary resignation from the Contractor's company. Any substitution requires the prior written approval of the PCO or COR. To request a substitution, the Contractor must submit a written justification to the PCO and COR at least thirty (30) calendar days prior to the proposed substitution.

Any proposed substitute must have qualifications, experience, and expertise that are equal to or greater than the qualifications of the person being replaced. The PCO's final approval is contingent upon a determination that the proposed substitute meets or exceeds all requirements for the position.

5.3.4 Employee Training

The contractor is responsible for all task order-assigned employee training at no additional cost to the Government. Each contractor employee shall come to work and be fully trained and capable of performing the assigned task order tasks.

5.3.5 Contract Management

5.3.5.1 Quality of Support and Service

The contractor shall accomplish tasks by providing personnel possessing skills to accomplish tasks assigned. Quality of performance will be assessed via the QASP based on the accomplishment of all tasks and deliverables within the specified performance measurements established in this PWS and task order deliverables.

5.3.5.2 Work Product Integration of Effort

The contractor is solely responsible for the actions and management of its employees, associate organizations, and any other part of its team helping to perform these tasks, and the execution and integration of all work performed for this task order. The term “associate organizations” means any proposed team member other than the prime (e.g., including but not limited to, subcontractors, divisions, partners, joint ventures, and subsidiaries).

5.3.5.3 Government Security Instructions

The Government official designated as having security supervision over all security aspects of this contract, under the provisions of the Industrial Security Manual (ISM), is the Space Systems Command Director of Security. Any other security requirement not specifically defined in this contract, or in the ISM will be provided by the SSC Director of Security by written instructions to the Contractor via a Contractor Visitor Group Security Agreement in accordance with paragraph 1-108e, DOD Directive 5220.22R.

5.3.6 Security Requirements

The Contractor shall comply with the personnel security requirements in the attached DD254. Contractor personnel are subject to all local installation rules and procedures. Site specific approval regarding access, issue of security badges, etc., will be coordinated as required. All contractor employees must complete DoD Information Assurance awareness training before issuance of network access and annually thereafter. The Contractor shall comply with any other security requirement not specifically defined in this contract.

5.3.6.1 Security Clearances

Contractor shall ensure contractor personnel have appropriate clearances prior to commencing work on this task order unless otherwise approved in writing by the CO. All assigned personnel must possess and maintain a Top Secret//SCI clearance and be eligible for SAP (SAR) read-ins for the entire Period of Performance.

5.3.6.2 Security Requirements

DoD 5220.22-M; Change 2 and Defense Counterintelligence & Security Agency (DCSA) Assessment and Authorization Process Manual (DAAPM) Version 2.2. Controlled Unclassified Information (CUI) - For Official Use Only (FOUO) Information generated or provided under this contract shall be safeguarded and marked as specified in Department of Defense Instruction (DODI) 5200.48 Controlled Unclassified information (CUI) is the term which collectively refers to FOUO and Unclassified Controlled Nuclear Information (UCNI). CUI provided under this contract shall be managed and safeguarded IAW DoDM 5200.01 V1, 2 and 3, Controlled Unclassified Information. UCNI is sensitive unclassified information subject to special handling as outlined in DoDI 5210.83, DoD UCNI, MAJCOM/DRU Public Affairs Office to the Secretary of the Air Force, Office of Public Affairs, Security and Review Division (SAF/PAX), 1690 Air Force Pentagon, Washington DC 20330-1690.

5.3.6.3 Dress and Appearance

Contractor personnel shall present a clean, neat, and professional appearance at all times and be easily recognized as contract employees. No item of military clothing shall be worn as an outer garment.

5.3.6.4 Employment of Government Employees

The contractor shall not employ any person who is an employee of the United States Government if the employment of that person would create a conflict of interest, or the appearance of a conflict of interest; nor shall the contractor employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives proper approval. The contractor is cautioned that off-duty active military personnel hired under this contract task order 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 task order. The contractor is prohibited from employing off-duty government employees who are managing any contracts or subcontracts awarded to the contractor.

5.3.6.5 Organizational Conflict of Interest (OCI) and Non-Disclosure Agreements (NDA)

The contractor is required to comply with FAR 52.203-13- Contractor Code of Business Ethics and Conduct, which requires the contractor to have a written code of business ethics and conduct, proactively train their employees on the code, and seek out these conflicts of interest. Contractor personnel shall complete and sign an NDA prior to the commencement of work. This requirement extends to all subcontractors and teaming arrangements. The non- disclosure statement shall be provided to the COR. The Contractor is responsible to obtain all necessary approvals prior to obtaining access to proprietary information, in accordance with FAR 9.505-4. The Contractor shall have adequate procedures to monitor and prevent such non-disclosures, including responsibility for preventing disclosures by subcontractors, team members, or others performing on behalf of the Contractor. Any OCI or NDA concerns, questions, or infractions must be communicated in writing to the PCO and reported to the ATLAS security officer. Vetting of personal, financial, and other conflicts of interests must be completed by the PCO.

If the Contractor discovers an actual or potential organizational conflict of interest not previously considered and adequately mitigated under this OCI requirement and the Government-approved OCI Plan, the Contractor shall make a prompt and full disclosure in writing to the CO. This report shall include a description of the violation and the actions the Contractor has taken or proposes to take to mitigate and avoid repetition of the violation. The Contractor shall routinely monitor its proposed business development and shall discuss any real or perceived OCI issues with the CO and affected customers to proactively resolve and/or mitigate those potential OCI issues. After full analysis, the CO and the Contractor will agree on appropriate corrective action, if any, or the CO will direct such action, subject to the terms of this contract.

Any security violations or infractions must be communicated in writing to the PCO and reported to the ATLAS security officer and will be documented in the Month Surveillance Assessment Report (SAR) including, what was the security violation, any classified information compromised, what time, and who.

5.3.6.6 Cybersecurity & ATO

The Contractor shall support the Government in maintaining the SWAN system’s Authority to Operate (ATO) in compliance with all applicable DoD and DAF Risk Management Framework (RMF) policies, including continuous monitoring and vulnerability patching.

5.4 Hours of Operation

5.4.1 Normal Hours of Operation

The Government will provide proper building access identification badges as required to perform tasks herein. The Government may provide access to applicable reference materials, databases, and systems in the performance of this effort. A normal work week is 40 hours per week. Performance should primarily occur during the core hours of 0900 to 1500 hours Pacific Time, Monday through Friday, but could be required at any day and time of the year to support mission requirements.

5.4.2 Federal Holidays

The contractor shall not be required to perform services on federal legal holidays or the day of observation if holiday falls on the weekend. The contractor shall not be required to provide services on the following federal holiday observance days:

· New Year’s Day

· Martin Luther King’s Birthday

· Presidents Day

· Memorial Day

· Juneteenth

· Independence Day

· Labor Day

· Columbus Day

· Veterans Day

· Thanksgiving Day

· Christmas Day If the federal holiday falls on a Saturday or Sunday, it may be observed on Friday or Monday as directed. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

The contractor is responsible for conducting business between the core hours of 0900 - 1500 (Local Time of the office being supported), Monday through Friday. For virtual worksites, the contractor shall be available during these core hours regardless of physical location. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

5.5 Discrepancy Notification

The COR will inform the government PM (or authorized representative) when discrepancies occur and will request corrective action. The COR will make a notation of the discrepancy on their surveillance checklist with the date and time the discrepancy was noted and will request the government PM (or authorized representative) to initial the entry on the checklist.

5.5.1 Nonconformance

Failure to fulfill any task requirement of the PWS is a nonconformance. The Contractor shall take immediate corrective action for any nonconformance. A nonconformance will take one

(1) of two (2) forms:

Minor Nonconformance. See FAR subpart 46.101 for definition. A minor nonconformance is almost always low risk; for example, does not impact conformance to the requirements in Appendix C-Services Summary or the phases, key tasks and associated SWAN work products. Minor nonconformances are communicated by the PCO through a First and/or Second Notice.

Major Nonconformance. See FAR subpart 46.101 for definition. An example of a major nonconformance for this SWAN Support requirement would be to fail to perform the actions necessary to maintain the SWAN system’s ATO. The PCO will communicate a major nonconformance on a Corrective Action Request (CAR) form with a suspense date for the contractor’s corrective action plan. As a minimum, the contractor’s corrective action plan shall address:

A. A description of the incident/problem B. Root cause analysis of the problem C. All causes of the incident/problem D. Action taken to fix the immediate problem E. Corrective action taken to fix the cause of the problem and to return to Satisfactory levels with target dates for implementation.

F. Actions taken to prevent recurrence G. Follow-up actions to ensure corrective actions are effective

5.5.2 Scope Changes

Any matter concerning a change to the scope, prices, terms or conditions of this task order shall be referred in writing to the PCO and not the government PM or the COR.

5.6 Meeting Participation

Contractor personnel shall support SWAN-related meetings convened at the direction of the applicable COR. The Contractor shall provide information in support of meetings and briefings in the format requested by the Government.

5.7 Administrative Records

All records, documents, and associated papers provided by the Government and/or generated by the contractor during the period of this task order become government property and will remain in place upon contract termination or completion. During the period of the task order, records, documents, and associated papers shall be available for review. All items must be maintained in accordance with AFI 33-322 Records Management Program requirements. Contractors who perform roles associated with records management as defined in AFI 33-322 must fully comply with the duties for their assigned role.

5.8 Safety

The applicable Occupational Safety and Health Act (OSHA) standards (https://safetyculture.com/topics/osha-standards/) will be mandatory for this contract task order. The contractor shall comply with all federal, state and local laws concerning safety. The contractor shall ensure that contractor personnel are properly trained on the equipment they are tasked to operate.

6 Appendices A. Performance Tasks B. Deliverables C. Services Summary D. Acronyms and Definitions E. Applicable Publications and Forms F. Table of Locations

Appendix A - Performance Tasks

Appendix B – Deliverables

The deliverables in this table are not separately priced.

Due Date: To be completed within 10 business days of Task Order award.

Details: The contractor’s PM shall schedule and coordinate a Project Kick-Off Meeting at a location approved by the Government, or virtually, within ten (10) business days after date of task order start. The kickoff meeting will be with the members of the Government Program Management Office (PMO), the Contracting Officer’s Representative(s) (COR(s)) and other officials as designated by the Government. It shall provide the opportunity to discuss technical, management, and security issues, travel authorizations, and reporting procedures.

Due Date: The 15th of every month Details:

Monthly Activity Report – The contractor shall provide one Monthly Activity Report for Task Order by the 15th of every month. If the 15th occurs on a weekend or holiday, then the contractor shall provide the Report the previous business day. Report to reflect major accomplishments, projected major tasks, and identified risks for each requirement and all applicable Tasks outlined in the PWS.

Deliverable includes:

-Monthly Activity Report in a PDF signed by the contractor PM and approved by the COR.

Due Date: The contractor shall provide the TOMP within 30 calendar days after Task Order start and as required thereafter.

Details:

This TOMP shall be issued with the greatest level of detail and estimation of need available at the time of issuance. Efforts of cooperation between the Government and the contractor/team members shall consider government concerns identified in weekly tasking meetings and Task Order (TO) priorities. The contractor shall develop a Quality Control Plan (QCP) as part of the TOMP that demonstrates how the contractor shall maintain an inspection system acceptable to the Government that covers the services under this task order.

Deliverable includes:

-The contractor shall provide the TOMP as a PDF or Word document signed by both contractor and the government stakeholder.

Due Date: This must be started at least 45 calendar days before the end date of the task order.

Details: Prior to the end of the Task Order’s PoP, the incumbent Contractor shall support a forty-five (45) calendar days transition period with the in-coming Contractor. During this period, all programs, information, data, etc. will be passed from the incumbent Contractor to the incoming Contractor so that there is no break in customer support. The Contractor shall maintain continuity folders for each contract position. Folders shall detail the routine duties performed, status of current projects, and a point of contact list for both routine duties and project coordination. Folders shall be maintained and be available for Government review throughout the performance of the contract and be provided to the in-coming Contractor during the transition period

Deliverable includes:

- All programs, information, data

- Continuity folders for each contract position

Appendix C – Service Summary and Method of Surveillance

Performance standards are specified in the Services Summary Table below:

System Sustainment & Upgrades

Appendix D – Acronyms Acronyms

Appendix E - Applicable Publications and Forms

Publications (to include their supplements at any organizational level) and forms that apply to this PWS are listed below. The publications and forms have been coded as mandatory or advisory. The contractor is obligated to follow those publications and use those forms coded as mandatory to the extent specified in other sections of this PWS. The contractor shall be guided by those publications or use those forms coded advisory to the extent necessary to accomplish requirements in this PWS. Supplements or amendments to listed publications from any organizational level may be issued during the life of the task order. The contractor shall immediately implement those changes that result in a decrease or no changes in the task order price and notify the PCO in writing of such changes. Before implementing any change that will result in an increase in price, the contractor shall submit to the PCO a price proposal within 30 calendar days following receipt of the publication change. The PCO and the contractor shall negotiate the change into the task order under the provisions of the clause entitled “Changes”. Failure of the contractor to submit a price proposal within 30 calendar days following receipt of the publication change entitles the Government to performance according to such change at no increase in task order price.

RFO, R-DFARS

M

DoD 5000 Series

M

Joint Travel Regulation (JTR)

M

DD-254

National Industrial Security Program Operating Manual (NISPOM)

M

DoD Operations Security (OPSEC) Program & Manual

AFI 31-101

AFMAN 33-326

Appendix F – Table of Locations

Los Angeles AFB, California (In person)

National Capital Region (In person)