N00039-18-R-0005-0001 SMIT RFP Amendment 10262018.docx

N0003918R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT LOG

N00039-18-R-0005 Amendment Log

26 Oct 18

The time and date for receipt of offers, is 2:00 PM local time, 10 January 2019. The time and date for receipt requirements applies to both electronic and paper copy submittals.

To:

The time and date for receipt of offers, is 2:00 PM ET, 10 January 2019. The time and date for receipt requirements applies to both electronic and paper copy submittals.

26 Oct 18

Questions: Offerors may submit questions concerning any aspect of this solicitation. All questions regarding this solicitation shall be submitted via the NGEN-R AcquServe Vendor Portal at https://vendors.acqucenter.noblis.org/NGENR/SMIT by 4:00 PM ET, 9 November 2018. Questions submitted by any other means will not be accepted. As time may not permit responses to questions received after the stated submission date, the Government may decline to answer questions received after this deadline. Offerors shall not provide questions or comments that include proprietary information. The Government will use its best efforts to respond to Offeror questions and comments; however, responses are not guaranteed to questions submitted after the deadline. Unless expressly stated by the Contracting Officer, questions and answers published throughout this solicitation’s open period do not constitute an amendment to this solicitation. Specific instructions on how to access the AcquServe Vendor Portal can be found in Attachment L-5, NGEN-R AcquServe Vendor Portal Access.

To:

(g) Questions: Offerors may submit questions concerning any aspect of this solicitation. All questions regarding this solicitation shall be submitted in writing to the PCO at kim.reavis@navy.mil and the CS at ryan.f.thompson@navy.mil by 4:00 PM ET, 9 November 2018. Offerors are requested to use the Government furnished comment resolution matrix (CRM) as provided in the solicitation announcement, for the submittal of questions. As time may not permit responses to questions received after the stated submission date, the Government may decline to answer questions received after this deadline. Offerors shall not provide questions or comments that include proprietary information. The Government will use its best efforts to respond to Offeror questions and comments; however, responses are not guaranteed to questions submitted after the deadline. Unless expressly stated by the Contracting Officer, questions and answers published throughout this solicitation’s open period do not constitute an amendment to this solicitation.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L-1

L-1 GENERAL INFORMATION

This RFP is for Service Management, Integration, and Transport (SMIT) services using full and open competition, with the intent to award a single Indefinite Delivery/Indefinite Quantity (ID/IQ) contract. Offers submitted in response to this RFP shall be unclassified.

0. Proposal Incorporation. Portions of the successful Offeror’s proposal may be incorporated into the contract.

0. Communications. The Procuring Contracting Officer (PCO) and the Contract Specialist (CS) are the sole points of contact for this procurement. Exchanges of information between Government and Offerors will be controlled by the PCO. The PCO may use email to transmit information to Offerors. All communications shall be marked with the following restrictive legend: “Source Selection Information – See FAR 2.101 & 3.104”.

0. Electronic Reference Documents. All referenced documents for this solicitation are available, via the SPAWAR e-Commerce Central (ECC) website (https://e-commerce.sscno.nmci.navy.mil/), the NGEN-R Bidder’s Library/Technical Data Repository (https://acqupass.noblis.org/NGENTDR), and on the Supplemental Network Technical Data hard drive. Offerors are required to register and be approved for access to the NGEN-R Bidder’s Library; access requests should be submitted as early as possible. Offerors must also request and be approved to obtain a copy of the Supplemental Network Technical Data; requests should be sent to the NGEN-R Procuring Contracting Officer (PCO) and the Contract Specialist (CS). Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the SPAWAR ECC website for this solicitation.

0. Discrepancies. If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing via email at kim.reavis@navy.mil, prior to solicitation closing date.

0. Proposal Precedence. In the event of any inconsistency between paper and electronic proposals, the electronic proposal submission will take precedence.

0. Estimated award date. For Bidding/Proposal purposes the estimated effective date of contract award is 30 June 2019.

L-2 INSTRUCTIONS FOR SUBMISSION OF OFFERS

(a) The proposal shall remain valid at least 270 days after proposal due date.

(b) The proposal shall be submitted in the format set forth herein and correlate directly with the specific proposal preparation instructions. Failure to submit complete information in the manner described herein may be considered “Unacceptable” and may result in the exclusion of the proposal from further consideration. Where cross-referencing is used, the volume, attachment, exhibit and paragraph numbers, as appropriate, shall be stated.

(c) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience and will base its evaluation on the information presented in the Offeror's proposal.

(d) Elaborate brochures or documentation, binding, detailed art work, internet hyperlinks, or other embellishments are unnecessary and are not desired.

(e) The Government will not consider alternate proposals. If an Offeror (1) fails or refuses to assent to any of the terms and conditions of this RFP, (2) proposes additional terms or conditions, (3) includes conditions in its proposal with assumptions that take exception to the RFP or (4) fails to submit any of the information required by this solicitation, then the Government may consider the offer to be unacceptable and therefore ineligible for contract award.

(f) The time and date for receipt of offers, is 2:00 PM ET, 10 January 2019. The time and date for receipt requirements applies to both electronic and paper copy submittals.

(g) Questions: Offerors may submit questions concerning any aspect of this solicitation. All questions regarding this solicitation shall be submitted in writing to the PCO at kim.reavis@navy.mil and the CS at ryan.f.thompson@navy.mil by 4:00 PM ET, 9 November 2018. Offerors are requested to use the Government furnished comment resolution matrix (CRM) as provided in the solicitation announcement, for the submittal of questions. As time may not permit responses to questions received after the stated submission date, the Government may decline to answer questions received after this deadline. Offerors shall not provide questions or comments that include proprietary information. The Government will use its best efforts to respond to Offeror questions and comments; however, responses are not guaranteed to questions submitted after the deadline. Unless expressly stated by the Contracting Officer, questions and answers published throughout this solicitation’s open period do not constitute an amendment to this solicitation.

L-2.1 PROPOSAL FORMAT

(a) Proposal Requirements. Offerors shall submit proposals in the format set forth herein. Failure to submit complete information may be considered unacceptable and may result in the exclusion of the proposal from further consideration. Proposals submitted in response to this RFP shall be unclassified. Each page shall contain a footer that includes, as a minimum, the Offeror’s name, solicitation number, volume number, page number and, if applicable, restrictive legend (see FAR 52.215-1 (e) (2)).

(b) Page Limits. A page is defined as a sheet of paper that includes information. When information is contained on both sides of a single sheet of paper it will be counted as two (2) pages and shall be numbered accordingly. INFORMATION SUBMITTED IN EXCESS OF THE PAGE LIMITS ESTABLISHED IN TABLE L-3.1 WILL NOT BE READ OR EVALUATED. Page limits do not include cover sheets, tables of contents, traceability matrices, lists of figures, lists of drawings, lists of proprietary data, glossaries, tabs, dividers, or blank pages. All proposal material must be contained within the page limit(s) identified for each volume, unless otherwise specified. A partial page counts as a full page. All pages, within a page limited volume, shall be consecutively numbered, starting at page one (1), and shall not exceed the page limitation.

(c) Page Format. Format instructions apply to electronic and paper unless otherwise stated. Proposals shall be on 8-1/2" X 11" paper with single-spaced typed lines, including figures, glossaries, table of contents and cover sheets. The font shall be Times New Roman and no smaller than 12 point in the text, 10 point in spreadsheets, and eight (8) point on drawings, figures, and tables. Offerors may use foldout pages up to 11” X 17” only for diagrams, charts or graphic material. Foldout pages will count as one (1) page for each side. Standard margins shall be a minimum of 1”, excluding header and footer. The volumes shall contain a glossary of abbreviations and acronyms used and an explanation of each. The ORIGINAL physically signed paper proposal shall be on white bond paper; no pen and ink changes are allowed.

(d) Electronic Submissions. The electronic submissions (except where otherwise specified) shall include separate files using Microsoft Office, Adobe Acrobat, in accordance with Table L-3.1. This includes: Microsoft Word for all text in *.docx files in original searchable text format; Microsoft Excel for all spreadsheets in *.xlsx files [all Excel files shall be operable versus value only spreadsheets (i.e., Formulas should be included in all applicable cells)]; and Microsoft Project in *.mppx files shall be used for all schedules. All signed documents shall be submitted as Adobe Acrobat .pdf files (e.g., signed SF1449, Cover Letter, teaming agreements, etc.). All other *.pdf files must be “searchable.” Any graphics software, which produces embedded objects and pictures compatible with Microsoft Office, may be used for graphics within the Offeror’s proposal. All files shall use file formats compatible with and follow Windows 10 / Microsoft Office naming conventions, and include Offeror’s company name. Tables, figures, and graphics that are placed or embedded into Word (*.doc or *.docx) or PDF (*.pdf) documents or other Office compatible files shall be kept simple, understandable, and must be legible. No files shall be password protected. The Offeror shall not prepare any portion of its proposal using sound, animation, or video files.

(e) Binding and Labeling. Each paper volume of the proposal shall be separately bound in a three-ring binder. A cover sheet shall be affixed to each volume, clearly marked as to the volume number, the copy number, the RFP identification, the Offeror’s name, and if applicable, restrictive legend (see FAR 52.215-1(e) (2)). The volume and copy numbers shall appear on the spine of the volume binder to permit rapid accounting when the volume is placed in a vertical position in a storage cabinet.

(f) Cover Page and Table of Contents. Each proposal volume shall include a Cover Page and Table of Contents, which will not count against page count limitations. The Cover Page shall identify the solicitation number, proposal volume and title, the Offeror’s name, and if applicable, restrictive legend (see FAR 52.215-1(e) (2)).

L-2.2 DELIVERY OF ELECTRONIC PROPOSAL

Offerors shall upload all required proposal documentation to the NGEN-R AcquServe Vendor Portal located at, https://vendors.acqucenter.noblis.org/NGENR/SMIT, by the date and time specified in this solicitation. To obtain access to the AcquServe Vendor Portal, an Offeror must acquire a U.S. Government External Certificate Authority (ECA) Medium Assurance Certificate. Offerors may purchase an ECA through IndenTrust (https://www.identrust.com/certificates/dod-eca-programs) or Operational Research Consultants (https://eca.orc.com). Offerors may alternatively use an existing Access Certificate for Electronic Services (ACES) Business Representative Certificate. (The government is discontinuing the ACES Certificate program in August 2018, but existing certificates may be used until they expire.) Specific instructions on access and use of the AcquServe Vendor Portal can be found in Attachment L-5, NGEN-R AcquServe Vendor Portal Access.

Electronic file names shall identify the Offeror and be consistent with the instructions at Table L-3.1, and include revision number, if applicable. Each proposal section shall be uploaded through the AcquServe Vendor Portal as a separate electronic file. Offerors will receive a time-stamp receipt of submission for each file submitted through the AcquServe Vendor portal.

L-2.3 DELIVERY OF PAPER PROPOSAL

The Government intends to conduct its evaluation at Noblis, a support Contractor facility. The Offeror shall submit one (1) ORIGINAL PHYSICALLY SIGNED paper copy of its proposal by mail or hand-delivery to the Noblis address listed below:

Attn: Mrs. Kim Reavis, Contracting Officer Office: Space and Naval Warfare Systems Command 2002 Edmund Halley Drive Reston, VA 20191 Phone: (703) 595-3363

All parcels must be numbered, an inventory must be provided, and each parcel shall be prominently labeled: “REQUEST FOR PROPOSAL – SOLICITATION N00039-18-R-0005.”

The only hours for delivering proposals to Noblis are 8:00 AM to 2:00 PM ET, 10 January 2019. To coordinate the successful receipt of the paper proposal, Offeror’s shall contact the PCO at kim.reavis@navy.mil and CS at ryan.f.thompson@navy.mil at least 24 hours prior to delivery.

L-3 SUBMISSION OF PROPOSALS STRUCTURE

Offerors shall submit proposals in accordance with the instructions set forth in Section L-2 and organized as shown below. The Cover Page and Table of Contents required for each Volume will not count against page limitations. Pricing shall only be included in Volume 5, no pricing shall be included in any other volume.

Volume GC: Gate Criteria (Non-Cost / Price) Gate Criteria 1: Performance at Scale Gate Criteria 2: Small Business Utilization

Volume 1: Technical Proposal (Non-Cost / Price) Factor 1 – Technical Approach Subfactor 1.1: Systems Engineering Subfactor 1.2: Network Transformation/Modernization Sample Exercise

Volume 2: Management Proposal (Non-Cost / Price) Factor 2 – Management Approach Subfactor 2.1: Program Management Plan Subfactor 2.2: Network Operations Subfactor 2.3: Tools Management and Data Access Subfactor 2.4: Supply Chain Risk Management

Volume 3: Past Performance Proposal (Non-Cost / Price) Factor 3 – Past Performance Documentation

Volume 4: Transition Proposal (Non-Cost / Price) Factor 4 – Transition Approach Subfactor 4.1: Phase-In Services Subfactor 4.2: NMCI Transition Plan Subfactor 4.3: ONE-Net Transition Plan Subfactor 4.4: USMC Transition Plan

Volume 5: Cost / Price Proposal Factor 5 – Cost / Price Proposal

Volume 6: Cover Letter and Contract Documents (Non-Cost / Price)

TABLE L-3.1-PROPOSAL PAGE LIMITATIONS AND FILE NAMING CONVENTIONS

VOLUME GC: GATE CRITERIA

VOLUME 1: TECHNICAL PROPOSAL

FACTOR 1: TECHNICAL APPROACH

*.docx

VOLUME 2: MANAGEMENT PROPOSAL

FACTOR 2: MANAGEMENT APPROACH

VOLUME 3: PAST PERFORMANCE PROPOSAL

FACTOR 3: PAST PERFORMANCE DOCUMENTATION

VOLUME 4: TRANSITION PROPOSAL

FACTOR 4: TRANSITION APPROACH

VOLUME 5: COST/PRICE PROPOSAL

FACTOR 5: COST/PRICE PROPSAL

VOLUME 6: CONTRACT DOCUMENTS

L-4 SUBMISSION OF PROPOSAL CONTENT

(a) Volume GC-Gate Criteria - (Non-Cost/Price Factors).

(1) Gate Criteria 1: Performance at Scale

(i) The Offeror shall submit a summary of contract performance that demonstrates how its proposed team has experience managing the portfolio of services described in the Performance Work Statement (PWS) (Attachment J-1), for an intranet that consists of a wide area/multiple base area and local area networks (BAN/LAN) which supported a minimum of 40,000 virtual and/or physical seats. The experience must have occurred within the last five (5) years of the date of release of this solicitation on one or more contracts. Documentation shall include:

a. Identification of the intranet by agency/corporation and contract number (if applicable),

b. Identification of the contract's periods of performance, and

c. Identification of the portfolio of services managed under the contract or agreement.

(2) Gate Criteria 2: Small Business Participation

(i) The Offeror shall attest that it will meet the minimum mandatory Total Small Business Participation goal of 35% of total contract value as well as the various percentages for each subcategory.

Total Small Business-35% Small Disadvantaged Business-5% Woman Owned Small Business-5% HUB Zone-3% Service-Disabled Veteran Owned Small Business-3% Veteran Owned Small Business-3%

(b) Volume 1-Technical Proposal-(Non-Cost/Price Factors) Technical Approach-Content (Factor 1).

(1) Subfactor 1.1: Systems Engineering

(i) The Offeror shall provide subsections of its draft NMCI Systems Engineering Management Plan (SEMP) (CDRL A052), in accordance with PWS sections 3.3.7.1 and 3.3.7.1.3.1, that addresses the following sections of the NEN Systems Engineering Plan (SEP):

a. 4.4.2 Technical Management Processes

b. 4.4.8 Technical Reviews

c. 4.5.10 Technical Refresh Planning Guidance

d. 4.7.1 Model Based Systems Engineering

e. 4.7.6 System Verification and Evaluation Testing

(ii) The Offeror shall provide its approach to NMCI Network Transformation/Modernization in accordance with PWS section 3.3.7.1.1.1.

(2) Subfactor 1.2: Network Transformation/Modernization Sample Exercise

(i) The Offeror shall provide an overarching approach to its NMCI Network Transformation/Modernization Plan (NT/MP) utilizing the processes described in Subfactor 1.1, and in accordance with PWS section 3.3.7.1.1.2.

(ii) The Offeror shall provide a notional NMCI Network Transformation/Modernization Plan (NT/MP) that consists of project descriptions incorporating end-to-end solutions for transformation/modernization that leverages existing infrastructure where applicable, and addresses:

a. A long-term strategy for transformation and modernization, addressing network, storage and compute, which aligns with the Navy Enterprise Operations Support System (NOSS) Framework that achieves the following Government objectives and provides prioritization recommendations that maximize investment and optimize benefit to the Government:

i. Optimization of services performed on both NMCI and ONE-Net as part of the ONE-Net convergence activities in accordance with PWS section 3.4.5 ONE-Net Convergence, and PWS section 3.3.6.1 Continual Service Improvement.

ii. Unified Capabilities that allow ubiquitous access to classified and unclassified collaboration, messaging, voice, video, and storage from multiple endpoints for all users.

iii. User self-provisioning for future infrastructure services for multiple hypervisors/containers and public and/or DoD cloud platforms.

iv. Automation/Orchestration – Automation of tasks such as configuration, coordination and management of SW and SW interactions in cloud computing environments.

v. Dynamic allocation of network bandwidth resources.

vi. Tech refresh that addresses End of Life/End of Service HW and SW.

vii. Alignment to Windows as a Service.

viii. Compliance as Code – Implementing continuous compliance monitoring as required in PWS section 3.3.7.1.1.2.a.

b. Project descriptions for ONE-Net Convergence activities to complete ONE-Net Convergence 24 months after contract award.

c. Prioritization recommendations for all remaining project descriptions that maximize investment and optimize benefit to the Government.

d. Existing/planned Government solutions that provide similar capabilities, such as DISA provided services, where these services may be most effective and/or efficient for Navy.

e. Ensuring costs for sustainment of Navy base services remain at or below baseline, or where above baseline, are fully justified as part of the return on investment and benefit description.

(iii) The Offeror shall assume a Government Network Transformation Modernization budget of $125M annually, which includes development, procurement, integration and deployment costs, but not sustainment costs.

(iv) The Offeror shall ensure that each project description submitted with its notional NT/MP consists of the items listed below and is aligned to the Rough Order of Magnitude Price Estimate provided in the cost volume.

a. Project narrative to include capability provided and examples of previous implementation

b. Project justification and how it relates to achieving the Government objectives to include benefit to the Government/Return on Investment

c. Rough Order of Magnitude Price Estimate for development, procurement and deployment provided in the cost volume

d. Schedule, including design, development, integration and deployment phases

e. Risks and opportunities for each phase of the schedule to include risks and opportunities in sustainment

f. Interdependencies with other projects and Government activities

(c) Volume 2-Management Proposal-(Non-Cost/Price Factors) Management Approach-Content (Factor 2).

(1) Subfactor 2.1: Program Management Plan: The Offeror shall provide subsections of its draft Program Management Plan (CDRL A004) that addresses the following sections of the DID-MGMT-80004A:

(i) 3.3 Organizational Structure

(ii) 3.4 Program Management

(iii) 3.5 Methodology, paragraph 3.5.a, only

(2) Subfactor 2.2: Network Operations

(i) The Offeror shall describe its approach for Navy Enterprise Service Operations specifically:

a. Managing Network Operations Center (NOC) services in accordance with PWS 3.3.5.1.2.d; f; and g

b. Managing Security Operations Center (SOC) services in accordance with PWS 3.3.5.1.3.g

c. Conducting maintenance activities in accordance with PWS 3.3.7.4.1.c and PWS 3.3.7.4.1.f.

d. Providing a global service desk solution in accordance with PWS 3.3.2.1.a. and b.

e. Providing a solution in executing PWS 3.3.6.11.a.(viii), detailing the use of data in minimizing events, reducing critical incident volume and severity.

(ii) The Offeror shall describe its approach for USMC Operations Support Services (OSS) specifically:

a. Describe its approach to meeting the labor category qualifications in Labor Rate Card and Material Discounts (Attachment J-13).

b. Identify the planned recruiting and retention activities under this contract to ensure USMC labor support requirements, as identified in USMC OSS (Attachment J-24)are met; and include any specific incentives for the junior labor categories.

(3) Subfactor 2.3: Tools Management and Data Access

(i) The Offeror shall describe its innovative approach to providing historical and near real-time network data in a fashion that is accessible to multiple stakeholders performing multiple varied missions in accordance with PWS section 3.3.5.8 Tools and Data.

(ii) The Offeror shall describe its innovative approach to leverage advanced data management technologies, such as Business Intelligence and machine learning, to address the event, incident, and problem management challenges of data accessibility, capture, analysis, search, sharing, transfer, visualization, querying and updating, in accordance with PWS sections 3.3.5.1.2, 3.3.6.11, 3.3.6.12 and 3.3.6.13.

(iii) The Offeror shall describe its approach and strategy for the full lifecycle of provisioning, operating, maintaining, and improving the IT Service Management and Network Management tools in accordance with PWS section 3.3.5.8 Tools and Data, and NGEN Master Tools Library (Attachment J-29). The Offeror shall also describe its approach to managing tool/technology roadmaps, requirements traceability, change management and its approach to utilize tools to directly support execution of ITSM processes.

(4) Subfactor 2.4: Supply Chain Risk Management

The Offeror shall describe its approach to supply chain risk management. The Offeror’s description must identify specific practices currently in place to reduce supply chain risk. The Offeror will use the RFP, PWS, and NEN Program Protection Plan (PPP) as resources for developing its SCRM approach. At a minimum, the Offeror’s proposal shall address its approach to mitigating and/or eliminating the risk of sabotage, maliciously introduced unwanted function, or other subversion to the design, integrity, manufacturing, production, distribution, installation, operation, or maintenance of devices delivered to the Government.

(d) Volume 3-Past Performance Proposal-(Non-Cost/Price Factors) Past Performance-Content (Factor 3).

(i) The Government will assess the performance of the Offeror, and its major subcontractors (greater than $50 million) on previous contracts of similar type and complexity to the work required herein.

(ii) Offerors are advised that:

a. The Government may contact any or all references listed in the proposal and other third parties, unreferenced customers, agencies, consumer protection organizations, etc. for performance information; or use any other data available such as, Contractor Performance Assessment Reporting System (CPARS). The Government reserves the right to use any such information received or identified as part of its evaluation of the Offeror’s past performance.

b. In the evaluation of past performance, the Government reserves the right to use past performance information obtained from sources other than those identified by the Offeror, including, but not limited to, Federal, State, and local Government agencies, Better Business Bureaus, published media and the Past Performance Information Retrieval System. This information may include, but is not limited to, Award Fee letters and related reports, Letters of Concern and any performance notifications whether positive or negative.

c. If the Offeror omits projects of which the Government evaluation team is aware or becomes aware, the Government may seek customer assessments from the relevant organizations.

(iii) Offerors shall submit a Contractor Past Performance (Self-Assessment) regarding at least three (3) and no more than five (5) previous contracts completed and/or ongoing by the Offeror and each of its major subcontractors during the last five (5) years. These contracts shall reflect similar work scope to the efforts described in this solicitation. As a part of this submission, Offerors shall describe the extent to which personnel who contributed to these previous efforts and will be supporting the resultant contract.

(iv) Relevant past performance includes performance of a contract of same or similar requirements as defined in this Solicitation.

(v) At least one (1) previous Federal Government contract reference must be provided.

(vi) Contractor Past Performance (Self-Assessment).

Each submitted self-assessment shall include the Customer’s name and address along with PCO/ACO/COR name, telephone number, and email address; Contract Number, Title, and Type; Contract Award Date; Awarded Cost/Price; final or projected final, Cost/Price; description as to whether the Offeror was the prime or a subcontractor on the effort; the Offeror's record of forecasting and controlling prices; Original and Final or projected final delivery schedule; the Offeror's adherence to contract schedules, including the administrative aspects of performance; Offeror's record of providing quality products and services, conforming to specifications and standards of good workmanship; and effective management relating to business relationships, the Offeror's commitment to Customer satisfaction.

(vii) Contractor Performance Evaluation Survey (CPES).

The Offeror shall send a copy of the CPES (in the format specified at Attachment L-2) to either the PCO/ACO/COR for each contract submitted for consideration. The Offeror shall inform those individuals sent the CPES that the CPES forms must be completed and submitted directly to Ms. Kimberly Reavis, Procuring Contracting Officer via email at Kim.reavis@navy.mil no later than the due date and time for receipt of proposals. In its proposal, the Offeror shall provide a consolidated contact information list for the individual(s) who were asked to complete a CPES. The contact list is not included in the total page-count for Volume 3. The Government reserves the right to contact references for verification of information or additional information.

(e) Volume 4-Transition Proposal-(Non-Cost/Price Factors) Transition Approach-Content (Factor 4).

(1) Subfactor 4.1: Phase-In Services. The Offeror shall provide its general approach to simultaneously managing and executing the transition plans outlined in Subfactors 4.2, 4.3, and 4.4.

(2) Subfactor 4.2: NMCI Transition Plan. The Offeror shall provide an NMCI Transition Plan in accordance with CDRL A001 (NMCI Transition Plan) and PWS section 3.4.2 that includes a schedule to achieve Assumption of Full Operational Responsibility (AFOR) within nine (9) months after contract award. The plan shall be developed in accordance with the Government provided Navy Site Listing (Attachment J-4). The plan shall address the people, tools, and processes required to achieve AFOR for all services listed in the PWS sections 3.1, 3.2, and 3.3. The Offeror shall identify any risks and mitigation plans associated with the transition timeline.

(3) Subfactor 4.3: ONE-Net Transition Plan. The Offeror shall provide a plan in accordance with CDRL A002 (ONE-Net Transition Plan), PWS section 3.4.3, Navy Site Listing (Attachment J-4), and ONE-Net Transition Support Services Manning (Attachment L-4). The plan shall address the services, people, and tools associated with transitioning ONE-Net within nine (9) months of contract award. The Offeror shall identify any risks and mitigation plans associated with the transition timeline.

(4) Subfactor 4.4: USMC Transition Plan. The Offeror shall provide a plan in accordance with CDRL B040 (MCEN Transition Plan), PWS section 3.4.4 and USMC Operational Support Services (OSS) (Attachment J-24). The plan shall address the services, people, and tools associated with transitioning the MCEN within 90 days of contract award. The Offeror shall identify any risks and mitigation plans associated with the transition timeline.

(f) Volume 5-Cost/Price Proposal-Content (Factor 5).

(1) Cost/Price Proposal Organization. Cost/Price Proposal shall consist of the following sections:

(i) Volume 5-Section 1: Cost/Price Proposal Methodology and Basis of Estimate (BOE)

(ii) Volume 5-Section 2: Cost/Price Evaluation Template (Attachment L-3), Labor Rate Card and Material Discounts (Attachment J-13), Network Infrastructure Services Rate Card (Attachment J-14), Travel Rate Card (Attachment J-17), USMC OSS Cost Format (Attachment L-1), and ONE-Net Estimated Transition Support Services Manning (Attachment L-4)

(iii) Volume 5-Section 3: Section B CLINs

(iv) Volume 5-Section 4: Network Transformation/Modernization ROM Price Estimate

(v) Volume 5-Section 5: Non-Commercial Data and Computer Software Restrictions

(2) Cost/Price Proposal-General:

(i) The Offeror shall complete Section B and all RFP Attachments in Sections J and L associated with the price proposal, including all worksheets within Excel workbooks. For information required where no Government format is provided, the Offeror shall provide the required information in the Offeror’s chosen format. All calculations shall be provided in the Excel-based attachments. There are no specific font-size requirements for the information provided in the price proposal, but all information provided in hard copy shall be easily legible.

(ii) All price information shall be submitted in Then-Year dollars (TY$). If the Offeror desires to provide additional information not specifically required in the price attachments, the information may be supplied in the Offeror’s chosen format.

(iii) All data provided by the Offeror, whether in the Offeror’s format or a specified Government format, shall be traceable throughout the proposal. For example, all data provided at lower levels in the Cost/Price Volume should add up to the totals on the Cost/Price Volume’s summary formats as well as the prices in Section B; the information shall also be traceable to that provided in the Technical and other volumes (where applicable). Where the traceability is not clear, it shall be explained.

(iv) The Offeror shall provide proposed discount rates in Labor Rate Card and Material Discounts (Attachment J-13) to be evaluated against an estimate of material categories purchased via the rate card. The rate shall be consistent with Section B-2, Material Discounts.

(3) Section 1-Cost/Price Proposal-Methodology and Basis of Estimate.

(i) The Offeror shall provide priced and unpriced Basis of Estimates (BOEs), including a narrative and supporting workbooks, used to establish its proposed cost/prices. The BOEs shall clearly and concisely state the scope, pricing basis, allowances, assumptions, exclusions, risks and opportunities, and any deviations. The Offeror’s BOEs shall demonstrate its efforts to respond to the solicitation and the cost/prices reflected in Cost/Price Evaluation Template (Attachment L-3), USMC OSS Cost Format (Attachment L-1) and applicable Rate Cards are reasonable for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the approach described in the Offeror’s management/technical proposal. Any inconsistency, whether real or apparent, between promised performance and cost/price should be explained in the BOEs. For example, if the intended use of new and innovative procedures, processes or tools is the basis for an abnormally low estimate, the nature of these innovative efforts and their impact on cost/price must be explained and fully justified. As another example, if the Offeror's investment is the basis for an abnormally low estimate, this must be explained. Any significant inconsistency, if unexplained, raises a question as to the Offeror’s understanding of the nature and scope of the work required and the ability to perform the contract. If the cost/price information demonstrates that the Offeror does not understand the level of work necessary to successfully meet the requirements, the Government may consider that a cost/price proposal submitted, as a result of this solicitation, is unrealistically low.

(ii) In addition to the narrative, the Offeror shall provide the following five (5) workbooks for both priced items and rate cards, which will summarize and quantify the narrative information. Each workbook may have multiple worksheets as determined by the Offeror. The five (5) workbooks (*.xlsx files) shall be segregated as follows, and shall include the following information:

a. Labor workbook for FFP CLINs (fully burdened):

1. Reference the applicable PWS sections/subsections.

2. Reference the applicable CLIN for each PWS section/subsections in item 1.

3. List of all Labor Categories for each CLIN in item 2.

4. Staff-hours for each Labor Category in item 3 by applicable base year and/or option years.

b. Bill of Materials (BOM) workbook:

1. Reference the applicable PWS sections/subsections.

2. Reference the applicable CLIN for each PWS section/subsections in item 1.

3. List of all BOM elements for each CLIN in item 2.

4. For each BOM element in item 3 include:

i. Type (i.e. hardware, software, maintenance, etc.).

ii. Brief description/purpose of BOM element.

iii. BOM element Quantity (per applicable base year and/or option year).

iv. BOM element Cost (per applicable base year and/or option year).

c. Travel workbook:

1. Reference the applicable PWS sections/subsections.

2. Reference the applicable CLIN for each PWS section/subsections in item 1.

3. Total travel costs (per applicable base year and/or option year)

d. Other Direct Costs (ODC) workbook (Only applicable to Cost-Reimbursement type CLINs):

1. For each ODC element include, a description and total cost.

2. Identify ODC by entity (Prime or subcontractor) by name. If the subcontractor is submitting proprietary BOEs, the Prime shall include a summary element.

3. For each row in item 1, reference a single applicable PWS section/subsection, single CLIN.

e. Direct Labor workbook and supporting information (Information supporting the reasonableness of proposed labor rates):

1. Explanation of Direct Labor Categories – The Offeror shall provide an explanation of any direct labor categories contained in its proposal which apply to Cost-Reimbursement type CLINs. For any labor category proposed that is covered by the Service Contract Act (SCA), the Offerors shall provide the SCA occupation code, title, and identify the applicable wage determination.

2. Explanation of Direct and Indirect Allocation Bases – The Offeror shall provide an explanation of any direct and indirect allocation bases used in its proposal which apply to Cost-Reimbursement type CLINs.

3. A buildup of fully burdened labor rates (excluding Fixed-Fee).

4. Direct and Indirect Rate History – The Offeror shall provide historical rates for the last three (3) fiscal years for any rate included in the cost proposal.

5. Offeror Cost Accounting System (CAS) Disclosure(s) as required in Section K, Cost Accounting Standards Notices and Certification. NOTE: May be provided in a separate PDF file.

6. The Offeror shall also provide copies of correspondence from DCAA or DCMA regarding the most recent approval of rates and/or systems, such as Forward Pricing Rate Agreements (FPRAs), Forward Pricing Rate Recommendations (FPRRs), Provisional Billing Rates (PBRs), Accounting System Approval, etc. NOTE: May be provided in a separate PDF file.

(iii) The Offeror shall provide an unpriced BOE, with corresponding spreadsheets, as described above; however, no pricing/cost information shall be included. The unpriced BOE will be provided to the technical evaluators to provide additional insight into the Offeror’s Technical and Management approach for their consideration in evaluating Factor 1 (Technical Approach), Factor 2 (Management Approach) and Factor 4 (Transition Approach) including the Subfactors.

(iv) The Offeror shall document in this Section where the proposed rates used for inputs to Labor Rate Card and Material Discounts (Attachment J-13) have been used in other contracts, or shall demonstrate that its rates are consistent with those actual rates or describe both the source of rate and how the resulting rate was established. The Government will only evaluate the labor categories in the Labor Rate Card and Material Discounts (Attachment J-13).

(v) If the Offeror provides information in other Proposal Volumes that the Offeror believes will significantly assist the Cost/Price Team in evaluating and/or understanding the Cost/Price Volume, the Offeror shall provide a cross-reference statement in the Cost/Price Volume that indicates the Volume, page number where the information can be located, and explain its significance in evaluating the Cost/Price Volume.

(4) Section 2-Cost/Price Evaluation Template (Attachment L-3), Labor Rate Card and Material Discounts (Attachment J-13), Network Infrastructure Services Rate Card (Attachment J-14), Travel Rate Card (Attachment J-17), USMC OSS Cost Format (Attachment L-1), and ONE-Net Estimated Transition Support Services Manning (Attachment L-4):

(i) The Offeror shall complete all fields per the instructions provided in the Cost/Price Evaluation Template (Attachment L-3).

(ii) The prices in Cost/Price Evaluation Template (Attachment L-3) shall match those which the Offeror has priced in the CLIN pricing tables in Section B and be consistent with the instructions contained in the Attachment L-3. The Quantity (QTY) column reflects the Government’s reasonable estimates for evaluation purposes only.

(iii) The costs proposed in Cost/Price Evaluation Template (Attachment L-3) shall be consistent with cost/price in Section B, USMC OSS Cost Format (Attachment L-1), and ONE-Net Estimated Transition Support Services Manning (Attachment L-4).

(iv) The pricing proposed in ONE-Net Estimated Transition Support Services Manning (Attachment L-4) shall be consistent with the labor rates proposed in Cost/Price Evaluation Template (Attachment J-13).

(v) The Offeror shall complete all other Rate Card attachments in accordance with the instructions set forth in the attachment.

(5) Section 3-Section B, CLINS. The Offeror shall provide pricing for all priced CLINs in Section B.

(6) Section 4- Network Transformation/Modernization ROM Price Estimate: The Offeror shall provide enough detail in the BOE for the Government to determine the NT/MP proposed in RFP Section L-4(b)(2) Subfactor 1.2, does not exceed the ceiling amount of $125M annually.

(7) Section 5-Non-Commercial Data and Computer Software Restrictions: The Offeror shall submit a table (hereinafter the CLIN 0096 Table), as listed below, identifying any and all non-commercial technical data (TD) or computer software (CS) that the Offeror proposes to deliver with less than Government Purpose Rights (GPR). For each line item listed in the CLIN 0096 Table, Offerors are encouraged to include a price at which the Offeror would provide GPR. For any line item in the CLIN 0096 Table for which the Offeror does not provide a price for GPR, the Offeror shall provide a price to implement an alternative solution which does not entail delivery of non-commercial TD or CS with less than GPR.

a. In order to list the price for the GPR, or the alterative solution for each CLIN 0096 Table line item, Offerors shall add a price column to the CLIN 0096 Table and shall clearly designate whether each line item price is for GPR or for an alternative solution that does not entail delivery of non-commercial TD or CS with less than GPR.

b. The CLIN 0096 price in Section B and in the Cost/Price Evaluation Template (Attachment L-3) shall reflect the total of the items priced in the CLIN 0096 Table. The CLIN 0096 Table will be made an attachment (Data Rights Table and Alternate Solution Plans, Attachment J-32) to any resulting contract.

*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

***Enter asserted rights category (e.g., government purpose license rights from a prior contract, rights in SBIR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate.

*****Enter “none” when all data or software will be submitted without restrictions.

(g) Volume 6-Cover Letter and Contract Documents.

(1) Cover Letter. The Offeror's proposal shall include a cover letter on the Offeror's letterhead stationery that:

(i) Acknowledges receipt of all SF30s if any amendments are issued to the solicitation.

(ii) References the solicitation number and acknowledge that it transmits its offer in response to the solicitation.

(iii) Identifies all enclosures being transmitted as part of the response to the solicitation.

(iv) States: (1) Commercial and Government Entity (CAGE) number, (2) DUNs Number, (3) Taxpayer Identification Number (TIN), (4) address(es) of the location(s) at which the Offeror intends to perform the proposed effort, and (5) that the proposal is valid 270 days after proposal due date.

(v) Certifies that the Offeror intends to be unconditionally bound by the terms and conditions of the resulting contract.

(vi) Certifies that the electronic and paper copies of its proposal are identical.

(vii) Is physically signed by an executive of the Offeror who possesses authority to bind the Offeror contractually, and states that the executive has this authority.

(2) Contract Documents. Each of the following Contract Documents are required in response to this solicitation. The submission of each of these documents represents minimum requirements, as applicable. Failure to submit complete responses to each of the following Sections, if applicable, may result in rendering the Offeror ineligible for contract award.

(i) Section 1-Completed Contract and Representations and Certifications. The Offeror’s proposal shall provide a completed proposal to include the physically signed SF33, Sections B-K, and any SF30 amendments. In addition, the Offeror shall complete and submit all representations and certifications as required by this solicitation.

(ii) Section 2-Proposal Cross-Reference Matrix. Each Proposal shall contain a matrix that cross-references each Evaluation Factor and Subfactor contained in Section M, the information requested in Section L, and the SMIT Solicitation and attachments, including PWS, with the applicable pages and paragraph(s) in the Offeror’s proposal. The matrix will use the Factors and Subfactors in Section L as the key reference. There is no page limit for the Cross Reference Matrix.

(iii) Section 3-Teaming agreement, if applicable. The Offeror shall submit a copy of its teaming agreement for major Subcontractors (greater than $50 million of total contract value).

(iv) Section 4-Proprietary Data Protection Agreements (PDPAs).

a. Contractor support personnel from the below listed companies under existing contracts, will be used for administrative purposes only.