N00019-15-R-0079_Amendment_01_(113016).pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this modification is to:

1) update Contract Specialist (CS) and Procuring Contracting Officer (PCO) Point of Contacts throughout the RFP: for CS, from Patrick Abell to T'ann Perrault; for PCO, from Noelle Reimers to Erin Young, see pages 2 and 8 of this SF30,

2) update physical location for proposal submission: from NAVAL AIR SYSTEMS COMMAND (HQ) to NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION (NAWCTSD), see pages 2 and 8 of this SF30,

3) update the number of copies of proposals to be submitted: from 7 to 0, see page 2 of this SF30,

4) revise Section L-1, Part A, Paragraph 4.1 for Past Performance tables early submission, see pages 8 and 14 of this SF30,

5) revise attachment L-4 Past Performance Questionnaire to capture new POCs, see page 8 of this SF30, and

6) update contact info under clauses 52.233-2 and 5252.233-9500, see pages 27 of this SF30.

All changes and updates listed above are highlighted in the follow ing pages of this SF30.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 27

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 30-Nov-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00019-15-R-0079

X 9B. DATED (SEE ITEM 11)

16-Nov-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

30-Nov-2016

CODE

NAWCTSD

12211 SCIENCE DRIVE

ORLANDO FL 32826

N61340 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00019-15-R-0079

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The depository location has changed from Building 2272, Suite 453 to Orlando, De Florez Bldg.

The organization for offers to be sent to has changed from

NAVAL AIR SYSTEMS COMMAND

AIR-2.2.3.3 SUITE 453 BLDG 2272

47123 BUSE ROAD UNIT IPT

PATUXENT RIVER MD 20670

to

NAWCTSD

12211 SCIENCE DRIVE

ORLANDO FL 32826

The number of offeror copies required has decreased by 7 from 7 to 0.

The following have been modified:

SECTION A

SF 30 BLOCKS 6&7 CONTINUATION

ISSUE BY and ADMINISTERED BY (Agency Full Address):

N61340

NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION ( NAWCTSD)

ATTN: ERIN YOUNG, PROCURING CONTRACTING OFFICER, CODE AIR-2.5.3.7

T’ANN PERRAULT, CONTRACT SPECIALIST, CODE AIR-2.5.3.7

12211 SCIENCE DRIVE, ORLANDO, FL 32826-3224

SF33 BLOCK 8 – ADDRESS OFFER TO:

N61340

NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION ( NAWCTSD)

ATTN: ERIN YOUNG, PROCURING CONTRACTING OFFICER, CODE AIR-2.5.3.7

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3224

SF 33 BLOCK 9:

See Section L for a complete list of copies required for solicitation submittal for each proposal Volume and complete proposal submittal address.

SF 33 BLOCKS 10

For Information, Call:

Block 10A: Name: T’ann Perrault, Block 10B : Telephone: (407) 380-4723 Block 10C: Email Address: trang.perrault@navy.mil

SF 33 BLOCK 12:

The Offer validity date shall be 01 December 2017. The SF-33 Block 12 fill-in shall be completed in accordance with this date.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L-1 CONTENT OF PROPOSALS

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. No price or pricing information shall be included in any portion of the proposal, including cover letters, except for the Price (Volume 4), the Contract Administration (Volume 5), and the SB Subcontracting Plan (as part of Annex D).

Alternate proposals are not acceptable.

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 Government to evaluate the various work efforts, support, and management approaches, as well as the price proposal without opening discussions. 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 summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

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 work totaling at least 10% of the proposed total price for the contract. 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, JV, JV Team Member, subcontractor, corporate parent, division, subsidiary and/or affiliate.

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 shall be presented in no smaller than a 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. Text utilized in charts, figures, and graphics shall also be no smaller than a 10 point font and may use a font type selected by the Offeror. Each volume, book, 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.

2.1 Electronic Submission of Proposal

This section provides information to the Offeror on the electronic format and application software 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 shall submit its proposal electronically on CD-ROM(s) compatible with the operating system and applications defined in Section 2.1.2 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, Volume 4 Price, Small Business Subcontracting Plan (Annex D), 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 shall submit four sets of CD-ROMs that contain its proposal. One set of CD-ROM disks shall be marked "Master," the other sets shall be marked "Back-Up." All sets of CD-ROM disks shall be clearly marked with the set number, the Offeror’s name and address, the point of contact's name and phone number, the solicitation number, and proposal information contained therein. CD-ROMs and the documents contained therein shall not be password protected. The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the disk 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 separate electronic versions containing identical proposal information in each set: 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 Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among the portions of the proposal that do not include price information.

However, there shall be no links from any other volume or annex into Volume 4 Price, or any portion of the proposal that contains 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 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:

Type of Application/Files Valid Extensions Portable Document Files .pdf Microsoft Word documents .docx Microsoft Excel documents .xlsx Microsoft Power Point .pptx Microsoft Project .mpp

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 G-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, book, or annex) as one separate file (i.e., do not provide each section/paragraph as separate files).

Table G-1 Offeror Electronic File Naming Convention

Volume Number

Title File naming convention

1 Executive Summary Vol 1 ES#.pdf and Vol 1 ES#.docx

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

Vol 1 ES Tables.xlsx and Vol 1 ES Tables.pdf

2 Technical Vol 2 Tech#.pdf and Vol 2 Tech#.docx

Table T-1Cross Reference Matrix CRM.xlsx and CRM.pdf Table T-2 Experience Vol 2 Exp#.xlsx and Vol 2

Exp#.pdf 3 Past Performance Vol 3 PP#.pdf and Vol 3

PP#.docx Table PP-1 Past Performance Contract Data Vol 3 PP-1 PP Con

Data.pdf and Vol 3 PP-1 PP Con Data.xlsx

Release of Adverse Past Performance Authorization Letters;

and/or Past Performance Point of Contact Information for Principal Subcontractors and Joint Venture Team Members

Rel Ad PP Ltr#.pdf and Rel Ad PP Ltr #.docx; and/or PP POC Info#.pdf and PP POC Info#.docx

4 Price Vol 4 Price#.pdf and Vol 4 Price#.docx

Section B Price Matrix Vol 4 Section B.xlsx and Vol 4 Section B.pdf

Prime Contractor Cost Summary Vol 4 Prime CCS.xlsx and Vol 4 Prime CCS.pdf

Non-Prime Entity Cost Summary Vol 4 Non-Prime CS.xlsx and Vol 4 Non-Prime CS.pdf

Draft CSDR Plan Vol 4 CSDR.xlsx and Vol 4 CSDR.pdf

5 Contract Administration (Excluding Model Contract which is to be provided under a separate file name.)

Vol 5 CA#.pdf and Vol 5 CA#.docx

Model Contract Vol 5 MC.pdf and Vol 5 MC.docx

Annexes Annex A Manning AnnA Manning #.xlsx and

AnnA Manning #.pdf Annex B Quality Control Program Plan AnnB QP #.pdf and AnnB

QP #.docx Annex C Property Management Plan AnnC PMP #.pdf and

AnnC PMP #.docx Annex D Small Business Subcontracting Plan

AnnD SmBusSP #.pdf and AnnD SmBusSP #.docx

Annex E Final Versions of Previous SOWs/PWSs for Past Performance AnnE SOWPP #.pdf and AnnE SOWPP#.docx

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror must present its proposal information in a manner that facilitates a one-for-one comparison between the information presented and Section L 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 paragraph 2.1, “Electronic Submission of Proposals,” each volume, book, and annex of the proposal shall be submitted as an original and additional paper copies as specified in Table G-2 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 G-2 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 “Part B Specific Instructions” and do not count towards the suggested page count.

Table G-2 Proposal Structure

Title

Suggested Pages

Hard Copies Required

Vol. 1 EXECUTIVE SUMMARY 10 1 Original

Vol. 2 TECHNICAL 50 1 Original Vol. 3 PAST PERFORMANCE 50 1 Original Vol. 4 PRICE As Needed 1 Original

Vol. 5 CONTRACT ADMINISTRATION As Needed 1 Original

Annex A Manning As Needed 1 Original

Annex B Quality Control Program Plan As Needed 1 Original Annex C Property Management Plan As Needed 1 Original Annex D Small Business Subcontracting Plan As Needed 1 Original Annex E Final Versions of Previous SOWs/PWSs for Past Performance As Needed 1 Original

Each binder must contain the following information using tabs and dividers:

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/book/annex number;

f. Copy number; and

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.

The following table G-3 lists the attachments provided to the Offeror with Section L, to assist with proposal development.

Table G-3 Section L List of Attachments

Attachment Number

Title

L-1 Table ES-1 Offeror Summary and Table ES-2 Relevant Contract Summary L-2 Manning L-3 Table T-2 Experience L-4 Past Performance Questionnaire (updated version) L-5 Table PP-1 Past Performance Contract Data L-6 Section B Price Matrix L-7 Prime Contractor Cost Summary L-8 Non-Prime Entity Cost Summary L-9 Draft CSDR Plan

4.0 PROPOSAL PACKAGING AND SUBMISSION

4.1 Unclassified Data

Clearly mark all packages with the solicitation number. The submission date for the proposal 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 Table PP-1, Table ES-1 and Table ES-2 be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9).

In the official proposal submitted on the date/time specified on Standard Form 33 (Block 9), indicate any changes made to the information delivered two weeks earlier. If no changes are made, state so at the beginning of Volume 1 Executive Summary and Volume 3 Past Performance.

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with T’ann Perrault, Contract Specialist (407) 380-4723 no later than 24 hours prior to the SF 33 Block 9 submission date/time. Proposals shall be submitted using the address provided below. (Offerors are cautioned to see FAR 52.215-1 regarding late proposals.) The Initial Proposal, the Final Proposal, and the early submission of Table PP- 1, Table ES-1 and Table ES-2 shall not be submitted by facsimile or electronically via email.

Naval Air Warfare Center Training Systems Division (NAWCTSD) Code: AIR 2.5.3.7 (Erin Young) Solicitation Number: N00019-15-R-0079 12211 Science Drive Orlando, FL 32826-3224

4.2 Classified Data

All proposals shall be UNCLASSIFIED.

4.3 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/book number and title, and copy number. Each carton shall be double wrapped. The outside wrapping of the carton should be plain and the inside wrapping shall be stamped or marked ― “For Official Use Only”; and “Source Selection Information – See FAR-2.101 and 3.104”. The master set of proposals shall be grouped separately and marked for NAWCTSD PCO, AIR-

2.5.3.7. 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; Representations, Certifications and Other Statements of Offerors or Respondents (Section K of this RFP) and other applicable fill-ins.

5.0 CHANGES TO SOLICITATION

All amendments and any additional information for this solicitation will be posted at https://www.fbo.gov/. Search the database for the solicitation number N00019-15-R-0079.

6.0 TECHNICAL LIBRARY

A Technical Library of information directly related to the requirements of solicitation N00019-15-R-0079 is available to all Offerors intending to propose as a Prime. The library is located at:

https://pma273.navair.navy.mil/

To gain access to the technical library, register on the website above. Requestors shall be required to provide e-mail addresses, phone number, and IP addresses.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost or 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

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 areas outlined below:

a. 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 within this section and 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 entity that is 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.

ES-1 Offeror Summary Table

b. 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 Experience for the Prime, Principal Subcontractors, and JV Team Members. The Offeror shall 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, Attachment L-5, (Table PP-1 Past Performance Contract Data) (i.e., the contract identified as P1 in the Relevant Contract Summary Table is the same P1 contract identified in Past Performance).

ES-2 Relevant Contract Summary Table

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 management approach;

Offeror:

Entity Name Place of

Performance CAGE Codes/

DUNs Roles &

Responsibilities with Work Description

% of Total Proposed Price

Total Proposed Price (must add up to 100%)

100%

d. Past Performance The Offeror shall provide a summary of the Prime’s, Principal Subcontractors’, and JV Team Members’ past performance, including systemic improvements, pertaining to the tasks required by this solicitation;

e. Terms and Conditions

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

2.0 VOLUME 2 - TECHNICAL

Note: This volume shall not contain any reference to cost or 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-2 Manning Attachment L-3 T-2 Experience

A Cross Reference Matrix (CRM) for the Technical Volume, Table T-1, is included to help the Offeror develop its technical 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.

Table T-1 Cross Reference Matrix

Section L – Proposal

Instructions Volume or Paragraph Numbers

Section L - Proposal Instructions Volume or

Paragraph Title Section M PWS CLIN

Volume 2 Technical II. A N/A N/A

2.1 Manning II. A N/A N/A

2.2 Quality Control Program

Plan

II. A 9.1.2.1, 9.1.2.2 0X02, 0X06

2.3 Management II. A N/A N/A

2.3.1 Maintenance Management II. A 9.2.2, 9.2.3 0X02, 0X06

2.3.2 Transition (Phase-in) II. A 9.1.4.3, 9.1.5.1, 9.1.5.3.1, 9.2.2.1.f,

2.3.3 Property Management II. A 6.1.1, 9.1.1.4.1, 9.1.5, 9.1.6.2.8, 9.1.6.2.10, 9.1.6.2.11, 9.1.7.1.1, 14.1, 14.5

0X02, 0X06

2.4 Experience II. A N/A N/A

2.5 SB Subcontracting Plan II. A 13.1 All

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 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 or risk reducing feature may be included in the resulting applicable contract within the proposed price.

2.1 Manning

All manning data shall be proposed in terms of Full Time Equivalent (FTE) personnel.

a. Provide a comprehensive workload/man-year analysis to support site manning levels for each site. Provide a top-level block diagram or flow chart of the overall process used to determine man-hours and man loading.

Describe the method by which the man-hours, man loading and work shifts were calculated or determined and identify any data or standards used. Identify any adjustments to the standards or any process efficiencies that were applied to the man-loading and provide substantiating data that justifies the adjustments or efficiencies being applied. Substantiation shall include historical data, or comparison analysis with similar aircraft maintenance services. General statements such as “estimates were derived from engineering judgment” or “estimates were derived from comparison with similar services” are not acceptable substantiation unless the details of the analysis are provided.

b. Provide step-by-step details of how the Offeror’s available man-year and productive man-year are calculated. If the Offeror’s available and productive man-year estimates differ from historical actuals, provide detailed rationale and justification for the differences and for any efficiencies applied to the calculation.

c. Identify the critical skills required to accomplish the effort and describe the personnel qualifications that will be required by these people. Demonstrate how the direct and indirect manpower expertise and experience effectively perform the work. Identify FAA licensed and other skilled positions requiring a type of special licensing or certification. Provide certification and skill level distribution logic. Describe qualification requirements that are used in hiring for each labor category. Qualification descriptions should include experience, education, training, and certification/re-certification requirements.

d. The Offeror shall fully describe how premium time requirements will be met, and how they will staff/plan for the non-routine requirements of the PWS. Offerors are advised that any proposed manning levels by labor category and site falling below the Government manning estimate without reasonable substantiation, as determined by the Government, will be assessed as higher technical risk and the Government will identify weaknesses.

e. Complete Attachment L-2 (Manning) and submit it as Annex A (Manning), showing the Offeror’s proposed manning for in accordance with the L-2 (Manning) instructions. 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 L-7 (Prime Contractor Cost Summary) and L-8 (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.

2.2 Quality Control Program Plan - Provide a Quality Control Program Plan as Annex B that complies with each element of AS9100C, CNAFINST 4790.2 Chapter 10.7, PWS Paragraph 9.1.2.2, Section J, Attachment (2) Applicable Documents, and includes the processes and procedures needed to demonstrate compliance with the outcomes in Federal Acquisition Regulation 52.245-1 Paragraph (f)(1)(i) through (f)(1)(x).

2.3. Management

2.3.1 Maintenance Management-- Demonstrate how the on-site maintenance services required by the Performance Work Statement shall be accomplished given the Offeror’s approach.

a. Illustrate the planned maintenance process by means of a flow or block diagram.

b. Provide an overview of proposed maintenance processes and their inter-relationships, and the proposed approach to control these processes.

c. Describe how and when all work instructions will be developed and implemented.

d. Describe the work process and documentation for reviewing, approving and assigning workload priorities based on the ICRLs.

2.3.2 Transition (Phase in) - Submit a detailed plan that defines the critical tasks and timelines needed to ensure a smooth and phased transition into full performance. The plan shall provide the schedule of critical tasks, task owners, interrelationships, and resources, at the lowest level necessary to ensure a smooth and phased transition into full performance IAW the PWS.

2.3.3 Property Management - Provide a Property Management Plan as Annex C that complies with PWS Paragraphs 9.1.5 through 9.1.5.3.3 and Section J Attachment (2) Applicable Documents; provides detailed written procedures for each outcome listed in FAR 52.245-1; and describes how periodic internal reviews, surveillances, self-assessments or audits shall be performed on the Contractor's departments.

2.4 Experience – The Offeror shall demonstrate the degree to which its previous experience is similar to the requirements of this solicitation, particularly with respect to processing approximately 25,000 intermediate level maintenance actions annually and 45,000 intermediate maintenance man hours annually at a single site supporting multiple type/model/series aircraft platforms at a single site, utilizing Naval Aviation Maintenance Program CNAF 4790.2B processes and procedures. The Offeror’s demonstration of experience shall only use the contracts submitted on Table ES-2 (Relevant Contract Summary). No information on individual employee experience of the Prime Contractor, Principal Subcontractors or JV Team Members should be submitted as part of this proposal; this information will not be considered in this Experience evaluation. As a minimum, complete Section L Attachment L- 3, Table T-2, Experience, for each contract. 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.

Experience by the Prime, Principal Subcontractors and JV Team Members (if applicable) will be evaluated on the amount of experience gained; and extent to which the associated efforts are similar in scope, magnitude, and complexity to this solicitation as well as relate to the proposed roles and responsibilities. Only risk will be assessed.

Experience that took place greater than 3 years from the proposal due date will not be considered.

Experience by individual employees will also not be considered. Lack of a record of experience similar to the requirements of this solicitation particularly with respect to processing approximately 25,000 intermediate level maintenance actions annually and 45,000 intermediate maintenance man hours annually at a single site supporting multiple type/model/series aircraft platforms at a single site, utilizing Naval Aviation Maintenance Program CNAF 4790.2B processes and procedures, may be considered a significant weakness.

2.5 Small Business Subcontracting Plan

Large Business Offerors shall provide either an approved comprehensive Small Business (SB) Subcontracting Plan or individual Small Business Subcontracting Plan.

If an approved Comprehensive SB Subcontracting Plan is submitted, the plan shall be considered to have met the PWS requirement in paragraph 13.1.

If an individual SB Subcontracting plan is submitted, the plan shall conform to the requirements of FAR 19.7 and DFARS 219.7 as part of Annex D and demonstrate how the Offeror will meet the minimum SB requirements identified in PWS paragraph 13.1. The Offeror’s individual SB Subcontracting Plan shall 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. The Offeror shall describe its specific efforts to ensure the resulting contract meets or exceeds the minimum PWS Paragraph 13.1 SB requirements. These efforts shall include, but are not limited to: sponsoring program specific outreach programs and industry conferences, establishing Mentor-Protégé relationships and using the NAVAIR Office of Small Business Programs website (http://www.navair.navy.mil/osbp ) to locate small business concerns.

The Individual SB Subcontracting Plan of the successful Offeror will be reviewed and approved by the PCO prior to contract award. See FAR 19.702(a)(1) statutory requirements regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved individual or Comprehensive SB Subcontracting Plan will be incorporated as an Attachment into the resultant contract.

Offerors are advised that failure to provide either (1) an approved Comprehensive Small Business Plan or (2) an Individual SB Subcontracting Plan that demonstrates compliance with SB requirements in PWS paragraph 13.1 shall be considered non-responsive to the solicitation and will be assessed as a technical deficiency.

3.0 VOLUME 3 - 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:

Attachment L-4 Past Performance Questionnaire (PPQ) Attachment L-5 Past Performance Contract Data (Table PP-1)

For this volume, the Offeror shall identify in Table ES-2 Relevant Contract Summary, relevant contracts, or those portions of a relevant contract, for the Prime, JV Team Members and Principal Subcontractors listed in Table ES-1 (Offeror Summary) with performance within three years of the initial proposal due date and containing efforts similar to those efforts (e.g., end product or service, type effort, contract tasks, contract type, contract dollar value, etc.) required by this solicitation.

Offerors shall also identify contracts with performance within three years of the initial proposal due date that had any show-cause notices, cure notices or terminations for default.

Contractor Performance Assessment Reports (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 a CPAR, or where the CPAR is older than 12 months, the Offeror shall complete item 1 of the L-4 Past Performance Questionnaire and forward a copy to that contract’s Procuring Contracting Officer (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 to T’ann Perrault, via email at trang.perrault@navy.mil and Erin Young, at erin.b.young@navy.mil. 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.

3.1 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 participating Principal Subcontractor and/or JV Team Member, 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 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 Principal 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 Principal 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 Principal Subcontractor or JV Team Member, and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract for the Prime, Principal Subcontractors and JV Team Members identified for past performance in Table ES-2 (Relevant Contract Summary) provided in L-1 (Executive Summary Tables), the Offeror shall complete L-5 Table PP-1 (Past Performance Contract Data), following the instructions provided within the attachment and submit it within this section and as a separate electronic file. Please note that L-5 Table PP-1 is a summary of the Prime’s, Principal Subcontractors’ and JV Team Members’ relevant contract data.

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.

Table PP-1 Past Performance Contract Data

1 Contractor Name

2 Contract Reference

3 Title of Contract

4 Contract Number

5 Contract Type

Relevant Delivery/Task Order Numbers (if applicable)

7 Subcontract Number/PO Number

8 Procuring agency

9 Description of product or service

10 Period of performance

11 Cage Code

12 DUNS

13 Dollar value of contract

14 Acquisition Phase(s) of Contract

Brief Work Description and/or Program Responsibility for this past contract.

16 Date of last completed CPARs

17 Date past performance questionnaires were sent.

19 Gov't PCO or Commercial Purchasing Agent Name:

Phone:

Email:

20 Gov't ACO Name:

Phone:

Email:

21 Gov't PM or Commercial PM Name:

Phone:

Email:

22 Other:

Name:

Title:

Phone:

Email:

Points of Contact who can validate performance on the contract referenced in Block 4 or specific delivery order or task order number referenced in Block 7.

3.3 Evaluation

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

Past performance for each contract identified in L-5 Table PP-1 (Past Performance Contract Data) will be evaluated in two pieces, the first being the relevance of the past performance information and the second, how well the Offeror performed.

a. Relevancy:

(1) In Annex E, Offerors should provide an electronic copy of the Statement of Work/Performance Work Statement (SOW/PWS) from each of the referenced contracts identified in Table ES-2 (Relevant Contract Summary). The Offeror is advised that the Government will assess each contract and assign a relevancy rating of Very Relevant (VR), Relevant, Somewhat Relevant (SR) or Not Relevant.

The provided contract(s) should be relative to the Prime’s, Principal Subcontractor’s, or JV Team Member’s proposed role/responsibility identified in Table ES-1 (Offeror Summary) versus relative to the whole solicitation. For example, a Principal Subcontractor who is being proposed to perform only software development has a past contract whose total work is software development. Even though the software effort is only 10% of the hypothetical solicitation’s effort, the previous contract relates to 100% of the Principal Subcontractor proposed effort for the hypothetical solicitation and therefore the reference contract may be 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 complexities required by this solicitation; or

iv. Contracts, or those portions of contracts, whose performance is older than three (3) years from the initial proposal due date. (If only a portion of a contract is older than three (3) years, then only that portion is not relevant for reasons of recency.)

(3) Past Performance contract references of any entity with multiple CAGE codes and DUNS will be considered if the CAGE code/DUNS was 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. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity.

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 and explain how the changes impact the relevance of any contract references provided. All current CAGE Codes/DUNS must appear in Table ES-1 (Offeror Summary Table) indicating a commitment of work for those entities.

b. Past Performance Information: Provide a brief description of past performance in delivering quality products and services in each of the areas identified below. 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., performing analysis, design, testing, etc.);

(2) Schedule Performance: meeting schedule requirements (i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc.); and

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

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems listed in 3.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 reference contract and, if applicable, how these techniques, elements, and tools may be used for the contract to be awarded as the result of this solicitation. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and demonstrate that the past problem will not occur on the contract to be awarded as the result of this solicitation. 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.

4.0 VOLUME 4 –PRICE

4.1 Volume Content

a. This Volume shall contain the information requested below and shall include a copy of Price Attachment L-6

(Section B Price Matrix) of the solicitation with the CLINs and SLINs Unit Prices and for evaluation purposes, the Extended Prices…