N00024-18-R-5200-0001.docx

N0002418R5200

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 15-Jun-2018 03:00 PM to 29-Jun-2018 03:00 PM.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

The following documents, exhibit, and other attachments form a part of this contract:

Exhibit A Supplement A1

TDP Option Selection Worksheet – Conceptual Level TDP

Exhibit A Supplement A2

TDP Option Selection Worksheet – Developmental Level TDP

Exhibit A Supplement A3

TDP Option Selection Worksheet – Production Level TDP

Exhibit A Supplement A4

TMCR_2-2A_090027000

Exhibit A Supplement A5

TMCR 2B 090055000

Exhibit A Supplement A6

OT-18-20036 Integrated Support Plan (ISP)

Exhibit A Supplement A8

CDRL Addressees List

Exhibit A Supplement A9

List of CDRL Data Items

Attachment 14

CEC Facility Support Equipment List

Attachment 15

Bidder’s Question Submittal Form

Attachment 16

Sample Problems

Attachment 17

Sample Cost Model

Attachment 18 eSLOC Definitions

Attachment 19

Contract-Wide Staffing Plan

Revision 1

Note: Version dates shown in the table correspond to the version of the document, exhibit or other attachment that forms a part of the conformed copy of this contract. The contract modification SPIINs shown in parentheses denote the most recent modification under which the attachment was updated or incorporated. The version dates for the documents, exhibits, or other attachments do not necessarily represent the effective date or signature date for the modification.

SOLICITATION NOTES:

· Attachments will be updated prior to contract award to incorporate administrative details (e.g., contract number) as necessary.

· Attachments 1, 12, 13, 14, and 16 will not be posted publicly on the GPE, but will be made available to prospective offerors that are cleared to access the Bidder’s Library for this solicitation. These controlled solicitation attachments are not subject to the Terms of Use Agreement governing the use of the Bidder’s Library materials.

· Attachments marked with an asterisk (*) next to the attachment number will be incorporated at contract award based on Offeror submission.

· Attachments 14 through 21 are included for the purposes of the solicitation only and will be removed from this table at contract award.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

1. GENERAL INFORMATION

Each Offerors is required to submit a proposal that is sufficiently detailed and complete to fully demonstrate an understanding of, and compliance with, all of the requirements of the solicitation. Proposals shall contain only material directly related to this acquisition. Offerors shall submit all information required by this solicitation. Offerors’ proposals shall be based on the requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Offerors shall submit a proposal encompassing all of the line items listed in Section B of this solicitation. FAILURE TO FOLLOW THE INSTRUCTIONS OR CONFORM TO ALL REQUIREMENTS OUTLINED IN THIS SOLICITATION MAY RESULT IN REJECTION OF THE OFFEROR’S PROPOSAL.

Proposals submitted in response to the solicitation must contain a complete description of all pertinent aspects of the effort proposed by the Offeror. Offerors shall not assume that previously submitted data or prior experience presumed to be known to the Government (e.g., previous projects performed for the Government) will be considered as part of the proposal.

General statements such as, “the Offeror understands,” “the Offeror can or will comply with the requirements,” “standard procedures will be used,” “well-known techniques will be used,” or statements which merely paraphrase the solicitation in whole or in part do not constitute compliance with the requirements for proposal content. 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 explicitly incorporated into the proposal. Discussions of each topic in the proposal shall exhibit continuity and logical progression.

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

0. GOVERNMENT-WIDE POINT OF ENTRY (GPE)

This solicitation will be made available only through the Internet on the Federal Business Opportunities (FBO) website (http://www.fbo.gov). From time to time, the Government may post additional information to the FBO website relating to this solicitation (e.g. responses to questions, solicitation amendments, etc.). It is the responsibility of prospective Offerors to monitor the FBO website for any such information.

0. COMMUNICATIONS WITH THE GOVERNMENT

Unless otherwise specified, the Naval Sea Systems Command Procuring Contracting Officer (PCO) and Contract Specialist (CS) are the sole Government points of contact for this acquisition.

Mr. Shawn Fu Procuring Contracting Officer shawn.fu@navy.mil

(202) 781-1087

Mr. Gary Braunstein Contract Specialist gary.braunstein@navy.mil

(202) 781-0942

0. AVAILABILITY OF ATTACHMENTS AND BIDDER’S LIBRARY

The Government will make available to Offerors a Bidder’s Library containing information to assist in the preparation of a proposal. The Bidder’s Library will also contain certain solicitation attachments that cannot be posted to the GPE. Documents in the Bidder’s Library may contain classified data and/or technical data whose export is restricted by the Arms Export Control Act (Title, U.S.C. Section 2751 et seq. or Executive Order 12470).

Follow the instructions detailed in Attachment 21 to request access to the controlled solicitation attachments and the bidder’s library. Offerors that previously executed a TOUA during the pre-solicitation phase for this solicitation must still submit a request via email to the PCO and CS for access to the controlled solicitation and Bidder’s Library, but need not resubmit the TOUA or DD Form 254.

The deadline to request access to the controlled solicitation documents and bidder’s library shall be the same as the deadline to submit bidder’s questions regarding this solicitation.

0. SUBMISSION OF QUESTIONS AND COMMENTS

Offerors shall submit written questions and comments related to this solicitation using the Bidder’s Question Submittal Form (Attachment 15) for this solicitation. For ease of Government review and to minimize response time, Offerors shall submit this form in the original file format. Do not convert the form to Portable Document Format (PDF). To ensure the Government understands the context of the question, Offerors shall detail the applicable document name, document date or version, page, paragraph, clause or other specific citation to which the question applies. Information contained in the Government’s responses to bidder’s question shall not supersede any information contained in the solicitation (including amendments). In the event of a discrepancy between a response to a bidder’s question and the content of the solicitation, the latter shall take precedence.

Offerors shall not submit comments, questions, or inquiries to any Government representative other than the PCO and CS identified in this section.

The Government intends to distribute bidder’s questions and associated responses via public posting to the Federal Business Opportunities website. However, any question or response that contains classified or controlled unclassified information will not be posted publicly, but rather will be posted in the bidder’s library or sent directly to those Offerors who have executed Terms of Use letter and meet the security requirements detailed herein.

In the event that a prospective Offeror wishes to submit a comment or question that the prospective Offeror believes addresses a subject that is specific or proprietary to the Offeror, then the Offeror shall mark the question accordingly on the submission form and provide justification to support its claim. If the Government concurs with this identification, the Government will respond only to that potential Offeror. If the Government does not concur with this identification, it will inform the submitting Offeror and will not provide any further response.

The Government will not entertain any proposed revisions to the terms and conditions contained in this solicitation submitted as part of Offerors’ proposals, including any attachment or exhibit referenced therein. Therefore, any offer that includes “redlines,” condition(s) of offer, or any other deviation from the requirements of the solicitation may be rejected by the Government. As such, Offerors shall submit in accordance with this section any questions or suggestions related to the terms and conditions of this solicitation prior to the deadline for questions.

The deadline for receipt of questions is 30 days after the date on which the original solicitation was issued (See Block 5 of the Standard Form 33). Any questions received after this date may not be answered prior to receipt of proposals.

3. UNCLASSIFIED QUESTIONS

Written unclassified questions related to this solicitation shall be submitted electronically as follows:

TO: PCO as listed above CC: CS as listed above SUBJECT LINE: N00024-18-R-5200 Question from (insert name of Offeror)

3. CLASSIFIED QUESTIONS

Questions concerning classified attachments shall be submitted in accordance with the DD Form 254 and the DoD 5220.22M NISPOM. Contact the PCO and CS for instructions on submitting classified questions related to this solicitation. Do not send classified questions or information directly to the PCO or CS.

0. SOLICITATION SECURITY CLASSIFICATION

This solicitation is unclassified, although some information provided in conjunction with this solicitation may be classified. All employees of the Offeror working on the classified portion of its proposal shall have active SECRET clearances. Offerors must provide a completed DD Form 254 in order to gain access to and handle classified materials. The completed form must have Block 10 e. (2) marked “yes” (Non-SCI Intel Information), if applicable.

Classified responses to this solicitation are allowed, but the Offeror shall provide all classified information in Volume VII (i.e., the Classified Annex) only and include appropriate references to the information where necessary. The use of coded pointers such as “c1”, “c2” or other means should be employed when feasible to keep the bulk of the proposal content unclassified and legible. It is the responsibility of the Offeror to ensure classified data handling does not impact successful delivery of the proposal within the prescribed due date. OFFERORS SHALL NOT PLACE ANY CLASSIFIED INFORMATION IN ANY PORTION OF ITS PROPOSAL OTHER THAN THE CLASSIFIED ANNEX (VOLUME VII).

Although Offerors need clearance at the SECRET level to work on a proposal in response to this solicitation, Offerors must meet all clearance requirements detailed in the DD Form 254, including TOP SECRET requirements, by the time of contract award.

0. AWARD WITHOUT DISCUSSIONS

Pursuant to the provision under this section entitled FAR 52.215-1, “Instructions to Offerors – Competitive Acquisition,” the Government intends to award a single contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions per FAR 15.306 “Exchanges with Offerors After Receipt of Proposals” if determined by the Contracting Officer to be necessary. Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and the submission of multiple proposals will result in rejection of the proposal. Therefore, each Offeror’s proposal submission shall contain the Offeror’s best terms from a price and technical standpoint. However, the Government may contact any, all, or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15. Upon the conclusion of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range.

1. GENERAL PROPOSAL INSTRUCTIONS

The completion and submission to the Government of an offer shall indicate the Offeror’s unconditional acceptance of the terms and conditions in the solicitation.

The Government encourages Offerors to contact the PCO and Contract Specialist via email to request an explanation of any aspect of these instructions.

Offerors shall take care to submit a legible, neat, orderly, concise and comprehensive proposal. 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 unnecessary. Clarity is essential. The use of brochures shall be minimized and if used will count against page limits.

1. PROPOSAL STRUCTURE, FORMAT, AND PAGE COUNTS

Offerors shall structure proposal submittals such that the required content is organized as follows:

Note 1: The total page limit will for this volume will vary depending on the number of subcontractors for which the Offeror must provide past performance information. The past performance narrative for the Offeror shall not exceed five (5) pages in length. The past performance narrative for applicable subcontractors shall not exceed two (2) pages in length for each subcontractor. Therefore, the page limit for this volume shall be (5 + 2x), where x represents the number of applicable subcontractors. For further details, see the instructions for Volume VI.

Note 2: The Classified Annex does not have its own page limit as the information contained in the volume is intended to represent classified material that cannot be included in an unclassified volume. As a result, information presented in the Classified Annex will count towards the page limit for the volume that the information supports. For example, if the Offeror submits the Classified Annex with 15 pages of Technical Approach information and 10 pages of Sample Problem information, then the page limits for Volumes II and III will be reduced by 15 pages and 10 pages, respectively.

Each Offeror shall submit paper hard copies and separate electronic copies on CD-ROM or DVD media in the quantities specified above. All copies must contain the same information and format as the original. See paragraph 3.0 and subparagraphs under this section for instructions regarding proposal content that must be submitted solely on electronic media and omitted from the paper versions of the volume, including the original and any copies thereof. Proposal content designated by this solicitation for electronic submission only (e.g., Integrated Master Schedule, Contract-wide Staffing Plan, etc.) does not count against the solicitation page limits.

In presenting material in these volumes, Offerors are advised that the quality of information is significantly more important than quantity. In this respect, the page limitation must be strictly observed. Pages in excess of the applicable page limit shall not be read or evaluated and will be removed by the PCO from the back of the respective volume prior to evaluation. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Offerors shall organize proposal content sections using index pages or tabbed index divider pages with clear cross-referencing to the table of contents. All pages shall be consecutively numbered within each volume (e.g., 1,2,3,…), with the exception of the Cost/Price Volume. For the Cost/Price Volume only, pages must be numbered consecutively within each section, but page numbering may restart at the beginning of each section.

Paragraph 3.0 of this section identifies specific items that will be exempt from the page count limitations set forth above. In addition, the following proposal content will be exempt from the page count limitations:

· Cover letter

· Table of contents

· Title pages

· Index pages

· Tabs

· Glossary

1. BINDING, LABELING, AND PACKING

Offerors shall pack and submit all proposal binders in cardboard (or equivalent) boxes that may lifted and handled manually. Offerors should observe a reasonable maximum weight for each box and avoid overloading any single box. The boxes must be sequentially numbered with the box numbers marked on all sides of each box, and written on all sides of the outside wrapper, if necessary. Box 1 must include all copies of electronic media and a master packing list. The master packing list must list the contents (i.e., volume number, copy number, and volume name) of each box, by box number. CD-ROM/DVD media shall be secured to the proposals in a manner that prevents the media from falling out or becoming dislodged during transport and handling. These packing instructions also apply to all subcontractor submissions.

Offerors shall submit all volumes in three-ring binders with index tabs or tabbed index divider pages separating each section. Each proposal section shall start on a new page. Each volume shall contain a table of contents that lists the sections, subsections, and page numbers. Each volume shall also include a glossary explaining all abbreviations and acronyms used.

Offerors are responsible for the condition of delivered proposals. 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 such binders. Thus, binders may not be reassembled as originally sent.

The first page of each proposal volume shall display the information required by FAR 52.215-1(c)(2) and shall also contain the volume number, volume title, security classification level of the volume and serial/copy number. If an Offeror wishes to restrict the disclosure or use of its proposals, the Offeror shall use the legend permitted by FAR 52.215-1(e) and prominently indicate the specific pages and paragraphs that contain proprietary information. Each page of an Offeror’s proposals shall be labeled with the Offeror’s name, solicitation number and date corresponding to the date of the proposal.

All information relating to contract cost or pricing data shall be included only in the section of the proposal designated as the Cost/Price Proposal Volume. UNDER NO CIRCUMSTANCES SHALL OFFERORS INCLUDE CONTRACT COST AND PRICING DATA IN VOLUMES I THROUGH VII. In the event that cost and pricing data are included in Volumes I through VII, that data will be excluded from the evaluation.

Classified information shall be classified no higher than SECRET and bound in a red binder if SECRET or blue binder if CONFIDENTIAL. Do not bind unclassified volumes in a red or blue binder. Classification markings shall conform to the requirements of the DD Form 254 and the DoD 5220.22M NISPOM.

1. ELECTRONIC VERSIONS OF PROPOSALS

Unless otherwise stated in this solicitation, Offerors shall ensure that electronic versions of proposals do not contain any substantive information not included in the paper versions. In the event of a discrepancy between the paper version and electronic version of a proposal, the electronic version will govern. Electronic proposal submissions and supporting information shall be submitted on CD-ROM or DVD media in a format that can be accessed using a standard PC-compatible CD-ROM/DVD drive. The Government will not accept submissions on any other electronic media, such as flash memory cards or USB flash drives. All files submitted to the Government shall be compatible with Microsoft Office 2010. A duplicate set of all proposal files in PDF format may be submitted only as a supplement to the Microsoft Office format files. All viewgraphs shall be submitted in Microsoft PowerPoint format. All spreadsheets shall be submitted in Microsoft Excel format with all mathematical equation used for calculations visible and traceable. All text and proposal narrative shall be submitted in Microsoft Word format. All schedules shall be submitted in Microsoft Project format. No fields or documents may be password protected. Offerors shall not embed sound or video files into the electronic files. All Microsoft Excel files shall be completely readable and editable such that the Government may readily ascertain the validity of the pricing or other data contained therein. All data and tables shall be submitted in a printable format. All Adobe Acrobat files shall be word-searchable.

Each CD-ROM/DVD shall be labeled with the solicitation number, proposal volume number and title, the Offeror’s name, date of submittal, security classification level, serial/copy number, any restrictive marking permitted by the FAR (See FAR Part 15), and “Source Selection Information – See FAR 2.101 and 3.104.” The Offeror shall also submit a hardcopy directory listing with each CD-ROM/DVD submitted.

If classified information will be provided, the classified information shall be provided on separate CD-ROMs/DVDs, marked to the highest classification level required. All unclassified CD-ROMs/DVDs shall be marked “Unclassified.” Separate files shall be used to enable rapid retrieval of all contents, including exhibits, appendices, and attachments, if any. Each volume shall be organized into directories within the CD-ROM/DVD that duplicate the volumes and partitions used in the paper version of the proposal. Prior to submittal, the Offeror shall screen all CD-ROMs/DVDs to ensure that the media does not contain computer viruses or other malware.

1. PAGE SIZE AND FORMAT

The narrative material in each proposal shall be single-spaced, typed, or printed in 12-point Times New Roman font. Paper, excluding foldouts, shall be 8 1/2 × 11 inches (standard letter size) with a minimum margin of 1 inch around the page. Text within tables, diagrams, pictorial charts, or graphic material may use no smaller than 8-point font in Times New Roman or Arial typeface.

Every section, figure, and table shall be numbered; paragraphs within sections do not need to be numbered.

Proposal material shall be presented on double-sided pages only and in a single column on each page in accordance with FAR 52.204-4. Each double-sided page counts as 2 pages.

Foldout sheets may be used for charts and graphs where necessary to depict organization, layout, or implementation schedules. Foldouts shall be uncomplicated to preserve clarity. Extensive written text or tabular data, beyond that reasonably required for clarity, shall not be included in the material presented on the foldout sheet. Foldout pages shall fold entirely within the volume and shall not exceed 11 × 17 inches. Each non-blank side of a foldout page will count as two (2) pages for page count purposes. Foldouts for the entire proposal are limited to a total of 25 foldout sheets. Foldout sheets contained in the Cost/Price Proposal (Volume VIII) do not count towards the 25-sheet foldout limit.

1. PROPOSAL SUBMISSION

Proposals in response to this solicitation shall be submitted to the Government no later than the time specified in Block 9 of the SF 33 and shall remain valid for 360 days after the due date for receipt of proposals. “Local time” shall refer to the time zone for Washington, DC.

Telegraphic offers, facsimile offers, or offers submitted by electronic commerce will not be considered. Any proposals received through these means will be deleted or destroyed. Furthermore, the Government will not consider telegraphic, facsimile, or electronic commerce modifications of offers, or withdrawals of offers.

The preferred method of response is by overnight delivery service, such as FedEx, UPS, or DHL. Do not use the United States Postal Service.

All copies of the proposal shall be submitted to the PCO or Contract Specialist at the address below.

N00024-18-R-5200

PROPOSAL

DO NOT OPEN IN MAIL ROOM

For instructions on delivering hand-carried proposals, see the provision in this section entitled HQ L-2-0013, SPECIAL PROPOSAL RECEIPT REQUIREMENTS (NAVSEA).

1. MAJOR SUBCONTRACTOR PROPOSALS

For the purposes of this solicitation, major subcontractors are defined as any subcontractor proposed to perform 5% or more of the total hours under the contract. However, where otherwise minor subcontractors cumulatively perform more than 10% of the total hours under the contract or cumulatively perform more than $15 million of work under the contractor, all subcontractors with proposed costs exceeding $750,000 are considered major subcontractors and must propose as such. Major subcontractors may submit proposals or supporting information directly to the Government. The prime Offeror shall be responsible for the timeliness of any major subcontractor submissions. Failure to submit major subcontractor proposals by the proposal due date may render the entire proposal, including the prime Offeror's proposal unacceptable. All subcontractors that do not meet the definition of major subcontractor are minor subcontractors.

1. PROPOSAL CONTENT REQUIREMENTS

Offerors shall provide the information requested in the following paragraphs in the volumes indicated. If additional information is provided in other volumes or sections, Offerors shall provide clear references to the location in the proposal where the information may be found.

2. VOLUME I: EXECUTIVE SUMMARY

Do not include cost or price information in this volume. The Executive Summary Volume shall summarize the Offeror’s planned approach to satisfy the Government’s requirements. Key elements of the proposal shall be highlighted for both technical and management perspective. The Executive Summary shall be unclassified. The Government will not formally evaluate the Executive Summary.

2. VOLUME II: FACTOR 1 – TECHNICAL APPROACH

Do not include cost or price information in this volume. The Government intends for the Technical Approach Volume to present a discussion of the Offeror’s proposed approach to performing each of the CLINs in this solicitation within each topic area or element described below. The Offeror shall provide sufficient information to enable Government 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 solicitation. To this end, the Technical Approach Volume shall be specific, detailed, and complete enough to demonstrate clearly and fully that the Offeror understands the CEC objectives and has a thorough understanding of the solicitation requirements for accomplishing the efforts under this solicitation and the technologies involved. Proposals shall include block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. The level of technical detail provided must be sufficient to show how the Offeror proposes to fulfill the Government’s requirements and fully explain the methodology and procedures to be followed. The narrative must also identify and evaluate any risks associated with the Offeror’s proposed approach and propose mitigation steps to minimize the Government’s risk in accepting the Offeror’s proposed technical approach.

Additionally, the Offeror must clearly state any and all assumptions made to develop the proposed technical approach. Unless amended, Attachments 2 and 3 form a complete list of all GFI and GFP the Government intends to provide under this contract.

Within each element, the Offeror shall describe where applicable the extent and depth of its use of Small Business, HUBZone Small Business, Service-Disabled Veteran-Owned Small Business, Small Disadvantaged Business and Women-Owned Small Business concerns to accomplish contract requirements.

The Offeror shall describe its proposed approach for each of the following elements to accomplish the tasks defined in Section C. The Offeror should describe common processes and approaches to accomplishing both the completion and level-of-effort tasking. However, in the event that the Offeror proposes a different approach for any portion of the completion and level-of-effort tasking, the Offeror shall clearly describe any such differences and provide rationale to support the proposed approach.

The Technical Approach Volume shall address the following topics, or elements:

1. ELEMENT 1: SOFTWARE DEVELOPMENT APPROACH

The Offeror shall describe its software development approach and illustrate its intended method for accomplishing each of the software development requirements defined in Section C. The Offeror shall specifically demonstrate its software development capabilities and resources that will be used to support the development and testing efforts necessary for the development of CEC capabilities and interfaces. This rationale shall address at a minimum Open Architecture (OA), Commonality of Hardware, Software/Firmware and Interfaces, Cybersecurity and prospective Critical Program Information (CPI) with current protection rationale.

The Offeror shall describe its approach to providing the Government early insight into the development process by providing access to its Software Development Environment, development documentation, and any other relevant data throughout the development process. The Offeror shall describe its reuse philosophy and its approach to minimizing inter-component dependency. The Offeror shall describe why its software development approach is appropriate for CEC.

The Offeror shall provide a software build plan. The Offeror shall discuss the processes and tools to be used to automate pre-integration levels of testing and to collect and analyze data related to pre-integration testing.

The Offeror shall provide Software Lines of Code (SLOC) estimates showing new/modified/reused code along with justification for the underlying assumptions for CLIN 0001. The Offeror shall categorize its SLOC estimates in accordance with the definitions provided in Attachment 18. The Offeror shall describe its software development processes and its proposed system software, including: timing, techniques, partitioning (for SLOC and Computer Software Configuration Items (CSCI)), code, top level architecture, complexity and expandability. The Offeror shall describe its plan to design, develop, test, modify, integrate, optimize and document software drivers using estimated SLOC, function points, or other appropriate software size measurement. The Offeror shall provide SLOC estimates to demonstrate the Offeror’s clear understanding of the solicitation’s completion-scope requirements and represent a realistic approach to performing the completion-scope.

The Offeror shall provide a plan for long term software sustainment and maintenance and the reduction of software life-cycle maintenance costs. The Offeror shall provide historical metrics as evidence of software reliability improvements in terms of build stability prior to delivery on previous projects of similar scope.

The Offeror shall describe its process to resolve Software Trouble Reports (STRs) within the single source library.

The Offeror shall demonstrate its ability to manage the development, integration, and sustainment of software for multiple platforms, sensors, and warfare areas. The Offeror shall describe its System of Systems System Engineering approach, including its plan to manage multiple sets of requirements and interfaces, communicate with multiple platform/sensor organizations, and affect multiple warfare areas. The Offeror shall demonstrate its ability to manage multiple simultaneous software builds in the single source library. The Offeror shall discuss the processes and tools to be used to optimize and standardize development.

The Offeror shall demonstrate its understanding of composite track management and sensor netting in support of integrated fire control. The Offeror shall demonstrate its capability to design, develop, and, integrate software systems, and maintain system of system interoperability within composite track management and sensor netting. The Offeror shall demonstrate its ability to maintain configurability and adaptability of the software architecture and algorithms for multiple interfaces across multiple platforms, and ensure backwards compatibility with all existing variants of CEC. The Offeror shall provide details on its approach to develop, manage, and control a single-source baseline with multiple integration requirements across all versions of CEC, including multiple simultaneous baselines.

Offerors shall also submit an SDP rationale 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 CMMI® capability level 3. The SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 5 pages.

The Offeror shall submit a description of previous relevant experience, within the past 36 months in developing software of the similar size and complexity as that required under the statement of work. As a part of this description, the Offeror shall describe the extent to which personnel who contributed to these previous efforts will be supporting any resultant contract.

The Offeror shall describe any previous relevant Capability Maturity Model Integration (CMMI)® or equivalent model-based process maturity appraisals performed within the past 36 months. As a part of this description, Offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned. This description shall not exceed two (2) pages.

1. ELEMENT 2: SYSTEMS ENGINEERING PROCESS

The Offeror shall describe its Systems Engineering process and how this process allocates the performance and interface requirements and the Offeror will flow the requirements across CEC into a balanced system design as described in Section C. The Offeror shall describe its approach to flow-down of system requirements to hardware and software engineering teams. The Offeror shall address its plan to establish and maintain processes that will provide early design disclosure directly to the Government. The Offeror shall describe its approach toward managing new requirements and the impact on the system of systems. The Offeror shall demonstrate its understanding of the CEC Program Integrated Product Team (IPT) and Working Group (WG) requirements. The Offeror shall describe its plan to allocate systems engineering roles and how the Offeror’s system engineering process will influence team selection, qualifications, and role allocation. The Offeror shall describe the use of its system security engineering (SSE) process in specifying and designing a system that is protected against external threats and hardware/software vulnerabilities as described in Section C. The Offeror shall describe its plan to use Computer-Aided Systems Engineering (CASE) or similar tools and its experience in using these tools in developing a structured process that encompasses all disciplines under systems engineering. The Offeror shall describe its approach to providing the Government continuous insight and oversight into its System Engineering process by providing access to contractor tools, documents, databases, and any other information sources. The Offeror shall provide a description of the process and automated tools to be used in CEC Systems Engineering. If an automated tool is proposed, describe how it will be used and whether and how this tool will be interfaced with other automated tools. The Offeror shall also describe any proposed use of virtualization of the CEC system in support of systems engineering efforts. The Offeror should not respond with a description of a generic system engineering process.

1. ELEMENT 3: TRANSITION PLAN AND STARTUP APPROACH

The Offeror shall describe its transition and startup approach for the CEC program to ensure program milestones are met. The approach shall detail how the Offeror plans to set up facilities, ramp up staffing, schedule meetings, and allocate tasking to meet CEC test and schedule requirements as described in the Post Award Milestone Schedule and product cards, provided as GFI.

1. ELEMENT 4: TEST AND EVALUATION

The Offeror shall describe its Test and Evaluation strategy for the entire CEC effort as described in Section C. The Offeror shall describe its test planning processes for testing at Government, Independent, and Offeror test sites. The Offeror shall detail its test approach that would enable efficiency gains without losing effectiveness in all aspects and stages of testing from unit testing through at-sea testing. The Offeror shall describe its proposed facilities, equipment, test assets, and development and integration environments. The Offeror shall describe its approach to integrating processes, resources, and deliverables of second and/or third party vendors, Government test agencies, independent test agencies, and the Offeror’s own testing efforts into an integrated test program. The Offeror shall describe its approach to reducing T&E duration, complexity, and cost while achieving the T&E goals of the CEC program. The Offeror shall provide a description of the process, methodologies, and automated test and analysis tools, including CEC system virtualization, as applicable, to be used in CEC Test and Evaluation. If an automated tool, process, or methodology is proposed, describe how it will be used and whether and how this tool will be interfaced with other automated test and analysis tools.

3. FORMAL QUALIFICATION TEST (FQT)

The Offeror shall describe its formal qualification test (FQT) program, including its proposed:

· Test approach of the program to verify requirements using modeling and simulation tools and risk mitigation prior to FQT;

· Specific list of test assets and facilities to be utilized for testing, including needs for GFP or Government facilities and when the GFP or Government facilities will be required; and

· Allocation of the requirements to the individual tests and verification methods to validate these requirements.

Much of the system test program will be performed and executed in parallel with continuing development integration test activities. The Offeror shall provide its approach to identifying and integrating the test program to account for these concurrent activities. The Offeror shall discuss how this approach will be executed and managed during the test program.

The Offeror shall provide details to demonstrate the process the Offeror will use to develop and validate the Test Procedures prior to laboratory or shipboard use. The Offeror shall identify how it derives the elements to be validated by each test procedure. The Offeror shall identify how it will map elements to be validated to test results. The Offeror shall provide details that demonstrate what constitutes a valid test procedure and what information is gathered to build a test procedure. The Offeror shall identify any special test equipment (STE) required to conduct testing.

During the testing, it may be necessary to modify delivered hardware and software configurations in order to maintain schedule. The Offeror shall identify its approach to ensuring these modifications are tracked. The Offeror shall provide specific examples that demonstrate the effectiveness of the proposed approach.

The Offeror shall provide details to demonstrate its process to monitor and record each stage of testing as it occurs. The Offeror shall detail how it will efficiently maintain test records and perform analysis on test results.

3. INTEGRATION AND VERIFICATION TESTING

The Offeror shall describe its approach and methodology for intra-subsystem, inter-subsystem, and inter-system integration and verification, including the full range of testing and verification methods. This description shall cover test events, facilities, and assumptions required to satisfy all test objectives. The Offeror’s proposed test program shall include its plan to identify and resolve issues early in the design process prior to Government Independent Verification and Validation (IV&V).

3. ENVIRONMENTAL QUALIFICATION PLAN

The Offeror shall describe the plan for environmental qualification testing for any proposed hardware changes to the CEC system that will be performed to verify compliance with the platform environmental requirements described in Section C.

1. ELEMENT 5: TECHNICAL RISKS AND OPPORTUNITIES

The Offeror shall identify all the critical schedule risk items and technical risks under CLIN 0001. The Offeror shall identify the top three (3) critical schedule risk items and the top three (3) technical risks and further explain the consequences and mitigation for each.

1. ELEMENT 6: KEY PERSONNEL

The Offeror shall propose a Technical Director and a Program Manager as mandatory key personnel possessing the experience and education specified below. The Offeror shall submit detailed resumes for proposed key personnel that include the following information:

· Name

· Years of experience

· Training

· Unique or special qualification

· Positions held

· Tenure with the firm

· Degrees received from and dates of attendance at accredited colleges or universities

· Work history (including dates) of each individual as it relates to the anticipated statement of works task(s) to be assigned to that individual

· Security Clearance Level, including date and time of last investigation

· Citizenship

Resumes shall have a page limit of three pages each, but will not count towards the overall page count limit for Volume II. The resumes shall demonstrate the qualifications possessed by the proposed key personnel to complete the functions of which the Offeror has proposed that person.

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 the clause entitled 5252.237-9106, Substitution of Personnel. 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). When the Government awards a contract under those circumstances, the Government will require the awardee to use the qualifications listed on the relevant proposed key personnel resume as the basis for replacing that individual under 5252.237-9106(b) during contract performance. The Offeror shall make no substitution of key personnel without prior notification to and concurrence of the Contracting Officer.

Minimum requirements and desired qualifications for each of the key personnel identified above are as follows:

5. TECHNICAL DIRECTOR

Minimum Requirements:

· Ability to obtain and maintain a TOP SECRET security clearance.

· Degree from an accredited college or university in an engineering, scientific, or technical discipline.

· Substantial professional experience in engineering, including experience as a senior engineer supporting a team of skilled professional, technical, and support personnel involved with warfare/combat system integration or naval shipbuilding experience.

Highly Desired Qualifications:

· More than fifteen (15) years professional experience in engineering, including greater than five (5) years as a senior engineer supporting a team of skilled professional, technical, and support personnel involved with warfare/combat system integration or naval shipbuilding experience.

· Substantial engineering knowledge of composite track management and sensor netting in support of integrated fire control as well as experience with CEC (or an equivalent, complex US Navy combat system), system engineering and system architecture.

· Substantial experience in performing engineering analyses of total system product to include: functional analysis, timeline analysis, detail trade studies, requirements allocation and interface definition studies to translate customer requirements into hardware and software specifications, test, installation, as well as information assurance, cybersecurity, operation and maintenance engineering support functions.

· Bachelor’s or post-graduate degree from an accredited college or university in an engineering, scientific, or technical discipline.

5. PROGRAM MANAGER

Minimum Requirements:

· Ability to obtain and maintain a TOP SECRET Security Clearance.

· Substantial professional experience in program and project management, including experience as a program manager supporting a team of skilled professional, technical, and support personnel involved with warfare/combat system integration experience or naval shipbuilding.

Highly Desired Qualifications:

· More than ten (10) years’ experience integrating sensor/weapon hardware and software into combat systems.

· Bachelor’s or post-graduate degree from an accredited college or university in an engineering, scientific, or technical discipline.

1. ELEMENT 7: INTERFACING WITH KEY STAKEHOLDERS

The Offeror shall provide its proposed approach for interfacing with the Government and other stakeholders. The Offeror shall identify key stakeholders for CLIN 0001 tasking, including internal CEC program stakeholders and key stakeholders supporting programs with which CEC will be integrated. The Offeror shall describe its communication plan and demonstrate how that plan ensures efficient and effective communication and coordination with all stakeholders.

1. ELEMENT 8: FACILITIES

The Offeror shall describe company and/or subcontractor facilities that are available and proposed for the execution of the Offeror’s CEC proposed approach, including necessary engineering, development, assembly, integration, and test facilities consistent with the size and scope of the CEC requirements. The CEC Facility Support Equipment List (Attachment 14) provides a full listing of items in the existing CEC facility that complements the Government-Furnished Equipment. The Offeror need not propose to outfit its own facility with the specific items listed in the attachment. However, the Offeror shall demonstrate that its facility will, at a minimum, meet the functionality provided by the support equipment used in the existing facility.

If facilities are not available at contract award the Offeror shall provide a detailed schedule and commitment of availability for use to meet requirements of this contract. The Offeror shall identify any facility upgrades required to meet the requirements of the SOW.

The Offeror shall define the communications structure that will be used to ensure efficient and cohesive interaction between physically separated development activities. The Offeror shall identify the physical geographic location of all program related organizational units.

The Offeror shall describe its proposed use of Contractor-owned facilities and Government-furnished test-bed systems and the roles of these resources (see the clause under Section H of this solicitation entitled 5252.245-9108, Government-Furnished Property (Performance)).

1. ELEMENT 9: CONTRACT-WIDE STAFFING PLAN

The Offeror shall submit this item in the electronic version of the proposal only. The Offeror shall provide a Contract-wide Staffing Plan using the sample format provided in Attachment 19. The Offeror shall provide a matrix that describes the experience of each personnel listed on the Staffing Plan in supporting contracts of similar size and complexity.