Appendix_D_-Section_L-_ITO.pdf

SECTION L - INSTRUCTIONS TO OFFERORS (ITO)

APPENDIX D

Part IV – Representations and Instructions

SECTION L

INSTRUCTIONS TO OFFERORS

1.0 Program Structure and Objective

1.1 The purpose of this award is to award a single contract for the B-1 Self-Contained Attitude Indicator (SCAI) program. SCAI will primarily include the installation design and the production of the Electronic Standby Instrument System (ESIS).

The government plans to award a single Indefinite Delivery/Indefinite Quantity contract (ID/IQ) as a result of this solicitation. Award will be made on the basis of “best value” and may utilize tradeoff source selection procedures.

If used, the tradeoff will be between technical risk, past performance, and price among those Offerors who have been determined technically acceptable. Award will be made to the Offeror that provides the “best value” to the Government over the entire period of performance. The contract will consist of a four-year basic ordering period, which includes an estimated one-year for Engineering and Manufacturing Design (EMD) and three years for Production ordering for kits and spares. The Government intends to award without discussions but reserves the right to conduct discussions if necessary.

1.2 Initial funding will be obligated for the Engineering Manufacture Design (EMD) Contract Line Item Numbers (CLINs) for the development and design period and will satisfy the minimum contract guarantee.

1.3 To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein.

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. Failure to meet a requirement may result in an offer being ineligible for award. The response shall consist of four (4) separate volumes; Volume I –Technical Proposal, Volume II – Past Performance Information; Volume III –Price Proposal; and Volume IV – Contract Documentation.

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

2.0 General Instructions

2.1 This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with (IAW) these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), System Requirements Document (SRD) and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation or exclusion from the competition.

2.2 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the offeror’s proposal.

2.3 Text of proposals shall be submitted in English. Proposals received in languages other than English shall be rejected.

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

2.5 The proposal acceptance period is specified in Section A of the Request for Proposal (RFP) which will become the model contract/solicitation. The Offeror shall make a clear statement in Volume IV of the proposal documentation that the proposal is valid until the date specified in Section A of the solicitation.

1 (of 29)

2.6 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) 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.

3.2 Debriefings - The CO will promptly notify Offerors of any decision to exclude them from the competitive range, where upon they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing. The CO will notify unsuccessful Offerors IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable

3.3 Discrepancies - If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

3.4 Electronic Reference Documents - All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fbo.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 Oral Presentation-Oral presentations will not be utilized.

3.6 Communications - Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Additionally, source selection information may be transmitted via facsimile (encrypted when possible), U.S. Postal (or like service) delivery, and/or oral with telephonic or face-to-face meetings.

3.7 Amendments to Solicitation - In the event this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment(s) by signing and returning the amendments with their proposal, thus providing confirmation of receipt and understanding upon submission of the Offeror’s proposal.

3.8 Submission, Modification, Revision, and Withdrawal of Proposals - Proposals and modifications to proposals shall be submitted in sealed envelopes or packages in paper media and electronic media (either CD or DVD) addressed to the CO at the address shown in Section A of the RFP/model contract/solicitation, and showing the time and date specified for receipt, the solicitation number, and the name and address of the Offeror.

3.9 Organization/Number of Copies/Page Limits

3.9.1 The title Page of each volume must show solicitation number, name, address, and telephone and facsimile numbers of the offeror and electronic e-mail address if available.

3.9.2 A Team List of the offeror’s primary Point of Contacts shall be submitted in each volume using the format shown in Attachment 2.0 of the ITO.

2 (of 29) http://www.fbo.gov/

3.9.3 The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 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 and with the number of copies as specified in Table 1. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 1 Proposal Organization

Volume

ITO

Paragraph Number

Volume Title

Hard Copies/

Disk Copies

Page Limit

I 4 Technical 4/1

3.9.1 Title Page (Not included in 95 page limit) 1

3.9.2 Team List (see Attach 2.0)(Not included in 85 page

limit)

3.9.8 Table of Contents Unlimited

3.9.8 List of Tables and Figures Unlimited

3.9.9 Glossary of Abbreviations and Acronyms Unlimited

4.1

4.2

4.3 4.4 4-5

Instrument Panel Structure (Subfactor 1) System Requirement Document (SRD) Requirements (Subfactor 2) Installation Design (Subfactor 3) Program Schedule (Subfactor 4) Small Business Participation (Subfactor 5)

4.6 Technical Risk Included with

the 95 pgs of technical

II 5 Past Performance 4/1 Unlimited

3.9.1 Title Page 1

3.9.2 Team List (See Attach 2.0) 5

5.1.1 Present/Past Performance Information Sheets (PPIS)

(See Attach 1.1)

5.1.2 Consent Letter (See Attach 1.4) Unlimited

5.1.2 Client Authorization Letters (See Attach 1.5) Unlimited

5.2 Present/Past Performance Questionnaires (See

Attach 1.2) Tab Only

5.3.1 Relevant Contract Narrative Max 5 pages

per contract

5.3.3 Roadmap 2

III 6 Price Volume 2/2 Unlimited

3.9.1 Title Page Unlimited

63.9.2 Table of Contents Unlimited

3.9.9 Glossary of Abbreviations & Acronyms Unlimited

6.15 Section 1 Unlimited

6.15 Section 2 Unlimited

6.15 Section 3 Unlimited

6.16 Other Documentation Unlimited

IV 7 Contract Documentation 2/1 Unlimited

3.9.1 Title Page (SF1449) 1

3 (of 29)

3.9.2 Team List (see Attach 2.0) 5

3.9.8 Table of Contents Unlimited

3.9.8 List of Tables and Figures Unlimited

3.9.9 Glossary of Abbreviations and Acronyms Unlimited

7.3.4 /Company/Division Address, Identifying Codes and

Applicable Designations Unlimited

7.1 Model Contract (Sections A-J) N/A

7.1.4 Representations and Certifications (Section K) N/A

7.3.1-7.3.3 Contact Information Unlimited

7.3.5 Attachments to the Model Contract Unlimited

7.3.6 Small Business Subcontracting Plan Unlimited

3.9.4 File Names - Offerors shall submit volumes with the following file names: Volume 1 – Technical.doc, Volume II – Past Perf.doc, Volume III –Price.doc, and Volume IV – Contract.doc.

3.9.5. 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 and (for paper copies) will be returned to the Offeror as soon as practicable. Page limitations may also be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited. Page limits apply to both hard and electronic copies.

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

3.9.7 Cross Referencing - Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for 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 when its use would conserve space without impairing clarity.

3.9.8 Indexing - Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Also, in the technical volume, identify which evaluation factor is being addressed within the tab. Include an indexed list of Tables and Figures.

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

3.9.10 Requirements Correlation Matrix -- The Offeror shall complete the Requirements Correlation Matrix provided in Table 2 that will indicate the corresponding proposal paragraph in each volume which addresses the referenced item.

Reference SOW SRD Sections

L&M CLIN CDRL Proposal Vol

& Para Technical

Technical Risk

Past Performance

4 (of 29)

Price

3.10 Page Size and Format

3.10.1 A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Page line spacing shall be 1.5 lines. Except for the reproduced sections of the solicitation document, the text size shall be no less than Arial 12 points. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notice (ENs). These limitations shall apply to both electronic and hard copy proposals.

3.10.2 Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. The following limitation only applies to the Technical Volume. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8-pt. These limitations shall apply to both electronic and hard copy proposals. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation. These limitations shall apply to both electronic and hard copy proposals.

3.11 Binding and Labeling - Each volume of the proposal should be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, 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 unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

3.12 Electronic Offers - The content and page size of electronic copies must be identical to the hard copies. When discrepancies exist between the written hard copies and those provided in electronic format, the written hard copies will take precedence in all cases. For electronic copies, indicate on each Compact Disc Read Only Memory (CD- ROM) the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The offeror shall submit volumes I through IV in electronic format. Each volume shall be submitted on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2007 or 2010, MS Excel 2007 or 2010, MS-Project 2007 or 2010, and MS-Power Point 2007 or 2010, or Microsoft Office XP as applicable.

3.13 Distribution - The "original" proposal shall be clearly identified. Proposals shall be addressed to the Contracting Officer and mailed to:

DEPARTMENT OF THE AIR FORCE

OFFICE: AFLCMC/WWKKB ATTN: Ms. Maisie Raju 3001 Staff Dr, STE 2AG 85B Tinker AFB OK 73145-3020 Telephone: 405-739-2881 Email: Maisie.Raju@tinker.af.mil

5 (of 29) mailto:Maisie.Raju@tinker.af.mil

4.0 Volume I – Technical Proposal (Factor 1-Technical & Factor 2-Technical Risk)

The Technical Volume shall include all information related to Factor 1 Technical and Factor 2 Technical Risk.

Factor 1 Technical and Factor 2 Technical Risk 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Format and Specific Content

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

Volume Organization The Technical Volume shall be organized according to the following general outline as provided in Table 1:

4.1 Subfactor 1: Instrument panel

The Offeror shall provide an approach for instrument panel installation that shall include

a. Proposed dimensions of the “as installed“ modification

b. Dimensional analysis that proves why the proposed solution shall not require any modification to the existing instrument panel structure (i.e. mounting hole enlargement, modification of internal structure such as cooling ducts, legacy wire harness routing, movement/re-location of other instruments, etc) IAW SRD

3.6.6 and SOW 3.1.4.

4.2 Subfactor 2: System Requirement Document (SRD) Requirements The Offeror shall provide data to demonstrate the proposed unit shall meet all requirements established in the SCAI SRD or shall present a technically acceptable mitigation plan to bring the unit into compliance. If the proposed unit meets all SRD requirements without mitigation, the Offeror must address elements a and c. If the proposed unit does not meet all SRD requirements without mitigation, the Offeror must address elements b and c.

a. The Offeror shall clearly identify how the proposed unit meets all the requirements specified in the SRD without mitigation.

b. The Offeror’s proposed unit does not meet all requirements identified in the SRD, the Offer shall:

1. Clearly identify and provide rationale describing what SRD requirements are met by the proposed unit.

2. Clearly identify all SRD requirements that are not met by the proposed unit.

3. For those requirements identified in 2 above, clearly quantify the difference(s) between the SRD requirements and the proposed unit.

4. For those requirements identified in 2 above, clearly identify what mitigation actions will be pursued during the execution of this effort to bring the proposed unit into full compliance with the requirements identified in the SRD.

c. The Offeror shall clearly and concisely identify that the proposed unit has either completed development and has been “flight qualified” through test and demo in a flight environment similar to that of a B-1B, or has demonstrated functional performance in an actual system; that is, “flight proven” through successful operation. SOW 3.1.3

NOTE: In cases where the Offeror cites a MIL-STD based requirement compliance by meeting that requirement through a commercial or FAA standard, the Offeror shall clearly demonstrate the commercial or FAA standard’s equivalence with MIL-STDs referenced in the SRD.

4.3 Subfactor 3: Installation Design

6 (of 29)

The Offeror shall provide a proposed installation design such that the modification can be installed on a B-1 aircraft by Air Force personnel within 24 man-hours IAW SOW 3.1.10. The proposed installation design must address the following:

• Proposed aircraft locations where new equipment will be installed or changed, an installation concept, and an estimate of man-hours required for each installation procedure.

• Estimated items that require removal for installation or access, and an estimate of man-hours required for each operation.

• Estimated aircraft wiring changes (modification, deletion, or new installation), and provide an estimate of man-hours required for each installation procedure.

• Estimate of post-installation procedures that will be necessary to operationally check the installed system; this should include any disturbed systems checks driven by equipment removal for installation access.

4.4 Subfactor 4: Program Schedule

The Offeror shall provide a notional schedule that is representative of the contents required by DID XXXX as identified in SOW paragraph 3.2. The approach must identify the key tasks with scheduled dates that must be completed to meet the required schedule.

4.5 Subfactor 5: Small Business Participation

The Offeror shall provide an approach to describe the ability to establish and maintain subcontract arrangements and relationships, identifying the flow down of system requirements, activities, and performance which addresses the requirements of TAFB H-0002, Small Business Requirements. This is in addition to the Small Business Subcontracting Plan (FAR 52.219-9).

4.6 Technical Risk (Factor 2)

The offeror shall address Technical Risk associated with those aspects of the offeror’s proposed technical approach for Factor 1, Technical, Subfactor 2, SRD Requirements, Subfactor 3, Installation Design, and Subfactor 4, Program Schedule, all elements. The Offeror shall address all Technical Risk that the offeror considers to have potential for disruption to schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. The offeror shall provide the rationale for each risk, including quantitative estimates of the impacts on cost, schedule, and performance. The offeror shall describe the impact of each identified risk in terms of the risk’s potential to interfere with or prevent the successful accomplishment of contract requirements (for example, SOW requirements), whether or not those requirements are identified as subfactors. For each risk the offeror identifies, the offeror shall outline how that risk is eliminated or reduce to an acceptable level in the proposed mitigation plan.

5.0. VOLUME II - Past Performance (Factor 3)

5.1. General

5.1.1 Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 1.1 of the ITO. This information is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. 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.

5.1.2. The Offeror shall submit a consent letter (Attachment 1.4) 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 (Attachment 1.5) authorizing release to the Government of requested information on the Offeror’s performance.

5.2. Early Proposal Information - Each Offeror is requested to submit Volume II - Past Performance for each relevant contract fifteen (15) calendar days prior to the solicitation closing date. Failure to submit early proposal information will not result in Offeror disqualification.

7 (of 29)

As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (Attachment 1.2) and e-mail it and the Performance Questionnaire Letter (Attachment 1.3) to all points of contacts (POCs) the Offeror has listed in the Past Performance Information Sheets (Attachment 1.1). The POCs will complete the questionnaires and forward them by FAX, directly to the CO. Fax copies to 405-739-2817(Attn: Maisie Raju) or e-mail maisie.raju@tinker.af.mil. RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE OFFEROR. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires.

5.3. Recent and Relevant Contracts

5.3.1 Request each PPIS not exceed a target of 8 pages, although more or less may be submitted if necessary and relevant to the SCAI effort. Request each offeror submit up to three (3) PPIS forms for the prime Contractor and up to three (3) for each significant subcontractor/teaming partner (any vendor performing more than 10% of the total requirements) you consider most relevant in demonstrating their ability to perform the proposed effort. The target of 8 pages for PPIS does not include the allowable 5 pages for ITO Paragraph Number 5.3.1, Relevant Contract Narrative. NOTE: The requested number of PPIS forms for the prime and subcontractors are preferences, and not requirements. Offerors who submit less than the preferred number of PPIS forms are not automatically assigned an “Unknown Confidence” rating. Fewer numbers may be acceptable if the Government determines there is sufficient information to determine a confidence rating. Please only submit information on subcontractors and teaming partners performing key or critical portions of the SCAI effort. There is no limit on the number of PPIS forms allowed per team; however, offerors are requested to limit responses to those efforts necessary for evaluation and relevant to the SCAI effort.

5.3.2 Specific Content

Offerors shall provide a narrative explaining 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 shall clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required.

Categorize the relevance information into the specific technical subfactors and Price assessment used to evaluate the proposal.

5.3.3 Organizational Structure Change History

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

6.0 Volume III – Price Proposal

6.1 General Instruction. In the price volume, the Offeror shall provide the following information in addition to the Pricing Matrix included in the solicitation. These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

8 (of 29) mailto:Eneshal.Borders-Jones@tinker.af.mil

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

6.1.2 The SCAI Estimated Quantities (EQs) given in the Pricing Matrix attachment represent estimates of the SCAI LRU to be completed during specific periods of performance. All such quantities will be used for evaluation purposes only and DO NOT obligate the Government nor guarantee such quantities or prices will be purchased during the contract performance period.

6.1.3 Rounding

All proposed dollar amounts shall be rounded to the nearest dollar, except hourly labor rates (fully loaded or burdened) shall be rounded to the nearest cent. The Pricing Matrix format provides for decimal places that must be in accordance with this required decimal format. If any pricing proposal deviates from this format, the Government will apply the specified format to determine the extended pricing and TEP.

6.1.4 Pricing Information Requirements

FAR Part 15 applies regarding price analysis as a basis for determining reasonable and balanced pricing. In accordance with FAR 15.404-1(b)(2)(i), normally adequate price competition establishes price reasonableness.

However, IAW FAR 15.304(a)(1), cost realism analysis is required for Cost Reimbursement CLINs.

6.2 Accounting System

Provide a summary of your accounting system or methods. Provide your current Cost Accounting System (CAS) Disclosure Statement and discuss any pending revisions applicable to this solicitation. Indicate whether you have Government (DCMA) 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.

6.3 Estimating System

Provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government (DCMA) approval of your system and if so, provide evidence of such approval.

6.4 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 (DCMA) approval of your system and if so, provide evidence of such approval.

6.5 Explanation of Specific Estimating Techniques and Methods Explain the methodology used to estimate prices in the development of your proposed pricing. A variety of estimating techniques and methods are acceptable as a basis of estimate in proposed pricing. When responding to the Price volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating techniques consistent with the Offeror’s Disclosure Statement as appropriate and if required based on current contracts per Defense Contract Audit Agency (DCAA) policy and guidance. Acceptable contemporary estimating methods can include Cost-to-cost and Cost-to-non-cost Estimating Relationships (CERs), commercially available parametric price models, in-house developed parametric price models, commercial catalogs, etc.

6.6 Past Experience Basis of Estimate

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

6.7 Cost Assumptions Used in Development of Proposed Pricing

9 (of 29)

Information to support reasonableness of proposed pricing is required including supporting data and estimating methodology to support price reasonableness. All cost assumptions (including indirect rates for the Offeror’s appropriate accounting period, volume or location discounts), scope limitations and/or qualifications of the pricing proposal shall be addressed and explained.

6.8 Cost Realism, Price Reasonableness and Balance

Offeror’s pricing proposal will be evaluated for price realism for CLIN 0001 only. Offeror’s pricing proposal will be evaluated for reasonableness and balance for all CLINs. Unrealistic prices, initially or subsequently, may be grounds for eliminating a proposal from the competitive range on the basis the Offeror does not understand the requirement. Unreasonable proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition on the basis that the Offeror does not understand the requirement. Additionally, unbalanced pricing may pose an unacceptable risk to the Government and may render an Offeror’s proposal ineligible for award.

Offers should be sufficiently detailed to demonstrate how their proposed costs are realistic, and how all proposed prices are reasonable and balanced. The burden of proof for credibility of proposed prices rests with the Offeror.

6.8.1 Cost Realism

Realism is based on the proposed costs being realistic for the work to be performed, reflecting a clear understanding of the requirements, and are consistent with the various elements of the offeror’s technical proposal. Proposed costs will be reviewed and evaluated to determine the probable cost of performance. To assist in the cost realism evaluation, the Offerors are required to provide the other than cost or pricing data information in the CPFF Detailed Cost Sheet attached to the Pricing Matrix and provide the supporting explanation/rationale in the Pricing Volume as outlined in this ITO.

6.8.2 Price Reasonableness

Reasonableness is based on an overall evaluated proposed price and must represent a price to the Government a prudent person would pay in the conduct of competitive business. Normally, price reasonableness is established through adequate price competition, but may also be determined through proposal analysis techniques. To assist in the price reasonableness assessment the Offeror is required to provide supporting explanation/rationale as outlined in this ITO.

6.8.3 Unbalanced Pricing

The Offeror is cautioned against submitting an offer that exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable prices. Unbalanced pricing exists when, despite an acceptable Total Evaluated Price (TEP), the price of one or more contract line items (CLINs) is significantly over or understated as indicated by application of price analysis techniques such that there is reasonable doubt the offer would result in the lowest overall price to the Government, even though it is the lowest TEP. Also, an offer could be so grossly unbalanced that acceptance of the offer would be tantamount to allowing an advanced payment. Balanced pricing is determined with respect to separately priced CLINs or SubCLINs, or significant unexplained variance in pricing from year to year.

To assist the determination of balanced pricing, Offerors shall complete the attached Pricing Matrix. Completion of the Pricing Matrix allows efficient comparison of proposed pricing with the SOW requirements. If what appears to be unbalanced pricing is due to sound rationale associated with, for example, the proposal’s technical approach, Offerors shall provide an explanation to account for any pricing that appears unbalanced.

6.8.4 Cost Plus Fixed Fee – CLINs 0001 and 0002 are Cost Plus Fixed Fee effort for the Engineering Manufacturing and Design effort. CLIN 0001 is for Target Cost and CLIN 0002 is Fixed Fee, which is limited to 10%. Offerors are required to provide the cost information in CPFF Detailed Cost Sheet, which is attached to the Pricing Matrix. In addition, the Pricing Volume must include the following for these CLINs:

Explain the major tasks to be accomplished. If non-recurring and recurring activities are contained in the same element, provide separate descriptions. Describe the functional labor groups included in this effort.

Describe material or subcontract dollars, including any applicable quantity information. For subcontracted costs, indicate whether the bid is a firm negotiated price, a budgetary quote, a Not to Exceed (NTE), or a Rough Order of Magnitude (ROM), etc… Show when the bid price was established and the date the quote remains valid.

10 (of 29)

Describe the estimated manpower build up to include the various functional labor categories and labor mixes, estimated hours per category and explanation/rationale for the estimated hours.

Describe basis of estimate/rationale for fringe, overheads, G&A, etc… to include use of any Forward Pricing Rate Agreements.

6.8.5 Firm Fixed Price -- CLINs 0004 and CLINs 0005 are Firm Fixed Price for kits and spares. Offerors are required to provide the cost information in Attachment 1 of the Pricing Matrix. In addition, the pricing volume must include the following for these CLINs:

Describe the basis of estimate/rationale for the proposed unit price for the kit and spares to include a breakdown of the material to be provided.

Describe material or subcontract dollars, including any applicable quantity information. For subcontracted costs, indicate whether the bid is a firm negotiated price, a budgetary quote, a Not to Exceed (NTE), or a Rough Order of Magnitude (ROM), etc… Show when the bid price was established and the date the quote remains valid.

6.8.6 Hourly Labor Rate for O&A

Offerors are required to propose a fully burdened labor rate for over and above tasks in accordance with SOW

3.1.12. Minimal O&A is anticipated for repairs required from damage during installation or other non-warranty repairs. The Pricing Matrix includes estimated hours that will be multiplied by the O&A labor rate and included in the evaluation of the Total Evaluated Price. The Offeror must provide an explanation of the labor rate to include rationale for development. The rationale must include details describing the labor categories, all fringe benefits, indirect costs and fee used to develop the wrap rate.

6.9 Subcontractor and Vendor Pricing

Include a detailed explanation of your determination of proposed subcontractor or vendor pricing considered fair and reasonable. As prime contractor, documentation is required to demonstrate subcontractor/vendor commercial quotes are considered fair and reasonable. Include a detailed description of your process for evaluating subcontractor/vendor pricing in your determination of fair and reasonable pricing.

Offerors are required to provide an explanation of how indirect costs, General and Administrative (G&A) and profit are applied to subcontractor proposal pricing and whether all subcontractor costs, including indirect rates, G&A and profit are included as a total subcontract amount (i.e., prime treats all subcontractor/ vendor costs as their direct cost to which the prime applies their own indirect costs, G&A, cost of money (COM) and profit). Also, include any explanation of your determination to utilize “make” or “buy” subcontractor or vendor parts.

6.10 Contractor Furnished Property/Equipment/Tooling (CFP/CFE/CFT) If property, equipment and/or tooling is necessary to meet the requirement, it is the Contractor’s responsibility to obtain that property, equipment and/or tooling.

Verify your understanding and intention to provide property, material, equipment and tooling. Also separately list all your assumptions regarding facilities, equipment, parts and manpower provided by contractors (prime contractor, subcontractors and/or vendors).

6.11 Proposed Price Reduction per Corporate/Management Decision If estimated prices to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major pricing element (e.g., material, labor, overhead, etc.). Also provide complete rationale for the reduction. Provide the estimated dollar and percentage of the reduction, explaining how such reductions are ensured not to increase performance risk to the Government.

6.12 Submission of Price Matrix

Submit the fully completed Pricing Matrix electronically in support of the proposed TEP. Any price model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal in Volume III Price proposal. Any deviation must be fully explained. All unit prices for each CLIN or SubCLIN which requires proposed pricing must be provided. The

11 (of 29)

Pricing Matrix shall remain locked without any revisions, adjustments or tampering by Offerors. Price models submitted must comply with the following format requirements:

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

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

6.13 Probable Subcontractors

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

6.14 Government Field Support Agencies

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

6.15 Volume Organization

The Price volume shall consist of the following sections:

SECTION 1 Include your rationale in response to the following paragraphs in Section1:

6.2 – Accounting System

6.3 – Estimating System

6.4 – Purchasing System

6.5 – Explanation of Specific Estimating Techniques and Methods

6.6 – Past Experience Basis of Estimate

6.7 – Cost Assumptions Used in Development of Proposed Pricing

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

6.12 – Submission of Pricing Matrix

6.8 -- Cost Realism, Price Reasonableness and Balance

6.8.1 – Cost Realism

6.8.2 – Price Reasonableness

6.8.3 – Balance

6.8.4 – Cost-Plus Fixed Fee

6.8.5 – Firm Fixed Price

6.8.6 – Hourly Labor Rate for Over & Above

SECTION 3 Include your response to the following paragraphs in Section 3:

6.9 – Subcontractor and Vendor Pricing

6.10 – Contractor Furnished Property/Equipment/Tooling

6.11 – Proposed Price Reduction per Corporate/Management Decision

6.13 – Probable Subcontractors

6.14 – Government Field Support Agencies

6.13. Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in Section 3. Pursuant to paragraph 6.1.12 above, Offerors are requested to address any proposed prices which reflect a business decision to offer prices at or below cost.

7.0 VOLUME IV – CONTRACT DOCUMENTATION

7.1 Request for Proposal (RFP) (future 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 RFP, which will become the Model Contract, and Sections A through K (omitting Sections L & M), plus Pricing Matrix,.

7.1.1. Solicitation/Contract Form (Section A)

12 (of 29)

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF1447. Signature by the offeror on the SF1447 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.

7.1.2. Supplies or Services and Costs/Prices (Section B)

Completed pricing information in Pricing Matrix shall be provided as part of the RFP / model contract. Offerors are not required to enter unit prices in Section B. The Pricing Matrix will be used to input prices in Section B of the resultant contract.

7.1.3. Contract Clauses (Section I)

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

7.1.4. Representations, Certifications, and other Statements of Offerors (Section K ) The Offeror shall complete the annual representations and certification electronically via the ORCA website at http://orca.bpn.gov. After reviewing the ORCA database information, the Offeror verifies by submission of this offer that the representation and certifications currently posted electronically at FAR 52.204-8, Annual Representations and Certifications are correct.

7.2. Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and mission requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Should the Offeror make any exceptions in developing / submitting their proposal, they must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. Any proposed deviation or exception that does not meet, or impacts, minimum requirements may make the Offeror’s proposal ineligible for award. This information shall be provided in the format and content of Table 6.

Table 6 Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOO, SOW, SPEC, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

7.3. Other Information Required

7.3.1 Ombudsman

An Ombudsman has been appointed to hear concerns from Offerors or potential Offerors during the proposal development phase of this acquisition. The Ombudsman for this acquisition is AFSC/PZC, located at Tinker AFB.

This does not diminish the authority of the program director or CO, but communicates Offeror concerns, issues, disagreements and recommendations to the appropriate Government personnel. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process; interested parties are invited to call AFSC/PZC at 405- 736-3273.

7.3.2. Authorized Offeror Personnel

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

7.3.3 Government Offices

13 (of 29)

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

7.3.4. Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

7.3.5 Attachments to the RFP / Model Contract

The Offeror shall provide as attachments to the RFP / model contract the documents listed in Section J of the RFP except for Sections L and M.

7.3.6 Small Business Subcontracting Plan

If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 and Special Clauses that also identifies and specifies the extent of Offeror’s commitment to the participation of small businesses (SB), whether as joint venture members, teaming arrangements partners, mentor/protégé, or subcontractors. If applicable, submit a copy of your approved Master Plan. The subcontracting plan must detail the roles the small businesses will fulfill.