DRAFT ATTACHMENT 6 - Instruction to Offerors (52.212-1).pdf

ATTACHMENT 6 – INSTRUCTIONS TO OFFERORS

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS

1.0 Program Structure and Objectives

The Government plans to award a single contract for the A4M/R Aircraft Battle Damage Repair (ABDR) program. The ABDR Trailers will replace the current trailers built on top of aged demilitarized MHU-12 and MH-141 ammo trailers with organic provisions. The ABDR Trailers acquisition includes the production and delivery of a contract ceiling of eighty-three (83) ABDR Trailers that will reside at multiple oversea locations (description of program).

1.1 Award will be made on the basis of best value utilizing Tradeoff Source Selection Procedures. Award will be made to the contractor that provides the best value to the Government over the entire period of performance.

1.2 Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) for the initial purchase of the First Article (CLIN 0001) and the subsequent ABDR Trailers (CLIN X0002).

1.3 Contractor Technical Proposal

All or parts of the Contractor’s Technical Proposal may be added to the contract. Should there be any discrepancies between the Technical Proposal and the Statement of Work (SOW), the SOW will take precedence unless otherwise approved by the Procuring Activity

2.0 General Instructions

2.1.1 This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. Any Offeror who submits an incomplete package may be considered ineligible for award. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP), to include but not limited to, it’s attachments and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

2.1.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 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 shall 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.

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

2.1.4. The proposal acceptance period is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid until this date.

2.1.5. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

2.2. General Information

2.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 the CO at the address located in Section A of the model contract/solicitation.

2.2.2. 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 may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in accordance with FAR 15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.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 proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the System for Award Management (SAM) website at https://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.2.5. Amendments to Solicitation

If this RFP is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the Offeror’s proposal. Any unacknowledged amendments in the Offeror’s proposal are subject to solicitation provision FAR 52.212-1(f).

2.2.6. Submission, Modification, Revision, and Withdrawal of Proposals Proposal packages shall be transmitted to the Solicitation CO via DoD SAFE (safe.apps.mil). Physical delivery of proposal packages will not be accepted. See ITO sections 2.6 & 2.7.

2.2.7 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the subject line.

2.3. Organization/Number of Copies/Page Limits

2.3.1. The Title Page of each volume shall contain the solicitation number, name, address, telephone of the Offeror, and Commercial and Government Entity (CAGE) code.

2.3.2. A Team List of the Offeror’s primary Point of Contacts shall be submitted in each volume using the format shown in Attachment 1.1 of the ITO.

2.3.3. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). 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 2.2. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.3. Proposal Organization

Volume

ITO

Paragraph

Number

Volume Title

Electronic

Copies

Page Limit

I 3.0 Factor 1 - Technical 1 25 https://sam.gov/

3.2.2 Title Page (Not included in 25 page limit) 1

3.2.2 Team List (see Attach 1.1) (Not included in 25

page limit)

3.2.2 Table of Contents Unlimited

3.2.2 List of Tables and Drawings Unlimited

3.2.2 Glossary of Abbreviations and Acronyms Unlimited

3.2.3

3.2.4

3.2.5

Subfactor 1 ATTLA Certification, First Article, and Data Rights Subfactor 2 Trailer Functions and Support Equipment Subfactor 3 Tool Cabinets Installed into Trailers

Included as part of the 25 page limit

II 4.0 Factor 2 - Past Performance 1 25

2.2.1 Title Page (Not included in 25 page limit) 1

2.2.2 Team List (Not included in 25 page limit) 5

4.1 Past Performance Information Forms (PPIF)

(See Attach 3.1)

4.1.2 Consent Letter (See Attach 3.2) Unlimited

4.1.3 Client Authorization Letters (See Attach 3.3) Unlimited

4.1.4 Commitment to Perform as Proposed Letter

(See Attach 3.4) Unlimited

4.2 Present/Past Performance Questionnaires

(See Attach 3.5)

Tab Only

4.3.2 Relevant Contract Narrative Request Max 5

pages per contract

4.3.4 Roadmap 2

III 5.0 Factor 3 - Price 1 Unlimited

5.2 General Information Unlimited

5.4 Volume Organization Unlimited

IV 6 Contract Documentation 1 Unlimited

2.2.1 Title Page (SF1449) 1

2.2.2 Team List (see Attach 1.1) 5

2.2.3 Table of Contents Unlimited

2.2.9 List of Tables and Figures Unlimited

2.2.10 Glossary of Abbreviations and Acronyms Unlimited

6.1 Model Contract (Sections 1-2) N/A

6.1.4 Representations and Certifications N/A

6.3.1-

6.3.4 Contact Information Unlimited

6.3.5 Attachments to the Model Contract Unlimited

2.3.4 Names

Offerors shall submit volumes with the following file names: Volume I – Technical.doc or .docx, Volume II – Past Performance.doc or .docx, Volume III – Price.doc or .docx with PricingMatrix.xlsx, and Volume IV – Contract.doc or docx. Files provided in .pdf format are also acceptable if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text.

2.3.5. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be considered in the evaluation of the proposal. Page limitations may also 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. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited.

2.3.6. Pricing Information

All pricing information shall be addressed ONLY in the Price Proposal and Contract Documentation volumes. Cost tradeoff information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and tradeoff decisions.

2.3.7. Cross Referencing

The Technical 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 the technical proposal evaluation, which is not found the Technical volume, will be assumed to have been omitted from the proposal, and will not be considered in the technical evaluation. Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity. The Past Performance and Price evaluation will utilize information from each’s respective volume for the evaluation but may also utilize information from other volumes as well.

2.3.8. Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.3.9 Tables and Figures

Include an indexed list of Tables and Figures and Drawings.

2.3.10. Glossary of Abbreviations and Acronyms

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

2.4. Page Size and Format

2.4.1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Page line spacing shall be 1.5 lines. Except for the reproduced sections of the solicitation document, the text size shall be no less than Arial 12 points. Offerors are prohibited from using other Arial fonts such as Arial Black, Arial Narrow or Arial Rounded MT Bold. 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 and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notice (ENs).

2.4.2 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 and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, 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. The following limitation only applies to the Technical Volume. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8-pt. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation.

2.5. Labeling

A cover sheet shall be included in each proposal volume, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. For each proposal volume, the Offeror shall 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.6. Electronic Offers

All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested Offerors must e-mail Chelsea Kuykendall (chelsea.kuykendall@us.af.mil) in order to receive a request code to drop-off (upload) files in DoD SAFE. One of the Government Points of Contact (GPOCs) will send an e-mail to the Offeror acknowledging the request for a proposal drop-off code in DoD Safe. The GPOC e-mail acknowledging the request will not be sent to the Offeror after close of business hours, weekends, or on nationally observed holidays. If you do not receive an acknowledgement e-mail from either of the GPOCs after 72 hours, you must send another e-mail. E-mails will not be returned after close of business hours, weekends, or on nationally observed holidays. After the e-mail request for a drop-off code has been sent from the Offeror and the Offeror has received the acknowledgment e-mail from either GPOC, the Offeror will then receive an e-mail from DoD SAFE to drop-off proposals and other requested documents. If the Offeror does not receive the e-mail from DoD SAFE the Offeror will need to check SPAM and JUNK folders before requesting another drop-off code from the GPOC. The request for drop-off is only valid for 14 days. If the 14 days has expired and the RFP is still open, the Offeror may send another e-mail request for drop-off code to the GPOCs e-mail addresses listed above.

Be advised that classified information is not allowed on DoD SAFE. Any files containing CUI/PII/PHI must be encrypted prior to uploading or by checking the “Encrypt every file” box. The Offeror is allowed to drop-off one or more files (up to 8GB total). The Offeror may select the box ‘Send me an e-mail when each recipient picks up the files” for documentation purposes. The GPOC will receive an automated e-mail containing the information the Offeror has entered and instructions for downloading the file(s). The GPOC will have 7 days to retrieve the files submitted in the drop-off. DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours. All electronic documents and files submitted shall contain the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The Offeror shall submit volumes I through IV in electronic format. Each volume shall be submitted as a separate file. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 365 Word, MS Office 365 Excel, MS Office 365 Power Point, and Adobe PDF Note: files must be searchable and able to copy and paste. For amendment purposes to the proposal, the "original" proposal shall be clearly identified.

2.7. Distribution

2.7.1 Once the Offeror has uploaded the Offeror’s proposal in its entirety DoD SAFE, the Offeror shall take a screen shot (Print Screen function) of the Offeror’s DoD SAFE upload confirmation screen showing all the uploaded files included in the proposal submission. The Offeror shall notify Chelsea Kuykendall by email that the files have been uploaded and provide a copy of the DoD SAFE completed upload confirmation screen shot. If the proposal files are uploaded in their entirety prior to the proposal closing date and time, and the Offeror has notified Chelsea Kuykendall the files have been uploaded (notification is to include the DoD SAFE upload confirmation screen shot has also been provided), the proposal will be considered timely, even if the files are not accessible to the PCO in DoD SAFE until after the proposal closing date and time. If the Offeror fails to notify Chelsea Kuykendall by email, the files will be considered timely if they are accessible in DoD SAFE prior to the closing date and time. However, they will be considered late proposals, if they are not accessible until after the proposal date and time.

Email addresses are as follows:

Chelsea Kuykendall: chelsea.kuykendall@us.af.mil Kaysi Simmons: kaysi.simmons@us.af.mil

3.0 Factor 1 – Technical

3.1. General

The Technical Volume should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Addendum to FAR 52.212-2, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. Offerors shall assume that the government has no prior knowledge of their experience or facilities and will base its evaluation on the information presented in the proposal. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation.

It is neither necessary nor desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

3.2.1. Technical

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor.

3.2.2. Volume Organization

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

(1) Title Page

(2) Team List (See ITO Attachment 1.1)

(3) Table of Contents

(4) List of Table and Drawings

(5) Glossary of Abbreviations and Acronyms

(6) Subfactor One – ATTLA Certification, First Article, and Data Rights

(7) Subfactor Two – Trailer Functions and Support Equipment

(8) Subfactor Three – Tool Cabinets Installed into Trailers

3.2.3. Subfactor One: ATTLA Certification, First Article, and Data Rights

The Offeror shall provide an approach for the ABDR Trailers. At a minimum, the approach shall provide the following essential elements:

a) An approach to Air Transportability Test Loading Activity (ATTLA) certification requirements. At a minimum, the approach must describe how the offeror will achieve ATTLA certification requirements prior to First Article delivery. The approach should include utilizing and inputting data required for the ATTLA Universal Data Sheet excel under the following tabs applicable to this acquisition:

Instructions for Airlift Certification, General Info, Trailer Type 1, Trailer Type 2, and Pictures/Drawings in accordance with SOW section 1.8.1.

b) An approach to First Article and Production requirements. At a minimum, the approach shall describe how the offeror will meet First Article and production deliveries of ABDR Trailers. The proposal shall include a single milestone schedule for all deliveries in accordance with SOW paragraphs 1.8.1 and 1.8.2 .

The approach must also describe any mitigations that are or will be enacted to minimize potential supply chain issues in meeting the delivery schedule for First Article and subsequent production units.

c) The Offeror shall provide a completed CDRL Assertion Matrix (ITO Attachment 2.1) indicating data rights asserted/proposed, given consideration to the data rights requested by the Government. Anything less than what the Government requested on ITO Attachment 2.1, CDRL Assertion Matrix, the Offeror shall fully justify and describe how their Intellectual Property assertions will impact fielded system’s organic sustainment and repairs. The Offeror shall not add rows or columns to the matrix. If applicable, the required justification and description shall be included in the technical volume and not in the Attachment.

3.2.4. Subfactor Two: Exceeding Requirements contained in the SOW Trailer Functions and Support Equipment

Offerors are afforded an opportunity to receive best value credit for a proposed approach which exceeds SOW requirements related to the criteria listed below.

The best value credit will be applied as strengths or significant strengths to the offeror’s proposal. Within the Offeror’s Technical proposal, the Offeror shall indicate areas of the proposed approach which exceed requirements. The Government will not consider strengths/significant strengths for requirements that are not described within the Offeror’s proposal. The Offeror shall provide supporting information and rationale for each area the Offeror’s proposed approach should receive consideration as a strength/significant strength for exceeding requirements to the criteria listed below. The Government will only evaluate the approach for potential strengths/significant strengths for requirements where the Offeror has indicated a proposed strength/significant strength. For requirements that the Offeror does not describe and/or provide sufficient supporting rationale for a proposed strength/significant strength, the Government will not assign any strengths/significant strengths.

a) Trailer Tow Bar and Parking Brake System, SOW 1.3.3

b) Trailer Environmental Resistance, SOW 1.3.6

c) Trailer Pneumatic Connections, SOW 1.3.8 thru 1.3.8.4

d) Trailer Workstations, SOW 1.3.9 thru 1.3.9.3

e) Trailer Material Storage, SOW 1.3.10 thru 1.3.10.3

f) Trailer Tools, Foam, and PVC, SOW 1.5 thru 1.5.3.3

g) Trailer Servicing Criteria, SOW 1.6 thru 1.6.3

If the Offeror chooses to not address this section, either in part or in whole, the offeror shall state so in the proposal. If the offeror does not address this section, and the proposal does not state the section is intentionally blank, the Government will assume the section is intentionally blank.

3.2.5 Subfactor 3 Tool Cabinets Installed into Trailers

The Offeror shall provide an approach for the Tool Cabinets Installed into ABDR Trailers.

At a minimum, the approach shall provide the following essential element:

a) An approach to Tool Cabinets Installation. At a minimum, the approach shall describe how the offeror will install and mount tool cabinets with the physical dimensions and specifications in accordance with SOW paragraphs 1.4.1, 1.4.2, 1.4.3, 1.4.4 and 1.4.5 to include all subparagraphs.

b) An approach to all required Tool Installation. At a minimum, the approach shall include all required tools in Attachment X- Inventory Listing (maybe change the name to Tool Inventory Listing). The approach shall also describe install of foam precut out foam for tooling IAW SOW paragraphs 1.5.2.1-1.5.2.3. and PVC attached beneath the foam for each tooling cabinet IAW SOW paragraphs 1.5.3.1-1.5.3.3.

4.0. Factor 2 – Past Performance.

4.1. General

4.1.1. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 3.1 of the ITO. The Past Performance volume shall include a title page, team list, which includes the prime contractor, all significant subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. The Offeror shall describe the portion of effort each team member is proposed to perform in relation to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude and Complexity. The Government Past Performance Evaluation Team (PPET) evaluates each member of the Offeror’s team for relevancy and performance quality, based on their proposed portion of effort. Therefore, it is important for the Offeror to provide a detailed portion of effort description, in order for the PPET to conduct an accurate assessment. Offerors shall also provide approximate percentages for portion of effort for each team member. For the Past Performance evaluation, the Government will use data provided by the Offeror in the Past Performance volume, as well as data obtained from other sources.

4.1.2. ITO Attachment 3.2 Consent Letter. This letter shall be executed and signed by each subcontractor, teaming partner, and/or joint venture partner. The letter authorizes the release of adverse past performance information to the Offeror so the Offeror can respond to such information.

4.1.3. ITO Attachment 3.3 Client Authorization Letter. For each identified effort for a commercial customer, the Offeror shall submit a client authorization letter (Attachment 1.5) authorizing release to the Government of requested information on the Offeror’s performance.

4.1.4. ITO Attachment 3.4 Commitment to Perform as Proposed Letter. This letter shall be executed and signed by the Prime contractor and each Subcontractor. The letter states that, in the event a contract is awarded to the Prime Contractor, the Prime Contractor and Subcontractor (to include teaming partners, and/or joint venture partners) commit to joint contract performance as described in the proposal. A separate letter shall be completed for each subcontractor separately. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, the subcontractor references will not be evaluated or considered. In the event the signed letter is not submitted with the initial proposal, but is later submitted during the evaluation, the subcontractor references will be considered at that point.

4.2. Early Proposal Information

4.2.1 Each offeror is requested to submit the Past Performance volume fifteen (15) calendar days prior to the solicitation closing date. The Past Performance volume early proposal information is a request, and not a requirement. Failure to submit early proposal information will not result in offeror disqualification, nor will offerors be penalized.

4.2.2. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (ITO Attachment 3.5) and e-mail it and the Performance Questionnaire Letter (ITO Attachment 3.6) to all points of contacts (POCs) the Offeror has listed in the Past Performance Information Form (ITO Attachment 3.1). The POCs will complete the questionnaires and forward them directly to the Past Performance Evaluation Team (PPET). (Attn: Chelsea Kuykendall). Email address for questionnaires is chelsea.kuykendall@us.af.mil. RESPONDENTS TO THE

QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS

BACK TO THE OFFEROR. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The PPET will conduct such follow-up with any POC as necessary.

4.3. Relevant Contracts

4.3.1. The Offeror shall provide Past Performance Information (PPI) on current or previous contracts (or efforts). The PPI shall be completed in accordance with Addendum to FAR 52.212-1, Attachment 1.1, Past Performance Information Form (identified in this document as “PPIF”). The Offeror shall submit PPIFs for contracts which include all or some performance within the past three years, as defined in Addendum to FAR 52.212-2, para 2.3.2.1 Recency Assessment. Request each offeror submit up to three (3) PPIFs for the prime contractor, and up to three (3) PPIFs for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 5% of the total effort, or a contractor who is proposed to perform less than 5% of the total effort but is determined to be performing a critical function. NOTE: The requested number of PPIFs for the prime and subcontractors are preferences and not requirements. Offerors may submit more than the preferred number if the Offeror believes the extra contracts are needed to fully describe their relevancy. Offerors who submit less than the preferred number of PPIFs are not automatically assigned a “Neutral Confidence” rating. Fewer numbers may be acceptable, if the Government determines there is sufficient information to determine a confidence rating. Request each PPIF not exceed a target of 5 pages, although more or less may be submitted, if necessary and relevant to the ABDR Trailers program.

4.3.2. PPI Relevant Contract Narrative

For each PPIF, the Offeror shall provide a narrative explaining what aspects of the contract is deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. Specifically, the narrative should focus on similarities to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude, and Complexity, as defined in Addendum to FAR 52.212-2, paragraph 2.3.2.2, and should be tailored to the proposed portion of effort. Categorize the relevant information into the specific technical subfactors and price assessment used to evaluate the proposal. The narrative 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, since 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 shall 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. The Offeror is requested to limit the narrative to a maximum of 3 pages. However, the Offeror may exceed the requested page limit, if determined necessary to fully describe relevancy.

4.3.3. If subcontractor experience is submitted for consideration as part of the proposal, the offeror should include a commitment signed by offeror and subcontractor certifying that if a contract is awarded resulting from the proposal, the parties commit to joint performance as proposed. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, subcontractor references will not be evaluated or considered.

Affiliate companies, sister companies, teaming arrangements, joint venture agreement, etc., will be considered, provided that sufficient documentation is included in the proposal. The Prime contractor must demonstrate that the affiliate will perform significant and critical aspects of the contract if awarded. Proposal documentation should include a copy of the signed arrangement such as documented affiliation, a copy of the teaming agreement, a copy of the joint venture agreement, etc. If the required information is not included in the proposal, the proposed affiliate companies, sister companies, joint venture companies, etc. not be evaluated or considered.

4.3.4. 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 past efforts or between the 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, offeror’s shall include a "roadmap" describing all such changes in the organization of the offeror’s company. A pamphlet or other commercial document describing such reorganizations may suffice. 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), the "roadmap" should be both specifically applicable to the efforts identified, yet general enough to apply to efforts on which the Government receives information from other sources.

5.0. Factor 3 – Price

5.1. In the price volume, the Offeror shall provide the following information in addition to the pricing in Supplies or Services and Prices/Cost Section (Part B) of the solicitation.

These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

5.2. General Instructions

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

Offeror’s pricing proposal will be evaluated for reasonableness, balance, and realism.

Unreasonable and/or unrealistic proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Additionally, unbalanced pricing may pose an unacceptable risk to the Government and may render an Offeror’s proposal ineligible for award. Offers should be sufficiently detailed to demonstrate their price reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror

5.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition but may also be determined through other price analysis techniques. The burden of proof for credibility of proposed costs/prices rests with the Offeror. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.). It shall be noted that completeness is one aspect of price reasonableness. For completeness, the Offeror shall provide unit prices and/or rates for all listed items in the Pricing Matrix (ITO Attachment 4.1). If an Offeror’s proposed unit price or rate is zero, then the Offeror shall provide rationale to support the zero dollar/rate entry.

5.2.2 Balanced Pricing

The Government will evaluate proposals for balance. The Offeror is cautioned against submitting an offer which exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable or unrealistic prices. For this acquisition, balanced pricing is determined with respect to year-to-year price variances for separately priced CLINs. Offerors shall provide rationale for any proposed CLIN price increase greater than 5% from one year to another, or any proposed CLIN price decrease from one year to another. In addition, the Offeror shall provide rationale for any proposed CLIN price that does not change from one year to another. Unexplained price variances from year-to-year could suggest unbalanced pricing. It is in the Offeror’s best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

To assist in the determination of balanced pricing, Offerors shall complete the attached Pricing Matrix (ITO Attachment 4.1). Completion of the Pricing Matrix allows efficient comparison of proposed pricing with the PWS requirements.

5.2.3 Price Realism

The Government will evaluate proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements and to ensure the proposed price does not pose an unacceptable risk to performance.

Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc).

5.2.4. Cost or Pricing Information Requirements

FAR 15.4 applies as appropriate. Specifically, FAR 15.404-1 applies regarding proposal analysis. Price analysis techniques shall be utilized to ensure fair and reasonable pricing in accordance FAR 15.404-1(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process.

FAR part 15 applies. In accordance with FAR 15.403-3-1(b), prices based on adequate price competition do not require submission of cost or pricing data. In accordance with FAR 15.403-3(a), however, information other than cost or pricing data may be required to support price reasonableness. FAR 15.403-3(a)(1) provides for obtaining information other than cost or pricing data if needed to determine price reasonableness. Therefore, the FAR does not preclude the requirement for obtaining other than cost or pricing data under certain circumstances and the Government reserves the right to obtain data as appropriate. Should the CO determine proposed prices to appear unreasonable or the possibility that an Offeror does not fully understand the requirement, the offerors may be required to support price reasonableness via other than cost or pricing data. 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.

5.2.5. Rounding

All dollar amounts shall be rounded to the nearest penny.

5.3 Pricing Support Information

5.3.1 Annual Price Changes

Proposed price increases greater than 5% per period shall be verified and addressed for reasonableness in this section.

5.3.2 Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in this section. Offerors are requested to address any proposed prices which reflect a business decision to offer prices at or below cost.

5.3.3 Probable Subcontractors

Submit a list of the proposed probable subcontractors and inter-divisional transfers showing (a) the supplier, (b) description of effort, and (c) type of contract.

5.3.4 Submission of Price/Cost Models

Submit an electronically encoded price/cost model in support of the proposed Total Evaluated Price (TEP). Any price/cost model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. Price models submitted must comply with the following format requirements:

(a) Data file should be submitted on a CD.

(b) Data file should be .XLS file format (MS-Excel 2007 or earlier) compatible format.

5.4 Volume Organization

The Price volume shall consist of the following sections to include Title Page, Table of Contents, List of Tables and Figures, and Glossary of Abbreviations and Acronyms:

SECTION 1 - Include your rationale in response to the following paragraphs in Section 1, along with a Table of Contents.

5.2.1 - Price Reasonableness

5.2.2 - Balance

5.2.3 - Price Realism

5.3.1 - Annual Price Changes

5.3.2 - Other Documentation

5.3.3 - Probable Subcontractors

5.3.4 - Submission of Price Model

SECTION 2 – Include your response to the following paragraphs in Section 2.

5.3.1 - Annual Price Changes

5.3.2 - Other Documentation

5.3.3 - Probable Subcontractors

5.3.4 - Submission of Price/Cost Models

6.0. Contract Documentation

6.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.

6.1.1. Solicitation/Contract Form

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF1449. Signature by the offeror on the SF1449 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover.

6.1.2. Supplies or Services and Costs/Prices

Completed pricing information in Section B of the model contract.

6.1.3. Contract Clauses

The offeror shall provide required information to complete clauses as required.

6.1.4. Representations, Certifications, and other Statements of Offerors

The offeror has completed the annual representations and certification electronically via the System for Award Management (SAM) website at https://www.sam.gov. After reviewing the SAM database information, the offeror verifies by submission of this offer that the representation and certifications currently posted electronically at FAR 52.212- 3, Offeror Representations and Certifications—Commercial Items are correct.

6.2. Exceptions to Solicitation Requirements

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, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

Table 6.2 - Solicitation Exceptions

Solicitation Development

Page/ Paragraph

Requirement/ Portion

Rationale

SOO, SOW, SPEC,

Model Contract, 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

6.3. Other Information Required

6.3.1. Ombudsman

An Ombudsman has been appointed to hear concerns from Offerors or potential Offerors during the proposal development phase of this acquisition. The Ombudsman for this acquisition is AFSC/PZC, located at Tinker AFB. This does not diminish the authority of the program director or CO, but communicates Offeror concerns, issues, disagreements and recommendations to the appropriate Government personnel. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process; interested parties are invited to call AFSC/PZC at 405-736- 3273.

6.3.2. Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact 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.

6.3.3. Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

6.3.4. Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code; 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.

6.3.5. Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

Form Number Description/File Date Number of Pages ATTACHMENT 1 Statement of Work (SOW) 12/5/2025 12 ATTACHMENT 2 Inventory Listing ATTACHMENT 3 Prototype Photos 11 ATTACHMENT 4 First Article Form 260 05/14/2024 3 ATTACHMENT 5 ATTLA Certification Form EXHIBIT A Contract Data Requirements List 03/31/2024 9 ATTACHMENT 6 Addendum to FAR 52.212-1, Instructions to Offerors 01/21/2025 33

ATTACHMENT 7 Addendum to FAR 52.212-2, Evaluation Factors for Award

01/21/2025 15

ITO ATTACHMENTS

ITO Attachment – 1.1 Proposed Team List

TECHNICAL PACKAGE ATTACHMENT

ITO Attachment – 2.1 CDRL Assertion Matrix

ITO Attachment – 2.2 Tool List Cross-Reference Matrix

ITO Attachment – 2.3 Small Business Participation Commitment Document (SBPCD)

PAST PERFORMANCE PACKAGE ATTACHMENT

ITO Attachment – 3.1 Past Performance Information Form (PPIF)

ITO Attachment – 3.2 Consent Letter

ITO Attachment – 3.3 Client Authorization Letter

ITO Attachment – 3.4 Commitment to Perform as Proposed Letter

ITO Attachment – 3.5 Past Performance Questionnaire

ITO Attachment – 3.6 Performance Questionnaire Letter

PRICE PACKAGE ATTACHMENT

ITO ATTACHMENT – 4.1 Pricing Matrix

ITO ATTACHMENT 1.1

PROPOSED TEAM LIST

TEAMING LIST

Offeror (Prime) Contractor: CAGE Code: DUNS Number:

Designation Codes:

Joint Venture: JV

Informal Joint Venture: IJV

Prime/Sub: PS

Mentor/Protégé: MP

Subs/Teaming Contractor: Designation Code: CAGE Code: DUNS Number:

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

ITO ATTACHMENT 2.1

CDRL ASSERTION MATRIX

ITO ATTACHMENT 2.3

SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT (SBPCD)

1. Prime Contractor Size:

Indicate the applicable size and socioeconomic categories -- all that apply:

{ } Other than Small Business or { } Small Business also categorized as a

{ } Small Disadvantaged Business (SDB) { } Woman-Owned Small Business (WOSB) { } Historically Underutilized Business Zone (HUBZone) Small Business { } Service-Disabled Veteran Owned Small Business (SDVOSB)

2. Minimum Quantitative Requirement (MQR) -- Participation of Small Businesses

Total Contract Value (Awarded) $__________________________________

Minimum Quantitative Requirement (MQR)

Business Category Dollar Value % of Total Evaluated Price (TEP)

Total Contract Value – Prime Contractor $________________ ___________%

Total Small Business $________________ ___________% Small Disadvantaged Business $________________ ___________% Woman-Owned Small Business $________________ ___________% HUBZone Small Business $________________ ___________% Veteran-Owned Small Business $________________ ___________%

Service-Disabled Veteran-Owned Small Business

3. Small Business Participants *

* Changes must be pre-approved by Contracting Officer per: (insert required clause which should be written as a ‘special contract requirement’ if a canned clause does not fit for SBPCDs)

Company Name

Business Category(ies)

(SB, WOSB, SDB,

VOSB, SDVOSB)

Product(s)/Service(s) to be Provided

NAICS

Code

Nature of Commitment

ITO ATTACHMENT 3.1

PAST PERFORMANCE INFORMATION FORM

Provide the information requested in this form for each contract/program being described. Provide frank, concise comments regarding your performance on the contracts you identify. Request each offeror submit up to three (3) PPIFs for the prime contractor, and up to three (3) PPIFs for each significant subcontractor/teaming partner.

A. Offeror Name (Company/Division):

CAGE Code:

DUNS Number:

(NOTE: If the company or division performing this effort is different than the offeror or the relevance of this effort to the instant acquisition is impacted by any company/corporate organizational change, note those changes. Refer to the "Organizational Structure Change History" you provided as part of your Past Performance Volume).

B. Program Title:

C. Contract Specifics:

1. Contracting Agency or Customer:

2. Contract Number:

3. Contract Type:

(If multiple types (i.e. Firm-Fixed Price with Time & Material), list percentage and dollar amount of Firm- Fixed Price portion)

4. Period of Performance:

5. Original Contract $ Value: (Do not include unexercised options)

6. Current Contract $ Value: (Do not include unexercised options)

7. If Amounts for 5 and 6 above are different, provide a brief description of the reason:

D. Brief Description of Effort as Prime or Subcontractor (Please indicate whether it was development and/or production, or other acquisition phase and highlight portions considered most relevant to current acquisition)

E. Completion Date:

1. Original date:

2. Current Schedule:

3. Estimate at Completion:

4. How Many Times Changed:

5. Primary Causes of Change:

F. Are there Contractor Performance Assessment Reports (CPARS) or other Past Performance Reports available for this contract? YES NO

G. Primary Customer Points of Contact: (For Government contracts, provide current information on all three individuals. For commercial contracts, provide points of contact fulfilling these same roles).

1. Program Manager and/or Name:

Site Manager Office:

Address:

Telephone:

Fax Number:

Email:

2. Contracting Officer Name:

Office:

Address:

Telephone:

Fax Number:

Email:

3. Administrative Name:

Contracting Officer Office:

Address:

Telephone:

Fax Number:

Email:

H. Address any technical (or other) area about this contract/program considered unique.

I. For each of the applicable subfactors under the technical factor in the “Evaluation Criteria for Award, illustrate how your experience on this program applies to that subfactor, if you are to perform the same effort on the proposed contract.

J. Specify, by name, any key…