Attch 08 Cross-Reference Matrix.xlsx
XLSX spreadsheet 27 KB Posted
- Attached to
- Gunnery Training Systems: Solicitation
- Solicitation number
- W900KK-21-R-0055
About this file
This solicitation requests proposals for Gunnery Training Systems to implement technical refresh upgrades, current system production, concurrency upgrades, and Risk Management Framework certification requirements for multiple gunnery trainer programs, including Abrams, Bradley, Stryker, and LAV-25. The Army Program Executive Office for Simulation, Training, and Instrumentation, Project Manager Soldier Training Product Manager Virtual Training Systems has a requirement for these services. Proposals are due by 1700 EST on February 12, 2021. The Army anticipates awarding a contract in the first quarter of fiscal year 2022, though this date may change. A Justification and Approval for Other than Full and Open Competition has been approved for this solicitation. Government-furnished information is available to potential offerors who are vetted by the security office and download files from DoD SAFE within seven days of receiving access.
View the file
Other files
Show 40 more
Latest 50 of 52 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
SF 1.1 Tech Elems.
| Section L | Section M | Contractor's Proposal | |||||
| Factor | Subfactor | Requirement | Subfactor | Volume I Technical | Section and Page Number | Paragraph | Contractor Subfactor Notes/Other References |
| Factor 1 - Technical | 1.1 - Technical Elements L.4.1.1 | SOW Refs: 3.2, 3.5, 3.9 | 1.1 - Technical Elements M.3.1.1 | ||||
| a. The Offeror shall clearly demonstrate their understanding of the nature of the work being undertaken in accordance with the SOW elements and technical specifications for tech refreshes and concurrency upgrades of each legacy system. The Offeror shall clearly demonstrate their competency and technical understanding to successfully accomplish the requirements set forth in the SOWs and technical specifications. The Offeror shall describe its technical approach to design, develop, fabricate, integrate, test, validate, deliver, and install tech refreshes. | a. The Government will evaluate the Offeror’s technical solution for efficiently and effectively designing, developing, fabricating, integrating, testing, validating, delivering, and installing tech refreshes and concurrency upgrades. The Offeror will be evaluated based on its suitable analysis and realistic description of its tech refresh approach for each legacy system. The Government will evaluate the Offeror’s clear understanding of the nature of the work being undertaken in accordance with each of the SOWs and specifications. The Government will also evaluate the measurable efficiencies and advantageous benefits of the Offeror’s technical approach and solutions. | ||||||
| b. The Offeror shall describe its technical approach to design, develop, fabricate, integrate, test, validate, deliver, and install production systems of existing gunnery training devices. | b. The Government will evaluate the Offeror’s technical solution for efficiently and effectively designing, fabricating, integrating, testing, validating, delivering, and installing production systems of existing gunnery training devices. The Offeror will be evaluated based on its suitable analysis and realistic technical approach to meet the requirements described in the SOWs and existing system specifications. The Government will also evaluate the measurable efficiencies and advantageous benefits of the Offeror’s technical approach and solutions. | ||||||
| c. The Offeror shall describe its technical approach for integrating third party hardware/software products. Successful previous experiences in integration, such as SE Core products, Common Software Libraries (CSLs), Blue Force Tracker (BFT) hardware and software products, and One Semi-Automated Forces (OneSAF) to meet GTS requirements are desired and should be described as part of the technical approach. | c. The Government will evaluate the effectiveness, completeness and feasibility of the Offeror’s technical approach and experience with integration methods of third party products to meet the Government’s needs. | ||||||
| d. The Offeror shall describe relevant experiences, not to exceed five, total, for tech refreshes, concurrency updates and production of existing virtual training systems within the past five years. | d. The Government will evaluate the Offeror’s relevant, credible and verifiable technical experiences which demonstrate an understanding in executing tech refreshes, concurrency upgrades, and production of existing virtual training systems, in accordance with the SOWs and specifications. | ||||||
| e. The Offeror shall describe relevant experiences, not to exceed three, total, for accreditation/re-accreditation accomplishments, in certifying systems in accordance with the DoD Cybersecurity requirements. | e. The Government will evaluate the Offeror’s relevant, credible and verifiable experience which demonstrate understanding in certifying systems in accordance with DoD Cybersecurity requirements. |
SF 1.2 Program Man.
| Section L | Section M | Contractor's Proposal | |||||
| Factor | Subfactor | Requirement | Subfactor | Volume I Technical | Section and Page Number | Paragraph | Contractor Subfactor Notes/Other References |
| 1.2 - Program Management L.4.1.2 | SOW Refs: 3.1, 3.2, 3.5, 3.6, 3.9 | 1.2 - Program Management M.3.1.2 | |||||
| a. The Offeror shall describe its technical approach and process to ensure successful overall management. The Offeror shall provide the administrative effort necessary to meet requirements of this contract. The Offeror shall identify the top three risk areas associated with its approach/solution and corrective actions and resources required to eliminate or reduce schedule and performance impacts. The Offeror shall describe its understanding of the GTS requirements based on the risk areas and the recommended Courses of Action (COAs) to mitigate the impacts to include management of staffing, resources, and subcontracts. | a. The Offeror will be evaluated based on its proposed approach to effectively and efficiently address the full breadth of contract requirements, including its identification of risk areas associated with its technical approach and the described COAs required to eliminate the impacts. The Government's evaluation will consider: working relationships and agreements with all partners including subcontractors; roles and responsibilities of the prime Contractor and sub-contractors; and skill sets appropriate to meet or exceed the program requirements. | ||||||
| b. The Offeror shall provide an Integrated Master Plan (IMP) and an Integrated Master Schedule (IMS) down to the third level that reflects its understanding of the program requirements for Abrams, Bradley, Stryker and USMC GTS Solicitation Delivery Orders’ efforts that will be performed concurrently. The IMS shall address the Offeror’s identified major milestones, critical paths, development/integration/testing approach to include fielding, Cybersecurity RMF, and subcontractor partnership(s), without negatively impacting any individual delivery order, based on the quantities listed in Section F of each DO GTS Solicitation Delivery Order. Offerors shall propose a delivery schedule substantially the same as the table titled: Offeror’s Proposed Delivery Schedule included in FAR clause 52.211-8, Time of Delivery and include it as part of the technical proposal. ALT III of this clause will be included in the resulting contract. | b. The Government will evaluate for completeness, timeliness and reasonableness of the Offeror’s proposed IMP, proposed delivery schedule, and IMS plan to address its programmatic approach in delivering the initial delivery orders of the Abrams, Bradley, Stryker, and USMC tech refreshes. The Offeror will be evaluated based on the realism of major milestones, critical paths, fielding plans, and their practical ability to ramp staffing up and down to support multiple complex efforts. | ||||||
| c. The Government desires a minimum of Government Purpose Rights to all technical data and non-commercial software in order to: |
i. Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction
ii. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes
iii. Maintain, repair, modify, and upgrade a GTS using Government personnel and other Government Contractors
iv. Compete future GTS requirements and upgrades
Offerors shall identify the rights in technical data and non-commercial software IAW DFARS Subparts 252.227-7013 and 7014 via completion of solicitation provision DFARS Subpart 252.227-7017. If the Offeror proposes to offer rights less than Government Purpose Rights for technical data or non-commercial software, Offeror must furnish a written explanation that explains the offer of lesser rights. Additionally, the Offeror should describe the process, if any, the Government may use to obtain Government Purpose Rights, or a risk mitigation plan for anything less than Government Purpose Rights.
c. The Government will evaluate the Offeror’s adequate response to solicitation provision DFARS Subpart 252.227-7017. If anything less than Government Purpose Rights is offered for technical data or non-commercial software, the Offeror must furnish a written explanation that explains the assertion of offering lesser rights. Additionally, the Offeror should describe the process, if any, the Government may use to obtain Government Purpose Rights, or a risk mitigation plan for anything less than Government Purpose Rights. The response to DFARS 252.227-7017 and the written explanation will be evaluated to determine the extent to which the offered rights allow the Government to
i. Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction
ii. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes
iii. Maintain, repair, modify, and upgrade a GTS using Government personnel and other Government Contractors
iv. Compete future GTS requirements and upgrades
d. The Offeror shall provide its approach to simultaneously produce and store the amount of systems/kits required by the four initial Delivery Orders requirements included with this solicitation. d. The Government will evaluate the feasibility of the Offeror’s approach to address available facility space for storage and production of training devices/kits. The Offeror will be evaluated based on its realistic ability to simultaneously produce and store the amount of production systems/kits required by the multiple Delivery Orders.
SF 1.3 Product Line Support
| Section L | Section M | Contractor's Proposal | |||||
| Factor | Subfactor | Requirement | Subfactor | Volume I Technical | Section and Page Number | Paragraph | Contractor Subfactor Notes/Other References |
| 1.4 - Product Line Support L.4.1.3 | SOW Refs: 3.1.4, 3.2.6.10 | 1.4 - Product Line Support M3.1.3 | |||||
| a. The Offeror shall describe its technical approach for common parts/components and interfaces across all GTS platforms/products. | a. The Offeror will be evaluated based on the complexity and commonality of proposed subsystem components and interfaces that can be efficiently and effectively utilized across all GTS platforms/products. | ||||||
| b. The Offeror shall describe its technical solution for leveraging the LT2 tools and their configuration management approach for GTS. | b. The Government will evaluate the Offeror’s understanding and feasibility of their configuration management approach leveraging Live Training Transformation (LT2) tools. |
File details come from the government source that posted it. Updated .