N61340-17-R-0020_NSST_Amend_0004.docx

N61340-17-R-0020

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 09-Jun-2017 12:00 PM to 14-Jun-2017 12:00 PM.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

BASIC CONTRACT ATTACHMENTS

Basic ID/IQ Contract Attachments

Attachment 1. Statement of Work (SOW) 170001 Attachment 2. NAWCTSD Data Item Transmittal/Acceptance/Rejection Form 4330 Attachment 3. Over and Above Work Request (OAWR) Form Attachment 4. Individual Subcontracting Plan Goals Sheet Attachment 5. System Specification (PRF) 170003

Solicitation Attachments Attachment L1. Price Attachment_Rev2 Attachment L2. Delivery Order 0001 Terms and Conditions (T&Cs)_Rev2 Attachment L3. CPARS Update Questionnaire_Rev1 Attachment L4. Past Performance Questionnaire_Rev1 Attachment L5. Solicitation Question/Comment Form Attachment L6. NSST QA Tracker Set 5 Ver 1(9MAY2017) Attachment L7. NSST QA Tracker Set 6 Ver 1(24MAY2017) Attachment L8. NSST QA Tracker Set 7 Ver 1(5JUN2017)

Delivery Order 0001 Attachments/Exhibits

Attachment 1. NSST DO1 Statement of Work (SOW) 170002A Attachment 2. RESERVED Attachment 3. Trainer Test and Evaluation Plan (TTEP) Template Attachment 4. DD-254 Security Classification Attachment 5. NSST TRD Attachment 6. NSST_TMCR 17-05 Attachment 7. NSST_WBS Attachment 8. NAVDORM 3530.4E Attachment 9. NAVEDTRA 43492-2I(NAV_PQS) Attachment 10. NAVEDTRA_43101-4F(SWO_PQS)

Exhibit 1. CDRL A001 Test Procedures (TP) Exhibit 2. CDRL A002 Revisions to Existing Government Documents, Trainer Test & Evaluation Plan (TTEP) Exhibit 3. CDRL A003 Scientific And Technical Reports, Software Product Specification (SPS) (Includes Annex to CDRL A003) Exhibit 4. CDRL A004 Scientific And Technical Reports, Requirements Traceability Verification Matrix (RTVM) Exhibit 5. CDRL A005 System/Subsystem Specification (SSS) Exhibit 6. CDRL A006 System/Subsystem Design Description (SSDD) (Includes Annex to CDRL A006) Exhibit 7. CDRL A007 Scientific And Technical Reports, Training System Analysis Report (TSAR) Exhibit 8. CDRL A008 Product Drawings/Models And Associated Lists (PDAL) (Includes TDP Option Selection Worksheet for CDRL A008) Exhibit 9. CDRL A009 Engineering Change Proposal (ECP) Exhibit 10. CDRL A00A Request for Variance (RFV) Exhibit 11. CDRL A00B Operations Security (OPSEC) Plan Exhibit 12. CDRL A00C Revisions to Existing Government Documents, Authorization To Operate (ATO) Package Exhibit 13. CDRL A00D Test/Inspection Report Exhibit 14. CDRL B001 Contractor’s Progress, Status And Management Report (CPSMR), Monthly Status Report Exhibit 15. CDRL B002 Integrated Program Management Report (IPMR), Integrated Master Schedule (IMS) (Includes Government provided WBS) Exhibit 16. CDRL B003 Trip/Travel Report Exhibit 17. CDRL B004 Conference Agenda Exhibit 18. CDRL B005 Conference Minutes Exhibit 19. CDRL B006 Presentation Material Exhibit 20. CDRL C001 Logistics Product Data (LPD) Exhibit 21. CDRL C002 Engineering Data For Provisioning (EDFP) Exhibit 22. CDRL C003 Special Equipment Tools and Test Equipment List Exhibit 23. CDRL C004 Bill Of Materials (BOM) for Logistics and Supply Chain Risk Management Exhibit 24. CDRL C005 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan Exhibit 25. CDRL D001 Warranty Performance Report Exhibit 26. CDRL D002 Equipment Inventory Records (EIRS) Exhibit 27. CDRL D003 Configuration Audit Summary Report And Certification Exhibit 28. CDRL D004 Technical Directive (TD), Training Equipment Change Directive (TECD) Exhibit 29. CDRL E001 Operation and Maintenance Manual Exhibit 30. CDRL E002 Data Module Requirements List S1000D Exhibit 31. CDRL E003 Common Source Data Base (CSDB) Exhibit 32. CDRL E004 Project Business Rules Decision Table, S1000D Exhibit 33. CDRL E005 Project Business Rules Exchange (BREX) File, S1000D Exhibit 34. CDRL E006 Instructor Operator Manual (I/OH) Exhibit 35. CDRL E007 Maintenance Requirement Cards Exhibit 36. CDRL E008 Commercial Off The Shelf (COTS) Manual Exhibit 37. CDRL E009 Technical Data Content and Production Plan Exhibit 38. CDRL F001 Training Program Structure Document, Maintenance Training Course Exhibit 39. CDRL F002 Training Program Structure Document, Instructor Training Course

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

The offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the offeror’s capability to meet or exceed the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements, and that the offeror has valid and practical solutions for all requirements and potential risk areas. Offerors must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The offeror has the burden of proof to demonstrate compliance with all the evaluation factors and subfactors identified in this solicitation. The offeror is advised that the Government may incorporate into the final contract enhancing features included in the offeror’s proposal deemed beneficial to the Government. With the exception of the price volume, no pricing information should appear in any volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price proposal without opening discussions. Statements that the prospective offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable.

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 subfactor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The offeror is expected to comply with all requirements of the RFP. The Government advises the offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal unawardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency.

If an offeror proposes the resources of a principal team member – which is defined as a subcontractor, joint venture owner (joint venturer), partnership owner (partner), corporate parent, division, subsidiary, or affiliate that is proposed to provide at least 20% of the proposed total price (excluding the offeror’s profit) for the contract – the offeror will not receive past performance credit of the proposed principal team member unless the offeror’s proposal demonstrates how the resources of the principal team member – its workforce, management, facilities or other resources – will in fact be provided to perform at least 20% of the proposed total price for the contract, excluding the prime offeror’s profit. Merely stating that the offeror has access to the resources of a principal team member is insufficient.

2.0 PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt. normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page.

The offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer PCO in paper format and on a CD-ROM as electronic files fully compatible with Microsoft Office 2010 and for information not supported by MS Office products, with the latest Adobe Acrobat reader. The offeror will ensure the Price Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the offeror’s name. If a discrepancy exists between the original paper version of the proposal and the CD-ROM copy, the paper version will take precedence.

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 such that its paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the offeror may add lower tier subparagraphs. The offeror must 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, book, section, and element, etc., in offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Page limitations for each volume if any, are specified in the table below; title and table of contents pages do not count towards page limit.

Information submitted as an Annex to the proposal includes 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. Annexes and Cross Reference Matrices do not have page limitations with the exception of the Data Rights Annexes. The authorized Annexes are summarized in the table below and shall contain only directly related proposal information.

AND WAIVERS

I. Page count does not include the tables for Section L.B.2.2.1 Contract Data II. Page count does not include requirement documents for Section L.B.2.3.7

Each volume shall contain the following information:

· Cover and title page

· Title of proposal and proposal number as applicable

· Offeror’s name, address and POC

· RFP number

· Proposal volume/book 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

The offeror may submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The offeror’s CRM may be identical to the one provided.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Volume 2 Technical Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the Performance Specification

Volume 2 Technical

Volume 2 Technical

4.0 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for the original proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP.

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 Warfare Center Training Systems Division (NAWCTSD) Code: AIR-2.5.3.6 Jason Harvey 12211 Science Dr.

Orlando, FL 32828 Solicitation Number: N61340-17-R-0020

Hand carried proposals may be delivered to the address above, attention Jason Harvey. If an offeror chooses to hand carry a proposal, arrangements shall be made at least three (3) Government workdays in advance with Mr. Jason Harvey. Mr. Harvey may be contacted by phone at (407) 380-4024 or by email at Jason.G.Harvey@navy.mil. The alternate point of contact is Mr. Jonathan Abbott who may be reached at (407) 380-8010 or by email at Jonathan.D.Abbott@navy.mil. Visitor request approval must be obtained prior to facility access.

5.0 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. If more than one container is required, one container shall include all Original Proposal volumes including the original/signed documents submitted.

Each container 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.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0 SOLICITATION CHANGES

For any changes and additional information for the solicitation please search for solicitation number N61340-17-R-0020 on the Federal Business Opportunities website located at URL: https://www.fbo.gov/

8.0 SOLICITATION QUESTIONS/COMMENTS

Solicitation questions shall be emailed to the point of contact identified in Section 4.0 using Attachment L-5, Question/Comment Form and must be received no later than 20 calendar days before the RFP closing date. It is requested that each question or comment reference the applicable document, paragraphs, and page number.

The Government will answer all questions prior to the deadline for proposal submittal provided that those questions are received by 1400 Eastern Standard Time (EST) 20 calendar days before the RFP closing date. Answers and questions will be sent to offerors via a formal RFP amendment. Thus, offerors are cautioned not to include proprietary information in the questions because the government may release it to all offerors. The Government reserves the right not to respond to any questions received concerning this solicitation after the date above. Accordingly, offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer with the exception of the small business targets submitted in the Small Business Annex.

The offeror shall provide information and data required to conduct a thorough and complete technical evaluation. The offeror shall not provide additional information beyond what is described herein.

1.1 Subfactor 1 – Delivery Order 1 Proposal

The Offeror shall provide the following information.

1.1.1 Section 1 – Technical Approach

The Offeror shall submit a written technical approach describing the offeror’s proposed program management approach, systems engineering approach, and system test and evaluation approach that the offeror would use to meet the requirements of the specified processes in NSST DO1 SOW #170002A. Where the offeror believes the offeror’s written technical approach establishes an innovation, unique capability, or a unique qualification that may be advantageous to the Government during contract performance, the offeror shall indicate in the written technical approach that the proposed element is an innovation, unique capability, or unique qualification. The offeror shall address all known technical approach risks, in accordance with impacts to price, schedule, and performance, and the offeror’s plans to mitigate those risks.

1.1.2 Section 2 – Training System Hardware Design

The Offeror shall provide a written training system hardware design that includes a written narrative describing each major hardware component, hardware block diagrams, and conceptual training system hardware arrangements that depict the proposed training system hardware components and their interfaces for each NSST configuration and instructional station as defined in Specification #170003, sections 3.1.1 - 3.1.8 and subsections, and 3.3 and subsections. Where the offeror believes the offeror’s written training system hardware design establishes an innovation or unique capability that may be advantageous to the Government, the offeror shall indicate in the narrative that the proposed element is an innovation or unique capability. The offeror shall include a list of system hardware components as an Annex. For each of the listed components in the Annex, the offeror shall identify if the component is a Commercial Off The Shelf (COTS) item, as defined in FAR 2.101, or not and provide rationale for using hardware components other than COTS.

1.1.3 Section 3 – Training System Software Design

The offeror shall provide a written training system software design that includes a written narrative describing all training system software components, a written narrative describing the training system wide application program interface (API) and the data to be sent and received for each software component, and a software block diagram that depicts the proposed training system software components and their interfaces as required in Specification #170003, sections 3.1.1 - 3.1.8 and subsections, and 3.3 and subsections. Where the offeror believes the offeror’s written training system software design provides an innovation or unique capability that may be advantageous to the Government, the offeror shall indicate in the narratives that the proposed element is an innovation or unique capability.

1.1.4 Section 4 – Development Seat Design

The offeror shall provide a written development seat design describing the design of the development seat as required in Specification #170003, section 3.1.9 and subsections, and 3.3 and subsections. The offeror shall list the software proposed to be resident on the NSST development seat. The offeror shall describe how the development seat will be used for offline visual database modeling, training system software development, modification, and testing. The offeror shall describe how modified NSST software and databases are deployed to all NSST configurations.

1.1.5 Section 5 – Instructional Station Operational Description

The offeror shall provide a written instructional station operational description that includes a written narrative describing the conceptual instructor control of each NSST configuration with illustrations showing proposed screen layouts and how the proposed screen layouts will be organized for the Instructor Operator Station (IOS), Master IOS (MIOS), and briefing station as defined in Specification #170003, section 3.1.5 and subsections. Where the offeror believes the offeror’s written instructional station operational description provides an innovation or unique capability that may be advantageous to the Government, the offeror shall indicate in the narrative that the proposed element is an innovation or unique capability.

1.1.6 Section 6 – Simulation and Visual Fidelity Description

The offeror shall provide a written simulation and visual fidelity description that includes a narrative describing the proposed training system’s fidelity for: 1) Simulation of: interfaces and methods for trainee establishment of the ship’s position; total system accuracy and precision for each fix type (i.e. visual, radar, and GPS); vessel steering systems; vessel propulsion systems; vessel motion; degraded navigation system conditions; degraded vessel steering systems; degraded vessel propulsion systems; perceptually accurate depictions of visual and audio training cues; and surface radar systems; and 2) Visual system auto calibration process; projection system luminance and resolution via plots over the design basis display surface with the calculations used to arrive at the estimated luminance and resolution; positional and temporal correlation across all visualization and other sensor related software components as defined in Specification #170003, section 3.1.2 and subsections, section 3.1.3 and subsections, 3.1.7 and subsections, and 3.1.8.4 and subsections. Where the offeror believes the offeror’s written simulation and visual fidelity description provides an innovation or unique capability that may be advantageous to the Government, the offeror shall indicate in the narrative that the proposed element is an innovation or unique capability.

1.1.7 Section 7 – Small Business Utilization Annex

1.1.7.1 Element 1 - Strategies for using Small Business (SB) Concerns

All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. For purposes of this solicitation, SB shall also include Small Disadvantaged Business, Veteran-Owned SB, Service-Disabled Veteran-Owned SB, HUBZone SB, Women-Owned SB, and Historically Black Colleges or Universities (HBCU) and Minority Institutions (MI). Each subcategory of SB shall be addressed. This strategy is separate from, but shall be consistent with, the Small Business Subcontracting Plan.

In describing its strategy for this solicitation, the offeror shall describe the following:

1. The extent of participation of SB Concerns on this contract, especially as principal subcontractors;

2. Provide targets, expressed as dollars and percentages of total contract values for SB participation. Targets of subcontractors must be listed separately. Note: This calculation is different from the calculation required by FAR 52.219-9 in the Subcontracting Plan, as the Plan requires percentage of subcontracting value;

The Government has identified a small business utilization goal of 15% of the total estimated value of the ID/IQ over the life of the contract.

1.1.7.2 Element 2 - Small Business Subcontracting Plan

The Large Business offeror shall provide its SB Subcontracting Plan conforming to the requirements of FAR 19.704 and DFARS 219.7. If the offeror is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, the offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive Subcontracting goals. The offeror shall describe its specific efforts to ensure the resulting contract meets or exceeds proposed goals. 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 offeror shall identify the small business subcontracting goals for Delivery Order 0001 in an addendum to the small business subcontracting plan using contract attachment 4 “Individual Subcontracting Plan Goals Sheet”.

1.2 Subfactor 2 – Software and Data Rights

In the two Technical proposal volume annexes set forth below, the offeror shall provide the required information regarding proposed rights in technical data (TD), computer software (CS), and computer software documentation (CSD) to be delivered under Delivery Order 0001. The terms “technical data,” “computer software,” and “computer software documentation” are defined in DFARS clause 252.227-7013 and DFARS clause 252.227-7014.

1.2.1 Annex: Rights in Noncommercial TD, CS, and CSD

1.2.1.1. The “7017 List.”

The offeror shall include in this annex a list identifying all noncommercial TD, CS, and CSD that the offeror asserts should be delivered with other than Unlimited Rights. Specific instructions and requirements concerning this list are set forth in DFARS clause 252.227-7017, “Identification and Assertion of Use, Release, or Disclosure Restrictions” (JAN 2011), which is incorporated in Section K of this solicitation. If there is no TD, CS and CSD being delivered with other than Unlimited Rights to be identified in the “7017 List,” the offeror shall submit the list and enter “None” in the body of the list. If the offeror is awarded a contract, the “7017 List” shall be attached to the contract.

For each item listed in the “7017 List,” the offeror shall discuss the extent to which the rights in the deliverable noncommercial TD, CS, and CSD offered to the Government provide for:

1.2.1.1.1 Unimpeded and cost effective production, operation, maintenance, and upgrade of NSST systems throughout their life cycle;

1.2.1.1.2 Allow for open and competitive procurement of NSST systems, NSST system enhancements, and NSST system support; and

1.2.1.1.3 Permit the transfer of the NSST system’s non-proprietary technical data, computer software documentation, and computer software - to include source code, object code, and related material that would enable the software to be reproduced, recreated, or recompiled - to other contractors for use on other systems or platforms.

1.2.1.2. The “7028 List.”

The offeror shall include in this annex a list identifying all noncommercial TD, CS, and CSD that the offeror intends to deliver with other than Unlimited Rights and that are identical or substantially similar to TD, CS, or CSD that the offeror has delivered to, or is obligated to deliver to, the Government under another contract or subcontract. Specific instructions and requirements concerning this list are set forth in DFARS clause 252.227-7028, “Technical Data or Computer Software Previously Delivered to the Government” (Jun 1995), incorporated in Section K of this solicitation. If there is no data or software to be identified in the “7028 List,” the offeror shall submit the list and enter “None” in the body of the list. If the offeror is awarded a contract, the “7028 List” shall be attached to the contract.

For each item listed in the “7028 List,” the offeror shall discuss the extent to which the rights in the deliverable noncommercial TD, CS, and CSD offered to the Government provide for:

1.2.1.2.1 Unimpeded and cost effective production, operation, maintenance, and upgrade of NSST systems throughout their life cycle;

1.2.1.2.2 Allow for open and competitive procurement of NSST systems, NSST system enhancements, and NSST system support; and

1.2.1.2.3 Permit the transfer of the NSST system’s non-proprietary technical data, computer software documentation, and computer software - to include source code, object code, and related material that would enable the software to be reproduced, recreated, or recompiled - to other contractors for use on other systems or platforms.

1.2.1.3. Specifically Negotiated License Rights.

The offeror shall include in this annex any proposed specifically negotiated license rights for each item of noncommercial TD, CS, or CSD that the offeror asserts should be delivered with specifically negotiated license rights, as found at DFARS clause 252.227-7013, “Rights in Technical Data – Noncommercial Items” (FEB 2014), and/or DFARS clause 252.227-7014, “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation” (FEB 2014). If there are no specifically negotiated license rights proposed the offeror shall submit a statement stating “None.”

The offeror’s proposed specifically negotiated license rights, which require mutual agreement, must set forth a complete description of all proposed non-standard restrictions on the Government’s ability to use, modify, reproduce, release, perform, display, or disclose noncommercial TD, CS, or CSD. The offeror shall submit the proposed specifically negotiated license as an annex to its Technical proposal volume, dated and signed by an official authorized to contractually obligate the offeror.

Any proposed specifically negotiated license rights require agreement by the Government. Pursuant to this RFP, however, the Government is entitled to award on initial proposals and, thus, the Government is not required to enter into discussions to discuss an offeror’s proposed specifically negotiated license rights. Thus, an offeror may not have the opportunity to resolve any evaluated weaknesses that may be associated with the offeror’s proposed specifically negotiated license rights. If the Government has agreed to the proposed specifically negotiated license rights, either as part of award on initial proposals or as a result of discussions and receipt of a revised proposal, and the offeror is awarded a contract, the specifically negotiated license rights shall be made a part of this contract.

1.2.2 Annex: Rights in Commercial TD, CS, and CSD

The offeror shall include in this annex a list, entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use Restrictions” (the Commercial Restrictions List), that provides the following information regarding all commercial and commercially available off-the-shelf TD, CS, and CSD that the offeror intends to deliver with other than Unlimited Rights: (1) identification of the TD, CS or CSD; (2) basis for asserting restrictions; (3) asserted rights category; and (4) name of the person asserting restrictions.

For each entry in the Commercial Restrictions List, the offeror shall provide a complete description of the asserted rights. The commercial license shall be attached to the Commercial Restrictions List for Government review. The offeror shall submit the Commercial Restrictions List as an annex to its Technical proposal volume, dated and signed by an official authorized to contractually obligate the offeror. If there is no information to be included in the Commercial Restrictions List, the offeror shall submit the list and enter "None" in the body of the list. If the offeror is awarded a contract, the Commercial Restrictions List shall be attached to the contract.

2.0 VOLUME 2: PAST PERFORMANCE

2.1 General Information

2.1.1 The offeror shall identify up to three (3) of the prime offeror’s most relevant government or commercial past performance contracts, and up to two (2) of the most relevant government or commercial past performance contracts for each principal subcontractor.

2.1.2 An offeror will not receive past performance credit for a proposed principal subcontractor unless the offeror’s proposal demonstrates how the resources of that principal subcontractor – its workforce, management, facilities or other resources – will in fact be provided to perform at least 20% of the proposed total price of the estimated contract ceiling, excluding the prime offeror’s profit. Merely stating that the offeror has access to the resources of a principal subcontractor is insufficient.

2.1.3 The government will not consider past performance references performed by an individual joint venturer or partner unless the joint venturer or partner meets the definition of “principal subcontractor.”

2.1.4 Any submitted past performance contract must contain performance within five (5) years of the proposal due date specified in Block 9 of Standard Form 33 of the RFP. Performance that took place greater than five years from the proposal due date will not be considered.

2.1.5 Forward a copy of the Past Performance Questionnaire attached to this RFP to the past performance contract customer’s Program Manager and/or Point of Contact - with a copy to the Contract Specialist - for the following past performance contracts:

a. Past performance contracts that do not have CPARS Reports

b. Past performance contracts with CPARS Reports completed by the Assessing Official more than six months prior to the RFP’s proposal due date.

2.1.6 All questionnaires shall be forwarded within 14 calendar days from the RFP release date, with a copy forwarded to the Contract Specialist. The offeror shall include instructions for its customers to send completed questionnaires within two weeks of the customer’s receipt of the questionnaire to Mr. Jason Harvey, Contract Specialist, via email at Jason.G.Harvey@navy.mil.

2.1.7 The offeror should provide written consent from its principal subcontractor that will allow the government to coordinate any of those entities’ past performance issues with the offeror. If the offeror does not submit such written consent, then the government will address any past performance issues directly with the principal subcontractor, and the offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractor that does not provide such written consent, provide a point of contact name, address, phone number, fax number, and email address with whom the government may coordinate past performance issues.

2.1.8 To evaluate past performance, the government may use information other than information provided by the offeror in its proposal, and may use past performance information obtained from sources other than those identified by the offeror.

2.1.9 The offeror has the burden of providing thorough and complete past performance information. It is incumbent upon the offeror to explain the relevance of data provided in its proposal. The government has no duty to search for additional data to cure problems the government finds in the information provided by the offeror.

2.1.10 Regardless of relevancy, the offeror shall provide a list of Show Cause Notices, Cure Notices and Terminations for Default received on any contract, task order, or delivery order within the past 5 years.

2.2 Past Performance Contract Information

2.2.1 Provide the information identified below in an MS Word Table for each past performance contract identified.

1 Place of Performance should be the location of the government or contractor’s facility where the predominance of the work was performed.

2 Provide the CAGE Code and DUNS Number of the company performing the work. If the CAGE Code or DUNS Number is different than the past performance entity proposed to perform the solicitation’s effort, please explain the reason.

3 As part of its Past Performance Volume, the offeror shall provide printed CPARS that are referenced in the table.

2.2.2 Task or delivery orders awarded under Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance evaluation. Thus, offerors may not propose an entire MAC as a past performance contract reference.

2.2.3 For a single-award indefinite delivery past performance contract, offerors may propose the entire basic contract as a past performance reference, or may propose a specific task or delivery order as a past performance reference. If an offeror proposes an entire single-award indefinite delivery contract as a past performance reference, however, the offeror must provide the past performance information below for each and every task or delivery order issued.

2.3 Past Performance Relevancy Information Required For Each Contract

2.3.1 Contract Types: Compare the contract type of the past performance contract to the contract type of this solicitation’s effort.

2.3.2 Total Dollar Amounts: Compare the total dollar amount of the past performance contract to the total proposed dollar amount of this solicitation’s effort.

2.3.3 Dollar Amounts Actually Performed: Compare the dollar amount of the effort actually performed by the offeror or principal team member under the past performance contract to the dollar amount of the effort proposed to be performed by the offeror or principal team member under this solicitation’s effort.

2.3.4 Locations and Divisions: Compare the location and division of the company that performed the past performance contract effort to the location and division of the company that is proposed to perform this solicitation’s effort.

2.3.5 Period of Performances: Compare the period of performance of the past performance contract to the period of performance actually performed under that past performance contract for the offeror or principal team member.

2.3.6 Compare Similarities: Compare the similarity of the product or service actually performed by the offeror or principal team member under the past performance contract to the product or service proposed to be performed by the offeror or principal team member under this solicitation’s effort in the following areas:

a. Scope

b. Magnitude

c. Complexity

2.3.7 Requirement Documents: For each past performance contract reference submitted, the offeror's Past Performance Volume shall include a copy of the Statement of Work, Performance Work Statement, and/or Performance Specification for that past performance contract reference to aid the government in its relevancy assessment for that past performance contract reference.

2.4 Demonstrated Past Performance Required For Each Contract

2.4.1 For each past performance contract, the offeror shall provide available CPARS and Past Performance Questionnaires that address the following demonstrated past performance areas:

a. Quality of Product or Service. The offeror’s past performance in the delivery of quality supplies and services, which includes meeting technical requirements.

b. Schedule. The offeror’s past performance in meeting schedule requirements, to include on-time or late deliveries, modifications of original schedules.

c. Cost Control. The offeror’s past performance in controlling contract costs, to include the cost of performance, cost overruns, and cost underruns.

d. Program Management and Subcontract Management. The offeror’s past performance in managing the contracted effort, to include program management, subcontract management, and cooperation with the customer.

2.4.2 The government will use CPARS and Past Performance Questionnaires to document demonstrated past performance. The government does not want to receive, and will not use for evaluation, an offeror’s self-described assertions of demonstrated past performance. For the CPARS and Past Performance Questionnaires provided, however, explain the reasons for any past performance problems, as well as schedule slips and cost or price increases from the schedule and cost or price at time of award. Also describe any claims or requests for equitable adjustment.

2.4.3 For any past performance problem identified in the CPARS or Past Performance Questionnaires, describe the status of the problem. If the problem is likely to happen again, describe the impact that the offeror’s implemented improvement effort had on resolving the problem so that it would not happen again. Describe the resolution used to correct the past performance problem and, if applicable, how the offeror proposes to use that resolution for this solicitation’s effort.

3.0 VOLUME 3: PRICE PROPOSAL

3.1 Volume Content

3.1.1 Attachment L-1 shall be provided both in printed format and a digital data copy in MS Office 2000 Excel format on CD-ROM media. Spreadsheets shall not be protected.

3.1.2 All price and price supporting information shall be contained in Attachment L-1 and the price proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

3.2 Ground Rules and Assumptions:

3.2.1 As this is a competitive acquisition with adequate price competition anticipated, any price documentation requested shall not be certified cost or pricing data in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the offeror and subcontractors and may conduct negotiations with the offeror, pursuant to FAR 15.403-4, in order to ensure a reasonable and realistic price/cost. Further, the offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

3.3 Price Information

3.3.1 The offeror shall explain any appearance of unbalanced pricing in the proposal.

3.3.2 The offeror shall identify the proposed prices for each CLIN as specified in the Delivery Order 0001 CLIN Pricing and the System Pricing tabs of attachment L-1 of this solicitation.

i. System pricing (menu pricing) will be incorporated in Section B of the contract at time of contract award

3.3.3 Offeror shall provide the following:

i. Signed SF33 for basic solicitation and each amendment

ii. Signed Representations, Certifications and Acknowledgements or System for Award Management (SAM) reference

iii. Affirmation via a a one-page Volume 4 stating no Exceptions, Deviations or Waivers if Volume 4 is not being submitted as part of the proposal

iv. Name, title, phone number and e-mail address of the offeror's principal point of contact for the solicitation

v. Identify those individuals authorized to negotiate with the Government and contractually bind the offeror

vi. The TIN, DUNS and CAGE code

vii. The mailing address, telephone, fax numbers, and facility codes for the offeror's local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office

viii. Provide a statement that the proposal shall remain valid for a period of at least six (6) months from the designated closing date indicated for receipt of proposals in the request for proposal (RFP)

ix. Identify the Joint Certification Program (JCP) certification number that corresponds to the CAGE code of the offeror to include all principal team members

4.0 VOLUME 4– EXCEPTIONS, DEVIATIONS AND WAIVERS:

In this Volume, the offeror must certify that it contains all exceptions, deviations, and waivers that the offeror takes from the provisions of the solicitation and its applicable documents. An “exception” is where an offeror states it will not comply with a requirement, usually involving contract terms and conditions. A “deviation” is where an offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement, usually involving a specification. A “waiver” is where an offeror requests authorization for the Government to accept an item, which will depart from specified requirements, but would nevertheless be considered suitable. Exceptions, deviations, and requests for waivers may cause proposals to be considered deficient.

Provide a detailed description for each exception, deviation, or request for waiver, as applicable. The offeror shall indicate the offeror’s difficulty with the applicable requirement and the offeror’s proposed solution. The offeror shall specifically identify the portion of the solicitation and the offeror’s proposal which are affected. If there are no exceptions, deviations, or waivers, the offeror shall provide a one-page Volume 4 stating so.

(End of Summary of Changes) image1.wmf