Attachment 04 Section L ITO Risk Price 15Nov22.pdf

SECTION L – INSTRUCTIONS TO OFFORS (ITO)

1 (of 17)

SECTION L

INSTRUCTIONS TO OFFERORS

15 Nov 22

1 PROGRAM STRUCTURE AND OBJECTIVE

1.1 General Information

1.1.1 The Government plans to award a single contract for the Man-Portable (MP) Tactical Air Navigation (TACAN) Replacement program with a contract value ceiling of $198,360,000.00.

The MP TACAN will be a replacement for the AN/TRN-41. The AN/TRN-41 is a ground-based system that provides a TACAN signal which can be used by any aircraft with a TACAN receiver to help navigate. The AN/TRN-41 is small and easily transportable versus the various fixed-base systems found at many airports around the world. The existing AN/TRN-41 was fielded back in the 1970s so it is maintenance-intensive with insufficient quantities available to meet mission needs.

1.1.2 Contract 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 (IAW)Section M, Evaluation Factors for Award.

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 5 MP TACAN Systems (CLINs 0001, 0002, 0003, 0004).

1.3 Contractor Technical Proposal

All or part of the Contractor’s Technical Proposal may be incorporated to the contract. Should there be any discrepancies between any of the documents FAR 52.215-8 establishes an order of precedence with H06 included in the Request for Proposal clarifying FAR 52.215-8(d).

2 GENERAL INSTRUCTIONS

2.1 General Guidance

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 IAW 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, its 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

2 (of 17) 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 the model contract/solicitation. The Offeror shall make a clear statement in specified model contract of the proposal documentation volume that the proposal is valid until this date.

2.1.5 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.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 e-mail 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, where upon they may request and receive a debriefing IAW 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 IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW 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) web site at http://www.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 will render the proposal ineligible for award, however clarifications maybe offered to correct a Government perceived administrative error.

2.2.6 Submission, Modification, Revision, and Withdrawal of Proposals

Proposals and modifications to the proposals shall be submitted via DoD SAFE as described in http://www.sam.gov/ http://www.sam.gov/

3 (of 17) paragraph 2.4 and 2.5

2.3 Organization/Number of Copies/Page Limits

2.3.1 The Title Page of each volume must show solicitation number, name, address, telephone numbers 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 following the Title Page using the Offeror’s own format. Information provided should include the name, title, phone number, and e-mail address of the Offeror’s primary Point of Contacts.

2.3.3 The Offeror shall prepare the proposal as set forth in the Proposal Organization table (Table

2.3 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 as stated in Table 2.3 unless an exception is noted in this document. The contents of each proposal volume are described in the ITO paragraph as noted in the table below. The electronic files identified in the table shall use the following naming convention: Volume I – Technical.doc or .docx, Volume II – Price.doc or .docx (.pdf is acceptable for Volumes I, II and III if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text), with PricingMatrix.xls or .xlsx, and Volume III – Contract.doc or .docx. The Pricing Matrix shall be submitted in MS Excel form.

Do not change this Excel portion to PDF.

Table 2.3: Proposal Organization

Volume

ITO

Paragraph Number

Volume Title

Page Limit

I

Factor 1 - Technical

2.3.1

Title Page (Not included in 65 page limit)

2.3.2

Team List (Not included in 65 page limit)

2.3.7

Indexing

Unlimited

2.3.8

Tables and Figures List

2.3.9

Glossary of Abbreviations and Acronyms

3.2.3 3.2.4 3.2.5 3.2.6

Subfactor 1 SRD Cross-Reference Subfactor 2 SRD Requirements Subfactor 3 SRD Non-Compliance (Performance Gap)

Included as part of the 65 page limit

4 (of 17)

3.2.7 3.2.8

Subfactor 4 Small Business Participation Subfactor 5 Delivery Requirements Subfactor 6 CDRL Data Rights

3.3 Factor 2 – Technical Risk

Included as part of the 65 page limit

II

Price Volume

Title Page

Team List

4.4

Volume Organization

4.2

General Information

III 5 Contract Documentation Unlimited

Title Page (SF33)

Team List

2.3.7

Table of Contents

2.3.9

Glossary of Abbreviations and Acronyms

3.2.6

Arrangements, and/or Letters of Intent Unlimited

5.1

Model Contract (Sections A-J) to include amendments

N/A

5.1

Representations and Certifications (Section K)

N/A

5.3.2

Contact Information

5.3.5

Attachments to the Model Contract

2.3.4 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

5 (of 17) letters forwarding the ENs to the Offerors. Each page shall be counted except the following: blank pages, title pages, team lists, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited.

2.3.5 Pricing Information

All pricing information shall be addressed ONLY in the Price Proposal and Contract Documentation volumes (Volumes II and III). Price 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.6 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 in 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 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.7 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.8 Tables and Figures List

Include an indexed list of Tables and Figures.

2.3.9 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 Pages

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. 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) also. These limitations shall apply to electronic proposals.

2.4.2 Tables Charts, Graphs, and Figures

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, 6 (of 17) 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. These limitations shall apply to all electronic volumes.

2.5 Electronic Offers

The submittals shall be electronic only. Each volume of the proposal shall be provided in a separate electronic file and named IAW the naming convention identified in para 2.3. All unclassified document files shall have a color other than red or other applicable security designation colors on the title page. Be sure to 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.

All proposals shall be submitted using DoD Secure Access File Exchange (SAFE), https://safe.apps.mil/. All interested Offerors must e-mail Amanda Jones (Amanda.Jones.39@us.af.mil) and Ashley Brink (Ashley.Brink@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 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 (1500 CST), 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 request. 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.

If the Offeror checks this box to encrypt all files, the Offeror is required to email the Pass Phrase established in DoD Safe to both GPOCs before the closing of the RFP. 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. FAR 52.215-1(c)(3)(ii)(1) will govern proposal timeliness with adequate documentation to support a claim, if needed. If the Offeror believes there may be a concern regarding proposal receipt, email the GPOC for confirmation. The PCO will request further documentation to support a timely proposal claim from the Offeror if deemed necessary.

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. 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 (version 2016 or later), and Adobe Acrobat Pro DC or newer. Note PDF files must be searchable and able to copy and paste. For amendment purposes to the proposal, the "original" proposal shall be clearly identified.

https://safe.apps.mil/ https://safe.apps.mil/

7 (of 17)

2.6 Distribution

The Offeror shall submit volumes I through III in electronic format via DoD Safe as described in

2.5. Each volume shall be submitted in separate files. If submission files are compressed, they must be able to be decompressed using inherent Microsoft (MS) Windows tools (e.g., ZIP), otherwise the necessary decompression utility program must also be provided. The electronic files shall be submitted in a format readable by MS Word, MS Excel, MS Power Point, or searchable PDF. All MS product submissions shall be readable by MS Office 2016 or newer versions, and all PDFs shall be readable by Adobe Acrobat Pro DC or newer.

It is the responsibility of the Offeror to save any necessary screen shots to prove timeliness of a complete proposal. This may include screen shots of complete uploads for each of the required document. The PCO will request proof of proposal delivery timeliness, if it is determined necessary by the Government. This documentation shall be provided within 72 hours of the request, or it will not be considered by the PCO when making a proposal timeliness determination.

3 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 Section M, 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. 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 unless otherwise noted as an exception IAW Section M 1.6 or marked as a non-compliance on the SRD Cross-Reference in Factor 1- Technical, subfactor 1, and your proposal clearly states your proposed system will not meet the requirement in Factor 1 Technical, Subfactor 3- SRD Non-Compliance. It is neither necessary nor desirable for you to tell us you meet all other requirements 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 general outline included in Table 2.3.

3.2.3 Subfactor One: SRD Cross-Reference

The Offeror shall provide a completed SRD Cross-Reference Matrix (Appendix 1) indicating compliance/non-compliance with the SRD minimum threshold requirements outlined in Section 2 of the SRD for the MP TACAN replacement. An indication of compliance indicates the proposed product specifications for the MP TACAN replacement currently (as of the date of the proposal) meets the threshold requirement as is, without additional testing or modification. Non-compliance

8 (of 17) indicates the current proposed product specifications for the MP TACAN replacement requires additional testing or modification to meet the minimum threshold (identifying a current Performance Gap). All requirements identified as non-compliant must be identified in red text in Appendix 1 and shall be addressed in Subfactor Three below unless it is addressed in Subfactor Two SRD elements QLT-2, PER-1, PER-2, QLT-5, RMM-2, and QLT-17. The Offeror shall not add rows or columns to the matrix.

3.2.4 Subfactor Two: SRD Requirements

The Offeror shall provide documentation describing how the proposed MP TACAN replacement meets, or will meet by delivery of the first system, the following critical elements (3.2.4a through 3.2.4f). The Offeror shall provide documentation of the Offeror’s current state of specification as of the date of the proposal. If the proposed system is not currently compliant, the Offeror shall provide an approach to obtain full compliance upon delivery. The Offeror shall provide (1) the current specifications and future expected specifications as compared to the SRD threshold requirement by the time of delivery for the first unit; (2) actions and mitigations needed to meet the SRD minimum requirement, which must include items such as, but not limited to, modifications, software changes, and additional testing; (3) milestone dates to bring the current proposed system up to the minimum SRD requirements ensure the MP TACAN delivery requirements are met IAW SOW Paragraph 6.4 for each of the below SRD elements that are non-complaint as of the date of the proposal.

a. Flight Check (SRD QLT-2, KPP). The Offeror shall provide an adequate approach describing actions to ensure a successful FAA/ICAO flight check upon first delivery. The approach shall include sufficient details depicting additional steps deployed to ensure successful flight check. An approach merely stating reliance on the Government’s Flight Check is not considered sufficient. An approach may include documentation of a successful FAA/ICAO flight check on a system in its proposed configuration or near-similar setup that is electronically the same (i.e., repackaged transmitter and/or antenna), listing the part numbers of the transmitter and antenna that is being claimed as near-similar.

b. Portability (SRD PER-1, KPP). Offeror shall describe their product’s physical dimensions, weight, and manpower requirements in different phases: man-carry, storage, and transport both in and outside of the transport cases with no more than 2-person lifts allowed (as proposed either with or without transport aide).

c. Set Up (SRD PER-2). Offeror shall provide documentation and describe their approach to ensuring the setup time in no more than 75 minutes can be accomplished for the proposed MP TACAN replacement system.

d. Transmitter Power Out (SRD QLT-5). Offeror shall provide test documentation and describe their approach ensuring the system is capable of transmitting sufficient watts RF peak power to reach a distance of no less than 75 nm at 0.5 degrees while adhering to MIL-STD-291C and ICAO Annex 10 criteria and describing adjustable lower power settings to include as a minimum a 50% power setting.

e. Remote Monitoring & Maintenance (RMM) (SRD RMM-2). Offeror shall provide a listing of what TACAN parameters can be remotely (wirelessly) monitored from the remote status unit, as well as both theoretical and tested distance limits between the TACAN and the remote status unit. The Offeror’s documentation shall provide proof of a remote reset (RMM-2b) capability.

f. Mean-Time-Between Failure (MTBF) (SRD QLT-17). Offeror shall provide

9 (of 17) documentation of the overall MTBF analysis of the MP TACAN down to the Line Replaceable Unit (LRU) level for detail of the overall or major subsystem analysis. The Offerors documentation shall show no less than 10,000 hours MTBF of the overall system and all major subsystems.

3.2.5 Subfactor Three: SRD Non-Compliance (Performance Gap)

For all Subfactor One SRD minimum threshold requirements (Appendix 1) indicated as noncompliant, the Offeror shall provide an approach to ensure the proposed MP TACAN replacement system will meet the minimum threshold requirements at time of delivery. If the threshold requirement cannot be met (or exceeded), then the Offeror shall provide an approach to attain the best possible value as close to the requirement as possible, providing reasonable rationale as to why this is the best possible value attainable. The approach must include the following for each non-compliant SRD requirement:

a. Current proposed product’s specification and future proposed expected value to meet the SRD threshold requirement by time of delivery for the first unit.

b. Actions and mitigations needed to meet or meet to the fullest extent possible the SRD minimum requirement, which must include items such as, but not limited to, modifications, software changes, and additional testing.

c. Milestones dates to bring the current proposed MP TACAN replacement up to the minimum SRD requirements or to the fullest extent possible ensuring the MP TACAN delivery requirements are met IAW SOW paragraph 6.4.

d. If no gaps are identified in Subfactor One, then the Offeror must include a statement in their Technical Volume indicating this section is not required.

3.2.6 Subfactor Four: Small Business Participation

The Offeror shall provide their Small Business Subcontracting Plan IAW Federal Acquisition Regulation (FAR) 52.219-9 and Defense Federal Acquisition Regulation Supplement (DFARS) 252.219-7003 or 252.219-7004. The proposed approach for subcontracting shall clearly describe subcontracting arrangements, relationships, roles, work to be performed by subcontractors, and how data rights will be passed to the Government.

3.2.7 Subfactor Five: Delivery Requirements

Fielding of the MP TACAN replacement system is critical. Provide a single milestone schedule along with your approach to ensure delivery IAW SOW paragraph 6.4.2 for the first five (5) units. In your approach, provide any mitigations that are/will be enacted to minimize potential supply chain issues in meeting the delivery schedule. Ensure your approach also describes how subsequent orders will be delivered IAW SOW paragraph 6.4.3.

3.2.8 Subfactor Six: CDRL Data Rights

The Offeror shall provide a completed CDRL Assertion Matrix (Appendix 2) indicating data rights asserted/proposed, given consideration to the data rights requested by the Government. Anything less than what the Government requested on Appendix 2 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 Appendix.

10 (of 17)

3.3 Factor 2 - Technical Risk

The Offeror shall address technical risk associated with the approach provided in the following:

Subfactor Two, SRD Requirements Subfactor Three, SRD Non-Compliance (Performance Gap) Subfactor Five, Delivery Requirements Subfactor Six, CDRL Data Rights

The Offeror shall address all technical risks that the Offeror considers having potential to disrupt schedule, increased cost, degradation of product performance, increase need for Government oversight, or the increased likelihood of unsuccessful contract performance. For each identified risk, the Offeror shall provide the rationale for the risk and quantitative estimates for both potential consequence (to cost, schedule, and/or performance) and the probability of the risk to occur. The Offeror shall also outline a mitigation approach describing how each risk is eliminated or reduced to a Low or Moderate overall (combined potential and consequence) level.

4 FACTOR 3 – PRICE

4.1 Price Volume

In the price volume, the Offeror shall provide the following information in addition to the Pricing Matrix (Appendix 3). These instructions are to assist you in submitting information required to evaluate the reasonableness, balance, and realism of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

4.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. Offerors shall not input pricing information in Section B – Supplies or Services and Prices/Costs of the model contract. Proposed unit prices will only be entered in the Price Matrix (Appendix 3).

4.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/rates for all listed items in the Pricing Matrix (Appendix 3). If an Offeror’s proposed unit price/rate is zero, then the Offeror shall provide rationale to support the zero dollar/rater entry.

4.2.2 Balance

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

11 (of 17) pricing is determined with respect to year-to-year price variances as applicable for separately priced CLINs and will be considered between the unit quantities variations. 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. Unexplained price variances from year to year could suggest unbalanced pricing. It is in the Offerors best interest to provide explanations or supporting rationale for any significant annual CLIN price variances or any significant quantity unit price variations.

To assist in the determination of balanced pricing, Offerors shall complete the attached Pricing Matrix (Appendix 3).

4.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.). All proposed prices shall be sufficient and adequately proposed to ensure performance is not at an unacceptable risk with prices proposed too low.

4.2.4 Total Evaluated Price (TEP)

Offerors shall complete the Pricing Matrix (RFP, Appendix 3). Offerors must ensure all required proposed pricing is provided in the Pricing Matrix, ensuring all periods of performance are priced. These include a five-year Basic, one two-year Option Period, and a six-month Option Period to extend services applicable to only Interim Contractor Support (ICS). Offerors shall propose pricing for the six-month extension based on proposed pricing of year seven of Option I.

The input spreadsheet in the Pricing Matrix automatically applies the year 7 Option I unit prices to the six-month extension unit prices.

The Quantities provided in the Pricing Matrix (Appendix 3) will be used for evaluation purposes only and do not obligate the Government to exercise options or guarantee such quantities during the contract period of performance.

4.2.5 Pricing Information Requirements

Price analysis techniques shall be utilized to ensure fair and reasonable pricing IAW FAR 15.4041(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process.

FAR part 15 applies. IAW FAR 15.403-1(b)(1), prices based on adequate price competition do not require submission of cost or pricing data. IAW FAR 15.4033(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 certified cost or pricing data.

4.2.6 Rounding

12 (of 17)

In the Pricing Matrix (Appendix 3), all proposed dollar amounts and labor rates shall be rounded to the nearest cent. Proposed percentages (Travel General & Administrative (G&A), and Material Handling) are rounded to four places to the right of the decimal.

4.3 Pricing Support Information

4.3.1 Estimating Techniques and Past Experience

Provide a brief explanation of the methodology used to estimate prices in the development of the Offeror’s proposed pricing. Where price estimates are based on past experience, identify the past experience; explain how the past experience relates to the current effort including similarities and differences and how price data available from the past experiences was adapted to the current effort pricing.

4.3.2 Proposed Price Reduction per Corporate/Management Decision

If proposed prices to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major pricing element (e.g., material, labor, overhead, etc.). Also, provide complete rationale for the reduction. Provide the estimated dollar and percentage of the reduction, explaining how such reductions are ensured not to increase performance risk to the Government. If the Offeror has not proposed any price reductions, then state accordingly in Section 2 of the Price Volume.

4.3.3 Price Assumptions Used in Development of Proposed Pricing

All significant assumptions, scope limitations, and/or qualifications affecting the pricing proposal shall be addressed and explained. If there are no proposed price assumptions, then state accordingly in Section 2 of the Price Volume.

4.3.4 Labor, Travel G&A, and Material Handling

Proposed rates will be used for all To Be Negotiated (TBN) tasks. These rates shall be proposed as fixed price, fully burdened rates valid for all rates referenced in the Pricing Matrix (Appendix 3). The labor wrap rates shall be proposed at sufficient dollar amounts to adequately cover any and all fluctuations and actual costs in contract performance out-years. All rates should be proposed with sufficiently high ceiling rates to ensure adequate coverage of all labor costs, all indirect costs, including G&A, Facilities Capital Cost of Money (FCCM), and so forth as well as prime and subcontractor profit in every contract out-year. The material handling rate shall represent all indirect costs plus profit associated with obtaining direct material and/or subcontract costs.

The Offeror is required to provide a statement indicating their understanding that proposed ceiling rates will apply to all out-years despite what current actuals are running at the time.

4.3.5 Service Contract Labor Standards (SCLS)

It is the responsibility of the Offeror and the subsequent contract awarded to comply with the Services Contract Labor Standards (SCLS). In this section of the Price Volume, a table shall be provided conforming (linking) the Offeror’s proposed job categories/skill levels considered subject to the SCLS with the job categories/skill levels of the Wage Determination (WD). This cross-reference provides a tie between the labor categories/skill levels proposed and the labor categories/skill levels listed in the SCLS WD.

4.3.6 Probable Subcontractors

13 (of 17)

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. Provide the methodology used to determine subcontractor pricing fair and reasonable.

4.3.7 Government Field Support Agencies

Identify the cognizant Defense Contract Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) office responsible for administration of the Offeror’s Government contracts.

4.3.8 Other Documentation

Other documentation considered by the Offeror to be essential for support of proposed prices shall be presented in this section. Offerors may provide any additional data, other than certified cost or pricing data, as believed necessary to support, justify, or clarify their proposed pricing.

4.3.9 Submission of Pricing Matrix

Submit the completed Pricing Matrix (Appendix 3) in support of the proposed Total Evaluated Price (TEP). The proposed pricing in the Pricing Matrix (Appendix 3) submitted shall be consistent with the Offeror’s approved estimating system. The Pricing Matrix (Appendix 3) submitted shall comply with the following format requirements:

a. Data file shall be .XLSX file format (MS-Excel 2016 or above) or compatible format without passwords or hidden information.

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

4.2.1 – Price Reasonableness

4.2.2 – Balance

4.2.3 – Price Realism

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

4.3 – Pricing Support Information

4.3.1 – Estimating Techniques and Past Experience

4.3.2 – Proposed Price Reduction per Corporate/Management Decision

4.3.3 – Price Assumptions Used in Development of Proposed Pricing

4.3.4 – Labor, Travel G&A, and Material Handling

4.3.5 – Service Contract Labor Standards (SCLS)

4.3.6 – Probable Subcontractors

4.3.7 – Government Field Support Agencies

4.3.8 – Other Documentation

SECTION 3 ‑ Include your response to the following paragraphs in Section 3.

4.3.9 – Submission of Pricing Matrix

5 CONTRACT DOCUMENTATION

5.1 Model Contract/Representations and Certifications

14 (of 17)

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 to include all amendments.

5.1.1 Solicitation/Contract Form

Completion of blocks 13, 15, 16 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" copy should be clearly marked under separate cover. Section B of the contract shall clearly indicate all of the parts included in each kit for CLIN x001 Antenna Kit, CLIN x002 Beacon Transponder Kit, CLIN x003 RCSU Kit, and CLIN x004 MP TACAN Assembly Kit. These four CLINs ordered together shall be the proposed complete MP TACAN replacement system with no additional parts necessary to operate the system as required in the SRD and SOW.

5.1.2 Supplies or Services and Prices

Do not complete pricing information in the model contract. All pricing is required to be in the Pricing Matrix (Appendix 3).

5.1.3 Contract Clauses

The Offeror shall provide required information to complete all provisions and clauses as required.

5.1.4 Progress Payments and Performance Based Payments

Proposal pricing and contract award will be based on customary progress payment financing if requested, but the Government may be willing to incorporate Performance Based Payments (PBP) by modification to the contract with the successful offeror if PBPs are determined to be practical and in the best interest of the Government by the contracting officer, the contractor agrees to their use, and adequate consideration is received by the Government (FAR 32.005(b) and DFARS 232.1004(iii)). Contractors shall provide written notification within their proposal identifying their request to incorporate Progress Payments at time of award or PBPs after award of the basic ID/IQ contract and minimum Delivery Order. If offerors intends to not request Progress Payments or PBPs, no notification is required.

5.1.5 Section K Representations, Certifications, and other Statements of Offerors or Respondents

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.204-7, System for Award Management is correct.

5.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 5.2. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible https://www.sam.gov/ https://www.sam.gov/

15 (of 17) for award.

Table 5.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale

SOW, SRD, 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

5.3 Other Information Required

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

5.3.2 Contact Information

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.

5.3.3 Government Offices

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

5.3.4 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; Unique Entity ID (SAM Generated); 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.3.5 Attachments to the Model Contract

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

16 (of 17)

LIST OF DOCUMENTS, EXHIBITS, OR ATTACHMENTS

Form Number Description/File Date Number of Pages

Attachment 1 MP TACAN SOW (Version B) 11 Nov 22 47

Attachment 2 System Requirements Document Version 1 (includes attached SRD Appendix A)

13 Oct 22 22

Attachment 3 Delivery Locations Basic List 31 Oct 22 05

Attachment 4

Section L- Instruction to Offerors

15 Nov 22 17

Attachment 5

Section M- Eval Factors for Award

07 Nov 22 09

Attachment 6 AF Form 158 09 Sep 21 02 Attachment 7 AF Form 158 Vendor Packing Ins. 09 Sep 21 01 Attachment 8 AFMC Form 807 19 Apr 22 02

Attachment 9 Wage Determination - 5489

27 Jun 22

Attachment 10 Wage Determination – 5105

10 Jan 18 10

Attachment 11 Wage Determination - 5487 06 Aug 18 10

Attachment 12 Warranty Tracking Information 3 Mar 22 2

Attachment 13 Warranty Tracking Information v. 2.6 26 Apr 22 Excel Spreadsheet

Attachment 14

DO 1 Locations Min. Order (This will be attached to the first DO upon award and not the ID/IQ Contract;

Deliver locations subject to change prior to final contract award without notice)

31 Oct 22 1

Attachment 15 AFMC Form 718 03 Nov 22 2

Appendix 1 SRD Cross Reference Matrix 13 Oct 22 Excel Spreadsheet

Appendix 2 CDRL Assertion Matrix 27 Oct 22 Excel Spreadsheet

Appendix 3 Pricing Matrix 14 Nov 22 Excel Spreadsheet

Exhibit A Technical Data Package A026 27 Oct 22 51

17 (of 17)

Exhibit B Tech Order A028 27 Oct 22 24

Exhibit C Tech Order A047 27 Oct 22 23

Exhibit D Other CDRLs DD Form 1423 A0XX 27 Oct 22 60

Exhibit E

Technical Data Package B026

27 Oct 22

Exhibit F

Tech Order B028

27 Oct 22

Exhibit G

Tech Order B047 27 Oct 22 23

Exhibit H

Other CDRLs DD Form 1423 B0XX 27 Oct 22 60

5.3.5.1 Attachment 15 AFMC Form 718

IAW RFP Attachment 1 MP TACAN SOW section 9.1.6 the Offeror shall complete Attachment 15 AFMC Form 718 with the proposal and submit it with the contract documents stated above. This form shall be completed based on anticipated contract award date of 29 Sep 23. The offerors form shall be consistent with the delivery approach described in technical volume Technical Factor 1, Subfactor Five, Delivery Requirements.