ACES_Section_L_20_Aug_19_v2.pdf

Section L

INSTRUCTIONS TO OFFERORS

Aircraft Maintenance Enterprise Solution (ACES)

1. Program Structure and Objective

1.1. The Government plans to create an Aircraft Maintenance Enterprise Solution (ACES)

Multiple Award Contract (MAC) vehicle by awarding multiple Indefinite Delivery Indefinite Quantity (IDIQ) contracts. The ACES MAC will create a group of pre-selected contractors who meet the overall criteria to provide aircraft maintenance and related services on-site at operational Government locations in the Continental United States (CONUS), Alaska and Hawaii.

1.2. The MAC IDIQ initial award will require all selected contractors to attend the MAC Post Award Conference.

2. General

2.1. 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 proposals. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted In Accordance With (IAW) 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 the entire Request for Proposal (RFP), including attachments.

2.1.2. The Government will evaluate the information presented in the Offeror's submission. The proposal shall be clear, concise, and shall include sufficient technical detail for effective evaluation and for substantiating the validity of stated claims. It is the Offeror’s responsibility to provide a submission that enables the Government to effectively evaluate the Offeror’s submission. The Offeror has the burden to provide a submission that demonstrates the Offeror has an accurate understanding of the requirements and the associated risks; the Offeror has viable solutions for the requirements and potential risk areas; and the Offeror is able to meet the requirements.

2.1.3. The proposal should not simply rephrase or restate the Government's requirements, but rather provide convincing rationale to address how the Offeror intends to meet these requirements. Where appropriate, specific examples of an Offeror’s processes may be used to demonstrate how the Offeror will meet the Government’s requirement. Offerors shall assume the Government has no prior knowledge of their experience, facilities or capability and will base its evaluation on the information presented in the Offeror’s proposal. Statements that the Offeror will provide a particular feature or objective without explaining how the Offeror proposes to meet that feature or objective are generally inadequate and may adversely impact the Government’s evaluation of the Offeror. The following types of statements are also considered inadequate:

2.1.3.1. Unsupported statements that the Offeror allegedly understands the requirements and risks.

2.1.3.2. Unsupported statements that the Offeror allegedly can or will comply with requirements.

2.1.3.3. Unsupported statements that simply paraphrase the requirements.

2.1.3.4. Undefined or unexplained statements such as “best commercial practices will be used.”

2.1.3.5. Undefined or unexplained statements such as “standard procedures will be used.”

2.1.3.6. Undefined or unexplained statements such as “well-known techniques will be employed.”

2.1.4. Offerors are strongly encouraged to carefully review all Government provided information and documents, to include, but not limited to: submittal instructions, including attachments, the Performance Work Statement (PWS), and the evaluation factors.

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

2.1.6. Offeror proposals must be valid for 18 months from proposal submittal date.

2.1.7. IAW Federal Acquisition Regulation (FAR) Subpart 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of all unsuccessful proposals.

2.1.8. Proposals addressing only a subset of the solicitation requirements, such as a specific location or type of aircraft, may be deemed incomplete and ineligible for award.

2.1.9. Funding will be obligated on each Task Order awarded under the basic contract.

Task Orders may be fully or incrementally funded, as appropriate.

2.2. Debriefings

2.2.1. Competitive Range: If a competitive range is established, the Contracting Officer (CO) will notify Offerors of any decision to exclude them from the competitive range, whereupon they may request to receive a debriefing IAW FAR Subpart 15.505, Pre-award Debriefing of Offerors.

2.2.2. Unsuccessful Offerors: The CO will notify unsuccessful Offerors IAW FAR Subpart 15.503, Notification to Unsuccessful Offerors. Upon such notification, Offerors desiring a debriefing must make their request IAW the requirements of FAR Subpart 15.506, Postaward Debriefing of Offerors.

2.3. Discrepancies

2.3.1. If an Offeror believes 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, to include the remedies the offeror is requesting the CO to consider as related to the omission or error. The Offeror is reminded the

Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

2.4. Electronic Reference Documents

2.4.1. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fbo.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.5. Oral Presentation

2.5.1. Oral presentations will not be accepted.

2.6. Amendments to Solicitation

2.6.1. If the RFP is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by signing and returning the front page of each amendment no later than the date and time specified in the amendment(s).

2.7. Submission, Modification, Revision, and Withdrawal of Proposals

2.7.1. Proposals and modifications to proposals shall be submitted via these instructions to the POCs identified in Paragraph 2.12, Distribution, showing the time and date specified for receipt, the solicitation number, and the name and address of the Offeror.

2.8. Organization/Number of Copies/Page Limits

2.8.1. Title Pages: The Title Page of each volume must show the solicitation number, as well as the Offeror’s name, address, telephone number, and electronic e-mail address.

2.8.2. Proposal Organization Table: The Offeror shall prepare the proposal and provide the number of copies set forth in Table L.2-1, Proposal Organization.

2.8.3. Page Limitations: Page limitations listed in Table L.2-1 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 request.

Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited.

2.8.4. Cross Referencing: Each volume shall be written on a stand-alone basis so its contents may be evaluated without cross-referencing to other volumes of the proposal.

Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity. Any cross references must be absolutely clear. The specific page, section, paragraph, line, etc. location of the cross referenced material must be included in the text at the point of reference to avoid any confusion. A cross reference table should not be used as the sole means of identifying cross referenced material.

http://www.fbo.gov/

2.8.4.1. Individual subcontractor/vendor proprietary information may be submitted via separate binders/CD/DVDs, if necessary. The information contained in these binders/CD/DVDs must be referenced (by binder title, page and section number, as appropriate) within the main proposal where the information would have been included if it were not subcontractor/vendor proprietary. The information in these separate binders/CD/DVDs is subject to all other requirements of the RFP; contributes to the overall 50 page limit for Technical Subfactors 1, 2 and 3; and must be well-marked to clearly indicate any special handling instructions.

2.8.5. Restriction of Disclosure/Proprietary Information. If the Offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR Subpart 52.215-1(e), Instructions to Offerors - Competitive Acquisition.

2.8.6. Table of Contents: Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. The page limits associated with the Table of Contents are not included in the 50 page limit associated with Subfactors 1, 2 and 3.

Table L.2-1 - Proposal Organization

Volume Title Hard Copies

Soft Copies

CD/DVD

Page Limit Due Date

I Technical* 3 2 50** (Subfactors 1,2,3)

60 Calendar Days after

RFP Release

Subfactor 1 – Aircraft Maintenance Included in 50 page limit

Subfactor 2 – Human Resources Included in 50 page limit

Subfactor 3 – Program Management

Included in 50 page limit

Subfactor 4 – Small Business No Limit

II Past Performance 3 2 No Limit 30 Calendar Days after

RFP Release

III Cost/Price -

RESERVED RESERVED

IV Contract Documentation 1 2 No Limit

Notes:

* Technical Volume organization is detailed in Paragraph 3.2.

** When combined, Technical Subfactors 1, 2, and 3 shall not exceed 50 pages.

2.8.7. Tables and Figures: The Offeror’s proposal shall include an indexed list of tables and figures. The page limits associated with The List of Tables and Figures are not included in the 50 page limit associated with Subfactors 1, 2, and 3. The tables and figures are included in the page limit.

2.8.8. Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used with an explanation for each; however, the Glossary pages are not included in the 50 page limit associated with Subfactors 1, 2, and 3.

2.9. Page Size and Format

2.9.1. A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches. Page line spacing shall be single spaced. The font shall be Times New Roman, no less than 12 points. Headers and Footers are excluded from this text requirement. 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 Notices (EN) as well.

2.9.2. 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 paper size or be less than size 8 font. Each 11 x 17 inch page will count as two pages. The following limitation only applies to the Technical Volume: text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than size 8 font. The size 8 font requirement includes the caption of the figures, charts, tables, and graphs. It shall also include callout/focus boxes. These limitations shall apply to all softcopy and hardcopy proposals. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation.

These limitations shall apply to all softcopy proposals.

2.10. Hardcopy Submissions

2.10.1. Each Volume shall be bound separately in hard side three-ring binders (e.g., Volume I – Factor 1: Technical in a binder, Volume II – Factor 2: Past Performance in a binder, etc.).

2.11. Softcopy Submissions

2.11.1. In addition to the hardcopy submission, the Offeror shall submit ALL proposal information in CD/DVD format only. Any other electronic method of submission, including email, will not be accepted. CD/DVDs shall be “read-only”. No file compression utilities, such as .zip, may be used. The softcopies of the proposal shall be submitted in a format searchable by Microsoft (MS) Word 2007, 2010 or 2016; MS Excel 2007, 2010 or 2016; MS Project 2007, 2010 or 2016; MS Power Point 2007, 2010 or 2016; and Adobe Acrobat (PDF).

2.11.2. The Offeror must ensure the CD/DVD submission is readable, in the format specified in the solicitation, and is free of computer viruses. Prior to any evaluation, the Government will check all files for viruses and ensure all information is readable.

If any files contain viruses and/or are defective (unreadable), the Government may only evaluate the readable/virus free files. If the defective (unreadable) media renders a significant deficiency in the Offeror's proposal, the government may consider the proposal incomplete and will not consider such proposals for evaluation.

2.11.3. The Offeror must ensure the softcopy and hardcopies of its proposal submitted in response to the solicitation are identical. If the copies are not identical, the hardcopy will take precedence.

2.11.4. It is the Offeror's responsibility to confirm receipt of all formal communications. Late proposals will be excluded from the evaluation.

2.12. Distribution

2.12.1. Proposals shall be submitted to the POCs listed below and are due NLT 1200 Central Time on:

Past Performance Volume: 8 October 2019 Technical Volume: 8 November 2019

2.12.2. The CO is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Block 7 of the solicitation.

Table L.2-2 - Distribution/Contact Information

For Hardcopy and Softcopy (CD/DVD) Submissions:*

Mr. Waid Harper and Ms. Lisa Hartman 338th SCONS/PKC 2021 First St West JBSA-Randolph TX 78150

* The Government POC will provide a receipt showing the submission delivery time and date. All submissions must reference Solicitation FA3002-19-R-A001.

Proposal submissions via e-mail will not be accepted.

Contact Information: **

Mr. Waid Harper Phone: 210-652-8269 E-mail: waid.harper@us.af.mil Ms. Lisa Hartman Phone: 210-652-8268 E-mail: lisa.hartman@us.af.mil ** All e-mail and telephone communications must reference Solicitation FA3002- 19-R-A001.

3. Volume I – Factor 1: Technical

3.1. General

3.1.1. The Technical Volume shall be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying the criteria. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all of the requirements specified in the PWS and 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.1.2. In the Technical Volume, address your proposed process to meet the minimum performance or capability requirements of each technical subfactor. To be eligible for award, Offerors are required to receive an “Acceptable” rating in each Technical Subfactor. If an Offeror’s proposal has an “Unacceptable” rating for any Technical Subfactor, this proposal will be unawardable.

3.1.2.1. Section L, Paragraph 4.5.3, provides FAR direction regarding unavailable or sparse past performance, which will be considered neutral in the evaluation of Offerors’ proposals. In the context of acceptability/ unacceptability, a neutral rating shall be considered “acceptable”.

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

a. Table of Contents (Not included in the 50 page limit)

b. List of Tables and Figures (Not included in the 50 page limit)

c. Executive Summary (Limited to 2 pages, and not included in the 50 page limit)

d. Subfactor One – Aircraft Maintenance

e. Subfactor Two – Human Resources

f. Subfactor Three – Program Management

g. Subfactor Four – Small Business (Not included in the 50 page limit)

h. Proposed Teaming Arrangements and/or Letters of Intent (Not included in the 50 page limit)

i. Cross Reference Table (Not included in the 50 page limit)

j. Glossary (Not included in the 50 page limit)

3.3. Subfactor 1: Aircraft Maintenance:

3.3.1. This subfactor assesses the Offeror’s strategy to provide complete aircraft maintenance capabilities to ensure aircraft are available to meet Government mission requirements. The Aircraft Maintenance subfactor consists of one (1) aspect containing four (4) elements (1a-1d).

3.3.2. Aspect I: Aircraft Maintenance Functions: Provide:

3.3.2.1. Element 1a) specific, comprehensive processes which demonstrate the capability to perform Organizational-level aircraft maintenance: sortie launch and recovery; scheduled and unscheduled maintenance; repair; Crashed, Damaged, or Disabled Aircraft Recovery (CDDAR); and aircraft inspection management to ensure sufficient mission capable primary and spare aircraft (where applicable) are available to meet daily, weekly, and monthly flying schedules.

3.3.2.2. Element 1b) specific, comprehensive processes which demonstrate the capability to perform Intermediate-level aircraft maintenance: back shop support to ensure sufficient mission capable primary and spare aircraft (where applicable) are available to meet daily, weekly, and monthly flying schedules.

3.3.2.3. Element 1c) specific, comprehensive processes which demonstrate the capability to perform aircraft and equipment Maintenance Support Activities:

Maintenance Operations Center (MOC); Maintenance Recovery Team (MRT);

Aerospace Ground Equipment (AGE); Munitions Management and Storage; and Transient Alert (TA) Services to ensure sufficient mission capable primary and spare aircraft (where applicable) are available to meet daily, weekly, and monthly flying schedules.

3.3.2.4. Element 1d) specific, comprehensive processes which demonstrate the capability to maintain data integrity for data systems and forms documentation (e.g., approved Maintenance Information Systems, aircraft forms, vital records, manpower expended, etc.) and demonstrates an understanding of the criticality of accurate and precise maintenance documentation.

3.4. Subfactor 2: Human Resources

3.4.1. This subfactor assesses the offeror’s strategy to provide trained and qualified aircraft maintenance personnel. The Human Resources subfactor consists of two (2) aspects containing four (4) elements (2a-2d).

3.4.2. Aspect I: Workforce and Staffing: Provide:

3.4.2.1. Element 2a) a Staffing Plan identifying all key positions, which demonstrates a detailed strategy to recruit and retain a qualified labor pool capable of performing aircraft maintenance and related activities IAW the PWS.

3.4.3. Aspect II: Training. Propose a process which demonstrates a thorough understanding of complexities and issues involved with providing a trained, qualified, and certified workforce throughout the life of the contract. Provide:

3.4.3.1. Element 2b) a comprehensive Training Plan and management process which demonstrates an effective strategy for completing formal training, classroom training, on-the-job training (OJT), and training documentation.

3.4.3.2. Element 2c) a comprehensive strategy that considers local, regional and/or national educational institutions to provide a workforce capable of performing aircraft maintenance services.

3.4.3.3. Element 2d) a comprehensive management strategy to ensure all new hires and entry-level employees obtain the applicable professional certifications/recertifications to meet PWS requirements.

3.5. Subfactor 3: Program Management

3.5.1. This subfactor assesses the offeror’s plan to provide safe, airworthy, mission capable aircraft and well-maintained support equipment with a trained workforce in an environment that identifies and corrects deficiencies. The Program Management subfactor consists of three (3) aspects containing seven (7) elements (3a-3g).

3.5.2. Aspect I: Fleet Management. Present a comprehensive strategy for fleet aircraft maintenance management that minimizes impacts to aircraft availability due to conflicts associated with maintenance scheduling. Provide:

3.5.2.1. Element 3a) a specific strategy to manage:

3.5.2.1.1. A smaller fleet of aircraft to meet higher performance standards IAW the PWS (for example a fleet of 10-25 aircraft with multiple Mission Design Series (MDS) and a ~98% departure reliability rate). The focus is not on the actual size of the fleet, but the strategy to manage the complexities and dynamics associated with a smaller number of aircraft without an established flying hour schedule; and/or,

3.5.2.1.2. A larger fleet of aircraft to meet moderate performance standards IAW the PWS (for example a 70 - 80% mission capable rate).

The focus is not on the actual size of the fleet, but the strategy to manage the complexities and dynamics associated with a larger number of aircraft to meet an established flying hour program.

3.5.2.1.3. Offerors shall identify to which of the strategies described above in Paragraphs 3.5.2.1.1 or 3.5.2.1.2 (or both) they are proposing.

Offerors proposing for only one of the above strategies will be restricted to proposing on Task Orders associated with that strategy.

Offerors may propose to both strategies and if deemed acceptable for both strategies may propose to any Task Order on this MAC. The actual size of the fleet and the applicable performance standard(s) will be determined at the Task Order level.

3.5.2.2. Element 3b) a strategy to effectively utilize personnel during periods of reduced flying hour requirements, examples of which are expanded employee training/certification events, reduction in hangar queens, process improvements, etc.

3.5.3. Aspect II: Quality Management System (QMS). Present an independent, contractor oriented QMS process IAW AS 9110, Quality Management Systems – Requirements for Aviation Maintenance Organizations, that assures high quality maintenance with unbiased/independent internal inspection procedures. Provide:

3.5.3.1. Element 3c) a comprehensive Quality Control organizational structure showing clear lines of authorities and responsibilities.

3.5.3.2. Element 3d) a detailed method to identify discrepancies; assess risk;

analyze root causes; devise, implement, track and close corrective actions; and document discrepancy trends.

3.5.3.3. Element 3e) a detailed method to record, compute, assess, identify trends, and report performance measurement data (metrics).

3.5.3.4. Element 3f) a management structure that fosters a culture of continuous process improvement, risk management, and compliance with contractual requirements, regulatory/technical guidance, and technical data.

3.5.4. Aspect III: Parts Supply Management. Propose a detailed strategy which provides:

3.5.4.1. Element 3g) a comprehensive parts supply management process (forecasting, ordering, issuing and turn in) to maintain aircraft, Aerospace Ground Equipment (AGE), and tools and support equipment at established levels.

3.6. Subfactor 4: Small Business

3.6.1. This subfactor assesses the offeror’s Small Business Subcontracting Plan, which demonstrates how the offeror intends to meet the ACES MAC subcontracting goals. The Small Business Subcontracting Plan applies ONLY to Large Businesses and, IAW FAR Subpart 19.702 (b) (3), The Small Business Subcontracting Program – Statutory Requirements, applies to work performed in the United States AND ITS OUTLYING AREAS ONLY. All Offerors (both Large and Small Businesses), to include Offerors with a DCMA approved Small Business Subcontracting Plan, must submit a Small Business Participation Commitment Document. NOTE: The Small Business Subcontracting Plan shall be submitted in Volume IV - Contract Documentation, and will be evaluated as part of responsibility.

3.6.2. Aspect I: Small Business Subcontracting Plan

3.6.2.1. Element 4a): The Offeror shall provide a Small Business Subcontracting Plan IAW FAR Subpart 52.219-9 Alternate II, Utilization of Small Business Concerns; DFARS 252.219-7003, Small Business Subcontracting Plan (DoD Contracts), or DFARS 252.219-7004, Small Business Subcontracting Plan (Test Program); and AFFARS 5319.704, Subcontracting Plan Requirements. As required by FAR Subpart 19.7, The Small Business Subcontracting Program, the Offeror’s proposal, as further described in Paragraph 3.6.3.1.2, shall provide a narrative describing the Prime’s corporate commitment to the goals and targets for subcontracting (small business, small disadvantaged business, women-owned small business, HUBZone small business, and service disabled veteran-owned small business) as indicated in Table L.3-1. Describe the strength and specificity of each corporate commitment (i.e., what type of commitment, how binding is the commitment, how specific is the commitment to this proposed effort, and what types of tasks are included in these subcontracting opportunities).

Table L.3-1 – Small Business Subcontracting Goals

Small Business 12% of total contract dollars Small Disadvantaged Business 5% of total subcontracting dollars Woman Owned Small Business 5% of total subcontracting dollars

HUBZone Small Business 3% of total subcontracting dollars Service Disabled Veteran Owned Small Business 3% of total subcontracting dollars

3.6.2.1.1. The Offeror must demonstrate adherence to the goals established in Table L.3-1 using Attachment 6 Small Business Subcontracting Plan Checklist.

3.6.2.1.2. Describe how specific subcontracting percentage goals and targets will be met for the ACES contract expressed in dollars and in percentages of the total contract dollars and total subcontracting dollars to each socio-economic small business category listed above.

The subcontracting goals and other targets may be met by any combination of subcontracts, other business teaming arrangements, or vendor purchases and should make use of small businesses to the maximum extent practicable.

3.6.2.1.3. Work performed in foreign countries is not applicable to these goals.

3.6.3. Aspect II: The Small Business Participation Commitment Document evaluates the Offeror’s corporate commitment. All Offerors shall include information concerning Extent of Small Business Participation. The Small Business Participation Commitment Document shall include the subcontracting goals expressed at the IDIQ contract level as a percentage of annual total contract dollars obligated on awarded Task Orders for each of the following: small business, small disadvantaged business, women-owned small business, HUBZone small business, and service disabled veteran-owned small business.

3.6.3.1. Element 4b): The Small Business Participation Commitment Document shall provide small business concerns (veteran-owned, service disabled veteran-owned, HUBZone, small disadvantaged business, and women-owned small business) the maximum practicable opportunity to participate in performing with established procedures pursuant to the terms of their subcontracts with small business concerns.

3.6.3.1.1. Small Business Offerors may include their own efforts when addressing the names, products and/or services and estimated total dollars planned to be provided by small business concerns. These requirements apply at the prime contract and first tier subcontract levels.

3.6.3.1.2. For proposal purposes, a notional obligated value is provided for completing the Small Business Participation Commitment Document. Offerors shall use a notional obligated value of $100,000,000.00 for each of ten (10) years for a total contract ceiling value of $1,000,000,000.00. Using the excel spreadsheet in Section J, titled ACES MAC Small Business Participation Commitment Document Calculation, Offerors shall fill in the yellow highlighted cells with the appropriate dollar amount and percentage. The Small Business Participation Commitment Document shall also describe the Offeror’s approach to meeting each of its subcontracting goals.

4. Volume II – Factor 2: Past Performance Information:

4.1. General

4.1.1. Volume II shall be prepared and organized IAW these instructions and Paragraph 4.2 of this Section L. Each Offeror’s proposal will be evaluated IAW the evaluation criteria in Section M. Offerors without a record of relevant past performance on contracts that are similar in size, scope and complexity, or for whom past performance is not available, will be evaluated neither favorably nor unfavorably on past performance. Volume II shall contain the following:

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

a. Table of Contents

b. Summary Page

c. Past and Present Performance Information (PPI) Reports (from PPI Tool)

d. Specific Content

e. Subcontractor Letters of Consent/Client Authorization Letters

f. Organizational Structure Change History

4.2.1. Volume II - Past Performance Information shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

4.2.2. Summary Page, limited to one (1) page, shall describe the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner for whom the Offeror is required to provide Past Performance Information IAW Paragraph 4.2.3 of Section L. The Summary Page shall also indicate the percentage and type of work the Offeror and each subcontractor, teaming partner, and/or joint venture partner will conduct.

4.2.3. Past and Present Performance Information (PPI). Offerors must use the PPI Tool (use the latest version from FBO.gov) to electronically submit the Past

Performance Information Report (PPIR) portion of the Past Performance Volume. The PPI Report(s) for each past performance contract shall be submitted under Volume II as printed out of the PPI Tool. Offerors are requested to limit responses for each past performance reference to those efforts necessary for evaluation and relevant to the ACES effort. No more than a cumulative total of six (6) contracts (could include major subcontractors, teaming partners, and joint venture partners) shall be submitted, identifying active or completed contracts (either Government or commercial), that Offerors consider relevant and consistent with the definitions in Section M in demonstrating the ability to perform the proposed effort. Only submit PPI for each prime, teaming partner, or joint venture partner, and for a major subcontractor performing meaningful work determined to be critical to overall successful performance. Each submitted contract must also meet the Recency and Relevancy requirements defined in Section L Paragraphs 4.4 and 4.5.

4.2.3.1. Key Personnel: The evaluation will be based on the Offeror’s/joint venture firm’s present/past performance and NOT on the key personnel of the Offeror’s/joint venture firm.

4.2.4. Ordering-Type Contracts Submission: In an ordering-type contractual vehicle, performance is demonstrated at the order level (i.e. a Delivery/Task Order). Therefore, if the contract being submitted is an ordering type contractual vehicle (for example, an Indefinite Delivery “D” type contract per FAR Subpart 16.5, Indefinite-Delivery Contracts), the Offeror shall also submit the individual Delivery/Task Order (or series of orders) for evaluation, in lieu of just the basic ordering contract itself. The Government will use the information submitted for each order (or series of orders) under one Ordering Contract to evaluate the effort’s recency, relevancy, and performance acceptability for that Ordering Contract.

4.2.4.1. Series of Orders: If a series of orders is submitted for evaluation, in lieu of the basic ordering contract, the Offeror shall provide the total dollar value and total period of performance for each order in the series. All orders (Task or Delivery) associated with a basic ordering contract shall be counted as one contract for the purposes of evaluation.

4.2.4.1.1. The Government will add up all total dollar values in the series of orders to arrive at a Total Dollar Value for the series of orders, to be used in the evaluation.

4.2.4.1.2. The Government will add up the Period of Performance of each order to calculate the Total Period of Performance for the series of orders, to be used in the evaluation. Only orders that meet the Recency definition in Section L Paragraph 4.4.1 will be evaluated.

4.2.4.1.3. The Total Dollar Value and Total Period of Performance for the submitted effort’s series of orders, as well as the technical complexities and programmatic/logistical scope and magnitude of effort, will be evaluated to arrive at a Relevancy Rating for the total effort.

4.2.4.1.4. The Government reserves the right to request additional information from the Offeror Points of Contact to verify the series of orders is for the same continuous technical scope.

4.2.5. Specific Content.

4.2.5.1. Offerors 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 an “Unacceptable” 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. In addition, explain corrective actions taken in the past, if any, for substandard performance and any current performance problems, such as cost overruns, extended performance periods, numerous warranty calls, etc.

4.2.5.2. Each offeror shall submit past performance information to demonstrate compliance with the requirements of FAR Subpart 52.219-8, Utilization of Small Business Concerns, including the extent to which small business performance objectives/requirements were met for the contracts that required submission of a Small Business Participation Commitment Document. Copies of contractual reports may be submitted to validate compliance with requirements of FAR Subpart 52.219-8. Submit eSRS data that documents your company’s compliance with previous Small Business Participation Commitment Documents or equivalent. Explanation of efforts where minimum quantitative requirements and/or goals were not met must be provided. All supporting documentation is excluded from the page count.

4.2.5.3. Each offeror shall submit past performance information to demonstrate compliance with the requirements of FAR Subpart 52.219-9, Small Business Subcontracting Plan - DEVIATIONS 2018-O0018 and 2019-O0005, including extent to which applicable goals and other small business performance objectives/requirements were met for the contracts submitted to demonstrate compliance. Explanation of efforts where goals were not met should be provided. All supporting documentation is excluded from the page count.

4.2.6. Subcontractor Letters of Consent and Client Authorization Letters.

4.2.6.1. Subcontractor Letters of Consent. Past performance information pertaining to a subcontractor cannot be disclosed to the prime Offeror without the subcontractor’s consent. Provide with the proposal a letter from all subcontractors that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the Prime Contractor. Consent Letters are executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing the release of past performance information so the Offeror can respond to such information.

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

4.2.7. Organization 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 present or past efforts or between 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, include with the proposal volume a “roadmap” describing all such changes in the organization of your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance acceptability assessment. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the Offerors, 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.

4.3. Early Proposal Information

4.3.1. Early proposal information associated with Volume II Past Performance is requested to be submitted within 30 calendar days after the request for proposal is posted. This will facilitate a timelier past performance evaluation.

4.4. Recent Contracts

4.4.1. To be recent, at least 12 months of the effort’s period of performance must have been performed during the past five (5) years from the date of issuance of this solicitation. Recently awarded contract must include at least 12 months of performance.

4.5. Relevant Contracts

4.5.1. Relevant performance is defined as efforts involving a similar scope and similar magnitude of effort and complexity as this solicitation requires, as described in the PWS and the Sections L and M Evaluation Factors and Subfactors.

4.5.2. Specific Content: Offerors shall explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. Also, the Offeror shall explain how the past performance effort is relevant to the percent of effort to be performed as identified in the PPIR. 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. 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.

4.5.3. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available or is so sparse that no meaningful past performance rating can be reasonably assigned, the Offeror may not be evaluated favorably or unfavorably on past performance [see FAR Subpart 15.305(a)(2)(iv)]. Therefore, the Offeror shall be determined to have unknown (or “neutral”) past performance [see FAR 15.305(a)(2)(iv)]. In the context of acceptability/unacceptability, a neutral rating shall be considered “acceptable”.

5. Volume III – Cost/Price – RESERVED for Task Orders

5.1. General

5.1.1. THIS VOLUME IS RESERVED FOR TASK ORDER PROPOSALS AND IS

NOT APPLICABLE TO THE MAC PROPOSALS. The Cost/Price Volume is to assist the Offeror in submitting information required to evaluate the reasonableness, completeness and balance of the Offeror’s proposed costs/prices.

Price or cost analysis may be evaluated at the Task Order level based on a customer's specific requirements and, if evaluated, instructions will be included in the individual Fair Opportunity Proposal Requests (FOPRs) as appropriate.

Offerors are, therefore, not required to propose a unit price or total amount for each CLIN in Section B at this time since unit prices and total prices will be required at the Task Order level.

6. Volume IV – Contract Documentation

6.1. Solicitation/Representations and Certifications

6.1.1. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Solicitation. The Offeror’s proposal shall also include a signed copy of each RFP Amendment.

6.1.2. Contractor Responsibility. To assist the CO in determining contract responsibility IAW FAR Subpart 9.1, Responsible Prospective Contractors, the Offeror shall have an approved accounting system and explain how they plan to maintain adequate financial capability for a contract of this magnitude and length.

6.1.2.1. Approved Accounting System for Performing Cost Type Contracts.

The Offeror shall provide a current (within 12 months from date of proposal submittal) audit report, finding, or letter from the Offeror’s cognizant Administrative Contracting Officer (ACO) or Defense Contract Auditing Agency (DCAA) office stating that the Offeror’s accounting system has been approved and/or is adequate for cost type contracts. If it has been over 12 months since the accounting system was reviewed, the Offeror shall provide a statement that the accounting system has not changed since being reviewed. If the accounting system has changed, a certification shall be provided indicating that the changes have not impacted the approval or adequacy of the accounting system. A cost-reimbursement contract may only be awarded when FAR Subpart 16.301-3, Limitations are met. This FAR reference establishes criteria for the Contractor’s accounting system to be adequate for determining costs.

Therefore, no award can be made to an Offeror whose accounting system has not been determined to be adequate for cost type contracts. This impacts all team member/subcontractors if the prime anticipates awarding cost type contracts to any of the subcontractors. If no cost type subcontracts are to be awarded, the Offeror shall so state. If cost type subcontracts are to be awarded, the Offeror shall provide the necessary information from the subcontractors.

6.1.2.2. Offerors must provide the last three years financial statements and Statements of Cash Flows for the firms or corporations proposed, 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. In addition to the aforementioned, Offerors shall explain how performance of the resultant contract will be funded. 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, identify the maximum lines of credit that may be available; include documentation to support the amounts and a point of contact and phone number for the lender.

The maximum lines of credit must be based upon the inclusion of this contract effort.

6.1.2.2.1. The information above shall be provided for the prime and all subcontractors with anticipated costs of $25,000,000 or more http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/09.htm#P7_489

(based on a potential five-year Task Order period of performance).

If the Offeror is a combination of firms (including joint venture partners, individual companies which comprise the proposed organization, and/or major and key subcontractors), discuss the financial responsibilities among the companies. Historical and year-to-date financial data shall be submitted for each company that makes up the Offeror, and the ability to fund contract performance shall be addressed for the combined firm.

6.2. Section A - Solicitation/Contract Form

6.2.1. Complete blocks 12-18 of the Standard Form 33, Solicitation, Offer and Award (SF33). Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept.

6.3. Section B - Supplies or Services and Costs/Prices

6.3.1. RESERVED

6.4. Section H - Special Contract Requirements

6.4.1. All Unique Contract Requirements are described in the special clauses in Section H of the RFP. The Offeror shall provide required information to complete special clauses as required.

6.5. Section I - Contract Clauses

6.5.1. All other contract clauses are listed in Section I of the RFP. The Offeror shall provide required information to complete clauses as required.

6.6. Section J – Attachments

6.6.1. The following Section J Attachments are included as part of the RFP:

1. Performance Work Statement

2. Exhibit A – Contract Data Requirements List (CDRL)

3. Small Business Participation Commitment Document Calculation

Spreadsheet

4. Past Performance Information (PPI) for Offerors

5. DD Form 254

6. Small Business Subcontracting Plan Checklist Template

7. Staffing Summary - ACES Manpower Matrix RESERVED

8. ACES Wage Determinations - RESERVED

9. Federal Equivalent Wage Rates - RESERVED

10. Incentive Plan Attachment – RESERVED

6.7. Section K - Representations, Certifications, and other Statements of Offerors

6.7.1. Complete representations, certifications, acknowledgments and statements.

Offeror is required to fill out an online provision FAR Subpart 52.204-8, Annual Representations and Certifications (Jan 2018). The Offeror shall insert “none” into FAR Subpart 52.204-8(d) [if applicable] to indicate that the fill-in was not missed.

6.8. Exceptions to Solicitation Requirements

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

Table L.6-1 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

PWS, Solicitation, ITO Attachments, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

6.9. Other Information Required

6.9.1. Authorized Offeror Personnel

6.9.1.1. Provide the name, title, telephone number and e-mail address of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.9.2. Company/Division Address, Identifying Codes, and Applicable Designations

6.9.2.1. Provide company division's street address, county and zip code;

Commercial and Government Entity (CAGE) code; Data Universal Numbering (DUNS) code; Taxpayer Identification Number (TIN); size of business (large or small); and labor surplus area designation.

6.9.3. Teaming Arrangements and/or Letters of Intent

6.9.3.1. If applicable, Offerors shall complete Proposed

Teaming/Subcontracting List.

6.9.3.2. If applicable, Offerors shall provide written contract teaming arrangement agreements, subcontracting letters of intent and other necessary agreements associated with joint ventures and mentor-protégés that clearly identify roles and responsibilities. All associated parties must sign the corresponding agreements. This information will not be counted towards Offeror page limitations (unlimited) as noted in Table L.2-1 Proposal Organization. If an Offeror proposes to use any kind of joint venture, the Offeror must provide a copy of that agreement. The joint venture agreement must be signed by all parties, clearly identify the roles and responsibilities of each party, and be submitted along with the Offeror’s proposal. The copy of the joint venture agreement provided by the Offeror will not be counted towards the Offeror’s page limitations (unlimited) as noted in Table 2.1 Proposal Organization.

6.9.3.2.1. If applicable, provide complete, verifiable information detailing the joint venture, to include any relevant and recent information on previous teaming arrangements with same partner. Submit information relative to the formation, organization and operation of the business unit. Additional information that should be submitted shall include cost and revenue sharing agreements and any other information which describes the business arrangement. Disclose existing or planned agreements between and among the principals, each company’s responsibility for financial management of the venture, the business systems contemplated for use by the entity and their location.

6.9.4. Government Field Support Agencies

6.9.4.1. Identify the cognizant Defense Contract Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) office responsible for administration of the Offeror’s Government contracts.

6.10. Alternate Proposals

6.10.1. No alternate proposals will be accepted.

6.11. Continuation of Essential Contractor Services

6.11.1.