Att 18 - F-15 TDAS Section L.pdf

FA8621-12-R-6259

Attachment 18

6 Feb 2012

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L-III - ADDITIONAL INSTRUCTIONS TO THE OFFEROR:

1. Program Description.

The efforts anticipated under the resultant contract from this solicitation are for the sustainment and ongoing support of the F-15 Training Device Acquisition and Support (TDAS) program.

This full and open acquisition is a follow-on from a competitively awarded contract to the incumbent in 2002. The successful offeror under this acquisition will be required to provide

Contractor Logistics Support (CLS) for the government-furnished hardware comprised of the 31 training devices and the Training System Support Center (TSSC). The offeror will also be required to provide software/hardware modifications via the TSSC to keep the fielded devices concurrent with the F-15 aircraft and to resolve obsolescence issues that may occur during the contract period of performance. See Attachment 1, Performance Work Statement (PWS) for further details.

2. General Instructions.

a. Introduction. This section of the solicitation, also known as the Instructions to

Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. Proposals must be submitted with all data and information requested herein. The offer shall be compliant with the requirements as stated in the

F-15 TDAS PWS. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation or removal from award consideration. Offers (or amendments to offers, if required) received by the Government after the specified due date and time may not be considered in accordance with Federal Acquisition Regulation (FAR) 15.208(b)(1).

(1) All required elements of an offeror’s proposal must be submitted to the

Procuring Contracting Officer (PCO) at the address specified in Paragraph 2.a.(3) no later than

1500 (Eastern Daylight Time) on 9 Apr 2012.

(2) The Government requests that Volume III – Past Performance Information be submitted early, no later than 1500 (Eastern Daylight Time) on 26 Mar 2012 to the address specified in Paragraph 2.a.(3) (see Paragraph 4.c.(2)).

(3) Distribution. The "original" proposal shall be identified. Proposals shall be addressed to the PCO, Mr. John Huber, at the following address:

Acquisition Center of Excellence (ASC/AQH)

Area B, Bldg 570, 1755 Eleventh Street

Wright-Patterson AFB OH 45433-7404

b. The proposal shall be clear and concise, with sufficient detail to substantiate the validity of the offeror’s approach to meet the requirements. 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.

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

d. Proposal Acceptance Period. The proposal acceptance period is specified in Section

A, Block 12 of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for 365 calendar days from the closing date for receipt of proposals.

e. Copies. 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.

f. North American Industry Classification System (NAICS) Code. The NAICS code for this acquisition is 541511 and size standard is $25M/year.

g. Central Contractor Registration (CCR). The final rule implementing CCR in the

Department of Defense (DoD) was published 31 Mar 1998. Contractors will not be eligible to receive a contract award from a DoD activity unless they are registered in CCR. The rule requires a firm to be registered in DoD CCR Database prior to award of any contract, basic agreement, basic ordering agreement, or blanket purchase agreement, for awards based on solicitations issued after 31 May 1998. Firms must register on a one-time basis and annually confirm accuracy and completeness of registration information. On-line registration and instructions can be accessed at https://www.bpn.gov/ccr/default.aspx.

h. Data Universal Numbering System (DUNS) Number. DUNS Number applies to offers exceeding $25,000. The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation “DUNS” followed by the DUNS number that identifies the offeror’s name and address. If the offeror does not have a DUNS number, Dun and Bradstreet should be contacted to obtain one at no charge. An offeror within the United States may call 1-

800-333-0505. The offeror may obtain more information regarding the DUNS number, including locations of local Dun and Bradstreet Information Services offices for offerors located outside the United States, from the internet homepage at http://www.dnb.com/. If an offeror is unable to locate a local service center, an email may be sent to Dun and Bradstreet at custserv@dnb.com.

i. Points of Contact. PCO is Mr. John Huber, and the Contract Negotiator is Mr. Brett

Wray. Address any questions or concerns you may have to Mr. John Huber, john.huber@wpafb.af.mil, or 937-255-3801. It is encouraged that any such questions or requests http://www.dnb.com/ mailto:custserv@dnb.com mailto:john.huber@wpafb.af.mil be submitted within ten days after the RFP release date. Answers to such questions and clarifications will be provided by posting questions and answers (Q&A) on the “F-15 TDAS” solicitation on Federal Business Opportunities (FBO) at http://www.fedbizopps.gov. In the event of conflict between the answer to any questions and the RFP, the RFP shall take precedence.

j. Debriefings. The PCO will promptly notify offerors of any decision to exclude them from the competitive range, if applicable, whereupon they may request and receive a debriefing in accordance with FAR 15.505. The PCO 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 debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

k. 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 PCO in writing with supporting rationale.

l. Electronic Reference Documents. All referenced documents for this solicitation are available on the FBO web site. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The

F-15 TDAS re-compete contract FedBizOpps web page is:

https://www.fbo.gov/index?s=opportunity&mode=form&id=aa43d9904036378b845511a749e78 cf2&tab=core&_cview=1

m. Bidder’s Library. A Bidder’s Library can be made available via CD-R upon request.

Please email Mr. Brett Wray at brett.wray@wpafb.af.mil with your company name and mailing address. The Bidder’s Library will be sent within 1 business day of receipt of your request.

n. Communications. Exchanges of source selection information between Government and offerors will be controlled by the PCO. 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” in the subject line.

3. Proposal Preparation Instructions:

a. These instructions prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. The instructions permit the inclusion of any additional data or information an offeror deems pertinent.

Offerors are cautioned to follow the detailed instructions fully and carefully, as the Government intends to make an award based on initial offers received, without discussion of such offers. The

Government may make a final determination regarding acceptability solely on the basis of the proposal as submitted without requesting any further information. However, if deemed necessary the Government may request additional information in accordance with FAR 15.306.

b. It is anticipated that pricing of this action will be based on adequate price competition;

therefore, offerors are not required to submit certified cost or pricing data. However, if after http://www.fedbizopps.gov/ https://www.fbo.gov/index?s=opportunity&mode=form&id=aa43d9904036378b845511a749e78cf2&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=aa43d9904036378b845511a749e78cf2&tab=core&_cview=1 mailto:brett.wray@wpafb.af.mil receipt of proposals it is determined that adequate price competition does not exist, certified cost or pricing data shall be required (see FAR 15.406-2).

c. Organization/Number of Copies/Page Limits. The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this table, and shall be within the required page limits with one original and copies as specified in the table below. The contents identified in the table shall be separately bound in three-ring, loose-leaf binders. The required contents of each proposal volume are described in Section 4 herein.

PROPOSAL ORGANIZATION TABLE

VOLUME

ITO

PARAGRAPH

NUMBER VOLUME TITLE

COPIES

(PAPER/

ELECTRONIC)

PAGE LIMIT

I 4.a Executive Summary 3/2 10

II 4.b Technical Proposal 3/2 150

III 4.c Past Performance Information 3/2 No Limit

IV 4.d Price Proposal 3/2 No Limit

V 4.e Contract Documentation 3/2 N/A

d. 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 destroyed. Page limitations may be placed on responses to Evaluation Notices

(ENs), if requested. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

e. Pricing Information. All pricing information shall be addressed only in the Price

Proposal and Contract Documentation Volumes.

f. Cross Referencing. 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 complete the cross reference matrix at Attachment 18B of this ITO indicating the proposal reference information as it relates to Sections L and M, the

Work Breakdown Structure (WBS), Performance Work Statement (PWS), Contract Line Item

Number (CLIN), and Contract Data Requirement List (CDRL) references found therein.

g. Indexing. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections and will not be included in page limitations. Index pages should be blank and not impart any information.

h. Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Page limitations do not apply to glossaries.

i. 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, printed or copied double-sided, except for foldout pages containing figures (see Paragraph 3.j, below). Pages shall be double-spaced and typed, 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. At least 1-inch margins on the top and bottom and ¾-inch side margins shall be used. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to EN responses. These limitations shall apply to both electronic and hard copy proposals. Page size and format restrictions do not apply to the past performance information submitted Past Performance Information Tool (see Paragraph 3.l.(2)).

j. Figures. 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, legible and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume and may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. Each foldout page shall be numbered sequentially with all other pages in the volume. A foldout page shall only be counted as one page and shall display printed material on only one side of the sheet. For tables, charts, graphs and figures, the text may be smaller than 12 point; however, it must be legible. These limitations shall apply to both electronic and hard copy proposals.

k. Binding and Labeling. Each volume of the proposal shall be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. Staples shall not be used. The original proposal shall have 2 holes punched in the top (using a 2-hole punch) in addition to the holes punched for the binder. A cover sheet shall 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 (e.g. blue). Be sure to apply any and all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), “Restriction on Disclosure and Use of Data,” and 3.104-4, “Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.”

l. Electronic Offers.

(1) Do not submit your proposal on a flash drive or CD-RW media. The content and page size of electronic copies must be identical to the hard copies. Electronic storage media shall be submitted in one of the following formats: prerecorded (pressed) CD-ROM or CD-R.

(No CDRW’s). For electronic copies, indicate on each compact disc (CD) the volume number(s) and title(s). Use separate files to permit rapid location of all portions, including sub-factors, exhibits, annexes, and attachments, if any. Each volume shall be in a different directory on a CD.

If files are compressed, the necessary decompression program must be included. Two electronic copies of the proposal shall be submitted in the following formats: Microsoft (MS) Word 2007, MS Excel 2007, MS-Project 2007, or MS-Power Point 2007, as applicable. One copy must be unlocked in order to export the winning offeror’s information into government contract writing systems.

(2) Past Performance Information. Offeror’s must use the Past Performance

Information Tool (see Section L, Attachment 18F for instructions) for submittal of relevant past performance contract information. Hard copies of the pages generated from this tool shall be used in the hard copy of the past performance volume subject to the limitations outlined in this solicitation. In addition to the hard copies included in the proposal, submit one electronic copy of the Past Performance Information Tool database on a prerecorded (pressed) CD-ROM or CD-

R (No CD-RW’s), and include it with the proposal sent to the Procurement Contracting Officer.

If you are unable to download the past performance information tool, contact the contracting officer for assistance. All Past Performance materials shall include the following legend at the top and bottom of each page: SOURCE SELECTION INFORMATION FOR OFFICIAL USE

ONLY – See FAR 3.104 AND 2.101

4. Proposal Organization

a. Volume I - Executive Summary. In the executive summary volume, the offeror shall provide the following information:

(1) Narrative Summary. The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding 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.

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

b. Volume II – Technical Proposal.

(1) General. The Technical Proposal should be specific, complete, legible, and coherent. Your responses will be evaluated against the sub-factors defined in Section M. Using the instructions provided below, give a description and explanation of your processes. A thorough explanation is critical so that the government may determine an offeror’s ability to perform the work required in the PWS. Your process descriptions shall be as specific as possible for the actual methodology you would use for accomplishing and satisfying these factors and subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing how your company will perform all the requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. In addition to the items described below, the offeror shall submit, as attachments to the Technical Proposal, Volume II, the plans specified in the Table below.

(2) Volume II Organization. The Technical Proposal volume shall be organized according to the following outline:

TECHNICAL PROPOSAL ORGANIZATION

VOLUME II -- PAGE LIMIT 150 (TO INCLUDE ATTACHMENTS)

SECTION TITLE

1 Table of Contents 2 List of Tables and Drawings 3 Glossary 4 Technical Proposal Cross Reference Matrix 5 Technical Subfactors

5.1 Subfactor 1: Systems Engineering/Program Management

5.2 Subfactor 2: Change Management

5.3 Subfactor 3: Contractor Logistics Support (CLS)

Attachments

1. Transition Plan

2. Draft System Security Plan

3. Small Business Subcontracting Plan

4. Small Business Participation Plan

(3) Subfactors. Address your proposed approach that meets the requirements of each of the following technical subfactors.

(A) Subfactor 1: System Engineering/Program Management. The offeror shall specifically provide the following elements in their proposal. With each element, the offeror shall also identify any cost/performance/schedule risks, and any mitigation to those risks:

(i) Transition Plan. The offeror shall provide a time-phased 60-calendar day Transition Plan (with an attached schedule in Microsoft Project 2007) ensuring adherence to PWS Para 10.1, as an attachment to the Technical Proposal, Volume II, addressing:

(a) Initial staffing requirements, including identification of key positions, recruitment and hiring plans, and personnel qualifications; and

(b) If applicable, how the offeror plans to relocate, setup, and verify device functionality of Government Furnished Property; and

(ii) Management Approach. The offeror shall provide an approach to program management for the F-15 TDAS program to include:

(a) Descriptions and organizational charts identifying and substantiating the qualifications of the program manager, site managers, TSSC managers, and key supervisory personnel; includes specific lines of supervision such as management devoted to the F-15 TDAS TSSC, and

(b) Process(s) for identifying issues and risk to the F-15

TDAS program’s schedule or performance and their prevention or mitigation; and

(c) A discussion of their approach to subcontractor management. The offeror shall present in an attachment, appropriate Letters of Intent, signed by both companies. Offerors shall also provide a table that lists all proposed first and second tier subcontractors (individually by name), and include their addresses, the principal service or supply being provided by the subcontractor, and the expected dollar value of the subcontract. A sample of the table is provided below:

NAME OF

SUBCONTRACTOR

ADDRESS SUPPLY OR SERVICE

PROVIDED

DOLLAR AMOUNT

OF SUBCONTRACT

XYZ Corp.

123 Main St.

Anytown, NY 01345 Castings $1,500,000

Acme, Ltd.

456 First Ave.

Somewhere, NY 54321 Logistics software $75,000

(iii) Draft System Security Plan. The offeror shall provide a draft

System Security Plan that addresses their approach to ensuring adherence to Paragraph 3.3. of the Performance Work Statement (Attachment 1). This plan should include any applicable configuration drawings.

(iv) Small Business Subcontracting. Offerors are required to subcontract to small businesses a minimum of 20% of the total dollar value of all task orders issued within the same 12-month period (see Clause H-109). The offeror shall provide the following:

(a) A Small Business Subcontracting Plan that complies with Section I clauses 52.219-8, 52.219-9 Alternate II, and 252.219-7003; and AFFARS

5319.704, and applicable FAR supplements.

(b) A Small Business Participation Plan, required from all offerors (including large business companies with master subcontracting plans, individual subcontracting plans, commercial subcontracting plans or comprehensive subcontracting plans, and small business companies) which includes the following:

(1) Individual requirements and goals, expressed in dollars and percentages (against Total Contract Value) for each and every year of the contract and as a total for all first tier subcontractors (Large Business, Small Business (SB), Small

Disadvantaged Business (SDB), Woman-Owned Small Business (WOSB), Historically

Underutilized Business Zone (HUBZone), Veteran-Owned Small Business (VOSB), and

Service-Disabled Veteran-Owned Small Business (SDVOSB)).

(2) Initiatives to assist, promote, and utilize SB, SDB, WOSB, HUBZone, VOSB, and SDVOSB. The offeror’s plan includes examples of how the offeror will maximize SB opportunities and use small businesses in mission critical aspects

(e.g. technology innovation) of the F-15 TDAS program.

(3) A list identifying specific small businesses in support of meeting contractual small business participation requirements (IAW Clause H109), including documentation of commitments with specific small businesses or rationale where commitments have not yet been accomplished.

(B) Subfactor 2: Change Management. The offeror shall specifically provide the following elements in their proposal. With each element, the offeror shall also identify any cost/performance/schedule risks, and any mitigation to those risks:

(i) Concurrency. The offeror shall describe its approach to implement Suite 8 OFP Update adhering to PWS Para 6.2.6 and ensure the following is included:

(a) A description of how the offeror will design, validate, and deliver the release to keep the devices concurrent with the platform; and

(b) A description of how the offeror will obtain/use/develop source code and other technical data while remaining consistent with the offeror’s approach to subcontractor management [see 4.b.(3)(A)(ii)(c)]; and

(c) A detailed schedule in Microsoft Project 2007 assuming a Suite 8 OFP fielding in July of 2016 with a lead-time consistent with the contractor’s proposed

Suite 8 lead-time found in Attachment 2 – Price Matrix submitted by the contractor; and

(d) A description of the proposed process for timely resolution of Deficiency Reports (DR).

(e) A description that defines and discusses its processes to implement and maintain configuration management of the devices; and

(f) A description of the risk analysis performed and mitigation plans; and

(g) A description of the impacts to training devices and associated support equipment and software.

(ii) Databases. The offeror shall describe their proposed processes and allocated resources to support the development of, and modifications to, the F-15 TDAS visual and sensors simulation databases and entity models.

(iii) Device Conversion. The offeror shall describe its approach to modify one existing CONUS TFE-2 from an F-15C to an F-15E configuration, adhering to PWS

Para 6.2.2 and ensure the following is included:

(a) A detailed description of the parts replaced, added, and removed; and

(b) A description of any temporary relocations, if applicable; and

(c) A detailed schedule for the TFE-2 conversion in

Microsoft Project 2007 with events and allocated resources related to accomplish the full completion of this conversion and with lead-time consistent with the contractor’s proposed TFE-

2 lead-time found in Attachment 2 – Price Matrix submitted by the contractor.

(iv) Build to Print Production. The offeror shall describe their proposed approach to build a single new Integrated Aircrew Trainer (IAT) device to print as per drawings located in the bidder’s library. This approach shall include:

(a) A description of any impacts to the baseline drawings identified by the offeror such as outdated/obsolete parts; and

(b) A detailed schedule for the IAT production in Microsoft

Project 2007 with events and allocated resources related to accomplish the full completion of this effort and with lead-time consistent with the contractor’s proposed IAT lead-time found in

Attachment 2 – Price Matrix submitted by the contractor.

(C) Subfactor 3: Contractor Logistics Support. The offeror shall specifically provide the following elements in their proposal. With each element, the offeror shall also identify any cost/performance/schedule risks, and any mitigation to those risks:

(i) On-Site Requirements. The offeror shall describe their approach for on-site CLS maintenance/logistics support adhering to approved technical documents found in the bidders library. The approach shall:

(a) Describe how the offeror will achieve a 95% Integrated

Aircrew Trainer (IAT) availability; and

(b) Address Preventive Maintenance Inspections (PMI) and material management (to include processes for identifying, reporting, tracking, verifying, and resolving trainer system discrepancies).

(ii) On-Call Requirements. The offeror shall describe their approach for on-call CLS maintenance/logistics support adhering to approved technical documents found in the bidders library. The approach shall:

(a) Describe how the offeror will achieve MTD repairs within 48 hours at Sheppard AFB, 72 hours Continental United States (CONUS), and 96 hours

Outside of Continental United States (OCONUS); and

(b) Address Preventive Maintenance Inspections (PMI) and material management (to include processes for identifying, reporting, tracking, verifying, and resolving trainer system discrepancies).

c. Volume III – Past Performance Volume.

(1) Offerors shall submit a Past Performance Volume with its proposal, containing past performance information on recent and relevant efforts (see Section M for recency and relevancy definitions). This information shall be provided for the offeror and proposed significant subcontractors, teaming partners, joint venture partners, and suppliers (those whose cost/price on the proposed contract are the lower of either -- (A) $12.5 million or more; or (B) both more than $700,000 and more than 10 percent of the prime contractor’s proposed price). In addition to the data provided in this volume, the government may use data obtained from other sources in the evaluation of past performance.

(2) Early Proposal Submission. In order for the government to be able to conduct its assessment efficiently, offerors are requested to submit their past performance volume no later than the date specified at Section L, Para 2.a.(2). Failure to submit early past performance proposal information will not result in offeror disqualification. However, any past performance information received from the offeror after proposal submission due date will not be considered.

(3) Volume III Organization. The Past Performance Volume shall be organized according to the following outline:

PAST PERFORMANCE PROPOSAL ORGANIZATION

VOLUME III -- NO PAGE LIMIT

SECTION TITLE

1 Table of Contents

Past Performance Effort List (Generated from the Past Performance Information Tool)

3 Past Performance Questionnaires

4 Terminated Contracts (if applicable)

(4) Each offeror shall submit the following:

(A) Past Performance Effort List. Offerors shall provide a list of past performance information of up to five (including subcontractors) relevant efforts performed for

Federal agencies and commercial customers within three years of issuance date of this solicitation. If this is a first time joint effort, each party to the arrangement must provide a list of past and present relevant contracts on no more than a combined total of five efforts. The Past

Performance Information Tool described in Section L, Paragraph 3.l.(2) shall be used. The specific content shall include:

(i) Information on recent efforts that you consider most relevant in demonstrating your ability to perform the proposed contract. The offeror’s past performance information shall include information about predecessor companies, proposed key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to this acquisition. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see

Section M paragraph 2.c.(3). Not all aspects of relevancy must be included within a single effort;

aspects of relevant performance may be from separate efforts.

(ii) Offerors shall explain what aspects of each effort they deem relevant to the proposed contract and why they are considered relevant. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts and past efforts to identify and manage program risk. Merely having problems does not automatically equate to a Limited or No Confidence Past Performance Confidence

Assessment 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 rated higher in the Past Performance

Confidence Assessment. Submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

(iii) Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of recent and relevant efforts or between conclusion of recent and relevant 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 for the last three years. A pamphlet or other commercial document describing such reorganizations will 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 information 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.

(iv) Subcontractor Consent: Subcontractor past performance information cannot be disclosed to the prime offeror without the subcontractor’s consent. The offeror shall submit, together with the information required in this paragraph, a Consent Letter

(Attachment 18D), 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 18E), authorizing release to the

Government of requested information on the offeror's performance.

(B) Past Performance Questionnaire. A past performance questionnaire is included at Attachment 18C. Offerors shall complete Sections I and II and then send this past performance questionnaire directly to the referenced points of contact (a.k.a. “respondents”) for the past efforts identified in the Past Performance Effort List. Respondents shall be instructed to complete Section III and to send the Past Performance Questionnaire (with Sections I, II, and III completed) directly to the government contracting officer by the date specified in Paragraph

2.a.(2) via e-mail to john.huber@wpafb.af.mil or directly to John Huber at the address specified in Paragraph 2.a.(3). A copy of each Past Performance Questionnaire sent to respondents with

Sections I and II completed shall be included in Volume III, Section 3 of the offeror’s proposal.

(C) Terminated Contracts. In addition to the content provided in the Past

Performance Information Tool on FBO and Past Performance Questionnaires, offerors shall furnish the following information for all contracts terminated in 2009 through the date this solicitation was issued:

CONTRACT INFORMATION

1 Company/Division name

2 Program Title

3 Contracting Agency/Customer

4 Contract Number

5 Contract Dollar Value

6 Period of Performance

Current Point of Contact with the customer’s organization including name, address, email address & telephone number

Reason for Termination

d. Volume IV – Cost/Price Volume.

(1) General Instructions.

(A) Price Reasonableness. These instructions provide critical information for you to submit information other than 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 either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Offers should have sufficient detail to demonstrate their reasonableness. The burden of proof for credibility of proposed prices rests with the offeror.

(B) Estimating Techniques and Methods. When responding to the 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.

mailto:john.huber@wpafb.af.mil

(C) Price Information. 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.

(D) “Then Year” Dollars. Proposals shall be in “Then Year” (TY) United

States currency dollars unless stated specifically otherwise. TY dollars are dollars that have been escalated into the time period of performance of the contract. They are sometimes referred to as

“escalated dollars” or “inflated dollars”.

(E) Pricing Approach & Methodology. The offeror shall provide a narrative of the basic pricing approach and methodology used to generate prices. The offeror shall provide any ground rules and assumptions necessary for the government to understand what the prices represent and to enable the government to determine if the prices are reasonable.

These assumptions should correlate to and/or supplement information elsewhere in the proposal to add clarity but avoid repetition or conflict.

(F) Cost or Pricing Information Requirements. In accordance with FAR

15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided in accordance with FAR 15.403-5.

If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit certified cost or pricing data.

(G) Dollar Format. All dollar amounts provided in response to these instructions shall be stated in U.S. currency, and shall be rounded to the nearest dollar. All dollars shall be displayed in the same units (millions, thousands, and so on).

(H) Price Proposal Submission Sheet. Populate the Price Proposal

Submission Sheet found at Attachment 18A. Within the Price Proposal Submission Sheet, populate only the unit prices and applicable lead times (highlighted in yellow). Extended Prices will automatically be calculated. The Price Proposal Submission Sheet will also calculate the

Total Evaluated Price (TEP). Should a contract award result, prices on the Price Proposal

Submission Sheet will be incorporated directly into the CLINs found in Section B and applicable dollar amounts will automatically be input into the Price Matrix which will be incorporated into the resulting contract at Attachment 2. Offerors will also input pricing information directly into

Section B (see Paragraph 4.e.(1)(B)). In the event of a discrepancy between Section B pricing and the Price Proposal Submission Sheet pricing, the Price Proposal Submission Sheet pricing will be used to evaluate TEP and will be used in any resulting contract Section B.

(2) Volume IV Organization: The Price volume shall be organized according to the following outline:

PRICE PROPOSAL ORGANIZATION

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b154031 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b154031 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b154033 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b154035 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b154031

VOLUME IV -- NO PAGE LIMIT

SECTION TITLE

Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement.

Pricing information and supporting data, to include estimating methodology. The Price Proposal Submission Sheet should be included in this section.

Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), base support, long lead costs, facilities cost, termination costs, inflation rate summary and explanation. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Price volume, if any.

e. Volume V – Contract Documentation.

(1) Volume V Organization. The Contract Documentation volume shall be organized according to the following outline:

CONTRACT DOCUMENTATION PROPOSAL ORGANIZATION

VOLUME V

SECTION TITLE

1 Table of Contents

2 Model Contract

3 Representations and Certifications

4 Exceptions to Solicitation Requirements (if applicable)

5 Other Information Required

(2) Model Contract. The purpose of this volume is to provide information to the

Government for preparing the contract document and supporting file. Please note that Sections

K, L (to include Attachment 18), and M (to include Attachment 19) are used for the solicitation but will be removed prior to award of any resultant contract. Also note that the solicitation number found on all attachments will be changed to a contract number prior to award of any resultant contract. The offeror's proposal shall include:

(A) Completion of Blocks 14-18 to include signature/date of the Standard

Form 33 and if applicable a signed SF 30 Amendment of Solicitation/Modification of Contract for all amendments. Signature by the offeror on the SF 33 constitutes an offer, which the

Government may accept. The “original” copy should be clearly marked under separate cover and should be two-hole punched at the top of each sheet of paper.

(B) All pricing information in Section B of the RFP. This information should match the pricing information on the Price Proposal Submission Sheet (see Paragraph

4.d.(1)(H)).

(C) Section F – Completed fill-in text for all applicable deliveries.

(D) Section H – Completed fill-in text for Clause H110 Associate

Contractor Agreement, remaining consistent with the Offeror’s Technical Proposal, Volume II.

(E) Section I – Completed fill-in text for clauses 52.244-02 and 252.211-

7003.

(F) Attachment 2 – Price Matrix. This Price Matrix will automatically be completed when the offeror completes the required information within the Price Proposal

Submission Sheet.

(G) Proposed Plans. Please note that the offeror’s Transition Plan, Small

Business Subcontracting Plan, and Small Business Participation Plan (submitted as part of the offeror’s Volume II Technical Proposal) will be incorporated into the contract as Attachments.

(H) Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. See Section K, DFARS

Provision 252.227-7017 and Section L, DFARS Provision 252.227-7028 for applicability. Any assertions will be incorporated into the contract as an Attachment.

(4) Representations and Certifications. Offerors shall complete and submit all representations, certifications, acknowledgments and statements found at Section K.

(5) Exceptions to Solicitation Requirements. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of the table below.

SOLICITATION EXCEPTIONS

Solicitation Document

Page/Para Number

Requirement/Portion Rationale

PWS, Model

Contract, ITO, etc.

Applicable

Page and Para

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can or will not be met

(6) Other Information Required:

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

(B) Government Offices. Provide the mailing address, email, and telephone number and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name, email, and telephone number for the

Administrative Contracting Officer (ACO).

(C) 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.