N00024-16-R-6414_Amendment_0002.pdf

N0002416NR55045

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. Revise Attachment 2 - GFI List to remove the SRMS P-SPEC; and

2. Extend the date for acceptance of bidder questions to February 2, 2017.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 25

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

16C. DATE SIGNED

BY 19-Jan-2017

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 N00024-16-R-6414

X 9B. DATED (SEE ITEM 11)

28-Dec-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

19-Jan-2017

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-16-R-6414

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J – LIST OF ATTACHMENTS

Document Type Description Pages Date Attachment 1 CIS Statement Of Work (SOW) 27 10 June 2016 Attachment 2 Unclassified Government Furnished

Information (GFI) List 2 19 January 2017

Attachment 3 Classified GFI List 1 30 November 2016 Attachment 4 Contract Security Classification

Specification, DD Form 254 4 23 June 2016

Attachment 5 Quality Assurance Surveillance Plan

(QASP)

8 10 June 2016

Attachment 6 Classified Material Request Form 1 10 June 2016 Attachment 7 Past Performance Questionnaire 6 10 June 2016 Attachment 8 Bidders Question Submittal Form 1 10 June 2016 Attachment 9 CIS Performance Specification TO BE SUBMITTED UNDER

SEPARATE COVER

Exhibit A DD Form 1423 CDRLs 32 14 June 2016 Attachment 1 to Exhibit A CDRL Glossary and Distribution List 7 10 June 2016

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

Section L - Instructions, Conditions and Notices to Bidders

1.0 ADDITIONAL INSTRUCTIONS AND CONDITIONS AND NOTICES TO OFFERORS

1. 1 GENERAL

The Offeror shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award. The Offeror’s proposal shall be based on the requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section J).

Comprehensive responses to this RFP are required to enable the Government to evaluate the Offeror’s full understanding of the requirements and proposed approaches to accomplish the stated requirements. Accordingly, the

Offeror shall submit all information required by this RFP. Offerors are advised that information submitted in excess of that required herein will not be evaluated.

The solicitation will be made available only through the internet at:

http://www.fbo.gov

Offerors are hereby notified that from time to time, the Government may post additional information to the web site relating to this solicitation (e.g. responses to questions, amendments). It is the Offeror’s responsibility to check the web site for any such information.

The performance of this contract requires that the Offeror have a SECRET facility clearance granted by a Military Department. Any firm lacking the requisite security clearance and intending to respond to this procurement shall, within ten (10) calendar days of issuance of this RFP, request initiation of such clearance action, in writing, from the Naval Sea Systems Command, Code: SEA 00P3, 1333 Isaac Hull Avenue SE Stop 1020, Washington, DC 20376- 1020. Appropriate clearance action in accordance with established procedures will be initiated by the Naval Sea Systems Command, but the Naval Sea Systems Command does not represent that such action can be completed and clearance granted prior to contract award.

Proposals in response to this solicitation shall be valid for a period of two hundred and ten (210) calendar days from the date specified for receipt of proposals.

1.2 QUESTIONS

Offerors may electronically submit written questions requesting clarification of solicitation requirements by sending an email to the Procuring Contracting Officer (PCO) Cherissa Tamayori, cherissa.tamayori@navy.mil and the PCO Representative Corinthia Price, corinthia.a.price@navy.mil . All questions shall be completed on the Bidder’s Question Submittal Form (Attachment 8) of the RFP and received in writing by 2 February 2017 to allow the Navy adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals.

Only questions transmitted electronically will receive a response. The Navy will continue to accept questions up to the closing date and time of the solicitation; however, time may not permit responses to be issued prior to proposal receipt. Answers to questions will be posted on the Federal Business Opportunities (FBO) website. No classified Bidders questions shall be submitted for this RFP.

1.3 START DATE

In order to allow for procurement lead time and a fair and equal evaluation of all proposals submitted under this competitive procurement, all proposals shall be based on a contract start date 31 August 2017. This date is only an estimate of the anticipated contract start date and will be used for the purpose of proposal evaluation only. The Government reserves the right to award sooner or later if necessary and will adjust the period of performance as necessary.

2.0 SOLICITATION RESPONSE REQUIREMENTS

NOTE: THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL THAT DOES

NOT COMPLY WITH THESE PROPSOAL PREPARATION/SUBMISSION INSTRUCTIONS.

2.1 PROPOSAL FORMAT & GENERAL INFORMATION

The following general information applies to proposal preparation:

The Offeror need not repeat information within the same volume required in the response to two or more proposal requirements. Such information shall be presented in detail in one area of the volume where it contributes most critically to the discussion. In other areas where discussion of the same information is necessary, the Offeror shall refer to the initial discussion and identify its location within the proposal volume.

General statements such as “the Offeror understands the method for performing the Systems Engineering efforts (or any portion thereof) and can or will comply with the requirements of the solicitation” will be considered inadequate, as will generic statements such as "straight forward engineering techniques" and the "highest quality control procedures.”

The Offeror’s proposal must contain a precise description of all terms and conditions of the services offered and must address all topics described below. The information provided in the proposal shall appear in the same order as outlined herein.

The Offeror’s shall ensure consistency, defined as “free from variation,” between the Technical and Cost/Price proposals. During the course of evaluating the proposals, the Contracting Officer will validate that the Technical proposals is consistent with the Cost/Price proposal. Specifically, the costs proposed will be evaluated and verified using historical and current market information to confirm proposed costs are within reason and consistent with the technical approach. Any inconsistencies may be viewed as weaknesses and/or risks in the proposals, and the Offeror may, at the Government’s discretion, be considered unacceptable and eliminated from the competition for award.

The Contracting Officer reserves the right to request such additional information regarding scheduling, manpower, facilities and management organization and capabilities as may be necessary to determine the Offeror’s qualifications for award of a contract, to determine the relative merit of the Offeror’s proposal, or to otherwise clarify any aspect of the proposal. If such communications are deemed to be warranted by the Contracting Officer, they will be addressed through discussions.

Offerors shall note that if awarded a contract based upon this solicitation, the Offeror’s Technical Proposal or portion thereof may be incorporated into the contract by reference.

Offerors are required to submit proposals that are sufficiently detailed and complete in order to fully demonstrate understanding of, and compliance with, all of the requirements of the RFP and shall contain only material directly related to this acquisition.

Each Offeror is responsible for the condition of its delivered proposal. Binders and their contents that are broken apart or received in a disorderly fashion will be reassembled by the Government in a manner with expeditiousness as the rule. The Government is not responsible for proper reassembly of these binders. Thus binders may not be reassembled as originally sent.

In the event that any portion of the proposal is written by anyone who is not a bona fide employee of the firm submitting the proposal, a certificate to this effect shall be furnished which must be signed by an authorized official of the Offeror and shall indicate the person’s name, employment capacity, firm name, relationship of that firm to the Offeror, and which portion of the proposal was written by that person.

2.2 PROPOSAL FORMAT

In order to maximize efficiency and minimize the time for proposal evaluation, all Offerors shall submit their proposals in accordance with the format and content specified. The electronic proposal shall be prepared so that if printed, the proposal meets the following format requirements:

The text of the proposal shall be printed on double sided 8.5 x 11 inch paper. Type size shall be 12-point Times New Roman Font or equivalent. Text shall be single-spaced with margins of at least one inch on all sides. Foldouts shall be used only where needed, e.g., engineering drawings, diagrams, and schematics. Foldout pages up to 11 x 17 inches may be used for diagrams, charts or graphic material with type size of minimum 8-point font. Each foldout shall contain printed material on only one side of the foldout. Foldout pages shall fold entirely within the particular volume.

All documents shall be provided in Microsoft Office (can be submitted in any version compatible with Office 2010) applications (Word, Excel, PowerPoint) or word searchable Adobe, with the file extension .doc, .docx, .xls, .xlsx, .ppt, .pptx or .pdf. More specific file-type guidance is provided below for specific portions of the proposal.

All supporting Cost Data shall be provided in Microsoft Excel software, with all files named with the file extension .xls or .xlsx. All cells containing derived data shall be presented together with the formulas used to derive the data.

This is only for evaluation purposes. Narratives related to cost/price summary data may be provided in Microsoft Word.

The electronic proposal material shall not contain any information not contained in the hard copy format. In the event of disparities between hardcopies and electronic information, the hardcopy governs. Disks shall be CD- Read Only Memory (ROM) formatted and all documents, spreadsheets, databases, or other data submitted must be compatible with Microsoft Office 2010, Microsoft Project 2010, and Adobe Acrobat 9. The information contained within the CDs shall not be locked such that formulas are able to be viewed. Original documents Excel, or equivalent shall be the actual workable documents, and not scanned Portable Document Format (PDFs). All Microsoft Excel files shall be completely readable and editable, as to ascertain the validity of the pricing or other data contained therein. All Adobe Acrobat files shall be word-searchable.

A legible, neat, orderly and comprehensive proposal is required. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids beyond those sufficient to present a complete and comprehensive proposal are neither necessary nor desirable. This may be construed as an indication of a lack of understanding or cost consciousness. Offerors shall follow the general rule that quality of information is significantly more important than quantity or visual esthetics of presentation. Do not elaborate unnecessarily or provide other presentations beyond that sufficient to present a complete and effective proposal.

Compression tools are limited to PKZip or WinZip.

Subcontractor data submitted directly to the Government in support of the prime Offeror’s cost proposal shall follow the format described above. Subcontractor submittals shall prominently identify the prime Offeror.

NOTE: Instructions regarding use of certain electronic products (e.g., Microsoft Office, Excel, Adobe) listed herein shall not be construed as Government endorsement of specified products.

2.2.1 PAGE NUMBERING

The Offeror shall use a standard page numbering system to facilitate proposal references. Pages are to be numbered sequentially and tabs are to be used for chapter breaks. Charts, graphs and other insert materials shall be page-numbered as part of the page numbering system. Proposals that restart page numbering every chapter within an individual volume will not be acceptable. Any pages intended to be blank shall be marked, "Intentionally Left Blank." Every page, except those marked as blank, will be numbered.

Each page shall be labeled with the Offeror’s name, the RFP number, and the proposal disclosure position in accordance with FAR 52.215-1. A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.

All volumes shall be submitted in three-ring binders with index tabs or tabbed index divider pages indicating sections which correspond to those set forth above.

In addition to the paper copies, the Offeror shall provide Volumes I, II and III on separate CD-ROMs in the format described above. If a classified supplement is included it shall be provided separately with the appropriate security classification markings and following guidance for classified information. Each disk shall be labeled as follows:

Solicitation Number Volume # Offeror Company Name, City, State Offeror POC Offeror POC Phone #

2.3 PAGE LIMITATIONS

Page limitations are identified for each volume of the proposal, as described in Table 1.0 below and will be treated as maximums. If the proposal exceeds the page limit, the Government will remove all pages exceeding the specified page count from the back of the proposal prior to the evaluation and will not review these pages. When both sides of a sheet display printed material, it shall be counted as two (2) pages. Graphs, charts, and tables are included in the page count. There should be no more than (6) foldouts included in the proposal. Each foldout will count as one page for page count purposes.

The RFP response shall be provided in three (3) separate Volumes, delivered by 2:00PM eastern daylight time on 28 February 2017.

Table 1.0 – Proposal Page Limitations

VOLUME TITLE PAGE LIMIT ORIGINALS COPIES CD ROMS

I Technical Proposal 60 1 4 4 II Past Performance NONE 1 4 2 III Cost/Price Proposal NONE 1 4 3

Each volume shall be bound separately and shall not exceed the page limitation cited above.

The following are not included in the page limitations:

a. Title/Cover pages/Cover Letter

b. Table of contents

c. Glossaries of abbreviations and acronyms

d. Letters of intent for key personnel or subcontractors/consultants

e. Proposal Cross-Reference Tables

f. Software Development Plan

g. Labor Category Definitions

Any other content that is excluded from the page count will be addressed in the section for that particular volume.

2.4 TABLE OF CONTENTS, TITLE PAGE, PROPOSAL CROSS-REFERENCE TABLE

Table of Contents – Provide a Table of Contents in sufficient detail so that the important proposal elements can be easily located. The use of tabs and dividers is encouraged.

Title Page – The proposal Title Page(s) will include the following information and shall identify original document with authorizing signatures and copies:

Proposal Title Proposal Category (Technical or Cost) Volume Number Security Classification (Unclassified Only) RFP Number Name and Address of the Offeror

Proposal Cross-Referencing – Provide all pertinent information in sufficient detail to permit evaluation of the proposal. Cross referencing is permitted where its use would conserve space without impairing clarity. However, each response within a given volume of the proposal shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with minimal cross referencing. Where cross referencing is necessary, the Offeror shall provide a Proposal Cross Referencing Table that cites the required proposal content and the specific page number, section or paragraph where this content appears in the proposal.

2.5 GLOSSARY OF ABBREVIATIONS AND ACRONYMNS

Each volume shall contain a glossary which includes all abbreviations, acronyms and their corresponding definitions. Glossaries will not count against page limitations

2.6 COST AND PRICE INFORMATION

No cost or pricing information of any kind shall be included in any volume except Volume III, Cost/Price Proposal.

Offerors must submit all cost/price related documentation required for Volume III. Cost/price summary and back-up spreadsheets must be submitted in Microsoft Excel format. Note: In the event of any discrepancies between the Offeror’s proposal, either hard copy or electronic, and the Section B pricing, the highest number will be used during the cost realism analysis.

2.7 FILE NAMING CONVENTIONS

All files must be submitted in the following formats:

Cost_Company Name_Document Name_Vol# (or Attachment Number) Example: Cost_NAVSEA_Cost Narrative_Vol III Example: Cost_NAVSEA_Cost Summary_Attachment 1

Technical_Company Name_Document Name_Vol# Example. Technical_NAVSEA_Technical Capability_Vol I

Past Performance_Company Name_Document Name/Attachment #_Volume# Example: Past Performance_NAVSEA_Previous Contracting Efforts_Volume II The proposal shall be limited to the following submission and pages:

2.8 FORMAT OF ELECTRONIC SUBMISSION (CD ROMs)

The CDs for Volumes I and II, contents shall not be in a "read only" format or in scanned PDF format. For Volume III, any spreadsheets shall be "unlinked" to allow for review during cost/price analysis on all of the CDs. The pricing spreadsheets generated must replicate the format of Figure 1 in section L 4.3.2.1 and Figure 2 in section 4.3.2.2. All cells containing derived data shall be presented together with the formulas used to derive the data. This is only for evaluation purposes.

In the event that situations arise which necessitate the submission of revised information, to include pricing, technical, or other items, the revisions shall adhere to same instructions of Section L. Additionally, any spreadsheets, word processing documents, or other information shall be submitted in a working document form to permit the validation of submitted information. The electronic version shall not contain spreadsheet or word processing documents that have been changed, printed, and then scanned to a PDF or other file that cannot be readily used to verify the accuracy of pricing or other information.

CD ROMs, as required above, shall be attached to the proposal such that they do not fall out or become dislodged during transport and handling.

2.9 ELECTRONIC TECHNICAL INFORMATION CENTER (E-TIC)

The Navy has established an Electronic Technical Information Center (E-TIC) to serve as the repository for unclassified technical information related to the CIS Program. In order to gain access to the unclassified E-TIC, prospective Offerors must have a valid PKI certificate and be able to supply their Joint Certification Program (JCP) Certification JCP #________. If the Offeror has a valid PKI certificate, access to the E-TIC is gained as follows:

First fill out an AIMTC Account Request form at the following link:

https://aimtc.nuwc.navy.mil

The following fields must be completed as follows: the ‘branch’ or ‘Code’ you support is PMS425, the ‘Navy Sponsor POC’ is Angel Jaeger the ‘Navy Sponsor Code’ is PMS 425, the ‘justification for your need to know’ is Prospective Offeror for the PMS425 CIS Competition and check CIS E-TIC as the area for which you have a ‘need to know.’ When the request form is complete, hit the send button at the bottom of the page and you will be notified that the request is being processed. An AIMTC User Account Information email will follow that provides you E- TIC login and password information. Companies/individuals will be authorized access to these repositories on a “need-to-know and appropriate security clearance” basis.

Companies/individuals who are interested in receiving the classified reading material for the RFP on the topic of CIS must submit a Classified Material Request Form, RFP Attachment J-6 to the Naval Sea Systems Command Security POCs, Angel Jaeger at email angel.jaeger@navy.mil and Glenda Leon at email glenda.leon@navy.mil.

The written request must include data on the company facility and specific individual(s) requiring access as follows:

facility security clearance level, issuing Government agency, and expiration date; facility security office phone/fax numbers; facility storage level, cage code, and complete destination address’ personnel for whom access to classified data is requested to include full name; security clearance level, issuing Government agency, and expiration date; date of birth; and city/state of birth.

Access to this information will only be granted to those Offerors who can demonstrate that they meet the security requirements of this solicitation. The Government will mail a classified CD/DVD to the Offeror within five (5) business days following approval of “need-to-know” and security clearance verification. Access to these materials will be granted solely for the purpose of preparing a proposal in response to this solicitation and does not establish a common “need-to-know” with any other program, contract, or effort. Only one copy of the classified CD/DVD will be distributed per Offeror.

3.0 CONTENTS OF THE OFFER

Offerors are required to submit proposals that are sufficiently detailed and complete in order to fully demonstrate understanding of, and compliance with, all of the requirements of the RFP, and shall contain only material directly related to this acquisition. All claimed technical, management, performance and schedule capabilities shall be realistic and are subject to evaluation by the Government. Offerors must respond to all requirements of the solicitation document. The Government will evaluate each Offeror's understanding of the Government's requirements and ability to perform the work on the basis of its proposal. Offerors shall provide information and documentation in detail to clearly identify its overall qualifications. The Offeror shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award. The Offeror’s proposal shall be based on the requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section J). Certain sections of this solicitation require the Offeror to provide information and fill-ins. Offerors should review the solicitation carefully and insert relevant data wherever required.

The offer consists of and must include the following to be eligible for award:

Volume I – Technical Proposal Volume II – Past Performance Volume III – Cost/Price Proposal

Offerors are required to submit their proposal is in separate parts as follows:

Cover Letter identify the following:

Solicitation number;

The name, address, electronic-mail (e-mail) address, telephone number, Cage Code, DUNS Number and Tax Identification Number (TIN) of the Offeror;

A statement that the Offeror agrees to all terms, conditions and requirements included in the solicitation and all amendments. There shall be no pricing information in the cover letter.

A statement that the proposal is valid through 210 calendar days from the date specified in the receipt of proposals;

DCAA and DCMA office points of contact, including branch location, DODAAC, contact name, telephone number and e-mail address;

Names, titles, telephone numbers and e-mail addresses of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this solicitation;

Name, title and signature of a person authorized to sign the proposal;

Identify all enclosures being transmitted as part of its proposal; and The status of the Offeror’s accounting system, CAS disclosure system, purchasing system, and provide supporting documentation (e.g., DCMA letter confirming adequacy of accounting system).

Original plus 1 copy of the signed solicitation document with the following:

RFP Sections A through J, “Solicitation, Offer and Award” with all fill-ins completed.

RFP Section K, “Representation, Certifications and Other Statements of Offerors,” completed by the Offeror. Items which are not applicable should be marked “N/A”.

Small Business Subcontracting Plan. The Offeror’s attention is directed to Section I clauses FAR 52.219-9 entitled Small Business Subcontracting Plan, DFARS 252.219-7003 entitled “Small Business Subcontracting Plan (DoD Contracts)” and FAR 52.219-16 entitled “Liquidated Damages – Small Business Subcontracting Plan”. As prescribed in FAR 19.708, Offerors other than small business concerns shall submit a subcontracting plan and that plan, once approved, shall be made part of any contract resulting from this solicitation. The Offeror’s Small Business Subcontracting Plan will be incorporated into the contract by reference. NOTE: The Small Business Subcontracting Plan is separate from the Small Business Participation Factor.

Volume I – Technical Proposal – Include all data and information required for evaluation as set forth in the solicitation. Cost/Price information shall be completely omitted from the Technical Proposal Volume.

Volume II – Past Performance – Include all data and information required for evaluation as set forth in the solicitation.

Volume III – Cost/Price Proposal – Include all data and information required for evaluation as set forth in the solicitation.

4.0 PROPOSAL ORGANIZATION

4.1 VOLUME I – TECHNICAL PROPOSAL

Cost/Price information shall be completely omitted from the Technical Proposal Volume.

The Technical Proposal Volume shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal meets the requirements of the RFP. To this end, the Technical Proposal Volume shall be specific, detailed, and complete so as to clearly demonstrate to the Government that the Offeror has a comprehension of and capabilities to perform all aspects of the solicitation requirements.

Proposals shall include the block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. The technical section must be sufficient to show how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed.

The following is an outline of the information required to be addressed in the Technical Volume I and shall be addressed in the following order:

Page No. Description i Title Page ii Table Of Contents iii List Of Figures iv List Of Tables v List Of Appendices vi Glossary Of Abbreviations And Acronyms

(The items above do not count against the Technical Proposal Page limitation)

1.0 Introduction

1.0.1 Subfactor Summary

1.1 Subfactor (1): Technical Capability and Corporate Experience

1.1.1 (Sample Task 1) Design - Capability Improvements (CI)

1.1.2 (Sample Task 2) Design - Integration and Test for Advanced Processor Building (APB) Transition

1.1.3 (Sample Task 3) Design – Architecture

1.1.4 Rights in Technical Data (TD) and Computer Software

1.1.5 Software Development

1.2 Subfactor (2): Personnel

1.2.1 Staffing Plan

1.2.2 Key Personnel Resumes

1.2.3 Labor Category Definitions and Qualifications

1.3 Subfactor (3): Management

1.3.1 Subcontractor Management Plan

1.3.2 Configuration Management

1.3.3 Integrated Master Schedule (IMS)

1.3.4 Facilities

1.3.5 Transition Plan

1.3.6 Small Business Participation

4.1.1 INTRODUCTION

The Offeror shall provide a detailed approach to handle the Sample Tasks in sections 4.1.2.1, 4.1.2.2 and 4.1.2.3) demonstrating its understanding of the issue(s) presented, the requirements for completion, the types of personnel required (e.g. labor categories), the processes followed and the facilities required to complete the Sample Tasks. The Offeror shall identify necessary Applicable Documents and GFI and the Offeror’s plan to effectively incorporate these into the performance of the Sample Tasks. Note that Applicable Documents and GFI will be provided for proposal purposes and Offerors shall determine the need of the Applicable Documents and GFI based on the requirements in the solicitation. In addition, the Offeror shall demonstrate an understanding and identification of all potential risks as well as appropriate mitigation plans for the Sample Tasks.

LABOR CATEGORY DEFINITIONS AND QUALIFICATIONS (Does NOT count toward page limit)

The Offeror shall submit a description of each labor category it proposes (e.g. Engineer, Analyst) and any amplifying qualifications to differentiate within categories (e.g. Engineer I, Engineer II, Project Engineer, and Systems Engineer). The Offeror shall provide either excerpts from its Position Description Manual, or details of its qualifications for Labor Categories. Each description should not exceed ½ page in length, but should be sufficient to provide the Offeror and subcontractor criteria used to determine each individual’s eligibility.

4.1.2 SUBFACTOR (1): TECHNICAL CAPABILITY AND CORPORATE EXPERIENCE

The Offeror shall provide a concise but comprehensive narrative description of the design, development, test, integration, delivery and support approach being proposed. Provide a brief summary of the key features of this technical approach. Offerors shall provide Basis of Estimate (BOE) and labor mix for sample tasks identified below.

4.1.2.1 DESIGN– CAPABILITY IMPROVEMENTS (SAMPLE TASK 1)

A new CIS Capability Improvement (CI) item has been identified which intended to be introduced with TI18/APB17 centered on providing Common Recording functionality throughout SWFTS. Common Recording is intended to provide SoS access to a consolidated set of tape and optical drives that SWFTS systems can use to record stored data to Tape or Disc. The Offeror shall provide an approach to fully design, integrate, test and deliver this new CI within 12 months. The approach shall include as a minimum:

A Top level description, IMS and summary including diagram(s) detailing how Common Recording will be integrated into CIS and interfaces impacted Approach for requirements derivation/ definition Processes that will be utilized Analysis of SWFTS impacts and design features that minimize the impact Analyses tools that might be employed Activities and tools planned to formally track progress Approach to source new/existing components (Open Source, COTS, GOTS, NDI, etc.)

Methods to be used to ensure modularity of each CI to allow changes in subsequent baselines with minimal impact to the CIS.

Identify how the design contributes to minimizing ILS impacts

4.1.2.2 DESIGN – INTEGRATION ANDTEST FOR ADVANCED PROCESSOR BUILD (APB)

TRANSITION (SAMPLE TASK 2)

PEO IWS-5A will develop APB19 in coordination with PMS 401, PMS 425, PMS 435, PEO SUB-S and other organizations for delivery on the TI-18 SWFTS hardware configuration. The Offeror shall provide their technical approach, required resources, and management strategy to transition APB19 onto TI18. The approach shall include as a minimum:

A Top level description, IMS and summary including diagram(s) A plan to participate in and become an integral part of the APB process including working groups, IPTs, and milestone reviews to support the APB Step process.

Process to apply lessons learned from APB Development and Integration, Steps Three and Four, and Return on Investment (ROI) events Approach to managing resources to support the APB while simultaneously executing TI18 APB17 production efforts Approach to developing and integrating capability/maintainability improvements that do not get delivered as part of the APB process.

Processes that will be utilized Requirements Traceability and Analysis of SWFTS impacts Activities and tools planned to formally track progress Methods to validate software provided via to CIS and adjudicate issues that are identified Approach for subsystem and SWFTS/platform level Integration and Formal Test including measurement of system performance Approach for Delivery and fielding support

4.1.2.3 DESIGN - ARCHITECTURE (SAMPLE TASK 3)

A new CIS Capability Improvement (CI), targeted for introduction in TI20/APB19, has been identified which will be centered on providing a Common Computing Environment (CCE) that will provide application hosting services for SWFTS. The introduction of this CI will require a CIS architecture and software environment that is capable of seamlessly integrating and running virtual appliances delivered from a host of third party organizations in a common environment. The associated hardware suite must provide sufficient resources to support components, some of which are Mission Critical and/or Ship Safety / Self Protect (SS/SP) items, residing in the CCE. The Offeror shall provide an approach to fully design, integrate, test and deliver this new CI for TI20/APB19. The approach shall include as a minimum:

A Top level description, IMS and summary including diagram(s) detailing how the CIs will be integrated into CIS, interfaces impacted and resulting architecture Approach to ensure CIS uses a modular design Approach to design in reliability and ensure the design provides for graceful degradation Approach to using modern virtualization and related technologies Approach for requirements derivation/ definition with a focus on critical and SS/SP Processes that will be utilized Analysis of SWFTS impacts Analyses tools that might be employed Activities and tools planned to formally track progress Approach to source the new/existing components (Open Source, COTS, GOTS, NDI, etc.)

Methods to validate software provided to CIS and adjudicate issues that are identified Approach for delivery and fielding support Methods to be used to ensure hardware independence

4.1.2.4 RIGHTS IN TECHNICAL DATA AND COMPUTER SOFTWARE

The Government desires at least Government Purpose Rights (GPR) in all Data (Data includes Technical Data, Computer Software and Computer Software Documentation as defined in DFARS 252.227-7013 “Rights in Technical Data---Noncommercial Items” and/or DFARS 252.227-7014 “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation” as applicable) used or generated or delivered in performance of this contract. The Government desires at least GPR in all Data provided under CLIN 0003.

4.1.2.5 SOFTWARE DEVELOPMENT

The Offeror shall develop a Software Development Plan that meets the software development requirements of the solicitation with regards to the Software and Firmware requirements of CIS in accordance with the following clauses: HQ L-2-0016 SOFTWARE DEVELOPMENT PLAN and HQ L-2-0017 SOFTWARE DEVELOPMENT

AND CMMI OR EQUIVALENT EXPERIENCE.

4.1.3 SUBFACTOR (2): PERSONNEL

4.1.3.1 STAFFING PLAN AND KEY PERSONNEL

Note: There is a 2-page limit constraint in this section – the technical approach section is confined to a total of 60 pages)

The Offeror shall provide a Staffing Plan matrix/spreadsheet/table that supports the requirements specified in this RFP. The Staffing Plan shall clearly identify all proposed Key Personnel with an asterisk (*), identify all personnel assigned to the resulting contract, and identify all proposed labor categories with labor category definition (including subcontractor personnel, if used). To be considered “Key”, an employee must be dedicated to this contract at least fifty (50%) percent of the time. The Offeror shall include a chart showing personnel loading by skill category over time for this program (without including cost/price data in this Volume). Using MS Excel, Offerors shall provide a complete staffing, by task area, of all proposed labor categories, and all personnel supporting each of the task areas specified in the SOW. The Offeror shall provide their Staffing Plan as a separate document in Microsoft Excel in a format of the Offerors choice.

The Staffing Plan shall contain the following information.

· Individual's Name

· Employer (employee's company name)

· Company Labor Category (Company Proposing)

· Government category employee satisfies: Junior, Mid, or Senior

· Task Area(s) to Support

· Organizational Chart

· Key Personnel (Identify with an asterisk (*))

· · Years of related professional experience

· Number of labor hours proposed for each base and option year

· Percent (%) of total time dedicated to contract

· Highest educational degree obtained

· Degree area

· If no degree, relevant certificates attained

· Security Clearance level

In the event the Offeror has not identified a firm candidate for a proposed task area, include the word “pending” in lieu of an individual’s name. Offerors should attempt to minimize the number of proposed labor personnel for which candidates have not been identified. From an evaluation perspective, proposal risk in terms of “Technical Capability” and “Cost Realism” would be expected to increase when candidates have not been identified for proposed task area positions.

The Staffing Plan shall be limited to two (2) pages and submitted as part of Volume I.

4.1.3.2 KEY PERSONNEL RESUMES

Note: Resumes are limited to 2 pages each – Does not count toward page limitation for the technical approach section)

Cost/Price information shall be completely omitted from the Technical Proposal Volume.

Provide a resume for each proposed key personnel.

All key personnel shall have a minimum of five (5) years of experience in their respective field demonstrating specific capability, knowledge, and relevant experience for contract(s) of similar scope and complexity. The Offeror’s Key Personnel narratives shall demonstrate the individual’s depth of experience and qualifications to perform the scope of work required.

Provide a letter of intent signed by all proposed Key Personnel of the Offeror and proposed major subcontractors indicating their willingness to be hired or relocated if the contract is awarded to the Offeror. Major subcontractors are defined as subcontracts of $750,000 or more per year, or 10% or greater of the total contract price, whichever is less.

The Offeror’s proposal shall include the following statement signed and dated by both the employee and a company official:

“We attest to the accuracy of the information contained herein and that an agreement has been reached regarding salary, position and work commitment to this project”.

In the event that an Offeror has not identified a firm candidate for a proposed key personnel position, said position shall be addressed within the Staffing Plan identified with the word “Pending” in lieu of an individual’s name. All other (non-individual specific) information is still required.

The Offeror shall identity the Key Personnel who have an active Secret Clearance and the expiration date or provide documentary evidence of how the individual will support the requirement (e.g., work agreements and contracts). At a minimum, all Key Personnel and the Program Manager must have a Secret Clearance.

The data contained in the key personnel resumes shall not conflict with the information provided in the staffing plan, the technical proposal, the data provided in the Cost/Price proposal or the Work Breakdown Schedule (WBS). Any inconsistencies may be viewed as weaknesses and/or risks in the proposals, and the Offeror may, at the Government’s discretion, be considered unacceptable and eliminated from the competition for award.

Offers in response to this RFP shall minimize the number of proposed Key Personnel positions for which candidates have not been identified. Risk assessment in the evaluation, as it relates to “Technical Approach” and “Cost/Price”, would be expected to increase when firm candidates have not been identified for Key Personnel positions, and when signed offer letters have not been provided for contingent hires.

4.1.4 SUBFACTOR (3): MANAGEMENT

The management proposal shall define how the Offeror will manage the work required by this RFP including all attachments. It shall describe the proposed approach to management, planning, organizing, executing and controlling the development of CIS, as well as the facilities planned for designing, engineering, integration, and testing.

4.1.4.1 SUBCONTRACT MANAGEMENT

The Offeror shall discuss the management of subcontractors to ensure their products are delivered on time and within budget, and are of sufficient quality to enable the Offeror to meet all contractual requirements. The Offeror shall provide a matrix designating subcontractor assignments. The Offeror shall discuss its approach toward subcontracting and its relationship toward achieving the overall objectives of the resultant contract. Discussion shall include contractual arrangements, qualification requirements, selection process(es), including the process that verifies that subcontractors’ products meet the Offeror’s flow down requirements, contingency plans, identification of any proprietary processes and materials, quality assurance, software interfaces, and management interactions. If applicable, the Offeror shall discuss its approach for managing how design information from one subcontractor’s design influences another subcontractor’s design and include this in the matrix designating subcontractor assignments.

4.1.4.2 CONFIGURATION MANAGEMENT (CM)

The Offeror shall describe the process that will be utilized to identify configuration items, maintain configuration control, conduct functional and physical configuration audits, as appropriate, and maintain configuration status accounting. The Offeror shall describe the process that will be utilized for maintaining formal configuration control for all Computer Software Configuration Items (CSCIs), and methods for change management control from contract award through Government acceptance of all required CIS deliveries.

4.1.4.3 INTEGRATED MASTER SCHEDULE (IMS)

The Offeror shall provide a TI-18/APB-17 based IMS, in accordance with the Contract Work Breakdown Structure (CWBS) that at a minimum addresses the start date, duration, end date, predecessor and successor relations for the Post Award Conference (PAC), Integrated Baseline Review (IBR), Preliminary Design Review (PDR), Critical Design Review (CDR) or Incremental Design Review (IDR), and Delivery Readiness Review (DRR) for the TI- 18/APB-17 product. The Offeror shall also include Test Readiness Reviews (TRR), software tests, integration tests and delivery of all Contract Data Requirements Lists (CDRLs) consistent with the Contractor’s design, development and test approach. The IMS shall cover the period from contract award through Government acceptance (DRR) of the TI-18/APB-17 product.

4.1.4.4 FACILITIES

The proposal shall demonstrate that the Offeror has adequate design, development, testing, and manufacturing capability and capacity for successful performance of all described requirements of the SOW, including system and engineering support facilities and manufacturing facilities. The Offeror must describe and discuss the facilities in the context of specific plans for the resultant contract, including facility clearance information and status.

The Offeror’s proposal shall:

Describe its facilities for the physical inspection and storage of incoming materials and vendor supplied items;

production, fabrication, and assembly; performing critical processes and procedures; and development, production test and inspection.

Describe the simulations and stimulations to be incorporated into the test facility and the method of accreditation of each.

Describe the layout of space, provide a diagram of its facilities for this specific program, and assure the availability of the facilities to meet the Government’s requirements.

State whether the facilities are leased or owned; if leased, the Offeror must provide copies of all pertinent lease(s).

The lease(s) documents shall not be included in the overall Volume I proposal page limitation of the solicitation.

Describe any use of Government facilities (e.g., Naval Undersea Warfare Center (NUWC)). Include any plans for use, space requirements, timing/schedule requirements, and GFE/COTS equipment requirement needs. State whether the Offeror has contacted the Government facilities for plans to use, point of contact at the facility and when such contact was made.

The Offeror shall identify any use of facilities, in addition to those identified above, required to fully execute the effort associated with this RFP including the plan for use, effort to coordinate the effort, and support provided at the locations(s).

4.1.4.5 TRANSITION PLAN

The Offeror shall provide a transition plan that defines how the Offeror will be performing the requirements of the SOW within sixty (60) days after contract award. The transition plan shall address how the Offeror shall begin execution of SOW requirements within this sixty (60) day window. This shall include assumptions, dependencies on the Government, schedule, facility start-up, staffing, technical requirements, training, and documentation requirements. In addition, the Offeror shall include establishment of a software development and test site.

The Offeror shall include detailed labor hours broken out to functional WBS elements and material estimates (including detailed Basis of Estimates) to support the transition plan.

4.1.4.6 SMALL BUSINESS PARTICIPATION

The Offeror shall provide sufficient detail to permit a complete evaluation. This factor applies to every Offeror regardless of size status or location of working facilities or headquarters.

(a) Small Businesses as it relates to this provision include the following:

Small Business Concerns Small Disadvantaged Business Concerns (including Historically Black Colleges and Universities and Minority Institutions) Women-Owned Small Business Concerns HUBZone Small Business Concerns Veteran-Owned Small Business Concerns Service-Disabled Veteran-Owned Small Business Concerns

(b) The North American Industry Classification System (NAICS) code applicable to the requirements contained within this solicitation is 334511 and the Size Standard is 1,250 employees. The size standard certified to by the Subcontractor is valid for the duration of the contract. All Offerors who are themselves U.S. small business concerns based on the NAICS code assigned to this requirement, are to identify the extent to which U.S. small business concerns will be utilized as first–tier subcontractors in the performance of this proposed contract. U.S.

small business concerns are defined in (1) FAR 19.001 and (2) by the criteria and size standards in FAR 19.102 for the applicable NAICS code.

(c) Offerors shall propose a Small Business Participation percentage for this contract.