- Attached to
- 30 RS Mission Planning Software Tool (MPST)
- Solicitation number
- F3G1EB6257AG01
About this file
This is a Performance Work Statement (PWS) for software maintenance services supporting the RQ-170 aircraft program at Headquarters Air Combat Command.
The contractor shall provide remote and on-site software maintenance and support for the Mission Planning Support Tools (MPST) and Advanced Framework for Simulation, Integration and Modeling (AFSIM), serving the 30 Reconnaissance Squadron at Creech Air Force Base, Nevada. Primary work performance occurs at the contractor's facility in Rapid City, South Dakota, with periodic on-site visits to Creech AFB and other classified locations. All on-site personnel require Top Secret/SCI/SAP clearance and U.S. citizenship. Key deliverables include maintaining MPST software and custom databases; creating and maintaining a threat database usable by AFSIM updated semi-annually; providing software upgrades for Windows 10 and subsequent operating versions; delivering current documentation and training materials; providing two annual training sessions for up to ten individuals per session; conducting two working group and two technical interchange meetings annually; and developing an AFSIM threat library with updates twice yearly. The contractor must respond to support requests within one business day and complete standard modifications within 14 days of request, unless mission requirements dictate shorter timelines. The contract runs for one base year with four option years beginning November 30, 2026, with an estimated two trips annually to Creech AFB lasting three days each. Upon contract conclusion, the contractor must deliver comprehensive transition materials including the government-owned threat database in non-proprietary format, database schema documentation, complete AFSIM custom component source code with version history, build environment instructions, and detailed interface control documentation to enable independent government management of AFSIM and the threat database.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 30 RS MPST Combo - Revised - General.pdf | ||
| 30 RS MPST Combo - Revised.pdf | ||
| dd0254 Draft.pdf | ||
| MPST AFSIM PWS.pdf |
On GovTribe
Work with this file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Headquarters Air Combat Command (HQ ACC)
Multi-Role Reconnaissance Operations Division (ACC/A3M)
Performance Work Statement (PWS)
For
RQ-170 Mission Planning Support Tools (MPST) and
Advanced Framework for Simulation, Integration and Modeling (AFSIM)
Software Maintenance Services
FA486121C0028
17 October 2026
Performance Work Statement (PWS)
1. Mission. Provide software and database maintenance and support functions to the 30 RS for the Mission Planning Support Tools (MPST) and Advanced Framework for Simulation, Integration and Modeling (AFSIM).
1.1. Scope. This PWS defines the effort required by the contractor for support of MPST and
AFSIM. The contractor shall provide timely remote and periodic on-site support to the 30RS for
MPST and AFSIM. The contractor will maintain compatibility with upgrades to the RQ-170 mission planning system software, hardware, operating systems and databases. The contractor will utilize current intelligence products to inform updates with the software and AFSIM threat database. The contractor will accurately represent new and/or improved aircraft capabilities, correct errors, ensure compatibility with AFSIM, and address limitations encountered during operational use of the MPST software. This includes providing personnel, services, and management support to accomplish these objectives.
2. General Requirements. The contractor shall provide software programming support for
MPST computer program and its integration with AFSIM. All individuals performing on-site on this PWS must have a current adjudicated background investigation and be eligible for access to
Top Secret, SCI, SAP information and associated ACCMs. Contractor personnel shall be conversant in the computer programming skills to fully support MPST, the version of AFSIM used by the RQ-170 simulator, be familiar with RQ-170 aircraft survivability, capabilities, Blue/Gray/Red ground and airborne threat systems, and Suppressor modeling capabilities/architecture/function/programming. Suppressor model may contain Foreign
Government Information. The contractor shall provide support in training in the use of the version of AFSIM currently being used by the RQ-170. Actual work performance location is the contractor facility with periodic on-site visits to Creech AFB, NV and other classified locations as determined by the government. Support personnel shall provide support within one business day (Monday-Friday excluding Federal Holidays) from when the request is made by either telephone or email when working from the contractor’s facility. The period of performance will be for one base year with 4 option years beginning 30 November 2026. Standard turnaround time for modifications shall be within 14 days of request from the Contract Officer Representative
(COR), unless mission requirements dictate a shorter timeline.
2.1. Non-Personal Services. The Government shall neither supervise individual 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. It shall be the responsibility of the contractor to manage its employees and to 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, it shall be the contractor’s responsibility to notify the Contracting
Officer (CO) immediately.
2.2. Business Relations. The contractor shall successfully integrate and coordinate all activity needed to execute the requirement. The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors
(See Services Summary Table 3.1). The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel. The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement.
2.3. Personnel Administration. The contractor shall provide the following management and support as required. It is expected that the contractor will provide support during designated/specified Government non-workdays or other periods where Government offices are closed due to training requirements or security conditions. Additionally, the government will be closed for all permitted US Federal Holidays and contractor support would not be required on those days. The contractor shall maintain the currency of their employees by coordinating initial and refresher training to meet any contract security requirements with responsible agencies as required to meet the PWS requirements. US Citizenship required.
2.4. Subcontract Management. The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations.
2.5. Contractor Personnel, Disciplines, and Specialties. The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience.
2.6. Contractor Identification in the Government Workspace. All contractor and subcontractor personnel shall be required to wear visitor identification badges while performing on-site support visits. When conversing with Government personnel during business meetings, over the telephone, or via electronic mail, contractor and subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors and subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signatures shall identify company affiliation.
2.7. Location and Hours of Work. The contractor’s work schedule shall be flexible as required to meet the needs of the Air Force, which means available for “on call” work. The primary place of performance is at the contractor’s facility in Rapid City, SD as listed in the
DD254. The hiring of individual contractor personnel required to support this contract are at the discretion of the contractor as long as the candidates meet all of the requirements listed in this document. As such, employee work hours are unspecified. Work performance will be measured by timely adherence to agreed-upon support functions inherent in this contract (software patch or usability improvements, delivery and updating of documentation, training materials, etc.) and the
1 business day response time to telephone or email support requests. Support/training on-site visits will be of a duration agreed upon by the Government and contractor personnel to accomplish the pre-arranged support goals (training, patch/upgrade installation, new capability integration, etc.)
2.8. Travel. The Contractor may be required to travel based on the current travel projections listed in Travel Table 1. Any additional or changed travel requirements will be considered a change to the contract and be subject to a request for equitable adjustment.
Table 1 – Travel
Origin
Destination Number of
Travelers
Number of
Trips per
Year
Number of
Days Per
Trip
Contractor Facility Creech AFB, NV 2 2 3
2.9. Contractor Manpower Reporting. The contractor shall report all contractor labor hours
(including subcontractor labor hours) required for performance of services under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/ Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.
2.9.1. Mission Planning Support Tools. The Contractor shall provide a sufficient number of contract employees to meet the support requirements of the contract, i.e. meet agreed upon deliverable timelines and one business day response to support requests by the 30RS at Creech
AFB, NV. All contractor employees providing onsite services required by this contract shall maintain Top Secret/SCI/SAP-SAR clearances commensurate with work associated with the RQ-
170 and all aspects of survivability and mission planning for the aircraft.
2.9.1.1. The contractor shall:
2.9.1.1.1. Maintain MPST software and custom databases.
2.9.1.1.2. Create and maintain a threat database that is useable by AFSIM that will be updated by customer request on a semi-annual basis.
2.9.1.1.3. Provide software upgrades to improve ease of use, reliability, maintainability, or combability with AFSIM.
2.9.1.1.4. A Windows 10 version, followed by additional Windows operating versions as required.
2.9.1.1.5. Provide current/updated documentation and training materials for MPST application.
2.9.1.1.6. Upgrade/update the applications if database, mission planning systems or aircraft capabilities change.
2.9.1.1.7. Participate in meetings and working groups that impact the use/function of MPST.
2.9.1.1.8. Plan on two (2) Working Group plus two (2) technical interchange meetings annually. Topics of these meetings will include bugs, flaws, shortfalls, or other un-met expectations requested by the customer. Meeting should be pre-planned on a semi-annual basis with the option for a short-notice by need request if required.
2.9.2. Advanced Framework for Simulation, Integration and Modeling
2.9.2.1. The contractor shall:
2.9.2.2. Plan to provide two (2) training sessions on use of AFSIM per year. These training sessions will include operator use, troubleshooting and integrated functions with MPST and other software inherent to RQ-170. Training sessions will be designed for a group of ten (10) individuals per training session.
2.9.2.3. Provide current/updated documentation and/or training materials for AFSIM.
2.9.2.4. Develop a threat library for AFSIM and provide updates two (2) times per year.
2.9.3. Contractor employees associated with this contract shall have a thorough understanding of:
2.9.3.1. Aircraft threat vulnerabilities, capabilities of current fielded threat systems and how to best employ aircraft Radar Cross Section (RCS) characteristics to plan the most survivable route for the aircraft.
2.9.3.2. Function of Suppressor software and its interface with MPST to effectively replicate
RQ-170 and operational threat environment for full MPST function.
2.9.3.3. Familiarity with all current MPST data input sources to resolve any compatibility issues that may arise, maintaining full MPST function, modeling the most realistic operational threat environment.
2.9.3.4. Incorporating supplied Suppressor models for new capabilities or players within the
MPST/Suppressor environment.
3. Services Summary
Table 2 – Services Summary
Performance Objective PWS Para
Performance Threshold
1 Provide response to customer support request within one business day
2.,
2.7 Acknowledgement of a support request shall be delivered
within 1 day of customer communication of request, during normal M-F duty weeks, weekends and federal holidays excluded. If the request is made immediately prior to a weekend or holiday, a response shall be forthcoming during the next available standard duty day.
2 Provide current up-to-date documentation for
MPST Application
2.9. Current documentation/usage manuals will be
provided to accompany initial software distribution and will be kept up-to-date and delivered with any update/maintenance software distributions as performed by the other provisions of this contract.
Documentation/manuals should enable day-to-day use/maintenance without contractor intervention.
3 Update function of MPST software to maintain compatibility/functional status as databases and other inputs to the software are changed or updated
1.1, 2.9.
Contractor support personnel will maintain situational awareness of the status and changes to input data sources to MPST software. Any compatibility issue affecting proper function of the software shall to the maximum extent possible be proactively addressed to avoid loss of capability to the end user. Significant changes to input data sources that will cause capability gaps shall prompt contractor & user meetings to establish mitigation plans and establish timelines for capability restoration.
Standard time to make modifications shall be 14 business days with longer durations requiring notification of the
COR with estimated schedule and delivery date.
4 Create, update and maintain MPST threat library usable by AFSIM
1.1 2.8.
Create and maintain a threat database that is useable by
AFSIM that will be updated by customer request on a maximum of a semi-annual basis.
5 Update function of MPST software to maintain compatibility/functional status as aircraft capabilities change.
1.1, 2.8.
Contractor support personnel will maintain situational awareness of the status and changes of aircraft capability as it relates to MPST software. Any capability issue must be addressed at the earliest opportunity to maintain software capability; reflecting current RQ-170 capabilities including current capabilities. Standard time to make modifications shall be 15 business days with longer durations requiring notification of the COR with estimated schedule and delivery date.
6 Limited updates to MPST software to enhance usability and function
1.1, 2.8., Bugs, flaws, or shortfalls in expected capability of the software will be fixed and delivered with the semi-annual on-site contractor visit. Bugs, flaws, or shortfalls discovered during the on-site visit shall be resolved within the 14 day timeline.
7 Provide semi-annua on-site support as coordinated
2.8, 2.9
The contractor will support on-site visits to assess software function and any other support issues related to the MPST, AFSIM, and their inter-dependencies.
8 Provide semi-annual training sessions on use of AFSIM/MPST.
2.8, 2.9
Plan to provide two (2) training sessions on use of
AFSIM per year. These training sessions will include operator use, troubleshooting and integrated functions with MPST and other software inherent to RQ-170.
Training sessions will be designed for a group of ten (10) individuals per training session.
9 Provide current documentation and/or training on AFSIM.
2.9 Provide current up-to-date documentation and/or training
on AFSIM and it’s integration with MPST.
Documentation/manuals should enable day-to-day use/maintenance without contractor intervention.
4. Special Requirements
Contractor personnel shall present a neat appearance and dress in a professional manner as such is reasonably expected in a professional office setting. The contractor shall wear visitor security badges assigned when performing a site visit. A visit request notice will be sent to the 432 WG Advanced Program Office security manager prior to any site visit via applicable classified networks.
4.1. The Government will provide general office supplies and appropriate workspace.
The government will provide access to an unclassified and SIPRNET and program-level computers as required in the workspace. The Government will provide access to databases required for duty performance.
4.2. Security
The Contractor and all contractor personnel shall abide by all Air force and local rules, procedures and standards of conduct. A Department of Defense Security classification
Specification (DD FM 254) is required for access to classified material. The contractor shall perform in accordance with the National Industrial Security Program Operating Manual
(INISPOM-DoD 5220.22M)
4.2.1. Visitor Group Security Agreement. The contractor shall sign a Contractor Visitor Group
Security Agreement to protect classified information involved in performance under this contract. The Agreement will outline how the contractor integrates security requirements for contract operations with the Air Force to ensure effectiveness and economic operation on the installation. The agreement should address:
4.2.2. Security support provided by Air Force to the contractor to include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations, the use of security forms and conducting inspections required by DoD 5220.22- R (Industrial Security Regulation) and
AFI16-1406 (Industrial Security Program Management).
4.2.3. Security support requiring joint Air Force and contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks and internal security controls for protection of classified material and high value pilferable property.
4.3. Security Clearances.
All personnel performing on this PWS at the government facilities shall be U.S. Citizens and shall have a Top Secret/SCI clearance and be SAP eligible. The contractor must possess or obtain a facility security clearance at the level of Top Secret prior to performing contract work.
If the contractor does not possess a facility clearance the government (Contracting Office) will request one. The government (the Defense Security Service (DSS)) assumes costs and conducts security investigations for Top Secret, Secret, and Confidential facility security clearances. The contractor shall request security clearances (Submit Clearance Paperwork through DSS to the
Office of Personnel Management) for personnel requiring access to classified information within 15 days after receiving a facility clearance or, if the contractor is already cleared, within
15 days after contract award. Due to costs involved with security investigations, requests for contractor security clearances shall be kept to an absolute minimum necessary to perform contract requirements. Contractor personnel shall have appropriate clearances prior to commencing work on any T/O unless otherwise approved in writing by the CO. The Contractor shall also complete visit requests for each individual that will be performing work on a T/O in the Defense Manpower Data Center (DMDC) Joint Personnel Adjudication System (JPAS) prior to performance start unless otherwise approved in writing by the CO. The Prime
Contractor shall ensure that any teaming partners or subcontractors have the appropriate clearances prior to beginning performance.
4.3.1. Contractor personnel program accesses will be managed locally by the 432 WG
Advanced Program (AP) Office Program Security Manager (PSM). This includes all initial and maintenance security requirements specified by applicable personnel security regulations.
4.3.2. Clearance Documentation. Within 10 calendar days of contract award, the Contractor shall provide the Primary COR a list with the names, location of performance and clearance requirements of all company employees assigned to this effort.
4.3.3. Listing of Employees. The contractor shall maintain a current listing of employees.
The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer
(FSO) and provided to the Sponsoring Agencies Security Manager. An updated listing shall be provided when an employee's status or information changes.
4.3.4. Pass and Identification Items. The contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.
4.3.5. Retrieving Identification Media. The contractor shall retrieve all identification media, including vehicle passes from employees who depart for any reason before the contract expires;
e.g. terminated for cause, retirement, etc.
4.3.6. Traffic Laws. The contractor and its employees shall comply with base traffic regulations.
4.3.7. Controlled Unclassified Information (CUI). The contractor shall comply with DoD
5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material.
4.3.8. Reporting Requirements. Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.
4.3.9. Physical Security. The contractor shall be responsible for safeguarding all government property and controlled forms provided for contractor use. At the end of each work period, all government facilities, equipment, and materials shall be secured.
4.3.10. Controlled/Restricted Areas. The contractor shall implement local base procedures for entry to Air Force controlled/restricted areas where contractor personnel will work. An
AF Form 2586, Unescorted Entry Authorization Certificate, must be completed and signed by the sponsoring agencies Security Manager before a Restricted Area Badge will be issued.
4.3.11. Key Control/Access Badge Control. The contractor shall establish and implement methods of making sure all keys/badges issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The contractor shall not duplicate any keys issued by the government.
4.3.12. Lost Keys. The contractor shall immediately report to the Quality Assurance
Evaluator (QAE) or Program Manager any occurrences of lost or duplicated keys. In the event keys, other than master keys, are lost or duplicated, the contractor may be required, upon written direction of the contracting officer, to re-key or replace the affected lock or locks without cost to the government. The government may, however, at its option, replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the government and the total cost deducted from the monthly payment due the contractor.
4.3.13. Prohibited Use. The contractor shall prohibit the use of keys, issued by the government, by any persons other than the contractor’s employees and the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in performance of contract work requirements in those areas.
4.3.14. Lock Combinations. The contractor shall control access to all government provided lock combinations to preclude unauthorized entry. The contractor is not authorized to record lock combinations without written approval by the government Program Manager. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.
4.3.15. Automatic Data Processing Equipment (ADPE). The Contractor shall establish and implement procedures to ensure all ADPE, to include laptops and other data processing devices, issued to the Contractor by the Government are not lost or misplaced, are not used by unauthorized persons or are not subject to unauthorized external devices. The Contractor shall immediately report to the CO or PM any occurrences of lost ADPE within two (2) hours of discovery of occurrence. In the event that ADPE is lost, the Contractor may be required, upon written direction of the CO, to replace the equipment at no additional cost to the Government. The Government may replace the equipment and deduct the cost of such from the monthly payment due the Contractor.
4.3.16. Communications Security (COMSEC). Contractors may require access to COMSEC information. The DD FM 254 will give further instructions on safeguarding and managing
COMSEC material.
4.3.17. Contractor personnel program accesses will be managed locally by the 432 WG
Program Security Manager (PSM). This includes all initial and maintenance security requirements specified by applicable personnel security regulations.
4.4. Transition.
Purpose. This section establishes the requirements for the transition of all Government-owned data, software components, and responsibilities related to the Advanced Framework for Simulation, Integration and Modeling (AFSIM) and the associated Threat Database. The objective is to ensure the Government can independently manage, maintain, and update the
AFSIM integration and the Threat Database at the conclusion of the contract performance period, with no degradation of capability. This plan does not confer any rights to the contractor's proprietary Mission Planning Support Tools (MPST) software.
4.4.1. The contractor shall submit a comprehensive Transition-Out Plan to the Contracting
Officer Representative (COR) no later than 90 days prior to the end of the contract. This plan will detail the orderly transfer of the deliverables and knowledge outlined below.
4.4.2. Transition-Out Deliverables.
Table 3 – Transition Deliverables Summary
Deliverables Description Format
Government-Owned
Threat Database
The complete and current version of the threat database. The data must be delivered in a non-proprietary, open, and machine-readable format (e.g., CSV files) to ensure it can be imported into other systems.
Electronic, via a
Government-approved method.
Threat Database
Schema and
Documentation
Comprehensive documentation detailing the database structure, data schemas, fields, relationships, and data dictionary. This is essential for future development and maintenance.
Electronic, in an editable format (e.g., Microsoft
Word).
AFSIM Custom
Components Source
Code
The complete and latest version of all source code for any plug-ins, scripts, or modules developed or modified specifically to integrate the Threat Database with AFSIM.
This includes its complete version control history (e.g., Git repository).
Electronic, via a
Government-approved method.
AFSIM Component
Build Environment
All scripts and detailed instructions necessary to compile and build the AFSIM custom components from the provided source code. This must include a list of all dependencies and specific environment configurations.
Electronic, as part of the documentation.
Interface Control
Document (ICD)
A detailed document specifying the interface between the Threat
Database and AFSIM. It must define the data flow, API calls, data formats, and protocols used for communication between the two systems.
Electronic, in an editable format.
4.5. Directives.
Maintenance and support of the MPST software requires that the RQ-170 and its virtual environment are accurately replicated. Documents defining the performance of the RQ-170 and threat systems are:
4.5.1. T.O. 1Q-170A-1, RQ-170A Flight Manual
4.5.2. T.O. 1Q-170A-1-1, RQ-170 Performance Manual
4.5.3. AFTTP 3.1, Threat Guide
4.6. Key Personnel
The contractor shall identify the key technical, management, and administrative personnel to be assigned to work under this contract. Support required to fulfill this contract is at the discretion of the Contractor to meet improvement delivery schedules and support request timelines. An individual should be identified as the lead and point of contact for
COR/Contractor communications and notification of any changes in key personnel shall be made to the COR 14 days before transfer of responsibilities.
5. COR Designation
The CO will provide the Contractor with a COR Designation Memorandum to certify there are no potential OCI concerns with the proposed COR. The Contractor shall sign and return the memorandum to the CO within the timeframe designated. If a concern is identified with a potential COR, the Contractor shall provide the CO with justification immediately.
5.1. Performance Evaluation
Contractor performance is subject to Government COR surveillance to ensure PWS compliance.
The Contractor shall comply with the following:
5.1.1. Access. The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, CORs, state, federal, and other designated personnel in the performance of their official duties. Access shall be provided as soon as possible, but not to exceed one (1) workday after the request.
5.1.2. Non-conformances. Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence. Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time frames specified by the CO.
This contract identifies two types of non-conformances: Minor and Major.
5.1.2.1. Minor Non-conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance
(quality), schedule (delivery), or cost. It normally does not increase risk to the Government.
Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non- conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.
5.1.2.2. Major Non-conformance. A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate major non-conformances 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 will address:
5.1.2.2.1. Action taken to fix the immediate problem
5.1.2.2.2. Root cause analysis of the problem to determine cause
5.1.2.2.3. Corrective action on the cause of the problem
5.1.2.2.4. Actions taken to prevent recurrence
6. Deliverables
The Contractor shall provide task order deliverable(s) in a format mutually agreed upon by the
Government and the Contractor. The 99th Contracting Squadron does not require copies of listed deliverables. All deliverables will be reviewed for timeliness, accuracy and format. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date.
Table 4 - Deliverables
Monthly Status Report 6.1 COR On or before the 15th work day of each month
Trip Report 6.2 COR Within 5 business days after return
Quality Control Plan 6.3 COR No later than 30 calendar days after award
6.1. Monthly Status Report
The Contractor shall deliver a monthly status report on the fifth working day of each month. This report shall cover of the preceding calendar month and shall provide supporting documentation for the monthly invoice. The report should be unclassified if possible, and if the report must be classified, mark it with the appropriate classification markings and transmit using appropriate means. The Monthly Status Report shall include the following:
6.1.1. Contract number, Order number and Project number.
6.1.2. Brief task description.
6.1.3. A narrative review of work accomplished during the reporting period, significant events and whether it was in support of normal or contingency operations.
6.1.4. Progressive and problem areas.
6.1.5. Anticipated activity for the next reporting period.
6.1.6. Description of all travel or unique services provided during the period.
6.2. Trip Report.
The Contractor shall deliver a trip report for every TDY or multi-day conference attended
(reports are not required for local meetings attended during the course of a normal business day).
The Trip Report will be submitted to the contractor’s immediate supervisor within 5 business days of the completion of the trip/conference. The trip report will include at a minimum:
6.2.1. The name of the person conducting the travel/conference.
6.2.2. Dates and locations of the trip/conference.
6.2.3. Brief overview of purpose of the trip/conference.
6.2.4. Details of any significant decisions made during the trip/conference.
6.2.5. Details of Action Items assigned where attendee or office they represent are the Office of
Primary Responsibility (OPR) or Office of Coordinating Responsibility (OCR).
6.3. Quality Control Plan (QCP)
The contractor shall develop and maintain an effective quality control program to ensure the services of this PWS are being met. The contractor shall develop a QCP that includes quality control processes and procedures and apply them to meet this requirement. The QCP shall be submitted to the Ordering Contracting Officer (OCO) for acceptance no later than 30 calendar days after award. Updated versions of QCP shall be submitted to the OCO for acceptance no later than 10 calendar days of implementation by the Contractor.
Appendix A
Acronyms
ACCM-Alternative Compensatory Control Measures ADPE-Automatic Data Processing Equipment AFSIM- Advanced Framework for Simulation, Integration and Modeling
CO-Contracting Officer COR-Contractor Officer Representative DD Form-Defense Department Form DoD-Department of Defense FOIA-Freedom of Information Act FOUO-For Official Use Only FSO-Facility Security Officer
IAW-In Accordance With
JTR-Joint Travel Regulation MPS-Mission Planning System MPST-Mission Planning Support Tools OCI-Organizational Conflict of Interest OCO-Ordering Control Officer OCR-Office of Coordinating Responsibility OPR-Office of Primary Responsibility QAE-Quality Assurance Evaluator QCP-Quality Control Plan PSM-Program Security Manager PWS-Performance Work Statement RCS- Radar Cross Section SAP-Special Access Programs SAR-Special Access Requirement SCI-Sensitive Compartmented Information SIPRNET-Secure Internet Protocol Network TDY-Temporary Duty (Business Travel) TES-Test & Evaluation Squadron TO-Technical Order
| 4.5. Directives. Maintenance and support of the MPST software requires that the RQ-170 and its virtual environment are accurately replicated. Documents defining the performance of the RQ-170 and threat systems are:� |
| Appendix A� |
File details come from the government source that posted it. Updated .