N00024-18-R-6407-A0003.pdf

N0002418NR98157

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 0003 is to: 1) Under Section L, update font requirements for diagrams, f igures and tables.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 25

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

16C. DATE SIGNED

BY 31-Aug-2018

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002418R6407

X 9B. DATED (SEE ITEM 11)

12-Jul-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing Items 8 and 15, and returning 5 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

31-Aug-2018

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:

N0002418R6407

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SOLICITATION INSTRUCTIONS

Section L – Instructions to Bidders

1.0 GENERAL INFORMATION

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 website 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 9917, 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 three hundred and sixty-five (365) calendar days from the proposal due date of 14 September 2018.

Pursuant to FAR 52.215-1, the Government intends to award a contract based on initial proposals without conducting discussions with Offerors, but reserves the right to conduct discussions in accordance with FAR 15.306 if determined by the Government to be necessary. Therefore, the Offeror’s proposal submissions shall contain the

Offeror’s best terms from a cost/price and technical standpoint. Each Offeror shall submit only one proposal which represents its best approach to meeting the requirements of the solicitation. No alternative proposals will be accepted. The proposal submissions will have requirements for originals (paper), hardcopy (paper) and ‘Electronic

Media’ (CD-ROM), as detailed in subsequent paragraphs.

In the event that any portion of the proposal is written by anyone who is not an employee of the firm submitting the proposal, a certificate to this effect shall be included with the proposal. The certificate must be signed by an authorized official of the Offeror, and shall indicate the non-employee 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.

1.1 QUESTIONS

Offerors may electronically submit written questions requesting clarification of solicitation requirements by sending an email to the Procuring Contracting Officer (PCO) Peter Richmond (peter.richmond@navy.mil ) and Contract

Specialist Patrick Dooley (patrick.s.dooley@navy.mil). All questions shall be written on the RFP Question

Submittal Form (Attachment 5) of the RFP and received in writing within fourteen (14) calendar days after release of the RFP to allow the Navy adequate time to respond prior to the date and time set for receipt of proposals. Only questions transmitted electronically will receive a response. Each question must include the document name, http://www.fbo.gov/ mailto:peter.richmond@navy.mil document date, specific page number, specific paragraph number, clause number or other definitive citation requiring clarification. No classified Bidders questions shall be submitted for this RFP. Questions will not result in an extension to the proposal due date.

It is the Government’s intention that questions and responses will be posted on the Federal Business Opportunities

(FBO) website via RFP amendment(s). Answers will not be provided directly to potential Offerors. All business sensitive and proprietary information must be clearly marked. Properly marked business sensitive or proprietary information will not be posted on FBO. 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.

2.0 PROPOSAL CONTENT

The following general information applies to proposal preparation and delivery.

Although NAVSEA will make the RFP and amendments available electronically on the INTERNET, proposals in response to this RFP WILL NOT be accepted via electronic transmission. Only hard-copy (including specified

Electronic Media copies) proposals submitted in accordance with Section L of this RFP will be accepted. Any proposals received via electronic transmission will be deleted, and will not be reviewed or considered. If an Offeror is awarded a contract based on this solicitation, the Offeror’s Technical Proposal or portions thereof may be incorporated into the contract by reference.

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

Table 1.0 - Proposal Content

VOLUME TITLE FACTORS

Volume I Technical Proposal Factor (1): Technical Capability

Factor (2): Rights in Technical Data and Computer Software

Factor (3): Personnel

Factor (4): Management

Volume II Cost/Price Proposal Factor (5): Cost/Price Proposal

Volume III Past Performance and Small

Business Subcontracting Plan

Factor (6): Past Performance

Factor (7): Small Business

Subcontracting Plan

Volume IV Supplemental Information

For each volume, the number of copies required and the page limits are shown in the table below:

Table 2.0 – Proposal Page Limitations

VOLUME TITLE PAGE LIMIT ORIGINALS COPIES CD ROMS

I Technical Proposal 250 1 5 2

II Cost/Price Proposal Unlimited 1 5 2

III Past Performance and

**Small Business

Subcontracting Plan

50 1 3 2

IV Supplemental Information 100 1 3 2

** Small Business Subcontracting Plan – will not be counted toward the page limit for Volume III

2.1 PROPOSAL FORMAT AND DELIVERY INFORMATION

SUBMISSION OF PROPOSALS: The proposal shall be provided in four (4) separate volumes, delivered by

2:00PM Eastern Daylight Time on 14 September 2018.

All Offerors shall submit their proposals in accordance with the format and content specified. 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 interpreted by the Government to be an indication that the Offeror lacks a complete understanding of the requirement. Quality of information is generally 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.

The electronic media (CD-ROM) version of the proposal shall be prepared so that if printed, the proposal meets the following format requirements:

Hard Copy Proposals

The text of the proposal shall be printed on double sided 8.5 x 11 inch paper. Type size shall be no smaller than 12-point Times New Roman Font. Text shall be single-spaced with margins of at least one inch on all sides.

Attachments (i.e. Attachment 7), diagrams, figures and tables type size shall be no smaller than 8-point font.

Foldouts shall be used only where needed, e.g., engineering drawings, diagrams, schedules and schematics. There should be no more than (10) foldouts included in the proposal. 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. Each 11 x 17 foldout counts as two (2) pages and shall be marked accordingly.

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.

Format of Electronic Media

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. Within the CD-ROMs for Volumes I, II, III, and IV, contents shall not be in a scanned PDF format. Additionally, for

Volume II, spreadsheets (i.e. xls, .xlsx), shall be "unlinked" to allow for review during cost/price analysis on all of the CD-ROMs. Cost/price summary and back-up information must be submitted by populating Attachment 8, Supporting Cost Data Workbooks, Parts A and B, which are in Microsoft Excel format. All cells containing derived data shall be presented together with the formulas used to derive the data.

Narratives related to cost/price summary data may be provided in Microsoft Word. 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 the same instructions as 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.

The electronic media (CD-ROM) 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. All

Microsoft Excel files shall contain all formulas and 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. Compression tools are limited to PKZip or WinZip.

Each disk shall be labeled as follows:

Solicitation #

Volume #

Offeror Company Name, City, State

Offeror POC

Offeror POC Phone #

File Naming Conventions

All files must be submitted in the following formats:

Technical_Company Name_Document Name_Vol#

Example: Technical_NAVSEA_Technical Capability_Vol I

Cost_Company Name_Document Name_Vol# (or Attachment Number)

Example: Cost_NAVSEA_Cost Narrative_Vol II

Example: Cost_NAVSEA_Supporting Cost Data Workbook_Attachment 8_Part A

Past Performance_Company Name_Document Name/Attachment #_Volume#

Example: Past Performance_NAVSEA_Previous Contracting Efforts_Volume III

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.

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, shall be numbered.

Each page of the proposal shall be labeled with the Offeror’s name, the RFP number, the proposal disclosure position in accordance with FAR 52.215-1, and the date of the initial proposal. Any pages that are 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.

2.2 PAGE LIMITATIONS

Page limitations are identified for each volume of the proposal, as described in Table 2.0 above and will be treated as maximums. If the proposal exceeds the page limit, the Government will remove all pages exceeding the specified page count, and those page will not be evaluated. 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.

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

E. Proposal Cross-Reference Tables

F. Labor Category Definitions

G. Data Rights Assertion List (Section J, Attachment 6)

H. Software Development Plan

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

2.3 TABLE OF CONTENTS, TITLE PAGE, AND PROPOSAL CROSS-REFERENCE TABLE

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

Title Page

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

1. Proposal Title

2. Proposal Category

3. Volume Number

4. Security Classification (Unclassified Only)

5. RFP Number

6. Name and Address of the Offeror

Proposal Cross-Referencing

Provide all pertinent information in sufficient detail to permit evaluation of the proposal. Each 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. Cross referencing is permitted where its use would conserve space without impairing clarity. 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.

Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary which includes all abbreviations, acronyms and their corresponding definitions. Glossaries will not count against page limitations. All acronyms should be spelled out at first usage.

2.4 COST AND PRICE INFORMATION

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

Offerors must submit all cost/price related documentation required for Volume II. Cost/price summary and back-up information must be submitted by populating Attachment 8, Supporting Cost Data Workbooks, Parts A and B, which are in Microsoft Excel format. Note: In the event of any discrepancies between the Offeror’s proposal (either hard copy or electronic media) and the Section B pricing, the highest number will be used to determine the

Government Total Evaluated Cost/Price.

2.5 ELECTRONIC TECHNICAL INFORMATION CENTER (E-TIC) AND SOURCE CODE

REQUESTS

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

Fill out an AIMTC Account Request form at the following link:

https://aimtc.nuwc.navy.mil/aimtcmanagement/request.asp

The following fields must be completed as follows: the ‘Branch or Code you support’ is “PMS425,” the ‘NUWC or other Gov’t Sponsor POC’ is “Jay Kirschenbaum,” the ‘NUWC or other Gov’t Sponsor CODE’ is “PMS 425,” the

‘Brief description of your role supporting the DoD (Justification for your “need to know”)’ is “Prospective Offeror for the PMS425 TCS Competition.” At ‘Use the drop down menu below to select the categories for which you have a "need to know,”’ click the down arrow on ‘E-TIC (Electronic Technical Information Center)’ and check “Tactical

Control System ETIC.” 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, providing 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.

TI14/APB15 Source Code (Attachemnt 2, GFI Item 46) will be provided separately by electronic media only to

Offerors who send an E-mail request to Jay.kirschenbaum@navy.mil, patrick.s.dooley@navy.mil and

Susan.cadieux@navy.mil. This request must include the mailing address of the Offeror, and justification for need to know (Prospective Offeror for the PMS425 TCS Competition). Within 15 days after the solicitation closes, the

Offeror shall return the original source code CD-ROM to the PCO and provide a statement certifying that any copies have been destroyed.

3.0 CONTENTS OF THE OFFER

Offerors are required to submit proposals that are so specific, detailed and complete as to clearly demonstrate the

Offeror has a thorough comprehension of the total technical requirements, including compliance with System

Specifications, the Statement of Work (SOW), and all other requirements contained in the solicitation, and shall contain only material directly related to this acquisition. 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.

Offerors shall submit all information required by this RFP, including those documents, exhibits, and other attachments to the RFP identified in Section J. Offerors shall provide information and documentation in detail to clearly identify their overall qualifications. Certain sections of this solicitation require the Offeror to provide information and fill-ins. Offerors should review the solicitation carefully and insert relevant data where required.

Offerors should assume the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror's proposals. Data previously submitted, or presumed to be known (e.g., data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless physically incorporated into the proposal. The Government does not assume the duty to search for data to cure problems it finds in proposals.

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. All claimed technical, management, performance, and schedule capabilities shall be realistic and are subject to evaluation by the Government. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award.

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

Cover Letter identifying the following:

https://aimtc.nuwc.navy.mil/aimtcmanagement/request.asp mailto:Jay.kirschenbaum@navy.mil mailto:patrick.s.dooley@navy.mil mailto:Susan.cadieux@navy.mil

A. Solicitation number;

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

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

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

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

F. Names, titles, telephone numbers and e-mail addresses of persons authorized to negotiate with the

Government on the Offeror’s behalf in connection with this solicitation;

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

H. Identify all enclosures being transmitted as part of its proposal; and

I. 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).

The signed originals and copies of the solicitation in accordance with Table 2.0 above should include the following:

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

B. RFP Section K, “Representation, Certifications and Other Statements of Offerors,” completed by the

Offeror. Items which are not applicable should be marked “N/A”.

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

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

E. Volume III – Past Performance and Small Business Subcontracting Plan – Include all data and information required for evaluation as set forth in the solicitation.

F. Volume IV – Glossary of Acronyms and Abbreviations, Resumes of Key Personnel, and Supplemental

Information Regarding the Offeror’s Labor Mix and Basis of Estimates for Labor for TCS and

AN/BYG-1Development, Integration, Testing and Delivery, and TCS Re-Architecture CLINs 0008, 0101, 0102, 0201, 0202, 0301, 0302, 0401, 0402, 0501, and 0502; Labor for Engineering and

Development and Legacy Support CLINs 0001, 0003, 0103, 0105, 0203, 0205, 0207, 0303, 0305, 0307, 0403, 0405, 0407, 0503, 0505, 0507, 0601, 0603, 0605, 0701, 0703, and 0705.

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 Government technical/engineering personnel to evaluate the Offeror’s technical approach to meet RFP requirements. The technical proposal must be specific, detailed and complete, clearly demonstrating that the Offeror has a comprehensive understanding of the requirement and the capability to perform all aspects of the solicitation requirements. The technical proposal must 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. Proposals may include block diagrams, flow diagrams, sketches, drawings, schematics and interface descriptions required to describe the Offeror's proposed concept.

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

Page No. Description i Title Page (No page limit) ii Table of Contents (No page limit) iii List of Figures (No page limit) iv List of Tables (No page limit) v List of Appendices (No page limit) vi Glossary of Abbreviations and Acronyms (No page limit)

The Technical Proposal Volume shall include all required information and explanations for Factors 1-4.

Factors 1-4 are outlined below:

1. Factor (1): Technical Capability

1.1 Sample Task 1- Individual Capability Item (CI) or Non Developmental Item (NDI)

Product Integration

1.2 Sample Task 2- Design/Integration & Test for Advanced Processor Build (APB)

1.3 Software Development and Software Development Plan

1.4 System Engineering

1.5 TCS Re-Architecture

1.6 Systems Engineering Management Plan (SEMP)

1.7 Software Architecture Description Document (SWAD)

2. Factor (2): Rights in Technical Data and Computer Software

3. Factor (3): Personnel

3.1 Staffing Plan

3.2 Key Personnel

4. Factor (4): Management

4.1 Configuration Management

4.2 Product Planning Chart (PPC)

4.3 Sample Task 3- Multiple Baseline Management

4.4 Facilities Management

4.1.1 FACTOR (1): TECHNICAL CAPABILITY

The Offeror shall provide a brief summary and a concise but comprehensive narrative description of its proposed technical approach to design, develop, test, integrate, deliver, and support all aspects of the requirements of the SOW.

The technical approach shall demonstrate a clear understanding of the SOW technical requirements and how the Offeror proposes to execute the approach, including the types of personnel required (i.e. labor categories), the processes followed, the facilities required, proposed GFI incorporation, and potential risks and proposed mitigation to the proposed technical approach. Utilization of the TI14/APB15 Source Code (Attachment 2, GFI Item 46) is not required and will not necessarily result in a more favorable rating.

Note: Offerors shall provide Labor Mix and Basis of Estimate (BOE) for CLINs 0001, 0003, 0008, 0101, 0102, 0103, 0105, 0201, 0202, 0203, 0205, 0207, 0301, 0302, 0303, 0305, 0307, 0401, 0402, 0403, 0405, 0407, 0501, 0502, 0503, 0505, 0507, 0601, 0603, 0605, 0701, 0703 and 0705 in Volume IV: Supplemental Information.

4.1.1.1 Sample Task 1- Individual Capability Item or Non-Developmental Item Product Integration

As part of the Integrated Warfare System (IWS)-5A STEP process for APB 19, a new Target Motion Analysis

(TMA) Tactical Aid application developed by a third party has been identified for integration into the TCS system as a

Non-developmental Item (NDI). The TMA Tactical Aid must be integrated seamlessly into TCS and will require access to sensor feeds, contact data and navigation data, as well as promulgate contacts to SWFTS and the Payload

Control System (PCS). The Offeror shall provide an approach to fully assess, design, integrate, test and deliver this new

Capability Item (CI) within twelve (12) months. The approach shall include at a minimum:

A. A Top level schedule of the task – a TI18/APB19 Project Planning Chart (PPC) and summary, diagram(s) detailing how the TCS TMA Tactical Aid will be integrated into TCS, and architecture impacts/considerations and interfaces impacted.

B. Approach for determining system requirements to ensure seamless integration into the TCS, including identification of all integration risk and proposed mitigation strategies.

C. Explanation of all processes to be utilized and stakeholders that will be engaged, including activities and tools planned to formally track progress.

D. Analysis of both TCS and SWFTS level impacts and design features that minimize these impacts.

E. Approach to identify new/existing components (Open Source, COTS, GOTS, NDI etc.) to support integration.

F. Proposed methods to ensure modularity of each CI to allow changes in subsequent baselines with minimal impact to the TCS.

G. Explanation of how the design contributes to minimizing ILS impacts and allows for more streamlined and flexible training.

H. Approach to meeting Cybersecurity requirements and sustainment.

4.1.1.2 Sample Task 2- Design/Integration & Test for Advanced Processor Build (APB)

PEO IWS-5A will develop the APB19 baseline 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 its technical approach, required resources, risk mitigation approach, and management strategy to transition APB19 onto TI18. The approach shall include at a minimum:

A. A TI18/APB19 Project Planning Chart (PPC) including details of the tasks needed to complete the integration effort.

B. A plan to participate in and become an integral part of the APB process including working groups, Integrated Product Teams (IPTs), and milestone reviews to support the APB Step Process.

C. A proposed process to apply lessons learned from APB Development and Integration, Steps Three and

Four, and Return on Investment (ROI) events.

D. Demonstration of an innovative approach to managing resources to support APB development and test while simultaneously executing TI18 APB19 production efforts.

E. Offeror's approach to developing and integrating capability and maintainability requirements that do not get delivered as part of the APB process.

F. Offeror's management of this task, including all processes utilized, requirements traceability, risk tracking and resolution, analysis of SWFTS impacts, activities and tools utilized to formally track progress, methods to validate software provided via TCS, methods to adjudicate any identified issues and the approach for delivery and fielding support.

G. Offeror's approach for subsystem and SWFTS/platform level Integration and Formal Test, including measurement of system performance.

H. Offeror's NDI Integration Strategy.

I. Offeror's approach to integrate other AN/BYG-1 subsystems (PCS, CIS, IA) into a coherent package for system delivery.

4.1.1.3 Software Development and Software Development Plan

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

DEVELOPMENT AND CMMI LEVEL 3 OR EQUIVALENT EXPERIENCE. Offerors shall also submit an SDP rationale as part of Volume I which describes why their specific approach is appropriate for the system to be procured, developed or maintained and how their proposed processes are equivalent to those articulated by

Capability Maturity Model Integration (CMMI®) capability level 3 at the division or site(s) where the work will be performed.

The SDP shall be provided as part of Volume I. The Offeror shall identify whether the SDP provided is already in effect as a standard company policy or procedure at the Offeror’s site. The Offeror shall identify what parts of the SDP constitute new methods or changes from existing software development practices at the proposed team’s site.

4.1.1.4 System Engineering

The Offeror shall develop a Systems Engineering Management Plan (SEMP) that meets the systems engineering and design requirements of the solicitation in accordance with Contract Data Requirements List

(CDRL) A008 and also demonstrates traceability to the processes and requirements identified in the AN/BYG-1

Submarine Combat and Weapon Control System Systems Engineering Plan (SEP), Attachment 2, GFI Item 18.

Offerors shall also submit a SEMP rationale as part of Volume I which describes why their specific approach is appropriate for the system to be procured, developed or maintained and how their proposal supports the

AN/BYG-1 Submarine Combat and Weapon Control System Systems Engineering Plan (SEP), Attachment 2, GFI

Item 18.

The SEMP shall be provided as part of Volume I. The SEMP shall be no longer than 25 pages, exclusive of title page and table of contents.

4.1.1.5 TCS Re-Architecture

The Offeror shall propose high-level design and provide the plans to support a new TCS architecture for future development. The Offeror shall describe the approach to ensuring the proposed architecture will adhere to

Modular Open System Architecture (MOSA) requirements including the use of modular design, standards-based interfaces and widely-supported consensus-based standards. The Offeror shall describe how the architecture will allow for rapid and affordable technology insertion and refresh to support integration of new capabilities, and have the flexibility to off-load functions to separate processors without major modifications to the system architecture.

The description shall address how components/modules from third-party providers and reuse sources will be incorporated.

The Offeror shall identify the proposed schedule to develop and demonstrate the new architecture to the

Navy for implementation in TI20/APB21. The Offeror shall identify any concerns, challenges, risks, and dependencies with the proposed approach, design, or schedule impacts, as well as proposed mitigations to all identified risks.

The Offeror shall include a Software Architecture Description (SWAD) Document that meets the requirements of Appendix F of the SOW as part of Volume I. The SWAD shall be no longer than 25 pages, exclusive of the title page and table of contents.

4.1.2 FACTOR (2): RIGHTS IN TECHNICAL DATA AND COMPUTER SOFTWARE

The Offeror shall describe its approach to offer data rights for the work required by this solicitation. The

Offeror shall describe in detail the proposed rights to all Technical Data (TD) and Computer Software/Computer

Software documentation (CS/CSD) for all hardware, software, and interfaces to be developed under this contract.

Price information shall be completely omitted from the Data Rights section.

It is the Government’s intent that all non-commercial TD and CS/CSD developed or delivered under this contract be delivered with Government Purpose Rights (GPR) (as defined in DFARS 252.227-7013 (FEB 2014) and

DFARS 252.227-7014 (FEB 2014)) or better.. If the Offeror proposes to deliver commercial TD/CS/CSD, it is the

Government’s desire to obtain a license to the commercial TD/CS/CSD that would grant the Government the equivalent of GPR. The Data Rights offered (7017 list, 7028 list, and/or Supplemental Information—

Noncommercial TD, Noncommercial CS, Noncommercial CSD) shall be provided as attachments to Volume I and will become Attachment 6 to the Contract.

The Offeror shall describe the degree to which the proposal meets the Government’s desired level of rights in

TD, CS, and CSD. The Offeror shall describe how the proposed level of rights enables the Government to adequately sustain the end item deliverables over their lifecycle including for maintenance, repair, and upgrade.

In the event an Offeror proposes to deliver any commercial or non-commercial TD/CS/CSD with less than such rights as desired by the Government, the Offeror shall explain the impact on the Government’s ability to use, modify, release, or disclose such TD, CS, or CSD. The Data Rights offered will be incorporated into the successful

Offeror’s contract upon award. The Offeror shall provide the following information as attachments to its offer:

A. Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD.

i. The 7017 List. The Offeror shall list all non-commercial TD, CS, and CSD that it asserts will be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7017“Identification and Assertion of Use, Release, or Disclosure

Restrictions” (JAN 2011) provision incorporated at Section K of this solicitation. If the Offeror does provide assertions, this paragraph shall also serve as the Contracting Officer’s request for Offeror submission of evidence and information to evaluate and validate listed assertions. Additionally, if there is no data or software 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 incorporated into the contract as

Attachment 6.

ii. The 7028 List. The Offeror shall list all noncommercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to noncommercial

TD, CS, or CSD that the Offeror has delivered to, or is obligated to deliver to, the Government under any contract or subcontract. Specific instructions and requirements concerning this list are set forth in the

DFARS 252.227-7028 “Technical Data or Computer Software Previously Delivered to the Government”

(Jun 1995) provision incorporated at Section K of this solicitation. Additionally, 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 incorporated into the contract as

Attachment 6.

iii. Supplemental Information. The Offeror shall include in its offer a statement, entitled

“Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of noncommercial

TD, CS, or CSD that the Offeror asserts should be delivered with specifically-negotiated license rights (as discussed at DFARS 252.227-7013 “Rights in Technical Data –Noncommercial Items” (FEB 2014) and/or

DFARS 252.227- 7014 “Rights in Noncommercial Computer Software and Noncommercial Computer

Software Documentation” (FEB 2014), sets forth a complete description of all such proposed restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD.

This information shall be provided by referencing and delivering any and all proposed license agreements that are attached to the statement. The Offeror shall submit the statement dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the statement, the Offeror need not submit the statement. If the Offeror is awarded a contract, any statement provided will be incorporated into the contract as Supplemental Information Attachment 6.

B. Rights in Commercial TD, Commercial CS, and Commercial CSD.

i. The Offeror shall attach to its offer a list, entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use

Restrictions” (the Commercial Restrictions List (CRL)), that the Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) intends to deliver with other than unlimited rights: (1) identification of the data or software; (2) basis for asserting restrictions; (3) asserted rights category; and (4) name of the person asserting restrictions. For any item designated as NDI, the Offeror is requested to provide details of the Agency and level therein that paid for development and the contract number(s) and dates wherein payments were received. For each entry in the list citing an asserted rights category other than the standard license rights applicable to commercial TD as set forth in the DFARS

252.227-7015 “Technical Data –Commercial Items” (FEB 2014) clause, the Offeror shall provide a complete description of the asserted rights (e.g., a specially negotiated license, or the license customarily offered to the public); this information may be provided by referencing any proposed nonstandard or commercial license agreement that is attached to the list, but in all cases, the non-standard or commercial license will be attached for Government review. The Offeror shall submit the Commercial Restrictions List as part of Attachment 6 to its offer, 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" as the body of the list. If the Offeror is awarded a contract, the Commercial

Restrictions List shall be attached to the contract.

C. Rights in Background Inventions.

i. The Offeror shall provide a list, entitled "Background Inventions—Identification and

Licensing" (the BIIL List in Attachment 6), identifying all inventions described in and covered by any patents or pending patent applications in which the Offeror (1) has any right, title, or interest; and (2) intends to include in any items, components, or processes (ICP) to be developed or delivered under the resulting contract, or that are described or disclosed in any technical data (TD), computer software (CS), or computer software documentation (CSD) to be developed or delivered under the resulting contract. Such inventions are hereafter referred to as "background inventions." The BIIL List shall be part of Attachment 6 to the resulting contract, and shall be updated by the Offeror as necessary to identify all background inventions.

4.1.3 FACTOR (3): PERSONNEL

4.1.3.1 Staffing Plan

LABOR CATEGORY DEFINITIONS AND QUALIFICATIONS

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 each Labor Category. 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.

The Offeror shall fill out and submit Attachment 7 – Staffing Matrix, as part of Volume I.

In the event the Offeror has not identified a firm candidate for a proposed task area, include the word

“pending” (applicable to non-key personnel only) 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.

Estimated Labor Mix Across Experience Level

The Offeror shall propose its allocation of personnel labor hours to meet the requirement. The

Government’s recommended percentage allocations of senior, mid-level, and junior personnel (to meet the

Government’s hours for Labor CLINs 0001, 0003, 0103, 0105, 0203, 0205, 0207, 0303, 0305, 0307, 0403, 0405, 0407, 0503, 0505, 0507, 0601, 0603, 0605, 0701, 0703, and 0705 shown in Section B) are listed in the table below.

The recommended mix is based on the complexity of the requirement and historical experience. The Offeror’s resulting labor category allocation shall include all proposed labor categories, including key personnel.

TABLE L-1 LOE CLINs

Labor Mix Across Experience Level

Senior Mid-Level Junior

Government Estimate of Labor

Mix (Optional - Offeror to

Propose)

25% 60% 15%

Government Defined

Years of Experience 15 Years or More 5 to 15 Years

1 to 5 Years or less

In the event that the proposed labor mix or allocation of personnel resources differs from Table L-1 in any category, the Offeror shall provide the rationale used to select the proposed labor mix or allocation that clearly demonstrates the ability to meet the requirements. Offerors are cautioned that any deviation from the ‘Labor Mix

Across Experience Level’ identified in Table L-1 without sufficient justification may be assessed as a weakness that increases the risk of unsuccessful performance.

4.1.3.2 Key Personnel

Note: Resumes are limited to two (2) pages each.

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

Offerors must provide a resume for each proposed key personnel in Volume IV: Supplemental Information.

All key personnel must demonstrate specific capability, knowledge, and relevant experience for contract(s) of similar scope and complexity.

Program Manager – Desired Qualifications:

Fifteen (15) years of experience, including project management for software intensive development programs with large scale integration to external interfaces Experience with risk management, mitigation strategies, schedule development, and systems engineering intensive projects Experience with process improvement and monitoring, including cost control and analysis

AN/BYG-1 Production Lead– Desired Qualifications:

Fifteen (15) years of experience in the delivery of production level software based systems including systems engineering, baseline/software configuration management processes, requirements development, test and validation and life cycle support

Chief Engineer– Desired Qualifications:

Fifteen (15) years of combined experience within the areas of Combat Systems, Systems architecture, technology evaluations, Systems Engineering and Software Engineering for software subsystem development and design

Lead technical efforts to evaluate system architecture, technology selection, and future system development to improve/exceed system performance IAW approve performance specification

Evaluate and monitor technical processes, support design integration, products and all testing

The qualifications listed in each individual proposed Key Personnel resume, not the specific individual, are the materially relevant aspects of the proposed Key Personnel partially forming the basis of award under 5252.237-

9106, Substitution of Personnel (SEP 1990). Therefore, even if a proposed Key individual becomes unavailable to the Offeror between proposal submission and award, the Government will evaluate and make its award decision based on the qualifications listed on the proposed resume(s), irrespective of whether or not the Offeror notifies the

Government that any specific individual has become unavailable. If the Government awards a contract under which a particular proposed Key individual has become unavailable between proposal submission and award, the

Government will use the qualifications listed on the corresponding proposed Key Personnel resume as the basis for replacing that individual under 5252.237-9106(b) during contract performance. That said, Offerors shall only propose Key Personnel resumes for individuals that, at the time of proposal submission, the Offeror has a good faith expectation of providing at award. Failure to provide the specific individuals proposed as Key Personnel may result in negative CPARS findings during contract performance.

If the Key Personnel are not current employees of the Offeror/subcontractor, provide a Letter of Intent signed by 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

$2,0000,000 or more per year, or 10% or greater of the total contract price, whichever is less. The Government considers the submission of Letters of Intent for proposed contingent Key Personnel to be material to the proposal since these Letters of Intent demonstrate the Offeror's ability to hire personnel with the qualifications bid at the salary proposed. Letters of Intent shall be included with the resumes in Volume IV: Supplemental Information, and 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.”

The Offeror shall identify the Key Personnel who have an active Secret Clearance and the expiration…