Attachment_2_-_Section_L_(Revised)_-_22_Jun_16.pdf

FA3002-16-R-0004, Initial Flight Training

Attachment 2

Section L, Instructions, Conditions, and Notices to Offerors

Section L – Instructions to Offerors

1.0 GENERAL INFORMATION

1.1 General

1.1.1 To assure timely and equitable evaluation of proposals, Offeror(s) must follow the instructions contained herein. Offeror(s) are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. The response shall consist of four (4) separate volumes; Volume I - Price Proposal, Volume II -Technical Proposal, Volume III - Past Performance Information, and Volume IV - Small Business Participation.

1.1.2 IAW FAR Subpart 4.803(a)(10), the Government will retain one copy of all proposals. All additional copies of proposals will be destroyed by the Government after contract award.

1.1.3 Submission of offers. Submit signed and dated offers to the office identified in paragraph 1.2.1 below at or before the exact date and time specified in this solicitation.

1.1.4 The Procurement Contracting Officer (PCO) and Contract Specialist (CS) are the sole points of contact for this acquisition. Offerors are responsible for ensuring receipt of any communication by the designated officials. Verification of receipt of communications can be done via email or telephone. Questions and written requests for clarification shall be done via email only. Points of contact (POCs) are:

Mr. Stephen Pritchett (PCO) Mr. Kevin Grant (CS) E-mail: stephen.pritchett@us.af.mil E-mail: kevin.grant.10@us.af.mil Telephone: 210-652-7860 Telephone: 210-652-6904

1.1.5 Minimum Proposal Acceptance Period. The term “acceptance period,” as used in this provision, means the time period available to the Government to award a contract from the date specified in this solicitation for receipt of proposals. The government anticipates awarding this contract in May 2018. This award date and minimum acceptance period is determined by time required to evaluate offeror’s proposals for award and the time required for the apparent successful offeror’s location and operations to successfully complete an Environmental Assessment (EA) resulting in a Finding of No Significant Impact (FONSI) in accordance with the National Environmental Policy Act (NEPA), (Pub. Law 90-190; 42 U.S.C. § 4331 et seq.), and the Air Force Environmental Impact Analysis Process (EIAP), 32 C.F.R. §989. The Offeror is required to confirm that the pricing submitted is valid through 15 May 2018. This will serve as the minimum acceptance period for this acquisition.

mailto:stephen.pritchett@us.af.mil mailto:kevin.grant.10@us.af.mil

1.1.6 Exceptions to Terms and Conditions. Offerors are required to meet all solicitation requirements as defined in Section L of the RFP. Offerors must clearly identify any exceptions to the solicitation terms and conditions, to include a complete rationale supporting the exception that fully explains potential impacts on the performance, schedule, price, and specific requirements of the solicitation.

1.1.7 Potential Errors. If an Offeror believes requirements in these instructions contain an error, omission, or are unsound or ambiguous, the Offeror shall immediately notify the PCO in writing with supporting rationale. The Government reserves the right to award this effort based on the initial proposal, as received, without discussions in accordance with FAR 15.215-1(f)(4).

1.1.8 Proposals must be submitted in both electronic and paper format as specified in L.1.2, Organization/Distribution/Number of Copies/Page Limits. In case of conflict between paper and electronic proposal copies, the paper version will take precedence. Telegraphic or facsimile offers will not be accepted. The sealed envelope or package used to submit your proposal must show the time and date specified for receipt, the Solicitation Number, the name of the Offeror, and the Offeror’s POC name, address and phone number.

1.1.9 Offerors are cautioned that JBSA-Randolph has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass to gain entrance. SOME DELAY SHOULD BE ANTICIPATED WHEN HAND CARRYING PROPOSALS. Offerors are responsible for allowing sufficient time to obtain a visitor pass and deliver the proposal PRIOR to the time specified for receipt. Contact the POCs in paragraph 1.1.4 with questions regarding base entry. Late proposals will be processed IAW FAR 52.215-1(c)(3) “Submission, modification, revision, and withdrawal of proposals” and FAR 15.208 “Submission, Modification, Revision, and Withdrawal of Proposals”.

1.2 Organization/Distribution/Number of Copies/Page Limits

The proposal shall consist of four separate volumes. The Offeror shall organize the proposal as set forth in the Proposal Organization table below. The titles, contents of the volumes, page limits and number of copies shall be as follows:

Table 1.2 Proposal Organization Volume Title Hard Copies CD/DVD Page Limit Due Date I Technical Original + 5 per subfactor 2 125* See Block 9 of

SF 33

II Past Performance Original + 5 2 58** See Block 9 of

SF 33

III Price Original + 3 2 Unlimited See Block 9 of

SF 33

IV Small Business

Subcontracting Participation

Original + 3 2 25 See Block 9 of

SF 33

* Page count exclusions referenced in L.1.2.3.3 ** Subcontractor Letter of Consent and Client Authorization Letters do not count towards the page count.

One proposal shall be marked "Original" and all others shall be marked as "Copy." Narrative documentation shall be submitted in Microsoft Word (version Office 2010 or higher).

1.2.1 Mail or hand deliver required hard copies and electronic copies on CD or DVD of each volume to the following:

Mr. Stephen Pritchett Mr. Kevin Grant

338 SCONS/PKD

2021 First St. West JBSA-Randolph TX 78150-4302

1.2.2 Binding and Labeling. All hard copies (other than the Original) proposal volumes shall be submitted in separate three-ring binders. The unbound, Original proposal shall include a standard (3 inch spaced) two-hole punch applied to the top center of each page when viewed in portrait orientation (for Government filing) printed double sided head to foot. Volumes I, II, III and IV shall not be submitted together within the same binding. Additionally, each subfactor under the technical volume II shall be in separate binders. Designate on the volume cover which proposal package contains the original, executed copy of the RFP. Include with each proposal cover letter or proposal cover page: name, office phone and fax number (and, if applicable, cell phone number), and e-mail address for the proposal point of contact. Clearly mark as to whether it is the original or copy, volume number, title, solicitation identification, and the Offeror’s name. Be sure to apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), "Restriction on Disclosure and Use of Data,” and FAR 3.104-4, “Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.”

1.2.3 Page Format Restrictions and Limitations.

1.2.3.1 Page Format. Pages shall be 8.5 x 11 inches, not including foldouts used for charts, tables, or diagrams. Pages shall be typed. Except for the reproduced sections of the solicitation document, typing shall be single space, 12 font size, and Times New Roman font style. Smaller font size may be used in tables, drawings, charts, graphs, and diagrams, but shall not be less than 10 font size, Times New Roman. Margins on all four edges of each sheet shall be at least one inch. Proprietary statements, security markings, and page numbers may fall within the defined margin area. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notices (ENs), if issued, as well as to the initial proposal.

1.2.3.2 Page Limitations. Compliance with page count limits shall be verified via the hardcopy. Page limitations shall be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters when forwarding the ENs to the Offeror(s). Any supporting documentation that is in response to an EN, not to include change pages, will not be subject to page limitations.

1.2.3.3 Pages Counted. Pages exceeding the page limitations in this Section L, will not be read or evaluated, instead, such additional pages will be destroyed. Each page shall be counted except the following: the Quality Control Plan, transmittal letter, cover pages, tab-divider pages, title pages, table of contents, lists of tables and drawings, glossary of acronyms, cross-reference matrix, aircraft performance charts/data, position qualifications or staffing/manpower matrix, blank pages, outlines for the plans and programs, and exceptions to the solicitation. All signed letters of agreements are excluded from the page count. Double-sided printed sheets will be counted as 2 pages.

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

1.2.3.5 Foldouts. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume. Each printed side of a foldout will count as one page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics;

not for pages of text. For tables, charts, graphs and figures, the font shall be no smaller than 10 font size, Times New Roman.

1.2.4 Documents submitted in response to this RFP must be fully responsive to and consistent with the following:

1.2.4.1 Requirements of the RFP (including CLINs) and Performance Work Statement (PWS) and Government standards and regulations pertaining to the PWS.

1.2.4.2 Evaluation Factors for Award in Section M of this RFP.

2.0 VOLUME I – TECHNICAL FACTOR

2.1 General

2.2 The Technical Volume shall be specific and complete. Your responses will be evaluated against the technical evaluation criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided below, your technical proposal must provide a detailed approach to accomplish/satisfy all subfactors. All 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 not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

2.2.1 Technical Volume

In the technical volume, address your technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor.

PWS references provided are for reference and may not constitute every section of the PWS, or its appendices, in which a subfactor may be applicable.

2.2.2 Volume Organization

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

a) Table of Contents

b) Executive Summary

c) List of Tables and Drawings

d) Glossary/Acronym Abbreviation List

e) Cross Reference Matrix (If applicable)

f) Subfactor 1 - Mobilization

g) Subfactor 2 - Staffing

h) Subfactor 3 - Security

i) Subfactor 4 - Integrated Operations

2.2.3 Technical Risk. Throughout the Offeror’s responses to the Technical Subfactors 1 through 4, the Offeror should explain the Technical Risk associated with those aspects of its proposal it considers to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, unsafe conditions for students or the likelihood of unsuccessful contract performance. The Offeror shall classify each risk IAW the Section M Technical Risk Rating table. The Offeror shall provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance.

The Offeror shall describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of contract requirements. The Offeror shall propose risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. The Offeror should identify and classify any new risks introduced by such risk mitigation.

2.2.4 Site Visits. If site visits are conducted during the evaluation phase, offerors will be informed in advance of the time and date the site visit will occur.

2.3 Subfactor 1: Mobilization

2.3.1 The Offeror shall describe a mobilization strategy that will lead to full performance.

The mobilization plan shall include contractor developed milestones with detailed plans that demonstrate how the Offeror plans to begin training students six months after an Environmental Assessment (EA) Finding of No Significant Impact (FONSI) and contract award.

2.3.2 The Offeror shall include in the mobilization a contractor developed milestones/timeline and details of when and how all the plans and publications listed in Appendix A-4 will be acquired/developed within the mobilization timeframe.

2.3.3 The Offeror shall provide a timeline and methodology that details when and how the process of recruiting, hiring, training, and certifying required personnel will be completed within the mobilization timeframe.

2.3.4 The Offeror shall describe when and how primary and auxiliary airfields will be acquired/developed within the mobilization timeline. The Offeror must include in their airfield descriptions a list of all agencies that must approve/coordinate on the Offeror’s airfield operation plans.

2.3.5 The Offeror shall provide a plan of when and how flight training areas and routes will be acquired/developed to support the requirements in the PWS within the mobilization timeline.

2.3.6 The Offeror shall provide a detailed timeline and the methodology of how aircraft, facilities, equipment, and supplies will be acquired/modified and ready for use within the mobilization timeframe.

2.4 Subfactor 2: Staffing

The Offeror shall describe the methods and policies that will be used to sustain a work force that will perform the requirements in the PWS.

2.4.1 The Offeror shall provide staffing, training, and retention plans for all personnel needed to meet the PWS requirements. Include with the plans a detailed organizational chart that covers all manpower positions and identifies key personnel positions (program manager, chief pilot, chief of maintenance, and any other position(s) the Offeror deems key). Describe the proposed level of experience, background, skill levels and training of key personnel. The Offeror shall specifically address how sufficient numbers of qualified Certified Flight Instructors (CFI), key management, supervisory, and maintenance personnel will be encouraged to relocate (if necessary) and remain in the Offeror’s planned area of operations.

2.4.2 The Offeror shall describe a plan for surges, back-filling personnel on leave or unforeseen short/long term absences, and provide a plan to back up “one deep” positions. The plan shall also describe any cross utilization of employees. The Offeror shall describe the number of CFIs proposed for student production from minimum to maximum flight hours as required by the PWS Appendix A-1.

2.4.3 Support/Interface With Organizational Structure. The Offeror shall define interface with home office or corporate headquarters for such aspects as management, technical, and financial support.

2.4.4 Quality Control Plan. The Offeror shall provide a Quality Control Plan that describes how they will ensure that the contract requirements are met while maintaining safety. The plan must describe inspector and/or superintendent assignment controls and clearly demonstrate that quality is the contractor’s (not the Government’s) responsibility. Address the proposed skill levels, experience and training of the quality control personnel in relation to the required work disciplines.

2.4.4.1 Describe number of tasks planned per inspector, frequency, and a plan, including tools and methods, for identifying and documenting performance problems concerning subcontractors and/or in-house personnel.

2.4.4.2 Provide a plan that describes timely response and resolution of routine, urgent, and emergency discrepancy notices.

2.4.4.3 Describe how interface with Government Contracting Officer Representatives (COR) will be accomplished. Define on-site management staff’s responsibilities for timely response to notifications of quality assurance (QA) discrepancies.

2.4.4.4 Provide an example(s) that demonstrates past experience with developing and implementing successful quality control and/or inspection procedures to meet contractual requirements for operations similar to those described in this RFP.

2.5 Subfactor 3: Security

All information for sections L and M for security requirements must be accessed through separate secured packages attached to the RFP posting for IFT on FBO.Gov.

2.6 Subfactor 4: Integrated Operations

Within the following elements of this subfactor, the offeror shall describe its overall best approach to the Government’s requirement.

2.6.1 Flight Training. The Offeror shall describe how the mass and flight briefings/debriefings, flight room activities, academics, ground training, and the flying training detailed in the IFT Syllabuses and PWS will be conducted at the best estimated quantity level.

The Offeror shall demonstrate the measures that will be utilized to increase from BEQ to maximum student load and how their plans will replicate an undergraduate flying training (UFT)-like environment. Include in the description a flow-chart that details how required academic, ground, and flying training models will be integrated to fulfill the requirements of the syllabuses.

2.6.2 Airfields and Operations

2.6.2.1 Flying Training Areas and Routes Usage. The Offeror shall describe proposed flying training areas, routes, flight hazards and terrain. The Offeror shall submit their strategy/concept of operations for flying training areas and routes. The Offeror shall identify all agencies that must be coordinated with to develop the proposed flying areas and routes and any known issues that may restrict development of the areas and routes.

2.6.2.2 The Offeror shall submit US Government historical weather data for the location(s) proposed, averaged over a 5 year period as part of their proposal. The weather package must include weather phenomena that may affect the Offeror’s ability to conduct flying training; e.g., cloud ceiling and visibility (% or # of days better than 1500/3), wind (% less than student/airplane (whichever is lowest) wind limits or average wind for proposed flying periods), thunderstorm and hurricane occurrence (% of time or # days/year flying would be affected), snow accumulation (% or number of days of appreciable snow accumulation), freezing temperatures (% or number of days temp below freezing), etc. to support their solution for providing sufficient flying days to meet production requirements at maximum student load.

2.6.2.3 The Offeror shall describe the airfields’ operating procedures that will be used in training students IAW with PWS and Federal Aviation Regulations; capacity of the airfield to accommodate IFT training; general condition of the airfield; airfield environment; objects on and/or around the airfield; any other current tenants that can be expected to compete for capacity; flight support facilities, services, and equipment (such as tower, rapcon, navigation aids, runway/taxiway lighting, fuel contractors, crash & rescue, dining facilities, security patrols, etc.); existing airfields’ construction plans, refurbishments, and/or traffic growth that could impact IFT production; and a plan to mitigate the impact of these projects on the IFT program.

The Offeror shall submit their strategy/concept of operations for the airfields they intend to use and completed letter(s) of agreement from the appropriate airfield agency/owner for airfields not owned by the Offeror.

2.6.2.4 Emergency Support Services. The Offeror shall describe what emergency response services (fire, ambulance, and crash and rescue) are currently available at the airfields of intended use. The Offeror’s plan shall describe the emergency response assets and the number of personnel on the airfields available to respond to fires, aircraft accidents, and accidental injury to IFT personnel and students. If ambulance service is not available on the airfields, detail where an ambulance would come from and how long it would take to get to the proposed training facilities. If emergency response services are not normally available at the airfields of intended use, the Offeror shall describe the plan to provide these services at the airfields.

2.6.3 Management Plan

2.6.3.1 The Offeror shall provide the concept of a comprehensive schedule of all operations.

The concept shall include describing in detail a daily schedule that accommodates performance at best estimated quantity and with maximum student load. The schedule must show every ground and flight operation, maintenance actions (including aircraft launch, recovery, refueling, regeneration, inspections, scheduled maintenance, etc.) academic courses, ground training, required transportation, etc.

2.6.3.2 The Offeror shall provide a concept of operations and outline of all plans and programs. (e.g., transportation, tool control, FOD, SOF, Go–No Go, flying and ground safety, mid-air collision avoidance, FCIF, noise abatement, etc.).

2.6.3.3 The Offeror shall provide the concept for weekly, monthly, and annual schedules that include, in general terms, the operations mentioned above, as well as class flow (student reporting and departures), holidays, weather days, etc.

2.6.3.4 The Offeror shall describe a plan that anticipates and addresses short term surges in student load, long term operations at maximum student load, and “get-well” options when class graduation dates may not be met.

2.6.3.5 The Offeror shall describe previous experience with scheduling operations that demonstrate the Offerors ability to accomplish PWS requirements.

2.6.4 Aircraft Description and Maintenance

2.6.4.1 Aircraft Description. The Offeror shall describe in detail the aircraft proposed for IFT. The Offeror shall ensure that proposed aircraft meet the PWS requirements at paragraph

1.2.2. The Offeror shall provide aircraft performance charts/data from the proposed aircraft's pilot operations handbook/flight manual/aircraft performance charts/etc. The Offeror shall explain why those aircraft were chosen and explain any additional information the Offeror deems pertinent to the aircraft’s performance and suitability for IFT program use. Additional information could include documentation of aircraft capabilities that exceed PWS requirements, an outstanding reliability and safety record, excellent handling characteristics, ease of performing maintenance, engine performance and safety history, manufacturer support, etc.

2.6.4.2 Aircraft Maintenance. The Offeror shall provide a plan that describes the proposed daily aircraft maintenance and sortie generation. The plan shall detail the Offeror’s daily expectations for each aircraft and take into consideration the large daily sortie count (to include seasonal surges) the IFT syllabus will require.

2.6.4.3 The Offeror shall provide complete rationale for the proposed fleet size (to include spare aircraft) to meet PWS requirements. The fleet must be of sufficient size to fly the high daily sortie count, including seasonal surges, and allow for normal scheduled maintenance, required inspections, and occasional unplanned maintenance.

2.6.4.4 Spare Aircraft. The Offeror shall describe how spare aircraft will be used and how the Offeror plans to accomplish scheduled aircraft inspections and unscheduled maintenance while maintaining the required daily sortie count.

2.6.5 Training Facilities and Equipment

2.6.5.1 The Offeror shall describe the number and size of flight rooms/classrooms and the equipment anticipated for the projected student load. The Offeror shall describe how the student flight rooms will be separated from civilian students, if necessary, in order to replicate an undergraduate flying training (UFT) environment. This plan shall include the training equipment necessary to present the courseware.

2.6.5.2 Facilities and Equipment. The Offeror shall describe all facilities and equipment (to include vehicles) required for performance.

2.6.5.3 General Facilities and Equipment Maintenance and Appearance. The Offeror shall describe how all training and other associated facilities and equipment will meet best commercial practices for the following: maintenance, repair, cleanliness, hygiene and climate control.

2.6.6 Lodging and Food Service

2.6.6.1 Lodging. The Offeror shall describe their planned methodology and facilities to house students while they attend IFT, including the amenities anticipated for each student, and individual climate control (PWS paragraph 1.2.14 and 1.2.15). The Offeror shall describe how proposed lodging will meet commercial standards. The rooms shall meet best commercial practices for cleanliness and service. Describe the method to accept arriving students and to handle departing students.

2.6.6.2 Food Service. The Offeror shall describe their planned methodology and facilities for student dining. As a minimum, the plan shall describe a method to feed students during the training day, including access to a mid-day meal. Describe weekend meal service and how it might differ from normal weekday meal service. The plan shall describe how the students will be provided with a dining area. The plan shall provide varying nutritious meals from day to day, and flexible hours that will allow all students time to eat breakfast, lunch and dinner.

3.0 Volume II - Past Performance

3.1 General

Each Offeror shall submit a Past Performance Volume with its proposal. The Past Performance volume shall be prepared IAW all instructions contained within this Section L. Each Offeror’s proposal will be evaluated IAW the evaluation criteria in Section M.

3.2 Format and Specific Content

Volume II shall contain the following:

3.2.1 Volume Organization

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

a) Table of Contents

b) Summary Page

c) Specific Content

d) Past Performance Information

e) Organizational Structure Change History

f) Past Performance Questionnaires (PPQ)

g) Subcontractor Letters of Consent/Client Authorization Letters

3.3 Summary Page

Describe the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner. Past Performance Information is required for the Offeror and all subcontractors, teaming partners, and/or joint venture partners that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance. The Table of Contents and Summary Page(s) shall not exceed five (5) pages combined.

3.4 Specific Content

Offerors are required to identify what aspects of the past performance references are deemed relevant to the proposed effort and to explain how they relate to their proposal. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems.

3.5 Past Performance Information Sheet- (PPIS) Each Offeror shall complete and submit, as part of their proposal, Past Performance Information (PPI) in accordance with the format contained in Attachment 9, of not more than eight (8) contracts/efforts total (including major subcontractors, teaming partners, joint venture partners) that you consider recent and relevant to this acquisition, demonstrating your ability to perform the proposed effort. Recency is defined as performance that occurred within the last five (5) years of the date this solicitation was issued that included at least six (6) months of performance. Relevancy is further defined in Section M. The Government acknowledges that given the scope, magnitude and complexity of the IFT requirement, Offerors may not be able to submit single contracts that can fully encompass all areas of the IFT requirement. Offerors are encouraged to submit any combination of contracts or programs that Offerors would like to submit as relevant to demonstrate their quality of performance in the Primary Evaluation Areas identified in Section M 3.2.2. Each contract or effort submitted must be limited to six (6) pages. The combination of all PPIS, to include specific content, shall not exceed a total of 48 pages (eight (8) contracts/efforts multiplied by six (6) pages each). Submit original plus five (5) printed copies.

In addition to submitting the printed copies of the PPIS, the Offeror shall use the PPI Tool instructions provided as Attachment 6 to this solicitation to retrieve and submit the PPI Tool.

The instructions offer step by step guidance for using the PPI Tool to generate the past performance report required by this solicitation. Using the PPI Tool, the Offeror shall provide the information required by the PPI Tool on the same contracts/efforts submitted in the PPIS.

The Government may also consider the past performance of affiliated companies or operating divisions within the parent company or joint ventures of the parent company, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement when it is reasonable to attribute the experience of the past efforts to the proposed effort and when the proposal clearly demonstrates the resources (e.g. financial resources, overall oversight and management, or other resources) of the parent or affiliated division will meaningfully affect performance of the instant acquisition. If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner.

3.6 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 conclusion of recent past efforts and this source selection. To facilitate the relevancy determination, include a "roadmap" describing any such changes in the organization of your 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), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources. Organizational Structure will not be included in the past performance page count. This section shall not exceed five (5) pages.

3.7 Past Performance Questionnaires (PPQ)

The Government will evaluate the quality and extent of Offeror’s performance deemed recent and relevant to the requirements of this RFP. The Government will use information submitted by the Offeror and other sources such as other Federal Government offices and commercial sources to assess performance. Offeror shall send the questionnaire at Attachment 10 to references on no more than eight (8) contracts identified in their PPISs. The responsibility to send out the PPQs and ensure receipt by the Government rests solely with the Offeror.

Completed PPQs shall be sent by the reference directly to the Government POC identified in the PPQ form. It is highly recommended that Section 1 of the PPQ be pre-filled by the Offeror prior to sending to respondent. Once submitted, the information contained therein shall be considered source selection sensitive.

3.8 Subcontractor Letters of Consent/Client Authorization Letters Subcontractor Letters of Consent - Past performance information pertaining to a subcontractor cannot be disclosed to the prime Offeror without the subcontractor’s consent. Proposals must include a Subcontractor Consent Letter (Attachment 8) executed by each subcontractor, teaming partner, and/or joint venture partner, that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

Client Authorization Letters - If applicable, Offerors must also include Client Authorization Letters (Attachment 7) for each identified effort performed for a commercial customer, authorizing release to the Government of requested information on the Offeror’s performance.

4.0 VOLUME III – PRICE

4.1 Volume Organization

The Price volume shall be organized according to the following general outline:

a) Table of Contents

b) Summary Page

c) Glossary/Acronym Abbreviation List

d) Price Data (Section B on SF33)

e) Price Model (Attachment 4 of RFP)

f) Statement of Compliance with applicable SCA WD(s) and CBA(s)

g) Responsibility Determination Supporting Documentation

h) Teaming Arrangement(s) and/or Letters of Intent

i) Contracting/other

4.2 General Instructions

4.2.1 The Price proposal shall be prepared according to these instructions and will be evaluated IAW the evaluation criteria in Section M of this RFP for the Price Factor. Compliance with these requirements is mandatory and failure to comply may render the proposal unawardable. The CD/DVD shall include all Microsoft Excel files with all cell formulas viewable. As stated in paragraph 1.1.5 above, the Government anticipates an award being made May 2018 at the conclusion of a successful EA and FONSI. The proposed prices of the potential contract are anticipated to begin during this timeframe and should be priced accordingly.

4.3 Price Reasonableness

4.3.1 The source selection will be conducted with the expectation of adequate price competition per FAR 15.403-1(c)(1); therefore, certified cost or pricing data are not required per FAR 15.403-1(b)(1). If at any time during this competition the PCO determines that adequate price competition no longer exists or that price reasonableness cannot be determined, Offerors may be required to submit certified cost or pricing data or additional data other than certified cost or pricing data, as appropriate, for the PCO to determine price reasonableness. The proposed prices shall be based on the Offeror’s own technical approach submitted in the Technical Proposal (Volume II) and the Government’s PWS requirements. Unbalanced pricing may pose an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal.

Offers should be sufficiently detailed to demonstrate reasonableness and balance.

4.4 The Offeror must complete the following and include in Volume III:

4.4.1 Table of Contents. The table of contents should provide a list of titles for the contents of the price volume organized in the order in which they appear.

4.4.2 Summary Page. The summary page shall provide an overview of the overall pricing that clearly demonstrates the total price of the proposal for the aggregate of all FFP CLINs (except AVGAS and Off-Site support) described in paragraph 4.5 for mobilization and all subsequent years. Ensure the Best Estimated Quantity (BEQ) amounts are utilized for the Flight Instruction CLINs X001.

4.4.3 Glossary/Acronym Abbreviation List. Provide a glossary for a list of terms or abbreviations with accompanying definitions, if necessary, in order to explain or define difficult or unusual words, terms and expressions.

4.5 Price Data

4.5.1 The Offeror shall propose and insert a whole unit price, with no decimal places, for each Firm-Fixed-Price (FFP) CLIN of the Base Period (year 1 – year 5; including mobilization), Option Period 1 (year 6 – year 8) and Option Period 2 (year 9 and year 10) in the Price Model attached to this solicitation. The total extended amount for the FFP CLINs must equal, to the dollar, the unit price multiplied by the quantity of units. The sum total of all CLINs (except AVGAS and Off-Site support), for mobilization, the Base Period, Option Period 1 and Option Period 2 will form the Offeror’s total evaluated price (TEP).

4.5.1.1 For CLINs X001 Flight Instruction, enter the monthly unit price for each Exhibit Line Item Number (ELIN) that correlate with the number of annual hours. The amount on the bolded line that represents the BEQ will automatically populate the CLIN X001 amount in the Price Model.

4.5.1.2 For CLINs X002 International Military Students, enter the unit price per student.

4.5.1.3 For CLINs X003 Additional Flight Hours, enter the unit price per hour.

4.5.1.4 CLIN X004 AVGAS and CLIN X005 Off-site Support have been intentionally left out of the Price Model as these CLINs will be direct reimbursable and do not require pricing.

4.5.2 All ELIN amounts for X001, will be evaluated to determine that the pricing is fair and reasonable IAW FAR 15.404, however, the BEQ will be evaluated and used for determining the TEP. The ELINs represent the variations in flight training that may occur during the life of the contract. The variations range from 18,000 to 51,000 flight hours per year (+/- 1500 flight hours). These ELINs apply only to the Flight Instruction CLIN which includes the Pilot, CSO, and RPA Pilot candidates. Each year of the contract will have ELINs for the purpose of pre-priced ordering. All ELINs must be filled out for every year. Failure to complete all ELINs will render an offeror’s proposal ineligible for award.

4.5.3 Data beyond that required by paragraph 4.5 shall not be submitted, unless it is essential to document or support the Offeror’s price position. All data relating to the proposed price, including all required supporting documentation, must be included in the Price volume (Volume I). Under no circumstances shall this data and documentation be included elsewhere in the proposal.

4.6 Price Model. The Offeror shall complete the electronic Price Model attached to the RFP at Attachment 4, IAW the instructions contained in this Section L and the Price Model.

Ensure that the hard copies of the price model are included in the proposal along with the e-version on the DVD/CDs. The Price Model will be incorporated into the resulting contract.

4.7 Statement of Compliance with applicable Service Contract Act Wage Determination(s) and Collective Bargaining Agreement(s)*. The contractor shall submit the correct Wage Determination(s) (WD) based on location(s) of training, as part of their price proposal. The WD information shall include the specific labor categories utilized in the proposal. WD information can be found at http://www.wdol.gov. Upon determination of the place(s) of performance, the PCO will obtain the WD(s) for the location(s) proposed and ensure that the correct WD(s) were used for the proposal. In the event that the proposal does not include a required WD or CBA the proposal may be ineligible for award.

Offeror shall provide a Statement of Compliance with the Service Contract Labor Standards (SCLS). The Offeror shall provide a statement acknowledging:

i. Compliance with the requirements of the SCLS WD(s);

ii. The prices proposed for labor covered by the SCLS WD(s) were formulated in consideration of the rates specified in the document as required for covered contractor personnel; and

iii. The proposed wage and benefit rates covered by the SCLS WD are not escalated beyond the basic period of performance (FAR 52.222-43(a) and (b)).

* Note: If a Collective Bargaining Agreement (CBA) is applicable, offerors shall conform with FAR 22.1008-2 Successorship with Incumbent Contractor Collective Bargaining Agreement.

4.8 Responsibility Determination Supporting Documentation. To assist in determining contractor responsibility IAW FAR Part 9.104, the Offeror shall explain how they plan to maintain adequate financial resources for a contract of this magnitude and length.

Offerors shall address their fiscal plan for covering mobilization, unexpected or emergency situations, and initial performance costs prior to recoupment in the form of monthly invoice payments. Offerors must provide complete financial statements for one fiscal year and year-to-date financial information through the last quarter available. The year-end financial statements must be certified by an independent accounting firm, if practicable, or at least by an authorized officer of the organization. If the Offeror intends to rely on internally available working/operation capital, evidence of availability must be submitted. If the Offeror plans to rely on financial support from other sources, evidence of availability and the maximum lines of credit that may be available must be identified and must be based upon the inclusion of this contract effort. Evidence of external funding must be provided in the form of a dated letter from the external source. Documentation to support the amounts must also be included.

4.8.1 IAW FAR 9.104-5, the Offeror is required to comply with the submission regarding FAR 52.209-5, Certification Regarding Responsibility Matters found in Section K of this RFP.

Since the Government reserves the right to award without discussions IAW FAR 52.215-1(f)(4), http://www.wdol.gov/ the Government may request that an Offeror submit additional information so a responsibility determination can be made. This request for additional information will not be construed as communications or discussions with an Offeror as defined by FAR 15.306. Failure to certify the required responsibility matters outlined in Section K, may render the offeror’s proposal ineligible for award.

4.9 Teaming Arrangements and/or Letters Of Intent. If a teaming arrangement is contemplated, provide complete, verifiable information as to the arrangement, including any previous teaming endeavors on previous teaming arrangements with same partner. Submit information relative to the formation, organization and operation of the business unit.

Information shall include cost and revenue sharing agreements and any other information which describes the business arrangement.

4.10 Contracting/Other.

4.10.1 The Offeror must complete the following and include in Volume I, Pricing:

4.10.1.1 Completion of blocks 13, 14 (Offeror may sign and date each Standard Form (SF) 30 acknowledging receipt of each amendment to the solicitation), 15, 16, 17 and 18 and signature and date for blocks 17 and 18 of the Standard Form (SF) 33. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

4.10.1.2 Offerors must complete all necessary clause fill-ins in Sections I through K. Ensure compliance with RFP requirements if using the annual representations and certifications electronically via the System for Award Management website at https://sam.gov.

4.10.1.3 Submit a letter, signed at the vice-president level or equivalent or higher, that identifies the individual(s) with the authority to obligate or otherwise bind your company to the resulting contract and, if necessary, future contract modifications. Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal. Also, identify those individuals authorized to negotiate with the Government. In addition, provide the name, title, and telephone number of the CEO, Division President, and/or Vice President.

4.10.1.4 Provide company/division's name, street address, county and facility code; CAGE code; DUNS code; TIN; and size of business (large or small). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

4.10.1.4.1 Organization. The above information shall be provided for the prime and all subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition.

https://sam.gov/

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

4.10.1.6 Exceptions to Terms and Conditions. The Offerors shall list any exceptions to, or deviations from, any of the clauses or requirements to the RFP along with the justification.

4.10.2 Subcontracting Plan (Large Business Only)

4.10.2.1 IAW FAR 19.705-2, large business prime Offerors shall provide a clear, detailed and realistic plan that complies with FAR 52.219-9 and DFARS 252.219-7003 and satisfies all of the requirements of FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) in order to be determined acceptable by the PCO prior to contract award. The Offeror’s submission must provide sufficient information to support the PCO's review of the subcontracting plan to determine acceptability. If small business subcontract possibilities do not exist or are limited, the Offeror’s plan must state such and provide rationale supporting the assertion. An approved Subcontracting Plan is required for any contract awarded to a large business Offeror. (NOTE:

Small business participation may be addressed in a large business Offeror’s subcontracting plan;

however, it shall also be addressed in the Offeror’s Volume IV - Small Business Participation, as required by Section L, paragraph 5.0 and Section M, paragraph 5.0 criteria. FAR 52.219-9 Small Business Subcontracting Plan does not apply to small business concerns; however, they shall address Volume IV - Small Business Participation, as required by Section L, paragraph 5.0 and Section M, paragraph 5.0 criteria.)

4.10.2.2 FY15 DoD subcontracting goals are provided below (NOTE: FY16 DoD subcontracting goals have not yet been published). These goals represent the percent of small business subcontracting as it relates to total subcontracting dollars, not the total contract dollar value.

Small Business 36% of total subcontracted dollars Small Disadvantage Business 5% of total subcontracted dollars Woman Owned Business 5% of total subcontracted dollars HUB Zone 3% of total subcontracted dollars Veteran Owned 3% of total subcontracted dollars Service Disabled Veteran Owned 3% of total subcontracted dollars

Note: These goals may be met by any combination of subcontracts, other business teaming arrangements (exclusive teaming arrangements are prohibited) or vendor purchases.

4.10.2.3 Offerors should propose goals that are realistically obtainable and provide rationale for the proposed goals. The Subcontracting Plan Checklist is provided as a guide in Attachment 5.

5.0 VOLUME IV – SMALL BUSINESS PARTICIPATION

5.1 Provide a narrative detailing the corporate commitment and specific steps taken to identify sources and provide subcontracting opportunities for small businesses.