Attachment 2 - Technical Proposal Format.pdf
PDF 119 KB Posted
- Attached to
- Amendment 01 - Kessel Run DevSecOps Commercial Solutions Opening - Call 002 Test Standards
- Solicitation number
- FA8730-22-S-C001-002
About this file
This document is the Technical Proposal Format for a federal contract opportunity. It provides instructions for the format and content to be included in a proposal submitted in response to the "Kessel Run DevSecOps Commercial Solutions Opening - Call 002 Test Standards" solicitation.
The key details include: the proposal must adhere to specific font, spacing, and formatting requirements; the proposal should include an abstract, scope, credentials, work to be performed, and performance schedule; the period of performance for the base period is not to exceed 12 months, with optional periods also not to exceed 12 months each; the proposal should not include any pricing information in the technical section. The solicitation is being issued by the U.S. Air Force Life Cycle Management Center (AFLCMC) to obtain expertise in supporting the identification of test standards, auditing those test standards, and reporting metrics on those test standards to rapidly deliver quality software to the warfighter.
View the file
Other files
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
Attachment 2 – Technical Proposal Format DSO CSO 1 Step Call Test Standards
Attachment 2 - Technical Proposal Format
Technical Proposal:
Font shall be a standard business font and no smaller than 10. Character spacing must be normal (not condensed in any manner). All text, including tables and charts, must follow all font size and spacing requirements listed. Font and spacing requirements are not required for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be utilized to circumvent formatting requirements and/or page count limitations by including lengthy narratives in such items.
Recommend including company name and proposal title in the header of each page.
ABSTRACT: A brief summary of the proposed solution and how it addresses all of the AOIs.
SCOPE: This proposal is submitted in response to AFLCMC/C3C Commercial Solutions Opening (CSO) Call 002 – Test Standards
a. Objective: Include a clear and concise description of the objective of the proposed project.
b. Background: Include a discussion of the nature and scope of the research and the technical approach. Include additional information on prior work in this area.
c. Programmatic:
i. Describe the management plan for the proposed effort.
ii. Include all business aspects to the proposed contract such as type of contract, any exceptions to the terms and conditions of the announcements (provide rationale for exceptions), and any information not technically related.
iii. Include descriptions of available equipment/tools (if applicable), data, and facilities.
iv. List supporting and collaborating organizations and subcontractors. Clearly identify roles and responsibilities of each organization and subcontractor supporting the proposed effort.
v. Identify any technical data that will be delivered with less than unlimited rights (if applicable).
vi. Any requested Government Furnished Property (GFP) other than identified within the CSO Call (if applicable)
1. A list describing all government property that the offeror or its subcontractors propose to use on a rent-free basis.
2. The dates during which the property will be used, and for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent.
3. The voluntary consensus standard or industry leading practices and standards to be used in the management of GFP or existing management plans, methods, or practices and procedures of accounting for the property.
d. Relevance: Describe the relevance of the proposed project in terms of the Areas of Interest (AOIs) (Attachment 1), Kessel Run’s mission, end user needs and technology maturity of the proposed effort.
CREDENTIALS: Describe Offeror’s qualifications to perform the proposed work. Summarize the relevant credentials of the primary performing center and supporting academic and industrial partners. Describe specific examples of similar work performed. List summary qualifications of the Key Personnel. Focus on information directly relevant to the proposed work. Include resumes of primary personnel who will be participating in this effort.
a. Summary of Credentials
b. Summary of Qualifications for Key Personnel
c. Summary of Related Efforts
WORK TO BE PERFORMED: Include a Scope of Work (SOW) detailing the technical tasks proposed to be accomplished under this effort and the completion timeline of the tasks (do not include any proprietary information or pricing in the SOW).
a. General: Provide an overview/summary of the effort
b. Detailed tasks and subtasks: Describe the details of all tasks needed to perform the proposed work. Clearly distinguish base period tasks and option tasks as appropriate.
i. Base Period shall not exceed twelve (12) months.
1. Task 1: Title - Describe what will be accomplished, how the task will be performed, resources required (personnel, hours, materials, etc.). Include appropriate metrics to measure progress. Identify task deliverables.
Describe subtasks when applicable. Each task shall clearly identify why the task is necessary to meet project objectives with measurable performance objectives and deliverables.
ii. Option Periods (if applicable) shall not exceed twelve (months) for each Option Period.
DO NOT INCLUDE PRICING INFORMATION IN THE TASK OUTLINE
PERFORMANCE SCHEDULE: Depict the tasks and subtasks identified about and the duration of the performance of each task in a Gantt chart or other suitable milestone schedule format.
Briefly describe the period of performance.
REFERENCES: List any relevant documents used to develop the technical approach.
File details come from the government source that posted it. Updated .