Section_L.docx
DOCX document 32 KB Posted
- Attached to
- The Joint Threat Emitter (JTE) Program/Logistics Support Federal contract opportunity
- Solicitation number
- FA8210-24-R-5014
About this file
This document is the Instructions to Offerors (ITO) section of a Request for Proposal (RFP) for the Joint Threat Emitter (JTE) Enhanced Delivery Initiative (JEDI) contract. The RFP is a sole source opportunity from the Department of the Air Force Materiel Command Lifecycle Management Center at Hill Air Force Base.
The ITO provides detailed instructions for Offerors to prepare their proposals, which must be submitted in three volumes: Price, Technical, and Contract Documentation. Key requirements include an Integrated Master Schedule, supply chain processes, configuration management plan, obsolescence management approach, production approach, design compliance approach, and testing capabilities. Pricing information must be provided in a specific Pricing Workbook, and the Technical Volume is limited to 125 pages. The Contract Documentation Volume includes the signed Model Contract/Solicitation and required representations and certifications. Exceptions to solicitation requirements must be clearly identified. The period of proposal acceptance is 365 calendar days.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| CDRLs_A_List.pdf | ||
| FA8210-24-R-5014.pdf | ||
| Pricing_Work_Book.xlsx | XLSX spreadsheet | |
| Section_M.docx | DOCX document |
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
SECTION L
Instructions to Offeror (ITO) Joint Threat Emitter (JTE) Enhanced Delivery Initiative (JEDI)
1. PROPOSAL PREPARATION INSTRUCTIONS
1.1 To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The response shall consist of three (3) separate volumes; Volume I - Price, Volume II - Technical, and Volume III - Contract Documentation.
2. GENERAL INSTRUCTIONS
| 2.1 | This section provides general guidance for preparing proposals as well as specific instructions on format and content of the proposal. The Offeror's proposal shall include all data and information requested, and shall be submitted In Accordance With (IAW) these instructions. Any Offeror who submits an incomplete package may be considered ineligible for award and eliminated from the competition. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements Lists (CDRLs), and Model Contract/Solicitation. Non-compliance with these instructions may result in an “Unacceptable” proposal evaluation. |
| 2.2 | The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and shall base its evaluation on the information presented in the proposal. |
| 2.3 | All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, the Offeror is representing that the company will perform ALL of the requirements specified in the solicitation (including PWS); it is not necessary to tell us so in the proposal. |
| 2.4 | Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and not preferred. |
| 2.5 | The proposal acceptance period is specified in Block 12 of Section A (front page) of the Model Contract/Solicitation. Offerors providing less than the specified calendar days for Government acceptance after the date proposals are due will be considered ineligible for award and will be eliminated. |
| 2.5.1 | The Offeror agrees to hold the prices in its proposal for 365 calendar days from the date specified for receipt of proposals. |
| 2.6 | IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals. |
| 2.7 | The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address below: |
AFLCMC/PZZK
Attn: Patrick Kamea Robello, PCO 6039 Wardleigh Rd, Bldg. 1206 Hill AFB UT 84056-5838 Office (801) 866-4979 patrick.robello.1@us.af.mil
| 2.8 | Pre-Award Debriefings – The CO will promptly notify Offeror of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505, Pre Award Debriefing of Offerors. Offerors excluded from the competitive range may request a pre-award debriefing or, at the Offeror’s request, this debriefing may be delayed until after award. However, Offerors excluded from the competitive range are entitled to no more than one debriefing. |
| 2.9 | Post Award Debriefings – The CO will notify Offeror in the competitive range of the source selection decision IAW FAR 15.506, Post Award Debriefing of Offerors. Upon such notification, Offerors may request and receive a debriefing IAW the requirements of FAR 15.506, as applicable. |
| 2.10 | Discrepancies – If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. |
| 2.11 | Electronic Reference Documents – Referenced documents for this sole source solicitation are available on the sam.gov site. Classified documents and the Government owned Technical Data Package (TDP) will not be available on sam.gov but will be made available by mail to any Offeror that receives approval through the DD254 process. Potential Offerors are encouraged to subscribe for real-time e-mail notifications from FBO when information has been posted to the website for this solicit. |
| 2.12 | Oral Presentation - Oral presentations will not be allowed. |
2.13 Amendments to Solicitation - If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by signing and returning the front page of each Standard Form 30 (see section 6.2 for additional information).
| 2.14 | Submission, Modification, Revision, and Withdrawal of Proposals |
| 2.14.1 | Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 2.7 of this document showing the time and date specified for receipt, the solicitation number, and the name and address of the Offeror. Late proposals will only be considered IAW FAR 15.208. |
| 2.14.2 | Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the proposal wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel. It is the Offeror’s responsibility to ensure receipt of proposals by the Government. |
| 2.14.3 | Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an Offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award. |
| 2.15 | Organization, Number of Copies, and Page Limits |
| 2.15.1 | The title page of each volume must show: |
| 2.15.1.1 | Solicitation Number |
| 2.15.1.2 | Company Name, Address, Commercial and Government Entity (CAGE) Code, and Data Universal Numbering System (DUNS) Number |
| 2.15.1.3 | Primary point of contact name, telephone number, and email address |
| 2.15.1.4 | Volume number and name (i.e. Volume I, Price) and copy number (i.e. Original, Copy 1, Copy 2, etc.) |
| 2.15.2 | The Offeror shall prepare the proposal as set forth in Table 1: Proposal Organization. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies specified. Each volume identified in the table shall be separately bound in a three-ring, loose-leaf binder. Additionally, the Offeror shall prepare one (1) Master Proposal containing one hard copy of each volume identified in Table 1: Proposal Organization. This Master Proposal shall be printed double-sided, flipped on the short end, two-hole punched centered on the top of the page, and bound together but not in a binder. The contents of each proposal volume are described in the Information to Offerors (ITO) paragraph as noted in Table 1: Proposal Organization. |
TABLE 1: PROPOSAL ORGANIZATION
VOLUME
ITO
Paragraph Number
VOLUME TITLE
COPIES
PAGE LIMIT
| I |
| 3 |
| Price |
| Original, and 2 CDs |
| Unlimited |
| II |
| 4 |
| Technical |
| Original plus 1 Hardcopy, and 2 CDs |
| 125 |
| III |
| 6 |
| Contract Documentation |
| Original, and 2 CDs |
| Unlimited |
| 2.16 | Page Limitations – Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs) if discussions are conducted. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the applicable Offerors. Each page shall be counted except the following: |
| 2.16.1 | Blank pages, title pages, cover sheets, acronym lists, cross reference matrix, table of contents, list of tables and figures, tabs, glossaries, the full Integrated Master Schedule (IMS), and items noted in Table 1: Proposal Organization as unlimited. |
| 2.17 | Ensure that the electronic copies are identical to the hardcopies when printed. |
| 2.18 | Pricing Information – All pricing information shall be addressed ONLY in the Price Volume. Work hour estimates, and material kinds and quantities (excluding dollar amounts/prices) may be used in other volumes only as appropriate for presenting rationale of the technical approach. |
2.19 Cross-Referencing
2.19.1 Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted.
2.20 Indexing
| 2.20.1 | Each volume shall contain a detailed table of contents to delineate the paragraphs and subparagraphs within that volume. Tab indexing shall be used to identify sections. | |
| 2.20.2 | Include an indexed list of Tables and Figures. | |
| 2.20.3 | Each volume shall contain a glossary of all abbreviations and | acronyms used with a definition for each. |
2.21 Page Size and Format
| 2.21.1 | A page is defined as each face of a sheet of paper containing information. Sheet size shall be 8.5 by 11 inches, not including foldouts. Sheets shall be printed on both sides, flipped on the long edge, and will count as two pages. Except for the reproduced sections of the solicitation document, the text font shall be Times New Roman, font size shall be no less than 12 point, with the exceptions outlined in 2.21.2, and shall utilize 1.5 line spacing. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one inch margins on the top, bottom, and sides. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs, if applicable. These limitations shall apply to both electronic and hard copy proposals. |
| 2.21.2 | Legible tables, charts, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, be printed only on one side, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, and figures, the text shall be no smaller than 10 point. These limitations shall apply to both electronic and hard copy proposals. |
| 2.21.3 | All portions in the electronic version of the proposal shall be searchable for text in the host program. This includes narratives as well as all tables, charts, and figures. |
| 2.22 | Binding and Labeling – Other than the Master Proposal identified in section 2.15.2, each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked as to volume number, title, original or copy number, solicitation identification and the Offeror's name. The same identifying data shall be placed on the spine of each binder. All document binders shall be white or black. Apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. |
| 2.22.1 | Electronic Offers – The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard copy shall take precedence. For electronic copies, indicate on each CD the volume number and title. Use separate files for each volume to permit rapid location of all portions, including subfactor required plans, exhibits, annexes, and attachments, if any. The Offeror shall submit Volumes I - III in electronic format, using read only CDs (CD-R). Re-writable CDs (CD-RW) WILL NOT BE READ, EVALUATED, OR CONSIDERED. Each volume shall be on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft Office Suite 2010, as applicable. Word documents and Excel spreadsheets must be editable and NOT password protected. PDF formats shall NOT be used. Ensure all formulas used are included and viewable in Excel Spreadsheets. |
2.22.2 Hyperlink – The table of contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that “clicking” the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. In addition, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. A hyperlinking reference between different filenames is not acceptable.
2.23 Volume Summary – Identified Evaluation will be based on the following Factors and Subfactors:
Volume I – Price Volume II – Technical Subfactor 1 – Program Management / Logistics Subfactor 2 – System Design Compliance / Systems Engineering Subfactor 3 – Testing Volume III – Contract Documentation
3. VOLUME I –PRICE
| 3.1 | General Instructions – The primary purpose of this volume is to provide the CO and the Government evaluation team an understanding of how the price proposal was developed. The price evaluation criteria will be: (1) Completeness, (2) Reasonableness, (3) Balance, (4) Total Evaluated Price (TEP), and (5) Professional employee compensation plan, as defined in Section M of the RFP and will be assessed from the Offeror’s information provided in this volume. All pricing and delivery blocks in the Pricing Workbook shall be populated in accordance with the instructions outlined in the Pricing Workbook. |
| 3.2 | Total Evaluated Price (TEP) |
| 3.2.1 | Submit a copy of the completed Pricing Workbook in the Price Volume (Volume I) in Microsoft Excel. The Contractor shall adhere to all instructions outlined in the Pricing Workbook. |
| 3.2.2 | Government determined elements of the notional TEP formula WILL NOT be disclosed to Offerors. The TEP is for evaluation purposes only, however all proposed prices and rates regardless of pricing arrangements are contractually binding. Notional quantities may not align with actual contractual orders. |
| 3.2.3 | Rounding – All dollar amounts provided shall not extend beyond two decimal places. |
| 3.2.4 | Estimating Techniques and Methods – Offerors shall use generally accepted estimating techniques to develop their estimates for prices in the Pricing Workbook. |
| 3.3 | The Offeror shall submit a professional employee compensation plan meeting the requirements of FAR 52.222-46, Evaluation of compensation for Professional Employees. The Offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons in accordance with FAR 52.222-46. |
4. VOLUME II – TECHNICAL
| 4.1 | General Instructions – The Technical Volume shall be clear, specific, complete, and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. Responses will be evaluated using the evaluation criteria outlined in the Technical subfactors in Section M. Provide as specifically as possible the actual methodology the Offeror would use for accomplishing and satisfying each subfactor. There shall be no reference to rates or price in this volume. Offerors shall assume the Government has no prior knowledge of its facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal. It is imperative that the Offeror fully describe and provide detail as to how the Offeror shall meet the subfactor requirements. Evidence which clearly demonstrates and supports the Offeror’s claims is essential. |
| 4.2 | Volume Organization – The Technical Volume (Volume II) shall be organized according to the following general outline: |
Table of Contents List of Tables and Figures Acronym List and Definitions Glossary Cross Reference Matrix Subfactor One: Program Management / Logistics Subfactor Two: System Design Compliance / Production Subfactor Three: Testing Attachments
4.3 Subfactor One: Program Management / Logistics
The Offeror shall provide an approach for Program Management / Logistics. The proposed approach shall thoroughly substantiate all of the following elements:
4.3.1 Integrated Master Schedule (IMS) – The Offeror shall provide a Gantt Chart depicting the start and end points of all events required to complete the production and qualification testing for 1 of each end-item type from order to system delivery. The IMS shall include the procurement of long-lead material, a site survey, production of a Software Development Station (SDS), procurement of spares, production of a retrofit kit measured from award date/After Receipt of Order (ARO) (i.e. 30 days ARO). The full IMS shall be included as a separate document attached to the technical volume and will not count towards the page limit. The Offeror shall also clearly identify the critical path, for end-item delivery and include this critical path in the technical volume. This critical path will be counted towards the page limit of the technical volume. (PWS 4.10.9)
4.3.2 Supply Chain Processes and System Delivery – The Offeror shall describe how their supply chain processes are capable of procuring complex components from multiple vendors. The offer shall also identify and propose a mitigation solution for any schedule risks associated with OEM supplier constraints. The Offeror shall outline their system delivery process to OCONUS locations (i.e. United States Air Forces Europe and Pacific Air Force) not utilizing a Freight Forwarder.
4.3.3 Configuration Management Plan (CMP) – The Offeror shall provide an initial Configuration Management Plan IAW PWS 4.3.13 that includes, at a minimum, all critical configuration management elements as well as an outline for how the Offeror meets, or exceeds, the level three Core Process Areas and Development processes within the Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI). Additionally, the Offeror shall provide an outline of their quality assurance program that outlines ISO 9001 certification or equivalent.
4.3.4 Obsolescence Management – The Offeror shall provide an obsolescence management program which details a proactive approach to monitor the JTE system’s Bill of Material and identify parts obsolescence. The approach shall demonstrate the Offeror’s proposed use of predictive tool(s) to meet the requirements in PWS 4.3.14. The Offeror shall describe how their obsolescence program will reduce the impact of obsolescence.
4.4 Subfactor Two: System Design Compliance / Systems Engineering
4.4.1 Production Approach – The Offeror shall describe their production approach for the manufacturing of JTE systems (i.e. throughput, facility size, parallel production lines, inspection points, work flow, etc.) to include a picture/diagram of the manufacturing process flow. The production approach shall demonstrate how the Offeror will ensure the production of JTE end-items while delivering support equipment, retrofit kits, and full sets of spares for at least 50% of these end-items ordered.
4.4.2 Design Compliance Approach – The Offeror shall describe how their production processes utilized in the manufacture of JTE Systems will ensure compliance to the TDP. The description shall include how the system hardware and software will meet all Physical Configuration Audit criteria in PWS 4.3 and how variances from the TDP will be handled.
| 4.5 | Subfactor Three: Testing |
| 4.5.1 | Test Capability – The Offeror shall describe their capability to perform all required testing per the JTE System TDP to ensure the JTE System meets all requirements of the system TDP. The description shall include test equipment, support equipment, test plans, personnel training, and software (to include diagnostic aids). |
| 4.5.2 | Test Capacity – The Offeror shall describe a Test Capacity method which shows how the Offeror can meet PWS delivery requirements found in section 4.3.25 by demonstrating the capacity to complete all test requirements in the PWS and by identifying any parallel testing that will be necessary. |
5. VOLUME III – CONTRACT DOCUMENTATION
| 5.1 | Model Contract / Representations and Certifications - The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Model Contract/Solicitation and any applicable amendments, and Sections A through K. This includes delivery of all applicable documents. |
| 5.2 | Section A – Solicitation/Contract Form |
| 5.2.1 | Complete blocks 13 and 15, then sign and date block 16, 17, and 18 of the Standard Form (SF) 33, Solicitation/Contract. Any amendments (SF 30) to the RFP must be signed in block 15. Signature of the Offeror on the SF 33/SF 30 constitutes an offer, which the Government may accept. In signing the SF 33/SF30, the Offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. The “Original” copy should be clearly marked under separate cover and should be provide without any punched holes. |
| 5.3 | Section B – Supplies or Services and Prices |
| 5.3.1 | Unit and extended prices for Section B shall be completed by the Offeror within the Pricing Workbook attached in Section J. |
| 5.4 | Section F – Deliveries or Performance |
| 5.4.1 | Deliveries or Performance schedules not identified in the PWS shall be completed by the Offeror in the Pricing Workbook attached in Section J. |
| 5.5 | Section I – Contract Clauses |
| 5.5.1 | The Offeror shall complete necessary fill-ins in Section I and submit as part of their Model Contract/Solicitation. The Offeror shall comply with the clauses specified within Section I of the Model Contract/Solicitation. Furthermore, any reference of a clause and/or provision in the solicitation will be adhered to and included in the resulting contract. All laws, regulations, and statutory authorities will also be applied within the Model Contract/Solicitation. |
| 5.6 | Section K – Representations, Certifications, and other Statements of |
| 5.6.1 | Offerors The Offeror shall provide completed representations, certifications, acknowledgments, and statements. |
| 5.7 | Exceptions to Solicitation Requirements |
5.7.1 Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 4 below.
TABLE 4: SOLICITATION EXCEPTIONS
| Solicitation Document |
| Page / Paragraph |
| Requirement / Portion |
| Rationale |
PWS,
Contract/Solicitation, ITO, etc.
Applicable Page and Paragraph Numbers
| Identify the requirement or portion to which exception is taken |
| Describe why the requirement can/will not be met |
5.8 Other Information Required
| 5.8.1 | Authorized Offeror Personnel – Provide the name, title, and telephone number of the company/division POC regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. Additionally, provide the name, title, and telephone number of the Chief Executive Officer, Division President, and/or Vice President. |
| 5.8.2 | Government Offices – Provide the mailing address, telephone, and facility codes for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), and Government Paying Office. Also, provide the name, telephone, and email address for the Administrative Contracting Officer (ACO). |
| 5.8.3 | Company/Division Address, Identifying Codes, and Applicable Designations – Provide company/division's street address, county and facility code; CAGE code; DUNS code; Taxpayer Identification Number (TIN); size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location. |
| 5.8.4 | Attachments to the Model Contract / Solicitation – The Offeror shall provide the following, and when accepted by the Government, will be incorporated on contract as attachments or by reference upon contract award: |
5.8.4.1 Small Business Subcontracting Plan – If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan IAW FAR 52-219-9, Small Business Subcontracting Plan that separately addresses and specifies the extent of the Offeror’s commitment to the participation of Small Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), Historically Underutilized Business Zone (HUBZone) Small Business, Small Disadvantaged Business (SDB), and with Women-Owned Small Business (WOSB) concerns. If the Offeror is submitting an individual contract plan, the plan must separately address subcontracting with SB, VOSB, SDVOB, HUBZone, SDB, and WOSB concerns with a separate part for the basic contract and separate part for each option (if any). The plan shall be included in and made a part of the resultant contract. Failure to submit and negotiate the subcontracting plan shall make the Offeror ineligible for award of a contract. If applicable, submit a copy of your approved Master Plan. In the event the Offeror has negotiated a comprehensive Subcontracting Plan pursuant to DFARS 219.702, The Small Business Contracting Program – Statutory Requirements, the Offeror must submit the information that identifies and specifies the extent of their commitment to the participation of SB, VOSB, SDVOB, HUBZone, SDB, and WOS
5.8.5 Technical Volume – The proposed Technical Volume, Volume II, when accepted by the Government, will be incorporated into the contract upon award. Updated documents, delivered as part of a CDRL, will supersede the documents provided as part of the proposal.
File details come from the government source that posted it. Updated .