Atch_4_Section_L.pdf

Section L – FA8202-15-R-1004

Section L

Instructions, Conditions, and Notices to Offerors (ITO)

Acquisition of Engineering Services

For the

A-10 Field Level Technical and Engineering Services (Fault Isolation) Program

6 February 2014

Section Content:

1.0 - Program Structure Objectives

2.0 - General Instructions

3.0 - Volume I – Executive Summary

4.0 - Volume II – Technical Proposal

5.0 - Volume III – Performance Confidence

6.0 - Volume IV – Price Proposal

7.0 - Volume V – Contract Documentation

8.0 - Required Attachments

1.0 Program Structure and Objective

The objective of this effort is to obtain task based engineering services for continued technical and engineering support for the sustainment of all configurations of the A-10 weapon system and to accomplish work requirements specified within the Performance Work Statement (PWS).

2.0 General Instructions

(a) This section of the instructions 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 Instructions and must be submitted in accordance with (IAW) these instructions. The proposal must be complete, self-sufficient, and respond directly to the requirements of this solicitation. The proposal shall be compliant with and meet the entire RFP requirements. Offerors are advised that submissions that DO NOT conform to the instructions provided herein may result in an unacceptable proposal evaluation, and/or exclusion from further consideration.

(b) Include Sufficient Detail: The proposal shall be clear, concise, and shall include sufficient detail for an effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements and objectives, but 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, capabilities, and experience, and will base its evaluation on the information presented in the offeror’s proposal.

(c) Embellishments Not Desired: Elaborate brochures/documentation, binding, detailed art work, or other embellishments are unnecessary and not desired.

(d) Proposal Acceptance and Validity Dates: The proposal acceptance period is specified on the first page of the solicitation. The offeror shall make a clear statement on the front page of the contract documentation volume (volume V) that the proposal is valid through this date.

(e) Disposition of Proposals: IAW FAR Subpart 4.803(a), the Government will retain one copy of all proposals. Unless the offeror requests otherwise (in their proposal), the Government will destroy extra copies of the successful and unsuccessful proposals.

(f) Past Performance: For each contract identified, the offeror shall complete a Past Performance Information Sheet (PPIS), Attachment 1, in response to this RFP. The PCO will make a determination of acceptable past and current performance (defined in Section M) IAW FAR part 15.101-2 and FAR part 15.305(a)(2).

2.1 General Information

2.1.1 Contact Information: The Procuring Contracting Officer (PCO) and the Contract Specialist are the sole points of contact for this acquisition. Written requests for clarification may be sent by mail or email (preferred) to the PCO, with a copy to the Contract Specialist.

Contact Information is below:

AFLCMC/WWAK

ATTN: Ms. Stephanie Rearick Contract Specialist 6072 Fir Ave Bldg. 1233 Hill AFB, UT 84056-5820 stephanie.rearick@us.af.mil 801-777-7580

AFLCMC/WWAK

ATTN: Mr. Nathan Lee Procurement Contracting Officer 6072 Fir Ave Bldg. 1233 Hill AFB, UT 84056-5820 nathan.lee.3@us.af.mil 801-775-4928

All questions and answers shall be sent through the prime offeror.

2.1.2 Debriefings: The PCO will promptly notify offerors of any decision to exclude them from the competitive range or otherwise eliminate them from the competition IAW FAR 15.503;

whereupon, they may request and receive a debriefing IAW FAR 15.505 and/or FAR 15.506.

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

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The 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 a debriefing must make their request IAW the requirements of FAR 15.505 and/or FAR 15.506 procedures, as applicable.

2.1.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 PCO in writing with supporting rationale. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

2.1.4 Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at https://www.fbo.gov/ or via a ‘Bidder’s Library’ established by the A-10 Contracting Office. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5 Oral Presentations: Oral presentations will not be allowed.

2.1.6 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. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. The PCO may determine to conduct telephone exchanges when deemed appropriate by the Government.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.1) below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The technical proposal, performance confidence and price proposal volumes identified in the table shall be separately bound in three-ring, loose-leaf binders; the remaining volumes can be in one binder with a distinct tab for each volume.

The contents of each proposal volume are described in this section and summarized in the table below. Offerors shall include a Table of Contents in the proposal. In addition to the “Hard Copies” requested in Table 2.1 below, please submit one CD-R for each volume of the offeror’s proposal (not on CD-RW).

Table 2.1 - Proposal Organization

Volume Instruction Paragraph Number

Title Hard Copies

Electronic Copies

Page Limit

I 3.0 Executive Summary 2 1 5 II 4.0 Technical Proposal 5 1 61 III 5.0 Performance Confidence 3 1 15 IV 6.0 Price Proposal 3 1 Unlimited V 7.0 Contract Documentation 2 1 Unlimited

2.2.1 Page Limitations: Page limitations are identified in Table 2.1 – Proposal Organization, and explained below. Offerors are advised that the limitations shall be treated as maximums. If https://www.fbo.gov/ https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104 exceeded, the excess pages will not be evaluated or considered for award purposes; rather, they will be returned to the offeror, or destroyed as soon as practical. Additionally, information provided outside of the appropriate volume will not be evaluated. For example; additional technical information found within Volume V would not be evaluated. Page limitations may be placed on responses to Evaluation Notices (ENs) if applicable. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors if discussions are entered into. Each page shall be counted except cover/title pages, tables of contents, tabbed dividers, acronym lists, and glossaries.

2.2.1.1 Page Size and Format

(a) 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 by 11 inches (foldouts must fold into no larger than 8.5 by 11 inches). Pages shall be typed using single spacing, except for the reproduced sections of the solicitation document and contractor deliverable plans, for which the CDRL Data Item Descriptions state shall be prepared in contractor formatting. The text size shall be no less than 12 point in Times New Roman typeface. 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 also apply to responses to ENs. These limitations shall apply to both electronic and hard copy format.

(b) 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, legible and shall not exceed 8.5 by 11 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 8 point font. These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cross Referencing: Each Volume (I – V) of the proposal shall be submitted, evaluated, and considered based solely on the information contained therein (i.e. each volume “stands-alone”). Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

2.2.3. Pricing Information: All pricing information shall be addressed ONLY within the Pricing and Contract Documentation Volumes.

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

2.2.5. Indexing: Each volume shall contain a detailed table of contents delineating the subparagraphs within that volume. Tab indexing shall be used to identify sections.

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

2.2.7. Binding and Labeling: The three-ring loose leaf binders used to contain the proposal information shall permit the volumes to lie flat when open. Staples shall not be used. A cover sheet should preface each volume, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. The same identifying data should be placed on the spine of each binder. Since classified information shall not be provided in the proposal, all 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 IAW FAR 52.215- 1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Each page that contains proprietary information shall be marked inside the header and footer of each page with the following statement “SOURCE SELECTION INFORMATION (FAR 3.104) FOR

OFFICIAL USE ONLY.”

2.3 Electronic Offers: The content and page size of the electronic copies must be identical to the hard copies in all respects. The electronic copies shall be submitted on a single, virus free, ISO formatted read-only CD-R. Indicate on each “CD-R” the volume number and title (NOTE THAT “CD-RWs” CANNOT BE READ, EVALUATED, OR CONSIDERED). Each volume shall be in a different “CD-R”. File compression will not be used. Each disk will be clearly labeled. Paper and electronic copies must be identical in all respects. In the event that there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. The electronic copy of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2010 (or later) Suite of Applications (Word, Excel, and Power Point) as applicable. PDF files are not acceptable. To facilitate evaluation electronic copies of the Pricing Volume of the proposal shall be submitted using Microsoft’s Excel format.

Please do not “read protect” submitted Excel worksheets. Provide all formulas (evident within the spreadsheet) and links used. Do not embed electronic files within other electronic files.

Word documents and Excel spreadsheets must be editable and not password protected.

2.4 Distribution: The "original" proposal shall be so designated and signed by the offeror’s authorized representative, and the “copies” should be identified appropriately. All requested copies must be received by the due date identified on the front page of the RFP. Proposals shall be addressed to the PCO and delivered to:

AFLCMC/WWAK

Nathan Lee, PCO c/o Stephanie Rearick, Contract Specialist 6072 Fir Ave Bldg. 1233 Hill AFB, UT 84056-5820

(801) 775-4928/DSN 775-4928

nathan.lee.3@us.af.mil

Include Solicitation Number FA8202-15-R-1004 on the address label.

3.0 Volume I - Executive Summary

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

mailto:nathan.lee.3@us.af.mil

3.1 Table of Contents: Provide a master table of contents for the entire proposal, by SECTION L and Government PWS paragraph number and the corresponding paragraph that addresses the referenced item. The table of contents will not count against the page limitation for this volume.

3.2 Other Information Required

3.2.1 Authorized Offeror Personnel: Provide the name, title, telephone number, and email address of the company/division point of contact regarding decisions made with respect to the offeror’s proposal and who can obligate (as to this proposal) the offeror’s company/firm contractually. Also identify those individuals authorized to negotiate with the Government.

3.2.2 Government Offices: Provide the mailing address, telephone number, email address, and facility code for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), and Government Paying Office for the offeror’s company/firm. Also provide this information for the Administrative Contracting Officer (ACO).

3.2.3 Company/Division Address, Identifying Codes, and Applicable Designations; and verifications:

• Offeror shall provide company/division's street address, county and facility code; CAGE code; DUNS code; and labor surplus area designation. This same information must be provided if the work (for completing what is proposed) 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.

• Offeror shall provide verification that unlimited/unrestricted rights IAW DFARS 252.227-7013 or 252.227-7015 apply for all required technical data deliveries, since such deliveries are either (1) necessary for operation, maintenance, installation, or training (other than detailed manufacturing or process data) and/or (2) funded completely by the Government under this contract.

3.3 Volume Organization: The Executive Summary shall be organized according to the following general outline:

1. Table of Contents

2. Authorized Offeror Personnel POCs

3. Government Offices POCs

4. Company Address, Cage Codes and Applicable Designations

5. Partnership/Joint Venture Agreement(s)

4.0 Volume II - Technical Proposal

4.1 General: The technical proposal shall be clear, concise, and complete and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing documentation to address how the offeror will meet these requirements. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their certifications, facilities and/or structural, mechanical, and electronics capabilities, and will base its evaluation on the information presented in the offeror’s proposal.

Using the instructions provided below, provide as specifically as possible the actual methodology the offeror would use for accomplishing/satisfying these sub-factors. All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that the company/firm will perform ALL the requirements specified in the solicitation (including the PWS); it is not necessary or desirable to tell us so in the proposal.

Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Responses will be evaluated against the Technical sub-factors defined in Section M, Evaluation Factors for Award.

4.1.1 Adequate Responses: Cursory responses or content which merely reiterates or reformulates section L, section M, or the PWS will not be considered as being responsive to the requirements of the solicitation. Evidence, which clearly demonstrates and supports the offeror’s claims, is essential. The absence of such evidence may result in a technically unacceptable proposal.

4.2 Volume Organization: The Proposal shall be organized according to the following general outline:

2. List of Table and Drawings

3. Glossary

4. Sample Task Responses (Sub-Factor A &B)

5. Technical Approach (Sub-Factor C)

6. Management Approach (Sub-Factor D)

4.3 Factor 1: Technical Acceptability

4.3.1 Sub-Factor A: Sample Task #1 – Real Time Engine Data (RTED) Airborne Data Recorder (ADR) Flight Data – See Attachment 4

The proposal and response to this task shall clearly demonstrate that the offeror has sufficient familiarity, experience, technical expertise and competence to accurately, correctly, effectively and efficiently understand, interpret, correct, complete, and update Turbine Engine Monitoring System (TEMS)/ADR related 107s using the Aircraft Systems Information Support Tool

(ASIST).

4.3.2 Sub-Factor B: Sample Task #2 – Trouble Analysis – See Attachment 5

The proposal and response to this sample task shall clearly demonstrate that the offeror has sufficient familiarity, experience, technical expertise and competence to accurately, correctly, effectively and efficiently resolve Technical Order 00-25-107 Maintenance Assistance requests.

4.3.3 Sub-Factor C: Technical Approach

4.3.3.1 The proposal shall describe in detail the offeror’s technical approach for meeting the PWS, Section 3 requirements identified in the following paragraph(s). For those requirements, the proposal shall mirror the outline of the PWS. If the technical approach utilizes subcontractor(s), identify how the prime contractor will be responsible for performing the primary and vital requirements.

Specifically, the offeror shall provide detailed strategies of how they will accomplish and satisfy the following key requirements IAW the PWS:

• Maintenance Engineering and Technical Support (PWS 3.1)

• Include a description of the offeror’s knowledge of how each system listed in PWS

3.1 is integrated into the A-10 platform, offeror’s ability to provide on-site support, offeror’s ability to use approved A-10C Mil-Std-1553B protocol and support equipment as well as standard Electrical Engineering lab equipment (multimeters, power supplies, oscilloscopes) to analyze A/C deficiencies, offeror’s ability to use troubleshooting methods outside of official AF Technical Orders, and offeror’s ability to follow Operational Safety Suitability and Effectiveness (OSS&E) policies and processes, the A-10 SPO policies, processes, A-10 Drawing Practices (document number: 08-A10DOC-001), Time Compliance Technical Order standards and regulations, and general Air Force Maintenance practices, procedures, and policies.

• Engineering Support Requests (PWS 3.1.1)

• Avionics and Mechanical Sub-System Commodity/Component Failures (PWS 3.1.2)

• Technical Data Deficiencies (PWS 3.1.3)

• AFTO 22/252 (PW 3.1.4)

• Technical Meeting Support (PWS 3.1.5)

• Design Review (PWS 3.1.6)

• Mishap/Safety Investigations (PWS 3.1.7)

4.3.4 Sub-Factor D: Management Approach – Program Management and Program Metrics (PWS Section 4.0)

The proposal shall describe the offeror’s program management approach toward accomplishing the requirements of the PWS.

The offeror shall describe their approach that outlines all processes and programs by which the offeror will effectively execute the requirements of the PWS. The proposal shall include an organizational chart of all key contractor employees, consultants and subcontractors that contains the appropriate level of expertise and skill mix for the successful performance of the Fault

Isolation program. The proposal shall also describe their approach that outlines all task performance, schedule, travel requirements, and reports.

5.0 Volume III (Factor 2) – Performance Confidence

5.1 General: Each offeror shall submit a performance confidence volume containing:

1. Completed Past Performance Information Sheets (PPIS) IAW the format contained in Attachment 1. Offerors may submit a maximum of five (5) PPISs on the prime contractor and a maximum of three (3) for its proposed key subcontractors individually. These PPISs shall be recent and relevant in accordance with the definition located in Section M of this RFP. If Offeror does not submit any PPISs, they shall provide rationale of why none are being provided. If Offeror identifies any adverse past performance, their proposal shall state how they resolved the adverse past performance issues.

2. Completed Roles and Responsibilities Worksheet IAW the format contained in Attachment 3 for all proposed subcontractors performing direct labor for this effort. The offer has discretion in determining the most beneficial mix and quantity of work efforts by prime offeror, key partners, or subcontractors covering as many of these elements as a is practical. A minimum of two (2) relevant work efforts shall be for the prime offeror and if less than five (5) relevant work efforts are submitted, the contractor shall specifically state and acknowledge its number is less than the five (5) it could submit.

5.1.1 Consent and Client Authorization Letter: The offeror shall submit a consent letter (Attachment 2) executed by each key subcontractor, and/or teaming partners identified on Roles and Responsibilities Worksheet, Attachment 3, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. A Consent Letter is provided because past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor’s consent. Provide with the proposal a letter from key subcontractors and/or teaming partners that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

The offeror shall submit a client authorization letter (Attachment 2) for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror's performance. The Government will need that consent before contacting commercial customers to assess the offeror’s past performance. The completed client authorization letters should be submitted as part of your Present/Past Performance Volume.

5.1.2 Summary Table: The offeror shall submit a Summary Table (see format below). The purpose of the summary table is to capture the total scope of work that the offeror is presenting in this Performance Confidence Volume. The Government may obtain and use performance information on any or none of these programs as well as programs not submitted by the offeror (This Section counts against the page count.) The table shall include (as a minimum) current information as follows:

Contractor Contract

Number/Work Effort

Total Period of

Performance

Maximum Total

Estimated Dollars

Contracting Agency or Customer

Phone Number and

E-Mail Addresses of at Least Two POCs

(one being a “Contracts”

POC

Brief Program

Description (max 25 words)

Stage of the

Program & Brief Status

(max 25 words)

5.2 Performance Confidence Volume Submission: It is requested that the offeror submit its Performance Confidence Volume ten (10) calendar days prior to the date set forth in block 9 of the SF1449; however, offerors shall not submit it later than the proposal deadline.

5.3 Relevant Contracts: Relevance does not mean same or identical. Relevant means significantly similar to this acquisition to provide indicators of performance. Consider such things as product or service similarity, complexity, contract type, contract dollar value/size, program phase, division of company, major or critical subcontractors, teaming partners and joint ventures. Submit information IAW Attachment 1, PPIS. The offeror shall submit past performance information for work efforts identified in para 5.1.2; maximum of five (5) recent work efforts that are most relevant in demonstrating the offeror’s ability to perform the proposed effort. The offeror shall also include information for a maximum of three (3) recent work efforts performed by each of the teaming partners and significant subcontractors that are considered most relevant in demonstrating their ability to perform the proposed effort. Offeror shall include rationale supporting its assertion of relevance.

5.4 Organizational Structure Change History: If your company has been acquired or Acquired/Merged with another company, provide a roadmap explaining transitions as it relates to past performance for your company.

5.5 Contractor Relationships: If any of the offerors’ subcontractor identified on the PPIS are also potential offerors for this solicitation, the offeror may provide the POCs for the next higher level customer.

Provide information regarding predecessor companies, key personnel who have relevant experience of subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the acquisition and will be considered in the evaluation. If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangement with same partner. As with all past work efforts identified in the proposal, use the PPIS (Attachment 1).

5.6 Clarifying Submitted Past Performance: The Government may contact the points of contact provided by the offeror for the purpose of ascertaining and/or clarifying past performance information.

5.7 Other Performance Confidence Considerations: It is not presumed that the offeror’s past performance has been perfect. Rather, the proposal should contain evidence of the offeror’s ability to correct past problems if applicable. Problems not addressed by the offeror, but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of CPARS, if the offeror’s input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here. The Government may use data provided by each offeror in this volume and may use data obtained from other sources in the development of the confidence assessment.

5.8 Volume Organization: The Performance Confidence volume shall be organized according to the following general outline:

2. Glossary

3. Summary Table

4. Past Performance Information Sheets (PPISs) (Attachment 1)

5. Consent Letters (Attachment 2)

6. Roles and Responsibilities Worksheet (Attachment 3)

6.0 Volume IV (Factor 3) - Price Proposal

6.1 General: The price evaluation criteria of reasonableness, balance, and Total Evaluated Price (TEP) as defined in the evaluation document of the RFP will be assessed from the offeror’s information provided in this volume.

6.1.1 Total Evaluated Price (TEP):

(a) Insert proposed unit and extended prices in the pricing attachment of the RFP for each Contract Line Item Number (CLIN) including the option CLINs. The extended amount must equal the whole dollar unit price multiplied by the provided quantity unit of issue.

(b) The total TEP will be the price factor in determining which offeror’s proposal represents the best value to the Government. Consequently, the offeror submitting the “best value” proposal will be the successful contract awardee. The TEP is for award determination purposes only and will be a consideration in the best value award decision.

6.1.2 Price Information: Information beyond that required by this instruction shall not be submitted, unless offeror considers it essential to document or support their price position. All information relating to the proposed price including all required supporting documentation must be included in the Price Proposal and Contract Document Volumes. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

6.1.3 Pricing Information Requirements:

IAW FAR 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness the offeror shall be required to submit other than certified cost or pricing data; if none of the exceptions in FAR 15.403-1 apply, the offerors may be required to submit certified cost or pricing data.

Information shall be provided in format that is IAW FAR 15.403-5.

The PCO has made a preliminary determination of “Adequate Price Competition” IAW FAR 15.403-1 (c)(1). Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required. In the event that adequate competition does not emerge in response to the solicitation, the PCO may require submission of certified cost and pricing data, and a Certificate of Current Cost or Pricing Data (IAW FAR 15.403-4).

6.1.4 Rounding: All dollar amounts provided shall be rounded to the nearest dollar.

6.2 Volume Organization

The Pricing Volume shall consist of the following sections:

SECTION 1 – Table of Contents

SECTION 2 – Pricing information and supporting data, to include estimating methodology.

SECTION 3 – List each exception to the terms and conditions provided in the solicitation.

Provide complete rationale for any exceptions.

7.0 Volume V - Contract Documentation

7.1 Model Contract/Representations and Certifications: The purpose of this volume is to provide information to the Government for preparing the contract document and supporting files.

7.2 Solicitation/Contract Form:

(a) Complete blocks 13 and 27 of the RFP Section A In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. Sections A through J constitute the model contract. Offerors shall include signatures on all amendments associated with this RFP.

(b) Insert proposed unit and extended prices in the pricing attachment for each Contract Line Item Number (CLIN), including all option periods. The extended amount must equal the whole dollar unit price multiplied by the number of units.

(c) Complete the necessary fill-ins and certifications in Sections I through K. Section K shall be returned in its entirety. For Sections C through I, the offeror shall submit only those pages that require a fill-in.

(d) Offeror shall provide a 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 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU) and minority institutions https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b522199

(MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI.

7.3 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. 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 7.3 below.

Table 7.3 - 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

8.0. SECTION L – Required Attachments

Offerors shall submit the below attachments as part of their proposal:

Attachment 1: Past Performance Information Sheet Attachment 2: Subcontractor Teaming/Partner Consent Letter Attachment 3: Roles and Responsibilities Worksheet Attachment 4: Sample Task #1 Attachment 5: Sample Task #2

SECTION L ATTACHMENT 1: Past Performance Information Sheet (PPIS)

Past Performance Information (PPI): Offerors must provide the information requested in the paragraphs below (A through K) for each contract/program/work effort being described. Provide frank, concise comments regarding the offeror’s performance on the contracts identified. Provide a separate completed form for each contract/program/work effort submitted. Limit the number of past efforts submitted and the length of each submission to the limitations set forth at paragraph 5 of SECTION L of this solicitation. Identify past or current contracts/programs/work efforts (including Federal, State, and local Government and private) for efforts similar to the Government requirement (IAW paragraph 5 of SECTION L). Offerors may also provide information on problems encountered on the identified efforts and the offeror corrective actions.

A. Offeror Name (Company/Division), CAGE Code, DUNS Number

(NOTE: If the company or division performing this effort is different than the offeror or the relevance of this effort to the instant acquisition is impacted by any company/corporate organizational change, note those changes. Refer to the "Organizational Structure Change History" provided as part of the Past Performance Volume.)

B. Program Title

C. Contract/program/work effort Specifics - Contracting Agency or Customer, Contract Number or program/work effort title/description, Contract Type (if applicable), Period of Performance, Original Dollar Value and Current Dollar Value.

D. Brief Description of Effort as __Prime or __Subcontractor (Please indicate whether it was development and/or production, or other acquisition phase and highlight portions considered most relevant to current acquisition)

E. Completion Date - Original date, Current Schedule, Estimate at Completion, How Many Times Changed, Primary Causes of Change

F. Primary Customer Points of Contact: (For Government contracts provide current information on the Program Manager, ACO and PCO. For commercial contracts, provide points of contact fulfilling these same roles.)

G. For requirements under the Technical Acceptability factor in Section M, illustrate how the offeror’s past performance in applicable sub-factors applies.

H. Specify, by name, any key individual(s) who participated in this program and are planned to support the proposed acquisition. Also, indicate their contractual roles for both acquisitions.

I. Describe the nature or portion of the work on the proposed effort to be performed by the business entity being reported here. Also, estimate the percentage of the total proposed effort to be performed by this entity and whether this entity will be performing as the prime, subcontractor, or a corporate division related to the prime (define relationship)

SECTION L ATTACHMENT 2:

Subcontractor/Teaming Partner Consent Letter

For the Release of Past and Present Performance Information to the Prime Contractor

Past performance information concerning subcontractors and teaming partners cannot be disclosed to a private party without the subcontractor’s or teaming partner’s consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor/teaming partner past and present performance information to the prime contractor during exchanges. In an effort to assist the Government’s Performance Confidence evaluation team in assessing the offeror’s past performance relevancy and confidence, we request that the following consent letter be completed by the major subcontractors/ teaming partners identified in the offeror’s proposal. The completed consent letters should be submitted as part of the offeror’s Performance Confidence Volume.

SAMPLE

Dear “Contracting Officer:”

We are participating as a (subcontractor/teaming partner) with (prime contractor or name of entity providing proposal) in responding to the Department of the Air Force, Hill Air Force Base, Request for Proposal FA8202-15-R-XXXX for the A-10 Fault Isolation contract.

We understand that the Government is placing increased emphasis on past performance in order to obtain best value in source selections. In order to facilitate the performance confidence assessment process we are signing this consent letter to allow discussion of our past and present performance information with the prime contractor during the source selection process.

(Signature and title of individual who has the authority to sign for and legally bind the company)

Company Name:

Address:

CLIENT AUTHORIZATION LETTER

Past performance information concerning private sector contractors, subcontractors and joint venture partners cannot be disclosed to the Government without their consent. Client authorization letters are required for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror's performance.

The Government will need that consent before contacting commercial customers to assess the offeror’s past performance. In an effort to assist the Government's Past Performance Evaluation Team in assessing your past performance relevancy and confidence, we request that the following client authorization letter be completed by any commercial customers identified in your proposal. The completed client authorization letters should be submitted as part of your Present/Past Performance Volume.

Offerors should send with their list of references a letter similar to the following authorizing the reference to provide past performance information to the Government.

SAMPLE

Dear “Client:”

We are responding to a Department of the Air Force, Hill Air Force Base, Request for Proposal FA8202-15-R-XXXX for the A-10 Fault Isolation contract.

In their acquisitions, the Government is placing increased emphasis on past performance as a source selection factor. They are requiring those clients of entities responding to their solicitation to be identified, and their participation in the evaluation process is requested. In the event that you are contacted for information on work performed, you are hereby authorized to respond to those inquiries.

We have identified Mr./Ms.____________________________ of your organization as the point of contact based on his/her knowledge of our work. Your cooperation is appreciated. Any questions may be directed to [Bidder Point of Contact].

Sincerely, Signature and title of individual who has the authority to sign for and legally bind the company)

Company Name:

Address:

SECTION L ATTACHMENT 3: Roles and Responsibilities Worksheet

SECTION L ATTACHMENT 4: Sample Task #1—Real Time Engine Data (RTED) Airborne Data Recorder (ADR) Flight Data

Turbine Engine Monitoring System (TEMS)/ADR and Aircraft Structure Integrity Program (ASIP) system knowledge is required minimum to be able to troubleshoot and resolve TEMS/ADR related 107s.

The Government will provide Aircraft Systems Information Support Tool (ASIST) Computer Program Identification Number (CPIN) as a Government Furnished Information (GFI) for the offerors to be able to use it as a tool for the TEMS/ADR viewer. The Government owns ASIST with Distribution Statement D (Distribution authorized to DoD and U.S. DoD Contractors only). A-10 Technical Orders (TOs) will be provided in Bidder’s Library also.

Aircraft/file #___790175-3917-0.rted______ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________ What are your suggestions to troubleshoot the issue? (4 Points) What do you expect to find? (3 Points)

Aircraft/file #___800176-405-0.rted_____ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________ What are your suggestions to troubleshoot the issue? (4 Points)

What do you expect to find? (3Points) Aircraft/file #___800204-2586-0.rted_____ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________ What are your suggestions to troubleshoot the issue? (4 Points)

What do you expect to find? (3 Points)

Aircraft/file #__820665-3877-0.rted_____ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________

What are your suggestions to troubleshoot the issue? (4 Points)

What do you expect to find? (3 Points)

Aircraft/file #___820665-3906-0.rted_____ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________ What are your suggestions to troubleshoot the issue? (4 Points)

What do you expect to find? (3 Points)

Aircraft/file #__790152-4536-0.rted________ What are the Hits? (1 Point) _______________ Are they valid? (2 Points) __________________ Graph the issue (2 Points) _________________ What are your suggestions to troubleshoot the issue? (4 Points)

What do you expect to find? (3 Points)

SECTION L ATTACHMENT 5: Sample Task #2—Trouble Analysis

Efficiently resolving Technical Order 00-25-107 Maintenance Assistance requests is a critical element of the services intended to be performed by the offeror. The following problem scenarios are sample tasks for which the contractor shall submit their approach to providing field assistance. Responses should include instructions to the field using currently available technical data in support of the A-10 aircraft.

Responses may also include engineering approved deviations from technical orders or temporary modifications in order to effectively identify and fix the root cause and any contributing factors. Any proposed deviations shall not cause any unmanageable risk.

Responses shall indicate whether the problem can be resolved with field technicians at the base level or by contractor/depot personnel. Each response will be scored on a graded scale based on your clear written directions that show your understanding of aircraft systems and theory of operations. This shall lead to a clear defined logical approach in aircraft troubleshooting, identifying all key contributing factors and establishing the most expedient and effective means to resolve the problems.

Please take into consideration that real world activities and remote communications may translate into misunderstandings of actual field complaints, technician actions completed, incorrectly documented or inadvertently omitted directions toward problem isolation all negatively contribute to finding appropriate and efficient resolutions. Demonstrating your rigor in managing clear communications and direction with affected members in the field and verifying field findings is critical to success in any field support.

Problem 1 (32 points):

During a Functional Check Flight performed at Osan AB Korea, an A-10C aircraft rolled right 5 degrees per second to a 30 degree bank and then continued at 2 to 3 degrees per second to 60 degree bank when the Flight Control (FLT CONT) Switch is set from Normal (NORM) to Manual Reversion (MAN REV).

Maintenance has not been able to determine the cause of this un-commanded flight condition and have submitted a -107 request. Please indicate what questions you would ask of flight crew and maintenance personnel in order to assess possible contributing factors and gain an understanding of the most efficient approach to resolving this problem.

Please indicate all troubleshooting procedures you would request be completed by the field in order to expose the root cause and correct the condition. Please include appropriate Technical Order references or any proposed and approved deviations from existing data you would apply to find the malfunction. Please offer your determination if this problem requires on-wing contractor support.

When providing on-wing support to the field what limitations is a contractor susceptible to in conducting their activities?

Problem 2 (6 points):

A-10C aircraft deployed overseas experienced right roll at 6 to7 degrees per second when speed brakes are actuated at 5000 feet above ground level (AGL). Please indicate all troubleshooting procedures you would employ to determine the root cause.

Problem 3 (46 points):

A-10 aircraft in a war zone intermittently lost position lights and sometimes Strobe lights while in-flight after any pitch or roll maneuver. When it landed maintenance found that the position lights circuit breaker had released indicating system drew excess current. All attempts to localize the failure by maintenance personnel have been exhausted. The following are provided as responses for those activities completed by the mobilized unit:

1. Troubleshot wiring with a hand held multi-meter and TDR with no discrepancies found. The following A-10 Technical orders were referenced for use: 1A-10C -2-110-1, 1A-10C-2-110-1-1, 1A-

10C-2-24TS-1.

2. Documentation indicates that both left and Right wing lightening suppressors were replaced but did not solve problem.

3. Replaced position light and strobe light circuit breakers but did not solve problem.

4. Replaced Strobe light power supply, did not solve problem.

Due to the persistence and longevity of this problem and inability to identify the cause, the deployed unit requests TO 00-25-107 urgent engineering assistance. This has a direct and intolerable night mission impact.

Please indicate what actions you would perform in order to assist the field in resolving this issue.

During the course of your investigation stripped hardware securing the left wing Lightening Suppressor was discovered. The owning unit reported and documented both left and right wing suppressors had been changed. What conclusions and actions would you perform based on this finding?

Problem 4 (16 points):

Unit submitted 00-25-107 request for Auxiliary Power Unit (APU) auto shutdown on the ground and inflight whenever the VHF FM Radio is transmitting. This problem has plagued this aircraft for 36 months and has been an operational nuisance. Please indicate what contributing factors should be considered and how you would assist the field with the following information offered by them:

Used Technical orders 1A-10C-2-71TS-1, 1A-10C-2-110-1 to troubleshoot APU AUTO Shutdown.

1. Replaced APU Load Control Valve and ECB, did not fix problem

2. Replaced Fuel Engine Relay Box, did not fix problem.

3. Replaced APU hot air check Valve, did not fix problem

4. Replaced APU Fuel Control

Please indicate what conditions would need to exist to cause contractor personnel to mobilize in support of on-wing activities to resolve this condition.