PROS 7 Section L DRAFT RFP 2Jul25.docx

Solicitation: FA8630-26-D-XXXX Attachment 9, Section L 2 July 2025

DRAFT SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS FOR PREPARATION

1.0 Program Overview

The Air Force Security Assistance and Cooperation (AFSAC) Directorate located at Wright-Patterson Air Force Base OH manages the Parts and Repair Ordering System (PROS) contract that provides Commercial Buying Services (CBS) for Non-Standard and Difficult to Support Standard Items. The AFSAC PROS contract is a performance-based service acquisition providing supply, repair, and task order support services. This tri-service capable contract will support Air Force, Navy, and Army Foreign Military Sales (FMS) customers.

1.1 Budget/Funding Information

This is an Indefinite Delivery/Indefinite Quantity contract, including Firm Fixed Price (FFP) and Cost Reimbursable (CR) Contract Line-Item Numbers (CLINs). Contractor fill prices will be charged to a FFP CLIN; pass-through material costs (no profit allowed) will be charged to a CR CLIN. Funding will be provided for each individual requisition using FMS and Foreign Military Financing (FMF). The initial task order will be awarded for the competed price of the Contract Kick-off Meeting Proposed FFP at Section J, Attachment 5–Pricing Matrix which will satisfy the guaranteed minimum amount.

2.0 General Instructions and Information

The Offeror's proposal must include all data and information requested by these Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The proposal shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should 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 assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror's proposal.

Elaborate brochures, documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain the single digital submission of all unsuccessful proposals.

2.1 Point of Contact

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 Contracting Officer Alexis Spahn at alexis.spahn@us.af.mil.

2.2 Pre-Award and Post-Award Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range that desire a pre-award debriefing must submit a written request to the CO within three (3) days of receipt the competitive range exclusion notice. Be advised, Offerors excluded from the competitive range are entitled to no more than one debriefing.

The CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors have three (3) days to submit a written request for a post-award debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

To the maximum extent practicable, post-award debriefings will occur within five (5) days after receipt of the Offeror’s written request for debriefing. In accordance with DFARS 215.506-70, each Offeror receiving a post-award debrief will also have the opportunity to submit additional written questions related to the debriefing no later than two (2) business days after receiving the debriefing. The CO will respond in writing to timely additional questions within five (5) business days after receipt.

2.3 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 as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial requirements.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the official U.S. Government website for federal awards at sam.gov/. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of Controlled Unclassified Information (CUI)/Source Selection Information (SSI) between Government and Offerors will be controlled by the CO, utilizing the DoD Secure Access File Exchange (SAFE) to ensure proper encryption at https://safe.apps.mil/. If the Offeror needs to communicate with the CO regarding non-CUI/SSI information or to request a DoD SAFE-generated access code and hyperlink to drop-off (upload) non-CUI/SSI information regarding this solicitation, send an email to the points of contact in paragraph 3.2 of this document.

3.0 Volume Organization

3.1 General

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). This table must be tailored to reflect the proposal structure needed for your procurement. 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 as specified in Table 1. The contents of each proposal volume are described in the ITO paragraph as noted in the table below and should be clearly identified and labeled as such:

TABLE 1 – PROPOSAL ORGANIZATION BY VOLUME

3.1.1 Electronic Page Size and Format

A page is defined as the information contained in one electronic “page” meeting the requirements below. Page size shall be 8.5 x 11 inches, with exceptions described in the following paragraph. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom margins and ¾-inch side margins. Pages shall be numbered sequentially for each volume. These page size and format restrictions shall apply to EN responses.

Legible tables, charts, graphs, 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 single page size 11 x 17 inches for Volume Page Limit and formatted to print. Any pages exceeding 8.5 x 11 inches may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10-point font.

3.1.2 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 and excess pages will be redacted prior to sending them to the evaluation team. For example, a page limit of 10 means that page 1-10 will be evaluated, but pages 11 and beyond will not.

Each page shall be counted except the following: Cover pages, tables of contents, cross-reference matrix, tabs, glossaries, Small Business Subcontracting Plan, and all annotations of the PWS and Excel spreadsheets described in Paragraph 3.1.4.

Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

3.1.3 Cross-Referencing

To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with minimum cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. (Insert one of the following:)Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. (NOTE: If cross referencing within a volume is not allowed, the page limitation may need to be increased.)

Select one of the following:

(It is recommended that a matrix be provided. If you provide the matrix and require the offeror to fill it out, add:)

The Offeror shall provide a Cross Reference Matrix, which is a tool that shows critical interrelationships and dependencies among Section L (Instructions to Offerors), Section M (Evaluation Factors for Award), PWS, CLIN numbers, and CDRL references. All references shall contain the proposal volume, proposal page, and section number. The Cross Reference Matrix helps ensure compliance with all evaluation criteria and proposal submittal requirements identified in the solicitation.

3.1.4 PWS Changes

Offeror shall provide requirements language in the PWS for all strengths being attempted as part of this solicitation. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions. Inputs shall also be consolidated in an Excel spreadsheet with identifiers for PWS Page Number, PWS Paragraph Number, and Proposed Language. All inputs will be evaluated as part of the Technical Volume, Paragraph 3.5, and all annotations of the PWS and Excel spreadsheets are not subject to the 40-page limit.

3.1.5 Table of Contents per Volume

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

3.1.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, as well as an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

3.1.7 Electronic Offers

The electronic proposal shall be submitted in a format readable by Microsoft (MS) Office. All MS-Excel attachments shall be submitted in the MS-Excel format (unaltered) in which they are provided by this Request for Proposal (RFP). The Offeror shall not include any formulas or links beyond what is included in the provided format. Macros or other embedded objects or features will be disabled as part of regular security precautions. Electronic files must be unlocked in order to export the winning Offeror’s information into Government contract writing systems.

3.2 Distribution

All Offeror proposals shall be addressed to both the Primary and Alternate PoCs listed below and delivered via DoD SAFE according to the instructions in Section 3.1.7.

Primary:

Ms. Alexis Spahn AFLCMC/WFK Contracting Officer alexis.spahn@us.af.mil

Alternate:

Mr. Stephen Wells AFLCMC/WFK Contract Specialist stephen.wells.2@us.af.mil

Identify "Controlled Unclassified Information" and "Source Selection Information – FAR 2.101 and FAR 3.104” on all distributed materials.

3.3 Bid and Proposal Costs

Offerors are advised that costs of any response to, or other costs incurred as a result of responding to this solicitation, are at the Offeror’s own risk. Any costs incurred in preparing a response to this solicitation may be attributable to bid and proposal (B&P) overhead costs but may not be charged to any resulting awarded contract. B&P costs are indirect costs covered by CAS 420/FAR 31.205-18.

3.4 Volume I – Executive Summary

3.4.1 Volume Organization

The Executive Summary Volume shall be organized according to the following general outline:

a. Cover page

b. Table of Contents: Include a master table of contents for the entire proposal.

c. Glossary

3.5 Volume II – Gate 1

b. Table of Contents

c. Measure of Merit 1.1: FMS Logistics Contract Experience

3.5.2 Gate 1: Foreign Military Sales (FMS) Logistics Contract Experience The Offeror shall demonstrate experience, as a prime or subcontractor, supporting a Foreign Military Sales (FMS) Logistics contract, which may include Building Partner Capacity (BPC) efforts, within 36 months prior to receipt of this Request for Proposal (RFP) that involved the procurement, repair, or combination of both, and had a minimum value of at least $500,000 U.S. dollars for which they were solely responsible.

3.6 Volume III – Gate 2

a. Cover page

b. Table of Contents

c. Measure of Merit 2.1: Quality Control Program

3.6.1 Gate 2: Quality Control Program

The Offeror shall demonstrate current certification to Aerospace 9100 (AS9100) or an equivalent industry quality standard for aerospace/non-aerospace parts.

3.6.1.1 Measure of Merit (MoM) 2.1: Gate, Quality Control Program The Offeror shall provide proof of certification, including the certification body, certificate number, and expiration date. If an equivalent standard is proposed, the Offeror shall provide a detailed justification for its equivalency to AS9100.

3.7 Volume IV – Technical Volume

3.7.1 Volume Organization

In the Technical Volume, Offerors shall address their technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each Technical Subfactor. The Technical Volume shall be organized according to the following general outline:

a. Cover page

b. Table of Contents

c. List of Tables and Drawings

d. Glossary

e. Factor 1: Technical Processes

1. Measure of Merit 1: Non-Standard/Standard Parts, Ordering, Repair and Shipping

2. Measure of Merit 2: Customer Communication

3. Measure of Merit 3: Invoicing

4. Measure of Merit 4: PROS-IS Information Processing

5. Measure of Merit 5: Combating Obsolescence

3.7.3 Factor 1: Technical Processes

The Offeror shall describe an understanding of and sound proposed approach to the technical processes required to effectively complete the requirements of the PROS Program.

3.7.3.1 Measure of Merit (MoM) 3.1: Non-Standard/Standard Parts Repair, Ordering, and Shipping The Offeror shall provide a narrative outlining a sound approach and clear understanding of the definitions of Non-Standard and Standard parts as specified in the PWS. This narrative shall include:

a. Two (2) examples of both Non-standard and Standard parts (for a total of four (4) examples) relevant to this contract. Demonstrating an understanding of how Non-standard and Standard parts differ from each other.

b. The different requirements for Non-Standard and Standard parts ordering and repair.

c. Two examples of databases used to identify if an item is Non-Standard or Standard.

Given the two (2) scenarios below, the Offeror shall provide a proposed process flow chart for each, outlining a sound approach and clear understanding of the Non-Standard/Standard parts repair and ordering lifecycle.

a. For Scenario A, provide a step-by-step identification of the parts ordering lifecycle from acceptance to shipment.

b. For Scenario B, provide a step-by-step identification of the parts repair lifecycle from acceptance to shipment.

c. For both Scenario A and Scenario B, provide a description of each step of the required flowcharts to include:

i. Process for identification of potential suppliers.

ii. Process for acquiring bids.

iii. Methods for verifying supplier qualifications and reliability.

iv. Quality control measures for procured parts and repairs.

v. Process for managing lead times and potential supply chain disruptions.

vi. Process for coordinating with sub-vendors to manage the timely shipment and delivery of parts.

vii. A complete and accurate DD1348 for each part referenced in both Scenario A and B.

Note: Addresses are up to the Offerors’ imagination and will not be graded for correctness as the example country do not exist.

Scenario A:

The country of Banderia has requested the following part be procured:

SERIAL NUMBER:

Scenario B:

The country of Northrend has requested the following part be repaired:

U16G

SERIAL NUMBER: M33020

3.7.3.2 MoM 2: Customer Communication

Given the Scenario C listed below, the Offeror shall provide sound approach to clear and comprehensive communication outlining the methods, required information, and frequency of communication as defined in Section 3.5 of the PROS 7 PWS. This narrative shall include: Comment by SPAHN, ALEXIS J CIV DAF AFMC AFLCMC/WFKC: check this ref

a. Details on how the Offeror will provide regular updates on requisition status, potential issues, and any other relevant information.

b. A plan for utilizing appropriate communication technologies and platforms to facilitate effective information sharing and collaboration.

c. A description of the communication protocols for routine reporting, including the format, content, and frequency of reports.

Scenario C: Westeroth’s Widget

The country of Westertoth has requested repair for a Widget. Your company has received one bid for the repair. After determining fair and reasonable value for one bid, you award to a subcontractor and advise the country to ship the widget to the sub-vendor for repair. On day 75, the country affirms that the part was shipped that day via sea. On day 95, the part arrives at the sub-vendor who performs a test, teardown and inspection to determine cost of repair. The sub-vendor sends you a price quote for the repair, which comes to $135,000 dollars. The country has set a Not to Exceed (NTE) amount of $130,000. After approval for repair, the Estimated Completion Day (ECD) slips 20 days. The repair is finally completed on day 192 after receipt of the part. The item then ships back to the customer on day 200.

3.7.3.3 MoM 3: Invoicing

The Offeror shall provide a process flowchart with a narrative demonstrating a sound approach to the different invoice types and submission requirements outlined in PWS Section 4.7 through 4.7.4, including interim payments, final payments, material reimbursements, and fill fees. This flow chart and narrative shall:

a. Provide a detailed process for submitting accurate and compliant invoices, including a description of internal controls ensuring invoice accuracy and completeness.

b. Demonstrate the ability to adhere to the specified payment timelines and methods, including the prompt transfer of government funds to vendors and provide a description of its financial management systems and processes.

c. Clearly articulate an understanding of how to calculate and apply the Firm Fixed Price (FFP) fill fee according to Section B (Schedule), ensuring it encompasses all applicable costs, providing examples and demonstrating how it will track and account for these costs.

d. Describe the process for handling and documenting the material/repair service, disposal charges, prepayments (with required documentation) and customer credits, providing examples of how each scenario will be handled.

e. Describe the process and/or system for tracking and managing vendor invoices and ensuring all necessary supporting documentation is included with each interim payment request, including a description of the planned document managing system.

f. Describe the process for reconciling interim payments with the final payment request, ensuring all vendor invoices are processed before submitting the final invoice.

3.7.3.4 MoM 4: PROS-IS Information processing

The Offeror shall provide a narrative demonstrating a sound approach and clear understanding of how the PROS-IS will be used to process and monitor all PROS requisitions throughout the requisition life cycle, including the identification of potential technologies and frameworks to be used of which the offeror has demonstrated experience. This narrative shall:

a. Include a detailed explanation of how it will handle the required data elements for each requisition, including the FMS country's Letter of Offer and Acceptance (LOA) case designator, line-item authorization, and other necessary information, demonstrating an understanding of the data requirements and the ability to accurately populate the required fields.

b. Describe a process for acknowledging requisitions within the PROS-IS upon receipt, including the specific procedures for generating and submitting acknowledgement codes.

c. Describe a process for managing and tracking requisitions throughout the entire lifecycle, from receipt to fulfillment, ensuring efficient processing and allowing for progress monitoring.

d. Demonstrate a clear understanding of the different Levels of Service (LOS) and how they will be applied to requisition processing, showing the ability to prioritize and manage requisitions based on urgency and importance.

e. Describe internal quality control measures to ensure accurate and complete requisition processing, which could include data validation checks, automated processes, or other methods to minimize errors.

3.7.3.5 Measure of Merit 5: Combating Obsolescence

The Offeror’s approach shall demonstrate obsolescence identification, reporting, and forecasting. The Offeror’s approach shall include examples to address the challenges of obsolescence with today’s technology. The Offeror shall also address any partnering relationships for technology solutions. The Offeror shall address First Article Testing (FAT) for any proposed technology solution to satisfy OEM traceability.

Offeror shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength under this Measure of Merit. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

3.8 Volume V - Past Performance

3.8.1 General

Each Offeror shall submit a Past Performance Volume with its proposal. This information is required for the prime Offeror. The prime Offeror may submit past performance information (PPI) for any subcontractor regardless of proposed contract percentage performed, however, it is required (to the extent such information is available) for all significant subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 10 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance. Offerors shall utilize the PPI Tool (See Attachment L-4 and L-5) to identify their Past Performance Citations and Past Performance Information.

Along with the information required in this section, the Offeror shall submit a consent letter signed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information (see Section 3.4). For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

Prime Offerors may submit up to five (5) past performance citations, not including subcontractor citations. If a significant or critical subcontractor is proposed as part of this effort, the Offeror may submit up to two (2) past performance citations for each significant or critical subcontractor in which they performed 10% or more of the work in the citation, if past performance information is available. The Government will consider performance that has been performed during the past three (3) years from the date of the issuance of this solicitation or is ongoing with at least six (6) months of completed performance elapsed. If no relevant past or present performance information exists, do not submit a Volume III.

3.8.2 Format

This Volume shall provide recent and relevant performance citations in the format requested below:

1. Past Performance Information (see paragraph 3.8.3 below)

2. Relevancy Discussion (see paragraph 3.8.4 below)

3. Organizational Structure Change History (see paragraph 3.8.5 below)

4. Consent Letters. Consent letters executed by each joint venture partner and/or subcontractor, authorizing release of adverse past performance information so the Offeror can respond to such information (see paragraph 3.8.7 below).

5. Client Authorization Letters. Client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance.

6. List of Questionnaire Recipients

3.8.3 Past Performance Information

Offeror shall utilize the PPI Tool (See Attachment L-4 and L-5) to identify their Past Performance Information in the Past Performance Volume.

3.8.4 Relevant Contracts

For each citation, include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining Recency and Relevancy, see Section M, Paragraph 2.6, Past Performance. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, because the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required. Categorize the relevant information into the specific Technical Subfactors used to evaluate the proposal.

3.8.5 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror(s), your “roadmap” should be both specifically applicable to the efforts you identify and general enough to apply to efforts to which the Government receives information from other sources. Include Commercial and Government Entity (CAGE) codes for any predecessor companies to facilitate Government research.

3.8.6 Past Performance Questionnaires

The Government requests the Offeror send out Past Performance Questionnaires, Attachment L- 3 and L-4, for each citation to at least two Government points of contact. The Offeror shall send a standard transmittal letter to request the points of contact complete an unclassified Past Performance Questionnaire and submit via email five (5) working days after release of this solicitation. Preferred points of contact are, in order of descending preference: program manager, procurement contracting officer, technical or engineering lead. The Government requests completed questionnaires should be submitted directly to the Primary and Alternate PoCs listed in Section L 3.2, no later than 3:00 p.m. Eastern Time on XX Aug 25. The Offeror is solely responsible for ensuring that questionnaires are submitted in time for use in the evaluation process and shall make every effort to achieve this objective. Once the Past Performance Questionnaires are completed, the information contained therein shall be considered sensitive and shall not be released to the Offeror. The Offeror shall verify the POC information is current and valid. The evaluation team may conduct follow-up discussions with any of the POCs and reserves the right to send out additional questionnaires. Any information gained from these follow-up discussions may be used for evaluation purposes.

Past performance information submitted concerning subcontractors and teaming partners, if proposed, cannot be disclosed to a private party without the subcontractor’s or teaming partner’s written consent. Because the Offeror is a private party, the Government requires consent before disclosing subcontractor/teaming partner past performance information to the Offeror during exchanges.

3.8.7.2 Consent Letter

To assist the Government evaluators in assessing past performance relevancy and confidence, request the consent letter (if any) be completed by the major subcontractor/teaming partners identified in your proposal. The written consent(s) should be submitted as part of the Past Performance Volume. Should the Offeror not submit consent, the Government will only discuss past performance information directly with the prospective subcontractor or teaming partner that is being reviewed. If there is a problem with the proposed subcontractor’s or teaming partner’s past performance, the Offeror can be notified of a problem, but no details may be discussed without the subcontractor’s/teaming partner’s permission.

3.8.8 Contractor Performance Assessment Reports (CPARs)

Offerors shall identify the existence of past performance information in the Past Performance Volume. If this information is located outside the CPAR system, Offerors shall indicate where that information exists and are encouraged to provide additional information regarding the work effort to clearly describe how it relates to the PWS requirements. If a CPAR or other evaluation form has been accomplished on the Offeror’s existing work but has not yet been posted to an automated system, the Offeror is requested to advise the CO and provide a point of contact and phone number from which the information may be obtained. This information should be provided to the CO at the same time the Past Performance Volume is submitted. Also include information on cited contracts that has been captured in a database other than those used by DoD or other federal agencies.

3.9 Volume VI – Price Volume

3.9.1 General Instructions

This section is to assist Offerors in submitting data other than certified cost or pricing data required to evaluate the reasonableness of their proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price Volume. Data beyond what is required by this instruction shall not be submitted, unless considered essential to document or support the Offeror’s price position. Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror.

No pricing data or information shall be included in any other volume, including cover letters, unless specifically requested by the Government in the respective volume. If price information is included elsewhere in the documentation, the proposal may be deemed unacceptable and the proposal may not be evaluated. The Offeror shall comply with the intent of the pricing instructions in supplying information that is current, timely, and in full support of the proposal. Exceptions or deviations will not be accepted. The instructions for preparation of the content of the Price Volume shall not take precedence over requirements of other clauses of the contract, Public Law, or the FAR, as supplemented.

3.9.2 Price Data

The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

3.9.2.1 Rounding

All dollar amounts provided shall be rounded to the nearest dollar.

3.9.2.2 Volume Organization

The Offeror shall submit a proposal to capture prices for all contract line items listed in the Section J, Attachment 5–Pricing Matrix. The Offeror shall not tamper with the provided rows, columns or formulas or add any information to required worksheets, other than what is requested in the Pricing Matrix Instructions. The evaluation for future quantities are based on historical actuals represented in the Pricing Matrix. These quantities are used as a basis for evaluation since future quantities are unknown. The Offeror shall develop and input a proposed fill price for each criterion highlighted yellow in the spreadsheets. The total price for the basic and option years of the contract will be automatically calculated based upon the estimated historical quantities and fill prices. Instructions for completing the Pricing Matrix are located within Section J, Attachment 5–Pricing Matrix, and Instructions Worksheet. The Firm Fixed Price (FFP) Fees and Contract Kick Off Task Order proposed in Attachment 5–Pricing Matrix will be contractually binding.

CLIN MATRIX

FIRM FIXED PRICE CLINs:

COST REIMBURSEMENT NO FEE NO PROFIT CLINs:

The Offeror shall propose price for the Initial Task Order – Contract Kick Off Implementation at PWS 4.8.1 and IAW Section J, Attachment 5–Pricing Matrix.

The Offeror shall not propose fill prices for FFP CLINs: Task Orders CLINs 0003 – 9003. The Task Order price will be and negotiated at the time of need. These will not be evaluated as part of the Total Evaluated Price (TEP).

The Offeror shall not propose prices for the following Cost Reimbursable (CR) CLINs: Travel CLINs 0004 – 9004. These will not be evaluated as part of the Total Evaluated Price (TEP).

The Offeror shall not propose prices for the Data CLINs 0007 – 9007, as this is a Not-Separately-Priced (NSP) CLIN that will be utilized for Contract Data Requirements List (CDRL) reporting.

The Offeror shall not propose prices for the CR Material / Maintenance Vendor Invoiced CLINs 0006 – 5006. These will not be evaluated as part of the Total Evaluated Price (TEP).

3.10 Volume VII - Contract Documentation

3.10.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the USG for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Model Contract, (SF 33), and any completed attachments from Sections A through J; Section K is contained in System for Award Management (SAM).

3.10.2 Section A – Solicitation/Contract Form

Completion of Blocks 13, 14, 15, 16, 17, and 18 and signature and date for Blocks 17 and 18 of the SF33. Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept. The "original" proposal should be clearly marked under separate cover.

3.10.3 Section B – Supplies or Services and Prices

No special instructions. Do not enter prices into Section B, as they will not be evaluated. Price evaluation will be accomplished via Section J, Attachment 5 – Pricing Matrix.

3.10.4 Section C – Description/Specs/Work Statement

Performance Work Statement will be a Section J attachment.

3.10.5 Section F – Deliveries or Performance

No special instructions.

3.10.6 Section G – Contract Administrative Data

No special instructions.

3.10.7 Section H – Special Contract Requirements

No special instructions.

3.10.8 Section I – Contract Clauses

No special instructions.

.10.9 Section J – Attachments The Offeror shall complete and/or provide the following documents to the USG:

· Attachment 2: DD Form 254 – Contract Security Classification Specifications

· Attachment 3: Small Business Subcontracting Plan

· Attachment 5: Pricing Matrix

The USG will provide the following documents to the Offeror:

· Exhibit A: DD Form 1423 Contract Data Requirements List (CDRL)

· Attachment 1: Performance Work Statement (PWS)

· Attachment 4: Supply Discrepancy Report (SDR) Process

· Attachment 6: Specifications and Standards

· Attachment 7: Wage Rate Determination

· Attachment 8: SDR Process

3.10.10 Section K – Representations, Certifications, and other Statements of Offerors Offer must provide completed representations, certifications, acknowledgments and statements in System for Award Management (SAM) at www.sam.gov.

3.10.11 Section L – Attachments

The Offeror shall complete and/or provide the following documents to the USG:

Attachment 1: Cross Reference Matrix Attachment 2: Subcontractor/Teaming Partner Consent Letter for the Release of Past and Present Performance Information to the Prime Contractor (If applicable) Attachment 3: Client Authorization Letter (If applicable) The USG will provide the following documents to the Offeror:

Attachment 4: Past Performance Information Tool Instructions Attachment 5: Past Performance Questionnaire Shall be distributed by offeror to USG Contract POCs completing the questionnaire POC List and Contact information shall be submitted as part of Volume V

3.10.12 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, including, but not limited to, 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. 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 2. The Government reserves the right to reject any exceptions taken to the proposal requirements and consider such offers unacceptable.

TABLE 2 - Solicitation Exceptions

can/will not be met

3.11 Other Information Required

3.11.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact whom is authorized to make decisions with respect to the proposal, negotiate with the Government, and obligate the company contractually. Also provide the name, title and telephone number of the CEO, Division President, and/or Vice President.

3.11.2 Government Offices

The contract will be administered locally by the following:

Ms Alexis Spahn, Procurement Contracting Officer Bldg. 209, 5454 Buckner Road Wright-Patterson AFB, OH 45433-5337 Alexis.spahn@us.af.mil 937-656-2684 Payments will be made by:

Defense Finance and Accounting Service (DFAS)-CO/JAK 3390 East Broad Street, Bldg. 21 Columbus, Ohio 43213

3.11.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; Data Universal Numbering System (DUNS) number; Tax Identification Number (TIN); size of business (large or small) under North American Industry Classification System code (NAICS) 541614; 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.