Attachment_5_PSI_Section_L_13JUN23.pdf

Solicitation Number FA8232-23-R-3000 Attachment 5: Section L

L-900. INSTRUCTIONS TO OFFERORS

I. Proposal Format

A. General:

The following instructions cover the preparation and submittal of the Offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the Offeror shall provide a summary of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission in Volume I. The term “Offeror” shall be utilized throughout this document and shall include Team Venture and Teaming Partners, if applicable. Offerors shall submit only one proposal for the Product Support Integrator (PSI) Program as the Government will review only one proposal per Offeror. Proposals must be received by the Procurement Contracting Officer (PCO) and Buyer, no later than the date and time specified in Block 8 on the face page of the RFP. However, Offerors are requested to submit Volume III, Past Performance Information, so that it is received ten (10) calendar days prior to the required due date for proposals. Failure to submit Volume III by the earlier date will not result in Offeror disqualification.

B. Communications:

The PCO and the Buyer are the sole points of contact (POCs) for this acquisition. Address any questions or concerns you may have to these individuals.

Skye Barnard (PCO) Jessica Boyles (Buyer) skye.barnard@us.af.mil jessica.boyles.1@us.af.mil

Exchanges of source selection information between Government and Offerors will be controlled by the PCO and the Buyer. Email may be used to transmit such information only if the email can be sent encrypted and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. 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. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/PCO identified above prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). Otherwise, source selection information will be transmitted via DoD SAFE at https://safe.apps.mil/about_new_request.php. Contact the POCs above for directions on utilization of DoD SAFE. When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

All electronic copies shall be submitted in a format readable and searchable by Adobe Acrobat and/or Microsoft Word 2016 or newer (.docx), except where otherwise specified. Ensure all graphics (including tables, charts, and foldouts) in the proposal’s electronic version are pasted into the proposal (do not paste as picture only).

L-900. INSTRUCTIONS TO OFFERORS

Offeror shall coordinate with the POCs listed above a minimum of five (5) business days prior to proposal submittal to ensure submission process goes smoothly and the proposal is received by the due date.

II. Volume Organization

A. General:

Proposals shall be submitted to the Government in four (4) separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 1 Completed RFP (Cross Reference Matrix) II 50 1 Factor I and II: Technical/Technical Risk III N/A 1 Factor III: Past Performance (Except as instructed for Past Performance Information sheet paragraph II.D.8)

IV N/A 1 Factor IV: Cost/Price Proposal

1. Format Requirements: In addition to the page limitations set forth above, proposal volumes shall comply with the following format:

1.1 Each volume shall be marked with the RFP number, the Offeror’s name and address, and the number of the Volume (i.e., I, II, III, etc.). Proposals shall be in the English language and all monies shall be proposed in United States dollars.

1.2 Text shall be Times New Roman and no smaller than a font size of 12 with a paper size of 8 1/2” X 11”. Charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets may use a minimum of a font size 9 and shall be clear and readable by a reasonable person, without magnification and shall not be greater than 11” x 17”. Any page 11” x 17” will be counted as two

(2) pages. All text shall be Times New Roman. Each volume within the proposal shall be separately and clearly identified. Margins shall be no smaller than 1 inch on all sides and each page within a volume shall be numbered consecutively. Elaborate formats or color presentations are not desired or required. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

1.3 The page limitations shall be treated as maximums and include any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any cover page, table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation or sent back to the Offeror. One cover page is allowed per volume, totaling four (4) cover pages for the full proposal. Anything over one cover page per volume will not be read.

1.4 Page limitations may be placed on responses to Evaluation Notices (ENs), if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to Offerors or on the EN form itself.

1.5 Each page containing proprietary information should be so marked.

1.6 Each page, including attachments, shall contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

1.7 All portions of the proposal shall be searchable for text in the host program. This includes tables, foldouts, graphics, and figures.

1.8 Block 12 of the front page of the solicitation provides a period of 180 calendar days to award this contract. All proposals shall be valid for this duration. If a proposal states that its validity is less than this duration, it may be found to be noncompliant and may be rejected.

1.9 Cross Referencing: Volumes shall be written on a stand-alone basis so that their contents can be evaluated without cross-referencing to other proposal volumes. Information required for proposal evaluation that 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.

1.10 Table of Contents: Each volume shall contain a detailed table of contents to delineate the titled paragraphs and subparagraphs within that volume. The table of contents shall be hyperlinked to the corresponding material within each volume. Tables of contents do not count against the page limitations for their respective volumes.

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

1.12 Assumptions/Exceptions to Solicitation Requirements

At the beginning of each Volume, Offerors will identify any assumptions/exceptions to the requirements of the solicitation applicable to that Volume. Each assumption/exception to the solicitation 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 assumption/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 shown below.

Solicitation Assumptions/Exceptions Format Example

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale Impact

PWS,

Solicitation, Section, etc.

Applicable Section, Page and Paragraph Numbers

Identify the requirement or portion to which the assumption/excepti on is taken. Specify if it is an assumption or exception.

Provide supporting rationale for the assumption/exception.

Describe how the assumption/exception differs from the solicitation requirement.

Describe the impact, if any, on the requirements.

2. Section L Attachments:

L-1 Past Performance Information Sheet L-2 Consent Letter L-3 Client Authorization Letter L-4 Past Performance Questionnaire L-5 Cross Reference Matrix L-6 TEP Workbook L-7 Sample Repair List

B. Volume I, Completed RFP

1. General: Volume I, Completed RFP, shall consist of the completed and signed RFP, to include any amendments issued, cover page, and a table delineating any exceptions/exceptions taken to the RFP terms and conditions with accompanying rationale. Complete Blocks 12 through 18 of the SF 33. A signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. However, Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. Offerors shall ensure that all clauses and provisions that require “fill in” information are appropriately completed.

2. Format:

2.1 Organize Volume I as follows:

• Cover Page (not to exceed 1 page)

• Company Summary (not to exceed 1 page)

• Table of Assumptions/Exceptions (for this volume IAW para 1.12 above)

• Completed and signed RFP to include any amendments and fill in clauses

• Cross Reference Matrix

• Joint Venture Agreement Summary (not to exceed 1 page, if applicable)

3. Cross Reference Matrix: The Offeror shall fill out the cross reference matrix at RFP Attachment L-5 indicating where in its proposal the information can be found as it relates to the RFP. The cross reference matrix is in excel format. Offeror shall fill out the Excel as directed in the attachment and return in Excel format. The cross reference matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements document Performance-Based Work Statement (PWS), Section L (Instructions to Offerors), and Section M (Evaluation Basis for Award). The cross reference matrix will help an Offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Additionally, the matrix does not disclose details as to the manner by which the Government intends to evaluate the Offeror’s proposals for award, Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

4. Company Summary: Company summary shall include:

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

4.2 Company/Division Address, Identifying Codes, and Applicable Designations – Provide the Offeror’s company/division's address; Commercial and Government Entity (CAGE) code;

DUNS number; size of business (large or small); and labor surplus area designation (if an Offeror is located in the United States – if located outside of the United States no labor surplus area designation is needed). This same information must be provided if the prime contractor (Offeror) 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, of the prime contractor (offeror), and the percentage of work to be performed at each location.

5. Joint Venture Agreement: If a joint venture arrangement exists for this acquisition, the Offeror shall provide a summary of the joint venture agreement that is signed and dated by all joint venture members. This shall not exceed one (1) page.

C. Volume II, Technical/Technical Risk Proposal

1. General: The written technical/technical risk proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. 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 the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the Offeror’s technical/technical risk proposal.

2. Format:

2.1 Organize Volume II as follows:

• Cover Page (not to exceed 1 page)

• Table of Assumptions/Exceptions (for this volume IAW para 1.12 above)

• Table of Contents

• List of Drawings/Tables/Graphs/Figures/Charts

• Specific Content outlined in paragraph C.3

• Glossary

2.2 The Technical/Technical risk proposal shall address the Technical factor, its subfactors and elements listed below:

• Subfactor 1: Technical Approach and Capability o Sample Task #1 – Repair and Return (R&R) o Sample Task #2 – Engineering and Technical Services (E&TS) o Sample Task #3 – Diminishing Manufacturing Sources and Material Shortages

(DMSMS)

• Subfactor 2: Program Management o Small Business Participation o Management and Organizational Structure o R&R Execution Plan o Web-Based Management System o Risk Management Plan

3. Specific Content: The following information shall be provided in the written technical/technical risk proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M-900, Evaluation Basis for Award.

The written technical proposal shall address each of the following subfactors to describe the Offeror’s proposed approach to performing the requirements set forth in the PWSs. For each subfactor, the Offeror shall identify risks, if any, associated with the proposed approach and actions the Offeror will take to mitigate the identified risks. If no risks/mitigations are identified in the Offeror’s proposal, it indicates the Offeror does not consider there to be any risk associated with their proposed approach.

3.1 Subfactor One – Technical Approach and Capability: Offeror shall provide the requested information or describe the Offeror’s capability as instructed.

3.1.1 Sample Task #1 – R&R: Offeror shall provide details of its capability to perform Repair and Return (R&R) IAW the R&R PWS. The below paragraphs detail what, at a minimum, shall be included in the response.

3.1.1.1 Locate Repair Sources

Offeror shall identify a source of repair and provide proof of source repair qualification (R&R PWS para 4.2) for each part listed on the Sample Repair List (Attachment L-7) or state why a source of repair has not been identified. If a source of repair is unable to be located, Offeror shall provide details of its efforts to locate a source. Offeror can list itself as a source of repair.

3.1.1.2 Repair Process

Offeror shall describe its repair and return process from receipt of repair request to shipment after completion of repair IAW R&R PWS. Offeror shall provide a flow diagram of the entire process with estimated timelines for each step in the process, excluding the time required for the actual repair. At a minimum, the process shall include:

a. If using subcontractors, identify which position in the Offeror’s team will perform the overall subcontractor repair and return management.

b. Detailed description of how repair and return sources of repair will be managed. (R&R

PWS 3.1.2-3.1.4)

c. How sources of repair will be identified and selected

d. How parts will be shipped and tracked to and from the repair sources

e. How parts will be tracked and accounted for during the repair process

f. Describe oversight processes the Offeror will implement to ensure parts are repaired and returned in a timely manner in order to meet schedule requirements.

3.1.2 Sample Task #2 – E&TS: Offeror shall provide details and demonstrate its capability to perform Engineering and Technical Services (E&TS) IAW the E&TS PWS, by providing its proposed approach to the following fictitious new mounting bracket situation:

A new Line Replaceable Unit (LRU) has been selected to replace an existing LRU in the F-16 forward equipment bay. The new LRU cannot use the existing mounting bracket. Relevant technical data on the new LRU, old LRU and forward equipment bay would be provided by the Government. The mounting bracket shall match the form and function but not fit of the existing mounting bracket as the fit must change to account for the new LRU.

The Offeror shall describe its proposed process to complete a minor modification on the fictitious new mounting bracket. The process shall demonstrate the Offeror’s understanding of systems engineering and ability to work through the whole process of a minor modification.

Design specifics are not required. At a minimum the process must include:

a. Engineering Services - to include reviewing, formalizing, and incorporating F-16 SPO approved engineering and technical solutions into country specific F-16 aircraft.

b. Minor Modification - to include development, testing, materiel purchase and delivery, kit proofing, implementing deficiency resolutions found in kit proof, and installation with an Offeror provided Contractor Field Team (CFT).

3.1.3 Sample Task #3 – DMSMS: Offeror shall demonstrate its capability to perform Diminishing Manufacturing Sources and Material Shortages (DMSMS) work IAW the DMSMS PWS by providing its proposed approach to the following fictitious DMSMS situation:

A fictitious LRU flown on the F-16 suffers from DMSMS. The LRU has a microchip that will no longer be produced. The requirement for this LRU remains essential to FMS partners. The LRU interfaces with multiple systems and includes minimal software. The LRU is repairable;

however, multiple parts within the LRU suffer from obsolescence which impact repairs.

a. DMSMS Process - The Offeror shall describe its proposed process to analyze the DMSMS Fictitious Situation. The process shall demonstrate the Offeror’s understanding of DMSMS and its ability to analyze and present courses of action to resolve a DMSMS issue. At a minimum the process must demonstrate:

• Understanding of the DMSMS issue (DMSMS PWS para 2.1 and 2.2)

- Understanding of the origin of DMSMS issues

- Possible interface related issues

• Analysis of the DMSMS issue in order to establish recommended courses of action.

- Determine needed information to solidify potential courses of action

- How to obtain needed information

- Present recommended courses of action

3.2 Subfactor Two – Program Management: Provide the requested information to meet the following program requirements:

3.2.1 Small Business Participation: Offeror shall describe their Small Business Participation approach to address the goals within Basic PWS para 5.2.5. The Small Business Participation approach shall also include the extent to which such firms are specifically identified in proposals and the extent of commitment to use such firms. The Small Business Participation approach is not to be confused with an Offeror’s Small Business Subcontracting Plan (as required by 52.219- 9).

3.2.2 Management and Organizational Structure: Offeror shall provide its proposed Organizational Structure and Management narrative that describes the proposed organizational structure and personnel necessary to ensure management and personnel resources are provided to successfully accomplish PSI requirements (Basic PWS para 3.1.2, R&R PWS para 3.1). Provide, at a minimum:

a. Organizational Structure detailing:

• Management structure, line(s) of authority, chain(s) of command, including joint venture partners, teaming partner, and critical subcontractors (as defined in Section L

D.III.2).

• Clear lines of authority between management, personnel, and critical subcontractor personnel

• Clear paths of communication across all IPTs, locations, critical subcontractors and the Government

• Teaming arrangements that are currently in place or proposed

b. Explanation of procedures that will be implemented to proactively manage and monitor subcontractor, teaming partner, and associate contractor relationships to ensure execution of all PWS requirements in a manner that meets contract requirements.

c. Explanation of functional relationships, roles and responsibilities, and any pertinent events or milestones, to ensure effective processes critical to execution.

d. Communication procedures both within the company and with the Government to demonstrate:

• Responsiveness to Government requests

• Effective problem resolution

• Successful accomplishment of all requirements

e. Responsibilities and authority of the Program Manager (PM) and Contracting Officer.

Proposal shall reflect the PM and Contracting Officer are placed within the corporate structure to ensure the PM and Contracting Officer have visibility to senior decision makers and have sufficient authority, responsibility, and resources to execute the program. In addition, the Offeror shall identify and describe positions that it considers to be key positions for successful contract performance.

3.2.3 R&R Execution Plan: The Offeror's proposal shall include an execution plan describing how the Offeror will be prepared to receive and process orders no later than 30 calendar days after contract award. (R&R PWS para 1.3).

The execution plan shall include the following at a minimum:

a. Any activities and processes required to meet the requirement to be prepared to receive and process orders no later than 30 calendar days after contract award.

b. Standup of Web-Based Management System (R&R PWS para 7)

c. Training on the Web-Based Management System for Government personnel.

d. All key positions filled, and ready to execute including the Offeror’s PM and Contracting

Officer

3.2.4 Web-Based Management System:

Offeror shall provide a detailed description, including functions and capabilities, of its proposed Web-Based Management System IAW in the R&R PWS para 7. The system shall manage and streamline the R&R process from repair request to final shipment to country. The proposed system shall include the following capabilities, at a minimum:

a. Provide secure logistics system access for Government and Contractor personnel. Shall be accessible by all Government personnel identified by Government.

b. Requests and data shall not be user dependent. All users shall be able to access all data and modify all requests.

c. Government shall identify POCs that shall have administrative access to add and remove users.

d. Sort all data and requests by country.

e. Submit/cancel repair requests and receive responses (PWS para 4.3).

f. View current status of individual repairs (by country) per CDRL monthly status report

(CDRL B004).

g. Generate CDRL deliveries for Status and Cost/performance (CDRL B005)

h. Generate reports, including ad hoc reports with most recent data.

i. Submit Part Number Addition Requests. (R&R PWS para 4.6.1)

j. Ability to access the most current/updated repair table. (R&R PWS para 4.6)

k. Exporting data to Microsoft Office suite.

l. House and make accessible all training material. (R&R PWS para 7.2).

m. House and collaborate on documents and management activities including but not limited to action items, PMR slides/agenda/minutes, etc.

3.2.5 Risk Management Plan: Offeror shall provide a Risk Management Plan that describes a practical and reasonable approach to managing risk. The plan shall include the identification and mitigation of the Offeror’s five (5) highest rated risks that impact schedule, performance, or cost control related to compliance with the requirements of the PWSs and the execution of the overall program. Of the five (5) risks identified, at least one (1) risk shall address one (1) of the following: loss of source of repair, source of repair quality, source of repair schedule, or compliance with contractual requirements. (Basic, R&R, E&TS, and DMSMS PWSs).

D. Volume III, Past Performance

1. Format: Organize Volume III as follows:

• Cover page (not to exceed 1 page)

• Table of Assumptions/Exceptions (for this volume IAW para 1.12 above)

• Table of Contents

• Past Performance Information Sheets (PPIS) (Attachment L-1)

• Consent Letter executed by each critical subcontractor, teaming partner, and joint venture partner, as applicable, authorizing the release of past performance information to the Government. A sample consent letter is provided in Attachment L-2. A sample client authorization letter for release of customer information is provided in Attachment L-3.

2. General: The Offeror shall submit Present and Past Performance Information for itself and any joint venture member, as well as each proposed critical subcontractor in accordance with the format contained in the “Past Performance Information Sheet” (RFP Attachment L-1) and the following paragraphs. A critical subcontractor is defined as an entity (subcontractor and/or teaming partner), other than the Offeror itself that will perform centralized receiving, shipping, and management of overall asset movement.

3. Past Performance Format: A cover page shall be provided for this volume, describing the proposed role of the Offeror, any joint venture member, teaming partner, and any critical subcontractors (nature of work and percentage of overall work to be performed).

Cover page information must clearly communicate that proposed critical subcontractor(s) meet the definition of a critical subcontractor established above.

Efforts submitted for proposed critical subcontractors not meeting the established definition will not be evaluated. Each Offeror/joint venture shall complete a separate Past Performance Information Sheet for four (4) active or completed contracts (with at least one year of performance history) in the past five (5) years from the issuance date of the RFP, that the Offeror/joint venture considers relevant in demonstrating its ability to perform the proposed effort. If the total number of such contracts exceeds four (4), each Offeror/joint venture member shall address its four (4) recent and most relevant contracts. No more than four (4) Past Performance Information Sheets shall be submitted for the Offeror/joint venture. Relevancy is defined in Section M paragraph II.D.4.

For each critical subcontractor included in the Offeror's proposal, a Past Performance Information Sheet for two (2) of their recent and most relevant contracts shall also be included.

The Offeror's/joint venture member’s or critical subcontractor’s present and past performance information may include data on efforts performed by other predecessor companies, affiliates, divisions, or corporate management. If such was provided for evaluation, the Offeror’s past performance volume shall describe the resources the company, affiliate, or division will provide the Offeror for the instant proposed effort, such as workforce, management, facilities, or other capabilities demonstrating direct and meaningful involvement in the performance of the instant proposed effort. The Past Performance Information Sheet shall clearly indicate the division or corporate organization that performed or is presently performing the contract identified on the Past Performance Information Sheet. Contracts submitted may include those with the Federal Government, state and local governments or their agencies, and commercial customers.

4. Ordering Type Contracts Submission: If the contract the Offeror is submitting is an ordering type contractual vehicle (for example, including but not limited to an Indefinite Delivery “D” type contract per FAR 16.5), only after issuance of a delivery/task order does performance occur. Given this, an individual order (or series of orders) under the basic ordering contractual vehicle shall be submitted, in lieu of just the basic ordering contract itself. All information provided to the Government, for an ordering type contractual vehicle, shall be at the order level (i.e., a delivery/task order).

When determining what order (or series of orders) to submit for evaluation, please reference Section M, Paragraph II.D. for details on how the Government will evaluate each submitted effort for recency, relevancy, and quality of performance. In order to achieve optimal programmatic/logistical scope and magnitude of effort and complexities, as described in Section M paragraph II.D.4 Note and 4.1, the Offeror should consider submitting a series of orders, if possible. However, a series of orders should only be submitted if the series of orders is for continuous work of the same or similar scope demonstrating relevancy to the instant acquisition.

Not all ordering type contractual vehicles will have series of orders that meet these criteria. In this instance, only the single order demonstrating relevant technical scope should be submitted for evaluation.

When submitting an individual order (or series of orders) under an ordering type contractual vehicle, it is important that the Offeror’s past performance information be accurate, complete, and in the correct format. If the information is not submitted in the correct format, the Government will not be able to evaluate the effort for recency, relevancy, and quality. There are specific places for submission of this information in the Past Performance Information Sheet RFP Attachment L-1. Please ensure the information submitted, in the Past Performance Information Sheet RFP Attachment L-1, is for each order (or series of orders), in lieu of just the basic ordering contract itself. This includes but is not limited to information such as the dollar value, period of performance, quantity produced/managed, and type and complexity of data deliverables, for each order or series of orders. See paragraph 4.1 for further information on how to submit series of orders.

4.1 Series of Orders: When submitting a series of orders for evaluation, the Offeror should list the orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in the Relevancy Definitions in Section M paragraph II.D.4. Per the Note in Section M paragraph II.D.4, Relevancy consists of not only technical complexities, but also programmatic/logistical considerations. The programmatic/logistical considerations include dollar value, length of effort, quantity produced, and type and complexity of data deliverables. If an Offeror submits a series of orders for evaluation, the following information shall be submitted for the series of orders: total dollar value of each order, period of performance dates of each order, total quantity produced on each order, and the type and complexity of data deliverables for each order. The total dollar value of each order in the series of orders shall be added up to calculate the Total Dollar Value to be used in the evaluation of the submitted series of orders.

The total period of performance of each order in the series of orders shall be added up to calculate the Total Period of Performance to be used in the evaluation, for the submitted effort.

The total quantity produced on each order in the series of orders shall be added up to calculate the Total Quantity Produced to be used in the evaluation of the series of orders. The type and complexity of data deliverables provided for each order in the series of orders shall be evaluated as a whole for the series of orders.

Caution: All orders within the series of orders, being submitted, should be for the same continuous work of the same or similar scope demonstrating relevancy to the instant acquisition.

The Government reserves the right to request additional information from the Offeror or POCs provided to verify that the series of orders is for the same continuous work of the same or similar scope.

5. Key Personnel: Offerors, joint venture members, or critical subcontractors that are newly formed entities (in existence less than three (3) years from the issuance date of this solicitation) who either have no prior contracts or do not possess relevant corporate past performance, but have key personnel with relevant past performance while employed by another company, may demonstrate the performance of such key personnel by submitting Past Performance Information Sheets for four (4) of their recent and most relevant contracts under which such key personnel performed the same role being proposed on the instant acquisition and this performance occurred during the past five (5) years from the issuance date of this solicitation. Note, however, that the quality of the key personnel’s performance under the submitted contract must be able to be verified by the Past Performance Team in order to be considered in the assessment of confidence.

Any such key personnel must already be employed by the Offeror /joint venture member or, in the case of a critical subcontractor, must already be employed by the critical subcontractor; a letter of intent to hire does not constitute employment.

6. Subcontractor/Teaming Member Consent Letter: In addition to the information provided in the Past Performance Information Sheet (RFP Attachment L-1) for each entity as required above, the Offeror must submit a consent letter executed by each of its proposed teaming member(s) and/or critical subcontractors authorizing release of adverse past performance information to the prime Offeror to allow the prime Offeror an opportunity to respond. A sample Subcontractor/Teaming Partner Consent Letter is attached to this RFP (see RFP Attachment L- 2). The consent letter shall be completed by the team member(s) and/or critical subcontractors identified in your proposal. The completed consent letters shall be submitted as part of your Past Performance Volume III.

7. Small Business Compliance in Past Performance Efforts: On the four (4) contracts submitted in Volume III, Past Performance, include relevant information in the Past Performance Information Sheet concerning the Offeror’s/joint venture member’s and critical subcontractor’s compliance with FAR 52.219-8, Utilization of Small Business Concerns and FAR 52.219-9, Small Business Subcontracting Plan, if these clauses are or were contained in the contract.

(Please note that FAR 52.219-8 does apply to ALL businesses, whereas FAR 52.219-9 only applies to large businesses.) When subcontracting possibilities existed on the contracts submitted by the Offeror/joint venture member and critical subcontractor, address whether or not the Offeror/joint venture member and critical subcontractor awarded subcontracts to small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the Offeror/joint venture member and critical subcontractor’s policy to utilize small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance.

8. Past Performance Information Sheet: The Offeror/joint venture member or critical subcontractor, if applicable, shall focus its Past Performance Information Sheet responses so that they clearly correlate present and past performance with the requirements of this RFP. The Past Performance Information Sheet responses must clearly describe the relevance of the effort to the work proposed (See paragraph J.2, Relevancy Table of the Past Performance Information Sheet).

The answering space on the Past Performance Information Sheet may be expanded so that the filled-in Past Performance Information Sheet for each relevant contract covers no more than six

(6) 8 ½ x 11 inch pages. Offeror shall not alter or delete from the contents currently on the sheet.

Offeror shall add to the contents to provide the needed information. Provide the most current information for the POCs identified on the Past Performance Information Sheets. At least two of the following (in descending order of availability) should be identified as current POCs on the Past Performance Information Sheets:

(a) Procuring Contracting Officer/Contract Negotiator or equivalent

(b) Program/Project Manager, or equivalent

(c) Administrative Contracting Officer/Contract Administrator or equivalent

(d) Other (As specified in your Past Performance Information Sheet)

If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the Past Performance Information Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the Past Performance Information Sheet 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 Contractor Performance Assessment Report System (CPARS), if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here.

9. Past Performance Questionnaire: The Present/Past Performance Questionnaire (see RFP Attachment L-4) will be one means used by the Government to obtain present/past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the Offeror(s). For each of the four (4) submitted contracts found to have some relevance to the instant acquisition, the Past Performance Team will contact the points of contact identified in the Past Performance Information Sheet(s). A telephone interview will be conducted utilizing the Present/Past Performance Questionnaire (see RFP Attachment L-4). Offeror will not be penalized if the entities do not respond despite the Government’s best effort.

Once the Present/Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered source selection sensitive and shall not be released to you, the Offeror. Therefore, any exchange/contact between the Offeror/joint venture member and/or critical subcontractor and its own POCs regarding comments made on the questionnaire is not permitted.

10. Client Authorization Letter: In the event that commercial contracts are presented as present/past performance sources of information, a client authorization letter shall be issued to those commercial POCs requesting/authorizing them to complete a Present/Past Performance Questionnaire. A sample client authorization letter is attached to this RFP (see RFP Attachment L-3). The Offeror is required to send the client authorization letter(s) to each POC on commercial contracts. A separate copy of client authorization letter(s) for each commercial contract shall be included in the Offeror’s Present/Past Performance submission for the Government’s use.

11. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the Past Performance Information Sheets or in the Offeror’s Present/Past Performance Volume. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and through other sources, other than those listed within the Past Performance Information Sheets.

E. Volume IV, Cost/Price Proposal The purpose of this volume is to assist the Offeror in submitting other than certified cost or pricing data that is required to evaluate the price reasonableness, balance, and Total Evaluated Price (TEP) of the offeror’s proposed cost/price. The price evaluation criteria as defined in Section M of the RFP will be assessed from the information provided by the offeror in the Cost/Price Volume. Compliance with these requirements is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Note that proposals which reflect unbalanced and/or unreasonable pricing may be eliminated from competition either on the basis that the offeror does not understand the requirement or has submitted an inadequate proposal. The burden of proof for credibility of proposed costs/prices rests with the Offeror.

The Cost/Price Volume shall be organized according to the following general outline:

Section Title Table of Contents 1 TEP Workbook (Attachment L-6) 2 Basis of Estimate (BOE) 3 Estimating Methodology Listing of Abbreviations and Acronyms (used within the Cost/Price Volume)

1. General

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

1.2. Cost or Pricing Data Requirements: IAW FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the Offeror shall be required to submit additional cost or pricing data. Data shall be provided IAW FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the Offeror shall be required to submit additional cost or pricing data.

1.3. Rounding: All dollar amounts provided shall be rounded to the nearest dollar, except all labor rates shall be rounded to the nearest penny.

1.4. Data deliverables/Contract Data Requirements Lists (CDRLs) will not be separately priced.

2. Total Evaluated Price (TEP), Section L, Attachment 6:

2.1. The TEP will be the sum of:

- Administrative Price Per Repair (FFP) x Notional number of Repairs.

- Fully Burdened Labor Rates (FFP) x Notional number of Hours.

- Repair (CRNF).

NOTE: Travel (CLIN 2000) and Material (CLIN 4000) will not be proposed/included in the TEP but will be proposed and negotiated as needed at the order level.

2.2. The TEP will be computed for evaluation purposes only and will not become part of the resulting contract. The Administrative CLIN price and direct labor rates (along with their associated indirect costs and fees) will be incorporated into the resulting contract. The Government will use the rates within these worksheets to price future tasks/modifications/awards.

2.3. TEP Workbook: Offerors shall appropriately populate the indicated pricing and cost cells specified in the TEP worksheets, IAW the instructions below and in the worksheets themselves.

This workbook is provided in Excel format. Offeror shall fill out the excel workbook and return it in Excel format.

2.3.1 TEP Worksheet: No Offeror input. The TEP Worksheet will auto-populate from the Offeror’s inputs into the other worksheets. The worksheet will not show a total price until the Government inputs the notional hours for evaluation purposes. The notional hours shall not be disclosed to the Offerors.

2.3.2 Administrative Fee Worksheet (FFP): Offeror shall populate a Firm Fixed Price (FFP) for each year of this CLIN. This CLIN will encompass all management associated with the processing and accomplishment of R&R requirements, to include overall R&R program management and profit. The administrative fee shall be fully burdened and will be charged per asset on each R&R order. The price on this worksheet will be incorporated into the resulting contract.

2.3.3. Fully Burdened FFP Labor Rates Build Up Worksheet: Offeror shall populate hourly labor rates for all labor categories (LCATs) that include direct labor costs, overhead costs, general and administrative expenses, and profit. Offeror shall submit one rate per labor category.

3. Basis of Estimate (BOE)

3.1. The Offeror shall provide the basis of the proposed labor rates, e.g., actuals/current individual salaries, Forward Pricing Rate Agreement (FPRA), Forward Pricing Rate Proposal/Submission (FPRP/S), labor survey, etc.

4. Estimating Methodology

4.1. Estimating System. The Offeror shall provide a summary description of your standard estimating system or methods. Provide a summary description of your purchasing system or methods. Identify deviations (if any) from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your estimating and purchasing systems and provide evidence of such approval. Provide a summary description of your pricing methodology as it pertains to this acquisition. Also, identify any deviations from your standard procedures in preparing this proposal.

4.2. Accounting System. The Offeror shall provide evidence of accounting system approval. If the offeror does not currently have a Government approved accounting system, the offeror shall complete a Pre-Award Accounting Checklist (http://www.dcaa.mil/Home/Preaward) and send it to the PCO as soon as practicable after solicitation release, but no later than the due date for proposals specified in the RFP, for audit initiation. The Offeror shall identify any deviations from its standard accounting procedures in preparing this proposal.

4.3. Pricing Assumptions. Offeror shall summarize all significant pricing assumptions, scope limitations, and/or qualifications of the cost/price proposal. List exceptions to any ground rules or assumptions provided in the solicitation and each qualification to the price volume, if any.

Provide complete rationale for any exceptions. If the offeror takes exception to the required proposal validity period of 180 days, rationale for that exception shall be included in the cost/price volume (para A.1.8).