N00421-17-R-0071-0003_.pdf

SEE SCHEDULE

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 amendment is to:

1. Update Section L, Part A, Paragraph 4

2. Update Section L, Part B, Paragraph 2.2 (A)(3)

3. Update Section L, Part B, Paragraph 2.2 (A)(4)

4. Update Attachments P3 and P4

All other terms and conditions of this amendment remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

1 24

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

16C. DATE SIGNED

BY 11-Oct-2018

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 N0042117R0071

X 9B. DATED (SEE ITEM 11)

27-Sep-2018

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 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

11-Oct-2018

CODE

NAVAL AIR WARFARE CENTER AD

CODE 2.5.1.11

21983 BUNDY ROAD

BLDG 441

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0042117R0071

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Exhibit A CDRLs

Attachment 1 SOW

Attachment 1a Labor Categories

Attachment 1b Sample Travel Request

Attachment 1c GOP Guidance

Attachment 2 DD254

Attachment 3 RESERVED

Attachment 4 DPAP GFP Form

Attachment 5 WD - Patuxent River, MD

Attachment 6 WD - China Lake, CA

Attachment 7 WD - Point Mugu, CA

Attachment P1 CPAQ

Attachment P2 Past Performance

Contract Data - 04Oct18

Attachment P3 Cost Summary

Spreadsheet

Attachment P4 Subcontractor Cost

Summary

Attachment P5 Labor Hour Matrix to:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Exhibit A CDRLs

Attachment 1 SOW

Attachment 1a Labor Categories

Attachment 1b Sample Travel Request

Attachment 1c GOP Guidance

Attachment 2 DD254

Attachment 3 RESERVED

Attachment 4 DPAP GFP Form

Attachment 5 WD - Patuxent River, MD

Attachment 6 WD - China Lake, CA

Attachment 7 WD - Point Mugu, CA

Attachment P1 CPAQ

Attachment P2 Past Performance

Contract Data - 04Oct18

Attachment P3 Cost Summary

Spreadsheet - 11Oct18

Attachment P4 Subcontractor Cost

Breakout Spreadsheet -

11Oct18

Attachment P5 Labor Hour Matrix

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L – [ 1 ] CONTENT OF PROPOSALS (SERVICES))

PART A GENERAL INSTRUCTIONS

1 GENERAL

The Offeror (Prime or Joint Venture (JV)) must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror is advised that the Government may incorporate any portions of the Offeror’s proposal into the resulting contract.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. Statements that the prospective Offeror understands, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in assessing weaknesses and/or deficiencies.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or element clearly may be considered a deficiency.

Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Government advises the Offeror that taking exception or deviating from any term or condition of the solicitation may result in the assessment of a deficiency to the proposal.

“JV Team member” is defined as one of the entities that make up a joint venture (JV) formed for the purpose of responding to this solicitation. If proposing as a JV, Offerors shall submit the legal document and associated agreements that established the Joint Venture and identifies the roles of each member of the JV. Note: All joint ventures that are proposed shall provide their Joint Venture legal document with agreement(s) in Annex # 1.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing NAWC-

AD Contracts at sherry.stewart@navy.mil and candice.byrd@navy.mil. It is requested that all questions be received within 7 calendar days of the date this solicitation is issued.

2 PROPOSAL FORMAT

Written proposals should be formatted using the following:

Compatible with Microsoft Office 2016 and/or latest Adobe Acrobat Reader

Times New Roman no smaller than 10-point Normal font (no reduction permitted)

Single-spaced

1-inch margins all around

Formatted for standard 8.5 x 11-inch paper (except where indicated)

All pages numbered with section and page numbers

All pages have header with Company Name and Solicitation Number mailto:sherry.stewart@navy.mil

Foldout pages are allowed, but should be held to a minimum

Graphs and tables shall be presented in no smaller than an 8-point font and should contain a grid, which allows values to be read directly from the graph.

Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented.

The Offeror will ensure that the Cost Volume is provided on a separate CD/DVD-ROM. Each CD/DVD-ROM is to be labeled for content and the Offeror’s name and “For Official Use Only. Source Selection Sensitive Information –

See FAR 2.101 and 3.104.” If a discrepancy exists between the original paper copy of the proposal and the disk copy, the electronic file will take precedence.

3 PROPOSAL CONTENT AND VOLUMES

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured to the greatest extent possible such that its Volume/paragraph number matches the Proposal Instructions Volume/paragraph number provided in section “Part B Specific Instructions” to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must answer all parts of the section or provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, section, and element, etc., in the Offeror’s proposal.

Each volume of the proposal shall be submitted as one original and additional copies (both hardcopy and or electronic copy) as specified in the table below. The table below supersedes the copies requested in Block 9 of the

Standard Form (SF) 33. All volumes of the proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Suggested page counts for each volume, if any, are also specified in the table below. Utilizing the maximum number of suggested pages is not required and Offerors are encouraged to follow the instructions from earlier in this section related to 1) clarity and brevity being emphasized in the proposal and 2) unnecessary proposal data beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Annex submissions are limited to the information required in Section L, Part B, Specific Instructions. Information that may be required as an annex to the proposal includes statements of work for submitted contracts under the Past

Performance volume, manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Page limitations for

Annexes, if any, are specified below. The authorized Annexes, if any, are summarized in the table below.

Volume

Number

Volume Title Suggested

Pages

Copies Required

1 PAST PERFORMANCE

- Attachment P2 shall be submitted as a separate file, only electronically.

No Page

Limit

1 Original and 1 copy in Hard

Copy

2-CD/DVD-ROM electronic

Copies

Annex # 1

(Vol 1)

JV Agreement Information No Page

Limit

Electronic: Included in a separate folder on the Volume

1 CD/DVD

Annex # 2

(Vol 1)

Past Performance: SOW/PWS, Contract

(Cover Page, Sections A through J)and other contract information files for each submitted contract and Release of

Adverse Past Performance Authorization

Letters

No Page

Limit

Electronic: Included in a separate folder on the Volume

1 CD/DVD-ROM Copy

2 TECHNICAL

50 pages

Total

1 Original and 1 copy in Hard

Copy

2-CD/DVD-ROM electronic

Copies

Volume

Number

Volume Title Suggested

Pages

Copies Required

Annex #3

(Vol 2)

Technical: GGFR signed Tool Control

GOP (if applicable) (Part B, section 2.3)

No Page

Limit

1 Original Hard Copy

Electronic: Included in a separate folder on the Volume

2 CD/DVD-ROM

3 COST No Page

Limit

1 Original and 1 copy in Hard

Copy

1-CD/DVD-ROM electronic

Copy

Each volume of the Offeror’s proposal shall contain the following information:

-Cover and title page

-Title of proposal and proposal number as applicable

-Offeror’s name, address, and POC

-Solicitation number

-Proposal volume number

-Copy number

-Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

-Use tabs and dividers for hard copies

4 PROPOSAL SUBMISSION:

The Offeror shall clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the solicitation. It is requested that the following Past Performance information be submitted by 22 October 2018:

a. Table 1 Relevant Contract Summary for Past Performance

b. Attachment P2 Past Performance Contract Data for each Relevant Contract and

c. The part of Annex #2 that provides the SOW/PWS and the other contract information files needed to demonstrate relevancy for each submitted Relevant Contract

Early Past performance shall be provided electronically with two (2) CD/DVD-ROM electronic copies.

Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.

Naval Air Systems Command

Code: AIR-2.5.1.11.8 (Sherry Stewart)

21983 Bundy Road, Building 441, Patuxent River, MD 20670

Solicitation Number: N00421-17-R-0071

Hand carried proposals may be delivered to the address above, attention (PCO) and/or (Specialist).

5 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 container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 3 Cost.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information –

See FAR 2.101 and 3.104.”

6 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

7 SOLICITATION CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to www.FedBizOpps.gov.

PART B SPECIFIC INSTRUCTIONS

1 VOLUME 1: PAST PERFORMANCE

1.1 SPECIFIC INSTRUCTIONS FOR PAST PERFORMANCE

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

The following is a list of Attachments. Offerors shall send the Attachment P1 to the appropriate customer as described below and also submit the completed Attachment P2 in Volume 1 of the proposal. Detailed proposal instructions are shown below.

Attachment P1 – Contractor Performance Assessment Questionnaire

Attachment P2 – Past Performance Contract Data

For this volume, the Offeror shall identify relevant contracts, or those portions of a relevant contract, whose performance is within five years of the solicitation release date. The above mentioned attachments shall be included in Volume 1 as separate files. Contracts performed by any entity other than the offeror, such as teaming partners or subcontractors, will not be evaluated as prime contractor experience or prime contractor past performance, unless those other contractors are part of a joint venture offeror as demonstrated by a signed joint venture agreement. As a result, Offerors shall not submit present/past performance contract references for any proposed subcontractors. Offerors shall also identify relevant contracts within the past five years that had any show-cause notices, cure notices, or termination for default.

Contract Performance Assessment Reporting System (CPARS) and Contractor Performance Assessment

Questionnaires (Attachment P1) 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 CPAR, the Offeror shall forward a copy of the Contract Performance

Assessment Questionnaire (Attachment P1) to that contract’s COR, PM or PCO; or commercial contractor equivalents. Please forward all applicable 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 Sherry Stewart, Contracts Specialist, at sherry.stewart@navy.mil. The Offeror shall ensure that all points of contact identified above are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to these questionnaires, 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 other sources.

Past Performance Information Point of Contact http://www.fedbizopps.gov/

If any Past Performance information requires further coordination please contact Sherry Stewart, Contracts

Specialist, at sherry.stewart@navy.mil.

1.2 Relevant Contract Data

The Offeror shall submit only relevant contracts as defined in Section M of this solicitation. For each contract identified for past performance in Table 1 below, the Offeror shall complete a sheet/tab within Attachment P2 (Past

Performance Contract Data) and submit it electronically (Microsoft Excel) in Volume 1. The purpose of Table 1 is table is to provide a quick index of the contracts being submitted; clearly showing what was submitted as part of the early submittal and, if applicable, how it changed (e.g. additions, deletions, and data corrections) in the final proposal submission.

All detailed information and comparative analysis of the past performance references to the AVMI requirement shall be provided in Volume 1, Section 1.3 (Evaluation), of the Offeror’s proposal. The contract references submitted in

Table 1 shall be used in completing the Past Performance Volume and all contract references shall be numbered the same throughout the Offeror’s Past Performance Proposal (i.e. the first contract reference shall be designated “PP1”, the second contract reference shall be designated “PP2”, etc.).

Table 1 Relevant Contract Summary for Past Performance

Offeror:

Entity Name and CAGE

Code

Contract

Reference

Contract

Number

Contract

Type Contract Title

Description of

Changes/Additions from

Early Information

Prime Company

PP1

PP2

PP3

PP4

JV team member A

(where applicable)

T1

T2

T3

T4

JV team member N

(where applicable)

T5

1.3 Evaluation

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

For each contract identified in Table 1, the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement as described below, organized by contract. Offerors shall submit an Excel file - Attachment P2 (multiple sheets/tabs within the same Excel file is recommended) for each present/past performance contract reference and label them appropriately to match the contract reference designation in Table 1 (PP1, PP2 etc.).

mailto:sherry.stewart@navy.mil

Individual Delivery Orders/Task Orders (DOs/TOs) are considered separate contract references and will be evaluated for Relevancy (Scope, Magnitude, and Complexity) at the order level, not at the overall contract level. If multiple DO/TOs are submitted from the same base contract, and each order is determined to be relevant, and they contain similar scope, complexity, and magnitude of effort, those DOs/TOs will be treated as a single past performance contract reference. However, individual DOs/TOs will not be combined in order to meet the relevancy definition in terms of scope, magnitude and complexity, or recency.

For any contracts referenced where the Prime and/or JV team members are aware of problems, the Offeror shall describe the issues in section 1.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 1.3.c (Demonstrated Systemic Improvement) and explain how the improvement effort reduces the risk of the problem reoccurring.

a. Relevancy:

The Offeror shall demonstrate the relevancy of each submitted contract using the past contract’s SOW/PWS, the contract itself, or any other authoritative documentation.

If proposing as a JV, the offeror shall provide their Joint Venture legal document with agreement(s) in Annex # 1.

Ensure that the Cage Code(s) for the JV member(s), as well as the JV itself, are provided.

In Annex #2, Offerors shall provide one electronic copy of the Statement of Work/Performance Work Statement

(SOW/PWS), contract sections and other information as necessary for each of the contracts identified within Table 1 and Attachment P2. If the contract being submitted is a task order or delivery order, ensure that the SOW/PWS and contract sections for the order are provided in addition to the base contract. If the Offeror performed as a subcontractor on the past performance contract, ensure that the subcontract and associated SOW/PWS that was flowed down is provided to show the work performed as the subcontractor. If the Offeror performed as a member of a JV on the past performance contract, ensure that the JV agreement and associated contract documents that were flowed down are provided to show the work performed by the JV member. Offerors are advised that only performance pertaining to the proposed entity will be considered.

The Offeror’s past performance contracts’ SOW/PWS and other contract information files (provided in

Annex #2) only need to be submitted electronically, a hard copy is not required. For the electronic submission of the files, the Offeror’s identified sections related to the scope and complexity elements only need to be identified, and do not need to be broken out separately from the complete contract file. When submitting the entire electronic file for the referenced contract the Offeror shall clearly state, in Attachment P2, Column C, where to find the relevant scope, complexity and magnitude elements.

Offerors are required to explain what aspects of their referenced contracts are deemed relevant to the AVMI requirements. To demonstrate relevancy, Offerors shall provide a comparative analysis to the AVMI requirements with regard to the criteria identified in their Attachment P2 submission. To ensure that the past performance evaluators know where to find the relevant scope and complexity elements in their submitted contract files, Offerors shall identify the applicable portions (sections, paragraphs and page numbers) of the referenced contract. When conducting the evaluation, the evaluators will look to Column C within Attachment P2 to find the location (section, paragraph, page) of similar scope or complexity within the referenced contract files. If a referenced contract does not contain certain similar scope or complexity elements, Offerors are advised to mark those elements which are not contained in the referenced contract files as not applicable (N/A).

For each Scope and Complexity area, provide a cross reference of each RFP SOW paragraph or sub-paragraph or contract clause reference to the Offeror’s Past Contract’s SOW/PWS/Specifications paragraphs and/or contract reference. Include in this cross reference rationale explaining in technical terms if applicable, why it should be considered similar. Instead of including this cross reference information in P2, Column C, the offeror may provide this information in a separate table, or excel file, that provides for each scope and complexity area a row for each

RFP reference or SOW paragraph/subparagraph and three columns for the RFP reference, past contract references, and the similarity rationales. Do NOT provide self-assessed relevancy ratings. Only provide the comparative analysis as stated.

(1) The Offeror is advised that the Government will assess each present/past performance contract reference and assign a relevancy rating as outlined in Section M, Part B, Paragraph 1.0 Past

Performance.

(2) Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessment.

Identify the CAGE code for all proposed entities (Prime Contractor and if applicable each JV team member). The

CAGE Code is the same as the CAGE Code identified on Block 15A on the Standard Form (SF) 33, Solicitation, Offeror, and Award. Contract references that relate to a different CAGE code/DUNS than the proposed entity 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.

Therefore, identify all other CAGE Codes that are applicable to the proposed entity for these reasons. To facilitate the Relevancy determination, the Offeror shall provide an explanation and justification that multiple CAGE codes are applicable for the same physical location of the proposed entities. 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.

Note: “Place of Performance” for this solicitation pertains to the physical location of the prime or other entities that are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

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

(1) Quality: meeting technical requirements.

The quality rating assesses the contractor’s conformance to contract/order requirements, specifications and standards of good workmanship (e.g., commonly accepted technical, professional, environmental, or safety and health standards). Including, as applicable, information on the following:

Are reports/data accurate?

Does the product or service provided meet the specifications of the contract/order?

Does the contractor’s work measure up to commonly accepted technical or professional standards?

What degree of Government technical direction was required to solve problems that arise during performance?

(2) Schedule: meeting schedule requirements.

The schedule rating assesses the timeliness of the contractor against the completion of the contract, task orders, milestones, delivery schedules, and administrative requirements (e.g., efforts that contribute to or affect the schedule variance).

(3) Cost: controlling contract cost

The cost rating assesses the contractor’s effectiveness in forecasting, managing, and controlling contract/order cost; and

(4) Management: managing the contracted effort

The management rating assesses the integration and coordination of all activity needed to execute the contract/order, specifically the timeliness, completeness and quality of problem identification, corrective action plans, proposal submittals, the contractor’s history of reasonable and cooperative behavior (to include timely identification of issues in controversy), customer satisfaction, timely award and management of subcontracts.)

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

d. Authorization Letter(s)

In the event that the Offeror is a Joint Venture (JV), the Offeror shall submit a signed “Release of Adverse Past

Performance Authorization Letter(s)” with written consent from each JV Team Member, authorizing the release of adverse past performance information to the Offeror. The signed letter(s) should be included in Annex #2 within

Volume 1 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Offeror. For any JV team members that do not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each JV team member. This contact information shall include a name, address, phone number, and email address, with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does 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 JV team member, and the Offeror will forfeit the opportunity to participate in any related discussions.

VOLUME 2: TECHNICAL

Cost or pricing information shall not appear in this technical volume and only appear in the Cost volume.

Proposal information must be structured such that its Volume/paragraph number matches the Proposal Instructions paragraph number provided below to which it is responding, although the Offeror may add lower tier subparagraphs.

Throughout the proposal the offeror shall demonstrate the effectiveness of any proposed approach or capability based on historical data and the Offeror experience with those approaches/capabilities.

2.1 PHASE-IN TRANSITION PLAN

Offerors shall submit a detailed plan covering the period of 60 days prior to the start of the period of performance that defines the critical tasks and timelines needed to ensure a smooth and phased transition into full performance in accordance with the Statement of Work. Specifically include in the Transition Plan the following:

A) Provide a time phased transition plan that indicates functions during transition in order to demonstrate a "ramp-up" to achieve full staffing levels and performance, including staffing, associated security clearances, training, and GOP development. Show which tasks are dependent on others and which can be accomplished concurrently. Clearly identify the critical path. Assume for purposes of the transition plan that full staffing levels are 77 FTE’s at Patuxent River, 14 FTE’s at China Lake and 13 FTE’s at Point Mugu, excluding overtime.

B) Provide a plan for hiring personnel while complying with FAR Clause 52.222-17. This hiring plan should also account for new requirements, as well as, a plan for incumbent personnel that do not transition to the follow on contract. Discuss the approach, steps to take, personnel involved, etc. Show the time-phased elements of the plan in the transition plan provided in A above.

C) Demonstrate that new hires will have their clearance eligibility by day one of the PoP.

D) Provide a plan to address training for personnel to achieve contract (e.g. labor category and GOP) and regulatory requirements (e.g. OSHA). Include critical milestones and resources that may affect the ability to have everyone properly trained in time for full performance. Demonstrate that training will be developed from approved GOPs and personnel will be trained from those documents during the transition period. Discuss the approach, steps to take, personnel involved, etc. Show the time-phased elements of the plan in the transition plan provided in A) above.

E) Provide a plan for the development and Government Ground Flight Representative (GGFR) approval of the

Ground Operating Procedures identified in SOW Attachment 1c ‘GOPs Guidance’. Discuss the approach, steps to take, personnel involved, etc. that contribute to approved GOPs. Demonstrate that GGFR approved GOPs will be ready to be submitted per CDRL A031 on day one of the Period of Performance. Show the time-phased elements of the plan in the transition plan provided in A above. When including Government approval/review turn-around in your plan, please use the following guidelines: The GGFR will need five working days to review and/or approve the Tool Control GOP, as that is one of the more critical GOPs. The GGFR will need two working days for approval/review of the other GOPs – including resubmittals. The GGFR cannot review more than two GOPs at any given time.

F) Address any other tasks or functions needed to complete transition. Discuss the approach, steps to take, personnel involved, etc. Show the time-phased elements of the tasks in the transition plan provided in A above.

G) Describe risks associated with accomplishing the transition such that the Offeror is ready for full performance on day one. Describe risk mitigation plans to address those risks.

2.2 WORKFORCE MANAGEMENT EXPERIENCE

Demonstrate the extent to which the Offeror’s experience in managing a workforce is similar to the management effort that will take place on the future contract by comparing the past efforts of relevant contracts to the future contract as proposed. A relevant contract is defined under the Past Performance factor in Section M of the solicitation. If proposing as a JV team, Offerors shall include the experience of the JV as a whole, as well as the experience for each JV team member.

A) For each relevant contract, provide the following information in table 2 below:

1) Provide the reference number to a relevant contract provided under the Past Performance section.

2) Provide a customer POC, preferably Government personnel, who can verify the information below for each contract.

3) Provide the Period of Performance the contract was active, but not older than five years prior to the date of the release of this solicitation and with more than one year of recent experience. If providing a current contract, use the month/year of proposal submission as ending date. Based on the Period of Performance provide the total number of months of the contract’s performance up to the proposal due date that is within the recency window and provide the number of months since the contract was last performed (if ongoing, just state that it is currently being performed).

4) Provide the number of workforce personnel managed by the Offeror under the contract. Note: there is expected to be approximately 104 people on the future contract. For performance of one year, provide the maximum number of personnel managed on the contract at one time. For multiyear performance, use the maximum managed on the contract during a base or option period and average across the number of periods. For example, if during the last five years the Offeror had a relevant contract covering a base year, a first option year, and two months of a second option year, take the highest number for each of those periods, add together, and divide by 3.

5) Provide the percentage of the workforce that was subject to the Service Contract Act (SCA). Note: It is expected to be greater than 75% SCA on the future contract.

6) Provide the location (City, State) of each site the Offeror had personnel stationed full time during the period of performance, where it is expected to be three sites (Patuxent River MD, China Lake CA, and

Point Mugu, CA) on the future contract. If the Offeror was the prime on the contract, include all sites listed in the contract regardless of whether subcontractors provided all the support at a location.

7) Identify whether or not the Offeror was the Prime for this contract.

8) Identify whether or not the contract included working on military or commercial aircraft.

B) In addition to table 2 below, provide information for each attribute under each contract reference that demonstrates that the attribute was required and/or performed under that contract; e.g. refer to the specific paragraph of the past contract’s SOW. Examples provided in the table below assumes the proposal due date is

November 2018 and the solicitation release date is October 2018.

Table 2 Workforce Management Experience

R el ev an t C o n tr ac t R ef er en ce

C o n tr ac t

P O

(N am e, P h o n e, E m ai l)

P er io d o f

P er fo rm an ce

(M n /Y ea r to M o n

/Y ea r) in cl u d in g d u ra ti o n p er fo rm ed d m o n th s si n ce l as t p er fo rm ed

Attributes

A v er ag e o f w o rk fo rc e p er so n n el b ei n g m an ag ed f th e w o rk fo rc e th at i s

S

A

M ag ed s it e lo ca ti o n s

(C it y

S ta te

W as t h e P ri m e?

Y es o r N o

E ff o rt i n cl u d ed w o rk in g n a ir cr af t?

Y es o r

N

PP-1

Bob Smith, 301-342-0000

Bsmith1@service.mil

4/2015 – 1/2018

Amount: 33 months

Recency: Current

45 22%

Patuxent River, MD;

Aberdeen, MD

Yes No

PP-2

Bob Smith, 301-342-0000

Bsmith1@service.mil

9/2013 – 10/2015

Amount: 24 months

Recency: 37 months

45 22%

Patuxent River, MD;

Aberdeen, MD

Yes No

2.3 GOPS DEVELOPMENT CAPABILITY

Demonstrate capability in preparing high-quality Ground Operating Procedures for tool control. If the offeror cannot demonstrate its capability through experience as described in A) below, demonstrate capability through B) below and explain how that capability mitigates any risk associated with lack of experience.

A) Previous GOPS Experience

1) Identify the contracts with the five year recency period for which the Offeror was responsible for developing a Tool Control GOP.

2) From any of the contracts identified from 1) above, provide a copy of the most recent Tool Control GOP signed by the GGFR or the Ground Flight Representative (GFR) that satisfies NAVAIRINST 3710.1G paragraph 5.3 or equivalent DoD instruction (DCMA INST 8210.1, AFI 10-220, AR 95-20, or

COMDTINST M13020.3) to demonstrate that the Offeror has the capability to create a tool control GOP.

The submitted GOP must show your company name and must show a GGFR or a GFR signature. Place the submitted GOP in Annex #3 and state in the proposal that the GOP has been provided.

B) Provide a GOP Template per the following:

Using the NAVAIRINST 3710.1G Instruction and the SOW, Offerors shall create a generic GOP Template that would be used for the resulting contract. The template shall contain the sections identified below and any other sections the Offeror believes should be addressed in a GOP. For each section and sub-section of the GOP template, include a narrative that provides guidance to the future GOP writer about content and items/situations that should be considered, addressed, and/or included in that section when writing a GOP during contract transition. Include paragraph references to the NAVAIRINST 3710.1G requirements within each section as applicable. This template should address the most common situations the writer may encounter when writing the GOPs for this SOW in general and a Tool Control GOP in particular.

1) GOP Template Sections

2) Purpose of the GOP

3) Policy

4) Applicability

5) Referenced Documents

6) Procedures

7) Training/Certification

2.4 MANAGEMENT APPROACH

Describe the approach to managing the effort on this future contract in accordance with the SOW. This approach may be incorporated into the contract and become part of the Management Plan CDRL. Address as a minimum the following:

A) MANAGEMENT ROLES. Provide an Organizational Chart and a short description of the proposed roles of the

Offeror’s management structure for the resulting contract. The description shall include efforts for managing to the functional work group (FWG) level as defined in the SOW, paragraph 3.1.11.3 and include the following:

1) Identify the management structure beginning with the first manager level above ‘worker’ and continue through two levels above the Program Manager (or the president of the company, whichever comes first).

2) Identify major responsibilities for each management role relating to the management of the contract.

Include a discussion for any potential conflicts of interest under this contract.

3) Identify the authority each management role shall have (e.g. hire, removal, contract signature authority, travel approval, purchase approval, etc.)

4) Identify communication lines through which major tasks will be managed.

5) Identify the city and state where each manager will be located.

6) If subcontractors are part of your proposal, explicitly identify management roles that will be filled by subcontractors. Discuss how the subcontracts and subcontractors will be incorporated into your management approach in the above items.

B) CONTRACT MANAGEMENT SUPPORT USING DIRECT LABOR

Describe your approach towards contract management. In table 6, lab or categories Program Manager, Senior;

Safety Specialist; Secretary II, and General Clerk II have been set aside (each allocated with 1920 hours per option year) to perform the contract managing functions. Demonstrate that those hours are sufficient to perform the contract management function and if it is not, provide risk mitigation actions to overcome that challenge.

Specifically show how the management staff will be used to accomplish the management activities identified in

SOW paragraph 3.1.11.1 and 3.1.11.2.

C) PERSONNEL: Demonstrate the ability to hire, retain, and remove personnel needed to support the AVMI effort.

1) Hiring

a) Identify your approach to finding potential new hires to support the Government in the most responsive way.

b) For the technical positions on this contract, address your approach to ensuring a technical understanding of the labor category skills and requirements by your hiring manager which enables your company to interview and select qualified technical personnel.

c) Describe potential challenges in finding hard to fill labor categories that could occur and risk mitigation strategies that could be utilized.

d) Address your ability to hire short-term (less than one year) and/or part-time personnel to fill a temporary need due to absence (e.g. vacation, sick leave, family leave, military leave, and as a stop-gap for someone that retires, quits, etc.). Discuss your experiences with this scenario, the locations it was used, the approach/tools utilized, and how you would make this work at the three AVMI locations.

e) Provide a hiring timeline showing how you plan to add new support personnel to the contract during execution. If there is a difference between hiring SCA and non-SCA positions, the Offeror shall provide two timelines - one for SCA positions and one for non-SCA positions. If only one timeline is provided, it will be viewed as the same timeline for both. SCA positions are identified in the SOW

Attachment 1a – Labor Categories by the use of an SCA code. Address the following in your approach.

(i) Use the day that the requirement is provided to the contractor as day 1 (or January 1 if using calendar software). The timeline should be graphical for ease of understanding (e.g. a Gantt

Chart) and include typical tasks and their durations of the hiring process and cover through and including when the candidate is available and ready to work on site.

(ii) Per paragraph 3.4.1.5 of the SOW, all new hires shall have a clearance or interim clearance (if required) prior to the start date. DO NOT include a clearance function in the timeline. Assume they already have the proper clearance.

(iii) Show which hiring tasks are dependent on others and which can be accomplished concurrently.

(iv) Clearly identify the critical path and typical length of time to complete the hiring process.

(v) Provide a description of what is being accomplished within each of the identified functions discussed above. Address any subcontractor involvement. Explain the rationale and any assumptions in your approach including how you determined the amount of time each task will take.

2) Retention Strategy

Offerors shall describe their strategy for the retention of contractor personnel during the execution of the contract to ensure the continued staffing of the skill sets required for long-term mission success. This does not relate to retaining incumbent personnel during transition. The Offeror shall address specific approaches, programs, and efforts at the company level in the following three areas:

a) Compensation and recognition

b) Conducive work environment and life balance (considering that 100% of the work is performed on a

Government installation)

c) Training and growth

3) Remediation/Removal

Discuss the approach for remediating and ultimately removing a problem employee on this contract using the COR/PM discussion about the problem as the catalyst. Address all elements below.

a) Discuss which contractor management function/level intervenes, when, and how often.

b) Discuss which contractor management function(s) will monitor for future behavior, when, and how often.

c) Discuss any other management techniques employed and/or employee consequences in order to bring performance in line with contract expectations.

d) Discuss what must happen before the employee will be removed from the contract.

3 VOLUME 3: COST PROPOSAL

3.1 VOLUME CONTENT:

(a) This Volume shall include the Contract Compliance information specified below as follows:

i. Offeror Summary Table: The Offeror shall complete the table below. The Offeror shall include all subcontractors and Joint Venture (JV) team members who will be involved with the performance of the contract. In addition, Offerors shall list the CAGE Code for each member of the Offeror’s team (prime + subs or JV team member) and the percentage of the total proposed price based on what is being proposed to be performed by each company.

Contractor Name

(Indicate Prime, JV

Team Member, or

Subcontractor)

Cage Code /

DUNS #

% of Total

Proposed Price

ii. Signed SF33 for basic solicitation and acknowledgment of each amendment, including completion of any solicitation clause or provision that requires a fill-in or response (e.g. Section I (FAR 52.219-28 Post award Small

Business Program Representation).

iii. Signed Representations, Certifications, and Acknowledgements () and Section K certs and reps) and/or

System for Award Management (SAM).

iv. Guarantee the length of proposal validity is for at least 180 days after proposal due date.

(b) This Volume shall also contain a copy of Section B with the Contract Line Item Number (CLIN) Unit

Prices and, for evaluation purposes, the Total Prices filled in using the Government Provided Information (Section

L, Part B, Paragraph 3.5), the Attachment P3 (Cost Summary Spreadsheet) and the instructions below. Section B

CLIN prices shall be consistent with the calculated costs from the P3 Cost Summary Spreadsheet. As an example, the Estimated Cost, Fixed Fee and Total Estimated Cost + Fee dollar values for CLIN 0001 in Section B must be consistent with the calculated totals in the P3 spreadsheet for those elements related to CLIN 0001. In this example, the proposed CLIN 0001 dollar values are calculated within the P3 Attachment in the Worksheet/Tab entitled “PAX

(RDT&E X001 – X004)” and the total dollar value for that CLIN is summarized in the Worksheet/Tab entitled

“CLIN Summary”. The dollar value of the CLINs in Section B should be consistent with the CLIN totals in the

“CLIN Summary” Worksheet/Tab within the P-3 Attachment.

This proposal volume shall be provided in accordance with the required copies outlined in paragraph 3.0 in Part A of this section. The required electronic copy shall be submitted in one digital data copy in MS Office 2016 Excel format on CD/DVD-ROM media. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using “value only” cells. If links are utilized, supply those referenced files.

Spreadsheets shall not be protected.

(c) All cost and cost supporting information required in paragraphs 3.2 through 3.5 below shall be contained in the Cost Volume. Offerors shall organize their Cost Volume to be consistent with the paragraph structure of this Cost section. No price or pricing information shall be included in any other proposal volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their cost proposal.

(d) Government Agency Information: Offerors and their subcontractors shall provide the mailing address, telephone number, email addresses and facility codes for their local Defense Contract Management Agency

(DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. If the Offeror’s

Administrative Contracting Officer (ACO) at the DCMA is known,…