ITESS_Solicitation_N32205-18-R-1002_Amendment_0001.pdf

N3220518R1002

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See Amendment Summary for a complete summary of changes

1. CONTRACT ID CODE PAGE OF PAGES

J 1 44

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

16C. DATE SIGNED

BY 16-Apr-2018

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

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

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

X 9B. DATED (SEE ITEM 11)

19-Mar-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

16-Apr-2018

CODE

MILITARY SEALIFT COMMAND NORFOLK

471 EAST C STREET, BLDG SP-64 NAVAL STATION N

NORFOLK VA 23511

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 19-Apr-2018 04:00 PM to 26-Apr-2018 04:00 PM.

The following have been added by full text:

AMENDMENT SUMMARY

Amendment 1 Summary

1) The Solicitation closing date has been revised to 26 April 2018 at 4:00PM EST.

2) CDRL A107 was intended to be part of this Solicitation and has been uploaded as part of this Amendment along with the answers to all questions submitted prior to the ending of the question submittal date.

3) The Government is providing Attachment J-0013 as an attachment to the following amendment.

4) The Government intended to list paragraph 4.1.8 within CDRL A110. The following Amendment to the

Solicitation will provide a revised CDRL A110 attachment appropriately.

5) The Contract Management Plan and the Configuration Management Plan were crossed. A CDRL for the

Configuration Management Plan will be included.

6) The Government has added the summary tab as stated in the Solicitation and the revised Attachment has been added as part of this Amendment.

7) The Government has added the highlighted areas in Attachment 4 as stated in the Solicitation and the revised Attachment has been added as part of this Amendment.

8) The following Amendment includes the minimum requirements for all non-key personnel listed in

Attachment 4.

9) The Government has added the appropriate wage determination as an attachment included within the following Amendment to the Solicitation.

10) The CLIN numbers have been added to Attachment 4 accordingly and a revised Price Proposal Spreadsheet has been uploaded within this Amendment.

11) The Government requires font size to be twelve (12) point font with one (1) inch margins on each side.

These have been added to the Solicitation instructions within this Amendment. The Government will enable offerors to determine the appropriate requirements for the table and graphics.

12) The Performance Questionnaire attachment has been revised accordingly and attached as part of this

Amendment.

13) The Past Performance Data Sheet attachment has been revised accordingly and attached as part of this

Amendment.

14) Factor 3 Price price information has been updated.

15) Resolved the discrepancy between the PWS and CDRLs and addressed the correct timeframe for the deliverables. Attached revised CDRLs A209, A216, A501, A601, and A708.

The following have been modified:

52.212-1 ADDENDUM

52.212-1 (ADDENDUM) ADDITIONAL INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS

Any inconsistency between FAR Provision 52.212-1 and the Addendum to FAR 52.212-1 shall be solved by giving precedence to the Addendum to FAR 52.212-1.

A. Paragraph (c) of FAR Provision 52.212-1 is amended to read: Period of acceptance of offers. The offeror agrees to hold the prices in its offer firm for 120 days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

B. Paragraph (b) of FAR Provision 52.212-1, Submission of Offers, is amended as follows:

SOLICITATION PROVISIONS

Contractor will be required to fill out and return the following FAR and DFARs Provisions and Clauses:

CLAUSE TITLE DATE

52.209-7 Information Regarding Responsibility Matters Jul 2013

52.212-3 Alt I Offeror Representations and Certifications –

Commercial Items

Jan 2017

252.225-7000 Buy American – Balance of Payments Program

Certificate – Basic

Nov 2014

252.247-7022 Representation of Extent of Transportation by

Sea

Aug 1992

PROPOSAL PREPARATION INSTRUCTIONS

A. Proposal Submittal and Inquiries.

1. Proposals shall be received prior to the closing date and time identified on the SF 1449, electronically at the following address:

James.Findlay@Navy.mil

2. The subject line of the email submission shall read, “N3220518R1002 // [Offeror’s Name] // Part

[X] of [Y],” (Part X of Y is utilized to indicate multiple emails as part of the submission where X is the email number and Y is the number of total emails to be received). NOTE: to ensure attachments are properly received, offerors are encouraged to limit the sum total size of a single email to 10 megabytes (MB).

3. Submissions shall not contain any classified material. It is the sole-responsibility of the offeror to ensure that the files submitted are virus free and can be opened and read by the Government.

4. The point of contact responsible for supplying additional information and answering all inquiries is the Contract Specialist. Address all questions or concerns the offeror may have to the Contract

Specialist, James Findlay. All questions concerning the solicitation shall be submitted in writing via email to:

James.Findlay@Navy.mil

All questions shall be received no later than 20 calendar days after issuance of the solicitation.

Offerors are cautioned that any question received after this deadline may not receive a response.

B. General Instructions.

1. The selection of a source for award purposes will be conducted utilizing source selection

(negotiated) procedures as delineated in FAR Subpart 15.3. Offerors will be evaluated using the criteria under FAR Provision 52.212-2, “Evaluation – Commercial Items.” Noncompliance with the Request for Proposal (RFP) requirements may hamper the Government’s ability to properly evaluate the proposal and may result in elimination of the proposal from further consideration for contract award.

mailto:James.Findlay@Navy.mil mailto:James.Findlay@Navy.mil

2. The submission of the documentation specified below will constitute the offeror’s acceptance of the terms and conditions of the RFP and concurrence with the contract type.

3. It is the Government’s intention to award without discussions. Offerors are encouraged to submit their best technical proposal and prices in initial proposals. In accordance with FAR 15.306, should discussions become necessary, the Government reserves the right to hold them. If this occurs, a competitive range will be determined and offerors notified. The competitive range may be limited for purposes of efficiency in accordance with FAR 15.306(c)(2). Proposals containing unacceptable ratings may be included in the competitive range provided they can be made acceptable as a result of discussions.

4. Instructions outlined in paragraph C below, prescribe the format for the proposal and describe the approach for the development and presentation of proposal data. These instructions are designed to ensure the submission of information needed to allow for evaluation of proposals.

5. If an offeror believes that the requirements in these instructions contain an error, an ambiguity, omission, or are otherwise deemed unsound, the offeror shall immediately notify the Contract

Specialist in writing with the supporting rationale. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposals, as received, without discussion.

6. All referenced documents for this solicitation are available on the Federal Business Opportunities

(FBO) website at https://www.fbo.gov. Potential offerors are encouraged to subscribe for real-time email notifications when information has been posted to the https://www.fbo.gov/ website for this solicitation. If any necessary documents are not available on FBO, please notify the Contract Specialist via email.

7. Debriefings. The Contracting Officer will promptly notify offerors if the decision to eliminate their proposals from the competitive range, whereupon an offeror can request and receive a debriefing in accordance with FAR 15.505. The Contracting Officer will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506.

Upon such notification, unsuccessful offerors may request and receive a debriefing. Any offeror requesting a debriefing must make the request in accordance with the requirements of FAR

15.506.

C. Proposal Preparation Instructions

1. Offeror’s proposal shall consist of four (4) separate volumes: General (Volume I), Technical

(Volume II), Past Performance (Volume III), and Price (Volume IV).

2. Exceptions. Offerors are required to meet all solicitation requirements, such as terms and conditions, representation and certifications, and technical requirements, in addition to those identified as evaluation factors and subfactors. Failure to meet a requirement may result in an offeror being ineligible for award. If the offeror finds it necessary to take exception to any of the requirements specified in this solicitation, the offeror shall clearly identify the applicable Volume and exceptions with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Offerors are cautioned that taking an exception may render the offer ineligible for award. It is recommended that the offeror contact the Contracting Officer immediately prior to solicitation closing, upon identifying an area that may result in an exception.

3. Proposal Format

a. The proposals shall be organized into four (4) separate volumes. Each file sent via email shall include the volume number in the document title. It is permissible to include multiple volumes within one (1) email submission, however a single file can contain no more than one (1) volume.

b. Files shall be submitted in one (1) or a combination of the following formats: Adobe

PDF, Microsoft Word, PowerPoint, and/or Excel. Files should be consistent with twelve

(12) point font and one (1) inch margins. No file shall be locked. The file names shall consist of the volume number, factor, tab, company name, and state “initial” (for the first submission) and “Revision X” (for later submissions, if necessary) where X indicates the number of the revision.

c. The table below shows detailed page limits for submissions:

Table 1 – Volume Page Limits

VOLUME TITLE PAGE LIMIT

I General N/A

Tab 1 Cover Letter 2

Tab 2 Completed Attachments N/A

II Technical 60

III Past Performance N/A

IV Price N/A

d. Proposal Limitation. The proposal shall not exceed the limits stated above. If the page limits are exceeded, the pages in excess of the limit shall be removed and remain unread.

The Government will not accept any changes to the contractor’s proposal after the closing date of the solicitation (See FAR 15.208 for further information regarding late proposals). If discussions become necessary, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

e. Page limits include: all appendices, charts, graphs, diagrams, tables, photographs, drawings, etc.

f. Page limits do not include: covers for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, cross reference indices, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. Pages will be counted if they contain any other information, i.e., diagrams, extraneous data, etc. Pages marked, “This page intentionally left blank,” will not be counted.

g. In the event that the offeror creates ambiguity in their numbering of pages, the

Government may exercise its own discretion in counting pages.

D. Proposal Content

1. Volume I – General. Offerors are required to submit: (TAB 1) a Cover Letter; (TAB 2)

Completed Attachments, which will consist of a completed SF 1449 to include acknowledgement of amendments, if applicable; completed Representations and Certifications; provide the names of key personnel in accordance with Section 12 of the PWS, and Technical Non-Disclosure

Agreement.

Tab 1: The following information shall be provided in the cover letter:

a. Authorized Offeror Personnel: Provide the name, title, telephone number, and e-mail address of the individual who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government and who can answer questions regarding your quotation.

b. Company Information: The name, address, telephone number, Data Universal Numbering

System (DUNS) number, Commercial and Government Entity (CAGE) Code, and The

Company’s Small Business Size Standard under the applicable NAICS code.

c. Service Contract Act (SCA) Certification; The Offeror shall certify that it will comply with the Service Contract Act and Department of Labor Wage Determination

d. Agreement with Terms: A statement specifying the extent of agreement with all terms, conditions, and provisions included in the RFP. Offerors are to clearly detail any exceptions taken and the rationale for the exceptions taken to the RFP. Exceptions taken to the RFP may render the proposal unacceptable to the Government.

Tab 2: The following information shall be provided:

a. Completed Representations and Certifications. Offerors shall complete all applicable

Representations and Certifications, including FAR 52.212-3 and those provisions listed in the first table of this clause as well as the requirments included in DFARs 252.237-7024 NOTICE

OF CONTINUATION OF ESSENTIAL CONTRACTOR SERVICES (OCT 2010).

b. Signed acknowledgement of all RFP amendments. Offerors shall acknowledge all RFP amendments.

c. List of all key personnel names in accordance with Section 12.1 of the PWS.

d. Completed Form DD254 (Attachment 5) with applicable CAGE code

e. Technical Non-Disclosure Agreement. The offeror shall ensure that the required fields within the Technical Non-Disclosure Agreement (Attachment J-0016) are completed.

2. Volume II – Technical. The technical proposal will be the basis for assessing the offeror’s ability to understand the scope of the global material management services described in the solicitation.

FAR Provision 52.212-2 of the solicitation outlines the evaluation factors and defines the source selection evaluation criteria for evaluating the technical proposal. The technical volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the offeror’s proposal. Legibility, clarity, and coherence are very important. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet the requirements. Statements that the offeror understands, can, or will comply with the requirements;

statements paraphrasing the requirements or parts thereof; and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. Offerors shall assume that the Government has no prior knowledge of its facilities and experience, and will base its evaluation on the information presented in the offeror’s proposal.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired. The technical volume shall be organized according to the following general outline. Each Subfactor shall be submitted as its own Tab.

a. Subfactor A – Understanding of the Requirement:

The Understanding of the Requirement section shall describe the offerors understanding and strategy for fulfilling of the eight (8) major Task Areas in Section C of the Performance Work

Statement (PWS). Provide a written narrative of the Offeror’s proposed understanding and capability to perform the requirements of the PWS. The narrative shall include, but is not limited to, the elements set forth below:

a. Provide a detailed description of the approach, including a detailed step-by-step procedure and methodology which would be used in accomplishing each task

b. Identify reference documents that would be utilized to perform the SOW tasking

c. Identify any areas that may impact successful performance

d. Implementation plan that includes:

i. Manpower utilization to maintain an optimum level of support

ii. Warranty of work, if applicable

iii. Quality control of work product

iv. Quality assurance plan to monitor performance metrics

b. Subfactor B – Related Organizational Experience:

The Related Organizational Experience section shall describe the offeror’s corporate experience in providing services similar to those required by the Government. This section shall include a summary of general qualifications to carry out required tasks and ability to respond to the requirements detailed in the Statement of Work. Further, the organization undertaking the work must demonstrate low staff turnover, adherence to high quality control standards and budget limitations, and demonstrate the ability to meet project timelines.

The offeror shall describe its relevant experience in performing work similar in scope, size, and complexity to that described in the Performance Work Statement. Similar scope, size, and complexity are defined as follows: scope – type of work (e.g., work as identified in the PWS); size

– contract duration; and complexity – performance challenges and risk. The offeror’s description shall include:

a. Developing and implementing a Systems Engineering Management Plan (SEMP)

b. Developing and implementing an Enterprise Architecture (EA) Program

c. Developing and implementing an IA Program to implement and sustain appropriate IA management, operation, and technical controls and processes

d. Developing and implementing an In-Service Engineering Activity (ISEA) / Software

Support Activity (SSA)

e. Designing and deploying Information Technology (IT) systems and networks under a type Authorization to Operate (ATO) fully compliant with the Department of Defense

(DoD) Instruction 8510.01 Risk Management Framework (RMF)

f. Developing, implementing and maintaining an Information Technology laboratory for developing and sustaining Department of Navy (DoN) and similar Department of

Defense (DoD) accredited systems and networks

g. Developing and implementing an IT service management (ITSM) program capable of supporting Change Management (CM), Service Asset Configuration Management

(SACM) and Service Validation & Testing (SV&T)

3. Volume III – Past Performance. The past performance evaluation will be accomplished by reviewing aspects of an offeror’s recent and relevant past performance. Offerors may provide information for up to three (3) previous Government contracts whose effort is/was recent and relevant to the effort required by this solicitation.

a. “Recent” is defined as a contract in-progress or completed within the last three (3) years from the issuance date of this solicitation. If the offeror has not had three (3) Government contracts within the last three (3) years, information on recent and relevant subcontracts and/or commercial contracts may be submitted.

b. “Relevant” is defined as a contract or multiple simultaneous contracts cumulatively combined that is of similar scope, magnitude, and complexity to the requirements as set forth in this solicitation.

1) Scope: Experience in the areas defined in the PWS.

2) Magnitude: The measure of similarity of the volume of orders, dollar value, and/or duration of work actually performed under the offeror’s submitted contracts to this acquisition.

3) Complexity: The measure of the similarity of technical difficulty, managerial intricacy, and/or required coordination of efforts and disciplines performed by the offeror in its submitted contracts to this acquisition. For complexity, not only will the tasks performed by the offeror be considered, but also the offeror’s ability to coordinate tasks (e.g., concurrent performance requirements).

c. A Past Performance Data Sheet (Attachment 2) shall be submitted for each contract to be considered as past performance. Offerors shall provide a detailed explanation demonstrating the similarity of the contracts to the requirements of this solicitation; a detailed description of the work performed for the contract; and the role performed, including whether the offeror acted as a prime contractor or a subcontractor. Offerors are responsible for the accuracy of all data provided. Past performance information regarding predecessor companies, key personnel who have relevant experience and subcontractors that will perform major or critical aspects of the requirement may be provided as past performance submissions.

d. For each of the contracts the offeror describes in a Past Performance Data Sheet (Attachment

2), the offeror is requested to provide a Past Performance Questionnaire (Attachment 3) to a reference at the organization that awarded the contract. The reference, not the offeror, shall email the completed Past Performance Questionnaire BEFORE THE DUE DATE FOR

PROPOSALS directly to the Contract Specialist, James Findlay, at

James.Findlay@Navy.mil. Fax submittals will not be considered. The offeror, NOT THE

GOVERNMENT, is responsible for ensuring that the Government receives a sufficient number of questionnaires.

4. Volume IV – Price. Offerors shall provide a firm fixed price proposal using the provided Price

Proposal Spreadsheet (Attachment 4). Instructions for use:

a. The Price Proposal Spreadsheet includes seven (7) tabs; a summary tab and a tab for the base and each option period;

b. Offerors shall fill in the cells highlighted in yellow on the base and each option period tab.

c. Cells highlighted in green are pre-established formulas that will automatically update upon data being entered in the highlighted yellow cells;

d. For the purposes of the total evaluated price, the travel CLIN estimated price of

$1,175,000.00 is pre-filled in for the five (5) year ordering period of the resultant ID/IQ.

PERFORMANCE WORK STATEMENT

Performance Work Statement

Information Technology Engineering Support Services (ITESS)

1. Objectives

The objective of this contract is to obtain Information Technology (IT) Engineering Support Services that will assist the Military Sealift Command’s (MSC) Command, Control, Communications, and Computer Systems (C4S)

Division (N6) in providing and sustaining Department of Defense (DoD) and Department of the Navy (DoN) compliant technical C4S solutions for MSC through execution of the performance requirements defined in section

4.0, which will satisfy emerging requirements, enhance and develop IT capabilities in support of the MSC’s mission and assist in the development of governance to ensure IT capabilities align to MSC N6’s strategic Business Support

Plan, MSC N6’s technical architecture road maps, Department of Defense (DoD), and Department of Navy (DoN) mandates. The solutions primarily satisfy emergent cyber security mandates, CTOs, and technical refreshes for end of life hardware and software.

2. Scope

The Contractor shall provide IT Systems Engineering Support Services necessary to maintain, upgrade, test, develop and install new IT capabilities for MSC worldwide. All systems should be developed in accordance with the

Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and assessed using the applicable checklist and benchmarks available at http://iase.disa.mil/. Compliance with and variations of these requirements shall be documented in the appropriate form as described in Task Area 8, Information Assurance

(IA) Support.

The Contractor shall adhere and apply processes that are equivalent to those articulated by Capability Maturity

Model Integration (CMMI) for Development, Version 1.3 (CMMI-DEV, V1.3) capability level 3. The Contractor shall also provide disciplined systems engineering and project management practices in accordance with DoD

5000.02 and shall be in compliance with all DoD and Department of the Navy (DoN) mandates and instructions, and consistent with the work requirements identified within the following Performance Work Statement (PWS).

Unless otherwise indicated, copies of the specifications, standards, and handbooks referenced in this PWS are available upon request from the Document Automation and Production Service (www.defense.gov/pubs/), 700

Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094. MSC unique documents are available from the

Military Sealift Command Head Quarters (MSCHQ), Military Sealift Command 471 East Co Street, Bldg. SP 64, Norfolk, VA 23511-2419.

In the event of a conflict between the text of this document and the references cited herein, refer to the text of this document as it takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

The below Task Areas are identified within the following PWS and detailed herein to identify specific areas for performance under this requirement.

Task Area 1 – Contract Management

Task Area 2 – Project Management Support Services

Task Area 3 – Systems Engineering (SE) Support Services

Task Area 4 – In-Service Engineering Activity (ISEA) Support Services

Task Area 5 – MSC C4S Engineering Lab (MCEL) Support Services

Task Area 6 – IT Service Management (ITSM) Support Services

Task Area 7 – Enterprise Architecture (EA) Support Services

Task Area 8 – Information Assurance (IA) Support Services

3. Background

The Commander, Military Sealift Command (COMSC), in the role as single DoD manager for sea transportation, operates a worldwide command and a Government-owned fleet of approximately 116 ships that provides strategic and operational sealift to meet national defense objectives. In executing this mission, COMSC has implemented a

Program Management (PM) organization responsible for all life cycle matters pertaining to ships operating with the

Fleet Oiler (PM1), Special Mission (PM2), Prepositioning (PM3), Service Support (PM4), Sealift (PM5), Fleet

Ordnance and Dry Cargo (PM6), Afloat Staging and Command Support (PM7), and Expeditionary Fast Transport

(PM8). Each PM is responsible to COMSC for the operation, maintenance, and administrative management to provide mission-ready ships worldwide to the Command Sponsors. An inventory of the vessels by Hull Number is available at the following Internet address: http://www.msc.navy.mil/inventory/inventory.asp?var=hull. The fleet inventory and operating status change as required supporting sponsor mission requirements. The technical services provided though the ITESS contract provides support all MSC PM Organizations and all ship classes

Additionally, MSC has an extensive, global shore support organization that is focused on ensuring MSC’s fleet is operated and maintained in response to Fleet and Joint commander requirements. This shore infrastructure includes a headquarters element in Norfolk, VA, area command, and support units located in various locations as discussed in greater detail below. MSC’s operating model differs substantially from that practiced by the Navy’s combatant

Fleet. MSC ships are minimally manned, with shipboard personnel focused primarily on operations. MSC ships maintain higher levels of operational availability than Fleet units and operate in and out of ports not typically frequented by the Fleet. To balance the need for high operational availability with minimal crew manning, most troubleshooting, repair, sustainment, and maintenance tasks are provided by MSC shore personnel and the contractor workforce.

3.1 Current Operating Environment

The MSC current operating environment Afloat includes Government owned and operated ships, Government owned and Contractor operated ships, and Contractor owned and operated ships. Additionally, MSC employs an

Ashore infrastructure to support Afloat operations.

3.1.1 Ashore Environment

MSC’s IT environment operates using the following ashore networks including: Navy Marine Corps Internet

(NMCI) Continental United States (CONUS), Overseas Navy Enterprise Network (ONE-NET), Outside the

Continental United States (OCONUS), MSC Data Centers Continental United States (CONUS) and Afloat Network

Operations Center (ANOC) and Back-Up Network Operations Center (BNOC) (CONUS) for the continued operations of IT networks and systems support.

MSC’s ashore desktop operating environment is currently various Microsoft Windows environments.

MSC’s current ashore server operating environment includes Windows, UNIX and LINUX environments at the

Navy's Enterprise Data Center (NEDC), ANOC, and BNOC. Desktop applications include both standard off-the-shelf software products such as the Microsoft Office Suite and other common Windows software. In addition, MSC has a wide variety of Commercial-Off-The-Shelf (COTS), Government-Off-The-Shelf (GOTS), and legacy applications on user desktops including Standard Shipboard Automated Maintenance Management (SAMM), Shipboard Configuration and Logistics Information (ShipCLIP), Human Resource Management System

(HRMS/Department Head Afloat Management System DHAMS) and Financial Medical System (FMS), Budget

Preparation System (BPS), Logistics and Engineering System (LES)

3.1.2 Afloat Environment

The network infrastructure deployed on MSC ships includes a combination of MSC designed and developed systems as well as Navy Program of Record (POR) systems.

3.1.2.1 Shipboard Management Information System

Unclassified (SMIS-UNCLASS) Network, Attachment J-001, consists of workstations, primary and backup domain controllers, a database server, a switch, router, Dynamic Host Configuration Protocol (DHCP) and, accelerator, encryptor/decryptor, and link to the ANOC via satellite transport services. The MSC Shipboard SMIS-UNCLAS environment currently operates using Microsoft operating systems and Internet Explorer. The workstations utilize various Government-off-the-shelf (GOTS), Commercial-off-the-shelf (COTS), and Shipboard Management

Information System (SMIS) applications and software. Depending on the hull type of an MSC ship, the number of on board workstations can range from 15 to 120. This system is currently deployed on 68 MSC ships. MSC is currently in the process of providing a network upgrade to the deployed system and has numerous In-Service

Engineering Activity (ISEA) And Software Support Activity (SSA) activities ongoing including upgrading End of

Life (EoL) hardware and workstation operating systems. The SMIS-UNCLAS hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.2 Shipboard Management Information System

Classified AFLOAT Classified GOSUP(V)2 (ACG(V)2) Attachment J-002, includes a single Server running

Microsoft Exchange and thin-client workstations running Windows. Exchange servers and client desktops runs in a virtualized server environment. Data for Active Directory, DNS, and Exchange is replicated among local and remote domain controllers. This system is currently deployed on 34 MSC ships. MSC is presently executing a Non-

Recurring Engineering (NRE) project to upgrade and replace EoL hardware and software, which includes upgrades to servers, routers, storage and workstations, and server and workstation operating systems. Low-Rate Initial

Production (LRIP) and deployment scheduled FY18Q4. The SMIS-CLASS network hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.3 Shipboard Management Information System (SMIS)

SMIS Unclassified Mini (SMIS-UNCLASS-Mini), Attachment J-0013, Standalone workgroup with reach back to the Afloat Network Operations Center (ANOC). The system includes a desktop-laptop workstation environment.

This system is currently deployed on 21 MSC ships. MSC has recently completed the Low Rate Initial Production

(LRIP) phase of the system upgrade. Fleet deployment is in progress. The SMIS-UNCLAS-Mini hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.4 Shipboard Management Information System

SMIS Classified Mini (SMIS-CLASS-Mini), Attachment J-0014, Stand-alone workgroup with reach back to the

ANOC. The system includes a desktop-laptop workstation environment and is currently deployed on 56 MSC ships.

MSC has recently completed the LRIP phase of the system upgrade and MSC fleet deployment is in progress. The

SMIS-CLASS-Mini hardware and software technical refresh efforts will actively be supported through MSC N6 In-

Service Engineering throughout the duration of the life cycle.

3.1.2.5 Shipboard Management Information System

Unclassified Workgroup (SMIS-UNCLAS-WG), Is a standalone unclassified network deployed on MSC Ocean

Surveillance Ships. This system is currently deployed on 6 MSC ships. The SMIS-UNCLASS-WG hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.6 Integrated Shipboard Network System (ISNS) / Common PC Operating System Environment

(COMPOSE)

ISNS/COMPOSE is a Navy POR supported system that provides a common network infrastructure across multiple security domains and supports cross-domain and coalition operations. COMPOSE combines commercial-off-the-shelf (COTS) and government-off-the-shelf (GOTS) products to deliver directory services, e-mail, Web acceleration, office automation applications, collaboration tools and antivirus software for the Integrated Shipboard

Network System (ISNS), Combined Enterprise Regional Information Exchange System (CENTRIXS).

3.1.2.7 Standalone and Single PC Solutions

MSC deploys a number of standalone and single PC solutions:

PC to PC Transfer System (PPTS) - Provides 71 MSC ships with the capability to receive and transmit classified and unclassified data with the MSC Afloat Network Operations Center (ANOC) and the DoD Information Network

(DoDIN). Architecture includes a Commercial-Off-The-Shelf (COTS) workstation and a secure telephone (STE).

Navigation Aids (NAVAIDS) - Designed to provide navigation planning applications used by navigators to do celestial, chart planning, tides and waypoint marking. The NAVAIDS are loaded on a single, standalone workstation not connected to the network. The NAVAIDS are updated via CDs due to the size of the updates. The collection of NAVAIDS provides tidal predictions, celestial navigation, 3-D harbor visualizations, navigational routing, and electronic charting display capabilities.

The hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service

Engineering throughout the duration of the life cycle.

3.1.2.8 Integrated Navy Program of Record (POR) Systems

The integration and test for various Navy POR systems is required to interface with the MSC SMIS Networks.

Engineering Support Services for the Afloat environments include the following effort:

Naval Modular Automated Communications System (NAVMACS) - A ship-to-ship or ship/shore/ship message processing system. NAVMACS processes and records all incoming and outgoing message traffic and serves as an automated shipboard terminal for the Common User Digital Information Exchange System (CUDIXS). The

NAVMACS system architecture provides an RS-232 serial output capability which interfaces with MSC ACG(V)2.

Assured Command and Control (AC2) Modem integration efforts – The AC2 effort is required to integrate an additional modem onto MSC’s Next Generation Wideband (NGW) connected networks for network monitoring in a reduced operating status.

These hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service

Engineering throughout the duration of each system’s life cycle.

3.1.2.9 Pilot Systems

Engineering Support Services for the Afloat environments also includes system or software rapid prototyping efforts such as:

Visual Information (VI) Pilot-VI- Related to tactical level operations is required to be forwarded in a timely and accurate manner through the operational chain of command to help achieve operational objectives, support the combatant commanders' communication strategies and potentially counter propaganda. The ability to collect, process and disseminate VI is essential to achieve timely, factual information for operational decision-making, intelligence analysis and public information. me operations centers within 60 minutes of a reportable event.

Own Force Monitoring – Monitors the ship’s RF emissions and reports compliance with the emissions control

(EMCON) condition currently in effect.

The hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service

Engineering throughout the duration of the life cycle.

4. Performance Requirements

4.1 Task Area – 1 Contract Management

The Contractor shall provide all necessary personnel, administrative, financial, and managerial resources necessary for the performance of this task. The Contractor shall designate a single point of contact (POC) as the Contract

Manager (CM) who is responsible for fielding and responding to Government identified issues, concerns, or problems on this task order. The CM shall have the authority to direct the Contractor’s organization and make decisions for the Contractor’s organization in response to the Government identified issues, concerns, or problems. The CM shall be readily available to field and respond to the Government’s inquiries. The CM shall also be the designated POC to alert the Government to potential contractual/technical issues. Although Government staff may coordinate with other Contractor staff, the CM shall serve as the single Contractor POC responsible for resolving all issues, concerns, and problems. The CM position description and requirements are defined in section

12.1.

The Contractor shall provide a draft Contract Management Plan (CMP) in accordance with CDRL A103 to the MSC

Contracting Officer’s Representative (COR), Michele Gordon (757) 443-0873 Michele.Gordon@Navy.mil, at the

Kick-Off Meeting. Effective Contract Management will ensure that all contractor support assigned to this task are coordinating and leveraging processes already in place or being developed. This effort will include the overall management of Contractor resources assigned to the resultant contract as well as reporting to and direct interaction with the COR and the Alternate Contracting Officer’s Representative (ACOR), Earl Munrath (757) 443-3127

Earl.Munrath@Navy.mil. Contract Management support shall include the full range of project planning, resource management, risk assessment and mitigation, quality management, change control, and management of project deliverables consistent with industry best practices.

mailto:Michele.Gordon@Navy.mil mailto:Earl.Munrath@Navy.mil

4.1.1 Contract Kick-Off Meeting

The Contractor, after coordination with the Government, will schedule and coordinate a contract kick-off meeting to be held within five (5) business days of contract award. The Contractor, with the assistance of the Government, will develop an agenda for the meeting. The Contractor will ensure that all identified participants are notified of the meeting in advance. At a minimum, kick-off attendees shall include key contractor personnel (as defined in section

12) and key MSC personnel. At the kick-off meeting, the Contractor shall present its Transition Plan for overall contract management of the awarded task order in accordance with Contract Data Requirements List (CDRL)

A101. The Contractor shall develop and, after Government approval, distribute meeting minutes and action items within five (5) business days after the kick-off meeting in accordance with CDRL A102.

4.1.2 Contract Management Plan

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, a Contract

Management Plan that shall be used as a foundation for technical, resource, production and management planning. The Contractor shall develop and deliver a preliminary Contract Management Plan at the kick-off meeting in accordance with CDRL A103 and provide an updated Contract Management Plan within 30 calendar days after the kick-off meeting. The Contract Management Plan shall include the following summary information as well as any additional information deemed relevant by the Contractor:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

h. delivery procedures

i. tests

j. certifications

k. packaging

l. shipping

m. other

Data Item Description (DID) DI-MGMT-80004A may be used and tailored with the Government’s concurrence.

4.1.3 Contract Management Reviews

The Contractor shall prepare and submit a Contract Management Review (CMR) agenda to the COR five (5) business days prior to the CMR meeting in accordance with CDRL A104. The Contractor shall also prepare minutes for the CMR within five (5) business days after the meeting in accordance with CDRL A105. The Contractor shall prepare the actual CMR to be delivered the day of the review in accordance with CDRL A104. The CMR shall address current status to include current task order technical management and execution in comparison with task order planned activities, mitigation plans for under-performing areas, and all other risks, issues and concerns that may occur. The CMR shall summarize the previous three (3) months project execution and agreement with the

Contract Management Plan. The CMR will define the work planned and projected for the subsequent three (3) months. The first review will be conducted one month following award. Subsequent reviews will be conducted at monthly intervals. The CMR will occur 30 days from contract award, reoccurring monthly as determined by the

COR and Contractor PM.

4.1.4 Performance Measurement

The Contractor shall monitor performance standards and report monthly, via the Monthly Contract Status Reports.

The Contractor shall report performance metrics that shall provide status of resources, risk, deliverables, schedule, cost and hours by labor category for each reporting period. Metrics shall be reported for both monthly and aggregate/cumulative totals in accordance with CDRL A106. Data Item Description (DID) DI-MGMT-81861 may be used, tailored with the Government’s concurrence.

4.1.5 Performance Cost Reporting

The Contractor shall prepare and submit a report concurrently with each invoice presented for payment in accordance with CDRL A108. The Contractor shall report expenses that can be invoiced under the resultant contract. The report shall include labor expended for the period and cumulatively broken out to identify labor categories, labor rate, project ID and project phase and personnel utilized. Contractors must provide a cost summary sheet providing a breakout of monthly costs per effort and cumulative costs as they relate to the estimated amounts. The Contractor shall use the report format found as defined in the Performance Cost Report CDRL, A108. Data Item Description (DID) DI-FNCL-80912 may be used, tailored with the Government’s concurrence.

Alternate formats may be proposed and used with prior approval of the COR.

4.1.6 Information Assurance

The Contractor shall comply with the latest MSC Information Assurance Policy. Current policy is detailed in MSC

Instruction (COMSCINST 5239.3 series, Attachment J-004). Compliance with this directive is mandatory during the execution of design, development, and implementation and maintenance tasks within the following PWS.

The Contractor shall comply with the DoD Information Assurance Workforce Improvement Program (DoD

8570.01-M Attachment J-005). The Contractor shall use only certified personnel for all task(s) performed under this task order where certification is a requirement in accordance with DoD 8570.01-M.

4.1.7 Quality Assurance

The Contractor shall have at contract award, and shall maintain, an existing quality management system per the

International Organization of Standards ISO 9001:2000 or above which is standard for all work performed at the

Contractor’s facilities and onsite in support of this effort. The Government reserves the right to require the

Contractor to present its current ISO 9001 certificate of compliance at any time. The Contractor shall, in addition, support all MSC ISO 9001assessments by adhering to N6 processes for work performed under this effort.

The Contractor shall provide a quality assurance plan and approach for task order management, task order deliverables, and business process improvement to enhance the current and future processes in accordance with

CDRL A109. The quality assurance plan shall be provided at the contract kick-off meeting. DID DI-QCIC-81794, Quality Assurance Program Plan (QAPP) may be used and tailored with the Government’s concurrence.

4.1.8 Configuration Management

The artifacts used to engineer the systems and networks developed and sustained under this contract will need to produced, updated and maintained to accurately reflect the Technical Data Packages for all deployed instances. The

Contractor shall implement a Configuration Management (CM) system which complies with the following requirements:

a. Establishes initial hardware and software baseline of requirements. This baseline shall include hardware drawings and software programs and code which represent the delivered end items.

b. Perform CM reviews during formal technical program reviews at the Contractor and subcontractor facilities that verify the high level system requirements have been incorporated and implemented into the evolving detail baseline.

c. A change control system for identifying, evaluating, dispositioning, and implementing proposed hardware and software changes to the established baseline.

d. A system that provides for periodic audits, including subcontractors, to ensure the overall requirements and objectives of the program are being accomplished and satisfied.

The Contractor shall provide a Configuration Management Plan documenting all CM areas included in the above section (4.1.8) of this PWS and shall do so in accordance with CDRL A110. MIL-HDBK-61 may be used for guidance when doing so. Data Item Description (DID) DI-SESS-81875 may be used, tailored with the Government’s concurrence.

4.1.9 Communications

The Contractor will develop and organize the communications strategy necessary to keep key stakeholders, and project team leads informed as projects move through each of the life cycle phases (i.e. Requirements Definition, Design, Implementation, Test & Evaluation, Deployment) of the engineering processes and shall provide technical support by assisting MSC in drafting plans, Standard Operating Procedures (SOPs) and other guidance documents as pertain to this PWS.

4.1.10 Staffing

The Contractor is required to provide resources with required project management, systems engineering and IT

Service Management competencies in accordance with the…