Attachment S-2 Example Quality Assurance Surveillance Plan.xlsx
XLSX spreadsheet 22 KB Posted
- Solicitation number
- 693KA9-22-R-00016
About this file
This document contains a Quality Assurance Surveillance Plan (QASP) for the System of Airports Reporting (SOAR) contract opportunity with the Federal Aviation Administration. The QASP outlines 18 primary deliverables and associated performance standards required of the contractor to support ongoing SOAR operations and enhancements. Key deliverables include program management, project scheduling, resource management, reporting and data management plans and documentation. The contractor must also provide help desk, incident management, software development and security services. Performance will be monitored on metrics such as on-time delivery, completeness and data accuracy. The overall goal is to help transition SOAR responsibilities, maintain system functionality, and improve support services with a focus on reducing defects and user issues over time.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SIR_693KA9-22-R-00016_Section B thru M_FinalRev_Amend 3.pdf | ||
| Attachment S-3_Question and Comments - Government Response.pdf | ||
| 693KA9-22-R-00016 Section B Workbook.xlsx | XLSX spreadsheet | |
| SIR_693KA9-22-R-00016_Section B thru M_FinalRev.pdf | ||
| 693KA9-22-R-00016 Section B Workbook.xlsx | XLSX spreadsheet | |
| SIR_693KA9-22-R-00016_Section B thru M_Final.pdf | ||
| Attachment S-6 BusinessDeclarationForm.pdf | ||
| Attachment S-8 Industry QandC.xlsx | XLSX spreadsheet | |
| Attachment S-1 Section C - SOAR Statement of Objectives.pdf | ||
| Attachment S-5_ PP Questionairre.docx | DOCX document | |
| Attachment S-7 SOO Artifacts Workbook.xlsx | XLSX spreadsheet | |
| Attachment S-3_Question and Comments Form.doc | DOC document | |
| Section A_SolOfferAwardSF33.pdf | ||
| Attachment S-4 CLIENT AUTHORIZATION LETTER.docx | DOCX document |
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
QASP
| Del # | Deliverable Name | Performance Standard | Acceptable Quality Level (AQL) | Monitoring Method | Measure or Metric |
| PM-1 | Transition In Plan | Seamless transition from incumbent to new contract personnel with no adverse affect on SOAR operations or deliverables | 100% of transition plan tasks or knowledge transfer accomplished | trace accomplishments based on status and progress reports, interviews with key staff and individuals with high importance roles to transition plan | scale ranging from no information received to fully trained and ready to perform work |
| PM-2 | Transition Out Plan | The degree to which the Awarded Contractor has all documentation up to date and has prepared the government for successful transition | |||
| PM-3 | Transition In Report | The degree to which the Contractor is able to ascertain full responsibility of the work areas | |||
| PM-4 | Transition Out Report | The degree to which the Contractor has evidence for knowledge transfer necessary to enable transition | |||
| PM-5 | Performance Work Statement | The degree to which objectives are realized | |||
| PM-6 | Program Management Plan | The degree to which the PMP supports the SOAR team in fulfilling the contract scope and business objectives | |||
| PM-7 | Project Schedule | On time updates posted in FAA resource |
The degree to which the milestones are manage to baseline schedule or agreed up deviation PM-8-YYYY-MM-DD Master Schedule On time updates posted in FAA resource The degree to which the milestones are manage to baseline schedule or agreed up deviation The degree to which dependencies are accurately reflected
| PM-9 | Resource Management Plan | The degree to which resource disruption is minimized and relevant resources/knowledge are brought to bear for the benefit of the program | |||
| PM-10-YYYY-# | Staff Summary | complete, correct and current reporting summaries | |||
| PM-11-YYY-MM-DD | Progress Report | complete, correct and current reporting summary | |||
| PM-12-YYYY-MM | Status Report | complete, correct and current reporting summary | |||
| PM-13 | Quality Assurance Surveillance Plan | the degree to which surveillance methods are transparent and metrics can be analyzed independently by the government | |||
| PM-14-YYYY-MM- # | Quality Assurance Surveillance Report | complete, correct and current reporting on timely basis | |||
| PM-15 | Quality Control Plan | the degree to which the QCP ensures metrics for the Surveillance Report | |||
| PM-16 | Meeting Support - Agendas, Meeting Notes and Action Items | complete, correct and current reporting | |||
| PM-17 | Customer Relations Report | the degree to which self assessment is concise and supported by data | |||
| PM-18 | Uniform BiPartisan Infrastructure Law Spending Report | the degree to which the report meets the need established by contract | |||
| OM-1 | Change Control Board Report | complete, correct, current and timely change reporting (e.g., agendas, minutes, finding status updates) | 95 - 100% of deliverables | report review | delivery dates, completeness verified weekly in CCB meeting are within delivery timeframes and agree with F&I |
| OM-2 | System Description Characterization | complete, correct, and current reference as needed by FAA AIS or COR for reference |
OM-3 Infrastructure, Assets, Security and Patching Schedule on time delivery of milestones updated schedule OM-4 Configuration Management Plan complete, correct and current reference as needed by FAA AIS or COR for reference
OM-5 Data Management Plan complete, correct and current reference as needed by ARP for reference the extent to which the plan prevents data error reports
OM-6 Reporting and Analytics the degree to which 'cuff records' are reduced the ability to respond to ad hoc requests without contractor support
| OM-7 | System Defect Resolution Report | declining trend of defects | |||
| OM-8 | Release Report | declining trend in time to market for similar changes | |||
| OM-9 | Incident Reports | complete, correct and timely | |||
| OM-10 | Version Description Document or other deployment artifact | the degree to which there are no configuration or application errors generated as a result of deployment (i.e., exclusive of code) | |||
| OM-11 | Helpdesk Operations Plan | the degree to which the plan contributes to the response and user experience over time | |||
| OM-12 | Support Services Report | improving trend of comprehensive updates when initial change occurs to keep all artifacts and support systems current | |||
| OM-13 | Various products not specifically named as individual deliverables in this list. Examples include Needs Assessments, Proof of Technology Reports, Requirements, User Stories, Burn Down Charts, Design Documents, Source Code, Database Scripts, Test Plans, Test Results, Operations Manual or Standard Operating Procedures, and other reports or documents as may either be required by FAA policy during the life of the contract or deemed beneficial by mutual agreement of Contractor and COR | complete, correct and timely | |||
| OMS-1 | Security Impact Assessment | complete, correct and timely | |||
| OMS-2 | Monthly Status Briefings | complete, correct and based on timely review of AIT scans | |||
| OMS-3 | Continuity of Operations Plan or Information System Contingency Plan | complete, correct and timely | |||
| OMS-4 | Incident Response Plan | complete, correct and timely | |||
| OMS-5 | ISCP Test Plan and Results | complete, correct and timely | |||
| ST-1 | Software Measurement Plan | See section I.15 3.10.4-21 Requirement for Software Measures | |||
| ST-2 | Scope Report | List of functions and features in current SOAR by module or development objective plus any approved new functionality. Obsolete or features users agree to retire should be noted separately | 100% of existing functionality and approved findings/enhancement reflected in scope plan unless specifically exempted by COR or Business Lead delegate | traceability matrix comparing scope to existing functionality | SOAR SME group and Business Lead accept the Scope Report based on traceability matrix |
| ST-3 | Requirements or User Stories | degree to which initial requirements/user stories reflect user needs and sizing and coding inputs for development success | Requirements/User stores reflect 100% scope in a manner constent with user input to design and acceptance criteria | feedback on first draft of requirements or user stories | ratings such as: No change; Minor change; Significant change; New requirement or User Story |
| ST-4 | Design Document | to degree to which initial design reflects reuse of standards and code and anticipates development needs based on initial scope | |||
| ST-5 | Development Schedule and Status Report | declining or 0 deviation from plan | |||
| ST-6 | Release Deployment (Code and Report) | ideally every 3-4 months, with some legacy areas possibly taking longer |
deviation from baseline schedule and scope ST-7 through ST-12 Various Reports decrease in support costs or improvement in sustainability and security over time
File details come from the government source that posted it. Updated .