L001 INFORMATION TO OFFERORS 10 FEB 12.pdf

L001 INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL

1.0 Program Structure and Objectives

1.1 Background

The purpose of this procurement is to acquire an asset used by Battlefield Airmen. The asset is designated as a Line of Sight Short (LOS-S) device, providing a lightweight integrated range finder/designator/sensor to enhance targeting effectiveness at ranges less than or equal to three kilometers. The contracting activity conducting the LOS-S source selection is ASC/WISK, Wright-Patterson AFB, OH. The initial EMD contract(s) phase will conclude with the delivery of up to six (6) prototype systems, which will be developed and operationally tested and evaluated prior to being considered for the production phase. Upon successful evaluation, the program office may decide to exercise options to purchase production assets on a buy-to-budget basis. The successful offeror will also create a training curriculum and propose an interim contractor sustainment strategy to support the LOS-S units. However, based on cost and other considerations, the Government reserves the right not to award a contract at all. If two awards are issued for the EMD effort, an appropriate number of prototypes will be awarded to each successful offeror and these prototypes will be developed and operationally tested and evaluated.

The production options may be exercised to the offeror whose prototypes perform best during the evaluation. The contract type will be a combination of cost plus incentive fee for EMD and firm fixed price for all remaining CLINs.

1.2 Funding/Budget Estimates - Limitation of Government Obligation (LOGO) The following funding/budget estimates are provided for consideration in developing your proposal. These budgets are subject to change and availability. The budgets are for planning purposes only and are not contractual.

Limitation of Funding

RDT&E FY$M $2.998M

1.3 Schedule

For the purpose of scoping the EMD effort, the contractor should use an eighteen (18) month period from contract award to final testing.

2.0 General Instructions

The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offeror shall be compliant with the requirements as stated in the Statement of Objectives (SOO), Systems Requirements Document

(SRD), Contract Data Requirements List (CDRL) and Request for Proposal (RFP)/Model

Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors 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.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

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 for 180 days after proposal receipt date.

In accordance with 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.

3.0 General Information

3.1 Point of Contact

The Contracting Officer (CO), Captain Tom Guyer, e-mail thomas.guyer@wpafb.af.mil is the sole point of contact for this acquisition. Address any questions or concerns you may have to the

CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/ solicitation. Any questions shall be submitted within ten (10) days of the

RFP release date. Answers to any such questions/clarifications will be provided on FedBizOpps and/or via RFP amendment. In the event of conflict between the answer to questions/clarifications and the RFP, the RFP shall take precedence.

3.2 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 &

3.104” in the Subject line Otherwise, source selection information will be transmitted via USPS, FedEx, UPS, or pick-up by local representative designate by the CO.

3.3 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

3.4 Electronic Reference Documents

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15505 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15506

All referenced documents for this solicitation are available on the Federal Business Opportunities

(FedBizOpps) web site at <http://www.fedbizopps.gov>. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

3.5 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 discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

3.6 Proposal Submission Content

The offeror's proposal shall be prepared and submitted in six (6) volumes:

Executive Summary (Volume I)

Technical/Technical Risk (Volume II)

Past Performance (Volume III)

Cost/Price (Volume IV)

Contract Document (Volume V)

Contract Attachments (Volume VI)

Volume II shall have three distinct sub-volumes as defined in Table 1. The titles and contents of the volumes should be as defined in Table 1 all of which shall be within the required page limits and the number of copies specified in the table. All volumes shall be provided in two (2) different media, electronic (CD-ROM) and paper as defined in Table 1. As a minimum, each

CD-ROM as well as the paper volumes will be labeled with a cover page containing the program reference, volume title, and submission date. 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. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary.

Table 1 - Proposal Organization

Vol Page

Number

Title Hard

Copies

Elec

Copies

Page

Limit

I Executive Summary 4 4

IIA Technical: Performance Requirements

Section 1: System Specifications

Section 2: Technical Approach

4 2 30

IIB Technical: Systems Engineering and Program

Management

Section 1: System Engineering Plan

Section 2: Integrated Master Plan

Section 3: Statement of Work

Section 4: Integrated Master Schedule

2 50

(Note 1)

Section 5: Contractor Defined Level 3

Contract Work Breakdown Structure

Section 6: Small Business Subcontracting

Plan

Section 7: Technical Risk Matrix

IIC Technical: Product Support/Training

Section 1: Product Support Approach

Section 2 Training Information

4 20

III Past Performance

Note 2

IV Cost/Price

Section 1: Table of contents, summary desc.

Section 2: Cost/pricing information

Section 3: Other information, long lead costs

4 2 50

V Contract Documentation (Section A – K) (See

Note 2 below)

4 (Note 1)

VI Contract Attachments 2 (Note 1)

Note 1: For Volume IIB, attachments SOW, IMS, CWBS, Small Business Plan there will not be a page limit. The same shall apply to Section V and VI submittals.

Note 2: For Volume III contractors shall submit their Past Performance Information (PPI) using the PPI tool provided by the Government at Attachment 2 to Section L. Each Past Performance reference shall not exceed 5 pages. In addition, the Offeror shall submit a consent letter in accordance with the format contained in Attachment 3 to Section L executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter in accordance with the format contained in Attachment 4 to Section L, authorizing release to the Government of requested information on the Offeror's performance.

3.7 Page Size and Format

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. Foldouts shall not exceed 11 x 17 inches and may be used only for large tables, charts, graphs, diagrams and schematics, not for pages of text. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. 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 bound side and 1/2 inch on the unbound side margin. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to

ENs. Embedded tables, charts, graphs and figures shall be used wherever practical and shall be uncomplicated and legible. For tables, graphs and figures, the text shall be no smaller than 8 point. These limitations shall apply to both electronic and paper copy proposals.

3.8 Proposal Submission Deadlines and Guidance

Offeror are advised to submit the Past Performance (Volume 3) part of the proposal by 12:00 pm

Eastern Standard Time (EST) on the 15th calendar day after RFP release. Failure to submit early past performance information will not result in offeror disqualification.

Offeror shall submit an appropriate number of copies (ref. table 1) and one original signed and dated offer to the office specified below to be received no later than 1500 hrs (Eastern Standard

Time) on proposal receipt date: Late submittal will result in offeror disqualification in accordance with FAR 15.208.

ASC/WISK (Battlefield Airmen)

Attn: Capt Tom Guyer, Contracting Officer

1895 Fifth Street, Bldg 46

Wright-Patterson AFB OH 45433-7200

One of the four (4) paper copies submitted shall be the original signed copy and will become the official contract copy. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. Each volume of the proposal shall be contained in a separate three-ring loose leaf binder which permits the volume to lie flat when open. Staples shall not be used. A cover sheet should be contained in each volume, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. All appropriate markings including those prescribed IAW FAR 52.215-1(3), Restriction on Disclosure and Use of Data, and 3.104-5, Disclosure, Protection, and Marking of Contractor's Bid or Proposal Information, Source Selection Information, and classification will be applied.

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practicable. Each page shall be counted except the following:

a. Transmittal/cover letters b. The Integrated Master Plan

c. Cover pages d. The System Specification

e. Executive Summary f. The Integrated Master Schedule (IMS)

g. Tables, including Tables of Content h. The Statement of Work (SOW)

i. Graphs j. Contractor Defined Level 3 CWBS

k. Matrices - embedded or attached l. Small Business Subcontracting Plan

m. Glossaries n. Tabs

(*) Page limitations may be placed on responses to Evaluation Notices (ENs). In the event the Government conducts discussions with offerors, the specified page limits for

EN responses will be identified in the letters forwarding the ENs to the offerors.

Other than the CLIN pricing in Section B of the contract, all cost or pricing information provided by the contractor shall be addressed only in Volume IV. Pricing matrices exist for CLIN 0001 and 0002. Under CLIN 0001, the contractor is expected to reflect all developmental costs supported by the cost element worksheet and delivery of a single prototype under EMD Article

1. The contractor is also expected to reflect increased subsequent cost for one (1) each additional prototype up to and including EMD Article 6. Doing so will allow the government to appropriately consider developmental costs and costs associated with additional prototype awards

To the greatest extent possible, each volume shall 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. 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 cross reference matrix at Attachment 1 to Section L of the RFP indicating the proposal reference information as it relates to the ITO, SOO/SOW, CLIN numbers, and CDRL references found therein.

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.

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.

The electronic proposal version shall not be different in content or format from the paper version.

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

a. Electronic storage media shall be submitted in one of the following formats:

prerecorded (pressed) CD-ROM or CD-R.

b. Submitting documents using Microsoft Office 2010:

i. Word documents – Set "Save as type" to "Word Document (*.docx)" only.

ii. Excel spreadsheets – Set "Save as type" to "Microsoft Excel Workbook

(*.xlsx)."

iii. PowerPoint presentations – Set "Save as type" to "Microsoft PowerPoint 2010

Presentation (*.pptx)."

c. Submitting documents using Microsoft Office 2007:

i. Word documents – Set "Save as type" to "Word Document (*.docx)" only.

ii. Excel spreadsheets – Set "Save as type" to "Microsoft Excel Workbook

(*.xlsx)."

iii. PowerPoint presentations – Set "Save as type" to "Microsoft PowerPoint 2007

Presentation (*.pptx)."

d. Submitting documents using Microsoft Office XP (2003):

i. Word documents – Install the Office Compatibility Pack from www.microsoft.com

ii. Excel spreadsheets – Install the Office Compatibility Pack from www.microsoft.com

iii. PowerPoint presentations – Install the Office Compatibility Pack from www.microsoft.com http://www.microsoft.com/ http://www.microsoft.com/ http://www.microsoft.com/

e. Submit any Microsoft Project files in Microsoft Project 2007. There are no special

“save” functions required for later versions of Project.

f. Submit PDF documents using only Adobe Acrobat 9.0 or later. 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.

Indicate on each CD-ROM the offeror name, solicitation number, date, volume number and title.

Each volume shall be in separate directories on the CD-ROM. Use separate files to permit rapid location of all portions, including exhibits, annexes, addenda and attachment, if any. If files are compressed, the necessary decompression program shall be included. Multiple disks, if required, will each be labeled with the contents. The file-naming convention for the proposal volumes is as follows:

Files File Name

Volume 1 - Executive Summary Executive Summary

Volume 2 - Technical/Technical Risk Technical

Volume 3 - Past Performance Past Performance

Volume 4 - Cost/Price Cost Price

Volume 5 - Contract Documentation (Sections A - K) Contract Documentation

Volume 6 - Contract Attachments (Section J) Contract Attachments

4.0 Volume I - Executive Summary

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

4.1 General

This should be a concise narrative summary of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

4.2 Table of Contents

Include a master table of contents of the entire proposal.

5.0 Volume II - Technical Volume

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

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.

5.2 Format and Specific Content

5.2.1 In the technical volume, address your technical solution for meeting or exceeding the

Government’s minimum performance or capability requirements of each technical subfactor.

5.2.2 Under Factor 1, found at para. 5.3, address your Technical Risk at the factor level only associated with those aspects of the proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance.

Classify each identified risk in accordance with DoD Source Selection Procedures Table 3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOW, specification requirements, production capacity, etc.), whether or not those requirements are identified as subfactors. Propose a realistic

"work-around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation. (All graphical and tabular data must be in Microsoft Office EXCEL)

5.3 Sub-Factor Volume Organization

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

5.3.1 Table of Contents

a. List of Table and Drawings

b. Glossary

c. Cross Reference Matrix

d. Sections identified in table 1 above

e. Risk Matrix

5.3.1.1 Subfactor One – Performance Requirements

The offerer shall:

a. Provide a Performance Requirement Cross Reference Matrix that links the SRD requirements to the LOS-S System Specification, the CWBS and SOW

b. Provide a System Specification document which outlines conformance with the performance threshold requirements set forth in the LOS-S SRD. This document shall include detailed descriptions and the basis for any assumptions used to assess LOS-S performance.

c. Describe how the proposed System Specification will meet or exceed thresholds and move toward the objectives found within the SRD. Certain performance requirements will be considered for evaluation strengths based on ability to reasonably achieve objective criteria, see Section M Subfactor 1(c) criteria for elaboration.

5.3.1.2 Subfactor Two - Systems Engineering and Program Management

The offeror shall:

a. Provide a system design and design review plan which describes the design review process and how it relates to the IMP to include how you address risk identification and https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/1.%20%20Published%20Baseline/MP5315.3.doc#p5512 mitigation, content of reviews, frequency of reviews, entrance and exit criteria for each review.

b. Describe level of systems integration done to date and your plan to complete the System

Integration through the development program (any special emphasis on integration to meet form factor and software integration into the BAO Kit, and the Power, Generation and Management system).

c. Provide a Small Business Subcontracting Plan and Small Business Participation Plan, if applicable, satisfying the requirements as identified in Section L, para. 9.2.6 and FAR

52.219-8, 52.219-9 Alt II, DFARS 252.219-7003 and AFFARS 5319.704.

d. The contractor shall provide an IMS which reflects a critical path through EMD and production along with associated schedule risks commensurate with the IMP, SOW and

CWBS.

5.3.1.3 Subfactor Three – Product Support/Training

The offeror shall:

a. Provide a description of, and the types and quantity initial spares required for the system.

The offeror shall describe the methodology to support the initial Spares package.

b. Provide a plan for implementing and achieving your two level maintenance concept and articulate how the system will be maintained in the field and at the OEM depot; identify the sub-systems and components that will be maintained at both levels of maintenance.

As part of this procurement, the contractor will be required to provide and deliver an

Operator’s Manual for the system that describes the operational capability of the system as well as field repair procedures.

c. Provide training plan for the system, based on the LOS-S SRD, and include the training requirements in the LOS-S system specification. The offeror shall be required to develop and deliver a Type-1 (train the trainer) training course for the system. The training plan shall include the type and quantity of training to be offered, necessary facilities, etc. The offeror shall provide and deliver a training manual for the LOS-S.

6.0 Volume III - Past Performance

6.1 General

Each Offeror shall submit a past performance volume with its proposal, containing past performance information using the PPI tool (See Attachment 2 to Section L for instructions). This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 50% or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance. For

Volume III contractors shall submit their Past Performance Information (PPI) using the PPI tool provided by the Government at Attachment 2 to Section L. Each Past Performance reference shall not exceed 5 pages. In addition, the Offeror shall submit a consent letter in accordance with the format contained in Attachment 3 to Section L executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter in accordance with the format contained in Attachment 4 to Section L, authorizing release to the Government of requested information on the Offeror's performance.

6.2 Early Proposal Information

Each offeror is requested to submit the information shown in Attachment 2 to Section L for each relevant contract on the 15th calendar day after RFP release no later than 12:00 p.m. Eastern

Standard Time. Failure to submit early past performance information will not result in offeror disqualification.

6.3 Relevant Contracts

Submit information in accordance with Attachment 2 to Section L: Past Performance Information on four (4) recent contracts you consider most relevant in demonstrating your ability to perform the proposed effort. Contract performance is expected to have been occurring within the past three years. Also include information on two (2) recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance.

For a description of the characteristics or aspects the Government will consider in determining recency /relevance, and assessing performance confidence see Section M, provision M002 -

Evaluation Factors, paragraph M002 c. - Past Performance Factor.

6.3.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Cost/Price factor used to evaluate the proposal.

6.3.2 Organizational Structure Change History

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

7.0 Volume III Cost/Price

7.1 General

7.1.1 Cost/Price Reasonableness, Realism and Completeness

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, The burden of proof for credibility of proposed costs/prices rests with the offeror.

7.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating

Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the contract work breakdown structure (CWBS).

7.1.3 Cost/Price Data

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

7.1.4 Cost or Pricing Information Requirements

In accordance with FAR 15.403-1(b) and 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 FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR

15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

7.1.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154033 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154035 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031

7.2 Volume Organization

The Cost/Price volume shall consist of the following sections:

7.2.1 SECTION 1 - Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards

(CAS) Disclosure Statement.

7.2.2 SECTION 2 - Cost or pricing information and supporting data, to include estimating methodology.

7.2.3 SECTION 3 - Other information such as Government Furnished Property/Government

Furnished Equipment (GFP/GFE), base support, long lead costs, termination costs, development/production schedule, inflation rate summary and explanation, and special tooling/test equipment. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Cost/Price volume, if any. Provide complete rationale for any exceptions.

7.3 Estimating Methodology

7.3.1 Estimating System

Provide a summary description of your standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering

Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A). Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

7.3.2 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

7.3.3 Accounting System

Indicate whether you have Government approval of your accounting system and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

7.3.4 Explanation of Estimating Methods Used

Explain the methodology used to estimate each cost element. As a minimum, provide the following information for each cost element. If a portion of the required information is not applicable for a particular cost element, so state.

7.3.4.1 Past Experience-Based Estimates

Where cost estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

7.3.4.2 Learning Curve Estimates

Where cost estimates are based upon learning/improvement curve applications, identify the specific area subject to learning, the curve hypothesis (unit or cumulative) and the slope of the curve as a percent. Also, identify the data used to develop the first unit cost and slope and explain how this data related to the current effort and how entry on the learning curve was attained (i.e., how the first unit cost was derived).

7.3.4.3 Engineering Labor Hours

If engineering labor hours have been estimated based upon other than past experience, provide detailed rationale on how they have been estimated.

7.3.4.4 Engineering Labor Hour Skill Mix

Explain how the proposed engineering labor hour skill mix has been derived and how the skill mix on this proposal compares with the overall plant skill mix. Explain why the cost element requires an average, higher, or lower than average skill mix, as applicable. If your normal estimating system uses a plant wide average for proposal purposes, so state.

7.3.4.5 Manufacturing Labor Hours

If manufacturing labor hours have been estimated based upon other than past experience and/or learning curve application, provide detailed rationale on how they have been estimated. If standards were used, identify and explain how they were derived and state whether or not they have been used on other programs. If other than normal procedures were used to estimate manufacturing hours, explain.

7.3.5 Management Reduction

If estimated costs to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major cost element summary. Also provide complete rationale for the reduction.

7.4 Other Information

7.4.1 Commonality with Other Programs

Any cost reductions made in your proposal that are attributed to commonality with other programs, company funded efforts, or capitalization of equipment must be supported with the following:

(a) Commonality - Identify the specific program(s) and why it is applicable.

- Address the cost allowability and allocability of this action per FAR and your CAS Disclosure Statement.

(b) Company-Funded

Efforts

- Identify the specific efforts, the planned start and end dates, the applicability to the current solicitation, the source of company funding and how you plan to account for or allocate these costs in accordance with generally accepted accounting principles, and your CAS Disclosure Statement, if applicable.

(c) Capital Equipment - Identify the specific item(s) capitalized and what other applications exist for the equipment, provide corporate approvals for each action, address the cost allowability and allocability of the action per the FAR and your CAS

Disclosure Statement.

7.4.2 Funding Profile

Submit then-year funding requirements by type of funds, by Government fiscal year, supported by monthly/quarterly projections of expenditures, commitments, and termination expense. Note that the funding schedules must be consistent with any imposed Government budgetary constraints.

7.4.3 Cost Summary by Cost Elements

For CLIN 0001 EMD, provide a cost summary by major cost elements by using the format provided at Attachment 9 to Section L (and separately identify costs for Other Direct Costs including travel costs).

Under Section J, attachment 1 to the model contract offerors are requested to complete the pricing matrix. The matrix is used to show quantity discounts (if applicable) for the Production

Options, Offerors should show prices for the full range of production (1 to 600). 150 units will form the basis for evaluation of priced production options.

7.4.3.1 Data Assertions

For CLINs 0005 and 0006, the offeror is directed to the CDRL exhibit for the government assertions for timing of CDRL delivery in relation to program phase, either EMD or Production.

The offeror is requested to provide CDRL pricing in accordance with this asserted breakdown.

Data deliverables considered under the Operations, Maintenance, Installation and Training

(OMIT) as reflected in the CDRL table of contents should be prepared to provide the government unlimited rights to this data.

8.0 Volume V - Contract Documentation

8.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the

Model Contract, and Sections A through K. This includes:

8.1.1 Section A - Solicitation/Contract Form

Completion of blocks 12 - 16 and signature and date for blocks 17 and 18 of the SF33 for the basic contract. 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 and should be provided without any punched holes.

8.1.2 Section B - Supplies or Services and Costs/Prices

The offeror shall provide completed pricing information in Section B of the model contract for up to six (6) prototypes under CLIN 0001, option pricing for 600 production assets under CLINs

0002, training under CLIN 0003 sustainment under CLIN 0004, EMD Data under CLIN 0005, Production Data under CLIN 0006 and travel under CLIN 0007. Data will be separately priced for the EMD and Production effort.

8.1.3 Section C - Description/Statement of Work and System Specification

A Statement of Work (SOW) shall be delivered in response to the Statements of Objective

(SOO) for the contract which are included as Attachment 6 to Section L of this Request for

Proposal.

8.1.4 Section E - Inspection and Acceptance

The offeror shall propose inspection and acceptance terms.

8.1.5 Section F - Deliveries or Performance

The offeror shall propose the intended delivery schedule by completing the blanks in Section F of the model contract for CLIN 0001 (Prototypes), CLIN 0002 (Production Options). These dates may be shown in WARO (weeks after receipt of order) or MARO (months after receipt of order) format or the contractor can use the format shown below:

"Xx systems in xxx weeks/months, with xxx additional systems every week/month for xxx weeks/months".

An example might be: 10 systems in 4 months, with 5 additional systems every week for 4 weeks. (This would be a delivery schedule for 30 systems, with final delivery 5 months after order)

8.1.6 Section G - Contract Administrative Data

The required Contract Administration data is in Section G of the model contract.

8.1.7 Section H - Special Contract Requirements

H001 OPTIONS (MAY 1997)

The Government reserves the right to exercise the following option(s) subject to the stated conditions. In the event an option is exercised, the affected sections of the contract, e.g., Section B, Section F, Section G, etc., will be modified as appropriate.

LOS-S

CLIN 0002AA - FY14 Production

CLIN 0002AB - FY15 Production

CLIN 0002AC - FY16 Production

CLIN 0002AD - FY17 Production

CLIN 0003 - Training

SUSTAINMENT

CLIN 0004AA - Interim Contractor Support

CLIN 0006 – Data (Production Non-OMIT Data)

CLIN 0007 – Data (Production OMIT Data)

H014 IMPLEMENTATION OF PATENT RIGHTS CLAUSE (NOV 2011)

a. Interim or final Invention Reports 1) listing subject invention(s) and stating that all subject inventions have been disclosed, or 2) stating that there are no such inventions, shall be sent to both the Administrative Contracting Officer at the address located on the face of the contract, and to the Contracting Officer/Patent Administrator at det1.afrl.pk.patents@wpafb.af.mil, with a courtesy copy (cc:) to the government Program

Manager/Project Engineer, within the timeframes specified in the clause. Please include in the subject line of the e-mail the contract number followed by the words "Invention Reporting."

Also include in the body of the e-mail the names of the Government Project Engineer/Program

Manager and his/her office symbol. Contractors are highly encouraged to use DD Form 882, Report of Invention and Subcontracts to submit these reports. The DD Form 882 may also be used for the notification of an award of any subcontract(s) for experimental, developmental or research work which contain a "Patent Rights" clause.

b. All other notifications (e.g., disclosure of each subject invention to the Contracting

Officer within 2 months after the inventor discloses it) shall also be sent to the e-mail address above, with a courtesy copy (cc:) to the government Program Manager/Project Engineer.

c. This provision also constitutes the request for the following information for any subject invention for which the contractor has retained ownership, 1) the filing date, 2) serial number and title, 3) a copy of the patent application and 4) patent number and issue date.

Submittal shall be to the Contracting Officer/Patent Administrator e-mail address listed above, with a courtesy copy (cc:) to the government Program Manager/Project Engineer.

H025 INCORPORATION OF SECTION K (OCT 1998)

Section K of the solicitation is hereby incorporated by reference

ASC/HM014 DELIVERY AND LICENSE RIGHTS FOR TECHNICAL DATA AND

COMPUTER SOFTWARE NECESSARY FOR ORGANIZATIONAL AND DEPOT-

LEVEL MAINTENANCE AND TRAINING SYSTEMS (MAY 2011)

a. Definitions. As used in this special contract requirement and associated CLINs

1. The term "depot-level maintenance" as used in this contract-

A. Includes, but is not limited to-

(i) Installation, inspection, localization, isolation, disassembly, interchange, repair, reassembly, alignment, checkout; and

(ii) Maintenance performed on material requiring repair, major overhaul, or complete rebuild of parts, assemblies, subassemblies, and end items, and including modification, testing, and reclamation.

B. Does not include the manufacture of new items.

2. The term "OMIT Data" as used in this contract is defined as all technical data

(including computer software documentation), development tools, graphics, and computer software necessary for operation, maintenance, installation, or training purposes (other than detailed manufacturing) pertaining to the LOS-S system and equipment associated with its life cycle support sustainment. OMIT data includes all technical data required to accomplish Organizational, Intermediate, and Depot levels of maintenance, including Air Force sustainment of the technical data itself. All data to be delivered under CLIN 0007 are OMIT data.

3. Other terms used in this special contract requirement defined in the following clauses have the same meaning as set forth in those clauses:

A. DFARS 252.227-7013;

B. DFARS 252.227-7014; and

C. DFARS 252.227-7015.

b. Delivery Requirements. Pursuant to CLINs 0006 and 0007, the contractor shall deliver all technical data and computer software necessary for organizational and depot level maintenance of the LOS-S equipment.

1. General. The contractor shall provide the technical data, development tools, and computer software having the characteristics (e.g., content, format, and delivery medium) necessary for organizational and depot-level maintenance and Type 1 training as determined and required by the Government. The Government requirements for such technical data or computer software include-

A. No less information or detail than industry standards, nor less than the contractor typically requires to perform such maintenance or training activities;

and

B. Additional information or detail necessary for military purposes related to organizational and depot-level maintenance or training systems.

2. Depot-Level Maintenance Technical Data and Computer Software. Technical data and computer software described under Exhibit A021 (Contract Data Requirements List

(CDRL) OMIT) must comprise a complete package of all technical data and computer software necessary for the Government to perform depot level maintenance for the entire

LOS-S system and equipment, including all components without exception. This includes technical data and computer software necessary for installation and deinstallation, and disassembly and reassembly, at the lowest practicable segregable level that does not require detailed manufacturing or process information.

c. License Rights. Pursuant to the contract clauses and regulations governing rights in technical data and computer software (e.g., DFARS Subparts 227.71 and 227.72, 227.7202, 252.227-7013, 252.227-7014, and 252.227-7015), the Government is granted unlimited rights in OMIT data.

d. Technical Data and Computer Software of Subcontractors and Suppliers. The contractor's obligations in this special contract requirement shall apply to all technical data and computer software, including all technical data or computer software developed, delivered, or otherwise provided by subcontractors or suppliers at any tier, and regardless of whether the computer software or technical data is or relates to commercial items or noncommercial items. The contractor shall include these requirements in its subcontracts or other contractual or legal instruments with its subcontractors or suppliers at any tier.

e. Validation of Asserted Restrictions and Restrictive Markings. Nothing in this special contract requirement limits or otherwise affects the parties' rights or obligations specified in DFARS

252.227-7019 or DFARS 252.227-7037.

ASC/HM037 IDENTIFICATION AND ASSERTION OF RESTRICTIONS ON

TECHNICAL DATA AND COMPUTER SOFTWARE (MAY 2011)

a. Definitions. Terms used in this Special Contract Requirement (SCR) that are defined in the following clauses and SCR have the same meaning as set forth in those clauses:

1. DFARS 252.227-7013;

2. DFARS 252.227-7014;

3. DFARS 252.227-7015;

4. DFARS 252.227-7017; or

5. ASC/WISV HM014 Delivery And License Rights For Technical Data And Computer

Software Necessary For Organizational And Depot-Level Maintenance And Training

Systems (Jul 2011)

b. Identification and Assertion of Restrictions. The Contractor shall not deliver or otherwise provide to the Government any technical data or computer software with restrictive markings (or otherwise subject to restrictions on access, use, modification, reproduction, release, performance, display, or disclosure) unless the technical data or computer software has been identified in accordance with the…