47QFHA24R0001_T10_08_DEAMS OCI Related Information.pdf
PDF 267 KB Posted
- Attached to
- OUSD PRISM MATOC SOLICITATION
- Solicitation number
- 47QFHA24R0001
- Issued by
-
GSA Federal Acquisition Service
About this file
This document provides details for a federal solicitation seeking proposals for the Personnel and Readiness Infrastructure Support Management Multiple Award Task Order Contract. The solicitation will result in multiple awards for enterprise solutions to enhance capabilities for the OUSD Personnel & Readiness, its Directorates and Strategic Mission Partners. Services will include strategic tools like contract type flexibility, accelerated task order lead times, and technical direction letters. Offerors must submit any questions by February 14, 2024 and proposals by March 6, 2024 to the listed GSA points of contact. The contract vehicle will have two pools, one for Personnel and Readiness and another for Major Department of Defense Systems. The awarded contracts will be held by the GSA Federal Acquisition Service and utilized to issue both firm-fixed-price and cost-plus-fixed-fee task orders.
View the file
Other files
Show 40 more
Latest 50 of 86 listed here. See the rest on GovTribe.
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
DEAMS OCI RELATED INFORMATION
1. During the performance of the DEAMS work, the contractor has access to sensitive Government information including Government budgetary requirements, Government estimates, statements of work and third-party contractual information. The contractor will also be assisting in quality assurance tasks which must be independent.
2. During the performance of the DEAMS work, the contractor is responsible for conducting analysis of existing DEAMS programs and projects. If the awardee has a vested interest either as prime or sub-contractor of the existing system integration contract or other DEAMS program office support contracts, the conflicting roles may bias the contractor’s judgment of both the planned acquisition and the existing DEAMS support efforts. Examples include, but are not limited to:
a. Support the integrated testing team by providing AFAOC functional support to ensure requirements are met.
b. Support development testing, review a proposed system change request for compliance with applicable laws, regulations policies, system functionality, and document concurrence or non- concurrence with explanation in the Government provided ticket management system as user stories are being created.
c. Support the development and analysis of system changes in the form of user stories or bugs derived from test, production errors, system software upgrades or interface partnerships.
d. Participate in integrated testing and deliver test results and bugs related to testing outcomes. Contractor shall utilize provided testing software and tools to review, analyze and run test scripts.
e. Be an active participant on the Integrated Test Team (ITT) and offer support for all aspects of test to include test planning.
f. Participate in Qualification Test and Evaluation (QT&E) Process and deliver test results and analysis as required for failed and incomplete test scripts.
g. Coordinate closely with both Government and SIs to perform independent and integrated software testing as required to support system upgrades and releases.
h. Gather information from users, define work problems, and propose a systematic design and procedures to resolve problems.
i. Assist the FMO, the Program Management Office (PMO) and System Integrator (SI)/sustainment contractor with design, analysis, test of software, interfaces and to meet functional requirements.
j. Provide FMO/AOC input to specifications, test scenarios and/or user documentation.
k. Develop and document user workarounds for software defects and changes until solutions are implemented.
l. Support the FMO and PMO with the review of System
Integrator/sustainment contractor’s development deliverables to ensure correctness, consistency, completeness, and compliance with requirements.
m. Review for accuracy, completeness and provide comments related to the Functional Design (FD), Technical Design (TD), Test Condition Expected Result (TCER) and test script documentation, in advance of their respective due dates reflected within the Integrated Master Schedule (IMS), generated, and maintained by the DEAMS PMO in accordance with program schedule.
3. During the performance of the DEAMS work, the contractor is also responsible for recommending technical direction and preparing specifications or requirements definition for future actions. If the awardee has a vested interest either as prime or sub-contractor of the existing DEAMS system integration or other support contracts, the conflicting roles may bias the contractor’s judgment of both the planned acquisition and the existing system efforts. Examples include, but are not limited to:
a. Support an 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 the cross-functional Scrum Team activities, at the discretion of the Product Owners, to include Sprint Planning, Sprint Execution, Sprint Testing, Daily Scrum, Sprint Review, and Sprint Retrospective. The contractor shall also support the Program Increment reviews and planning sessions.
b. Provide input into functional, process, and data modeling in support of DEAMS data strategy and analysis efforts.
c. Review, develop and update program reports and queries and their associated requirements documentation.
d. Contractor shall facilitate and participate in the DEAMS requirements working group to develop Specific, Measurable, Attainable, Relevant, Testable and Traceable (SMART) requirements for system changes and releases.
4. In light of the above, offerors are advised of their Organizational Conflict of Interest (OCI) responsibilities. See the OCI requirements for the MATOC proposal Cover Letter (Section L.6), FAR 9.5 and DFARS 209.5 and DFARS provision 252.209-7008 and DFARS clause 252.209-7009.
File details come from the government source that posted it. Updated .