Attachment2_2023-07-28_RFP Section L ITO_Acoustics.docx

UNSCLASSIFIED

Section L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS (ITO)

FOR THE

AFLCMC/XA

Aeroacoustic Reproduction System Effort

Solicitation # FA8684-23-R-B023

28 July 2023

UNCLASSIFIED

Attachment 2 Section L - Instructions To Offerors

UNCLASSIFIED

TABLE OF CONTENTS

INSTRUCTIONS TO OFFERORS (ITO)

AND

INSTRUCTIONS FOR PROPOSAL PREPARATION

Aeroacoustic Reproduction System Effort Structure and Objectives The AFLCMC/XA Aeroacoustic Reproduction System (ARS) project broadly describes the United States Air Force (USAF) effort to develop a system to simulate the acoustic signature of an active airfield for immersive training scenarios. The effort is structured in five phases: (1) Research and Analysis, (2) Prototype Design, Development and Characterization Testing, (3) Full Scale Design, Development, and Operational Assessment, (4) End-User Employment Exercise, and (5) System Refinement and Additional Builds.

The objectives of this effort include development of an acoustic system, creation of training manuals and material, and consideration of full life cycle support measures. The scope of this Request for Proposal (RFP) includes procurement and testing of up to five Aeroacoustic Reproduction Systems. Although additional procurement or iteration of the ARS and documentation may be required, any follow-on efforts would be awarded as a separate acquisition under a new contract and not included within the scope of this RFP.

Information is provided below for consideration in developing a proposal:

a) Customer: United States Air Force (USAF)

b) Contract will be competitively awarded with full and open competition

c) Base plus options: One base CLIN, three option CLINs and one unpriced option CLIN

d) Cost Plus Fixed Fee (CPFF) Proposal Preparation Instructions This section provides general guidance for preparing proposals, as well as specific instructions on the format and content of the proposal. Offerors are required to submit one proposal IAW instructions in Paragraph 2.2 with sufficient information concerning all factors and subfactors to enable Government personnel to fully ascertain capabilities of the offeror to perform the requirements. The offeror’s proposal must include all data and information requested and must be submitted IAW these instructions. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Alternate proposals are not acceptable. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation.

The proposal shall be clear and 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.

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

Offerors are advised that the costs incurred as a result of responding to this solicitation are not chargeable to this proposal effort.

2.1.1 Point of Contact (POC)

The Contracting Officer (CO), Andrea Williams, (937) 904-5867, e-mail: andrea.williams@us.af.mil and Contract Specialist/Buyer, Ryan Murphy, (937) 656-5281, e-mail: ryan.murphy.43@us.af.mil are the primary POCs, for this acquisition. Unclassified written questions or requests for clarification may be sent via email to these individuals. It is encouraged that any such questions or requests be submitted within 10 days of the RFP release date. The subject line for such emails should read: Source Selection Sensitive – Solicitation # FA8684-23-R-B023 Competition Vendor Q&A. Answers to questions and clarifications will be provided via email. In the event of conflict between the answer to questions and the RFP, the RFP shall take precedence.

2.1.2 Discrepancies

If an offeror believes 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, and it is the Government’s intent, to award this effort based on the initial proposal, as received, but reserves the right to conduct discussions if necessary.

2.1.3 Data

The Government will provide cleared and approved bidders the statement of work (SOW), sample audio files, and AFLCMC/XA OPSEC Plan. In order for bidders to receive such information, a request must be made to the collateral security POC Chaun Edwards, (937) 713-0125, email: chaun.edwards@us.af.mil and Justin Harger, (937) 656-8942, email: justin.harger.ctr@us.af.mil no later than 10 business days after RFP release. Andrea Williams and Ryan Murphy, contact information above, shall be courtesy copied on all requests. Requests for access to CUI material shall include the following information:

· Facility Cage Code

· CUI Training Certificate of Completion IAW DoDI 5200.48

· Email to receive CUI material

2.1.4 Electronic Reference Documents

All referenced documents for this RFP are available to cleared and approved bidders.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 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 the table. The contents of each proposal volume are described in the ITO paragraph as noted in the following table.

Table 1- Proposal Organization and Page Limits

Note 1: The Integrated Master Schedule (IMS) associated with the SOW shall be delivered in MS Project and will not count towards the overall page count. Any updates (as required) shall be delivered with changes annotated and will not count towards the overall page count.

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

2.2.2 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price and Contract Documentation Volumes or when specifically asked for.

2.2.3 Cross Referencing

To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information cross-referenced and required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal.

2.2.5 Indexing

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tables of contents do not count against the page limitations for their respective volumes. Indexing shall be used to identify sections and do not count against the page limitations for their respective volumes.

2.2.6 Glossary of Abbreviations and Acronyms

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

2.2.7 Marking

All proposal pages shall include the following footer at the bottom of each page:

CUI - SOURCE SELECTION INFORMATION See FAR 2.101 and 3.104

2.2.8 Page Size and Format

Page size shall be 8.5 x 11 inches. Pages shall be single-spaced with a double space between paragraphs. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point Times New Roman. 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 ¾-inch side margins. Pages shall be numbered sequentially by volume.

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. Technical proposals may contain no more than three 11 by 17 pages for tables, charts, graphs, and figures, and those pages will count against the 100 page limit. For tables, charts, graphs, and figures, the text shall be no smaller than 10-point. Transmittal letters will not be considered in the overall page count, nor will they be evaluated.

2.2.9 Submission Format

No paper copies of offers will be accepted.

2.2.10 Electronic Proposals

Submit electronic versions of all volumes via email (preferred) or JWICS. If files are compressed, the necessary decompression application must be included. Multiple emails, if required, will each be labeled with the email number and contents. The file-naming convention for the proposal volumes is as follows. It is permissible to expand on these file names if a list of the content of each is provided.

2.2.11 Proposal Version

When submitting electronic versions of their proposal, offerors shall follow these instructions:

a) Submitting documents using Microsoft Office:

· Word documents – Set “Save as type” to “Word Document (*.docx)” only.

· Excel spreadsheets – Set “Save as type” to “Microsoft Excel Workbook (*.xlsx).”

· PowerPoint presentations – Set “Save as type” to “Microsoft PowerPoint Presentation (*.pptx).”

Submit any Microsoft Project files in Microsoft Project (*.mpp). There are no special “save” functions required for later versions of Project.

Submit PDF documents using only Adobe Acrobat. Do NOT submit any documents in PDF format that are copied as “images.” When creating PDF files always create to enable textual search and copy functions.

2.2.12 Proposal Submission

Proposals shall be submitted as follows no later than 2 October 2023 at 1700 EST.

Use classification and marking guidance provided by the Information Security Regulation (DoD 5200.1 vol. 1-3) and the National Industrial Security Program Operating Manual (DoD 5220.22-M) when marking and transmitting information previously classified by another original classification authority.

Proposals shall be addressed to the CO, Andrea Williams, and submitted through the Department of Defense (DoD) Secure Access File Exchange (SAFE) at https://safe.apps.mil to Ryan Murphy, Contract Specialist, at ryan.murphy.43@us.af.mil. An unclassified email should also be sent directly to ryan.murphy.43@us.af.mil with carbon copy (CC) to andrea.williams@us.af.mil to notify a submission has been uploaded and to provide the DoD SAFE encryption passphrase. Contractors that do not have an authenticated DoD Common Access Card (CAC) to login to DoD SAFE can request a SAFE Drop-Off from the Contract Specialist, Ryan Murphy, at ryan.murphy.43@us.af.mil. Request for DoD SAFE Drop-Off shall be submitted at least one week prior to the proposal due date.

Volume I – Technical Proposal

3.1 General

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 not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Directly answer each detail of every measure of merit.

The Volume I, Technical Proposal, should be specific and complete. Legibility, clarity, brevity, and coherence are important. Your proposal will be evaluated against the Technical subfactors as defined in the RFP’s 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.

3.2 Formats and Specific Content

The Volume I, Technical Proposal, shall address your proposed approach to meeting the requirements of the SOW and each Technical subfactor.

3.3 Organization

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

a) Table of Contents (not included in the volume page limit)

b) List of Tables and Drawings (not included in the volume page limit)

c) Glossary (not included in the volume page limit)

d) Content

3.4 Technical Approach/Risk Subfactors

The following are subfactors that will be evaluated in accordance with the RFP’s Evaluation Factors for Award:

Subfactor 1: Relevant Experience Gate Subfactor 2: Personnel and Infrastructure Subfactor 3: System Development and Performance Subfactor 4: Program and Risk Management

3.4.1 Subfactor 1 – Relevant Experience Gate

The offeror shall provide a clear and complete description of relevant experience that relates to successfully achieving performance requirements as outlined in the SOW. The description shall clearly detail how the relevant experience directly relates to the offeror successfully achieving the requirements in the SOW. The relevant experience description shall include important details of acoustic modeling, design (hardware and software), construction and/or integration, and testing and evaluation (T&E). The offer shall provide customer and/or government point of contact (POC) for the Government to contact to confirm experience.

This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of relevant experience.

3.4.2 Subfactor 2 – Personnel and Infrastructure

The offeror shall describe/submit the following processes/approaches/descriptions for this subfactor:

a) A complete description of key personnel, including, but not limited to, specialty jobs/skills applicable to completing the requirements of the SOW, current clearances held, and unique qualifications applicable to completing the requirements of the SOW. Do not include the names of the personnel in your description.

b) A complete description of the facilities and equipment to be used to complete the requirements of the SOW, specifically:

1) Acoustic T&E facilities and/or special test equipment planned to assess and develop the ARS

2) Acoustic M&S software to assess sound propagation and psychoacoustic performance

3.4.3 Subfactor 3 – System Development and Performance

The offeror shall describe their planned approach to design, develop, and evaluate an expeditionary ARS to achieve the requirements described in the SOW, Section 2 (including subparagraphs):

a) Describe how modeling, simulation and analysis (MS&A), research and develop (R&D), and/or testing and evaluation (T&E) will support design and development of the ARS and mitigate potential performance risks.

b) Describe your planned approach to balance acoustic performance with expeditionary deployment considerations in order to minimize the transportation footprint and setup time.

c) Describe your planned approach for conducting internal requirement validation testing and supporting the operational assessment and end-user employment exercise. This approach shall include recommendations for assessing the system performance in an operational environment.

3.4.4 Subfactor 4 – Program and Risk Management

The offeror shall describe its processes and capabilities to manage and execute the system requirements established in this RFP. The offeror shall describe its process and substantiate the following as required by the SOW, Section 2 (including subparagraphs), CDRLs, and reference documents included in the paragraphs:

a) Describe your process for supporting Program Management. This process and description shall specifically detail the following:

1) The offeror’s staffing plan to show how government requirements as described in the SOW will be met.

a. Management structure, processes for controlling/managing personnel, and quality control, including organizational charts. It shall include identification of a Program Manager, Site Managers, and other key supervisory personnel.

b. Integrated Master Schedule (IMS) that captures planned program milestones in MS Project.

b) Describe your process for identifying, analyzing, monitoring and responding to potential technical risks that could impact the project’s success.

Volume II – Cost/Price Proposal

4.1 General Instructions

This section is to assist offerors in submitting other than certified cost or pricing data that is required to evaluate the offeror’s proposal in accordance with Section M. Compliance with these requirements is mandatory and failure to comply with these requirements may result in rejection of an offeror’s proposal. All costs shall be contained in the model contract Section B and the Cost/Price Volume.

The Government will evaluate each proposal in accordance with the Cost/Price Factor in Section M. For CLINs 0001 through 0004 and 0007, the Government will evaluate the technical and estimating approach and perform a cost realism analysis. Additionally, unbalanced pricing may increase performance risk and could result in payment of unreasonably high prices. An offer may be rejected if the Contracting Officer determines a lack of balance poses an unacceptable risk to the Government.

The Government will determine the most likely cost for CLINs 0001 through 0004 and 0007 in accordance with Section M and the FAR. To assist this determination, the offeror must substantiate its proposed cost for CLINs 0001 through 0004 and 0007. CLIN 0005 will not be pre-priced but will be an option CLIN to be determined at a later date. In order to substantiate the proposed cost for CLINs 0001 through 0004 and 0007 the offeror must demonstrate the accuracy and validity of the cost proposal Basis of Estimate (BOE). Mere compliance with these instructions and documentation of the source data and calculations, while necessary, is not in and of itself substantiation of a realistic cost. The relationship of historical cost data to the proposed cost and the validity of adjustments and estimating judgments must be demonstrated and justified as outlined in this section.

The burden of proof for credibility of proposed costs/prices rests with the offeror. Proper presentation and adequate supporting documentation are necessary to ensure the cost/price proposal is efficiently evaluated and all assumptions are understood. If the offeror does not, in the Government’s judgment, substantiate its cost proposal in part or as a whole, the Government may consider other data and the judgment of the members of the source selection evaluation team in determining the most likely cost.

All costs/prices shall be provided in US currency and rounded to the nearest dollar unless otherwise noted. Labor rates shall be rounded to the nearest penny.

Proposed cost/price information shall be submitted in then-year dollars phased by the calendar year (1 January– 31 December) unless otherwise noted.

1.1.1 Cost Volume Instructions

The Cost Volume shall be arranged into primary sections as follows:

a) General Information

The offeror shall provide an overview of the process used to develop the proposal. This shall include, at a minimum, a summary of the approach used to estimate labor hours, labor rates and material costs, including a description of the process used to obtain any vendor quotes.

Indicate any deviations from the offeror’s standard estimating, purchasing, and accounting procedures in preparing this proposal volume. Also indicate whether the offeror has Government approval of its systems and if so, provide evidence of such approval.

Any accounting changes in the offeror’s estimating or accounting practices that impact the proposal’s historical data or basic assumptions shall be fully explained. General information shall be provided in this section, with specifics provided in the appropriate Basis of Estimate. The offeror shall also identify any changes to its accounting system that are planned or which are required to comply with this program’s requirements.

The offeror shall provide an explanation of ground rules and assumptions that affect the cost estimates. Topics to be addressed should include, but are not limited to: technical and programmatic requirements, business base, labor and overhead rates, investments, cost-sharing arrangements, make or buy decisions, prime- subcontractor relationships, and price escalation. General information shall be provided in this section, with specifics addressed in the appropriate Basis of Estimate or Additional Information section.

b) Cost Summaries

The offeror shall summarize its proposed costs in accordance with the proposed Work Breakdown Structure (WBS). The offeror may expand the program (WBS) and provide costs at a lower level to better reflect the level at which the estimate was developed. The sum of the WBS elements shall correspond to the offeror’s total proposed cost with subtotals provided at each higher level of the WBS. Information required in this section includes total program costs, separately identified as non-recurring and recurring costs, as well as the offeror’s G&A, profit or fee, and Facilities Capital Cost of Money (FCCOM).

The BOEs required in Section 3 below should trace to the lowest level at which the estimate is substantiated. BOEs should generally be provided at the WBS level provided in the Contract Data Requirements List (CDRL) (e.g. Contractor Performance Report (CPR) / Contractor Cost Data Report (CCDR)) but it is more important that the BOEs clearly demonstrate the proposed cost is realistic. As such, BOEs may be provided at either a lower level of detail with hours and/or costs shown to “roll up”, or BOEs may be provided at a higher level with reasonable and supportable allocation techniques used to spread hours and/or costs to “fill out” the estimate.

The offeror shall also include a traceability matrix or table that shows the link between the labor hours and material costs included in the cost summaries and those in the Basis of Estimate. Similar information shall be provided to show traceability between the prime and any subcontract or other effort separately substantiated.

c) Basis of Estimate (BOE)

1) Content Provide the following information, at a minimum for each BOE:

· WBS number and title

· SOW requirement being addressed

· Technical activities required to meet the SOW requirement

· Task description including the disciplines required to perform the work. Description of tasks and technical approach shall be consistent with other parts of the proposal

· Risks and planned mitigations, as applicable

· Total costs and labor hours, as applicable, proposed by Calendar Year

· Methods and calculations used to develop the estimate (see b. below)

· Source data, assumptions, and normalization (see c. below)

· Crosschecks and supporting data, if any, used to validate the realism of the estimate

2) Methods

This section shall provide the estimating methodologies of the labor hours, labor costs, material costs, and other costs presented in Cost Summaries and address why the offeror’s proposed cost is realistic. Individual BOEs should be written in a clear, concise manner with enough information to allow the evaluator to easily read and understand the basis of estimate and judge its credibility. The offeror shall describe the BOE in sufficient detail to enable the Government to replicate the offeror’s estimate.

The offeror may use any generally accepted estimating techniques to develop its estimates, including, but not limited to, cost-to-cost and cost-to-non-cost estimating relationships, commercially available parametric cost models, in- house developed parametric cost models, and adjusted or unadjusted historical performance on analogous tasks. Historical data from comparable or analogous systems or subsystems should be used to substantiate the offeror’s estimate where possible; multiple comparisons or cross-checks are preferred and generally enhance (but do not guarantee) estimate credibility.

3) Source data

When using historical data, a summary programmatic and technical description of the analogous system should be provided along with the actual cost data for the analogous system and a comparison to the proposed system. This information is required in order to identify parameters that are likely to influence the cost of the proposed system, and to establish the relationship between the proposed system and the analogous system. Historical data used in the BOEs should trace to total program costs reported in auditable reports (e.g., prior cost and technical CDRL items). The cost data should be provided in terms of total hours and dollars actually spent by calendar year and per unit as applicable. Also include an explanation of the relationship between the analogous element cost and its total program cost.

How comparable?

The offeror should describe how the historical effort is comparable to the proposed program. This includes an explanation of the technical and programmatic similarities and differences between the historical and proposed systems. The offeror should provide a technical description including the performance and physical aspects of the historical system. This describes the systems in terms of the number of parts, physical configuration, type of material, technology, as well as physical and performance parameters. The offeror should also provide a programmatic description related to the acquisition aspects of the historical system. This includes, for example, the years the item was procured, production rates, quantities procured by year and definition of system composition, sole source or competitive procurement, and the development time period.

How adapted?

The offeror should explain how cost data available from past experiences was adapted to reach the estimate for the proposed system. The offeror should provide the basis and document any adjustments applied to the historical data in order to reach the proposal estimate. All relevant assumptions should be identified and justified.

If a “new or improved” engineering or manufacturing process is the basis for projected cost savings over historical systems, the Offeror shall provide a description of the improvements, the relationship to the previous process, and a summary of how these improvements will be achieved. Specific savings in work hours and material must be documented and justified with regard to the content, practicality, and probability of these improvements.

General statements such as “estimates were derived from engineering analysis or judgments” are insufficient. Other approaches not considered sufficient include (not an exhaustive list): calculations without supporting rationale and data; Cost Estimating Relationship’s (CER) without providing an explanation of its application and merit to the proposed program and the historical data used in the derivation of the CER or documentation from the cognizant Administrative Contracting Officer (ACO) supporting its established use within the company’s estimating system; and references to analogous systems without providing the historical data, an explanation of the similarities or differences to the proposed program, and justification for all adjustments made to the historical data in developing the proposal.

4) Rates, Cost to Sell Equations, and Escalation

The offeror shall provide labor rate information used in the proposal in this section. If providing rates over a different period of performance than the calendar year (e.g. on a calendar year basis), include a trace between these rates and calendar year rates used in developing the estimate.

The offeror shall identify the basis of labor rates used in the proposal, e.g. Forward Pricing Rate Agreements (FPRAs), Forward Pricing Rate Proposals (FPRPs), Collective Bargaining Agreements (CBAs), Area Wage Determinations (AWDs), Government-recommended rates, or special rates analysis in support of the proposal. Submit a copy of any such document or agreement used as the basis for, or used as the starting point of special rates analysis in support of, proposed labor rates.

The offeror shall identify the indirect rates used in the proposal. The offeror should include a projection of indirect rates that assumes the award of this contract and options in its business base. Any deviation from a current FPRA (or current FPRP if there is no FPRA) due to the award, variation of the business base or other factors should be fully described and justified. If there is no standing FPRA/FPRP in effect, please provide three years of historical indirect cost data through which the proposed rates were developed. Discuss the application of these rates in the proposal. In addition, provide summary-level definitions for each major indirect rate account, explaining what costs are included in each indirect pool. The indirect accounts may include, but are not limited to, engineering overhead, manufacturing overhead, G&A, material handling overhead, and FCCOM.

The offeror shall identify the direct labor rates used in the proposal. Any deviation from the current FPRA (or current FPRP if there is no FPRA) should be fully described and justified. If there is no standing FPRA/FPRP in effect, please provide three years of historical labor cost data through which the proposed rates were developed. Discuss the application of these rates in the proposal, including the build-up of any composite or aggregated direct labor rates. In addition, provide a complete list of the offeror’s direct labor categories, including definitions for each, and describe the mix of direct labor categories included in the proposal. Direct labor categories may include, but are not limited to, engineering, manufacturing, maintenance and support, tooling, quality control, manufacturing, and integration.

The offeror shall submit the methodology used to transfer foundational cost data (i.e. direct labor hours or material direct dollars) into a sell price to the Government (i.e. fully-burdened with fee). This includes the sequence in which indirect rates, profit, etc. were applied to direct costs to determine the sell price. Include the base against which each of the overhead or other factors is applied in this description.

The offeror shall provide all escalation-related assumptions used in the proposal. Information required in this section includes, but is not limited. to, annual rates of escalation, source of escalation indices, rationale for its application, and the method of application.

Volume III – Contract Documentation 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 the following sections:

5.1 Sections

5.1.1 Section A: Contract Clauses

The contract clauses pertinent to this section and that are required are to be included in this volume.

5.1.2 Section B: Description/Specifications/Work Statement

Other plans/specifications due with the proposal IAW the SOW not otherwise provided for under the Technical Volume includes the following:

a) Security Plan in accordance with the SOW Section 9, the AFLCMC/XA OPSEC Plan, and DoDI 8510.01.

b) Quality Control Plan in accordance the SOW Section 5.

5.2 Other Information Required

a) 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 as well as the name, title, and telephone number of the Chief Executive Officer (CEO), Division President, and/or Vice President.

b) Government Offices: Provide the Point of Contact (POC) Name, mailing address, telephone and fax numbers, and facility codes for the cognizant DCMA, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

c) Company/Division Address, Identifying Codes, and Applicable Designations

d) Provide company/division’s street address and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area designation. The same information is required for any subcontractor(s).

UNSCLASSIFIED