rfpv-eoc-pt2-011510k1457.doc - Hennepin County_ Minnesota

Document Sample
rfpv-eoc-pt2-011510k1457.doc - Hennepin County_ Minnesota Powered By Docstoc
					                             REQUEST FOR PROPOSALS
              Virtual Emergency Operations Center (EOC) Enhancements
                            Part 2 – System Requirements
Item
No.       Functionality                                   S   C    N              Comments

Part 2 – This section consists of Technical Architecture requirements as well as
Operational requirements.

Technical Architecture
It is important that the County‟s project team obtain a clear understanding of a recommended
solution and the architecture required to support that technology. A proposal is expected to
provide sufficient details to help the County determine how the recommended solution will
conform to current enterprise architecture existing within the County, as well as meeting the
intent of those user requirements listed in the following tables.

The County encourages proposals with innovative solutions that use mainstream technologies
and established professional practices. The County realizes that commercial off the shelf
software will not comply with all aspects of the architecture. All proposals will be considered
regardless of the level of architectural compliance, although the County reserves the right to
exclude proposals that are not compliant with the County‟s Enterprise Technical Architecture
(ETA).

To assist the County with the review and evaluation of your proposal, a proposal needs to
include an explanation of architecture. Please review the County information systems
environment described below. The availability of applications that fit into the ETA is one of the
factors that will influence the decision as to whether to purchase an application, which
proposal will be selected, and what services will be outsourced.

Processes do exist to keep the ETA current as technologies and professional practices evolve.
Proposers are encouraged to explain the merits of a solution requiring architecture different
from the County ETA. Elements of proposals that do not comply will be reviewed by the Office
of the CIO. As a result, new technologies and practices may be added to the ETA, the project
may receive a one-time architectural variance, or the proposal may be rejected.

   Guide to Existing Hennepin County Enterprise Technical Architecture

   (See also attached diagrams at the end of this document)

   Background – Public Works

   The following information explains the operational and technical environment in which a
   recommended solution will be employed at the County.

   The primary operating department responsible for obtaining, implementing and using recommended
   solutions is the Emergency Preparedness Department within Hennepin County Public Works. The
   overview below is provided for enhanced understanding of the operations provided and to help identify
   other areas where benefits may be achieved through the deployment of a proposed recommendation.

   The mission of Public Works is to “strengthen economic vitality and quality of life through
   environmental stewardship; support of strong, healthy, and safe communities; wise investments in
   economic development; and affordable housing and provision of accessible transportation choices”.

   Public Works staff are housed in the downtown Government Center, the Environmental Services
   Building, and the Medina Public Works facility. Public Works staff is highly mobile with about one
   third of the staff working in vehicles and remote locations throughout the County. Mobile staff duties
   range from snow plow operators to inspectors, each presenting unique challenges for network
   connectivity.

Hennepin County RFP                                                    Emergency Operations Center (EOC)
10/20/2011                                             RFP Part 2, Section 2 Requirements - Page 1 of 29
                                REQUEST FOR PROPOSALS
                 Virtual Emergency Operations Center (EOC) Enhancements
                               Part 2 – System Requirements
    Item
    No.      Functionality                                    S   C    N              Comments


      Public Works maintains 2013 miles of roadways, 141 bridges, approximately 800 traffic signals and
      50,000 traffic signs. Public Works also manages the Energy Center, HERC Waste Recovery (burn)
      facility and three waste/recycle centers. Technology applications used in the planning, design,
      construction and operations of this infrastructure are numerous and range from interactive highway
      design tools to various engineering and analysis tools. Recent implementations include Project
      Management Accounting, Electronic Approval, Inventory and Fleet Management software, Solid Waste
      System, and Automatic Vehicle Location (AVL) equipment.

      Public Works has approximately 85 applications that range from desktop to Web based server
      systems. The majority of the applications are hosted by the central data center primarily on virtual
      servers and using SQL database servers. Some of the applications are hosted externally for various
      reasons. Sharing information with non-county organizations, etc., is one primary reason for external
      hosting. The Virtual Emergency Operations Center project will result in a significant increase in
      system accessibility by external parties, including the municipalities, major cities, other counties and
      emergency business partners

      Overview of Technology at Hennepin County

      Hennepin County is regarded nationally as a leader in the adoption of technology as a vehicle for
      improving its service delivery. From an enterprise perspective, Hennepin County has historically
      taken an active stance toward replacement of legacy technologies, ranging from adoption of predictable
      depreciation cycles for computer hardware to modernization initiatives for critical countywide business
      applications. This progressive approach to leveraging technology places Hennepin County in an
      enviable position among its peers: our attention can be focused on how to maximize the benefits of
      technology investments rather than how to catch up by providing basic computing equipment to
      County employees.

      Even before the recent economic downturn, The County Board and County Administration began
      asking whether sufficient business benefits are being achieved from the technology investments of
      departments. The current recession has only heightened the need and urgency to answer these cost-
      benefit questions.

      Strategic technology capabilities for Hennepin County include:
          Expansion of mobile technology tools including laptops, tablet PCs, blackberries and broadband
           cards so appropriate staff have access to critical information when and where they need it.
          Integration with State and other agency systems so staff has real-time access to critical
           information regarding clients and business. Service Oriented Architecture based systems are the
           basis of this integration.
          Document management and workflow systems such as Electronic Case File system so staff has
           immediate access to critical documents issued by the courts, human services or treatment
           providers.
          E-Government and electronic forms and self service capabilities for community, staff, contracted
           workers, and state/federal agencies.
          Controlled & Secure Access to systems for non Hennepin employee staff, e.g. contracted case
      workers, employee counselors, community volunteers, Municipalities, business partners, outside
      agencies (i.e. Red Cross).

      IT Infrastructure Current State

      Exhibit B and C provide a visual depiction of the current state infrastructure. These visuals and the
      information provide below is intended to provide an insight into the architecture employed within the
      County. As noted, the county currently has approximately 700 servers, 174 TB SAN-Storage, 1850 TB
      tape backup, 10500 network data connections, 5,200 GHZ total processor capacity, 8500 Lotus Notes
      users, 14,300 Hennepin County network connections, 1,630 Outside Agency network connections and

    Hennepin County RFP                                                    Emergency Operations Center (EOC)
    10/20/2011                                             RFP Part 2, Section 2 Requirements - Page 2 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                   S    C   N               Comments

  9,968 telecomm connections. Server and storage capacities have been growing at 20% annually. The
  mainframe environment is being decommissioned, therefore no solutions should be recommended that
  have dependency on that architecture.

  Number of Servers by Role and by Operating System
  Servers                            Quantity      Operating System                             Quantity
  Application Server                       222     Windows 2003 Standard Edition                    408
  Database Servers                          54     Windows 2003 Enterrpise                          102
                                                   Edition
  Virtual Servers                          253     Win2003 R2 (X64) Enterprise                            6
                                                   Edition
  Virtual Host Servers                      24     Win 2000 Server and Advanced                           26
                                                   Server
  Web Servers                               31     Citrix Gateway Appliance                                4
  Infrastructure & Other                   148     ESX 3x                                                 24
                                                   Suse Linux 10                                          73
                                                   Red Hat Linux 5                                        58
                                                   Other                                                  31
  Total                                    732     Total                                                 732

  Processor Capacity:
  3,755 GHZ Wintel processor capacity
  544 GHZ Linux processor capacity
  635 GHZ Virtual processor capacity
  284 GHZ DNZ processor capacity
  5,218 GHZ total processor capacity

  Typical Server Hardware:
  HP ProLiant DL380 G5 2.50GHz LV Server
  Quad-Core Intel® Xeon® L5420 (2.50GHz, 1333MHz FSB, 50W) Processor
  2 Quad-Core AMD Opteron 8354 Processors (2.2 GHz, 75 Watts)
  HP 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive

  VIDEO CONFERENCING
  Codian and Tandberg equipment has been installed at both Data Centers which provides video
  conferencing connectivity between external-to-internal as well as internal-to-internal County
  customers. Codian MCU‟s provide secured conferencing resources and Tandberg VCS provides call
  control and firewall traversal. The Cisco 3545 is integrated into the VoIP platform and is currently
  serving customers who use the Cisco VT Advantage video telephony solution (Department of
  Community Corrections, Public Works, and District Court).

  Voice Lines
  Centralized PRI lines are currently running on 3 DS3 Trunks Terminating with Qwest. 25 PRI lines
  provide core TDM connectivity and these lines allow for a sustained 575 concurrent calls on the VoIP
  Platform. 3 PRI lines providing dedicated long distance connectivity for a less expensive long distance
  rate. 7 PRI lines are providing dedicated TDM circuits for specific call center applications. There are
  approximately 2,499 Centrex phones currently deployed that need to be converted to VOIP. There are
  approximately 1,000 individual lines providing connectivity for Fax, Emergency Services (SRST, Alarm,
  Fire) and telecommuters.

  VOIP
  Cisco Call Manager supports 9,968 VOIP handsets installed throughout the County enterprise
  network.
  The Call Manager cluster is made up of a set of servers installed at each Data Center for fault
  tolerance and disaster recovery. Cisco Emergency Responder (CER) provides e911 support to VOIP

Hennepin County RFP                                                   Emergency Operations Center (EOC)
10/20/2011                                            RFP Part 2, Section 2 Requirements - Page 3 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                   S   C   N               Comments

  handsets and must use Cisco Discovery Protocol (CDP) between the CER servers located in each Data
  Center and the 9,968 VOIP handsets installed on access layer switches. Centralized Conference
  Bridging and Transcoding resources are deployed at both Data Centers which provides customers with
  advanced phone feature functionality.

  Remote Access
  Several remote access solutions are available to the County including the following:
    SSL VPN – Dedicated appliances installed in each Data Center support access through the Internet
     to the internal County network. Capabilities include the ability to support pandemic disaster
     scenarios for up to 10,000 simultaneous users through burstable one gigabit Internet connectivity.
    Netmotion – client based dynamic VPN solution which allows access over many technologies such
     as Sprint Wireless, WiFi, Internet, and 700mhz to the internal County network.
    RAS - standard dialup/ISDN remote access solution to the internal County network.
    SOHO (Small Office Home Office) – site-to-site VPN solution across the Internet; SOHO box also
     provides wireless and support of VOIP handsets to the remote small office.


  Internet
  Fault tolerant access to the Internet is supported through separate 1 gigabit burstable connections to
  separate ISPs through each Data Center. Support for the County‟s Internet web/email presence is
  through fault tolerant firewalls located in each Data Center. Each Data Center runs in an active/active
  mode in order to optimize access to/from the Internet, for load balancing, and for fault tolerance.
  Secure access to the Internet as well as for the Internet service DMZ is through firewalls, Intrusion
  Detection appliances
  (IDS reporting and IPS action), and web filtering. Load balancers are installed in both the outside
  DMZs at each Internet presence in each Data Center as well as on the internal network; this supports
  load balancing. DMZ based web/email/DNS/FTP servers are installed as pods which follow the same
  architecture as internal Data Center based file servers.

  Extranet
  The network supports non-Internet based connectivity to external entities including the following:
    State of MN and all of its agencies through dedicated fiber, firewall, and site-to-site VPN tunnels
     based on IPSEC standards. Separate VPN tunnels are established across MNet to each MNet based
     agency.
    Access to Logis (Local Government Information Systems) and Logis based municipalities.
    Direct connectivity to non-Logis based municipalities such as Brooklyn Park and Champlin.
    Direct connectivity to several Title Insurance companies over T1 PPP data circuits.


ETA Responses - Provide your response to the following questions and requests directly
following each item.

1.0 Application Architecture

   1.1 Provide a description of your proposed technologies and approach along with a concise
       explanation describing the rational for the architectural choices.

   1.2 Describe the architectural direction and timeframe for planned and future versions of
       the proposed software.

   1.3 Describe how future product release cycles will be managed and licensed. Provide a
       description of overall application topology.


Hennepin County RFP                                                  Emergency Operations Center (EOC)
10/20/2011                                           RFP Part 2, Section 2 Requirements - Page 4 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                S   C   N               Comments

   1.4 Describe how user presentation, business logic, and data access functions are
       partitioned.

   1.5 If the proposal includes the development of software components describe the overall
       application development approach, the design artifacts that will be produced, and how
       the artifacts will be reviewed and approved throughout the project lifecycle.

   1.6 Describe any required programming languages, component deployment environments,
       development environments, database access, transaction-processing monitors, or
       major application components not classified as current or emerging in the application
       architecture matrix.

Operational Requirements

Please indicate your response to each operational requirement presented in table format below.
A response must be provided for each item listed. Failure to provide all mandatory
requirements SHALL be cause for rejection of a proposal.

Requirements specific to a particular component of the EOC system are noted with a
designator in parenthesis at the beginning of the requirement. Refer to Table 1 for an
explanation of the designator.

Requirements that are mandatory in the system are indicated by the term “must".
Requirements that are not mandatory, but highly desirable in the system are indicated by the
term “should”. Place an "X" in the appropriate column. The three column headings represent
the following:

   S (Standard System) – This function is part of the standard system being proposed.

   C (Customization Required – Not standard System) – This function is not a part of the
   standard system and will require customization, which will be completed and included in
   the system at the time of installation. If a specification will be accomplished through site-
   specific custom programming, proposer must indicate any additional fees (including time,
   materials and any other costs whatsoever related to the proposer‟s services) and include the
   cost of the custom programming on the proposal form.

   N (Not Available) – This function is not a part of the standard system and will not be
   provided with the installed system.

   Comments – Comments should be provided as needed to clarify answers or to respond to a
   requirement to describe a feature or request for informaiton. Additional detail can be
   entered on a separate page(s). References to page number and item number are required.
   Responses should be concise but adequate, using a narrative style.

Named specific references, such as a record name or data element, should be construed as a
generic reference used to describe desired functionality.

Use the Comments column as needed to clarify any responses, special programming costs
including customization or required changes, or if the feature will be available at a later date.
Please provide full particulars. Clearly reference all responses that may be continued in other

Hennepin County RFP                                               Emergency Operations Center (EOC)
10/20/2011                                         RFP Part 2, Section 2 Requirements - Page 5 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                        S   C   N             Comments

exhibits. Other requested information should be inserted directly following each item
and preceded by the phrase "Response:"

1.0    Application
       Architecture/Accessibility
1.1    A software component should be web-based and
       optimized for the intended use. The component
       must use industry standard format with only
       standard plug-ins acceptable (ex: PDF reader,
       Flash, etc). A web based system must work on
       the last two releases of Internet Explorer. A
       software component should not include client
       side software.
1.2    Software components should permit unlimited
       users for anyone the County wishes to grant
       access, including the State of Minnesota, Federal
       Agencies (i.e. investigators) and all municipalities
       and business partners. Document any
       restrictions on the use of the product(s) by the
       County or others, including public access.
1.3    A software component must restrict user(s) to
       the maximum performance limits of the
       particular system. Note if load balancing or
       redundancy is required to handle the minimum
       number of users.
1.4    Each component must support all users (both
       local and remote) with efficient response times.
       Describe typical response times using minimum
       and optimal configurations for query, create and
       update transactions, based on a similar sized
       organization.
1.5    A software component must provide the ability to
       scale and expand capacity and users as needed
       to support demand. Describe the recommended
       means for scaling when more capacity is
       required.
1.6    Software components must be configurable and
       allow user customization of fields, screens and
       data elements. The component must allow the
       user‟s process to drive the configuration of the
       application rather than fixed and not
       accommodating changes to mirror the users‟
       processes. Note ability to customize.
1.8    A software component should prevent incorrect
       data from being introduced. Field lengths and
       character types should be limited appropriately.
1.9    A software component should hide the details of
       its construction from the user.
1.10   All software and hardware components must be
       available and have the capability to be in
       continuous operation 24 hours a day, 7 days a
       week, 365 days of the year. This should include
       a redundancy plan appropriate to a particular
       component. Each component must achieve 99%

Hennepin County RFP                                                       Emergency Operations Center (EOC)
10/20/2011                                              RFP Part 2, Section 2 Requirements - Page 6 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                        S   C   N             Comments

       uptime. This involves multiple paths of
       redundancy between multiple County sites. See
       Table 6. Redundancy
1.11   A software component should automatically
       recover after hardware or network failure,
       inactivity, power disruption or system „crash‟. In
       the event of an error, the system must be able to
       back-out partially completed transactions while
       insuring all database and file referential integrity
       remains completely accurate. Describe how
       transactions that were in process error are
       handled.
1.12   Software components must be remotely
       accessible using secure methods, and with
       authorization for accessing any component
       controlled by the County. The County used
       NetMotion or SSL.vpn with NetMotion being
       preferred for mobile workforces.
1.13   A software component should be able to operate
       efficiently at the same time as daily backup
       procedure is being performed.
1.14   All software components must be capable of
       handling year-end changes and daylight savings
       changes with minimal effort and effect.
1.15   Each component should allow operations staff to
       perform diagnostics.
1.17   Software components should comply with NIEM
       standards or include configurability to meet
       NIEM standards. Explain to what degree
       proposed component complies.
1.18   Software components must include scalable and
       movable windows such that any number of
       windows can be displayed on a monitor.
1.20   Software components must include error
       handling. Note if error trapping used.
1.21   Web pages must not contain any advertisement
       or other promotional materials.
1.22   (SysInt/Coll) Software component must be IP
       network based and provide access, display and
       sharing of other network connected resources to
       all participating partners.
1.23   (SysInt/Coll) Software component must include
       the ability for users to touch or click on
       interactive boards to view and update
       information.
1.24   (SysInt/Coll) Software component must provide
       ability to select data sources of interest and
       create a dashboard style display.
1.25   (SysInt/Coll) Software component should include
       status boards readable on projection systems or
       computer displays.
1.26   (SysInt/Coll) Software component must support
       multiple EOCS or other determined locations as
       well as scalability allowing for an increase of

Hennepin County RFP                                                       Emergency Operations Center (EOC)
10/20/2011                                              RFP Part 2, Section 2 Requirements - Page 7 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                      S   C   N             Comments

       EOCs.
1.27   (VD) The software component must allow
       connections for both permanently fixed and
       mobile camera units, for existing as well as newly
       deployed equipment. The system must also have
       scalability capability to handle cameras being
       added or removed from the system on demand.
1.28   (VD) The software component must be able to
       accommodate expansion of the number of
       camera deployed or monitored. Limitations must
       be described in the proposer‟s response. Also
       describe how proposed solution will facilitate
       anticipated future connectivity needs.
1.29   (VD) The software component must be an IP
       addressable camera system.



2.0    Integration Architecture
2.1    For components interfacing with any County
       application proposer must describe the
       application adapter provided with the software
       package, the availability of pre-built
       application adapters through third party
       vendors, or the interfaces required to construct
       application adapters allowing the proposed
       software package to participate in enterprise
       application integration architectures.

       If a pre-built application adapter is not
       available the following information must be
       supplied:

       1) How the software package will support the
       exchange of messages using IBM‟s MQSeries
       message-oriented middleware product.
       2) Published interfaces recognizing real time
       occurrence of business events, such as
       application event logs, application
       programming interfaces, data base triggers, or
       any other interface technology or protocol.
       3) Published interfaces for invoking appropriate
       application functions triggered by the arrival of
       messages on input message queues.
       4) Support for XML standards including SOAP,
       any industry specific XML standards, and ANSI
       EDI standards.
2.2    Any component must interface or integrate
       with other commonly used EOC components or
       brands, and should use industry standards to
       accomplish this. Note any EOC component or
       brand incompatibilities.
2.3    Components should be easy to deploy and
       require a minimum of new infrastructure and
       components to make the system operational.

Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                             RFP Part 2, Section 2 Requirements - Page 8 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                       S   C   N              Comments

2.4    Hardware components such as workstations,
       servers, cameras and network equipment
       should be commercially available off the shelf
       (COTS) as well as field proven where
       appropriate.
2.5    The proposer must indicate experience with
       and likelihood of integrating data sources and
       applications listed in Tables 4 and 5. At a
       minimum this will include video conferencing,
       remote video surveillance from multiple
       partners and smartboards.
2.6    (CommCon) Connectivity should include a
       reliable means of multi layered, integrated
       communication functionality and information
       exchange with emergency management
       personnel. This may include networks, video,
       GIS, computers, phones, radios, pagers, and
       other audio.
2.7    (CommCon) It will be the County‟s
       responsibility to provide connectivity to the
       Internet. It must be the proposer‟s
       responsibility to provide access to any
       component of the EOC system so staff can use
       the system for communicating, monitoring and
       reporting.
2.8    (SysInt) The component should provide the
       ability to expand capacity as needed to support
       current expected demand and the addition of
       up to 30 more EOC‟s.
2.9    (VD) The component should integrate with the
       County‟s existing IP based video conferencing
       system, remote video surveillance system, and
       any existing workstations or personal
       computers.
2.10   (SysInt) The component should include the
       ability to integrate other varying data streams
       to allow the monitoring and viewing of weather,
       news and other emergency related data sources
       (i.e. CNN, WebEOC).
2.11   (VD) Proposer must provide an overview of how
       their proposal will facilitate integration of video
       from the Minnesota Department of
       Transportation (MnDOT) Regional Traffic
       Management Center (RTMC), and surveillance
       video from city, county and other public
       sources into a single commonly hosted, shared
       solution. The video surveillance component
       must be able to maximize the existing
       hardware and software currently in place,
       including cameras, dvrs, and software used to
       access cameras. In particular, provide details
       on how proposer plans to address connectivity
       from many different camera architectures. The
       County is also interested in exploring remote

Hennepin County RFP                                                      Emergency Operations Center (EOC)
10/20/2011                                               RFP Part 2, Section 2 Requirements - Page 9 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                     S   C   N              Comments

       (on-scene) video equipment and related
       connectivity. Responses should present a clear
       understanding of the methods or alternatives
       for connectivity and transmission of video back
       to the EOC(s) as well as related mobility
       equipment (i.e. mobile unit, suit case storage,
       etc.).

3.0    Database, Data and Records
       Management
3.1    Data collected from components must be
       available on line for up to one year. Historical
       data must be available for a 5 year period.
       Data must be accessible for review or playback
       and downloadable to a DVD or compressed file
       for demonstration or evaluation purposes.
       Response must indicate relative time frames
       and capabilities for data access.
3.2    Certain existing data (see Table 4) must be
       modified, converted or otherwise transformed
       for baseline seeding into the respective
       component, as well as staged for conversion,
       copying or exchanging based in priority of
       information. Indicate experience with data
       conversion. Note ability to accommodate non-
       traditional formats and sources.
3.3    Components must ensure real time data is
       automatically pushed or fed, including
       automatic database refreshes as well as on
       demand refreshes, and provide the means of
       allowing EOC data to be batched, scripted, or
       other uploading to a central data repository.
       Describe refresh process, real time capabilities,
       data transfer and upload options.
3.4    Data to be transferred from a component
       should be encryptable in order to be secured
       from unauthorized access. Note encrypting
       capabilities.
3.5    For components requiring database storage,
       proposers must provide documentation of
       database structure and architecture, field
       mapping, data dictionaries, data relationship
       diagrams, and data counts. Provide a diagram
       of all business objects, entities, and classes
       that capture any connections.
3.6    Software components must have the ability to
       capture secure, computer generated time
       stamp audit trails that include identification of
       who made changes, changes made, and when,
       to include time zone.
3.7    Software components should not solely use
       proprietary formats, and should include
       industry format standards. Data sent or
       received by a component of the EOC system

Hennepin County RFP                                                    Emergency Operations Center (EOC)
10/20/2011                                             RFP Part 2, Section 2 Requirements - Page 10 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                      S   C   N               Comments

       should be transformable to a format that can
       be copied and maintained in a SQL database,
       for reporting and data archiving. Note
       available formats and tools for exporting and
       copying datasets and databases.
3.9    A software component must continue to
       operate during data collection and
       downloading.
3.10   Data collected must be stored in a secure,
       password-protected database. Note if another
       storage method exists and if so, how data is
       protected.
3.11   Each software component must have the
       ability to import and/or export multiple files,
       as defined by the County. Describe the
       methods available.
3.12   (Mob) Software components used in a mobile
       unit should include a storage system that
       adequately holds data collected in the field for
       a period of up to seven days or more, as well as
       the ability to reposit to and access from a
       central data repository.
3.13   (Mob) A mobile unit should include the same
       functionality found in an EOC as well as the
       ability to monitor and transmit emergency
       related activities.

4.0    Project Management
4.1    A comprehensive turnkey EOC system
       spanning the successful integration of the
       components mentioned in Table 1. EOC
       Components should be proposed but the
       County will accept a proposal for an individual
       component. Note whether a turnkey or
       standalone proposal is submitted.
4.2    For a proposed turnkey system, the primary
       solution proposer must be responsible for all
       design specifications of the proposed solution,
       to include other subcontracted vendor
       components, roles and responsibilities. The
       proposed solution should encompass: Vendor
       and subcontracted software, vendor and
       subcontracted hardware, all network
       architecture, integration of all software
       components (see Table 5), redundancy,
       business continuity, other services, training
       and resources.
4.3    A proposer must provide a detailed project
       plan that divides tasks between the proposer
       and Hennepin County. See Part 4 Section 1 for
       additional expectations.

5.0    Security and Authentication

Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                               RFP Part 2, Section 2 Requirements - Page 11 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                      S   C   N              Comments

5.1    A software component must provide security to
       restrict access. Functions and privileges based
       on configurable roles such as “View”, “Add”,
       “Delete” and “Update”
5.2    Authorization and administration of
       components and data access must be
       controlled by the County. Describe how
       component security is implemented and
       maintained.
5.3    Any software component must validate that
       the individual is authorized to perform each
       transaction being requested. Describe how
       security is maintained and how software, data
       and system will be protected.
5.4    Any software component must only display
       system information after authorization and
       authentication of the user is completed.
5.5    Any software component must provide a
       unique user account for each individual.
       Describe the directory structure(s) that may be
       utilized by the system.
5.6    Any software component must terminate
       inactive sessions after a specified time, which
       can be set by the County.
5.7    Any software component‟s security controls
       must include the creation of a log consisting
       of, at a minimum, date and time of access, who
       accessed and what was accessed.
5.8    Any software component must expire
       passwords. Describe the password
       specifications and configuration requirements.
5.9    Proposer must describe functionality that
       protects software component from infection or
       undesirable programs.

6.0    Communication Connectivity/
       Network
6.1    Wireless communication links must
       automatically establish and maintain reliable
       connection between nodes and the County
       network. Any proposed links or connections
       utilizing satellite or wireless must be capable of
       providing a robust connection in heavy rain
       and snow conditions up to and including 3
       inches per hour of rainfall. For a proposed
       satellite connection, provide six (6) references
       of comparable size to the County where
       proposed solution has been tested or used
       under these conditions. Communication
       between a system‟s nodes must occur via
       secure communications protocols.




Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                              RFP Part 2, Section 2 Requirements - Page 12 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                      S   C   N               Comments

6.2    All software components must support both
       local and remote users with efficient response
       times. Turnkey or standalone proposals must
       include response times for each component,
       based on minimal and optimal configurations,
       using the typical volumes of comparable
       organizations, and provide client side
       requirements for connectivity/network
       bandwidth, while considering both uploads and
       downloads. Note any other equipment
       requirements to support the proposed solution.
6.3    All components must efficiently and easily
       connect Hennepin County (including mobile
       units), City of Minneapolis, the City of
       Bloomington, MnDOT RTMC, and future
       municipalities to be determined, with a secure
       wired and wireless communications backbone.
       The system must connect traditional fixed EOC
       locations and numerous additional fixed and
       prepackaged mobile devices.
6.4    The various components should have the
       ability to communicate and transfer
       information by satellite, wireless mesh,
       microwave, cellular connectivity or other. Note
       requirements for a component‟s connectivity,
       as well as the ability to communicate with a
       private incident area network.

6.5    This component must include enhanced WiFi
       and cell signal strength for consistent
       communication within the Medina EOC
       complex, through obtaining a repeater
       component or other.
6.6    A mesh network solution must be scalable and
       provide bridging interconnects to multiple
       mesh networks over IP or a WAN link, support
       multiple radio channels and spectrums to
       increase overall capacity and coverage, and
       must include SNMP to allow network
       administrators to integration of components
6.7    Proposer is encouraged to suggest additional
       communications features or components that
       may enhance emergency capabilities not
       included in these requirements that would
       enhance the County‟s emergency operation
       center effectiveness.

7.0    Platform and Storage
7.1    The proposer must provide a list of minimum
       and optimal hardware configurations required
       to run a proposed component. Provide
       information regarding the number of
       processors, processor speed, memory, disk
       space, database, additional hardware needed,
       and other specifics including server and client

Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                               RFP Part 2, Section 2 Requirements - Page 13 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                     S   C   N             Comments

       configurations. Include suggested monitor
       sizes, and recommendations on touch-enabled
       screens.
7.2    A proposer must provide a list of hardware ,                    ?
       software and any other required elements,
       needed to install a proposed component to a an
       additional site, mobile, or portable unit.
7.3    A software component should be capable of
       operating with the database on a separate
       database server, and independent of the
       application server. Describe the component‟s
       storage architecture.
7.4    A software component should be capable of
       running on a virtual server with other
       applications. The County standard is VMWare.
       Describe the specific requirements and
       recommendations to meet this capability.
7.5    Any software component must be compatible
       with the County‟s current OS, Windows XP.



8.0    Functional Requirements
8.1    Software components should include the
       means for determining if the component is not
       operational. If a failure condition occurs, the
       system should create a failure notification to
       an operator that is unique to the regular
       operation mode. Failure conditions may
       include: a) Loss of network connection b)
       Malfunction of software c) Power Failure 4)
       Camera Failure, or other.
8.2    Any component using outdoor equipment must
       have self contained modules housed in
       weatherproof, NEMA 4X rated enclosures
       suitable for outdoor use. No internal manual
       settings or adjustments should be needed to
       install or maintain the systems.
8.3    Any component using outdoor equipment
       should be capable of operating at temperatures
       ranging from -40 degrees C to 60 degrees C,
       and humidity up to 95% relative, and
       withstand winds up to 65 mph.
8.4    A software component‟s information must be
       displayed only after authorization and
       authentication of the user is completed. User
       privileges must be password protected.
8.5    (AM) The software component should include
       RFID capability that allows for identification of
       physical equipment thru the use of fixed RFID
       tags, or individuals thru the use of badges or
       wristband RFID tags, and management of other
       indirect and mobile assets.


Hennepin County RFP                                                    Emergency Operations Center (EOC)
10/20/2011                                            RFP Part 2, Section 2 Requirements - Page 14 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                        S   C   N               Comments

8.6    (AM) The software component should include
       software that includes asset management
       points with the ability to identify – graphically
       using GIS – where assets are located and to
       dispatch and reassign if needed.
8.7    (AM) The software component should include
       the ability for tracking financial costs.
8.8    (AM) The component should tag, read, record,
       send, and track asset information using bar-
       coding and/or Radio Frequency Identification
       (RFID) technology. The RFID capability must
       allow for identification of physical equipment,
       mobile assets and indirect materials, thru the
       use of fixed RFID tags, or individuals thru the
       use of badges or wristband RFID tags.
8.9    (SysInt/Vis) The system must have the ability
       to allow critical parties located geographically
       separate to interact with EOC related
       information, using secure workspaces. This
       should primarily be through the sharing of
       streaming voice, video conferencing, and data.
8.10   (SysInt/Vis) The system must have the ability
       to share and monitor information from multiple
       systems– updates, status, affected locations,
       responses, etc for any incident – via large
       display panels. The panels should have the
       ability to display up to six (6) different
       information streams. This must include
       independent switching and routing. This may
       be six individual panels or one panel with six
       „tiles‟. Flat panel display technologies may be
       considered. Indicate experience with
       integrating equipment such as digital cameras,
       interactive whiteboards, plasma screen
       displays, and data sources.
8.11   (SysInt/Vis) The system must have the ability
       to share multiple files and formats that
       correspond to those typically found with audio,
       video and data files. Files may include GIS
       maps, pictures, text files, internet links, or
       video files.
8.12   (SysInt/Vis) The system must include ease of
       user programmability with minimal custom
       programming.
8.13   (SysInt/Vis) The system must include the
       ability to monitor multiple systems
8.14   (SysInt/Vis) The system must include the
       ability to operate as an independent standalone
       system, in order to be used by the County
       during a non EOC event.
8.15   (SysInt/Vis) The system must incorporate the
       use of electronic whiteboarding.
8.16   (Mob) A mobile unit and its components must
       withstand winds up to 60 mph.

Hennepin County RFP                                                       Emergency Operations Center (EOC)
10/20/2011                                                 RFP Part 2, Section 2 Requirements - Page 15 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                      S   C   N             Comments

8.17   (Mob) All equipment to be installed in a mobile
       unit should allow for operation up to 12 hours
       on self contained power, and normally operate
       on 12V vehicle electric power with an adapter.
       The mobile unit must be installable in such a
       way to ensure vehicle battery power is
       maintained at all times. All systems must
       have built in surge protection from low and
       high voltage exposures. All mobile computer
       equipment must automatically perform a
       power on-self-test and diagnostics upon the
       application of power.
8.18   (Mob) Any antenna system included in a mobile
       unit must be rated for mobility and include
       auto positioning capability for locating satellite
       signals.
8.19   (Mob) Portable IP video camera „pods‟ must be
       easily and readily installable to a mast as well
       as streetlight and power poles. Cameras must
       include functionality to adjust image for day or
       night monitoring. Note required power source
       for cameras.
8.20   (Mob) The County must have the availability to
       monitor an incident beyond surveillance
       coverage provided by permanent camera
       systems. A mobile trailer is desired. The
       mobile units should include prepackaged,
       relocatable, rapidly deployable unit . This unit
       should be capable of receiving, transmitting,
       accessing and incorporating multiple video
       surveillance platforms through network video
       sources, as well as using other components of
       the County‟s primary EOC. This mobile video
       surveillance unit may range from a classic
       vehicle, trailer or modified tow-able generator,
       should be cost effective and incorporate
       creative and innovative features.
8.21   The County must have the ability to transport
       the functionality and communication ability of
       a fixed location EOC in a self contained „EOC
       in a suitcase‟ unit, deployable by one person.
8.22   (Mob) The mobile unit must provide camera
       surveillance at multiple heights with a
       minimum of 30 feet. If tripod or aerial camera
       mast is proposed as part of the system, note
       the heights provided. A mast must be easily
       deployable by one person. Note if mast is
       permanently mounted to a mobile unit or
       vehicle.
8.23   (Mob) The mobile unit should include the
       ability to deliver high quality surveillance
       video, systems and data within a 600 ft radius
       of the location and to multiple users. Describe
       image quality.


Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                             RFP Part 2, Section 2 Requirements - Page 16 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                     S   C   N               Comments

8.24   (Mob) Proposer must provide a detailed
       description of any proposed video data storage
       solutions within the mobile unit.

8.25   (VD) The software component must deliver a
       visually acceptable resolution and format to
       fixed, mobile or virtual EOC locations. The
       delivered image should be scalable to different
       resolutions, rather than limited by a predefined
       setting. Note the available resolutions.
8.26   (VD) The software component must provide a
       link to allow live, real time monitoring of
       emergency activity areas using single or
       multiple, existing or mobile surveillance
       cameras, including audio and/or data and
       recording of events. Indicate the amount of
       delay time from live source, if any.
8.27   (VD) The software component must provide a
       playback feature allowing access to a central
       repository, server or other data storage system,
       for retention of portions of an entire event or a
       fixed time period (i.e. 30 days). The system
       must provide for the ability to replay video
       information based on the selection of a specific
       activity or time frame. The system should
       include the ability to capture and preserve pan
       and zoom actions completed during real-time
       surveillance and incidences, and should have
       fast forward and rewind functionality to
       enhance playback analysis.
8.28   (VD) The software component must provide the
       ability to display multiple camera images on a
       screen or video display, expand or exchange
       the selection of images, resize images, etc.
       Fully describe the ability to query or select
       cameras of monitoring interest, and explain the
       number of cameras that may be viewed with
       corresponding image size and resolution.
       Camera images must also identify camera
       location or other means of identification.
8.29   (VD) The software component should have
       capability for cameras to be securely
       monitored, recorded, and administered from
       any workstation or portable device within the
       network. This should include the ability to
       power up, power down, and restart a remote or
       local system.
8.30   (VD) The software component must incorporate
       and integrate multiple proprietary live video
       formats used by existing camera surveillance
       systems. This unified video management
       system must integrate the County, MnDOT
       RTMC, the cities of Minneapolis and
       Bloomington as well as formats found within
       institutional settings such as hospitals,
       schools, airports and correctional facilities
Hennepin County RFP                                                    Emergency Operations Center (EOC)
10/20/2011                                              RFP Part 2, Section 2 Requirements - Page 17 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                    S   C   N             Comments

       under surveillance within Hennepin County.
        The result should be an integrated, seamless,
       comprehensive surveillance solution that uses
       industry standards and includes the ability for
       connectivity to a system such as WebEOC.
       Indicate experience with integrating multiple
       proprietary video formats.
8.31   (VD) The software component must allow
       availability of video conferencing and remote
       video surveillance, through the use of a
       dashboard style disply allowing user to select
       and manage images, to all EOC partners.

9.0    System Installation, Support &
       Maintenance, Warranty, Retirement
9.1    Proposer must provide system implementation,
       with a detailed implementation plan that
       divides tasks between the proposer and the
       County, and includes installation assistance.
       Description, estimated time should be
       included. This should include a prioritization
       plan that outlines information or software
       applications to be loaded first.
9.2    Proposer must provide operations and
       maintenance manuals for all equipment and
       software procured. The selected proposer must
       provide twelve (12) sets of operator manuals
       and one digital copy for back-up and future
       needs. These manuals and a back-up copy will
       become the property of Hennepin County. The
       County may, at its option agree to an electronic
       copy of operator manuals, provided they can be
       printed and distributed as needed.
9.3    Proposer providing software components must
       submit a configuration management plan
       comprehensive to the proposed component.
9.4    Proposer responses must document whether
       the proposed component is a purchase or
       rental solution. Who owns what? Will the
       application and data run on shared or
       dedicated servers? Who owns all the
       components of the proposed solution
       (hardware, software, data)? What happens if
       the contract is cancelled or not renewed? What
       exit strategies exist? Under what
       circumstances do you cancel? Any additional
       costs associated with cancellation? What
       options exist to bring the application in house?
9.5    Off site host must notify the County at least 48
       hours in advance of any scheduled network
       downtime or maintenance and/or service.
9.6    Ongoing software component maintenance
       must be provided by proposer. The
       expectation is upgrades as well as fixes will be

Hennepin County RFP                                                   Emergency Operations Center (EOC)
10/20/2011                                           RFP Part 2, Section 2 Requirements - Page 18 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                   S   C   N             Comments

       included in maintenance. Describe the
       standard processes, specifically what is
       provided and if applicable any costs involved.
9.7    Ongoing hardware component maintenance
       must be provided. Hardware maintenance
       must consist of module-level replacement and
       must not require circuit board level or
       component level adjustment, replacement or
       repair.
9.8    Proposer must agree to notify the County when
       software updates /upgrades /patches /fixes
       have been certified for use with their
       application a minimum of 48 hrs prior to the
       application of changes.
9.9    An Off site host must provide a Disaster
       Recovery and Backup plan for any off-site
       hosting if proposed as a part of the EOC
       system. Proposer to indicate background and
       experience with hosting the proposed
       component, and indicate security level of host
       (eg Tier 4 or other).
9.10   Proposer must describe component backup
       and restore features. This should include any
       limitations. The proposer should recommend a
       backup and recovery procedure that includes
       estimates of how long it will take to backup
       and restore all system data based on the
       characteristics of their software, the County‟s
       environment and estimated transaction
       volumes. Describe if backups are stored, on or
       off site. Describe proposed system for recovery
       and business continuity.
9.11   Proposer should provide a minimum of one
       new release of their software every 12 to 18
       months. Provide a history of your last 5
       software releases that includes the time frame
       for each release and a summary of the new
       features included.
9.12   Proposer must offer any software upgrades
       (made commercially available to the public) to
       currently installed software, if the upgrade is
       made public within 18 months of the contract
       start date.
9.13   Proposer must offer any hardware upgrades
       (made commercially available to the public) if
       upgrades are made public within 18 months of
       the contract start date.
9.14   Proposer must provide emergency service for
       components and subsystems of the RV system
       within 24 hours of a service call. Service and
       support must be available 7 days a week, 24
       hrs a day, 365 days/year. Service and support
       must be provided at regular service rates or
       warranty where applicable.
9.15   Proposer must describe how the County would

Hennepin County RFP                                                  Emergency Operations Center (EOC)
10/20/2011                                          RFP Part 2, Section 2 Requirements - Page 19 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                       S   C   N               Comments

       report software problems, methods used to
       respond and how quickly response will occur.
9.16   Regardless of turnkey or standalone
       component proposal, proposer(s) must provide
       ongoing, permanent, offsite technical support
       for the hardware and software hosted or used
       on their components. Proposer must provide
       resolution of problems that cause the system to
       be completely unavailable to the user within 4
       business hours of notification.

       Describe hours of availability for the following
       support tiers, using CST times:

       Monday – Friday support
       After hours emergency support number
       available for management level staff
       Holiday support hours

       Responses to include answers to these
       questions: What procedures are required to
       obtain support? Do support agreements
       include full system support for hardware and
       software? Describe number of support staff
       available and their familiarity with the system.
       Describe expected response time, different
       support levels available, and other aspects of
       this service including any costs involved.
9.17   A component of the EOC system must provide
       on-line help that can be accessed easily during
       system usage. Describe these features and
       how they are utilized.
9.18   Proposer must describe if proposed software
       application(s) can be customized, modified or
       developed i.e. templates, reports. If so, is this
       a service that is offered? Responses must
       include a detailed fee listing for services.
       Include the time frame for development
       following finalized requirements.
9.19   Proposer should provide resolution of those
       problems that cause the system to be
       completely unavailable to the user, within four
       business hours of notification. Provide an
       explanation of the support service levels
       available and discuss the associated costs for
       each level.
9.20   A proposer must provide a twenty-four (24)
       hour response to system failures during
       emergencies. This means the contractor must
       resolve the system failure within 24 hours of
       notification to the County.
9.21   In the event of an unscheduled outage, a
       proposer must immediately notify the County
       of the outage and expected outage time.
       Should the outage continue for a period of four

Hennepin County RFP                                                      Emergency Operations Center (EOC)
10/20/2011                                                RFP Part 2, Section 2 Requirements - Page 20 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                    S   C   N             Comments

       hours or more, the County must be provided
       an update and new estimate of the outage
       period at four hour intervals.
9.22   Proposer must provide notice of all known
       system problems when they are identified or
       discovered. The notices should provide a
       description of the problem, the circumstances
       that cause it to occur and the impact that it
       will have on the County‟s business.
9.23   Proposer must provide software updates that
       correct known problems. Describe frequency
       and process of for upgrades, patches and fixes.
       Provide release history and planned releases
       for new software patches, as well as hardware.
        This will be used in part as an indicator of a
       product‟s longevity.
9.24   A proposer must provide at least a one (1) year
       full replacement warranty for all hardware,
       software and other equipment (after successful
       completion of the system acceptance test). A
       proposer must replace any failed component of
       the system at no additional cost to the County.
       All components must be available and
       delivered to the County by the next business
       day.
9.25   A proposer must provide an optional proposal
       for extended warranty periods beyond the first
       year, for one (1) and two (2) years. The County,
       at it‟s discretion, will make the decision as to
       the purchase of extended warranties at a later
       date.
9.26   Proposer must offer a new product (software,
       hardware or other) as replacement for any
       discontinued product used in a component of
       the EOC system, at same contracted cost of
       discontinue product, and with no additional
       fees or maintenance cost, until the existing
       contract expires.
9.27   If proposal includes services, proposer must
       submit a retirement plan to include a scenario
       of unsubscribing to any service, or vendor
       terminating the arrangement.

10.0   Quality/Testing
10.1   To determine acceptability and performance of
       the system and related hardware/software, the
       County must conduct acceptance test(s) on
       delivered components as they are implemented.
       The testing and acceptance of these
       deliverables must be completed in the proper
       sequence as defined in the project schedule
       when dependencies exist. At the County‟s sole
       option, such acceptance test(s) may be
       conducted together with or independent of any

Hennepin County RFP                                                   Emergency Operations Center (EOC)
10/20/2011                                           RFP Part 2, Section 2 Requirements - Page 21 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                    S   C   N              Comments

       other acceptance test(s) conducted by the
       County. Proposer must provide test cases for
       evaluating any component of the implemented
       system.
10.2   Proposer must allow time within the
       implementation plan to allow for testing and
       evaluating data collected, system functionality,
       vendor supplied reporting capabilities,
       equipment operations, and mapping.
10.3   The Deputy County Administrator must decide
       any dispute or issue(s) arising under the bid
       specification and subsequent contract as to the
       quality and acceptability of the contract work,
       and as to the manner and performance and
       rate of progress. The Deputy County
       Administrator must also decide questions
       which may arise in the interpretation of the
       plans and specifications and the satisfactory
       and acceptable fulfilling of the terms of the
       subsequent contract.

11.0   Training and Documentation
11.1   Proposer is responsible for all aspects of staff
       training for all equipment and software
       procured. Technical training should focus on
       three main areas: system administration,
       system operations and functionality (including
       software operations, features, and
       troubleshooting and demonstrations), and
       database/storage administration. The proposer
       must provide training at the convenience of the
       County. All training must be conducted at a
       location determined by the County. The
       proposer must provide instructors experienced
       with the system, as it relates to emergency
       operations. Proposer must provide the list of
       user documentation to be supplied for a
       system component. At a minimum this should
       include help files, wizards, etc. Proposer must
       supply training materials --- operations and
       maintenance manuals – for each student and
       for all equipment and software included as part
       of the system. Students must be able to retain
       the provided training materials after
       completion of the training. The selected vendor
       must provide 25 sets of operator manuals and
       one digital copy for back-up and future needs.
       These manuals and a back-up copy will
       become the property of Hennepin County. Any
       reference or training materials must be
       provided in an electronic format free of cost to
       the County, to include user guides, admin
       guides, best practices, data diagrams, data
       definitions, process flow, procedure diagrams,
       and others. The County may, at its option,

Hennepin County RFP                                                   Emergency Operations Center (EOC)
10/20/2011                                            RFP Part 2, Section 2 Requirements - Page 22 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.      Functionality                                    S   C   N              Comments

       agree to an electronic copy of operator
       manuals, provided they can be printed and
       distributed as needed. Any alternative training
       materials should be made available hard copy.
       Training sessions should be captured
       electronically and provided free of cost to the
       County.
11.2   Proposer‟s response must provide a training
       plan indicating days/hours of training,
       proposed class size and class content. This
       should include a breakdown on post-
       implementation for other organizations as they
       may be brought on line by Hennepin County.
       Proposer must provide one (1) sample training
       manual with proposal. Manuals must be
       written in language that can easily be
       understood by users who do not possess
       computer skills or knowledge.
11.3   Proposer must include all cost elements of
       training (tuition, travel, lodging, manuals,
       supplies and other) in the cost summary.
       Identify the costs for Information Technology
       technical training separately from end-user
       training. In addition to the initial training,
       proposer must include a quote for up to thirty-
       two (32) hours of additional training during the
       first twelve (12) months following system
       acceptance.
11.4   Software component should be intuitive, as
       indicated by EOC responder training of less
       than 30 minutes.
11.5   Proposer should provide an active, mature web
       site or other method that provides a forum for
       the County to obtain answers to frequently
       asked questions and to share experiences
       regarding the use of the software with other
       customers. Provide a description of your web
       site, user groups and any regularly scheduled
       forums for sharing ideas and solutions to
       problems. Explain if a demonstration of any
       web site described is available.




Hennepin County RFP                                                   Emergency Operations Center (EOC)
10/20/2011                                            RFP Part 2, Section 2 Requirements - Page 23 of 29
                                     REQUEST FOR PROPOSALS
                      Virtual Emergency Operations Center (EOC) Enhancements
                                    Part 2 – System Requirements
Item
No.               Functionality                                S   C   N              Comments

Table 1. EOC Components

      Designator                                            Component Name
IBIS                                Internet Based Information System (WebEOC)
Mob                                 Mobility
VD                                  Remote Video Surveillance & Video Conferencing
AM                                  Asset Management
CommCon                             Communication Connectivity including Network
SysInt/Vis                          System integration/unified operating platform resulting in a
                                    comprehensive collaboration Tool including visual


Table 2. EOC Component Availability by User - Points of Presence -- See Exhibit D


Table 3. Communication Connectivity by User

                         Participants                   Communication Connectivity

                                                        Existing multi site /Bldg
                                                         WAN/LAN
                                                        Internet connectivity
                  Hennepin County Minneapolis           *100 MBPS QMOE
                                                        Microwave
                                                    
Primary Hosts




                                                         WiFi Hotspots
                                                        Satellite TV

                                                            Internet connectivity
                      Henn County Medina
                                                             *200 MBPS QMOE
                    Henn County Mobile Unit                     Wi fi hotspot
Coordinating




                      City of Minneapolis                      Existing WAN
Primary

EOCs




                      City of Bloomington                      Existing WAN
Coorindating
Secondary




                         MnDOT RTMC                            Existing WAN
EOC
of Henn Co EOC
located outside
Critical Users




                   Remote users with varying                       VPN to
                           locations                           Existing WAN



* QMOE bandwidth can be increased at request of County




 Hennepin County RFP                                                       Emergency Operations Center (EOC)
 10/20/2011                                                RFP Part 2, Section 2 Requirements - Page 24 of 29
                                            REQUEST FOR PROPOSALS
                             Virtual Emergency Operations Center (EOC) Enhancements
                                           Part 2 – System Requirements
Item
No.                      Functionality                                    S      C   N             Comments

Table 4. EOC Data Sources (format in parenthesis)

                                                                       Video             Asset          Other Data
                        Participants        IBIS (Web EOC)
                                                                    Surveillance         Mgmt      Sources/Applications
                                                                                                       Google Maps
                                         ArcView mapping files
Primary




                         Hennepin                                      Digital                       Andover Building
                                          (native format ESRI
Hosts




                          County                                       Sentry                            Controls
                                              shape files)
                                                                                                 Pictometry International
                                         ArcView mapping files                                          PeopleSoft
                          City of                                   Proprietary      Currently        News/Weather
Primary Coordinating




                                           (ESRI shape files)
                        Minneapolis                                   format          no data             FEMA
                                          Flight information?
                                                                                      sources          State of MN
                                                                                                         MnDOT
                           City of           SmallWorld
                                                                        Pelco
                        Bloomington           (VMDS )                                               Other data sources
EOCs




                                                                                                     recommended by
                                                                                                         proposer
Coorindating
Secondary




                          MnDOT          ArcView mapping files      Proprietary
                          RTMC             (ESRI shape files)         format
EOC




Table 5. Software/Systems

                       Component                      Software Name                           To Integrate with:
IBIS                                       WebEOC;                                   System Integration/ Collaboration
                                           Mapper;                                   Tool; Other EOCs using WebEOC;
                                           Resource Manager, Team Manager            MnDOT cameras (using Mapper)
                                           Digital Sandbox (Risk Management)
GIS                                        ArcView /ESRi                             Integrated to WebEOC
Video Surveillance/CCTV                    Pelco Digital Sentry                      RV management system

Video Conferencing                         Tanberg, Cisco Systems                    Systen Integration/
                                                                                     Collaboration Tool
System Integration /                       TBD – currently none                      WebEOC
Collaboration                                                                        RV management system
RV Unified Management                       (TBD – currently none                    County, Minneapolis, &
System                                                                               Bloomington remote video systems

Table 6. Redundancy

   EOC Component                                   Existing                                  Conceptual
Communication                              WAN                           Backup antenna that can be erected after an
Connectivity                                                             event or if excessive forces disable a permanent
                                                                         antenna.
Miscellaneous                              None                          County is exploring Microwave for backup
News/Weather Feeds                                                       network.
WebEOC                                     Software to be hosted
                                           offsite with redundancy
                                           covered by host provider.
Video Surveillance/CCTV                    None
Video Conferencing                         Redundancy handled by

Hennepin County RFP                                                                      Emergency Operations Center (EOC)
10/20/2011                                                             RFP Part 2, Section 2 Requirements - Page 25 of 29
                               REQUEST FOR PROPOSALS
                Virtual Emergency Operations Center (EOC) Enhancements
                              Part 2 – System Requirements
Item
No.       Functionality                                   S     C   N             Comments

                          Henn County
Collaboration             None                           Secondary collaboration screen or panel is
                                                         desired to cover breakdown or malfunction. The
                                                         controller or board should be easily replaceable.

Table 7. Existing Hardware

       EOC Component                                            Hardware
                               Hennepin County                Minneapolis      Bloomington       MnDOT
IBIS (WebEOC)              Off site hosted servers
Video Surveillance/CCTV     2600 Cameras on some               Several            Several       ~20,000
                             County roadways.              hundred wired      hundred wired    cameras on
                            Sheriff‟s office – 150          and wireless           video       roadways
                             analog cameras spread               video          surveillance
                             throughout 6 buildings          surveillance         cameras
                            Corrections ~125                  cameras            citywide
                             cameras                         in skyways,      including MOA
                            Camera makes include          downtown, and
                             Sony, Panasonic with           other areas of
                             most Pan and Zoom,                   city
                             and most analog
                            45 DVR archiving
                             „servers‟ with digital
                             format
Video Conferencing         Internally hosted IP                Node exists      Node exists    Node exists
                           system; Bridging
                           capabilities to other sites
System Integration/        ~6 smartboards                     2 smartboards        None
Collaboration              Satellite TV
Mobile Unit                Outdoor Cisco WLAN
                           purchased
Asset Management           None
Communications             Multiple Servers                  WAN/LAN            WAN/LAN
Connectivity /             (refer to network diagram)        Public Wifi        Public Wifi
Infrastructure             *also see Table 3.                  Hotspot            Hotspot
                                                           Sprint AirCards       PageGate
Physical Location          Medina
Workstations




Hennepin County RFP                                                     Emergency Operations Center (EOC)
10/20/2011                                          RFP Part 2, Section 2 Requirements - Page 26 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.     Functionality                       S   C   N               Comments




Hennepin County RFP                                     Emergency Operations Center (EOC)
10/20/2011                               RFP Part 2, Section 2 Requirements - Page 27 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.     Functionality                       S   C   N               Comments




Hennepin County RFP                                     Emergency Operations Center (EOC)
10/20/2011                               RFP Part 2, Section 2 Requirements - Page 28 of 29
                            REQUEST FOR PROPOSALS
             Virtual Emergency Operations Center (EOC) Enhancements
                           Part 2 – System Requirements
Item
No.     Functionality                        S   C   N               Comments




                        End of Part 2 Section 2 of this RFP




Hennepin County RFP                                      Emergency Operations Center (EOC)
10/20/2011                                RFP Part 2, Section 2 Requirements - Page 29 of 29

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:11
posted:10/20/2011
language:English
pages:29