NTWL_N00421-15-R-0044-0003_RFP_Release_to_FBO_20151105.docx

N00421-15-R-0044

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. Proposals should 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. Cost/Price information, (e.g., dollar values and/or hourly rates) shall appear only in Annex B ((Small Business Subcontracting Plan) and Table T-3 (Small Business Goals)), Volume 5 (Cost/Price), and Volume 6 (Contract Administration). 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 responsibility of the Offeror to present enough information to allow the various work efforts, support, and management approaches, as well as Cost/Price, to be meaningfully evaluated without discussions. Unsubstantiated statements that the 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 summarized and referenced in other areas if an overlap exists. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is 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. 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. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g. any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance and corporate experience evaluations: (a) the prime contractor; (b) JV Team Members; and (c) other entities that perform at least 15.00% of the proposed total cost/price for the contract minus the ODC CLINs (X031 – X038) costs. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 5 Cost/Price and associated with a commensurate dollar value.

2.0 PROPOSAL FORMAT AND SUBMISSION

Proposals must be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. All pages should be numbered with volume and page numbers. When fold-out pages are used, they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. If the Offeror uses graphs to convey information the graphs must show enough detail to easily discern the information described. Graphs and tables should be presented in no smaller than a 10 pt 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. Text utilized in charts, figures, and graphics should also be no smaller than a 10pt font and may use a font type selected by the Offeror. Each volume, book, or annex should 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. a 30-page book should not be placed in a 2-inch binder).

2.1 Electronic Submission of Proposal

This section is intended to provide 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 will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically.

2.1.1 Electronic Proposal Media

The Offeror should submit all volumes of its proposal electronically on CD-ROM(s) compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications) below. 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, Annex B ((Small Business Subcontracting Plan) and Table T-3 (Small Business Goals)); Volume 5 Cost/Price; and Volume 6 Contract Administration contain cost/price information and should be delivered on separate CD-ROM(s) from the remainder of the proposal.

Table G-4 (Proposal Structure) identifies the number of sets of CD-ROMs that contain its proposal the Offeror should submit. The first set of CD-ROM disks should be marked "Original. Subsequent sets of CD-ROM disks should be marked "Copy 1, Copy 2, etc.” The 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.

The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4 (Virus Free Electronic Submission). If a discrepancy exists between the original paper copy of the proposal and the original electronic copy on the disk, the original electronic copy shall take precedence.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft (MS) Windows 7 Operating System. Each CD-ROM submitted by the Offeror shall contain two identical proposals in separate, electronic versions: one version in Portable Document Format (.pdf) and one version in Microsoft Office 2010 Applications (e.g. 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 Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes. However, there shall be no links from volumes that do not contain cost/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 delivered throughout the evaluation (e.g. original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been or will be checked for viruses and certify that its files are/will be virus free. The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

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 and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.7 Evaluation Hardware

The source selection facility uses the computer systems and printers noted in Table G-1.

Table G-1 Evaluation Workstations and Printers

2.94 GB RAM

CD-ROM Drive

Microsoft Windows® 7 Operating System

2.1.8 File Naming Conventions

Valid extensions for files using their associated applications are listed below in Table G-2 (file Extensions):

Table G-2 File Extensions

The Offeror shall follow the basic structure of the file naming convention in Table G-3 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g. proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offeror’s shall keep the file name as short as possible (under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt/inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. 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. Offerors shall not provide each section/paragraph as separate files.

The Offeror shall ensure that the electronically submitted files are directly traceable to hard copy submittals.

Table G-3 Offeror Electronic File Naming Convention

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

Table CE-1 Corporate Experience Cross Reference Matrix

Vol 4 CE CRM.xlsx and Vol 4 CE CRM.pdf

Vol 5 Cost_Price#.pdf and Vol 5 Cost_Price#.docx

ANNEXES

Please note: The Offeror should provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

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.

Each volume and annex of the proposal shall be submitted as original and additional hard and/or electronic copies as specified in Table G-4 (Proposal Structure). The Offeror shall submit all paper and/or electronic copies of the proposal to the address provided in section 4.0 (Submission and Packaging). Suggested page counts for each volume, if any, are also specified in Table G-4 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.

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 Part B Specific Instructions and do not count towards the suggested page count. Additionally, the individual subcontracting reports for the past performance volume are not included in the suggested page count.

Cost/price information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than Annex B ((Small Business Subcontracting Plan) and Table T-3 (Small Business Goals)); Volume 5 Cost/Price, and Volume 6 Contract Administration.

Table G-4 Proposal Structure

Each binder must contain the following information:

i. Cover and title page;

ii. Title of proposal and proposal number as applicable;

iii. Offeror’s name, address and POC;

iv. Solicitation number;

v. Proposal volume/annex number;

vi. Copy number;

vii. Table of Contents (The table of contents must provide sufficient detail to easily locate important elements); and

viii. Tabs and dividers.

Catalog Card - Each volume must contain an 8 1/2" x 11" Catalog Card containing the information required for the cover and title page. The back of the card must be formatted with three columns entitled "Name", "Date Out", and "Date In". This card must be removable from the back of each binder.

Table G-5 lists the attachments provided to the Offeror within Section J, to assist with proposal development.

Table G-5 Section J List of P Attachments

4.0 PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 PROPOSAL SUBMISSION

For proposal validity information, see Section A, PROPOSAL VALIDITY DATES (Solicitation/Contract Form) of the solicitation. 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 (Solicitation, Offer and Award) of the solicitation. However it is requested that electronic copies of Volume 1, Table ES-1 (Offeror Summary) and Table ES-2 (Relevant Contract Summary); Table PP-1 (Past Performance Contract Data); Volume 4, Table CE-1 (Corporate Experience Cross Reference Matrix); and Annex C (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance and Corporate Experience) be submitted two weeks prior to the submission date/time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award). Offerors that desire to update information submitted prior to the submission date/time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) may do so any time up to the date/time specified.

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with the Procuring Contracting Office (PCO) and/or contract specialist listed below. Proposals shall be submitted using the address provided below. Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

Contract Specialist AIR 2.5.1.12.8 Ms. Denise Morrissette

(301) 995-2683 Denise.Morrissette@navy.mil

Contracting Officer AIR-2.5.1.12.1 Mr. Benjamin Washburn

(301) 757-9712 Benjamin.Washburn@navy.mil

Procuring Contracting Officer AIR-2.5.1.12 Mr. Daniel Chambers

(301) 757-9796 Daniel.Chambers@navy.mil

NAWCAD Contracts (ATTN: Mr. Daniel Chambers / Mr. Ben Washburn / Ms. Denise Morrissette) Solicitation Number: N00421-15-R-0044 21983 Bundy Road Bldg 441 Patuxent River, MD 20670

4.2 PROPOSAL PACKAGING

The Offeror 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/annex number and title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and shall contain only pertinent shipping /mailing information. The inside carton shall be stamped or marked ― For Official Use Only; and Source Selection Information – See FAR-2.101 and 3.104, marked for the intended recipient in 4.1 (Proposal Submission). The original set of proposals should be marked for NAVAIR PCO, AIR-2.5.1.12 identified in Section 4.1 (Proposal Submission). The original set shall include a hard copy of the original proposal, 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 solicitation) and other applicable fill-ins. Note: Any documents which contain Cost/Price data shall be on a separate disk(s) from the non cost/price proposal information.

5.0 CHANGES TO SOLICITATION

For any changes and additional information to the solicitation please go to website:

https://www.fbo.gov/

Search the database for solicitation number N00421-15-R-0044.

6.0 TECHNICAL INFORMATION - SECTION L ATTACHMENTS

The three sets of attachments with information directly related to the requirements of this solicitation follow: Section J attachments (e.g. PBSOW, CDRLs), Section L attachments (e.g. historic maintenance and manpower data, anticipated aircraft load), and Section P attachments (e.g. documents offerors need to complete proposals). Section J and Section P attachments will be available on FedBizOps.

https://www.fbo.gov

Section L attachments will be made available, upon request, to all Offerors intending to propose as a STOPPED HERE ON 4 FEB 2015age in Genereal Section"reagrading rleevnat entities within the General Section.erformance Contract DaPrime Offeror. Distribution of data contained in the library to team members, partners, subcontractors, suppliers and/or vendors shall be the responsibility of the prime that was granted access and shall be limited to a “need to know” basis. All guidance contained herein with regard to handling, distribution and destruction of the data shall be flowed down to all team members, partners, subcontractors, suppliers and/or vendors.

To obtain the Section L attachments, send a written e-mail request to the Contract Specialist and PCO identified in Section 4.1 (Proposal Submission) with the company name, address, CAGE Code and DUNS, as well as the name, e-mail address, and phone number of a point of contact.

Upon review of the written request and approval of Potential Offeror’s eligibility status to access the data, Section L attachments will be sent via email to the POC. Those who take receipt of any Section L attachment data shall comply with all laws, export controls, and distribution statements associated with the data.

It is the responsibility of the Offeror to request all data needed to provide a proposal, including information referenced in the solicitation or needed to propose that cannot be obtained via public access. Requests for additional information not contained in the Technical Library should be made to the PCO and Contract Specialist. All Offerors, other than the successful Offeror, are required to destroy all original or copied data files from any and all storage media and provide proof of such destruction via signed letter on corporate letterhead sent to the PCO within 30 days after contract award to the above address listed in Section 4.1 (Proposal Submission). The PCO may extend the 30 day requirement upon request.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

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

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

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding cost/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 sections outlined below:

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment P-1 (Executive Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ (the prime contractor, JV, JV Team Members, any subcontractor, and any corporate parent, division, subsidiary, or affiliate) proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 5 Cost/Price and associated with a dollar value commensurate with the Percent of Total Proposed Cost/Price (minus the ODC CLINs (X031 – X038) costs) identified in Table ES-1 (Offeror Summary). Therefore, this table must be a reflection of what is proposed in Volume 5 Cost/Price.

(2) The Offeror shall provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship. In addition, 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. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason. However, all CAGE codes must be appropriately identified in the table to be considered.

Table ES-1 Offeror Summary

Offeror:

of Entity

b. Relevant Contract Summary Table The Offeror shall complete Table ES-2 (Relevant Contract Summary) provided in Attachment P-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance and Corporate Experience for the principal entities. Complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 (Past Performance) Table PP-2 (Past Performance Contract Data) and Volume 4 (Corporate Experience) Table CE-1 (Corporate Experience Cross Reference Matrix). For example, the contracts identified as P1, T1, or S1 in the Relevant Contract Summary Table are the same P1, T1, or S1 contracts identified in the Past Performance Contract Data Table which are the same P1, T1, or S1 contracts identified in the Corporate Experience Cross Reference Matrix Table.

Table ES-2 Relevant Contract Summary

Offeror:

Referenced in:

Reference

(Past Performance) Volume 4 (Corporate Experience)

P2

P3

T2

T3

T4

S2

S3

S5

c. 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 approach;

d. Past Performance The Offeror shall provide a summary of the principal entities’ past performance and systemic improvements which pertain to the tasks required by this solicitation;

e. Corporate Experience The Offeror shall provide a summary of the principal entities’ corporate experience which pertains to the tasks required by this solicitation;

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

2.0 VOLUME 2 - TECHNICAL

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

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

The Offeror shall complete Table T-1 (Technical Cross Reference Matrix), provided in Attachment P2, and submit it as the first page within this section and as a separate electronic file. The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Technical 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.

Table T-1 Technical Cross Reference Matrix

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. 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 cost/price.

2.1 Management Approach

The Offeror shall:

a. Provide an overview of the management approach. Include recruitment, retention, and professional development;

b. Describe the management approach to organize and manage a workforce at the following locations. Describe any innovation and efficiencies gained from the Offerors management approach.

(1) TPS (Hangar 110);

(2) HX-21;

a) Hangar 111/B2832

b) Hangar 109

(3) VX-20 (Hangar 306)/B510;

(4) VX-23 (Hangar 115); and

(5) Hangar 301/B507.

c. Describe the lines of authority and the levels of responsibility of management personnel;

d. Provide a high level organizational chart that clearly reflects the position of this program within the structure of the corporate organization; and

e. Describe the approach to managing the Collective Bargaining Agreement (CBA) for this solicitation. To include:

(1) Daily management and resolution of union grievances;

(2) Plan to negotiate the CBA, including a narrative of impact on contract costs; and

(3) Strike contingency plan.

2.2 Manning Approach

Demonstrate the proposed manning/personnel skill levels, and expertise to perform the work required by this solicitation. The Offeror shall provide an approach that includes, but is not limited to, the following:

a. Manning – Complete Attachment P-3 (Table T-2 Manning) and provide it as Annex A (Manning). Identify by labor category the number of FTEs and requisite skill level mix broken down by periods of performance, by location, and for each location by shop and by shift, by CLIN including both onsite and offsite management (excluding temporary personnel assisting with the transition phase) to meet the requirements of this solicitation. Identify all entities with a role and responsibility identified in ES-1 (Offeror Summary) and the effort that they will perform in Attachment P-3 (Table T-2 Manning). NOTE--All manning data shall be proposed in terms of Full Time Equivalent (FTE) personnel. This should not be construed as a personnel headcount.

Within Attachment P-3 (Table T-2 Manning) the Offeror shall provide a rationale for how the manpower requirements were determined. Describe the method by which the FTEs for each labor category were calculated or determined and identify all the data sources and industry standards used to derive the FTEs. If proposing FTEs in accordance with the Government estimate, so state. Describe any adjustments made from the Government estimate, other data sources and industry standards. Describe the rationale for why those adjustments are reasonable. Also specifically identify any process efficiencies that are being relied upon and justify the reasonableness of resulting FTE reductions. Substantiation shall include historical data, or detailed comparison analysis with similar aircraft maintenance services. If the substantiation also includes “new or improved” methods or standards as the basis for adjustments from the Government estimate, a detailed discussion shall be provided describing why those "new or improved" methods or standards should be deemed reliable as a basis for accurately projecting manning requirements. In addition, the substantiation must discuss the impact of any “learning” and “efficiencies” claimed and justify associated assumptions or conclusions.

The offeror’s total proposed manning in Annex A (Manning) must be consistent with the offeror’s total manning and labor category breakout proposed in the price attachments P-9 (Prime Contractor Cost Summary) and P-10 (Non-Prime Entity Cost Summary) . Any differences in these attachments may result in the offeror’s Technical Proposal being assigned up to a High Technical Risk, which may potentially make the offeror’s proposal unacceptable and unawardable.

Example from Table T-2 Manning

SHOP / Labor Category

b. Demonstrate that the Manning Approach provided in Annex A can be implemented as indicated to support the aircraft identified in Attachment L-3 (NTWL Anticipated Aircraft Load). The Offeror shall:

(1) Provide definition of work year capabilities of the work force (equivalent man hours/year analysis).

(2) Provide step-by-step details of how the productive man-year was calculated.

c. Describe how a temporary increase in the frequency and/or duration of maintenance operations will be supported. The Offeror shall describe the approach to the following scenarios:

(1) Execute two simultaneous MH-60R shipboard detachments concurrent with MH-60R Phase maintenance occurring at homeport.

(2) In preparation for numerous detachments involving several aircraft, describe the plan to prevent phase maintenance requirements from causing cancellations of detachments.

d. Manning Distribution – The Offeror shall:

(1) Describe integration, duties, responsibilities and authority within the onsite and offsite maintenance organization;

(2) Provide certification and skill level distribution for the onsite and offsite maintenance organization. Describe how qualifications/certifications will be kept current and maintained;

(3) Describe how Key and other personnel receive continual and recurring training with no additional direct charges to the Government; and

(4) Describe how lesser skilled and non-licensed personnel will be integrated into the maintenance process, and how their efforts will be overseen and supervised.

e. Overall Process Description – The Offeror shall provide a top-level block diagram or flow chart of the overall process showing man-hours and man loading for each work center. Depict the step by step process in the detail necessary to show the total effort that is being proposed.

2.3 Key Personnel

The Offeror shall provide a resume for the key personnel identified below, including experience, skills, education, training, qualifications, and certifications.

(1) On-Site Manager;

(2) On-Site Safety/Occupational Health Manager;

(3) On-Site Quality Assurance/Hazardous Materials Manager; and

(4) Squadron Group Manager.

2.4 Management Control Systems

The Offeror shall:

a. Describe the management information system or plan that will be used to plan and control costs, measure performance, track all maintenance activity, high-time items, tool control, quality assurance, material requisitioning, 3M data, recurring inspections and documentation for releasing aircraft safe-for-flight (aircraft that are not covered by OOMA) and generate timely, reliable and accurate management information for this program. State any differences between the Offeror’s proposed system(s) and those in use by the Government (OOMA) and provide a Plan of Action and Milestones (POA&M) for completion of any modifications to ensure the compatibility of both systems. Describe how the system will enable the Offeror to reliably plan and control costs, including Aviation Depot Level Repairable (AVDLR) costs, schedule, and technical performance, report accurate status of progress, and forecast potential results of alternative program actions. Provide evidence that the system is, or will be, used internally to manage contract performance.

b. Describe the corporate time keeping system and ability of the system to appropriately and accurately apply costs to CLINs.

2.5 Transition / Phase In Plans

a. Transition Plan - The transition period begins 90 days prior to the beginning of the period of performance. The Offeror shall describe the approach to initiating this program and provide a 90 day plan of action with milestones required to begin performing the requirements in this solicitation to start full performance on the first day of the period of performance. Include the following information:

(1) Start-Up/Learning. Identify the major challenges with regard to start-up and "learning". Describe the Offeror’s approach to minimizing start-up time as well as the effects of learning on accomplishing the work effort.

(2) Development of Procedures and Plans - Provide a plan of action and milestones for the development of the procedures and documents needed to start full performance on the first day of contract performance.

(3) Describe the approach used to fill all positions required for each labor category in the Manning Approach presented in Annex A (Manning). Identify the labor pools from which recruiting is expected and demonstrate the ability to hire. Provide an assessment by labor category and responsibility level of the prognosis for hiring the number of people with the required qualifications without impacting start/up schedule.

(4) Submit a manning schedule that indicates manning by site, work center and function during transition. Indicate a "ramp-up" to achieve full manning levels and performance. Analysis shall account for workload requirements/fluctuations, operational commitments/tempo, work in progress, and other area impacts.

b. Phase In Plan - The phase in period begins on the first day of the period of performance and extends for 60 days. The Offeror shall describe the approach to initiating this program and provide a detailed plan illustrating how Flight and Operational safety is maintained during the phase in period while supporting full performance from the first day of the period of performance. The phase in plan shall address the following:

(1) Program to train key maintenance and management personnel during phase in, including method for incorporation of lessons learned during previous site phase in(s).

(2) Training plan for personnel whose job requires formal certification/licensing prior to assumption of tasks, by site.

2.6 Risk Identification Plan

The Offer shall identify the risks inherent in the Management Approach. Describe a contingency plan for identified risk areas.

2.7 Small Business Management

a. Small Business (SB) Utilization Strategy All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB Concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. SB 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. This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan, if such a Plan is required. In describing its SB Utilization Strategy for this solicitation, the Offeror shall, as applicable:

(1) Describe its approach to identifying SB Concerns;

(2) 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. For each SB Concern specifically 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.

(3) Identify what processes have been implemented to correct past inabilities to meet proposed goals and any validated improvements;

(4) Provide goals, expressed as dollars and percentages of total contract value and percentages of total subcontract value for SB Concerns and each subcategory of SB, using the format depicted below and provided electronically in Attachment P-4 (Table T-3 Small Business Goals). The Offeror shall provide Table T-3 (Small Business Goals) as part of Annex B entitled “Small Business Subcontracting Plan and Table T-3 (Small Business Goals) ”. This table does not replace the Subcontracting Plan requirements in FAR 19.7. Use tab 1 for the prime and tab 2 etc. for each first tier subcontractor as goals for each subcontractor must be listed separately. The Offeror’s response to this section shall simply be a reference to Annex B;

Table T-3 Small Business Goals

Offeror Name

Large Business

Small Business

Total

100%

VOSB

SDVOSB

HUBZone

SDB

WOSB

(5) Describe its specific efforts and new, contract-specific initiatives to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach events and industry conferences, establishing Mentor-Protégé relationships and market research using websites such as the NAVAIR Office of Small Business Programs website (http://www.navair.navy.mil/osbp) and the Small Business Administration’s Dynamic Small Business Search tool (http://dsbs.sba.gov/dsbs/search/dsp_dsbs.cfm) to locate small business concerns; and

(6) Demonstrate (Large Businesses only) that its SB Utilization Strategy is consistent with its SB Subcontracting Plan. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, or if the Offeror submits a Commercial Subcontracting Plan for this proposal, then the Offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive or Commercial Subcontracting Plan goals.

Note: Offerors are advised that while the SB plan must be submitted to be eligible for award the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the evaluation. Therefore, resolution including changes to this plan may be made after source selection as part of the contract award process.

3.0 VOLUME 3 - PAST PERFORMANCE

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

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

For this volume, the Offeror shall identify all contracts, or those portions of a contract, whose performance is within three years of the proposal due date and contains efforts similar to those efforts (e.g., service, O-Level aircraft maintenance, type effort, aircraft, contract tasks, contract type, contract dollar value), required by this solicitation for the principal entities identified in Table ES-1 (Offeror Summary). Offerors shall also identify contracts within the past three years that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary) provided in Attachment P-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance. As much as possible, the contracts and their descriptions provided for this volume should correspond to the contracts and descriptions of the Offeror’s corporate experience provided for Volume 4 Corporate Experience.

In Annex C (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance and Corporate Experience), Offerors shall provide electronic copies of the complete final versions of the Statement of Work/Performance Work Statement (SOW/PWS) or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). For contract references for delivery/task orders, additionally provide the work description for the specific delivery/task order. For contract references where the offeror performed as a subcontractor, the offeror shall also provide a complete electronic copy of the final version of the statement of work or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW that the offeror performed as a subcontractor.

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 method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment P-5 (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 to the PCO/Contract Specialist, identified in 4.1 (Proposal Submission). 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 (or may not) 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.

0. Authorization Letter(s)

Within this section, the Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall state that adverse past performance issues shall be coordinated directly with the principal entity 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 principal entity (including JV team members), 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 principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

Offerors shall only identify contracts whose past performance can be leveraged in the future performance of this solicitation.