Attachment 3 Section L-Instructions to Offerors Rev02.pdf

CUI

Section L

Instructions to Offerors (ITO) and Instructions for Proposal Preparation for AN/TMQ-53 Tactical Meteorological Observing System

(TMOS)

Contractor Logistics Support (CLS)

Solicitation Number: FA2330-26-R-B006

20 May 2026

Prepared by: AFLCMC/ESAW, 75 Vandenberg Drive, Building 1630 Hanscom

AFB MA 01731

L-1

Distribution Statement C: Distribution authorized to U.S. Government Agencies and their Contractors (Administrative or Operational Use) (Mar 2026). Other requests shall be referred to AFLCMC/ESAW, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA 01731-2103.

HANDLING AND DESTRUCTION NOTICE. For classified documents, DoD civilians or military personnel will follow procedures outlined in DoDM 5200.01, Volume 3, and Enclosure 3: DoD Contractors will follow procedures outlined in DoDM 5220.22, Sections 11-19. For sensitive unclassified documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

L-2

Section L Instructions to Offerors for Proposal Preparation for AN/TMQ-53 Tactical Meteorological Observing System (TMOS) CLS

Revision History

Revision Number

(Rev01, Rev02, etc.) Date Description Sections Affected/Author

Original 11 May 2026

Rev01 20 May 2026 Revised based on Legal comments for Business Clearance

L2.1: Proposal Compliance L2.6.2: Debriefings

Rev02 01 July 2026 Revised based on Amendment to the RFP posted on 8 July 2026

L2.7 Organization/ Number of Copies/Page Limits L6.4 Non-Disclosure Agreements and Conflicts of Interest

L-3

Table of Contents

L1.0 PROGRAM STRUCTURE AND OBJECTIVES

L2.0 GENERAL INSTRUCTIONS

L2.1 PROPOSAL COMPLIANCE

L2.2 INCLUDE SUFFICIENT DETAIL

L2.3 EMBELLISHMENTS NOT DESIRED

L2.4 PROPOSAL ACCEPTANCE AND VALIDITY DATES

L2.5 DISPOSITION OF PROPOSALS

L2.6 GENERAL INFORMATION

L2.6.1 Point of Contact L2.6.2 Debriefings L2.6.3 Discrepancies L2.6.4 Electronic Reference Documents L2.6.5 Oral Presentation L2.6.6 Organizational Conflict of Interest (OCI)

L2.7 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS

L2.7.1 Page Limitations L2.7.2 Pricing Related Data L2.7.3 Classified Information L2.7.4 Cross-Referencing L2.7.5 Indexing L2.7.6 Glossary of Abbreviations and Acronyms L2.7.7 Binding and Labeling

L2.8 ELECTRONIC OFFERS

L2.9 DISTRIBUTION

L2.10 PROPOSAL SUBMISSIONS

L2.11 PROPOSAL QUALITY

L3.0 VOLUME I – EXECUTIVE SUMMARY

L3.1 NARRATIVE SUMMARY

L3.2 TABLE OF CONTENTS

L4.0 VOLUME II – TECHNICAL PROPOSAL

L4.1 GENERAL

L4.2 FORMAT AND SPECIFIC CONTENT

L4.2.1 Technical L4.2.2 Volume Organization

L4.3 TECHNICAL CAPABILITY FACTOR

L4.3.1 Transition Plan L4.3.2 Program Management Plan (PMP) L4.3.3 Lightning Detector Replacement Plan L4.3.4 Systems Engineering L4.3.5 Staffing Plan

L5.0 VOLUME III – PRICE

L5.1 GENERAL INSTRUCTIONS

L5.1.1 Ground Rules/Assumptions L5.1.2 Price Data L5.1.3 Pricing Data Requirements

L-4

L5.1.4 Rounding L5.1.5 Total Evaluated Price (TEP) L5.1.6 Professional Employee Compensation Plan

L6.0 VOLUME IV – CONTRACT DOCUMENTATION

L6.1 MODEL CONTRACT/REPRESENTATIONS AND CERTIFICATIONS

L6.1.1 Section A – Solicitation/Contract Form L6.1.2 Section B – Supplies or Services and Prices L6.1.3 Section C – Descriptions/Specifications/Statement of Work L6.1.4 Section F – Deliveries or Performance L6.1.5 Section G – Contract Administrative Data L6.1.6 Section H – Special Contract Requirements L6.1.7 Section I – Contract Clauses L6.1.8 Section K – Representations, Certifications, and other Statements of Offerors .. 15

L6.2 EXCEPTIONS TO SOLICITATION REQUIREMENTS

L6.3 OTHER INFORMATION REQUIRED

L6.3.1 Authorized Offeror Personnel L6.3.2 Government Offices L6.3.3 Company/Division Address, Identifying Codes, and Applicable Designations L6.3.4 Associate Contractor Agreements (ACA)

L6.4 NON-DISCLOSURE AGREEMENTS

L7.0 REQUIRED ATTACHMENTS

L-5

L1.0 Program Structure and Objectives AN/TMQ-53 Tactical Meteorological Observing System (TMOS) effort is intended to provide a single prime contractor to sustain all currently fielded TMQ-53 systems in their approved configurations worldwide, in accordance with (IAW) the requirements, as stated in the Performance Work Statement (PWS) and the TMQ-53 Technical Requirements Document

(TRD).

This includes, Program Management; Logistics Support (Helpdesk Support, Maintenance, Spares and Repair Management); Operational, Safety, Suitability, and Effectiveness (OSS&E) impact analysis; Test and Evaluation support; Configuration Control Board (CCB) support;

Government Furnished Property (GFP), and Obsolescence and Systems Engineering. Further, all system performance data, such as System Availability rates, Mission Capable rates, and Mean Time between Failure (MTBF) rates, shall be collected and reported. Additionally, program data shall be collected and reported, such as Government-Furnished Materiel-A (GFM-A) Management, materials, shipping, travel, etc., Engineering Change Proposals (ECP), Cybersecurity, Technical Manual development and maintenance, and Contract Data Requirements List (CDRL) deliverables. The Contractor shall also support and/or perform system design changes, upgrades, and enhancements due to technical refresh of component capability, obsolescence, and diminishing sources. Any travel directed by the Government, not specified under the CLS Contract Line Item Number (CLIN), will be completed under the Travel CLIN. The Contractor shall provide worldwide support, however there is no requirement for the Contractor to travel to an overseas location in the performance of this contract.

L2.0 General Instructions

L2.1 Proposal Compliance The offeror’s proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP), including all applicable attached documents. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation or an unacceptable proposal that is ineligible for award.

L2.2 Include Sufficient Detail The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The technical proposal must convey to the Government that the offeror possesses adequate technical expertise and experience, sufficient resources, and is able to plan, organize, and use those resources in a coordinated and timely fashion to meet the needs of the Government. The offeror’s proposal shall not simply copy and paste, rephrase or restate the PWS or Technical Order language for the technical volume 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 or experience and will base its evaluation on the information presented in the offeror’s proposal.

L2.3 Embellishments Not Desired Elaborate brochures or documentation, binding, detailed art work, or other embellishments are

L-6 unnecessary and are not desired.

L2.4 Proposal Acceptance and Validity Dates 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 through 180 days from RFP closing date.

L2.5 Disposition of Proposals In accordance with RFO 4.7 (Contract Records Retention) and RFO 4.309 (Storage, handling, and 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.

L2.6 General Information L2.6.1 Point Of Contact The identified Contracting points of contact are the only points of contact for this acquisition.

Address any questions or concerns you may have to the CO and Contract Specialists. Requests for clarification may be emailed to the CO and Contract Specialists at:

AFLCMC/ESAK

ATTN: Capt Ryan Weitgenant: Contracting Officer ryan.weitgenant.1@us.af.mil +1 786-994-5854

AFLCMC/ESAK

ATTN: Stephanie Prentice: Contract Specialist stephanie.prentice@us.af.mil

L2.6.2 Debriefings

Offerors desiring a debriefing must make their request in accordance with the requirements of RFO 15.206-2 or 15.301, as applicable. The CO will promptly notify offerors of any decision to remove them from the competition; whereupon, they may request and receive a debriefing in accordance with RFO 15.206-2. Offerors removed from the competition 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 removed from the competition are entitled to only one debriefing for each proposal. For unsuccessful offerors that were non removed from the competition prior to contract award, the CO will notify the offerors of the source selection decision in accordance with RFO 15.301. Upon such notification, unsuccessful offerors may request and receive a debriefing.

L2.6.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 or Contract Specialist by email 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 mailto:ryan.weitgenant.1@us.af.mil mailto:stephanie.prentice@us.af.mil

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

L2.6.4 Electronic Reference Documents All referenced documents for this solicitation will be available through the CO or Contract Specialist. Notices will be posted on the Government Point of Entry (GPE) at https://sam.gov.

L2.6.5 Oral Presentation No oral presentations are planned.

L2.6.6 Organizational Conflict of Interest (OCI) RFO Part 9.5 requires that action to avoid, neutralize, or mitigate potential OCI be accomplished. Offerors will notify the PCO in writing within five (5) days of receipt of the RFP regarding any actual/potential OCI and provide applicable mitigation plans.

L2.7 Organization/Number of Copies/Page Limits The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table

2.1 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 specified in Table 2.1. For the electronic copy requested below, it shall be submitted via email or DoD SAFE request:

ATTN: Capt Ryan Weitgenant: Contracting Officer ryan.weitgenant.1@us.af.mil +1 786-994-5854

ATTN: Stephanie Prentice: Contract Specialist stephanie.prentice@us.af.mil

The electronic copies shall be clearly identified. The contents of each proposal volume are described in this section and summarized in the table below. Offerors shall include a Table of Contents in the proposal.

Table 2.1 – Proposal Organization

Volume ITO Paragraph Number

Volume Title Page Limit

I 3.0 Executive Summary 5 II 4.0 Technical Proposal 25 50 III 5.0 Price Proposal (Excel Format) Unlimited IV 6.0 Contract Documentation Unlimited https://sam.gov./ mailto:ryan.weitgenant.1@us.af.mil mailto:stephanie.prentice@us.af.mil

L-8

L2.7.1 Page Limitations Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). 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:

cover/title pages, tables of contents, tabbed dividers, acronym lists, RFP Cross Reference Matrix (RCRM), and glossaries.

L2.7.1.1. Page Size and Format A page is defined as each face of a sheet of paper containing information. Proposals shall be prepared using a minimum Times New Roman 12 point font on 8.5” x 11”. Pages shall be typed using 1.5 line spacing. Use at least 1 inch margins on the top and bottom and ¾-inch side margins.

Offerors shall ensure that each page provides identification of the submitting offeror and solicitation number in the header or footer. Pages shall be numbered sequentially by volume. The page size and format restrictions shall apply to responses to ENs.

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 legible. For tables, charts, graphs and figures, the text font size shall be no smaller than Times New Roman 8-point font.

L2.7.2 Pricing Related Data All pricing information shall be addressed ONLY in Volume III (Price). Do not include any price data in any other volume. All amounts provided in response to these instructions shall be rounded to the nearest whole U.S. dollar.

L2.7.3 Classified Information Classified information SHALL NOT be provided in the offeror’s response to this RFP.

L2.7.4 Cross-Referencing To the greatest extent possible, each volume should be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal, except for cross-referencing directed herein. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the RFP Cross Reference Matrix (RCRM) Attachment L1 to specifically detail and correlate the RFP requirements to the offeror’s proposal. Offerors shall document in sufficient detail allowing evaluators to easily follow the offeror’s proposal and match the proposal to the requirements of the RFP. The cross-reference matrix shall reference the Proposal, PWS, Contract Line Item Number (CLIN), Section L, Section M, and Model Contract. The RCRM is not included in the volume page count.

L2.7.5 Indexing Each volume shall contain a table of contents to delineate the subparagraphs within that volume.

L-9

L2.7.6 Glossary of Abbreviations and Acronyms Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries are not included in the volume page count.

L2.7.7 Binding and Labeling A cover sheet should be clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. Make sure to apply all appropriate markings to proposal data in accordance with RFO 52.215-1(e) (Restriction on Disclosure and Use of Data) and RFO 3.104-4 (Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information).

L2.8 Electronic Offers Email and DoD SAFE proposals will be considered an official offer. Use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through IV in electronic format. Each volume shall be on a different file.

Electronic versions shall be in PDF, Microsoft Excel, and/or Microsoft Word or Office 365-compatible formats.

L2.9 Distribution The "original" proposal shall be so designated and signed by the offeror’s authorized representative. All official offers must be received by the due date identified on the front page of the RFP.

L2.10 Proposal Submissions

Offerors should allow for sufficient time to deliver all proposal information. Offerors are responsible for submitting proposals, and any modification or revisions, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. Any proposal, modification, or revision received at the Government office designated in the solicitation after the exact time specified for receipt of offers is “late” and will not be considered. Late proposals will be handled in accordance with RFO 52.215-1(c)(3).

L2.11 Proposal Quality Proposal must be written in a logical, practical, clear and concise manner and contain all pertinent information in sufficient detail to provide the evaluators with a clear understanding of the offeror’s approach and to permit evaluation of the proposed program. It is the responsibility of the offeror to present enough information to allow the various work efforts, support, and management approaches to be meaningfully evaluated without clarifications or competitive negotiations. The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions. In presenting material in this proposal, the offeror is advised that quality of information is more important than quantity.

Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable. A proposal must be internally consistent or the proposal will be considered unrealistic and may be considered unacceptable. Proposals must clearly and convincingly demonstrate that the offeror has a thorough understanding of the requirements and associated risks, and is able, willing, and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements.

L-10

L3.0 Volume I - Executive Summary

In the executive summary volume, the offeror shall provide the following information:

L3.1 Narrative Summary The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. The salient features should tie in with Section M evaluation factors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L3.2 Table of Contents Include a master table of contents of the entire proposal.

L4.0 Volume II - Technical Proposal L4.1 General

The Technical Proposal shall be clear, specific, complete, and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical Capability Factor 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 the Technical Acceptability Factor.

All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your company will perform all the requirements specified in the solicitation/PWS. It is not necessary or desirable for you to tell the Government so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L4.2 Format and Specific Content L4.2.1 Technical In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of the Technical Acceptability Factor.

L4.2.2 Volume Organization The Technical Volume shall be organized according to the following outline:

Table of Contents List of Tables and Drawings Glossary RFP Cross Reference Matrix (Attachment L1) Roles and Responsibilities Worksheet (Attachment L2) Factor 1 Technical Capability Factor

Tab A: Transition Plan Tab B: Program Management Plan (PMP) Tab C: Lightning Detector Replacement Plan Tab D: Systems Engineering Tab E: Staffing Plan

L-11

L4.3 Technical Capability Factor L4.3.1 Transition Plan The transition plan shall contain a narrative discussion describing the offeror’s transition phase-in approach and ability to achieve full contract performance at the end of the specified phase-in period in accordance with PWS Section 5.1. The detailed, sound, and comprehensive narrative shall include the following information:

• A plan and milestone chart to manage and accomplish a seamless contract phase-in process and employee orientation to ensure successful contract performance at the end of the specified phase-in period.

• A comprehensive, realistic, overall phase-in transition strategy to include timeframes, inventory relocation, and capital investment considerations, including installation of indoor and outdoor components of the mock-ups from incumbent contractor.

• A plan for coordinating with the Government for the transfer and accounting of Government Furnished Property and Equipment.

• A reasonable methodology to maintain the TMQ-53 at an operational availability as outlined in the PWS before the end of the transition period (Table 3-1).

L4.3.2 Program Management Plan (PMP) This section evaluates specific elements of the offeror’s PMP which shall detail the approach and plan by which the offeror will effectively execute the requirements of PWS Sections 5, 6, 7, 8, 9 and 10. The Program Management Plan should provide information on the contractor’s organization, practices and techniques to be used in managing the program and, if applicable, subcontractors. It must provide strong evidence that the requirements stated in the PWS and all other referenced documents are well understood and that the Offeror has developed an integrated approach for successfully managing all aspects of the TMQ-53 CLS program.

L4.3.3 Lightning Detector Replacement Plan The Offeror shall propose a viable technical solution for transitioning the TMQ-53’s currently obsolete lightning detector to an alternative commercially available lightning detector. This effort must be accomplished in accordance with the requirements of the PWS and the TMQ-53 Technical Requirements Document (TRD).

L4.3.4 Systems Engineering Describe the Offeror’s approach performing systems engineering and integration tasks for the TMQ-53 in accordance with PWS Section 8. This description should state the Offeror’s process for managing work including standards, process descriptions, and work procedures to include the purpose, inputs/outputs, entry/exit criteria, activities, roles, measures, and verification steps of work being performed. The Offeror shall provide evidence that these processes are well characterized, understood and described in standards, procedures, tools, and methods.

L-12

L4.3.5 Staffing Plan The Staffing Plan shall provide the offeror’s intended team structure, including partnerships, which demonstrate how the offeror will provide the required level of skills and experience to perform the Contractor Logistics Support (CLS) services for this contract. The plan shall demonstrate key personnel with at least two continuous years of experience in the past five years in the following areas: Program management (PWS Section 6), Logistics Support (PWS Section 7) Systems Engineering (PWS Section 8), Firmware Maintenance and Cybersecurity (PWS Section 9), and Technical Order (PWS Section 10).

1. In addition, the Staffing Plan will include an organization chart and a written rationale for the organizational structure by shift, skill mix, function, and numbers, that the offeror will use to meet PWS requirements (detailing the roles, responsibilities and capabilities of all team members, including subcontractor, supplier, and interdivisional team). The plan shall include a staffing matrix to PWS requirements and an explanation of the relevance of skills and prior experience in CLS services specifically related to weather systems of the team, as well as their interdependencies, relationships, and communication channels. The plan shall include a sound and comprehensive plan to hire, train, maintain and retain qualified staff from contract start and throughout the period of performance to meet all PWS requirements. The plan shall provide an adequate description of the teaming arrangements with any subcontractors or joint ventures including the organizational relationship and the lines of responsibilities between the prime and subcontractors.

2. Key Personnel Skill Level and Experience – The offeror shall provide skill level, education, and prior experience in CLS services specifically related to weather systems of key personnel. The plan shall include resumes for key personnel reflecting their roles/responsibilities, required education, experience, certification, and qualifications needed to comply with PWS requirements. Provide resumes for all key personnel as a separate attachment to the Technical Volume to substantiate the experience. Key personnel meeting this experience requirement do not have to be current employees.

Offeror shall detail how it will address transition of key personnel to maintain expertise and continuity. Changes to resumes of key personnel at time of award must include equivalent personnel of the same or substantially similar background experience.

3. Skill Sets and Experience – Provide the blend of skill sets and CLS services specifically related to weather systems experience levels for the remainder of personnel.

4. Elevated Privileges – Personnel with elevated privileges or access to Government information technology systems shall be certified according to DoDD

8140.01 (formerly DoD 8570.01M).

L-13

L5.0 Volume III – Price

L5.1 General Instructions

The primary purpose of the price proposal volume is to provide the Government an understanding of how the price proposal was developed. The price evaluation criteria of completeness, reasonableness, balance, and Total Evaluated Price (TEP), as defined in Section M of the RFP, will be assessed from the offeror’s information provided in this volume. Compliance with these instructions is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness.

Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal. The burden of proof for credibility of proposed costs/prices rests with the Offeror. Company-owned hardware, software, equipment, assets, etc., being used on this program should also be identified. All information regarding cost or pricing documentation must be included only in the Cost/Price Volume or in the associated Price Tables (B-Tables). Under no circumstances shall this information and documentation be included elsewhere in the proposal.

L5.1.1 Ground Rules/Assumptions The offeror shall identify all ground rules and assumptions used in developing the cost/price documentation.

L5.1.2 Price Data Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position Return to discuss. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume.

L5.1.3 Pricing Data Requirements In accordance with RFO 15.403-1(b) and RFO 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with RFO 15.403-1. If after receipt of proposals the Government determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-2 apply, the offeror shall be required to submit additional pricing data.

L5.1.4 Rounding All dollar amounts provided shall be rounded to the nearest whole U.S. dollar.

L5.1.5 Total Evaluated Price (TEP) Attachment L3 is the Pricing Workbook containing TEP worksheets and shall be populated by the offeror. Prices in the worksheet shall match pricing from information proposed in the line item schedule of the solicitation. The TEP is for award determination purposes only since actual quantities ordered will vary. The TEP will be the deciding factor among the proposals determined to be technically acceptable.

Although the TEP is for evaluation purposes only, the prices/rates proposed by offerors in the Pricing workbook will be incorporated into B Tables in the ID/IQ contract at the time of award and will be used for ordering during the contract ordering period.

L-14

L6.0 Volume IV - Contract Documentation

L6.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 solicitation and all amendments.

L6.1.1 Section A - Solicitation/Contract Form Completion of OFFER, blocks 12-18, ensuring authorized signature by the offeror.

L6.1.2 Section B - Supplies or Services and Prices The offeror shall not complete Section B, but refer to Section 5 for instructions for completing the TEP.

L6.1.3 Section C – Description/Specifications/Statement of Work The offeror shall not complete Section C, but will utilize the documents to develop understanding of the requirement and solicitation offer.

The following will be incorporated through attachment to the final award document:

PERFORMANCE WORK STATEMENT (PWS)

TECHNICAL REQUIREMENT DOCUMENT (TRD)

CONTRACT DATA REQUIREMENTS LIST (CDRLS)

L6.1.4 Section F - Deliveries or Performance Alternate delivery schedules are not acceptable as this is an Indefinite Delivery/ Indefinite Quantity award. Failure to meet the solicitation’s required delivery will result in ineligibility for award. Specific delivery requirements shall be addressed in each resulting Task/Delivery order placed under the resulting contract.

L6.1.5 Section G - Contract Administrative Data Upon Award, Section G data will be provided by the Government.

L6.1.6 Section H - Special Contract Requirements The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section H of each individual task order.

L6.1.7 Section I - Contract Clauses Complete the fill-in clauses listed in this section.

L6.1.8 Section K - Representations, Certifications, and other Statements of Offerors Complete representations, certifications, acknowledgments and statements.

L6.2 Exceptions to Solicitation Requirements Offerors are required to meet all solicitation requirements in addition to those identified as evaluation factors including: terms, conditions, representations, certifications, and technical requirements. 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

L-15 taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2.

Table 6.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph Requirement/ Portion Rationale

PWS, 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

L6.3 Other Information Required L6.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the offeror’s proposal and who can obligate the offeror’s company contractually. Also, identify those individuals authorized to negotiate with the Government.

L6.3.2 Government Offices Provide the mailing address, telephone and email addresses, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and email addresses for the Administrative Contracting Officer (ACO).

L6.3.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code;

TIN; and Small Business size status. 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.

L6.3.4 Associate Contractor Agreements (ACA) Provide statement of intent to submit Associate Contractor Agreements if applicable. Once an award is made, the ACA will be required within 10 days after award and inserted into the contract as an attachment by modification.

L6.4 Non-Disclosure Agreements and Conflicts of Interest

Offerors are advised that non-government personnel employed by the firms identified below may serve as advisors in the source selection process. Non-government personnel are excluded from determining ratings and rankings of offeror proposals. If the Offeror has any connection with the listed companies below, they shall submit a list of names, the member’s NDA, and the mitigation to remove the member from preparing any proposal submission. This may include an organizational chart showing the member is not in connection with the proposal or execution of the contract. Please ensure the solicitation title and number are indicated in each NDA.

The following are the non-government companies that may be part of the source selection process, and their points of contact:

L-16

Odyssey 55 Old Bedford Road, Suite 310 Lincoln, MA 01773 POC: Tim Letourneau Email: TimLetourneau@odysseyconsult.com Phone: 781-885-6126

Inquisit LLC 44715 Brimfield Dr., Suite 230 Ashburn, VA 20147 POC: Greg Walker Email: gwalker@inquisitllc.com Phone: 571-723-2745

Apogee Engineering 8610 Explorer Dr., Suite 305 Colorado Springs, CO 80920 POC: Elizabeth Burmester, ASSETS Program Manager Email: Beth.burmester@ApogeeUSA.com Phone: 402-912-7800

Astrion 1100 Redstone Gateway Ste 230 & 300 Huntsville, Alabama POC: David Kurz Email: david.kurz@astrion.us Phone: 757-927-2184

Quantech Services 1 Hartwell Pl #2 Lexington, MA 02421 POC: Alex Pinheiro Email: alex.pinheiro.1.ctr@us.af.mil Phone: 978-551-5459

Applied Research Solutions (ARS) 51 Plum St Suite 240 Beavercreek, OH 45440 POC: Keith Daniels Email: keith.daniels.4.ctr@us.af.mil Phone: 334-294-3504 mailto:alex.pinheiro.1.ctr@us.af.mil

L-17

L7.0 Required Attachments

The following attachments will be provided as separate files with the final RFP package:

Attachment L1: Cross-Reference Matrix

Attachment L2: Roles and Responsibilities Worksheet

Attachment L3: Pricing Workbook

L7.0 Required Attachments