2nd Draft RFP Appendix J DRAFT_C20_C37 CLS Addendum 52.212-1.pdf

ADDENDUM TO FAR 52.212-1 - INSTRUCTIONS TO OFFERORS (ITO)

FA8134-23-R-B002

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS

1.0. Program Structure and Objective

The Government plans to award a single contract for C-20G, C-37A, and C-37B Contractor Logistics Support (CLS) program. The program will primarily include mission essential CLS for thirteen (13) Gulfstream GV (designated C-37A), twelve (12) Gulfstream G550 (designated C- 37B) and three (3) Gulfstream GIV (designated C-20G) Commercial Derivative Aircraft (CDA).

This program supports the United States (US) Air Force (USAF) C-37A and C-37B fleet aircraft, the US Naval Reserve (USNR) C-37A, C-37B, and C-20G fleet aircraft, US Army (USA) C-37A and C-37B fleet aircraft, US Coast Guard (USCG) C-37A and C-37B fleet aircraft, and the US Marine Corp (USMC) C-20G fleet aircraft, hereafter referred to as “Covered Aircraft”. The scope of Full CLS includes, but is not limited to, operation of a single Contractor Operated and Maintained Base Supply (COMBS) at each operating site, Organizational-level maintenance at each operating site, Depot-level maintenance (including scheduled and unscheduled maintenance, depot field teams, engine/auxiliary power units (APU) repair and overhaul), and Field Service Representatives. Partial CLS, required where other entities perform CLS functions, may include any combination but not all of full CLS requirements. Specifics and other task areas are specified in the Performance Work Statement (PWS) for the contract. The Covered Aircraft are home stationed at the following locations:

• Joint Base Andrews, MD (JBA)

• Ramstein Air Base, Germany (RMS)

• Joint Base Pearl Harbor Hickam, HI (JBPHH)

• Marine Corp Base Hawaii, HI (MCBH)

• Naval Base Ventura County - Pt. Mugu, CA (NBVC)

• Ronald Reagan Washington National Airport, DC (DCA)

Unless specifically called out separately, the term C-37 aircraft encompasses both C-37A and C- 37B aircraft; the term C-20 is used interchangeably with the full C-20G variant nomenclature.

1.1. Award will be made on the basis of best value utilizing Tradeoff Source Selection Procedures. Award will be made to the contractor that provides the best value to the Government over the entire Period of Performance (PoP). Tradeoffs will be made only between past performance and price among those Offerors who have been determined technically acceptable.

Award will be made to the Offeror who is deemed responsible in accordance with the Federal Acquisition Regulation (FAR) Part 9, as supplemented, whose proposal conforms to the solicitation’s requirements (to include all stated terms, conditions, representations, certifications, and all other information required by FAR 52.212-1 and its Addendum of this solicitation) and is judged, based on the evaluation factors, to represent the best value to the Government. This may result in an award to a higher rated, higher priced Offeror, where the decision is consistent with the evaluation factors and the Source Selection Authority (SSA) reasonably determines that the technically acceptable proposal and superior past performance of the higher priced Offeror outweighs the price difference of lower priced Offerors.

NOTE: Both Federal Aviation Regulations (FAR) and Federal Acquisition Regulations (FAR) are contained within the Code of Federal Regulations (CFR). For clarity, when referencing Federal Aviation Regulations, the reference will be FAA FAR Title 14, and when referencing Federal Acquisition Regulations, the reference will be simply FAR.

1.2. Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) Phase-In Period and one month of the Base Period.

1.3 Contractor Technical Proposal

All or parts of the Contractor’s Technical Proposal may be added to the contract. Should there be any discrepancies between the Technical Proposal and the Performance Work Statement (PWS), the PWS will take precedence unless otherwise approved by the Contracting Officer (CO).

1.4 Supplemental Responsibility Requirements

Facility Clearance Information: The Offeror, and subcontractors working classified requirements with access to classified information, must possess, prior to award, a final facility clearance equal to the highest classification specification (DD Form 254) attached to this solicitation. The Industrial Security Facilities Database (ISFD) will be used to verify final facility clearances prior to award. Offerors who do not have a final facility clearance equal to the highest classification specification (DD Form 254) attached to this solicitation in the ISFD database one business day prior to the Source Selection Authority Decision Brief will be considered non-responsible and will not be eligible for award. Any determination that an Offeror is non-responsible will be IAW FAR Part 9.

2.0. General Instructions

2.1.1. This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. Any Offeror who submits an incomplete package may be considered ineligible for award. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

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

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

2.1.4. The proposal acceptance period is specified on the SF 1449 front page of the model contract/solicitation. The Offeror shall make a clear statement in their submitted SF 1449 of the proposal documentation volume (see ITO Section 6.0) that the proposal is valid until this date.

2.1.5. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

2.2. General Information

2.2.1. Point of Contact

The CO is the sole point of contact for this acquisition. Offerors shall address any questions or concerns to the CO. Written requests for clarification may be sent to the CO at the address located in Block 9 on the SF1449 front page of the model contract/solicitation.

2.2.2. Debriefings

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

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

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in accordance with FAR

15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing.

Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.2.3. Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the System for Award Management (SAM) website at https://sam.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.2.5. Restrictions to Public Disclosure

Certain documents are withheld from public disclosure. These documents will be available through the Bidder’s Library for qualified individuals. Documents are placed into the Bidder’s Library only due to:

a. Proprietary or copyright data that the Government does not have rights for distribution.

b. Unclassified documents containing information that is exempt from mandatory automatic disclosure under the Freedom of Information Act. These documents are marked as For Official Use Only (FOUO) or as Controlled Unclassified Information

(CUI).

c. Documents containing Export Controlled Information. These documents contain technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violations of these export laws are subject to severe criminal penalties.

2.2.6. Bidder’s Library

A Bidder Library will be provided via SAM.GOV. Special access instructions and criteria shall apply for access to SAM.GOV and the Bidder’s Library and data within. Certain documents and information within the documents have been marked as FOUO, CUI, or Export Controlled data.

Access to FOUO, CUI, and/or Export Controlled Data requires an approved registration through the Defense Technical Information Center (DTIC) and the approved DD Form 2345, Militarily Critical Technical Data Agreement. A completed, current, and valid DD Form 2345 shall be required for access.

2.2.7. Oral Presentation

Oral presentations will not be utilized.

2.2.8. Amendments to Solicitation

If this RFP is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the Offeror’s proposal. Any unacknowledged amendments in the Offeror’s proposal will render the proposal ineligible for award.

2.2.9. Submission, Modification, Revision, and Withdrawal of Proposals Proposal packages shall be transmitted to the Solicitation CO via DoD SAFE (safe.apps.mil).

Physical delivery of proposal packages will not be accepted. See ITO sections 2.6 & 2.7.

2.2.10. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the subject line.

2.3. Organization/Number of Copies/Page Limits

2.3.1. The Title Page of each volume shall contain the solicitation number, name, address, telephone, and e-mail address of the Offeror.

2.3.2. A Team List of the Offeror’s primary Point of Contacts shall be submitted in each volume using the format shown in Attachment 2 of the ITO. Include Letters of Intent as an attachment.

2.3.3. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.3 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. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.3. Proposal Organization

Volume ITO Paragraph

Number Volume Title Page Limit

I 3.0 Technical

2.3.1 Title Page (Not included in 75 page limit) 1

2.3.2 Team List (see Attach 2.0 & 3.0) (Not included in 75 page limit)

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and Acronyms Unlimited

3.2.3, 3.2.4, 3.2.5, 3.2.6

Appendices and Attachments Unlimited

3.2.3 3.2.4 3.2.5 3.2.6

Subfactor 1 Program Management Subfactor 2 Supply Support Subfactor 3 Maintenance Subfactor 4 Small Business Participation

75*

II 4.0 Past Performance

2.3.1 Title Page 1

2.3.2 Team List (see Attach 2.0 & 3.0) 5

4.3.1 Past Performance Information Forms (PPIF) (See Attach 1.1)

Request Max 5 pages per contract

4.1.2 Consent Letter (See Attach 1.4) Unlimited

4.1.3 Client Authorization Letters (See Attach 1.5)

Unlimited

4.1.4 Commitment to Perform as Proposed Letter (See Attach 1.6)

Unlimited

4.2 Present/Past Performance Questionnaires (See Attach 1.2)

Tab Only

4.3.2 Relevant Contract Narrative

Request Max 5 pages per contract

4.3.4 Roadmap 2

III 5 Price Volume

5.2 General Information Unlimited

5.4 Volume Organization Unlimited

IV 6.0 Contract Documentation

2.3.1 Title Page (SF1449) 1

2.3.2 Team List (see Attach 2.0 & 3.0) 5

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and Acronyms Unlimited

2.3.2/3.2.3 Team List, Arrangements, and/or Letters of Intent

Unlimited

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

6.1.4 Representations and Certifications (Section K)

N/A

6.3.1 - 6.3.4 Contact Information Unlimited

6.1 Attachments to the Model Contract Unlimited

*The Technical Subfactor page limit is 75 pages. Attachments and appendices are not included in the 75 page Technical Subfactor page limit.

2.3.4. Names

Offerors shall submit volumes with the following file names: Volume I – Technical.docx, Volume II – Past Performance.docx, Volume III – Price.docx with PricingMatrix.xlsx, and Volume IV – Contract.docx. Files provided in .pdf format are also acceptable if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text.

2.3.5. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be considered in the evaluation of the proposal. Page limitations may also be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following:

blank pages, title pages, tables of contents, tabs, indexes, glossaries, appendices, and those noted in the Proposal Organization Chart (Table 2.3) as unlimited.

2.3.6. Pricing Information

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

2.3.7. Cross Referencing

The Technical volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for the technical proposal evaluation, which is not found in the Technical volume, will be assumed to have been omitted from the proposal, and will not be considered in the technical evaluation.

Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity. The Past Performance and Price evaluation will utilize information from each respective volume for the evaluation but may also utilize information from other volumes as well.

The Offeror shall complete the cross-reference matrix provided in Table 2.3.1 that will indicate the corresponding proposal section or location which addresses the referenced item. The Offeror’s cross-reference matrix shall include the proposal reference information as it relates to the instructions, PWS contents, RFP sections, Contract Line Item Number (CLIN), Contract Data Requirements List (CDRL) references (if applicable), and the corresponding proposal section in the section which addresses the reference item as part of Volume I – Technical. The Offeror shall include the completed copy of the Cross Reference Matrix in the Technical Volume. The Cross Reference Matrix does not count as part of the page limit.

Table 2.3.1 Cross-Reference Matrix

Cross Reference PWS Ref Sec RFP Addendum to FAR 52.212 (-1) (-2)

Proposal (Volume & Sec)

Factor 1:

Technical

See Subfactors Below 3.0 2.2

Subfactor 1 – Program Management

PWS 1.1.1, 2.4, 2.4.1,

2.4.2, 2.5, 2.6, 2.8, 2.9, 2.9.2, 2.9.3, 2.15, 2.17, 2.18.1, 2.19, 2.21, 2.21.3, 2.23, 2.27, 3.4, 4.20, 4.20.1, 4.20.2, 4.21, 5.1, and 5.1.1 through 5.1.11

3.2.3 2.2.1

Subfactor 2 – Supply Support

PWS 2.4.1, 3.0, 3.1.1,

3.1.2, 3.3, 3.3.1, 3.3.2, 3.4, 3.5, 3.5.1, 3.5.2, 3.5.3, 3.6, 3.6.1

3.2.4 2.2.2

Subfactor 3 – Maintenance

PWS 2.12.1, 4.2, 4.4,

4.5, 4.5.1, 4.5.4, 4.5.5, 4.5.10, 4.5.15, 4.6, 4.6.1, 4.6.2, 4.7, 4.11,

4.11.1 through 4.11.3, 4.12, 4.12.1, 4.12.2, 4.12.3, 4.12.6, 4.12.9, 4.12.11.5, 4.12.14, 4.12.16, 4.13, 4.16

4.16.1 through 4.16.3, 4.17, 4.17.1, 4.17.2, 4.18, 4.20, 4.21, 4.22,

4.22.1 through 4.22.3, 4.23

3.2.5 2.2.3

Subfactor 4 – Small Business Participation

PWS 2.8 3.2.6 2.2.4

2.3.8. Table of Contents

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.3.9. Tables and Figures

Include an indexed list of Tables and Figures

2.3.10. Glossary of Abbreviations and Acronyms

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

2.4. Page Size and Format

2.4.1. Pages

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

2.4.2. Tables, Charts, Graphs, and Figures

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and shall not exceed 11 x 17 inches in size. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8-

pt. Page line spacing shall be single-spaced. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation.

2.5. Labeling

A cover sheet shall be included in each proposal volume, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. For each proposal volume, the Offeror shall apply all appropriate markings including those prescribed IAW FAR 52.215- 1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.6. Electronic Offers

All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested Offerors must e-mail Tracie Holman (Tracie.Holman@us.af.mil) and Stacey Stewart (Stacey.Stewart.4@us.af.mil) in order to receive a request code to drop-off (upload) files in DoD SAFE. One of the Government Points of Contact (GPOCs) will send an e-mail to the Offeror acknowledging the request for a proposal drop-off code in DoD Safe. The GPOC e-mail acknowledging the request will not be sent to the Offeror after close of business hours, weekends, or on nationally observed holidays. If you do not receive an acknowledgement e-mail from either of the GPOCs after 72 hours, you must send another e-mail. E-mails will not be returned after close of business hours, weekends, or on nationally observed holidays. After the e-mail request for a drop-off code has been sent from the Offeror and the Offeror has received the acknowledgment e-mail from either GPOC, the Offeror will then receive an e-mail from DoD SAFE to drop-off proposals and other requested documents. If the Offeror does not receive the e-mail from DoD SAFE, the Offeror will need to check SPAM and JUNK folders before requesting another drop-off code from the GPOC. The request for drop-off is only valid for 14 days. If the 14 days has expired and the RFP is still open, the Offeror may send another e-mail request for drop-off code to the GPOCs e-mail addresses listed above.

Be advised that classified information is not allowed on DoD SAFE. Any files containing CUI/PII/PHI must be encrypted prior to uploading or by checking the “Encrypt every file” box.

The Offeror is allowed to drop-off one or more files (up to 8GB total). The Offeror may select the box ‘Send me an e-mail when each recipient picks up the files” for documentation purposes.

The GPOC will receive an automated e-mail containing the information the Offeror has entered and instructions for downloading the file(s). The GPOC will have 7 days to retrieve the files submitted in the drop-off. DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours.

All electronic documents and files submitted shall contain the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The Offeror shall submit volumes I through IV in electronic format. Each volume shall be submitted as a separate file. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 365 Word, MS Office 365 Excel, MS Office 365 Power Point, and Adobe PDF.

Note: files must be searchable and able to copy and paste. For amendment purposes to the proposal, the "original" proposal shall be clearly identified.

2.7. Distribution and Delivery

2.7.1. Once the Offeror has uploaded the Offeror’s proposal in its entirety in DoD SAFE, the Offeror shall take a screen shot (Print Screen function) of the Offeror’s DoD SAFE upload confirmation screen showing all the uploaded files included in the proposal submission. The Offeror shall notify Tracie Holman and Stacey Stewart by email that the files have been uploaded and provide a copy of the DoD SAFE completed upload confirmation screen shot. If the proposal files are uploaded in their entirety prior to the proposal closing date and time, and the Offeror has notified Tracie Holman and Stacey Stewart the files have been uploaded (notification is to include the DoD SAFE upload confirmation screen shot has also been provided), the proposal will be considered timely, even if the files are not accessible to the PCO in DoD SAFE until after the proposal closing date and time. If the Offeror fails to notify Tracie Holman and Stacey Stewart by email, the files will be considered timely if they are accessible in DoD SAFE prior to the closing date and time. However, they will be considered late proposals, if they are not accessible until after the proposal date and time.

3.0. Factor 1 – Technical

3.1. General

The Technical Volume should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Addendum to FAR 52.212-2, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

3.2.1. Technical

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

3.2.2. Volume Organization

The Technical Volume shall be organized according to Table 2.3.

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

(1) Title Page

(2) Team List (See Attach 2.0 & 3.0)

(3) Table of Contents

(4) List of Tables and Figures

(5) Glossary of Abbreviations and Acronyms

(6) Subfactor One – Program Management

(7) Subfactor Two – Supply Support

(8) Subfactor Three – Maintenance

(9) Subfactor Four – Small Business Participation

3.2.3. Subfactor One: Program Management (PM)

The Offeror shall provide its approach to managing the C-20 / C-37 CLS program that demonstrates an understanding and capability for establishing and executing the program. As a minimum, the approach shall provide the following essential elements:

a. Program Management Approach – Describe the Offeror’s Program Management approach to establish, maintain, and provide program oversight and risk management to execute CLS support to the C-20 / C-37 fleets. Address Offerors ability to acquire data from the OEMs as required to maintain aircraft, aircraft systems and avionics, and aircraft engines and APUs. (PWS sections 2.4, 2.4.1, 2.4.2, 2.9, 2.15, 2.17, 2.19, 2.21, 2.21.3, 4.20, 4.20.1, 4.20.2, 4.21)

(1) Continuation of Essential Services Plan – Per DFARS 252.237-7023 and 7024(b) (1) and (2), submit the Offeror’s Continuation of Essential Services

Plan as an attachment to the Technical Volume. Describe the Offeror’s approach to establish and maintain the capability for Continuation of Essential Services. (PWS 1.1.1, 2.5)

(2) Describe the Offeror’s approach to establish a real-time (or updated daily), web-based, automated funds management system. (PWS 2.27)

(3) Provide approach for establishing agreements with primary vendors required to support the program after contract award IAW PWS 2.23. Letters of Intent (LOI) for data access/license, Proprietary Information Agreements (PIA), or other evidence of data access for any OEMs other than Gulfstream or Rolls Royce referenced in proposed Program Management approach shall be provided as attachments to the Technical Volume. Evidence of OEM cooperation must be shown, but signatures are not required at this time.

b. Subcontractor Management Approach – Describe the Offeror’s approach to subcontractor management, identifying subcontractors and detailing their portion of effort. (PWS 2.4.2, 2.6, 2.8, 2.9, 2.9.2, 2.9.3, and 2.18.1)

(1) The proposed approach for subcontracting shall clearly describe subcontract arrangements, relationships, roles, and work to be performed by subcontractors.

c. Phase-In Transition Planning – The Offeror shall submit a Phase-In Transition Plan

(PWS 5.1.2) as an attachment to the Technical Volume which demonstrates a disciplined approach to establishing the full C-20 / C-37 CLS capability by the beginning of full contract performance. The approach must include development of a critical path analysis of transition milestones which shall be reflected in the Phase-In Transition Plan. As a minimum the Phase-In Transition Plan shall include: (PWS 2.9, 3.4, 5.1, 5.1.1 through 5.1.11)

(1) Personnel Plan – Provide a proposed Contractor organization chart and detailed personnel plan and timeline for the contract including all Contract operating locations (does not include depot maintenance centers). Provide details on position titles, minimum experience, special qualifications, licenses, and any required training for each position. Incorporate hiring timelines into the Phase-In schedule. (PWS 2.9, 5.1.5)

(2) Resources – Address plans and provide a detailed schedule to establish initial materials strategy, support and test equipment strategy, furnishings, and other items necessary to establish capability at the fleet support center and each operating location to meet contract performance requirements no later than the start of full contract performance. Incorporate resource timelines into an Phase-In schedule. As there is no direct sustainment support during the transition period, no direct charges for sustainment material acquisition shall be authorized as part of the initial period. These shall be incorporated into the COMBS Cost per Flying Hour rates and/or specific maintenance CLINs, as appropriate. (PWS 3.4, 5.1.10)

d. Security – Describe the Offeror’s approach to meet security requirements of 32 CFR

Part 117, National Industrial Security Program Operating Manual (NISPOM) and the

DD254. (2.4.1.1, 2.9.2, 2.18.1, 2.18.2, 2.18.4, 2.18.10, 3.8.4, 4.19, 4.19.1, 4.19.2)

3.2.4. Subfactor Two: Supply Support

The Offeror shall provide, in the proposal, an approach for resource management for the C-20 / C-37 CLS Programs. As a minimum, the approach shall provide the following essential components:

a) Parts/Inventory Management – The Offeror shall submit a Material Management Plan (PWS 2.4.1) which demonstrates a disciplined approach to providing Supply Support requirements of the C-20 / C-37 CLS Program. The approach must include, at a minimum, C-20 / C-37 spares support methodology, parts obsolescence management, Aircraft on Ground (AOG) worldwide parts support, and Government Furnished Property (GFP) inventory management. (PWS 3.0, 3.1.1, 3.1.2, 3.4, 3.5, 3.5.1, 3.5.2, and 3.5.3)

b) Support and Test Equipment – Address the capability and plans to source and provide required C-20 / C-37 Support Equipment to include Test Equipment, tools, maintenance aids, and associated equipment for each Covered Aircraft operating location. Provide a planned Contractor Furnished Support Equipment list as an attachment to the Technical Volume for each operating location by name, part or model number, manufacturer, and quantity in an Excel spreadsheet. (PWS 3.6 and 3.6.1)

c) Contractor Operated and Maintained Base Supply (COMBS) Approach – Address strategy and capability to operate and manage a COMBS to source, manage, stock, repair, overhaul and dispose of required spares and repair parts in sufficient quantities or by other agreements by operating location to ensure the ability to maintain the C- 20 / C-37 fleets to PWS performance requirements. (PWS 3.3, 3.3.1, and 3.3.2)

3.2.5. Subfactor Three: Maintenance (MX)

The Offeror shall provide, in the proposal, an approach for meeting the world-wide maintenance requirements for the C-20 / C-37 CLS program. The approach shall reflect a thorough understanding of managing maintenance requirements in accordance with Gulfstream Aircraft Maintenance Manual Chapter 5 and Computerized Maintenance Program (CMP). Provide as a minimum the following essential components:

a. Main Operating Base (MOB) Maintenance – Provide an approach for supporting MOB Maintenance. The approach must include, at a minimum, experienced maintenance personnel, scheduled and unscheduled aircraft maintenance, maintenance planning and scheduling, and flight operations support. (PWS 4.2, 4.4, 4.5, 4.5.1, 4.5.4, 4.5.5, 4.5.10, 4.5.15, 4.6, 4.6.1, 4.6.2, 4.7, 4.21, 4.22, and 4.22.1 through 4.22.3

b. Depot Level Maintenance – Provide an approach to support depot level maintenance for all Covered Aircraft. The approach must include, at a minimum, scheduled and unscheduled depot maintenance, depot level maintenance planning and scheduling, depot capacity to support maintenance requirements for the Covered Aircraft, service actions, and warranty management. (PWS 4.12, 4.12.1, 4.12.2, 4.12.3, 4.12.6, 4.12.11.5, 4.13, and 4.23)

(1) Submit a copy of a valid and current FAA FAR Title 14 Part 145 certificated Repair Station with Operations Specifications for each equivalent commercial model Covered Aircraft as attachments to the Technical Volume.

(2) Interior and Exterior Appearance – Provide the approach to aircraft interior maintenance and refurbishment as well as executive paint application at a FAA FAR Title 14 Part 145 certificated facility. Provide a list of planned paint facilities to be used and address their capabilities and experience with executive custom aircraft painting for full strip and paint for the C-20 / C-37 aircraft types. Address aircraft paint protection processes during depot level maintenance. (PWS 4.12.9, 4.12.14, and 4.12.16)

c. Contractor Field Teams (CFT) – Address capability to provide FAA FAR Title 14 Part 145 certificated facility’s qualified depot level CFTs for worldwide repair/recovery of AOG events to include engine replacement. (PWS 4.11, 4.11.1 through 4.11.3)

d. High Value Asset (HVA) Maintenance – Provide the approach to support HVA depot level maintenance. The approach must include, at a minimum, Rolls Royce Corporate Care or equivalent Comprehensive Engine Maintenance Program for C-37, C-20 engine maintenance, Auxiliary Power Unit (APU) maintenance, and Landing Gear (LG) maintenance. The Offeror shall provide an approach to planning and executing engine maintenance IAW the aircraft 10-year depot maintenance plan and the Computerized Maintenance Program (CMP). (PWS 4.1.1, 4.12.1, 4.16, 4.16.1 through 4.16.3, 4.17, 4.17.1, 4.17.2, 4.18, 4.21)

3.2.6. Subfactor Four: Small Business Participation

The Offeror shall provide an approach for Small Business Participation. In addition, the Offeror shall submit a completed Small Business Participation Commitment Document (SBPCD) (ITO Attachment 2.0). Large businesses shall submit a subcontracting plan IAW FAR 19.7, tailored to this contract effort. Small business shall only submit a SBPCD. The Offeror shall describe their small business participation based on total subcontract dollar/value for this contract effort. The Offeror shall include small business Minimum Quantitative Requirement (MQR) of 15% of total subcontract dollar/value.

NOTE: The SBPCD differs from the subcontracting plan requirements IAW FAR 19.7. Also, work to be performed directly by a small business prime offeror shall be evaluated as Small Business Participation. Small business prime offerors shall include their information in the provided SBPCD template as required.

4.0. Factor 2 – Past Performance

4.1. General

4.1.1. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 1.1 of the ITO.

The Past Performance volume shall include a team list, which includes the prime contractor, all significant subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. The Offeror shall describe the portion of effort each team member is proposed to perform in relation to the Factor 1 Technical subfactors including Program Management (Subfactor 1.a – 1.d), Supply Support (Subfactor 2.a – 2.c), and Maintenance (Subfactor 3.a – 3.d), Small Business Participation (Subfactor 4.a – 4.b); Factor 3 Price; and Scope, Magnitude and Complexity. The Government Past Performance Evaluation Team (PPET) evaluates each member of the Offeror’s team for relevancy and performance quality, based on their proposed portion of effort. Therefore, it is important for the Offeror to provide a detailed portion of effort description, in order for the PPET to conduct an accurate assessment. Offerors shall also provide approximate percentages for portion of effort for each team member. In addition, Offerors shall complete the Portion of Effort Matrix provided in Attachment 1.8. for the Past Performance evaluation, the Government will use data provided by the Offeror in the Past Performance volume, as well as data obtained from other sources.

4.1.2. Attachment 1.4 Consent Letter. This letter shall be executed and signed by each subcontractor, teaming partner, and/or joint venture partner. The letter authorizes the release of adverse past performance information to the Offeror so the Offeror can respond to such information.

4.1.3. Attachment 1.5 Client Authorization Letter. For each identified effort for a commercial customer, the Offeror shall submit a client authorization letter authorizing release to the Government of requested information on the Offeror’s performance.

4.1.4. Attachment 1.6 Commitment to Perform as Proposed Letter. This letter shall be executed and signed by the Prime contractor and each Subcontractor. The letter states that, in the event a contract is awarded to the Prime Contractor, the Prime Contractor and Subcontractor (to include teaming partners, and/or joint venture partners) commit to joint contract performance as described in the proposal. A separate letter shall be completed for each subcontractor separately.

If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, the subcontractor references will not be evaluated or considered. In the event the signed letter is not submitted with the initial proposal, but is later submitted during the evaluation, the subcontractor references will be considered at that point.

4.2. Early Proposal Information

4.2.1. Each offeror is requested to submit the Past Performance volume fifteen (15) calendar days prior to the solicitation closing date. The Past Performance volume early proposal information is a request, and not a requirement. Failure to submit early proposal information will not result in offeror disqualification, nor will offerors be penalized.

4.2.2. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (Attachment 1.2) and e-mail it and the Performance Questionnaire Letter (Attachment 1.3) to all points of contacts (POCs) the Offeror has listed in the Past Performance

Information Form (Attachment 1.1). The POCs will complete the questionnaires and forward them directly to the Past Performance Evaluation Team (PPET), (Attn: Tracie Holman). Email address for questionnaires is Tracie.Holman@us.af.mil. RESPONDENTS TO THE QUESTIONNAIRES

SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE OFFEROR.

Offerors shall not follow-up with respondents to ensure they have completed the questionnaires.

The PPET will conduct such follow-up with any POC as necessary.

4.3. Relevant Contracts

4.3.1. The Offeror shall provide Past Performance Information (PPI) on current or previous contracts (or efforts). The PPI shall be completed in accordance with Addendum to FAR 52.212-1, Attachment 1.1, Past Performance Information Form (identified in this document as “PPIF”). The Offeror shall submit PPIFs for contracts which include all or some performance within the past five (5) years, as defined in Addendum to FAR 52.212-2, para 2.3.2.1 Recency Assessment. Request each offeror submit up to three (3) PPIFs for the prime contractor, and up to three (3) PPIFs for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 10% of the total effort, or a contractor who is proposed to perform less than 10% of the total effort but is determined to be performing a critical function.

Significant subcontractors are those relevant and current subcontractors or vendors that meet any of the following criteria:

a. FAA certified aircraft engine, APU, landing gear overhaul to OEM specifications

b. FAA FAR Title 14 Depot Facilities for equivalent commercial aircraft models

c. FAA FAR Title 14 Aircraft Interior/Paint facilities

d. Supply Chain Management

e. Performed more than 10% of total contract value by dollar award (by % of total contract value)

Note: The requested number of PPIFs for the prime and subcontractors are preferences and not requirements. Offerors may submit more than the preferred number if the Offeror believes the extra contracts are needed to fully describe their relevancy. Offerors who submit less than the preferred number of PPIFs are not automatically assigned a “Neutral Confidence” rating. Fewer numbers may be acceptable, if the Government determines there is sufficient information to determine a confidence rating. Request each PPIF not exceed a target of 5 pages, although more or less may be submitted, if necessary and relevant to the C-20/C-37 CLS Program.

The past performance contract is relevant if it is within the same scope, magnitude and complexity as effort defined in the PWS. Simply being another Government contract does not make it relevant.

4.3.2. PPI Relevant Contract Narrative

For each PPIF, the Offeror shall provide a narrative explaining what aspects of the contract is deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate.

Specifically, the narrative should focus on similarities to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude, and Complexity, as defined in Addendum to FAR 52.212-2, paragraph 2.3.2.2, and should be tailored to the proposed portion of effort. Categorize the relevant information into the specific technical subfactors and price assessment used to evaluate the proposal. The narrative may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a Limited or No Confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror shall clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. The Offeror is requested to limit the narrative to a maximum of 5 pages. However, the Offeror may exceed the requested page limit, if determined necessary to fully describe relevancy.

4.3.3. Affiliate companies, sister companies, teaming arrangements, joint venture agreement, etc., will be considered, provided that sufficient documentation is included in the proposal. The Prime contractor must demonstrate that the affiliate will perform significant and critical aspects of the contract if awarded. Proposal documentation should include a copy of the signed arrangement such as documented affiliation, a copy of the teaming agreement, a copy of the joint venture agreement, etc. If the required information is not included in the proposal, the proposed affiliate companies, sister companies, joint venture companies, etc. will not be evaluated or considered.

4.3.4. Organizational Structure Change History

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

5.0. Factor 3 – Price

5.1. In the price volume, the Offeror shall provide the following information in addition to the Pricing Matrix (Appendix G) These instructions are to assist you in submitting information required to evaluate the reasonableness, balance, and realism of your proposed price.

Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

5.2. General Instructions

Information beyond what is required by this instruction shall not be submitted unless the Offeror considers it essential to document or support the Offeror’s price position. All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

5.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition, but may also be determined through other price analysis techniques. The burden of proof for credibility of proposed costs/prices rests with the Offeror. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.). It shall be noted that completeness is one aspect of price reasonableness. For completeness, the Offeror shall provide unit prices and/or rates for all listed items in the Pricing Matrix (Appendix G). If an Offeror’s proposed unit price or rate is zero, then the Offeror shall provide rationale to support the zero dollar/rate entry.

5.2.2. Unbalanced Pricing

The Government will evaluate proposals for balance. The Offeror is cautioned against submitting an offer which exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable or unrealistic prices. For this acquisition, balanced pricing is determined with respect to year-to-year price variances for separately priced CLINs.

Offerors shall provide rationale for any proposed CLIN price increase greater than 5% from one year to another, or any proposed CLIN price decrease from one year to another. Unexplained price variances from year-to-year could suggest unbalanced pricing. It is in the Offeror’s best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

To assist in the determination of balanced pricing, Offerors shall complete the attached Pricing Matrix (Appendix G).

5.2.3. Price Realism

The Government will evaluate proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements and to ensure the proposed price does not pose an unacceptable risk to performance. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc).

5.2.4. Pricing Information Requirements

Price analysis techniques shall be utilized to ensure fair and reasonable pricing in accordance FAR 15.404-1(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process.

In accordance with FAR 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. The Government reserves the right to obtain data as appropriate.

Should the CO determine proposed prices to appear unreasonable or the possibility that an Offeror does not fully understand the requirement, the Offerors may be required to support price reasonableness and/or price realism via other than cost or pricing data.

5.2.5. Rounding

In the Pricing Matrix (Appendix G), all unit prices and labor rates shall be rounded to the nearest cent. Proposed percentages for the material handling/subcontractor and Travel G&A rates are rounded to four places to the right of the decimal.

5.2.6. Total Evaluated Price (TEP)

The TEP is calculated in the Pricing Matrix (Appendix G) as detailed in the Calculation Methodology tab.

5.3. Pricing Support Information

5.3.1. Estimating Techniques and Past Experience

Provide a brief explanation of the methodology used to estimate prices in the development of the Offeror’s proposed pricing. Where price estimates are based on past experience, identify the past experience; explain how the past experience relates to the current effort including similarities and differences and how price data available from the past experiences was adapted to the current effort pricing.

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

5.3.3. Price Assumptions Used in Development of Proposed Pricing All significant assumptions, scope limitations and/or qualifications affecting the pricing proposal shall be addressed and explained. If there are no proposed price assumptions, then state accordingly in Section 2 of the Price Volume.

5.3.4. Labor, Material Handling/Subcontractor, Travel General &…