Performance Work Statement.pdf

PERFORMANCE WORK STATEMENT (PWS)

for

Tactical Missile Technical Coordination Group (TMTCG) and

Joint Munitions World Wide Review (JMWWR) Website Hosting

Purchase Request: F3QLC25351A001

21 May 2026

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 2 of 15

1.0 Description of Services. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to provide hosting services for the Tactical Missile Technical Coordination Group (TMTCG) and Joint Munitions World Wide Review (JMWWR) websites as defined in this Performance Work Statement (PWS). The Contractor shall provide services to the standards in this contract. The Government shall not exercise 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 Objective(s). This Performance Work Statement (PWS) describes the services required to obtain secure, high-availability, lossless, and rapidly recoverable hosting services for the TMTCG and JMWWR websites supporting critical Foreign Military Sales (FMS) support roles.

1.2 Benefit to United States Air Force (USAF). This acquisition will benefit the United States Air Force (USAF) by providing greater flexibility, streamlining program management processes, and optimizing support for FMS customers. This acquisition benefits the warfighter by providing critical system technical support while increasing system management, administrative, and technical capabilities across multiple mission sets.

1.3 Background. The TMTCG and JMWWR websites have historically (for the past five [5.75] years; from May 2020 to January 2026) been hosted via Amazon Web Services (AWS) via an Engineering, Professional, and Administrative Support Services (EPASS) contract with Credence Management Solutions (FA8721-20-F-0001 & FA8721-25-F-B001). The CO for this EPASS contract has determined that hosting services are now not within the scope of the contract; thus, the decision has been made to remove these services from the EPASS contract and to instead obtain these services via a separate contract (this contract). Non-hosting-related services (i.e., website maintenance, programming, etc.) shall continue via the current EPASS contract with Odyssey Consulting Group, Ltd (FA8721-26-F-B001).

1.3.1 Current TMTCG website application specifications are outlined in Table 1. The hosting environment shall meet or exceed these specifications as necessary to meet current standardized best practices according to Appendix 6.1 and maintain sufficient room for future growth, which is anticipated to be approximately 73 GB of data/files per year.

Front-End Server Type & Version IIS 10, MS Hyper-V Server 2019

Back-End Server Type & Version SQL Server 15

Database Table Structure 70 tables

Concurrent Users Supported 50

Average Concurrent Users 3

Maximum Concurrent Users 50

Total Footprint (MB/GB) Database 3 GB, Site 178 MB

Avg. Throughput/Month (MB/GB) Avg. Inbound/month 110 MB | Avg. Outbound/month 168 MB

Max. Throughput/Per Month (MB/GB) Total Inbound/month 4 GB | Total Outbound/month 6 GB

Table 1 - Current TMTCG Website Application Specifications

P a g e | 3 of 15 PR: F3QLC25351A001 PWS REVISION 0

1.3.2 Current JMWWR website application specifications are outlined in Table 2. The hosting environment shall meet or exceed these specifications as necessary to meet current standardized best practices as specified in Appendix 6.1 and maintain sufficient room for future growth, which is anticipated to be insignificant, as this website is static.

Front-End Server Type & Version IIS 6.2, Windows Server 2012 R2

Back-End Server Type & Version SQL Server 11

Database Table Structure 29 tables

Concurrent Users Supported 50

Average Concurrent Users 3

Maximum Concurrent Users 50

Total Footprint (MB/GB) Database 11 MB, Site 154 MB

Avg. Throughput/Month (MB/GB) Avg. Inbound/month 59 MB | Avg. Outbound/month 93 MB

Max. Throughput/Per Month (MB/GB) Total Inbound/month 2 GB | Total Outbound/month 3 GB

Table 2 - Current JMWWR Website Application Specifications

1.3.3 The hosting environment shall be capable of processing and/or storing documents of all types and sizes. Table 3 contains a representative sample of typical file types and sizes in use by the Government and its customers.

Extension File Type Number of Files1

Maximum File Size2

Required Storage3

.docx Microsoft Word Document 14,801 105.5 MB 1,561,505.50 GB

.pdf Adobe Portable Document Format 1,591 95.4 MB 151,781.40 GB

.jpg Joint Photographic Experts Group 3,760 9.3 MB 34,968.00 GB

20,152 1,748,254.90 GB

Table 3 - File Extensions, Types, Quantities, Maximum File Size, and Required Storage

NOTE 1: Approximated by counting the number of files with this extension within the sampling.

NOTE 2: The largest file size in megabytes (MB) within the sampling of files with this extension.

NOTE 3: Approximated by multiplying the number of files by the largest file size in megabytes (MB) within the sampling of files with this extension divided by 1,000 to get gigabytes (GB).

1.3.4 Data Rights. The Government shall have unlimited rights to all documents and materials produced under this contract. All documents and materials, including the source code of any web content and/or software produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership and copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the CO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.3.5 Organizational Conflicts of Interest (OCI). Contractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCI as defined in the FAR Subpart 9.5. The Contractor shall notify the CO

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 4 of 15 immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI.

The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2.0 Services Summary.

Performance Objective PWS Reference Performance Threshold

Website accessibility 4.0.1 4.0.2 https://www.tmtcg.org: There shall be no more than two (2) hours of unplanned interrupted service within any one (1) twenty-four (24) hour period.

https://www.jmwwr.org: There shall be no more than four (4) hours of unplanned interrupted service within any one (1) twenty-four (24) hour period.

Website security 4.0.5 There shall be zero (0) successful intrusions resulting in unauthorized access to or retrieval of information contained within either of the two (2) websites.

Receipt of CDRL deliverables 4.2.4 There shall be no more than two

(2) late submission within any one (1) twelve (12) month period.

Quality of CDRL deliverables 4.2.3 There shall be no more than two

(2) rejected deliverables within any one (1) twelve (12) month period.

The Government will reject a deliverable if more than one (1) technical error or more than two

(2) minor errors shall be cause for rejection.

The rejected deliverable shall be corrected and resubmitted within two (2) business days of notification of Government rejection.

Requests for assistance 4.0.14.1 4.0.14.2

The Contractor shall initially respond to a request for assistance within six (6) business hours.

Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

There shall be no more than one

(1) late submission within any one (1) three (3) month period.

Website data integrity 4.0.5 There shall be no inadvertent loss or modification of website data (e.g., accidental deletion, theft, intrusion).

Table 4 - Performance Objectives, References, and Thresholds https://www.tmtcg.org/ https://www.jmwwr.org/

P a g e | 5 of 15 PR: F3QLC25351A001 PWS REVISION 0

3.0 Government Property.

3.1 Contractor Responsibility. The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided. Government property to be provided includes Government furnished information, consisting of the files, datasets, electronic records, etc.

contained within two websites.

3.3 Reporting of Government Property. The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.4 Reporting Loss of Government Property. The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.5 Return or Retention of Government Property. All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements.

4.0.1 The TMTCG website is one of the organization’s primary means of communicating with its FMS customers and must be operational on a continuous basis with no unplanned disruptions of operation, lasting longer than two (2) hours within any one twenty-four (24) hour period. This website shall be accessible at https://www.tmtcg.org.

4.0.2 The JMWWR website is used to coordinate and share information related to annual JMWWR events and must be operational on a continuous basis with no unplanned disruptions of operation, lasting longer than four (4) hours within any one twenty-four (24) hour period. This website shall be accessible at https://www.jmwwr.org.

https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/ https://www.tmtcg.org/ https://www.jmwwr.org/

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 6 of 15

4.0.3 The Government shall use the performance objectives listed in Table 4 as Performance Requirement Standards (PRS), to measure the Contractor’s performance. Service requirements are summarized into performance objectives that relate directly to mission essential items. Each PRS is listed with references throughout the PWS. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

4.0.4 Scope. The Contractor shall provide non-personal services, including organic or purchased hosting for two websites with appropriate hardware and software security features entailing full lifecycle services such as: 1) Cloud setup, 2) 24/7 monitoring, 3) backups, 4) patching, 5) fail-over, and 5) vulnerability remediation. The Contractor shall maintain all hardware, software, and licenses required to support the hosting of two websites. The Contractor shall submit timely reports and/or datasets pertaining to website hosting as prescribed in Paragraph 4.2.1, Table 5.

4.0.5 The Contractor shall monitor the security of server(s) and the hosting environment (physical and virtual) using appropriate intrusion detection and mitigation methods to prevent and/or substantially limit the impact of intrusions. There shall be zero (0) successful intrusions resulting in unauthorized access to or retrieval of information contained within either of the two (2) websites.

There shall be no inadvertent loss or modification of website data (e.g., accidental deletion, theft, intrusion). The Contractor shall submit timely reports and/or datasets pertaining to server security as prescribed in Paragraph 4.2.1, Table 5.

4.0.6 Administrator credentials shall be created and/or shared with Contractor employees working under another contract as specified in Paragraph 1.3 and as identified by the Contracting Officer (CO) and/or Contracting Officer’s Representative (COR; if applicable).

4.0.7 The Contractor shall collaborate with other Contractor(s) as needed to affect appropriate and efficient non-hosting-related web development activities. Such collaboration shall be transparent to the Government unless it fails or begins to affect the production of desired results, at which time the CO, COR, and other Government personnel, as appropriate, shall be notified in writing immediately.

4.0.8 The Contractor shall not perform non-hosting-related tasks (i.e., website maintenance, programming, etc.). As specified in Paragraph 1.3, these tasks shall be performed by other Contractor(s).

4.0.9 Modernization and/or refactoring of existing application code is not anticipated; however, the Contractor should be prepared to surge as needed in the event such work becomes necessary.

The Contractor may propose modernization options to the Government during the phase-in period or at any time during any Period of Performance (PoP).

4.0.10 The Contractor shall perform quarterly backup/restore tests and semi-annual disaster recovery exercises and report results to the Government as prescribed in Paragraph 4.2.1, Table 5.

4.0.11 The Contractor shall ensure its employees performing work on this contract possess and/or maintain the following:

P a g e | 7 of 15 PR: F3QLC25351A001 PWS REVISION 0

4.0.11.1 current Information Assurance Technician (IAT) Level II professional certification during the execution of this contract;

4.0.11.2 a minimum of eight (8) years of experience in the operation and maintenance of web hosting environments;

4.0.11.3 the following skills and qualifications; and

• Ability to clearly communicate with clients and to troubleshoot and optimize server performance.

• Ability to configure server environments to accept and operate with the Government’s Existing and future website content.

• Experience in planning and delivering worldwide accessible web/software platforms.

• Understanding of security principles and how to apply them to web servers/applications.

4.0.11.4 familiarization with the following site-specific technologies:

• Cold Fusion 6

• SQL Server 2008 / 2012

• Entity Framework ASP.NET Core

• C#

• Model View Controller (MVC)

• Internet Information Services (IIS)

• Bootstrap 4

4.0.11.5 Past performance may be used to meet the above experience requirements at the discretion of the CO/COR and/or Program Manager (PM) via written correspondence.

4.0.12 Phase-In/Phase-Out (PIPO) Periods. To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during a 30-day phase in/phase out period. During the phase in period, the new Contractor shall become familiar with performance requirements to commence full performance of services on the PoP start date. During this period, the Government shall provide or authorize the provision of full access to any existing website hosting environments, database schema, and configuration and source files to promote a clean and secure migration.

4.0.13 Specific Tasks.

4.0.13.1 Basic Services. The Contractor shall provide services suitable for the hosting of two websites.

4.0.13.2 Hosting Services. The Contractor shall ensure hosting services are equipped with the necessary hardware and/or software security features that address the following:

• Host o Maintaining development, test, and production environments

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 8 of 15 o Securing data and services o Protection from denial of service (DoS), cross-site scripting, SQL injection, and other attacks o Deactivating and disabling unused services and ports o Employing encryption where possible o Isolation of application data o Minimizing and managing permissions and privileges o Installation of security patches o Monitoring and auditing of server logs o Minimizing and managing user accounts o Removal of unused modules and extensions o Using server security tools o Strong password enforcement

Length of 12 or more characters Mix of uppercase and lowercase letters, numbers, and symbols No dictionary words, name, or personal information Change every 90 days

• Network o Firewall o Intrusion detection/prevention system(s)

• Physical o Secure location o Access control o Surveillance o Hardware security o Environmental controls o Disaster recovery o Encryption at rest o Intrusion detection

4.0.14 Help Desk Requirements. There are no specific ‘Help Desk’ requirements; however, the Contractor shall be prepared to accept feedback/input and take timely and appropriate action to address the needs of the Government as pertaining to this contract.

4.0.14.1 The Contractor shall initially respond to a request for assistance within six (6) business hours.

4.0.14.2 Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government. There shall be no more than one (1) late submission within any one (1) three (3) month period.

4.0.15 Deliverables. The Contractor shall submit deliverables to the Government as prescribed in Paragraph 4.2, Table 5.

P a g e | 9 of 15 PR: F3QLC25351A001 PWS REVISION 0

4.0.16 Meetings. The Contractor shall participate in regularly scheduled meetings with Government representatives, to include the COR and others as deemed necessary by the Government.

4.0.16.1 Meetings shall be virtual via Microsoft Teams, telephone, or other Government- or Contractor- provided means.

4.0.16.2 The following meetings shall be considered normally scheduled meetings:

4.0.16.2.1 Monthly expenditure and funding review.

4.0.16.2.2 Bi-weekly hosting status and deliverables review.

4.0.16.3 Other meetings shall occur on a non-routine basis as needed and as agreed to between the Government and Contractor.

4.1 Period and Place of Performance (PoP).

4.1.1 Contract/Order PoP. The PoP shall be for one (1) Base Year of 12 months and four (4) 12-month option years.

4.1.2 Place of Performance. The services to be performed under this contract shall be performed within the Continental United States (US) (CONUS) at any place or location deemed suitable by the Contractor and CO/COR. There is no requirement for performance of work related directly to website hosting at a Government facility. Remote work is acceptable.

4.2 Contract Data Requirements List(s) (CDRL).

4.2.1 Reports and other documentation that are required as a deliverable from the Contractor are listed in Paragraph 4.2.1, Table 5. A deliverable is anything that can be physically delivered or non-physical things such as electronic data and documents.

BY

ID

OY1

ID

OY2

ID

OY3

ID

OY4

ID

DID Title PWS

A001 B001 C001 D001 E001 DI-MISC-80508B/T Server Access Log(s) 4.0.5 A002 B002 C002 D002 E002 DI-MISC-80508B/T Server Security Log(s) 4.0.5 A003 B003 C003 D003 E003 DI-MISC-80508B/T Server Error Log(s) 4.0.4 A004 B004 C004 D004 E004 DI-MISC-80508B/T Server Audit Log(s) 4.0.5 A005 B005 C005 D005 E005 DI-MISC-80508B/T Server Referrer Log(s) 4.0.4 A006 B006 C006 D006 E006 DI-MISC-80508B/T Server Agent Log(s) 4.0.4 A007 B007 C007 D007 E007 DI-MISC-80508B/T Intrusion Report(s) 4.0.5 A008 B008 C008 D008 E008 DI-MISC-80508B/T Intrusion After Action Report(s) (AAR) 4.0.5 A009 B009 C009 D009 E009 DI-MISC-80508B/T Server Uptime Log(s) 4.0.4 A00A B00A C00A D00A E00A DI-MISC-80508B/T Server Patch Report(s) 4.0.4 A00B B00B C00B D00B E00B DI-MISC-80508B/T Backup/Restore Test Report(s) 4.0.10 A00C B00C C00C D00C E00C DI-MISC-80508B/T Disaster Recovery Report(s) 4.0.10 A00D B00D C00D D00D E00D DI-QCIC-81794A Quality Assurance Program Plan(s) (QAPP) 5.9 A00E B00E C00E D00E E00E DI-MGMT-82253 Mission-Essential Contractor Services Plan(s) 5.1.2.1

Table 5 - Contract Data Requirements List (CDRL)

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 10 of 15

4.2.2 Data deliverables shall be ‘as downloaded/extracted’, in comma-separated text format, remain in raw form, and may be bundled as appropriate when within file size limitations of delivery medium/format. E-mailed deliverables shall be forwarded to the COR (use appropriate e-mail addresses) and PM (AFLCMC.EBUIF.TMTCG@us.af.mil). E-mail or file encryption is not necessary.

4.2.3 Quality of CDRL Deliverable. There shall be no more than one rejection of any deliverable.

There shall be no more than two (2) total rejection(s) of deliverables per one twelve (12) month period. The Government shall reject a deliverable if one (1) or more technical errors or two (2) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within two (2) business days of notification of Government rejection.

4.2.4 Receipt of CDRL Deliverable. CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) and submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. Separately priced data must be submitted and accepted in WAWF for the Contractor to receive payment. There shall be no more than two (2) late submission(s) of deliverables per one twelve (12) month period. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Holidays and Facility Closings. Contractor personnel shall observe holidays and facility closings as authorized for Government personnel. Contractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.4 Travel. There are no travel requirements under this contract.

5.0 General Information.

5.1 Continuation of Mission-Essential Services During a Crisis.

5.1.1 Designation of Services as Mission-Essential. The Functional Commander/Director has determined certain services under this contract/order are mission-essential and will continue in the event of a crisis. The designation of services as mission-essential will apply to the entire contract but will apply only to services specifically identified as mission-essential by the Government. The mission-essential services under this contract/order include the website hosting services described herein.

5.1.2 Mission-Essential Contractor Services Plan.

5.1.2.1 The Contractor shall submit a plan as prescribed in Paragraph 4.2.1, Table 5 describing procedures for continuing performance of mission-essential services during a crisis. The Contractor shall identify provisions for ensuring required personnel and resources are available to mailto:AFLCMC.EBUIF.TMTCG@us.af.mil

P a g e | 11 of 15 PR: F3QLC25351A001 PWS REVISION 0 support continuity of operations for up to 30 calendar days or until normal operations can be resumed. The Contractor shall submit any revision to the plan for approval prior to implementation. The Contractor shall activate the plan only when authorized by the CO acting under the direction of the Commander/Director.

5.1.3 If the Contractor anticipates not being able to perform the mission-essential services, they shall notify the CO as soon as possible and fully cooperate with the Government’s efforts to maintain continuity of operations.

5.2 Security Requirements.

5.2.1 Security Regulations. The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor personnel who perform work on a Government facility comply with the security requirements of the facility.

5.2.2 Security Clearance. It is not expected that Contractor personnel will require security clearances for proper accomplishment of contract/order requirements. Contractor personnel shall not be authorized access to classified information and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.3 Access to Government System(s). Access to Government system(s) will not be required to perform tasks under the contract/order.

5.2.4 Security Incident or Violation. The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.5 The Contractor shall be responsible for safeguarding all Government property provided for Contractor use, to include website source code and artifacts.

5.3 Environmental Management System (EMS). These services shall not be performed at a Government facility; therefore, the EMS requirement does not apply.

5.4 Agency Affirmative Procurement Programs. This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements.

5.5.1 Contractor Environmental, Safety, and Occupational Health Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall require all subcontractors to comply with required safety, health and fire standards.

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 12 of 15

5.6 Inspection of Services. In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Service Contract Reporting (SCR). The contract does not meet the Department of War (DoW) contract reporting criteria or reporting dollar threshold; therefore, SCR does not apply.

5.8 Invoicing/Payment and Receipt/Acceptance. The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.9 Quality Control Plan/Quality Management System (QMS). The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) as prescribed in Paragraph 4.2.1, Table 5 addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required.

5.9.1 The Government shall evaluate the Contractor’s performance under this contract according to its Quality Assurance Surveillance Plan (QASP). 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).

5.10 Trafficking in Persons. The Contractor shall comply in accordance with the FAR and applicable supplements and shall follow all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons (https://www.state.gov/).

5.11 Key Personnel. Key personnel are listed in Table 6. The Contractor shall provide a Contract Manager who shall be responsible for the performance of work on this contract. The name of this person and an alternate who shall act on behalf of the Contractor when the Contract Manager is absent shall be designated in writing to the CO/COR. The Contract Manager or alternate shall have full authority to act on behalf of the Contractor on all contract matters relating to the daily operations of this contract.

Government Contractor CO/COR Contract Manager TMTCG Section Chief Alternate Contract Manager TMTCG Program Manager Program Manager/Team Lead

TMTCG IT SME

TMTCG Website User(s)

Table 6 - Key Personnel https://www.state.gov/

P a g e | 13 of 15 PR: F3QLC25351A001 PWS REVISION 0

6.0 Appendices.

6.1 Appendix A, Reference(s).

6.1.1 The Contractor shall abide by all applicable laws, regulations, publications, manuals, local policies, and procedures.

6.1.2 The Contractor shall adhere to current generally accepted and standardized website hosting and security best practices, to include but not limited to:

6.1.2.1 World Wide Web Consortium (W3C) standards, technical specifications, and guidelines.

6.2 Appendix B, Definitions and Acronyms.

6.2.1 Definitions.

CONTRACTOR – A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

CONTRACTING OFFICER – A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

CONTRACTING OFFICER’S REPRESENTATIVE (COR) – An employee of the U.S.

Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

DEFECTIVE SERVICE – A service output that does not meet the standard of performance associated with the PWS.

DELIVERABLE – Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

KEY PERSONNEL – Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the key personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the people that are listed in the proposal.

PHYSICAL SECURITY – Actions that prevent the loss or damage of Government property.

QUALITY ASSURANCE – The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

PR: F3QLC25351A001 PWS REVISION 0 P a g e | 14 of 15

QUALITY ASSURANCE PROGRAM PLAN – An organized written document specifying how the Contractor shall measure its own performance.

QUALITY ASSURANCE SURVEILLANCE PLAN – An organized written document specifying the surveillance methodology to be used for surveillance of Contractor performance.

QUALITY CONTROL – All necessary measures taken by the Contractor to assure that the quality of a product or service shall meet contract requirements.

SUBCONTRACTOR – One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

WORK DAY – The number of hours per day the Contractor provides services in accordance with the contract.

WORK WEEK – Monday through Friday, unless specified otherwise.

6.2.2 Acronyms.

AFOSI Air Force Office of Special Investigations AWS Amazon Web Services BY Base Year CDRL Contract Data Requirements List CO Contracting Officer CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative DAF Department of the Air Force DID Data Item Description DISA Defense Information Systems Agency DoS Denial of Service DoW Department of War EMS Environmental Management System EPA Environmental Protection Agency EPASS Engineering, Professional, and Administrative Support Services FAR Federal Acquisition Regulation FMS Foreign Military Sales GB Gigabytes JMWWR Joint Munitions World Wide Review IAT Information Assurance Technician IAW In Accordance With IIS Internet Information Services IT Information Technology MB Megabytes MS Microsoft MVC Model View Controller OY Option Year

P a g e | 15 of 15 PR: F3QLC25351A001 PWS REVISION 0

OCI Organizational Conflict of Interest PRS Performance Requirement Standard PIPO Phase-In/Phase-Out PM Program Manager PoP Period of Performance PR Purchase Request PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAPP Quality Assurance Program Plan QASP Quality Assurance Surveillance Plan SCR Service Contract Reporting SME Subject Matter Expert SQL Structured Query Language TMTCG Tactical Missile Technical Coordination Group US United States USAF United States Air Force USDA United States Department of Agriculture W3C World Wide Web Consortium WAWF Wide Area Work Flow