70Z04422RESD30016 Attachment 1 Scope of Work - Final.docx

Attachment I: Scope of Work

70Z04422RESD30016

DEPARTMENT OF HOMELAND SECURITY (DHS)

SCOPE OF WORK (SOW) FOR

C5ISC ENGINEERING DEVELOPMENT, INTEGRATION, AND SUPPORT SERVICES (CEDISS)

1.0 GENERAL

1.1 BACKGROUND

The Department of Homeland Security (DHS), U.S. Coast Guard (USCG), Command, Control, Communications, Computers, Cyber, and Intelligence (C5I) Service Center (C5ISC) has a requirement to procure C5I Engineering Development, Integration, and Support Services (CEDISS) for the design, development, integration, testing, and operational evaluation of new C5I and electronic systems as well as modifications and technology refreshment or upgrades to existing C5I and related electronic systems. These services include the development and maintenance of engineering change and logistics support documents that enable C5I and electronic system sustainment.

The C5ISC is responsible for the development, integration, deployment, sustainment, and enhancement of advanced electronic Command and Control (C2), communications, and navigation systems. The C5ISC facilitates continuous improvement engineering that focuses on the rapid deployment of essential functionality followed by planned improvements based on enhanced or refined requirements. The systems developed and supported by the C5ISC have a multi-mission focus on Law Enforcement, Search and Rescue, Maritime Mobility, Marine Safety, Defense Readiness, Marine Environmental Protection, and Ports, Waterways and Coastal Security. The systems may be as complex as a multi-tiered network of computers, radars, navigation receivers, satellite and radio-based communication links installed on board a Coast Guard Cutter, or a web-based Information Management System (IMS) that performs real-time correlation of CG and other government agency data feeds to provide geographic based maritime domain awareness, integrated vessel targeting, joint mission planning, and operations monitoring capabilities. Alternatively, the system may be as simple as interfacing a commercial maritime radar with an electronic chart plotter on a small boat. In both instances, the system architecture and development activities reflect the Coast Guard’s system engineering lifecycle process while the system implementation supports the Coast Guard’s operational Sense-Assess-Decide-Act cycle performed by hundreds of ashore, afloat, and aviation units nationwide.

1.2 SCOPE

The C5ISC has a continuing need for support services that provide qualified personnel with the required knowledge and experience, equipment, test instrumentation, system performance information collection and analysis, and other technical services to support the design, development, integration, testing, operational evaluation, modification, upgrade, and technical refresh of C5ISC and electronic systems. Within CEDISS, “operational evaluation” consists of fully functional systems installed for use in an operational setting to ensure the system will operate as designed and to assess system usability. SOW Section 1.2.1 summarizes the supported systems that would be supported through systems engineering life cycle phases listed in SOW Section 1.2.2.

1.2.1 SUPPORTED SYSTEMS: The following include, but are not limited to, the C5ISC and electronic systems that require engineering development, integration, and support services that shall be provided by the Contractor, organized by the following four (4) system groupings:

1.2.1.1 C2 and Navigation Systems: These systems provide reliable and efficient C2 capabilities to Coast Guard shore and afloat units and navigation capabilities to Coast Guard cutters and small boats. C2 systems provide maritime domain awareness (MDA), mission planning, mission tasking, and mission monitoring capabilities between Coast Guard operational C2 nodes (e.g. Coast Guard Area, District, Sectors, and cutters), operational units, and interagency partners. Shoreside C2 systems include Common Operational Picture (COP) systems, Vessel Traffic Systems (VTS), and geographic based information management systems (e.g. WatchKeeper and CG One View); afloat systems include shipboard C2 systems (e.g. SeaWatch and Coast Guard C2 System), aviation mission pallets, associated sensors including Navy-Type Navy Owned (NTNO) and Navy Type CG Owned (NTCGO) equipment, and associated information interfaces. Navigation systems include electronic navigation systems and navigation sensors installed onboard all Coast Guard cutters and small boats. Electronic navigation systems include both commercial and government systems that serve as Electronic Charting Systems (ECS), Electronic Chart Display and Information Systems (ECDIS), and Integrated Navigation Systems (INS). Navigation Sensors comprise a variety of electronic nautical sensors, GPS receivers, radars, depth sounders, Automatic Direction Finders (ADF), Automatic Identification System (AIS) transponders, and fixed or handheld electro-optical devices.

1.2.1.2 Operations Information Systems: Operations Information systems provide supporting MDA, mission planning, and operational readiness information services to C2 and Navigation systems as well as supporting enterprise level mission analysis and planning activities.

1.2.1.3 Communications Systems: These systems provide reliable and efficient voice and data communications between USCG shore and afloat units and the maritime public through UHF, VHF, HF and MF radio systems (e.g., commercial satellite, military satellite, NTNO communications, and terrestrial radio communication systems) as well as supporting ancillary radio system components (e.g. antennas, patch panels, modems) both afloat and ashore. Some communications systems are key elements of the Global Maritime Distress and Safety System (GMDSS).

1.2.1.4 Intelligence Systems: Intelligence systems provide information collection, processing, exploitation, and dissemination capabilities to support Coast Guard and other agency operations. These systems are located on USCG shore and afloat units and include Ships Signal Exploitation Equipment (SSEE), various NTNO/NTCGO equipment, document and media exploitation (DOMEX), and associated sensor, information processing, and display systems.

1.2.2 SYSTEM ENGINEERING LIFE CYCLE PHASES: The C5ISC designs, develops, integrates, tests, and operationally evaluates new C5I and electronic systems as well as implements modifications and technology refreshments or upgrades to existing C5I and related electronic systems consistent with the DHS System Engineering Life Cycle (SELC). The DHS SELC aligns to the four phases of the DHS Acquisition Life Cycle (ALF) as summarized below:

Needs Analysis

Requirements Definition (Functional Design)

Design (System Design)

Development

Integration and Test

Implementation

Disposition

The C5ISC serves as the system developer during the Obtain phase of the ALF and serves as the system sustainer during the Produce/Deploy/Support phase of the ALF. The C5ISC serves as the system developer for programs that establish new systems and projects that modify, refresh, or upgrade existing systems. CEDISS will provide the engineering design, development, integration, testing, operational evaluation, and logistic support services necessary for the C5ISC to fulfill its system developer role.

The C5ISC employs various engineering methodologies as a system developer including Waterfall, Incremental, Spiral, and AGILE with the majority of projects using Waterfall or AGILE. The C5ISC tailors SELC implementation to reflect the system development methodology.

The following six (6) phases of the SELC summarize the engineering development, integration, and support services to be provided by CEDISS to support the system groupings identified above:

1.2.2.1 Planning: The purpose of the planning phase is to analyze the project across the entire project’s life-cycle, define and implement management processes needed for project success, and plan key activities that will occur throughout the project’s lifecycle. Planning phase activities include assisting government project leads with developing project management plans and processes, defining the project’s technical scope, defining the project’s development methodology and SELC tailoring actions, identifying necessary technical resources, developing stakeholder engagement strategies, developing the technical schedule, defining the project’s technical management processes, identifying applicable design considerations, and developing appropriate developmental, acceptance, and end-user evaluation activities. The planning phase generally concludes with conduct of a project planning review to ensure completion of required activities and artifacts and determine the project’s readiness to proceed to the requirement’s definition phase.

1.2.2.2 Requirement Definition: The purpose of the requirements definition phase is to gather, analyze, and document changes to functional and non-functional requirements to establish the functional baseline. Requirement definition phase activities include assisting government project leads and engineers with identifying project related interfaces, inputs, and outputs; identifying applicable technical and industry standards; developing recommended changes to functional requirements; identifying non-functional requirements; ensuring requirements are complete, consistent, testable, and traceable; and complying with established technical management processes. The requirement definition phase generally concludes with conduct of a system design review to ensure completion of required activities and artifacts and determine the project’s readiness to proceed to the design phase.

Depending on the project scope, the requirements definition phase may also include documentation of or modifications to enterprise architecture viewpoints including As-Is and To-Be capability views and solution views using standardized formatting and strict adherence to current DoDAF Meta-Model data standards. Enterprise architecture viewpoints will integrate with and trace to documented functional and non-functional requirements, interfaces, inputs, and outputs.

1.2.2.3 Design: The purpose of the design phase is to ensure the functional baseline is transformed into a comprehensive functional/logical design and detailed design that can be used to efficiently and effectively guide or contract for system fabrication, assembly, coding, and configuration activities. Design phase activities include performing or assisting government project leads and engineers with defining the physical architecture, defining and documenting changes to system level and design level requirements consistent with applicable technical and industry standards, developing modifications to the data architecture, maintaining the system design, designing for system verification and validation, development of the deployment plan and site preparation plans and preliminary site surveys, developing service level agreements, developing technology insertion packages, developing interconnection security agreements, and initiating privacy impact assessments and information assurance documentation. Depending on the complexity of the system and project scope, the design phase will include a preliminary design review and conclude with conduct of a critical design review for projects following the Waterfall methodology. AGILE projects will complete a release planning review prior to initiation of planning and development sprints during which detailed design and developmental activities will occur. AGILE projects conduct sprint review and demonstration at the conclusion of each sprint throughout the iterative detailed design, development, and integration and test phases.

Depending on the project scope, the design phase may include documentation of or modifications to enterprise architecture viewpoints including As-Is and To-Be system views and datasets using standardized formatting and strict adherence to current DoDAF Meta-Model data standards. Enterprise architecture viewpoints will integrate with and trace to documented system and design level requirements, interfaces, inputs, and outputs. The design phase may also include preparation or update of Certification and Accreditation documentation required to ensure that all system and system enhancements meet the Federal Information Security Management Act of 2002 (FISMA) a United States federal law (44 U.S.C. § 3541, et seq.) enacted in 2002 as Title III of the E-Government Act of 2002 (Pub. L.107-347, 116 Stat. 2899) for review and approval by the government.

1.2.2.4 Development: The purpose of the development phase is to build, manufacture, code, and begin testing the components, products, and functionality that make up the solution that delivers the capability defined functional requirements while complying with non-functional requirements. Development phase activities include performing or assisting government project leads and engineers with finalizing the detailed sub-system/configuration item specifications; developing the software development environment; building, constructing, assembling, coding, and configuring the sub-system/system in compliance with information assurance controls; and developing supporting documentation. For Waterfall projects, the development phase generally concludes with conduct of an integration readiness review to ensure completion of required activities and artifacts and determine the project’s readiness to proceed to the integration and test phase. AGILE projects conduct sprint review and demonstration at the conclusion of each sprint throughout the iterative detailed design, development, and integration and test phases.

Depending on the project scope, the development phase may include logistics services required to prepare for sustainment activities throughout the system’s life-cycle including the performance of maintenance analyses, maintenance planning, and maintenance development services that comply with system availability, reliability, and maintainability requirements. This includes preparing life-cycle engineering and logistics documents that will be used by depot level support facilities and other field personnel responsible for maintaining and supporting the system.

1.2.2.5 Integration and Test: The purpose of the integration and test phase is to integrate the systems, subsystems, components, and configuration items that have been built during development and to demonstrate that the integrated system satisfies all defined requirements. Integration and test phase activities include defining the methodology for system verification and validation; planning the integration; planning and conducting developmental test and evaluation of individual sub-systems and configuration items; planning and conducting developmental test and evaluation of the system or increment to be delivered; conducting acceptance testing of the system against documented requirements and information assurance controls; conducting site surveys; and preparing logistics support, training, and data collection for end-user evaluations of temporary operational installations. The integration and test phase generally concludes with conduct of a production readiness review to ensure completion of required activities and artifacts and determine the project’s readiness to proceed to the implementation phase. AGILE projects conduct sprint review and demonstration at the conclusion of each sprint throughout the iterative detailed design, development, and integration and test phases; AGILE projects that require further evaluation in a production environment prior to full deployment may also complete production readiness review prior to entering the implementation phase.

Depending on the project scope, the integration and test phase may include logistics services required to maintain the system during its life-cycle including the performance of maintenance analyses, maintenance planning, and maintenance development services; and developing and updating integrated logistics support plans. This includes maintaining life-cycle engineering and logistics documents that will be used by depot level support facilities and other field personnel responsible for maintaining and supporting the system. Training support activities will ensure the USCG can operate and maintain the systems or changes that are developed for deployment. Training support activities include developing training aids, providing trainers to train USCG personnel, developing training plans, and producing required training materials. Information assurance support activities include integration of information assurance controls and maintenance of a system’s information assurance posture, as well as preparation and maintenance of supporting certification and accreditation documentation.

1.2.2.6 Implementation: The purpose of the implementation phase is to ready the system or engineering change for deployment by verifying the operational effectiveness and suitability of the system, preparing associated installation and logistic support documentation, and preparing the operational sites and users/operators for system deployment. Implementation phase activities include deploying operational evaluations (if applicable), reviewing and analyzing end user feedback, completing site preparation and installation documentation, making final changes to the system or engineering change prior to full production according to the project’s technical management, and obtaining authority to operate the system. The implementation phase generally concludes with conduct of an operational readiness review to ensure completion of required activities and artifacts and determine the project’s readiness to proceed to full deployment and the operations and maintenance phase. AGILE projects complete a release readiness review prior to full deployment in the production environment.

Depending on the project scope, the implementation phase may include field engineering support services to install operational evaluation systems/system changes and assess performance to ensure effective operation; perform periodic verifications that the subject system or system change is performing within all specifications; and provide end user training and assist the end user in problem resolution of operational evaluation systems. During operational evaluation installations, provision of onsite technical assistance and maintenance services may be required, including short notice callouts or support via telephone or other means. In addition, field engineering services may include conduct of electromagnetic interference (EMI) surveys, TEMPEST inspections, and Radio Hazard (RADHAZ) studies which may require travel to various locations to USCG facilities or meet deployed USCG cutters, both pier-side and underway.

CEDISS will generally not include installation of production systems and performance of routine maintenance as these services are currently provided under C5ISC’s companion Installation and Logistics Management Services (ILMS) contract.

1.3 OBJECTIVE

The objective is to establish a multiple award, indefinite delivery indefinite quantity (IDIQ) 8(a) contract for the procurement of the above mentioned services. The Government will provide contractual separation between system engineering and system sustainment activities acquired through other contract vehicles to comply with FAR Section 9.5 Organizational and Consultant Conflicts of Interest at the task order level.

1.4 APPLICABLE DOCUMENTS

The following documents, regulations, policies, guidance, and instructions are applicable to the IDIQ and flow down to all Task Orders. As these are updated and revised, the most current versions of these documents replace the versions identified here and will be the required standards.

1.4.1 Compliance Documents

The following documents provide specifications, standards, or guidelines to be followed in order to meet the requirements of this contract at the task order level. Documents include, but are not limited to the following:

1.4.2 Reference Documents

The following documents may be helpful to the Contractor in performing the work described in this document:

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 DATA ITEMS AND WORK PRODUCTS: Individual task orders will specify data items and work products required to be delivered to the Government via Contract Data Requirements List (CDRL). These items will depend upon the nature of the task order requirements which may include, but are not limited to, the following data items and work products:

a. Contractor Project Plans

b. Contractor IT Security Plans

c. Periodic Progress Reports

d. Periodic Cost Reports

e. Trip Reports

f. Meeting Minutes

g. Briefing Materials

h. Technical Reports

i. Site Surveys

j. Technical Requirements documents

k. System Architecture products and DoDAF viewpoints

l. Conceptual Design Drawings & associated lists

m. Engineering Change documentation including Time Compliance Technical Orders

n. System Configuration Management and Tracking Reports

o. “As-Is”, “Red-Lined”, and “As Built” Technical Drawings

p. Engineering Test Plans

q. Engineering Test Report

r. Computer Software

s. Technical Data Packages

t. Reliability Centered Maintenance Analyses

u. Level Of Repair Analyses

v. Maintenance Requirements Lists

w. Maintenance Procedure Cards

x. Integrated Logistics Support Plans

y. System Security Plans & supporting materials

z. System Operational Verification Test Reports

The contractor shall provide all data items in formats compatible with the Coast Guard Standard Workstation (e.g. Microsoft Office, Adobe Acrobat etc.) or as specified in the individual task order.

2.2 EVENTS: In addition, individual task orders will specify events requiring contractor participation and support. The format, location, and frequency of these events will depend upon the nature of the task order requirements, which may include, but are not limited to, the following:

a. Kick-Off Meetings

b. Progress Meetings

c. Technical Reviews and Meetings

d. Change Management Reviews and Meetings

e. Site Survey Visits

f. Operational Evaluation System Installation and Support Visits

g. System Operations Verification Tests

3.0 CONTRACTOR PERSONNEL

3.1 QUALIFIED Personnel

The Contractor shall provide qualified personnel to perform all requirements specified in this SOW and individual task orders. The labor categories for personnel required to perform the requirements are found in Attachment 5, Labor Category Descriptions. However, the individual task orders may provide for further labor categories not identified in the attached Labor Categories Descriptions

3.2 Key Personnel

The Government may designate Contractor personnel as Key in each task order under this IDIQ. The key personnel are considered essential to the work required under the IDIQ. In the event that it becomes necessary for the Contractor to replace the individual(s) designated as key personnel, the Contractor shall notify, in writing, the Contracting Officer (KO) and Contracting Officer’s Representative (COR) no less than 15 days in advance. The notification shall include the name of the substitute/replacement and a resume indicating that the proposed candidate meets the required qualifications. All substitutes shall have the qualifications as stated in the task order PWS as applicable. For substitutes with a required security clearance, notification in writing shall be no less than 10 business days in advance. The Contractor shall not replace any of the key personnel named to work on individual task orders without the written consent of the Contracting Officer.

3.3 Program Manager

The Contractor shall provide a Program Manager and also an alternate who shall be responsible for all Contractor work performed under this SOW and subsequent task orders. The Program Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Representative (COR) to discuss work being performed at the task order level. During any absence of the Program Manager, only the designated alternate shall have full authority to act for the Contractor on all matters relating to work performed under this contract and subsequent task orders.

3.3.1 The Program Manager and the designated alternate shall be able to read, write, speak and understand English.

3.3.2 The Program Manager and the designated alternate shall be able to perform the duties and satisfy the Education & Experience requirements for Program Manager, see Labor Definitions, including possessing and maintaining a Secret security clearance.

3.4 Employee Identification

3.4.1 Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

3.4.2 Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.5 Employee Conduct

Contractor’s employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the Department of Homeland Security. The Contractor shall ensure Contractor employees understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.

3.6 Removing Employees for Misconduct or Security Reasons

The Government may, at its sole discretion (via the Contracting Officer or CEDISS COR), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Government will provide the Contractor with a written explanation to support any request to remove an employee.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

All software and services provided shall be in accordance with DHS Management Directive (MD) 4300.1 as implemented by the following:

· The performance of this contract will require the Contractor to access classified and/or Sensitive but Unclassified information. Classified information is Government information which requires protection in accordance with Executive Order 13526, “Classified National Security Information, and supplemental directives. The Contractor shall abide by the requirements set forth in the DD Form 254, Contract Security Classification Specification, an attachment to the contract, and the National Industrial Security Program Operating Manual (NISPOM), DoD 5220.22-M for protection of classified information, as directed by the Federal Acquisition Regulation (FAR) Clause 52.204-2, “Security Requirements (Aug 1996).”

· Contractor access to classified spaces is required under this procurement at the SECRET level. System Administrators, Programmers, and Programmer Analyst require a Secret Clearance, per COMDTINST M5500.13(series). System Administrators will require access to C5I secure lab spaces which may take an undetermined amount of time while in performance of their tasking. Therefore, a lengthy sanitation period for restricted or classified spaces is not obtainable due to ongoing support operations. Programmers and Programmer Analyst may be required to attend meetings and/or briefings where classified discussion take place. Consequently, these positions must be provided access to as required.

· DHS Sensitive Systems Policy Directive 4300A, Version 13.1, July 27, 2017 and the companion publication DHS 4300A Sensitive Systems Handbook, Version 12.0, November 15, 2015 for systems processing Sensitive But Unclassified (SBU) information.

· DHS National Security Systems Policy Directive 4300B, Version 10.1, November 21, 2018 for National Security Systems (NSS) Collateral for systems processing Unclassified, Secret, and Secret Collateral information.

4.1.1 Access to Classified Information. In accordance with COMDTINST M5500.13 (series), Account Management, all CGOne Account Holders shall complete the mandated Federal Cyber Awareness Challenge (FCAC) training and digitally accept the Automated Information Systems (AIS) User Acknowledgement, Form CG-5500A which is located at the conclusion of the training. The training shall be completed using the Learning Management System (LMS) within 96 hours of initial access. After completion of the initial FCAC training, all CGOne Account Holders shall complete FCAC training annually. Any account delinquent more than 60 days shall be disabled. Contractors must read and sign a Classified Information Non-Disclosure Agreement (SF-312).

4.1.2 Contract Management Security. Secret access is required for management of the base contract and individual task orders; see attached Industrial Security Addendum B. Contractor access to classified information will be required to support individual task orders issued under this base contract(s). The maximum level of classification for individual task orders is Secret. The details are specified in the attached Department of Defense (DD) Form DD-254, Addendum C. Due to the time-sensitive nature of services provided under this contract and individual task orders, the Program Manager (Section 3.3.) must hold US citizenship and is required to possess, at a minimum, a valid in-scope national security clearance at the SECRET level in order to manage and perform CEDISS services located in classified/restricted areas at or within USCG facilities. Persons determined by the CO and COR to be a substantial risk to U.S. national security interests will not be employed under this contract. Contractor employees must maintain their security clearance eligibility for the duration of this contract. In general, all necessary employee security clearances shall be at the expense of the Contractor.

4.1.3 Task Order Security. The pertinent security clauses that will be applied to task orders under this IDIQ contract will vary based on the type of classified related work that is to be performed under each task order. C5I Security uses industrial security addendum (Unclassified, Classified [SECRET. For each task order, the C5I Industrial Security Officer will initial each applicable security requirement on the selected addendum as part of the required industrial security review. Further security details are contained in the attached CEDISS IDIQ DD-254. Due to the time-sensitive nature of services provided under individual task orders, personnel for individual task orders must hold US citizenship and are required to possess, at a minimum, a valid in-scope national security clearance at the clearance level specified in the task order in order to access government IT systems and/or perform CEDISS services located in classified/restricted areas at or within USCG facilities. Persons determined by the CO and COR to be a substantial risk to U.S. national security interests will not be employed under this contract or individual task order. Contractor employees must maintain their security clearance eligibility for the duration of the individual task order. In general, all necessary employee security clearances shall be at the expense of the Contractor.

4.1.4 Facility Clearance (FCL). Prime contractors are required to possess and maintain a Secret FCL; for Joint Ventures, all parties of the joint venture are required to hold a Secret FCL. Subcontractor team members are required to hold a Secret FCL. In general, all necessary facility clearances shall be at the expense of the Contractor.

4.1.5 Contractor personnel requiring access to DHS/USCG or DoD facilities where proof of a security clearance is a prerequisite, shall meet the security requirements of the [contract or task order] for accessing classified information and/or IT systems/networks as specified by the host and/or owner of those facilities. Access to all classified information is based on a strict need-to-know principle. Classification markings on the material to be furnished shall provide the classification guidance necessary for the performance of this [contract or task order]

4.1.6 Contractor shall provide a visit authorization letter (VAL), equivalent to the USCG Visit Access Request (VAR), to the place of performance. All requests shall contain the information required by the NISPOM and shall not exceed the completion date of the contract or a 12 month period, whichever is shorter. Additionally, the VAL shall note the applicable government COR or Technical Assistant (TA) responsible for coordinating the visit so that the host location can verify “Need-to-Know,” as necessary.

4.1.7 Contractor is not required/authorized to generate or store classified material at its facility.

4.1.8 Contractor personnel shall safeguard and handle all sensitive information in accordance with the DHS HSAR Class deviation 15-01 clauses as applicable for proper handling and safeguarding of the security of all such USCG information, as defined in the terms and conditions of this [insert contract or task order].

4.1.9 Contractor is responsible for controlling and safeguarding FOUO information in accordance with DHS MD 11042.1, “Safeguarding SBU/FOUO information.” Contractor shall provide an OPSEC Plan detailing how Sensitive but Unclassified/For Official Use Only material shall be handled, discussed, disseminated and protected by their employee within 45 days after call order award.

4.1.10 Contractor shall adhere to all required USCG mandated training/briefing to maintain security and network access to USCG sites and IS/IT. In accordance with COMDTINST M5500.13 (series), Account Management, all CGOne Account Holders shall complete the mandated Federal Cyber Awareness Challenge (FCAC) training and digitally accept the Automated Information Systems (AIS) User Acknowledgement, Form CG-5500A

4.1.11 Secret Internet Protocol Network (SIPRNET) access will be limited to only those employees who have a SIPRNet requirement to support contract mission [contract or task order]. Other applicable classified systems shall be indicated. Contractor is not authorized to access, download or further disseminate any classified information from SIPRnet, which is outside the scope of the defined contract requirements.

4.1.12 Further, all contracted work shall meet the requirements of USCG Commandant Instruction 5520.13 (series), Coast Guard Industrial Security Program, and the Department of Defense Instruction 5220.22 (series), National Industrial Security Program.

4.3 PLACE OF PERFORMANCE

Individual task orders will define the places of performance. In general, CEDISS task orders will require services to be provided in the following locations:

· At the USCG Command, Control, Communications, Computers, Cyber, and Intelligence Service Center (C5ISC), 4000 Coast Guard Blvd, Portsmouth, VA 23703-2199.

· At contractor facilities within local commuting distance to Portsmouth, VA.

· Aboard various USCG facilities and cutters throughout the United States, as stated in individual TOs and may include time underway.

· At various other locations as defined in individual TOs. Work may be performed at locations worldwide.

4.4 HOURS OF OPERATION

Contractor employees shall generally perform all work in accordance with working hours at the sites where work is to be performed, generally between the hours of 0800 and 1600 EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this SOW or individual TO.

4.5 TRAVEL

Contractor travel may be required to support this requirement and individual TOs. All travel required by the Government outside the local commuting area(s) will be reimbursed to the Contractor in accordance with the Federal Travel Regulations. The Contractor shall be responsible for obtaining COR and Contracting Officer approval (electronic mail is acceptable) for all reimbursable travel in advance of each travel event.

4.6 POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than ten (10) business days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The Post Award Conference may be face to face at the Government’s facility, located at Command Control and Communications Engineering Center (C3CEN), 4000 Coast Guard Blvd, Portsmouth, VA 23703-2199, or virtually by mutual agreement of the parties.

4.7 PROJECT PLAN

The Contractor may be required to provide a Project Plan on a task order basis.

4.8 BUSINESS CONTINUITY PLAN

The Contractor may be required to prepare and submit a Business Continuity Plan on a task order basis.

4.9 PROGRESS REPORTS

The Contractor shall be required to provide quarterly progress reports on a task order basis to the Contracting Officer and COR via electronic mail within 10 business days following the end of the quarter. The quarterly progress reports shall include at a minimum 1) performance monitoring and surveillance measures, and 2) information that allows the Government to monitor and track the percentage of CEDISS work, based on the cost of contract performance incurred for personnel, performed by the prime and team members/subcontractors.

4.10 PROGRESS MEETINGS

The Project Manager shall be available to meet with the COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place virtually.

4.11 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Windows and Microsoft Office Applications, Adobe Acrobat, etc.). Task orders may require additional electronic formats for task order specific deliverables.

4.12 DATA RIGHTS

The CEDISS IDIQ contract and individual task orders will specify required data items and work products for delivery to the Government via CDRL as well as events requiring contractor participation and support per Sections 2.1 and 2.2.

The individual task orders will provide details on what data is to be delivered along with the format and method for delivery and any other information pertinent to the delivery of data. In general, the contractor shall provide all data items in formats compatible with the Coast Guard Standard Workstation (e.g. Microsoft Office, Adobe Acrobat etc.) or as specified in the individual task order.

4.13 PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive But Unclassified (For Official Use Only) Information. For individual task orders requiring contractor access to business or procurement sensitive information, the Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

4.14 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act (classified to 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendixes A, C & D, and available at https://www.ecfr.gov/cgi-bin/text-idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139-05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139-05-001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

4.14.1 Section 508 Requirements for Technology Products (include in the SOW, PWS, or SOO) Section 508 applicability to Information and Communications Technology (ICT): C2 and Navigation Systems Applicable Exception: N/A Authorization #: N/A Applicable Functional Performance Criteria: All functional performance criteria in Chapter 3 apply to when using an alternative design or technology that results substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards, or when Chapters 4 or 5 do not address one or more functions of ICT.

Applicable 508 requirements for electronic content features and components (including but not limited to Electronic documents; Electronic forms; Electronic document templates; Electronic emergency notifications; Electronic surveys; Electronic reports; Electronic training materials): All requirements in E205 apply, including all WCAG 2.0 Level A and AA Success Criteria apply as specified in E205 Applicable 508 requirements for software features and components (including but not limited to Software infrastructure): All requirements in Chapter 5 apply, including all WCAG 2.0 Level A and AA Success Criteria, 502 Interoperability with Assistive Technology, 503 Application, 504 Authoring Tools Applicable 508 requirements for hardware features and components (including but not limited to Computers & laptops; Tablets; Peripheral Equipment (ex. keyboards); Information kiosks and transaction machines; Other): All requirements in Chapter 4 apply Applicable 508 requirements for support services and documentation: All requirements in Chapter 6 apply

4.14.2 Section 508 Requirements for Technology Products (include in the SOW, PWS, or SOO) Section 508 applicability to Information and Communications Technology (ICT): Operations Information Systems Applicable Exception: N/A Authorization #: N/A Applicable Functional Performance Criteria: All functional performance criteria in Chapter 3 apply to when using an alternative design or technology that results substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards, or when Chapters 4 or 5 do not address one or more functions of ICT.

Applicable 508 requirements for electronic content features and components (including but not limited to Internet or Intranet website; Electronic documents; Electronic forms; Electronic document templates; Electronic emergency notifications; Electronic surveys; Electronic reports; Electronic training materials; Multimedia (video/audio); Interactive maps): All requirements in E205 apply, including all WCAG 2.0 Level A and AA Success Criteria apply as specified in E205 Applicable 508 requirements for software features and components (including but not limited to Web, desktop, server, mobile client applications; Electronic content and software authoring tools and platforms; Software infrastructure): All requirements in Chapter 5 apply, including all WCAG 2.0 Level A and AA Success Criteria, 502 Interoperability with Assistive Technology, 503 Application, 504 Authoring Tools Applicable 508 requirements for hardware features and components (including but not limited to Computers & laptops; Servers; Tablets;…