N00024-18-R-5200_CEC_DA-ES_Draft_Sections_L.docx

DRAFT SOLICITATION SECTION L – N00024-18-R-5200

SELECTED DRAFT PORTIONS OF SOLICITATION N00024-18-R-5200

DRAFT CONTENT IS SUBJECT TO CHANGE WITHOUT NOTICE

SECTION L: INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

GENERAL INFORMATION

The completion and submission to the Government of an offer shall indicate the Offeror’s unconditional agreement to the terms and conditions in the solicitation. FAILURE TO FOLLOW THESE INSTRUCTIONS MAY RESULT IN REJECTION OF THE PROPOSAL.

The Offeror is required to submit a proposal which is sufficiently detailed and complete to fully demonstrate an understanding of, and compliance with, all of the requirements of the solicitation and shall contain only material directly related to this acquisition.

The Offeror shall submit all information required by this solicitation. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being disqualified from consideration for award. The Offeror’s proposal 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 are required to submit a proposal encompassing all items listed in Section B of this solicitation.

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 will 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 physically incorporated into the proposal. Discussions of each topic in the proposal shall exhibit continuity and logical progression. Failure to conform to all requirements of this solicitation may form the basis for rejection of the proposal.

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, a certificate to this effect shall be furnished, which must be signed by an authorized official of the Offeror and shall indicate the person’s name, employment capacity, 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.

GOVERNMENT-WIDE POINT OF ENTRY (GPE)

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 website relating to this solicitation (e.g. responses to questions, solicitation amendments, etc.). It is the Offeror’s responsibility to check the GPE website for any such information.

COMMUNICATIONS WITH THE GOVERNMENT

Unless otherwise specified, the Naval Sea Systems Command Procuring Contracting Officer (PCO) and Contract Specialist (CS) are the sole 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

AVAILABILITY OF ATTACHMENTS AND BIDDER’S LIBRARY

Attachments to this solicitation and the associated bidder’s library 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).

Requests for access to the controlled solicitation attachments and the bidder’s library shall be submitted electronically as follows:

TO: PCO as listed above CC: CS as listed above SUBJECT LINE: N00024-18-R-5200 Terms of Use (Offeror Name)

Offerors electronic request shall provide a signed Terms of Use letter (Attachment L-1) and completed solicitation DD254 (Attachment J-#) indicating that the requesting company has a Defense Security Service (DSS) issued SECRET facility clearance, providing for SECRET personnel clearances and SECRET safeguarding capability. The Government will not provide sponsorship for new or upgraded personnel or facility clearances.

Distribution of the controlled solicitation attachments and the bidder’s library will be made available in a secure manner to only those Offerors that meet the security requirements detailed herein and have submitted a signed Terms of Use letter (Attachment L-1).

Offerors with an executed Terms of Use letter for this solicitation on file with the Contracting Officer 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 terms of use letter or DD254.

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

SUBMISSION OF QUESTIONS AND COMMENTS

Offerors shall submit written questions and comments related to this solicitation in accordance with the Bidder’s Question Submittal Form (Attachment L-#) attached to Section L. For ease of Government review and to minimize response time, Offerors must submit this form in editable Excel file format, not Portable Document Format (PDF). Each question should include the applicable document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification. 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.

Offers shall submit comments, questions or inquiries to any Government representative other than the PCO and CS identified above. It is the Government’s intention to distribute bidder’s questions and associated responses to all Offerors. In the event that a potential Offeror wishes to submit a comment or question that the potential Offeror believes addresses a subject that is specific to the company (and/or addresses anything that is believed to be proprietary in nature) then the inquiry shall be marked accordingly. If the Government concurs with this identification, the Government will respond only to that potential Offeror. If the Government does not concur with that identification, it shall inform the submitter and not provide any further response.

It is the Government’s intention that all other publication of questions and answers in response to solicitation will be announced via the GPE. However, an answer that contains classified or controlled unclassified information will not be posted publicly, but rather will be sent directly to those Offerors who have executed Terms of Use letter and meet the security requirements detailed in herein.

The Government will not entertain any proposed revisions to the terms and conditions contained in this solicitation submitted as part of the Offeror’s proposal, including any attachment/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 non-compliant. As such, any questions or suggestions related to the terms and conditions of this solicitation shall be made known by the Offeror in accordance with this section and the deadline for questions below.

The deadline for receipt of questions is close of business, xx (#) days after the date the solicitation was issued (See block 5 of the Standard Form 33). Any questions received after this may not be answered prior to receipt of proposals.

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 (insert name of Offeror)

AWARD WITHOUT DISCUSSIONS

Please note that pursuant to FAR 52.215-1 “Instructions to Offerors – Competitive Acquisition” (JAN 2004), 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 in accordance with FAR 15.306 “Exchanges with Offerors After Receipt of Proposals” if determined by the Contracting Officer to be necessary [see paragraph (4) of FAR 52.215-1(f)]. Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and the submission of multiple proposals will result in disqualification of the submitting Offeror. Therefore, the Offeror’s proposal submissions 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. Each Offeror is required to complete Attachments L-# and L-# in their entirety and provide them along with the proposal submission.

PROPOSAL FORMAT

Format and composition for each submittal is as follows:

Note: Two (2) compact disks (CD-ROMs) or DVDs and xxx (x) hard paper copies (one (1) original, and xx (x) copies).

In presenting material in these volumes, the Offeror is 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. Index pages and tabs are required and shall be cross-referenced to the table of contents. All pages shall be consecutively numbered within each volume (e.g., 1,2,3,…).

Exclusions to page count limitation include: cover letter; title pages; table of contents; executive summary; glossary; appendices; drawings; weight estimates; structural calculations and/or reports; copies of regulatory body correspondence; calculations; any referenced completed analyses for purposes other than development of this proposal; and trade studies.

Information requested in the following paragraphs shall be provided in the volumes indicated. If additional information is provided in other sections, reference shall be made to those sections where this information can be found.

When evaluating an offer, the Government will consider how well the Offeror complied with these instructions. The Government will consider any failure on the part of an Offeror to comply with these instructions to be an indication of how the Contractor will comply with contract requirements during contract performance. Therefore, the Government encourages Offerors to contact the Contract Specialist via email (and cc: the PCO) to request an explanation of any aspect of these instructions.

Binding and Labeling

The Offeror 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 be included in the page count.

The Offeror is 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.

All volumes shall be submitted 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 and a glossary of all abbreviations and acronyms used, with an explanation for each.

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 of the Volume and Serial/Copy Number. If the Offeror wishes to restrict the disclosure or use of its proposals, the Offeror shall use the legend permitted by FAR 52.215-1(e). Each page of the Offeror’s proposals shall be labeled with the Offeror’s name, RFP number and date corresponding to the date of the initial proposal.

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

Electronic Data Format

The electronic proposals shall not contain any substantive information not included in the paper copy format. In the event of disparities between paper copies and electronic information, the electronic copy governs. Electronic proposal submissions and supporting information shall be submitted on virus-free and CD-ROM or DVD formatted suitable for reading in a standard PC-compatible CD-ROM/DVD drive. All files submitted to the Government shall be compatible with Microsoft Office 2010. 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 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/DVD shall be labeled with the Proposal Volume Number and Title, the Offeror’s name, solicitation number, date of submittal, a copy indicator 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/DVD submitted. If classified information will be provided, that information shall be provided on separate CDs/DVDs, marked to the highest classification level required, provided in a manner that mirrors the instructions above for submitting unclassified information. All other CDs/DVDs should 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 that duplicate the volumes and partitions used in the paper copy of the proposal. The Offeror shall screen all CDs/DVDs for computer viruses prior to submittal.

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 size 8-point font.

Every paragraph, 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.

Foldouts 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 x 17 inches and shall not exceed three folds. Each foldout page will count as two (2) pages for page count purposes. Foldouts for the entire proposal are limited to a total of XX foldout pages.

Proposal Submission

Proposals in response to this RFP shall be submitted at or before the time specified in Block 9 of the SF 33 and shall be valid for XX days.

Telegraphic offers, facsimile offers, or offers submitted by electronic commerce will not be considered. Furthermore, telegraphic, facsimile, or electronic commerce modifications of offers, or withdrawals of offers, will not be considered.

The preferred method of response is by overnight delivery service, such as FedEx, UPS, etc. Do not use U.S. Mail.

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

Electronic disks shall be attached to the proposals such that they do not fall out or become dislodged during transport and handling.

Cover Letter

The Price Volume of the proposal shall be accompanied by a cover letter prepared on the company’s letterhead stationery and shall state the following:

· The proposal is valid for XX days,

· The Offeror’s Cage Code and DUNS Number;

· All enclosures being transmitted;

· The approved security clearance and clearance level of storage capability for the Offeror’s facility;

· Address and point of contact for the Offeror’s cognizant security office,

· Name of the Offeror’s security representative,

· Address(es) of the location(s) at which the Offeror intends to perform the proposed effort including subcontractor facilities.

The cover letter is not subject to the page count limits specified in this solicitation. The Government will evaluate the cover letter to confirm that it contains the required information.

Each Offeror shall submit an offer/proposal and other written information in strict accordance with these instructions.

SF 33/Model Contract Volume I must contain the complete SF 33 Solicitation Set/Model Contract. The contractor shall ensure the complete SF 33 Solicitation Set/Model Contract contained in Volume I includes the following:

RFP Section A - The RFP Standard Form (SF) 33 will be used to make award. Blocks 12 through 18 of the SF 33, “Solicitation, Offer and Award,” shall be completed by the Offeror. The Offeror shall submit an executed SF-33 bearing the original signature of a representative who is authorized to contractually bind the company submitting the offer. The Offeror shall also submit a signed copy of the SF-30 cover page for each amendment to the solicitation. As with the SF-33, the representative who signs the SF-30 cover pages must be authorized to contractually bind the company submitting the offer. Block 12 shall be completed to align with the Section L clause, Proposal Submission.

RFP Sections B through I - The Offeror shall submit Sections B through I, with all appropriate information completed as required by the RFP.

RFP Section J – Exhibits and Other Attachments; The Offeror shall include the following completed attachments as part of their Volume I submittal:

· Attachment J-xx Small Business Subcontracting Plan*

· Attachment J-xx Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software submitted in response to 252.227-7017

· Attachment J-xx Guaranty Agreement for Corporate Guarantor**

*As prescribed in FAR 19.708, Offerors other than small business concerns shall submit a subcontracting plan and that plan, once approved, shall be made part of any contract resulting from this RFP. The Offeror’s Small Business Subcontracting Plan will be incorporated into the contract as an Attachment J-xx – Small Business Subcontracting Plan.

**Offerors are advised that Attachment J-xx, Corporate Guarantee, must be submitted with a raised corporate seal.

RFP Section K - Representation, Certifications and Other Statements of Offerors; Offeror shall complete and submit clauses applicable to fill in and submit with proposal. Items which are not applicable should be marked “N/A”.

Offerors must submit Volume I using the conformed RFP as of the date of the last amendment prior to the proposal submission due date.

The proper completion and submission to the Government of the SF 33 Solicitation Set/Model Contract shall constitute an offer and indicate the Offeror’s unconditional assent to the terms and conditions in this RFP and in any attachments hereto. Any objection to any of the terms and conditions of this RFP may constitute a deficiency, which may make the offer unacceptable. Offerors are notified that the Government’s acceptance of an offer does not imply acceptance of the pricing rationale or assumptions.

The following items in the model contract will be completed by the Government at award:

· Entire Contractual Document - Assign Contract Number and reformat for SPS, including updating page numbers;

· Standard Form 33, AWARD/CONTRACT, Items 19 thru 28 – Complete Items;

· Section G, complete clause and insert:

· Accounting and Appropriation Data

· CONTRACTING OFFICER’S REPRESENTATIVE,

· ADMINISTRATIVE CONTRACTING OFFICES, and

· DFARS 252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013);

· Attachment J-x - Attach signed DD 254 updated with Contract Number and

· Attachment J-x - Small Business Subcontracting Plan

VOLUME I: Factor 1 - Technical Approach

No Price information shall be included in this volume.

The Government intends for Volume I to be a targeted discussion of the Offeror’s proposed approach to performing each of the CLINs. Technical Proposal Volume shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal meets the requirements of the RFP. To this end, the Technical Proposal Volume shall be specific, detailed, and complete 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. Integrated Master Schedule (IMS) shall be created and submitted using Microsoft Project. The technical section must be sufficient to show how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed. The technical approach 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, Attachment J-XX is a complete list of all GFP and GFI the Government intends to provide under this contract. If the Offeror’s proposal assumes the use of any GFP or GFI not listed in Attachment J-XX, the Offeror must specifically note that assumption in it proposal, but bears the risk that such an assumption may be found to be unrealistic, which may increase the likelihood of unsuccessful contract performance.

The Technical Proposal Volume shall be limited to the page count as identified above. Pages in excess of the page limit will not be read or evaluated. Title Pages, cover pages, glossaries, tabbed dividers, and table of contents shall not be subject to the page limitations, will not be evaluated, and shall not be numbered. Price information shall be completely omitted from the Technical Proposal Volume.

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

Elements

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 the Section C, paragraph 3.1.3, Software Development, and its subparagraphs. 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) as described in Section C, paragraphs 3.1.12, Commonality of Hardware, Software/Firmware and Interfaces – Completion Tasks, and 3.1.13, Commonality of Hardware, Software/Firmware and Interfaces – LOE Tasks; assurances (systems, software), and Cybersecurity and prospective Critical Program Information (CPI) with current protection rationale as described in Section C, paragraph 3.1.14, Cybersecurity, and its subparagraphs. The Offeror shall describe its approach to providing the Government early insight into the development process by providing near real-time access to its Software Development Environment, development documentation, and any other relevant data as described in Section C, paragraph 3.1.3, Software Development. The Offeror shall describe its reuse philosophy and its approach to minimizing inter-component dependency as described in Section C, paragraph 3.1.3.1.2, Software Reuse – Completion Tasks, and 3.1.3.2.2, Software Reuse – LOE Tasks. The Offeror shall describe why its software development approach is appropriate for CEC.

The Offeror shall discuss how the software engineering function described in Section C, paragraph 3.1.3, Software Development, and its subparagraphs, will be integrated with the system engineering functions described in Section C, paragraph 3.1.2, Systems Engineering, and its subparagraphs. The Offeror shall discuss the approach that will be used to provide a seamless and efficient flow of information between the system engineers and the software engineers.

The Offeror shall summarize the software challenges of CEC and describe proposed solutions.

The Offeror shall provide a build plan in accordance with Section C, paragraphs 3.1.3, Software Development, and 3.1.3.1, Software Development 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 as described in Section C, paragraph 3.1.5.1, Contractor Developmental Test & Evaluation (DT&E) – Completion Tasks.

The Offeror shall provide Software Lines of Code (SLOC) estimates showing new/modified/reused code along with justification for the underlying assumptions for CLINs [TBD]. The Offeror shall categorize its SLOC estimates in accordance with the definitions provided in Attachment J-XX. 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 as described in Section C, paragraph 3.1.3.15, Reduction of Software Life-Cycle Maintenance Costs – Completion Tasks and 3.1.3.16, Reduction of Software Life-Cycle Maintenance Costs – LOE Tasks.

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

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 as described in Section C, paragraph 3.1.2, Systems Engineering, and its subparagraphs. The Offeror shall demonstrate its ability to manage multiple simultaneous software builds in the single source library as described in Section C, paragraph 3.1.7.3, Software 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 multiple simultaneous baselines.

The Offeror shall describe its process to resolve STRs as described in Section C, paragraphs 3.1.3.27, Software Trouble Reports (STR) – Completion Tasks, and 3.1.3.28 Software Trouble Reports (STR) – LOE Tasks.

Systems Engineering Process The Offeror shall describe its Systems Engineering process and how this process allocates the performance and interface requirements and flows those requirements across CEC into a balanced system design as described in Section C, paragraph 3.1.2, Systems Engineering, and its subparagraphs. The Offeror shall address its plan to establish and maintain a process that will provide early design disclosure directly to the Government. The Offeror shall describe its approach toward managing new requirements and scope and the impact on the system of systems. The Offeror shall demonstrate its understanding of what will be required to support the Integrated Product Teams (IPT) and Working Groups (WG) defined in the Section C, paragraph 3.1.1.11.3, Integrated Product and Process Development (IPPD), and its subparagraphs. The Offeror shall describe its plan to allocate systems engineering roles and how the system engineering process will influence team selection, qualifications, and role allocation. 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 into its System Engineering process by providing near real-time access to tools, documents, databases, and any other information sources, as appropriate. 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 should not respond with a description of a generic system engineering process.

Transition Plan and Startup 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.

Test and Evaluation The Offeror shall describe its Test and Evaluation strategy for the entire CEC effort. The Offeror shall describe its test planning processes for testing at Government, Independent, and Offeror test sites. 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 same goals. The Offeror shall provide a description of the process, methodologies, and automated tools 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 tools.

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 model and simulation tools and risk mitigation prior to FQT;

· Specific list of test assets and facilities to be utilized for testing, including needs for Government Furnished Test or other Government owned assets, equipment or facilities and when they will be required;

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

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 plan 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 shipboard use. The Offeror shall identify how elements to be validated by test procedure are derived and identify how test results will be mapped to elements to be validated. 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.

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

Environmental Qualification Plan The Offeror shall describe the plan for environmental qualification testing that will be performed to verify the platform environmental requirements described in Section C, paragraphs 3.1.5.1.4, Environmental Qualification Testing – Completion Tasks, and 3.1.5.2.4, Environmental Qualification Testing – LOE Tasks.

Key Personnel

The Offeror shall provide the following mandatory key personnel possessing the experience/education specified below. The Offeror may propose additional personnel.

· Technical Director

· Program Manager

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

Technical Director Minimum Requirements:

· Ability to obtain and maintain a Top Secret Security Clearance.

· Eligible for Top Secret Sensitive Compartmented information (SCI) Security Clearance.

Highly Desired Qualifications:

· Ten (10) years professional experience in engineering, including 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 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 degree from an accredited college or university in an engineering, scientific, or technical discipline.

Program Manager Minimum Requirements:

· Ability to obtain and maintain a Top Secret Security Clearance.

· Substantial program management experience supporting Department of Defense development efforts.

Highly Desired Qualifications:

· Ten (10) years professional experience in Program and Project Management, including five (5) years as a Program Manager supporting a team of skilled professional, technical, and support personnel involved with Naval shipbuilding or Warfare/Combat System integration experience.

· Substantial experience integrating sensor/weapon hardware and software into combat systems.

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

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; and tenure with the firm

· Degrees held from 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 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 Offerors agrees that the list of key personnel proposed serves as part of the basis for award of this contract. Accordingly, the Offeror agrees to assign to this contract those key persons whose resumes were submitted with the proposal necessary to fulfill the requirements of the contract. No substitution of key personnel shall be made without prior notification to and concurrence of the Contracting Officer.

Sample Problem

[Sample problem to be provided in formal solicitation]

VOLUME II: Factor 2 - DATA RIGHTS

The Data Rights Volume shall define how the Offeror will offer data rights for the work required by this solicitation. It shall describe in detail the proposed rights for hardware, software, and interfaces to be developed as required by this solicitation. Price information shall be completely omitted from the Data Rights Proposal Volume.

The Government desires at least Government Purpose Rights (GPR) (as defined in DFARS 252.227-7013 (MAR 2011) and DFARS 252.227-7014 (MAR 2011)) in all non-commercial technical data (TD) and computer software/computer software documentation (CS/CSD)( including object code, executable code and source code). . 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 Government Purpose Rights. The Data Rights offered (7017 list, 7028 list, and/or Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation) shall be provided as attachments to Volume # and will become Attachments J-# to the Contract.

The Government will evaluate the degree to which the proposal meets the Government’s desired level of rights in TD, CS and CSD and enables the Government to adequately sustain the end item deliverables over their lifecycle including for maintenance, repair and upgrade. The Offeror shall describe how they will support the Government’s desire with respect to noncommercial TD and CS/CSD.

In the event an Offeror proposes to deliver any commercial or noncommercial TD/CS/CSD with less than such rights as desired by the Government, the Government will evaluate the adverse impact on the Government’s ability to use, modify, release, or disclose such TD, CS, or CSD. Further, the Government will consider the adverse impact of less than Unlimited Rights/Government Purpose Rights in its best value determination. The Data Rights offered shall be incorporated into the successful Offeror’s contract upon award. The Offeror’s shall provide the following information as attachments to its offer:

VOLUME III: Factor 3 - Management Approach

No Price information shall be included in this volume.

Volume III – Management Approach shall address the following topics:

Elements

Program Management The Offeror shall describe what program management approach is being proposed, how it will be implemented, and unique features of the Offeror's plan as a means of conveying an understanding and compliance with tasks described in the SOW. Simply stating that the Offeror shall comply with the tasks described in the SOW will not convey an understanding of the requirement.

Program Organization The Offeror shall depict the program organization to include the management team (identifying the proposed Program Manager and Technical Director), including the Integrated Product Teams (IPTs)/Cross Product Teams (CPTs) (identifying Contractor and/or Subcontractor IPT/CPT Leads), and the Government/contractor technical and contractual interfaces planned. The Offeror's shall describe its plan for planning and execution of program reviews and System Engineering Technical Review (SETR) events described in the SOW.

Contract-wide Integrated Master Schedule (IMS) The Offeror shall provide a Contract-wide IMS with accompanying IMSs for CLINs 0001-0008, 1002-1006, 2002-2006, 3002-3006, and 4002-4006. The IMS shall be consistent with and traceable to the other aspects of the Offeror’s proposal and meet the requirements of Section C, paragraph 3.1.1.6, Integrated Program Management Report (IPMR), and its subparagraphs.

Contract-wide Contract Work Breakdown Structure (CWBS) The Contractor shall provide a Contractor Work Breakdown Structure that meets the requirements of Section C, paragraph 3.1.2 and CDRL A002.

Contract-wide Staffing Plan The Contractor shall provide a Contract-wide Staffing Plan in accordance with Section L Appendix XX. 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.

Organizational Structure The Offeror shall describe the proposed organizational structure including subcontractors.