Attachment_1_-_Statement_of_Requirements_Amendment_1.pdf

Amendment 1 - Attachment 1

HSCG23-14-R-MPE209

2.8.2 Interagency coordination support for execution of the mission.

2.8.3 Public information and social media support for execution of the mission.

tion of the mission.

2.8.5 at

2.8.6

2.8.7

2.8.8 port for execution of the mission.

.1 Support execution of the mission.

into other GIS viewers via a centralized data

2.8.4 Safety system management to support execu

Oper ional execution of the mission.

Planning for execution of the mission.

Logistical support for execution of the mission.

Financial documentation and sup

2.8.9 Resource management of the mission.

2.8.10 Situational awareness and dissemination process to:

2.8.10

2.8.10.2 Provide information and communications flow to agency leadership, maritime stakeholders, and the public.

2.8.10.3 Develop and disseminate open source Geographic Information System (GIS) data layers that can be imported set updated in near real time (near real time is defined as I timeframe of <=60 seconds).

2.8.11 Simulation and exercise support.

2.8.12 Preplanning and development of Contingency Plans, draft IAPs, response data to support a more efficient initial incident respon and geographic se and development er contract ts, es shall rdance standard liver the files to nment to access, migrate, and convert this section not d users authorized per site.

of the initial IAP.

T an t2.9 he Government owns all data entered into the database. Not more th year, USCG may require that the Contractor provide files that contain d developed using the softwar ard data set formats. In acco uest, the Contractor shall de wice p all produc

e. The filesigns, drawings and outputs that USCG comply with section 3.2.5 and 3.9.1 stand industry practice and within 30 days of req U t

SCG and provide assistance that enables the Gover o database into useable formats.

3 MINIMUM SYSTEM REQUIREMENTS

the minimum requirements of

The C no late tractor’s system and software shall meet r than 120 days after the contract award date.

3.1 The system shall:

3.1.1 nclude individual site licenses for 300 USCG‐approveI

HSCG23 -MPE209

incident being run using other commercial Incident Management Systems for situations where the USCG is relying on other Unified Command members for Incident Action Planning services.

-14-R

3.2.11

3.2.12

3.2.13

3.2.14

3.2.15

3.2.16

3.2.17

3.3 U

3.3.1 d

Have capability for a minimum of 2,800 concurrent users for routine operations and a maximum of 5,600 concurrent users for surge operations. Surge operations shall not cause system degradation that negatively impacts user processing time.

Have controls to restrict access to sensitive security information (SSI).

Maintain a redundant real time backup system.

less

Have system availability 24/7/365 with 99% up time.

Have a disaster recovery capability to reestablish full operating capability in no than 1 hr with 100% data integrity.

Have the ability to integrate and update USCG provided incident response templates.

Have the ability to track and audit user actions by date/time stamp.

sers and Access Control capabilities shall:

Maintain Department of Homeland Security (DHS)/Defense Information System Agency (DISA) approved federated account/user management system. License em provides initial user registration, authentication capability by syst administrators.

3.3.2 Meet or be upgraded prior to USCG use to meet the user access and security requirements set forth in the DHS Management Directive 4900, Individual use an operation of DHS Information Systems/computers.

http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4900_individual_use_an d_operation_of_dhs_information_systems_computers.pdf

3.3.3 Be compliant with Homeland Security Presidential Directive 12 (HSPD‐12).

3.3.4 Maintain version control capabilities with near real time track changes and abi roll back to previous versions.

lity to

3.3.5 Have the ability to define user roles, access, responsibilities, and authorities.

3.3.6 Have the ability to create user roles, access, responsibilities, and authorities based on ICS position described in the USCG Incident Management Handbook (CG‐IMH) 2014 edition. https://homeport.uscg.mil/ics.

roles and responsibilitie3.3.7 Have the ability to assign system administrator members.

s to USCG

HSCG 3-2

ey are y

ICS

14-R-MPE209

3.3.8 Have a comprehensive user management feature to control access to the system, create user accounts, manage user permissions, etc.

nt. 3.3.9 Have the ability to restrict user access based on role, unit, agency, or incide

3.3.10 Have the ability to limit users from viewing and/or editing incidents that th dent bnot assigned in order to prevent personnel from editing another inci accident.

3.3.11 Push notifications to users based on required action on a form/process based on position.

3.4 Command and Control of the mission capabilities shall:

3.4.1 Have the ability to view incident locations as a GIS layer.

3.4.2 Have the ability to click on incident location in the GIS layer and view incident specific data.

3.4.3 Provide an online mapping tool that integrates both static and near real‐time data, such as Environmental Sensitivity Index (ESI) maps, ship locations, weather, ocean a currents, and other Government provided or publicly available data layers in centralized, easy‐to‐use format.

3.4.4 Provide an online mapping tool enables a user to quickly and securely upload, draw, manipulate, export, and display spatial data in a GIS map with minimal training cialist required. Online mapping tool use does not require the expertise of a GIS spe to develop and display a basic incident specific situation map layer.

3.4.5 Have the ability to export/print GIS layer information.

3.4.6 Have the ability to include GIS layers of information from existing Government sites and/or files.

3.5 Public information and social media support for execution of the mission capabilities shall:

t‐

3.5.4 ith USCG public affairs branding standards.

3.5.1 Have the ability to for specified users to distribute photos, video, audio clips and other multi‐media materials.

ex3.5.2 Allow specified users to disseminate messages instantly: SMS Text Messages, T to‐voice phone messages, Email, Fax, Social Media Sites, Websites (one or many, public or private news releases, photos, video, and audio clips to the website at all times).

3.5.3 Have the ability for specified users, commensurate with administrator granted access levels, to collaborate on content including news release, photos, video clips, and audio clips in an area inaccessible by the public. This capability must also provide complete version control and recall.

Comply w http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4900_individual_use_and_operation_of_dhs_information_systems_computers.pdf

HSCG23-14-R-MPE209

3.6 afS ety system management to support execution of the mission capabilities shall:

nd 3.6.1 Digitally support development of the Site Safety and Health Plan (ICS 208‐CG) a Incident Health and Safety Plan (HASP) per 29 CFR 1910.120.

3.6.2 Have the ability to map data from the ICS‐208‐CG over to the ICS‐204‐CG forms.

3.6.3 Have the ability to push alerts to specified user groups.

3.6.4 Have the ability to indicate location of mishap within the GIS map.

3.6.5 Provide secure reporting of mishap information.

3.7 Operational execution of mission capabilities shall:

3.7.1 Have the ability to send and receive images, text, and completed ICS forms between ed away from the Incident mobile devices of operations personnel who are deploy

Command Post and operations section personnel in the Incident Command Post.

3.7.2 Have the ability to receive and upload a geo‐tagged photo directly to the GIS map using the photo’s metadata from operations personnel using mobile devices.

3.8 laP nning for execution of mission capabilities shall:

3.8.1 Have ICS forms and workflow process that:

3.8.1.1 Have the ability to virtually create, modify, save, archive, output and print documents to produce an IAP using the USCG ICS forms and planning processes outlined in the CG‐IMH 2014 edition.

3.8.1.2 Include all USCG ICS forms listed in the CG‐IMH and available at https://homeport.uscg.mil/ics.

3.8.1.3 Convert new forms created by the USCG HQ Program Manager to utilize in system.

3.8.1.4 Have the ability to edit forms based on incident specific needs.

3.8.1.5 Have the ability to automatically map data from the primary entry form to secondary forms based on operational period and shifts if multiple shifts of al period.

t, at a minimum, map to CG personnel are on duty during a single operation

3.8.1.5.1 CG ICS Form 211 (Check‐in List) data mus

ICS Forms 203 (Org Assignment List), 204 (Assignment List), 205a to tically map the ICS forms.

eriods.

(Comms List), and 207 (Org Chart);

3.8.1.5.2 CG ICS Form 202 (Incident Objectives) data must map to CG ICS Form

234 (Work Analysis Matrix);

S 3.8.1.5.3 CG ICS Form 234 (Work Analysis Matrix) data must map to the CG IC

Form 215 (Operational Planning Worksheet); and rksheet) data must map 3.8.1.5.4 CG ICS Form 215 (Operational Planning Wo the CG ICS Form 204 (Assignment List).

3.8.1.6 Have the ability to define the operational period and automa ctions of the USCG ent operational p operational period into the appropriate se

3.8.1.7 Have the ability to transfer data to subsequ

2.9 The Government owns all data entered into the database. Not more than twice per contract year, USCG may require that the Contractor provide files that contain all products, designs, drawings and outputs that USCG developed using the software. The files shall comply with section 3.2.5 and 3.9.1 standard data set formats. In accordance standard industry practice and within 30 days of request, the Contractor shall deliver the files to USCG and provide assistance that enables the Government to access, migrate, and convert to database into useable formats.