N00019-15-R-0106_Amendment_0004.docx

N00019-15-R-0106

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, experience and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing, and competent to devote the resources necessary to meet all requirements; and has valid and practical solutions for all requirements and potential risk areas. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract. With the exception of the Volume 5 Price and Volume 6 Contract Administration, no price information should appear in any other volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the Offeror’s responsibility to present enough information to allow the various work efforts, support, and management approaches, as well as price, to be meaningfully evaluated. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and referenced as needed. Elaborate brochures or other presentations beyond that sufficient to present a complete and effective proposal are neither necessary nor desired.

Throughout these instructions, Offeror is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF)-33, Solicitation, Offer, and Award. “Principal Subcontractors” are defined as a subcontractor who provides at least 20% of the proposed total price for the contract (excluding the Offeror’s profit). A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. “Critical Subcontractors” are subcontractors that perform a critical function, whether technical or financial, in the performance of the resulting contract. Critical functions are scheduled and unscheduled engine overhauls. The term “entity” is used to mean any or all of the following: prime contractor, principal subcontractor, critical subcontractor, JV, and/or each JV team member or other subcontractor.

2.0 PROPOSAL FORMAT AND SUBMISSION

Proposals must be formatted using a Times New Roman 10 point font (no reduction permitted), single-spaced with 1-inch margins on all sides, and formatted for/printed on standard 8.5 x 11 inch paper. All pages should be numbered with volume, paragraph, and page numbers. When fold-out pages are used, they must not exceed 11 x 17 inches. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. Graphs and tables shall be presented in no smaller than a Times New Roman 10 point font. Graphs should contain a grid, which allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Each volume or annex shall be provided separately in a 3-ring binder. The binders should be of an appropriate thickness for the number of pages it contains (e.g., 30 pages shall not be placed in a 2-inch binder).

2.1 Electronic Submission of Proposal

This section provides information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section reduces the time and effort needed to receive and read electronic proposals.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically on CD-ROM(s) compatible with the operating system and applications defined in Section 2.1.2. The Offeror should put as much proposal material as possible on each CD-ROM, keeping the portions of the proposal that contain pricing information on separate CD-ROM(s) from the portions of the proposal that do not contain pricing information. For this solicitation, Volume 4 Price and Volume 5 Contract Administration contain price information and should be delivered on separate CD-ROM(s) from the remainder of the proposal. The Offeror should submit two sets of CD-ROMs that contain its proposal. One set of CD-ROM disks should be marked "Master," the other should be marked "Back-Up." Both sets of CD-ROM disks should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, and proposal volumes contained therein. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the original paper copy shall take precedence.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 7 operating system. The Offeror shall submit two identical proposals in separate, electronic versions: one version in Portable Document Format (.pdf) and one version in Microsoft Office 2010 Applications (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Project). The .pdf document must be fully searchable. The Offeror is responsible for ensuring that the .pdf and the appropriate Microsoft Office 2010 applications versions contain identical information. The Government shall have the discretion to use the information in either version, and shall not be responsible for any differences in content between the two proposal formats submitted by the Offeror. Use of other application software for submission of proposals is prohibited except where specific instructions for non- PDF or Microsoft Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes that do not include price information.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information has been checked for viruses, and specify the software, version, and virus definition used to check the data. With each subsequent submission of proposal information (e.g., responses to Evaluation Notices, Final Proposal Revisions, etc.), the Offeror shall ensure and certify that its files are virus free.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

a. Simplify the color palette used in creating figures;

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.7 Evaluation Hardware

The source selection facility uses the following type workstation computer systems and printers.

2.94 GB RAM

CD-ROM Drive

Windows 7 Operating System

2.1.8 File Naming Conventions

There is no limit to the number of files that may be submitted. However, it is preferable that each volume, book, or annex not be broken up into multiple electronic files. Valid extensions for files using their associated applications follow:

Files should have the following naming convention ("#" represents the sequential numbering of files and the suffix is for illustration, and may be .pdf, .docx, .xlsx, .pptx, or .mpp). For electronic file submissions (e.g. proposal volumes, annexes, appendices, enclosures) the Offeror should follow the basic structure of the file naming convention suggested in Table 2.1 “Offeror Electronic File Naming Convention.” Offerors shall keep the file name as short as possible (under 40 characters) so that it is accessible on Government share drives. The Offeror shall ensure that the electronically submitted file names are directly traceable to hard copy submittals. In general, the Offeror should provide each binder (e.g. volume or annex) as one separate file (i.e. do not provide each section/paragraph as separate files).

Table 2.1 Offeror Electronic File Naming Convention

Cover Ltr.docx

Vol 1 ES#.docx

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary Vol 1 ES Tables.xlsx Vol 1 ES Tables.pdf

Vol 2 PP#.docx

Vol 2 PP Rel Ad Ltr #.docx

Vol 2 PP POC Info#.docx

Vol 2 PPQ.pdf

Vol 2 PP-1 Con Data.xlsx

Vol 3 Tech#.docx

Vol 3 Tech CRM.pdf

Vol 3 Tech Exp#.pdf

Vol 3 Tech MP Chart#.xlsx

Vol 3 Tech SB Goals.xlsx

Vol 4 Price#.docx Vol 4 Price#.xlsx

Vol 5 CA#.docx

Vol 5 MC.docx

AnnA Rel SOW PWS #.docx

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one-for-one comparison between the information presented and these proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

In addition to the electronic copies requested in Section 2.1, “Electronic Submission of Proposal,” paper copies of each volume and annex of the proposal shall be submitted as specified in Table 3.0 Proposal Structure. The Offeror shall submit all paper and electronic copies of the proposal to the address provided in Section 4.0. Suggested page counts for each volume, if any, are also specified in Table 3.0 Proposal Structure (title and table of contents pages are not included in the suggested page count). Annexes do not have suggested page counts.

Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in Section B Specific Instructions and do not count towards the suggested page count. Additionally, the individual subcontracting reports for the past performance volume is not included in the suggested page count.

Table 3.0 Proposal Structure

(Virus free electronic submission guarantee)

3 Copies

Attachment L-1 Table ES-1 Offeror Summary Attachment L-1 Table ES-2 Relevant Contract Summary

2 Copies

1 Copy

1 Copy

1 Copy

*Not included in the suggested page count

Each binder must contain the following information:

a. Cover and title page;

b. Title of proposal and proposal number, as applicable;

c. Offeror’s name, address, and POC;

d. Solicitation number;

e. Proposal volume or annex number;

f. Copy number;

g. Table of Contents (The table of contents must provide sufficient detail to easily locate important elements. At a minimum, it must include the paragraphs identified in the CRM.); and

h. Tabs and dividers.

Table 3.1 lists the attachments provided to the Offeror with Section L, to assist with proposal development.

Table 3.1 Section L List of Attachments

Table ES-2 Relevant Contract Summary

No price information, (e.g., dollar values and/or hourly rates) shall be included in any volume other than Volume 4 Price and Volume 5 Contract Administration.

4.0 PROPOSAL SUBMISSION

The Offeror shall clearly mark all packages with the solicitation number. The submission date for all volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the solicitation. However it is requested that one hard copy and one electronic copy on a CD-ROM of Volume 2 Past Performance, Table PP-1 (Past Performance Contract Data); as well as Volume 1 Executive Summary, Table ES-1 (Offeror’s Summary); and Volume 1 Executive Summary, Table ES-2 (Relevant Contract Summary) be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9). Please indicate any changes made to the information delivered three weeks early in the submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation. If no changes are made, please state so at the beginning of Volume 1 Executive Summary and Volume 2 Past Performance.

Questions regarding delivery of proposals may be directed to Deborah Karstens, (301) 757-7012, Deborah.Karstens@navy.mil. Offerors shall submit proposals via United States Postal Service, commercial carrier, or by hand to Deborah Karstens, Contract Specialist, at the address below. Initial and final proposals shall not be submitted by facsimile or electronically via email.

Naval Air Systems Command Deborah Karstens, AIR-2.3.5.1.4 Solicitation Number: N00019-15-R-0106 21936 Bundy Road, Bldg. 442 Patuxent River, MD 20670

5.0 PROPOSAL PACKAGING

The Offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible, grouping like volumes to the maximum extent possible. Each box should identify its contents by including a packing slip detailing each volume number and title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and the inside carton shall be stamped or marked ― “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104,” and marked for Deborah Karstens, NAVAIR Contract Specialist, AIR-2.3.5.1.4. The Master Set shall include all original proposal volumes, all proposal volumes on CD-ROM, a completed and original signed Standard Form 33; acknowledgement of all solicitation amendments, if applicable; and Representations, Certifications and Other Statements of Offerors or Respondents (Section K of this RFP), and other applicable fill-ins. Note: Any documents which contain price data shall be on a separate CD-ROM(s) from the other CD-ROMs.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

7.0 CHANGES TO SOLICITATION

All amendments to this solicitation shall be posted at https://www.fbo.gov/ Search the database for the solicitation number N00019-15-R-0106

8.0 TECHNICAL LIBRARY

A Technical Library of information directly related to the requirements of solicitation N00019-15-R-0106 will be available, on www.FedBizOpps.gov to all Offerors intending to propose as a prime.

Point of contact for questions related to the Technical Library::

Deborah Karstens, Contract Specialist

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

Attachment L-1 Executive Summary Tables

· Table ES-1 Offeror Summary

· Table ES-2 Relevant Contract Summary

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding price. Each section within the Executive Summary shall contain the salient points contained in each of the proposal volumes. In addition, this volume should be used by the Offeror to identify and highlight significant features of its proposal. The Executive Summary volume should be divided into the areas outlined below:

1.1 Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment and submit it as a separate electronic file.

(2) The Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are provided in Table ES-1 (Offeror Summary). The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason.

Note: Place of Performance for this solicitation pertains to the physical location of the prime contractor, all subcontractors, and JV team members that are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

1.2 Relevant Contract Summary Table

The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance and Technical for the relevant entities. The Offeror shall complete the table according to the instructions within the attachment and submit it as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 2 Table PP-1 (Past Performance Contract Data) and Volume 3 Technical Experience Summary Attachment L-5 (i.e., the contract identified as P1 in the ES-2 Relevant Contract Summary Table is the same P1 contract identified in Past Performance and the same P1 contract identified in Technical Experience Summary).

1.3 Past Performance

The Offeror shall provide a summary of the prime contractor, principal subcontractors, critical subcontractors, and JV team members’ past performance and systemic improvements which pertains to the tasks required by this solicitation.

1.4 Technical

The Offeror shall provide a summary of the effort and identify how its approach addresses the requirements of this solicitation as well as the salient features of the Offeror’s management approach.

1.5 Contract Administration

The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 5 Contract Administration.

1.6 Photographs

The Offeror may provide up to five electronic photographs for the proposed approach to assist the Government in understanding the Offeror’s capability. The electronic photographs must be in a standard readable format, e.g. Joint Photographic Expert Group (JPEG). Any text placed on these pictures shall contain factual information only, i.e., no “marketing.”

2.0 VOLUME 2 – PAST PERFORMANCE

Note: This volume shall not contain any reference to the price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

For this volume, the Offeror shall identify relevant contracts, or those portions of a relevant contract, whose performance is within five years of the proposal due date and contains efforts similar to those efforts (e.g., service, type effort, contract tasks, contract type, contract dollar value, etc.), required by this solicitation for the prime contractor, principal subcontractors, critical subcontractors, and JV team members, identified in Table ES-1 (Offeror Summary). Offerors shall also identify relevant contracts within the past five years that had any show-cause notices, cure notices, or termination for default.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary paperless method used to retrieve the CPARS for this source selection. For all contracts identified that do not have CPARS, the Offeror shall forward a copy of Attachment L-2 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM), or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail or fax to:

Deborah Karstens, Contract Specialist

The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

2.1 Authorization Letter(s)

Within this section as a separate electronic file, the Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each participating principal subcontractor, critical subcontractor, JV team member, authorizing the release of adverse past performance information to the prime contractor. This authorization letter allows the Government to coordinate past performance issue(s) with the Offeror. For any subcontractors or JV team members that do not provide an authorization letter with such written consent, the Offeror shall state that adverse past performance issues shall be coordinated directly with the subcontractor and past performance contact information shall be provided. The point of contact information shall include a name, address, phone number, and email address for each subcontractor, or JV team member, with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if Offerors do not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the subcontractor or JV team member, and the Offeror will forfeit the opportunity to participate in any related discussions.

2.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-3 Table PP-1 (Past Performance Contract Data), following the instructions provided within the attachment and submit it within this section as a separate electronic file. Please note that this form is a summary of the prime contractor, principal subcontractors, critical subcontractors, and JV team members’ relevant contract data. All detailed information and comparative analysis of the past performance references to this solicitation’s requirements shall be provided in Volume 2, Section 2.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing this volume and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e. the contracts identified as P1, S1, T1 etc.)

In general, recent performance will be considered more relevant than older performance. Commercial contracts may be included. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

2.3 Evaluation

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each contract or task order identified in Attachment L-3 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, demonstrated systemic improvement, earned value, and award fee as described below, organized by contract. As this information is presented in the proposal, demonstrate the relevancy of the prime contractor, principal subcontractors, critical subcontractors, and JV team members’ past performance with respect to this solicitation’s requirements. For any contracts referenced where the Prime, principal subcontractors, critical subcontractors, and/or JV team members are aware of problems, the Offeror shall describe the issues in section 2.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 2.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the contracts are deemed relevant to this solicitation’s requirements. To demonstrate relevancy, Offerors should provide a comparative analysis to this solicitation’s requirements. In Annex A, Offerors should provide two electronic copies of the Statement of Work/Performance Work Statements (SOW/PWS) from each of the referenced contracts identified in Table ES-2. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOW/PWS to clearly identify how past tasks performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be referenced/identified, and do not need to be broken out separately from the complete SOW/PWS.

(1) The Government will assess each contract and assign a relevancy rating.

i. The following relevancy definitions will be used:

Very Relevant (VR) – Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant (SR) - Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant (NR) - Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

ii. The following will be considered when determining the relevancy assessment rating with regard to subcontractors:

The contract relevancy assessment should be relative to the prime contractor, principal subcontractors, critical subcontractors, and JV team members’ proposed role/responsibility identified in Table ES-1 (Offeror Summary) versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only 10% of the hypothetical solicitation’s effort, the previous contract relates to 100% of the subcontractor proposed effort for the hypothetical solicitation and, therefore, is considered Very Relevant vice Somewhat Relevant.

(2) Offerors are advised that contracts assessed as Not Relevant by the Government will not be considered in the Past Performance assessment. Contracts or the portion of those contracts submitted by the Offeror that meet any of the conditions below will be assessed as Not Relevant:

i. Contracts from an entity that does not have a defined role and responsibility identified in Table ES-1 (Offeror Summary);

ii. Contracts from a different physical location (e.g., with different CAGE code/DUNS) than the entity proposed in Table ES-1 (Offeror Summary);

iii. Contracts that involve little to none of the scope, magnitude of effort and/or complexities required by this solicitation; or

iv. Contracts, or those portions of the contract, whose performance is older than 5 years from the proposal due date. (If only a portion of a contract is older than 5 years, then only that portion is Not Relevant for reasons of recency.)

(3) Past performance of any entity with multiple CAGE codes/DUNS will be considered for the same physical location if they have distinct roles and responsibilities identified in Table ES-1 (Offeror Summary), or the current and previous CAGE codes were created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. However, all current CAGE Codes/DUNS must appear in Table ES-1 which indicates a commitment of work for those entities. To facilitate the relevancy determination, the Offeror shall provide an explanation of why multiple CAGE codes are proposed, identify all applicable CAGE codes along with their defined roles and responsibilities, and provide a description of all such changes in the organization of the company within Volume 1.0, Executive Summary if past performance for a previous CAGE code/DUNs is submitted. In addition, the Offeror shall provide a narrative within this section explaining how the changes impact the relevance of any past performance contracts provided.

(4) The comparative analysis utilized to determine relevancy, should show how similar the past performance contract reference is to this solicitation with regard to scope of effort (consider PWS tasks); magnitude of effort (consider dollar amount); and complexity (consider attributes of the work being performed such as type of effort, frequency such as turn-around-time or delivery rate, number of sites, skills, processes, contract type, etc.)

b. Past Performance Information: Provide a brief description of performance in delivering quality products in each of the areas identified below. Include in these descriptions any information that demonstrates the level of performance obtained, and where available, provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

(1) Technical Performance: meeting technical requirements (i.e., the quality of your technical performance, e.g., maintaining aircraft in flyable status, performing supply chain management);

(2) Schedule Performance: meeting schedule requirements (i.e., schedule performance, e.g., meeting aircraft schedule, meeting emergent aircraft request);

(3) Cost Performance: controlling contract cost (i.e., cost performance e.g., within the budget, actual vs. contract cost, and cost metrics);

(4) Management Performance: managing the contracted effort (i.e., program management, e.g., cooperation with customer, subcontract management); and

(5) Small Business Utilization: The Small Business Offeror may provide this information in a format substantially the same as the Individual Subcontracting Reports (ISR). If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, the Offeror shall provide copies of DCMA's most recent “Review of Contractor's Comprehensive Subcontracting Program” (DCMA Form 640), and three final or most recent SF 295s/Summary Subcontracting Reports (SSRs), and explain how the results shown in these documents demonstrate the realism of their proposed SB Utilization Strategy. If applicable, note whether the contract met or exceeded Small Business (SB), Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB) small business utilization and subcontracting goals. All Offerors providing this information must explain how this information translates to reasonableness of their proposed SB Utilization Strategy goals provided in Volume 3, Technical.

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems identified in 2.3.b Past Performance Information. Provide the records of such results and indicate where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools used to correct problems on the contract and, if applicable, how these techniques, elements, and tools may be used for this contract. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and to demonstrate that the past problem will not occur on this contract. It is incumbent upon the Offeror to explain the relevance of the data provided and substantiate that improvements from past performance problems are being made. The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. Consideration for discounting problems may be given when those problems are addressed through demonstrated systemic improvement. Demonstrated systemic improvement may be indicated by information as it relates to preventing recurrence of past problems, including: identification of the root cause of a problem, a corrective action plan that systemically addresses the past problem, how and when the plan was implemented, documented timeframe to demonstrate when corrective action was implemented and became successful; and performance data, preferably through Government records, to show performance improvements.

3.0 VOLUME 3 - TECHNICAL

Note: This volume shall not contain any reference to the price aspects of the offer.

The following is a Section L Attachment that the Offeror shall utilize to provide information for this volume:

Attachment L-4, Cross Reference Matrix (CRM) is provided to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s CRM may be identical to the one provided or revised to add information. For example, the Offeror’s CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Throughout the Technical Volume the Offeror should identify any proposed capability, approach or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government. The Offeror should also identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to performance, operations and/or risk. Appreciably exceeding requirements that are expressed as a minimum or threshold requirement can potentially produce performance or operational benefits. Beyond the point where there is no additional performance or operational benefit, risk reduction may be assessed. Additionally, a proposal that provides the Government with a capability, service or resource that is not specifically required, but benefits the Government can have merit if it appreciably enhances performance and/or operations to benefit the Government. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable contract within the proposed price.

3.1 Transition Phase-In

In Annex C, provide a Transition Phase-In Plan that addresses the elements listed in the solicitation Attachment 1, PWS, paragraph 4.0. Describe the Offeror’s approach to initiating this program and provide a detailed Plan of Action and Milestones (POA&M) for actions that will be required to begin full performance of work in accordance with the requirements of this solicitation, including obtaining base access. Identify the major challenges with regard to start-up and provide an approach to mitigate risk. Provide a detailed plan to train personnel during transition, including method for incorporation of lessons learned at previous site transition(s), and formal certification/licensing procedures for personnel. The Offeror shall submit a detailed time phased manning plan that indicates staffing by site, and function during transition. Indicate an eventual "ramp-up" to achieve full manning levels and performance.

3.2 Experience

The Offeror shall demonstrate the degree to which its previous experience is similar to this solicitation, particularly with respect to performing aircraft maintenance and flight operations on commercial derivative aircraft similar to UC-35 type aircraft in an OCONUS/CONUS environment at multiple sites. The Offeror shall describe its experience in management of multi-site, Contractor Logistics Support including acting as the prime contractor, providing program management and subcontractor management for similar type of work, scope of effort and complexity with respect to the solicitation. Describe any long-term support agreements with proposed principal subcontractors.

The Offeror shall only reference the contracts submitted for the Past Performance evaluation to demonstrate its experience. As a minimum, complete Section L Attachment L-5, Experience for each reference contract, specifically citing the current/previous contracts from where this information pertains, using the contract reference numbers specified in Table ES-2. No information on individual employee experience of the prime contractor, principal subcontractors, and other principal entities should be submitted as part of this proposal; this information will not be considered in this experience evaluation. If proposing as a JV team, Offerors should include the experience of the JV as a whole, as well as the experience for each JV team member.

3.3 Staffing and Manning

3.3.1 Staffing and Manning

The Offeror shall demonstrate that the proposed manning, personnel skill levels, expertise, and experience are adequate to perform the work required by this solicitation. Identify the number of people and skill level mix for all periods of performance by platform using RFP Section B, including the transition phase. Describe how the proposed manning and personnel plan will accomplish the requirements of this program using RFP Section B. Provide a staffing plan that includes the following:

a. Manning Chart – Use Attachment L-6, Manpower Chart, as a template for developing Annex B, a manpower staffing chart. Include proposals by position, by labor category and by the number of personnel assigned. Explain how the proposed manpower numbers were established. Specifically, provide definition of work year capabilities of the work force (equivalent man hours/year analysis). Identify on-site and off-site personnel.

b. Manning Distribution – Provide the proposed maintenance organizational structure by department. For each department describe the composition, responsibilities, and titles for all on-site and off-site personnel. Identify all indirect labor classifications, titles, responsibilities.

c. Personnel - Describe the processes used in hiring, recruiting, and retaining personnel. Describe the approach used to fill all positions required for each labor category and the approach for retention.

d. Training - Provide certification and skill level for each labor category to fulfill the requirements described in the PWS. Describe how training certifications will be met and kept current.

3.3.2 Aircraft Survivability Equipment (ASE) Personnel Training and Qualification Describe the training, qualifications, and certifications required for Aircraft Survivability Equipment personnel (include any ordnance qualification and certification as necessary). Describe the re-certification and training programs required to maintain safety qualifications for site/management level personnel qualifications to meet the requirements of the PWS. The Offeror shall describe its approach to maintaining a replacement parts pool and reworking parts needing repair for ASE.

3.3.3 Supporting Multiple Detachments

Describe the approach for maintenance and logistics support of base operations and simultaneously supporting Operation Freedom’s Sentinal (OFS). Support for OFS may originate from any of the sites identified in the PWS Section 1.2, deploying to one OCONUS location not already a base operation site under this contract. Include the following in the description of your approach:

a. Describe the coordination with the Government site operations personnel to ensure operational requirements and commitments are met. Describe how the tailoring of manpower, qualifications and work shifts will provide maintenance and logistics support coverage for the OFS detachment.

b. Explain how the detachment support structure and personnel will interface and integrate with the primary operating site and the contractor’s home office for supporting the detachments in the following areas:

1. Maintenance support of the detachment

2. Supply and logistics support

3. Support equipment

3.4 Maintenance and Maintenance Management

3.4.1 Maintenance Management

Demonstrate how the Offeror intends to manage all Type/Model/Series (T/M/S) as required by the PWS. Describe how the maintenance organization will control the scheduled and unscheduled maintenance process to ensure meeting the minimum operational performance standards for Mission Capable (MC) aircraft availability described in Appendix H, Performance Metrics of the solicitation.

3.4.2 Aircraft Maintenance

a. Process Description- Describe the process to identify damage if required, parts and materials, repair team staffing, induction scheduling, and projected duration of work required.

b. Process Description - Describe the planned on-site organizational and depot level maintenance processes for aircraft, components, and associated support equipment.

c. Describe the procedures to store, update, distribute, and ensure that current technical data is used in the maintenance and logistics support process.

d. Describe the procedures for handling emergency and drop-in maintenance, damage repair and any other Over & Above work.

3.4.3 Engine Management

Describe the Offeror’s approach to scheduled and unscheduled engine maintenance to ensure meeting the minimum operational performance standards for aircraft engine availability described in PWS Section 12.0. Include the following in the description of your approach:

a. Describe the Offeror’s approach to performing on-wing Hot Section Inspection (HSI) of the engines.

b. Describe the Offeror’s process for maintaining configuration control of engines.

3.5 Depot Maintenance Facility

Demonstrate that the proposed depot maintenance facility is an FAA certified repair facility and maintains one of the following certificates:

1. An FAA FAR Part 145Airframe Class 4 Repair Station Air Agency Certificate; or

1. FAA FAR Part 145 Limited Rating Certificate for any model of Cessna 560.

3.6 Web-Based Information System

Describe the Offeror’s approach to provide a secured Web-Based Information System (WIS) that provides computerized storage of supply logistics support information with web based accessible interactive query and update capability on a real-time basis as described in PWS Section 3.16.

a. Describe the process to provide the Government with real-time aircraft and engine maintenance data while WIS maintenance is being performed to ensure minimum accessibility and interruption occurs.

b. Describe the scheduled and unscheduled maintenance process to ensure WIS meets requirements as described in PWS Section 3.16. Describe the process to ensure the Government is provided real-time aircraft and engine maintenance data during periods of WIS inaccessibility and interruption.

3.7 Small Business Utilization Strategy

All Offerors shall address their strategies for utilizing Small Business (SB) Concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. Offerors may meet this requirement using work they perform themselves.

For purposes of this solicitation, the term SB Concern shall also include the subcategories of Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB). Each subcategory of SB shall be addressed.

In describing its SB Utilization Strategy for this solicitation, the Offeror shall, as applicable:

a. Describe the extent of participation of SB Concerns on this contract, including a detailed description of the supplies and services for each SB Concern subcategory, and the complexity and variety of the work SB Concerns are to perform.

b. For each SB Concern identified in the proposal, provide the SB Concern's CAGE Code, or, if the SB Concern is not registered in the System for Award Management (SAM), at a minimum provide evidence of self-certification in accordance FAR 19.703(b) as an SB Concern. Where possible, provide documentation regarding enforceable commitments to utilize each SB Concern.

c. Provide goals, expressed as dollars and percentages of total contract values and percentages of total subcontract values for SB Concerns and each subcategory of SB, using the format provided in Attachment L-7 Small Business Goals.

3.8 Subcontract Management Strategy - The Offeror shall provide its subcontract management strategy for assembling teams, selecting subcontractors, maintaining subcontractor relationships, communicating information to the subcontractor, managing subcontractor performance, and problem resolution. The Offeror shall describe how its subcontract management strategy supports its role as the prime contractor. In describing its subcontract management strategy, the Offeror shall also address those aspects that will be accomplished through a subcontracting approach, including how the subcontract management strategy will be employed.

a. Describe the process that will be used to determine the complexity and variety of the work small businesses are to perform; and

b. Describe the process that will be used to ensure maximum practicable participation of small businesses for each delivery order/task order.

4.0 VOLUME 4 - PRICE

The following is a Section L Attachment that the Offeror shall utilize to provide information for this volume:

Attachment L-8 Price Matrix

4.1 Volume Content

This volume shall contain the following information for evaluation purposes:

1. The completed RFP Section B. The Contractor shall fill in each CLIN’s Unit Price and Total Price in accordance with the RFP Section B Pricing Notes.

2. The completed Attachment L-8 Price Matrix. The Contractor shall fill in the cells for “Unit Price” and “Total” in accordance with the RFP Section B Pricing…