Attachment_1_-_Statement_of_Requirements.pdf

Attachment 1

HSCG23-14-R-MPE209

S tatement of Requirements (SOR)

U.S. COAST GUARD INCIDENT MANAGEMENT AND INCIDENT ACTION

PLANNING SOFTWARE SYSTEM

1 GENERAL

1.1 SCOPE

The U.S. Coast Guard (USCG) seeks an Indefinite Delivery/Indefinite Quantity (IDIQ) contract to purchase software licenses for commercial incident management and incident action planning (IAP) software.

1.2 PLACE OF PERFORMANCE

The place of performance shall be the Contractor’s facility, except for training which will be at USCG Headquarters, Areas, Districts, Sectors, Marine Safety Units (MSU), and Bases.

(http://www.uscg.mil/top/units/).

1.3 PERIOD OF PERFORMANCE

There are five (5) consecutive ordering periods of one (1) year each.

1.4 ONTRACTOR PERSONNEL

C

1.4.1 The Contractor shall provide a point of contact (POC) as follows:

The POC shall be responsible for all Contractor work performed under this contract and resulting delivery orders. The POC shall coordinate a kick‐off meeting with the USCG within 10 working days of the contract award date.

The POC shall be the Contractor’s primary representative. The name of the POC, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the POC, shall be provided to the USCG. The POC shall respond to a request for discussion or resolution of technical problems within 24 hours of notification.

1.4.2 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 military uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure its employees present a professional appearance while working at Government facilities.

1.5 ACB KGROUND

1.5.1 SCG l ation technology suite of capabilities to

ment, which includes:

ICS

IAP

The U acks an enterprise wide inform nagesupport information and incident ma

1.5.1.1 form creation and storage.

1.5.1.2 creation and storage.

1.5.1.3 Tactical Command & Control Capabilities.

1.5.1.4 Data archiving and Freedom of Information Act (FOIA) request management.

http://www.uscg.mil/top/units/

HSCG23-14- ER-MP

memos

1.5.2 The USCG has identified countless lessons learned, after action reports, and documenting the need for improved Information Management during an incident, including reports developed as a result of the Deepwater Horizon (DWH) incident in 2010, http://www.uscg.mil/foia/FOIA_Library.asp.

1.5.3 The USCG has identified this enterprise wide software solution for Incident H 1.3.2

Management and IAP development as a corrective solution to resolve the DW Lesson Learned 3.1.3.1 – Develop Authoritative, Shared Information Systems, 3.

– Formalize Information and Communication Requirements, and 3.1.3.4 – Improve Command, Control, Communications, Computers, and Information Technology (C4IT) Capability.

Some USCG operational units have purchased single unit licenses for Incident se‐

1.5.4 t d incident preparedness activities.

2.2 In coordination with the Program Manager (Commandant (CG-761)) and Sponsor (Commandant (CG-CPE)), the Contractor shall:

2.2.1 Develop a configuration and implementation plan defining user roles/responsibilities and data interfaces/access.

2.2.2 Develop a training plan that provides an outline or overview describing the schedule, the instructors, the user guide, core skills to be learned, key learning objectives, and how feedback will be solicited.

2.3 The Contractor shall deliver the items in section 2.2 no later than 2 months after award of initial task order.

2.4 The Government will reimburse the Contractor for travel expenses in support of SOW 2.2 only.

2.5 Conduct initial on-site training and configuration at each unit: within 12 months of license purchase in year one of the contract and within 3 months of license purchase during the remainder of the contract. The number of users in each training course will be 10 - 20.

2.6 Have no unique obstacles introduced by this product that would prohibit the Government from providing product training.

2.7 Provide follow on training at USCG units upon request. This training shall be identical to initial on-site training.

2.8 USCG Incident Management Activities to be supported by the software include:

2.8.1 Command and Control of the mission.

Management and IAP Software systems. This contract will provide an enterpri wide standard USCG system.

2 GENERAL REQUIREMENTS

2.1 Provide a ready to use, software solution to support all functional areas of USCG Inciden Management, IAP development, an http://www.uscg.mil/foia/FOIA_Library.asp

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 ise support.

phic se and development er contract ts, es shall ndard liver the files to igrate, and convert this section not d users authorized per site.

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 real time.

2.8.11 Simulation and exerc

2.8.12 Preplanning and development of Conti ngency Plans, draft IAPs, and geogra response data to support a more efficient initial incident respon of the initial IAP.

T2.9 he Government owns all data entered into the database. Not more than twice p y all produc d e. The fil rdance sta ear, USCG may require that the Contractor provide files that contain esigns, drawings and outputs that USCG developed using the softwar c ard data set formats. In acco quest, the Contractor shall de the Government to access, m omply with section 3.2.5 and 3.9.1 stand industry practice and within 30 days of re USCG and provide assistance that enables to database into useable formats.

3 MINIMUM SYSTEM REQUIREMENTS

o the minimum requirements of

The C ntractor’s system and software shall meet later than 120 days after the contract award date.

3.1 T eh

I system shall:

3.1.1 nclude individual site licenses for 300 USCG‐approve

HSCG23-14-R E209 -MP

3.1.2 Permit ite licenses to be transferrable between USCG units.

3.1.3 Have the ability to track, manage, and input a minimum of 100 concurrent active ts a s inciden cross the USCG enterprise.

3.1.4 Provide a summary view of all active incidents as an interactive GIS layer.

3.1.5 Allow for summary view for additional details summary and include a link to n individual incident icon is clicked within the GIS detailed incident information whe layer.

3.1.6 Allow for summary view for user to toggle on and off individual incident map layers from active incidents within the GIS layer.

3.1.7 Include a digital library of USCG approved plans and form examples or templates for import and use during an incident. Plans and forms are available at:

https://homeport.uscg.mil/ics.

3.1.8 Provide full access to a 24/7 user support/help line.

3.1.9 Include a comprehensive integrated self service help tool (online system job aids, tutorials, and support tools).

3.1.10 Include a comprehensive user an

d administrator guide.

n design and requires minimal training e y

3.1.11 Have a user interface (UI) that is intuitive i

(less than or equal to 3 days) after which the user can operate with minor assistanc from user support/help line.

3.1.12 Have no unique obstacles introduced by this product that would prohibit the Government from providing product training.

3 on exchange and data

3.1.1 Meet or be upgraded prior to USCG use to meet the informati standards set forth in Department of Homeland Security (DHS) Management Polic

MD103‐01.

erated 3.1.14 Allow the Government to access, retain, and reuse all data and outputs gen through the use of the system.

3.2 Hardware and Software capabilities shall:

3.2.1 Allow access to the software using Microsoft Internet Explorer version 9 and higher via a portal

3.2.2 Be hosted on a secure non‐USCG system (e.g. cloud‐based infrastructure)

3.2.3 Comply with DHS 4300A DHS Sensitive System Policy and the DHS 4300A Sensitive Systems Handbook, to store sensitive but unclassified information, including but not limited to Law Enforcement Sensitive Information, For Official Use Only (FOUO), and Personally Identifiable Information (PII).

HSCG 32

-14-R-MPE209

https://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4300a_policy_v8.pdf

3.2.3.1 The Contractor will be subject to Security Review Terms and Conditions:

to ensure that the securityThe Government may elect to conduct periodic reviews requirements contained in this contract are being implemented and enforced. The Contractor shall afford DHS, including the organization of the DHS Office of the Chief Information Officer, the Office of the Inspector General, authorized COR, and other Government oversight organizations, access to the Contractor's facilities, ation installations, operations, documentation, databases and personnel used in the performance of this contract. The Contractor will contact the DHS Chief Inform Security Officer to coordinate and participate in the review and inspection activity of Government oversight organizations external to the DHS. Access shall be provided to the extent necessary for the Government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of DHS data or the function of computer systems operated on behalf of DHS, and to preserve evidence of computer crime.

3.2.4 Comply with Federal Government accessibility requirements (Section 508):

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105‐220) requires that when Federal agencies develop, procure, maintain, or use electronic and information technology (EIT), they must ensure that s of the it is accessible to people with disabilities. Federal employees and member public who have disabilities must have equal access to and use of information and data that is comparable to that enjoyed by non‐disabled Federal employees and members of the public.

http://www.section508.gov/Section‐508‐Of‐The‐Rehabilitation‐Act

3.2.4.1 All EIT deliverables within this work statement shall comply with the pplicable technical and functional performance criteria of Section 508 unless a exempt.

Specifically, the following applicable EIT accessibility standards have been identified:

36 CFR 1194.21 Software Applications and Operating Systems, applies to all EIT software applications and operating systems procured or developed under this work statement including but not limited to GOTS and COTS software. In addition, this standard is to be applied to Web‐based applications when needed to fulfill the functional performance criteria. This standard also applies to some Web based applications as described within 36

CFR 1194.22.

http://www.gpo.gov/fdsys/pkg/CFR‐2011‐title36‐vol3/xml/CFR‐2011‐ title36‐vol3‐sec1194‐21.xml

36 CFR 1194.22 Web‐based Intranet and Internet Information and Applications, applies to all Web‐based deliverables, including documentation https://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4300a_policy_v8.pdf https://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4300a_policy_v8.pdf https://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4300a_policy_v8.pdf https://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4300a_policy_v8.pdf

-14-R-MPE209

and reports procured or developed under this work statement. When any Web application uses a dynamic (non‐static) interface, embeds custom user control(s), embeds video or multimedia, uses proprietary or technical approaches such as, but not limited to, Flash or Asynchronous Javascript and XML (AJAX) then 1194.21 Software standards also apply to fulfill functional performance criteria. http://www.gpo.gov/fdsys/pkg/CFR‐2012‐title36‐ vol3/xml/CFR‐2012‐title36‐vol3‐part1194.xml#seqnum1194.22

36 CFR 1194.31 Functional Performance Criteria, applies to all EIT deliverables regardless of delivery method. All EIT deliverable shall use technical standards, regardless of technology, to fulfill the functional performance criteria. http://www.gpo.gov/fdsys/pkg/CFR‐2012‐title36‐ vol3/xml/CFR‐2012‐title36‐vol3‐part1194.xml#seqnum1194.31

6 CFR 1194.41 Information Documentation and Support, applies to all 3 documents, reports, as well as help and support services. To ensure that documents and reports fulfill the required 1194.31 Functional Performance Criteria, they shall comply with the technical standard associated with Web‐ based Intranet and Internet Information and Applications at a minimum. In addition, any help or support provided in this work statement that offer telephone support, such as, but not limited to, a help desk shall have the ability to transmit and receive messages using TTY.

http://www.gpo.gov/fdsys/pkg/CFR‐2012‐title36‐vol3/xml/CFR‐2012‐ title36‐vol3‐part1194.xml#seqnum1194.31

3.2.4.2 Section 508 Applicable Exceptions

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’s Technical Representative (COTR) and determination will be made in accordance with DHS MD 4010.2.

http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_40102_section_50 8_program_management_office_and_information_technology_accessibility.pdf

DHS has identified the following exceptions that may apply: 36 CFR 1194.3(b) http://www.gpo.gov/fdsys/pkg/CFR‐2011‐title36‐vol3/pdf/CFR‐2011‐ title36‐vol3‐sec1194‐3.pdf Incidental to Contract, all EIT that is exclusively s not y owned and used by the Contractor to fulfill this work statement doe require compliance with Section 508. This exception does not apply to an EIT deliverable, service or item that will be used by any Federal employe or member(s) of the public. This exception only applies to those Contracto assigned to fulfill the obligations of this work statement and for the purpo f this requirement, are not considered members of the public.

e(s) rs ses

3.2.5 Utilize

Nation https:/ o a common data set stored in a secure system that conforms to the DHS al Information Exchange Model (NEIM) /www.niem.gov/Pages/default.aspx. If system does not currently meet this ement provide upgrade plan with bid. requir http://www.section508.gov/Section-508-Of-The-Rehabilitation-Act http://www.section508.gov/Section-508-Of-The-Rehabilitation-Act http://www.section508.gov/Section-508-Of-The-Rehabilitation-Act http://www.section508.gov/Section-508-Of-The-Rehabilitation-Act http://www.section508.gov/Section-508-Of-The-Rehabilitation-Act http://www.gpo.gov/fdsys/pkg/CFR-2011-title36-vol3/xml/CFR-2011-title36-vol3-sec1194-21.xml http://www.gpo.gov/fdsys/pkg/CFR-2011-title36-vol3/xml/CFR-2011-title36-vol3-sec1194-21.xml http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.22 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 pliant with DHS Enterprise Architecture Compliance Terms and Conditions:

utions and services shall meet DHS Enterprise Architecture policies, rds, and procedures.

www.dhs.gov/xlibrary/assets/foia/mgmt_directive_0007_1_information_te

3.2.6 Be com

All sol standa http:// c hnology_integration_and_management.pdf the following Homeland Security p e standa Manag

Specifically, the Contractor shall comply with Enter Refer rise Architecture (HLS EA) requirements:

All developed solutions and requirements shall be compliant with HLS EA.

All IT hardware and software shall be compliant with the HLS EA Technical nce Model (TRM) Standards and Products Profile.

Description information for all data assets, information exchanges and data rds, whether adopted or developed, shall be submitted to the Enterprise Data ement Office (EDMO) http://www.dhs.gov/enhancing‐datagov for review, a_ approv Archit http:// al and insertion into the DHS Data Reference Model and Enterprise ecture Information Repository.

www.dhs.gov/xlibrary/assets/foia/mgmt_directive_103_01_enterprise_dat management_policy.pdf Development of data assets, information exchanges and data standards will y with the DHS Data Management Policy MD 103‐01 and all data‐related ts will be developed and validated according to DHS data management ctural guidelines.

www.dhs.gov/xlibrary/assets/foia/mgmt_directive_103_01_enterprise_data_ compl artifac archite http:// management_policy.pdf

• Applicability of Internet Protocol Version 6 (IPv6) to DHS‐related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M‐05‐22, August 2, 2005) regardless of whether the acquisition is for

/m05‐ modification, upgrade, or replacement.

http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005 22.pdf All EA‐related component acquisitions shall be IPv6 compliant as defined in the U.S.

Government Version 6 (USGv6) Profile National Institute of Standards and Technology (MIST) Special Publication 500‐267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

http://www‐x.antd.nist.gov/usgv6/docs/usgv6‐v1.pdf

3.2.7

3.2.8

3.2.9

3.2.10

Have the ability to access data across all network server regions.

Have the ability to use system both inside and outside of the USCG data network (CGOne) environments.

Have the ability to run web‐based application without the need for additional plug‐ ins for Window Internet Explorer, v9.

Have the ability to import .pdf incident action plans, display basic incident information on the GIS, and manually enter basic incident information for any http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.gpo.gov/fdsys/pkg/CFR-2012-title36-vol3/xml/CFR-2012-title36-vol3-part1194.xml#seqnum1194.31 http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_0007_1_information_technology_integration_and_management.pdf http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_0007_1_information_technology_integration_and_management.pdf ciden

3.2.11

3.2.12

3.2.13

3.2.14

3.2.15

3.2.16

3.2.17 e_an in t 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.

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

e. not cause system degradation that negatively impacts user processing tim

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

Maintain a redundant real time backup system.

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

Have a disaster recovery capability to reestablish full operating capability in no less 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.

3.3 Users and Access Control capabilities shall:

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

y and

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

http://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4900_individual_us 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 real time track changes and ability to roll back to previous versions.

ities.

ities b

3.3.5 Have the ability to define user roles, access, responsibilities, and author onsibilities, and author ment Handbook (

3.3.6 Have the ability to create user roles, access, resp ased CG‐IMH) on ICS position described in the USCG Incident Manage

2014 edition. https://homeport.uscg.mil/ics.

3.3.7 Have the ability to assign system administrator roles and responsibilities to USCG members.

HSCG 3-2

stem, incident.

ICS

s

P ll:

dministrator granted ips, 14-R-MPE209

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

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

03.3.1 Have the ability to limit users from viewing and/or editing incidents that they are not assigned in order to prevent personnel from editing another incident by 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.

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

3.4.3 Provide an online mapping tool that integrates both static and 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 required. Online mapping tool use does not require the expertise of a GIS specialist to develop and display a basic incident specific situation map layer.

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

e3.4.6 Have the ability to include GIS layers of information from existing Government sit and/or files.

sha3.5 ublic information and social media support for execution of the mission capabilities

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

3.5.2 Allow specified users to disseminate messages instantly: SMS Text Messages, Text‐ 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 a access levels, to collaborate on content including news release, photos, video cl and audio clips in an area inaccessible by the public. This capability must also provide complete version control and recall.

3.5.4 Comply with USCG public affairs branding standards.

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

3.6.1 Digitally support development of the Site Safety and Health Plan (ICS 208‐CG) and

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.

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

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 mobile devices of operations personnel who are deployed away from the Inciden Command Post and operations section personnel in the Incident Command Post.

t

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 Planning 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 Have the ability to create and add new forms to

3.8.1.4 Have the ability to edit forms based on incident

the system.

specific needs.

p to the CG ICS ta must map to

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 personnel are on duty during a single operational period.

3.8.1.5.1 CG ICS Form 211 (Check‐in List) data must, at a minimum, map to CG ICS Forms 203 (Org Assignment List), 204 (Assignment List), 205a to CG ICS Form (Comms List), and 207 (Org Chart);

3.8.1.5.2 CG ICS Form 202 (Incident Objectives) data must map 234 (Work Analysis Matrix);

trix) data must ma rksheet); and ing Worksheet) da

3.8.1.5.3 CG ICS Form 234 (Work Analysis Ma

Form 215 (Operational Planning Wo

3.8.1.5.4 CG ICS Form 215 (Operational Plann

the CG ICS Form 204 (Assignment List).

3.8.1.6 Have the ability to define the operational period and automatically map the operational period into the appropriate sections of the USCG ICS forms.

3.8.1.7 Have the ability to transfer data to subsequent operational periods.

lly based s

3.8.2

-14-R-MPE209

3.8.1.8 Have the ability to package several forms to create an IAP that can be digita signed within the system as a locked set of documents ready for n the same standardized dissemination.

8.13. s .9 Have the ability to export or print form form i at/layout as the current CG ICS forms.

3.8.1.10 Have the ability to accept images (electronic charts, jpeg, bmp, etc) as part of the IAP.

Hav hat 3.8.1.11 e the ability to create an image from the GIS system and import t ima Hav G on t ge into the IAP forms.

3.8.1.12 e the ability to auto populate an organizational chart, ICS‐207‐C he ICS‐203‐CG information.

3.8.1.1 Have forms within the system that are both user friendly for data input and in a standard template format that will print without needing to modify page rt setup parameters and in a format that is recognized by common computer systems.

3.8.1.14 Have the ability to print the IAP as a single document, save as .pdf, and expo the IAP to other formats to improve interagency functionality.

3.8.1.15 Have the IAP approvals tied to ownership of form and order of preparation a described in the CG‐IMH.

Provide a digital ICS‐233 “open action tracking” process that includes automatic ndocumenti g and tracking and closing of open actions, assigned POCs for each action and due dates/times.

3.8.3 Have the ability to develop a demobilization plan. See examples at https://homeport.uscg.mil/ics.

3.8.4 Have the ability to develop draft unit‐specific CG ICS forms data and preset geographic response data for future use.

onal a3.9 Situati wareness and dissemination capabilities shall:

, mo3.9.1 Create dify, save, and export open source geospatial Schemas or data layers, a defined by the Open Geospatial Consortium, ww s http:// w.opengeospatial.org/standards, which can be imported into other GIS viewers via a centralized data set updated in real time. An example of other

Government GIS viewers include, but are not limited to, the National Oceanic and Atmospheric Administration (NOAA) Environmental Response Management Application (ERMA, http://response.restoration.noaa.gov/maps‐and‐spatial‐ data/environmental‐response‐management‐application‐erma), the USCG One View (CG1V), and the Homeland Security Information Network (HSIN).

3.9.2 Have the ability to create, modify, save, and export an incident map using the GIS s system

3.9.3 Have the ability to create consolidated situational information and communication about an incident or multiple incidents for agency leadership, maritime stakeholders, and the public.

HSCG23-14-R-MP

defined s centralized data layers.

user, E209

3.9.4 Have the ability to import data from common GIS information exchange as by the federal geographic data committee. (For example, import information from NOAA’s suite of oil, hazmat, wind/water modeling applications)

3.9.5 Have the ability to create situation report and export the report in various format (.pdf, word, zip, etc.).

3.9.6 Have the ability to transmit situation reports via email or upload to repository for higher level users to view and download.

3.9.7 Have the ability to import digital contingency plans and their associated GIS

3.9.8 Allow for the user to specify and save default views and visible layer sets by unit, and incident.

3.10 Logistical support for execution of the mission capabilities shall:

3.10.1 Have the ability to document and track the ordering, check‐in, assignment, and demobilization of a resource.

3.10.2 Have the ability to document and track the ordering, arrival, use, and disposition of supplies and other logistical support items.

3.10.3 Have the ability to produce a logistical summary report on those items being documented and tracked by logistics.

3.11 Resource Management of the Mission capabilities shall:

3.11.1 Include personnel resource management (check‐in, check‐out, reassignment, demobilization, etc.) as defined by National Incident Management System (NIMS) and described in the CG‐IMH and Resource and Demobilization Unit Leader Job Aid found at https://homeport.uscg.mil/ics under job aids.

3.11.2 Digitize and automate the ICS‐213RR work flow management processes related to requests, approval, ordering, and receipt of resources. (See USCG Resource R on pages 113 through 115 of the Resource Unit Leader Job Aid found at https://homeport.uscg.mil/ics under job aids.)

3.11.3 Provide the data management of resource status (available, assigned, out of service).

3.11.4 Have the ability to auto calculate ICS‐209‐CG information based on resource ocument hours worked by a resource.

management data.

F

3.12 inancial documentation and support for execution of the mission. The system shall:

3.12.1 Have the ability to assign hourly or daily rates to a resource being managed within the system.

3.12.2 Have the ability to d

3.12.3 Maintain work flow management of financial processes related to procurement requests, ordering, and receipt of resources.

3.12.4 Maintain a financial accounting and calculation process to develop and report incident response costs.

3.13 The system shall have the ability to operate in a simulation/training/exercise mode.

3.14 The price of each software license shall include all features and functions in section

4 GOVERNMENT FURNISHED RESOURCES

3.

The Government will furnish applicable documents, necessary access to Government owned software and data, and training manuals required for integration into the proposed incident management and IAP software system solution.

5 CONTRACTOR FURNISHED RESOURCES

The Contractor shall be required to provide all resources to meet the requirements of this SOR except for the resources listed in section 4.

6 REFERENCES

The following references are provided for these requirements:

ent 6.1 USCG Homeport Incident Command System documents including the USCG Incid Management Handbook, USCG ICS Forms, USCG Position Job Aids:

https://Homeport.uscg.mil/ics

6.2 CG 5136 excel document:

http://www.uscg.mil/npfc/docs/PDFs/JA‐10‐4_NPFC‐JobAid_CG‐5136.pdf and http://www.uscg.mil/npfc/docs/Others/e5136O_Large.xlsx

6.3 Response Resource Inventory System (RRI) data:

https://cgrri.uscg.mil/logon.aspx?ReturnUrl=%2fdefault.aspx

6.4 DHS Management Directive 4900:

ophttp://www.dhs.gov/xlibrary/assets/foia/mgmt_directive_4900_individual_use_and_ era tion_of_dhs_information_systems_computers.pdf

6.5 FEMA Credentialing Guidance:

http://www.fema.gov/pdf/emergency/nims/nims_cred_guidelines_report.pdf

6.6 FIPS 201:

http://www.nist.org/nist_plugins/content/content.php?content.49

6.7 DHS Sensitive Systems Policy Directive 4300A:

6.8 DHS National Information Exchange Model (NEIM):

https://www.niem.gov/Pages/default.aspx

6.9 Section 508 Amendment to the Rehabilitation Act of 1973

http://www.section508.gov/Section‐508‐Of‐The‐Rehabilitation‐Act

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.