J28. 47QFHA24R0001_T10_09_DEAMS Seed Attachment 2_PRS.docx
DOCX document 27 KB Posted
- Attached to
- OUSD PRISM MATOC SOLICITATION Federal contract opportunity
- Solicitation number
- 47QFHA24R0001
- Issued by
- GSA Federal Acquisition Service
About this file
This document outlines a multiple award task order contract solicitation for personnel and readiness infrastructure support management services. Offerors are sought to provide enterprise solutions to enhance capabilities for the Office of the Under Secretary of Defense for Personnel and Readiness and strategic mission partners. The solicitation involves two pools, one for personnel and readiness support and another for major Department of Defense systems support. Task orders may utilize firm-fixed-price, cost-plus-fixed-fee, or hybrid contract types. Questions regarding the solicitation must be submitted by February 14, 2024, and proposals are due by March 6, 2024. The contract will utilize strategic tools such as streamlined task order procedures and technical direction letters.
View the file
Other files for this federal contract opportunity
Show all 50
OUSD PRISM MATOC SOLICITATION has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Page of
Describe what is being surveilled in the table below. Also describe the associated surveillance method. Be specific. Delete this sample language from the table prior to finalizing this QASP.
| TASK ORDER # |
| TASK |
| PERFORMANCE |
STANDARD
ACCEPTABLE
QUALITY
LEVEL (AQL)
| METHOD |
| FREQUENCY |
| APPLICABLE CPAR FACTOR(S) |
Technical (Quality of product or Service) /Cost control (n/a FFP)/Schedule/Management
| 5.1 Contract Management |
| Submission of Monthly Invoice |
| The contractor shall submit all invoices no later than (NLT) the 15th calendar day of the month following the reporting period |
| The Invoice is submitted no more than one day late |
| Electronically through the GSA portal ASSIST |
| Monthly |
| Quality, Management, Schedule |
| 5.1 Contract Management |
| Submission of Monthly Status Report (PWS, Section’s 5.2 – 5.10) |
| The contractor shall submit a Monthly Status Report that satisfies requirements of PWS Section 5.2 – 5.10 no later than the 5th business day of the month following the reporting period |
| The Monthly Status Report is submitted no more than one day late |
| 100% Inspection – The contract COR will note the date on which each Monthly Status Report is submitted and determine if it has been submitted in accordance with the established standard and AQL |
| Monthly |
| Quality, Management |
| 5.1 Contract Management |
| Contract Kickoff |
| Kickoff and requirements review completed within 5 business days of contract award unless otherwise agreed. |
| Conducted within 5 business days of contract award. |
| In-Person unless otherwise specified by Government |
| One time |
| Management |
| 5.1 Contract Management |
| Contract PM available per PWS requirements |
| Contract PM available per PWS requirements. |
-Release of claims for contract receive within 90 calendar days of contract expiration.
| No more than one absence without properly communicated delegation per quarter. |
| As directed by Government Lead |
| As required |
| Schedule |
| 5.1 Contract Management |
| Contract Service Support |
| Contract services provided timely and with services provided IAW contract level PWS |
As required
| 5.2 Air Force Accounting Operations Center (AFAOC) Support |
| Meeting minutes, Project/Task specific documentation, Training/Presentation Material and Supporting documentation |
| 90% of documentation and services shall be completed (including required updates) and submitted NLT the established date for completion/receipt and IAW the requirements established within the required documents (PWS\work definition\task directive\task assignment forms, etc.) and shall be compliant with all applicable governing regulations, policies, directives, and guidance. |
| No more than five (5) violations per month. |
| As directed by Government Lead |
| As required |
5.2.1 AFAOC CSD SME
| Meeting minutes, Project/Task specific documentation, Training/Presentation Material and Supporting documentation |
| 90% of trouble tickets assigned to the CSD Team are either resolved or elevated to Level 2 within 40 calendar days. Identified resolution actions do not result in negative impacts to any other areas. |
| No more than ten (10) violations per month. |
| All elevations are validated and/or substantiated by an authorized Government representative |
| As required |
| Technical |
5.2.2
AFAOC MC-SME
| Meeting minutes, Project/Task specific documentation, Training/Presentation Material and Supporting documentation |
| 90% of documentation and services shall be completed (including required updates) and submitted NLT the established date for completion/receipt and IAW the requirements established within the required documents (PWS\work definition\task directive\task assignment forms, etc.) and shall be compliant with all applicable governing regulations, policies, directives, and guidance. |
| No more than five (5) violations per month. |
| As directed by Government Lead |
| As required |
| Technical |
5.2.3 AFAOC Interface and Management Support
| Meeting minutes, Project/Task specific documentation, Training/Presentation Material and Supporting documentation |
| a. 100% of Alerts reported within the applicable time parameters. |
Consolidated inbound metric file completed and provided to government lead NLT 6th business day of each month; if delay is necessary due to circumstances beyond control, coordinate with Government lead to obtain approval of a new due date before the 6th business day of each month.
b. Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government lead.
a. No more than one (1) violation per month.
b. No more than one (1) violation per month.
As directed by Government Lead
Technical
5.2.4 AFAOC Internal Control Support
| Reports, policy, briefings, and guidance IAW applicable laws, regulations, instructions, and policies |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5.2.5 AFAOC User Communications
| Meeting minutes, Project/Task specific documentation, Training/Presentation Material and Supporting documentation |
| 90% of documentation and services shall be completed (including required updates) and submitted NLT the established date for completion/receipt and IAW the requirements established within the required documents (PWS\work definition\task directive\task assignment forms, etc.) and shall be compliant with all applicable governing regulations, policies, directives, and guidance. |
| No more than five (5) violations per month. |
| As directed by Government Lead |
| As required |
| Technical |
5.3 Deployment/Training Support
| Plans, Reviews, Assessments, Reports, etc. |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| Daily |
| Technical |
5.3.1 Deployment Training
| Training/Presentation Material and Supporting Documentation |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5.4 AFAOC Data Analytics and Field Support
| Meeting Minutes, Project/Task Specific Documentation, Training/Presentation Material and Supporting Documentation |
| 100% of documentation and services shall be completed (including required updates) and submitted NLT the established date for completion/receipt and IAW the requirements established within the required documents (i.e. PWS/work definition, task directive, task assignment forms, etc.) and shall be compliant with all applicable governing regulations, policies, directives, and guidance. |
| No more than five (5) violations per month. |
| As directed by Government Lead |
| As required |
| Technical |
| AFAOC DEAMS Surge Support |
| N/A |
| 5.5 DEAMS FMO Business Operations |
| Plans, Reviews, Assessments, Reports, etc. |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.6 DEAMS FMO Strategic Communication |
| Briefings, Presentations, Requirements Review Board Documentation, Stakeholders Presentations, Deployment Material, etc. |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5.7 DEAMS Compliance Development and Sustainment
| Reports, policy/guidance, briefings, assessments, corrective action plans, reviews of audit responses and/or related tasks IAW, or in consultation of, applicable laws, regulations, instructions and policies, to include but not limited to GAO, SSAE, GAGAS, FFMIA, NIST, A-123, FISCAM, and Air Force DoD policy. |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.8 AFAOC DEAMS Course Developers |
| Project/Task Specific Documentation, Training/Presentation Material and Supporting Documentation, Deployment Material |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5..9 DEAMS Functional Support – Agile Development Support
| Briefings, Presentations, Requirements Review Board Documentation, Stakeholders Presentations, Deployment Material, etc. |
| Documentation shall be provided within 15 business days following project/task assignment date unless otherwise specified by Government Lead. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5.9.2 DEAMS Integrated Process Teams (IPTs) and Software Development/Sustainment Support
a. Updates on plans of progress of IPT’s development status
b. Update back-log tickets (Service Now and/or JIRA) within 2 weeks of end of month.
c. Updates on plans and progress of team’s development status
a. Weekly updates on plans and progress of IPT’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are cancelled, then provide status electronically.
b. Back-log tickets (Service Now and/or JIRA) are updated within 30 calendar days of assignment with monthly status provided within 2 weeks of end of month. Monthly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are cancelled, then provide status electronically.
c. Contractor shall provide weekly updates on support provided to the Agile Team framework and work with the Government Product Owners to define User Stories and refine and prioritize Team backlogs. Additionally, the Contractor shall support cross-functional Scrum Team activities, at the discretion of the Product Owners, to include Sprint Planning, Sprint Review, and Sprint Retrospective. The contractor shall also support the Program Increment Reviews and planning sessions.
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
5.9.4 DEAMS Release Test Support
| Updates on test and release status |
| Provide high-level test status and updates during meetings, e.g. weekly Monday staff meeting, PMO meetings, etc. If meeting is cancelled, then provide status electronically, if required. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.9.5 Interoperability, Automation and Interface Support |
| Weekly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically. Updates on development status provided to pertinent development story/bug item during Daily Scrum meetings, grooming sessions and included in JIRA tickets. |
Monthly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically.
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.9.6 Reports and Analysis |
| Weekly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically. Updates on development status provided to pertinent development story/bug item during Daily Scrum meetings, grooming sessions and included in JIRA tickets. |
| Monthly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.9.7 Data Management Support |
| Weekly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically. Updates on development status provided to pertinent development story/bug item during Daily Scrum meetings, grooming sessions and included in JIRA tickets. |
Monthly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically.
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.9.8 Technical Advisor |
| Weekly updates on plans and progress of team’s development status provided to government during Agile Portfolio Sync staff meetings. If meetings are canceled, then status provided electronically. Updates on development status provided to pertinent development story/bug item during Daily Scrum meetings, grooming sessions and included in JIRA tickets. |
Monthly updates on plans and progress of team’s development status provided to government during Portfolio Sync staff meetings and to broader teams during PO/PM Sync meetings. If meetings are canceled, then status provided electronically.
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.10 DEAMS Integration SME |
| Plans, Reviews Assessments, Reports, etc. |
| Documentation provided within 15 business days following assignment dates unless otherwise specified by Government Lead. |
| No more than four (4) violations per twelve months. |
| As directed by Government Lead |
| As required |
| Technical |
| 5.11 AFAOC DEAMS Surge Support |
| Contract Labor in support of Air Force Accounting Operations Support |
| As directed by Government Lead |
| As required |
7.3 Monthly Invoice
Contractor shall provide a monthly invoice, NLT the 15th calendar day of the month following reporting period.
| No more than four (4) violations per twelve months. |
| As directed by COR |
| Monthly |
AAS QASP Template, 3/22/2022 AAS QASP Template version 3/24/2022 Page of image2.png image1.png
File details come from the government source that posted it. Updated .