HomeMy WebLinkAboutRESPONSE - RFP - 7396 PFA FIRE SERVICE RESPONSE PERFORMANCE ANALYSIS SOFTWARE & RUN CARD BUILDER SOFTWAREPoudre Fire Authority
Request for Proposal 7396
Fire Service Response Performance Analysis Software
for a Standard of Cover Study
Due Date: June 29, 2012
Due Time: 3:00pm MST
Signed By
____________________________________________
Milan Mueller
President
Contact:
Chris Baldwin
Regional Sales Executive
(858)450-2590 Headquarters
(858)450-0239 Fax
Chris@theomegagroup.com
The Omega Group, Inc.
5160 Carroll Canyon Rd., Suite 100
San Diego, CA 92121
NON-DISCLOSURE
This document has been prepared by the sales division of The Omega Group and is a confidential document that
contains ideas, concepts, methods and other proprietary information. Readers are to treat the information contained,
within clearly marked sections, as confidential and may not copy or reproduce any of these materials for distribution
outside of their organization without the written permission of The Omega Group. This document will remain valid for
120 days from the RFP due date.
2 | Page
June 28, 2012
Mr. Ed Bonnette
Buyer
City of Fort Collins
Purchasing Division
215 North Mason St. 2nd Floor
Fort Collins, CO 80524
Re: RFP 7396 Fire Service Response Performance Analysis Software
Dear Ed,
I am pleased to submit to you our bid for RFP 7396. The Omega Group is accustomed to
deploying solutions over the last 10 years that meet many of the requirements detailed within
the RFP. Our experience in working with the fire industry over these years has given us a unique
edge at understanding how to integrate GIS into fire operations that can have an immediate and
direct impact on Standard of Cover preparation.
Enclosed you will find our pricing for the delivery of an Omega-hosted FireView Dashboard and
an on-premise delivery of FireView Desktop application.
Please consider the following addition items as you review our pricing:
• Software and Professional Services are included. Esri Software, Hardware and a
networkable street centerline are required, but not included in cost.
• Our package costs are fixed fee for software and services.
We appreciate your consideration of our solutions. If you have any questions relative to our
pricing or technical proposals, please contact us at (858) 450-2590.
Thank you,
Chris Baldwin
Sales Executive
3 | Page
Table of Contents
Methods and Approach 04
PFA Technical Information 04
Technical Approach 04
Task Order 05
Deliverables 10
Qualifications and Experience 12
Corporate Background 12
Industry Experience 12
Standard of Cover 12
References 13
List of Project Personnel 14
Resumes 15
Organization Chart/Proposed Project Team 18
Availability 20
Estimated Hours by Task 20
Schedule of Rates and Cost by Task 21
Billing Rates 22
Subscription and Maintenance Fees 22
Third Party Software and Hardware Requirements/Price Summary 23
Payment Schedule 23
General System Requirements 24
Data Specifications 24
GIS Data Specifications 26
Application Specifications 27
Hardware Specifications 28
Customer Support Program 30
4 | Page
Methods and Approach
PFA Technical Information
PFA is primarily a Microsoft Windows shop with a splash of VMWare. AS such, we are assuming
that most vendors responding with proposals for this RFP will be using Microsoft Windows
Server with SQL server as their database.
As part of you proposal under Methods and Approach, vendors are to include your response to
the following:
_X_ YES, WE will be using Microsoft Windows Server with SQL server as our database
___ NO, We will NOT be using Microsoft Windows Server with SQL server as our database.
Technical Approach
The FireView Dashboard is an Omega-hosted, server-based application that presents a thin-
client interface for user interaction. FireView Desktop is a client-based application that presents
a graphic user interface for user interaction. Analysis within both applications is performed on
data generated from other parts of the enterprise, for example the Records Management
System (RMS) and Geographic Information Systems (GIS). The application is built around Esri’s
ArcGIS Server (FireView Dashboard) and Esri’s ArcGIS Desktop (FireView Desktop) to support the
geographic and analysis functions. FireView Dashboard and Desktop interface with the RMS and
GIS data using data extraction, preparation and automation processes via the Omega Import
Wizard.
Using the Omega Import Wizard, Omega creates data models tailored to the client’s data
sources that can be further modified to meet the client’s specific business requirements. A (SQL
Server & ArcGIS Server) spatial data warehouse will house information from the data sources
and used to provide data to the application. Views of these data will become geographic data
layers that can be queried and mapped. In the FireView Dashboard these data may then be used
in the geographic widgets and analysis tools. In the FireView Desktop these data are used in the
native Esri formats including a geodatabase and a feature class in an ArcSDE layer.
Additional Considerations
FireView Dashboard and FireView Desktop analyze data input through other systems and thus
has an indirect dependency on those systems. Omega does not warrant the quality of data
entered by the users into other systems that FireView Dashboard and FireView Desktop
consumes, therefore, there is an inherent risk in the quality, accuracy, and availability of data
outputted by both applications.
5 | Page
Task Order
The Omega Group will deliver the FireView portfolio of solutions over a six month period of
time, scheduled to commence in August, 2012 and end in January, 2013. Milestones events
relative to this deployment include:
1. Middleware Installation at Poudre Fire Authority
2. FireView Desktop deployment
3. FireView Dashboard deployment
1. Project Planning/Management Timeline: August 1st, 2012
1.1. Software and database requirements
1.1.1. Review deliverables for client
1.1.1.1. Omega client software: Omega Import Wizard, Omega Extractor
1.1.1.2. Esri software: ArcGIS Desktop 10
1.1.2. Review deliverables by Client
1.1.2.1. Esri’s ArcGIS 10
1.2. System Architecture
1.2.1. Identify hardware components and configuration.
1.2.1.1. Import server
1.3. GIS map layers and design preferences
1.3.1. Identify base map GIS data layers for geographic querying
1.3.2. Identify reference data for geocoding
1.4. CAD/RMS/other source data
1.4.1. Review import process and automation
1.4.2. Identify fields to be imported
1.4.3. Review database schema and tabular relationships
1.5. Dashboard Design
1.5.1. Review design options for baseline deployment
1.6. Determine remote connection method
1.7. Review roles and responsibilities
2. Omega Import Wizard Configuration Timeline: September 1st, 2012
2.1. Client will install ArcGIS on import workstation
2.2. Client will install Import Wizard on import server or workstation
2.2.1. Omega will extract sample datasets for application development
2.3. Omega will update import profile for CAD or RMS data extraction
2.3.1. Omega will create SQL Statement
2.3.2. Omega will configure data processing steps
2.3.3. Omega will work with the client to group incident types into one of the available
standard Omega fire type categories (where applicable)
2.3.4. Omega will configure geocoding process, review the sample data’s
geocoding rates and provide recommendations
2.3.5. Omega will configure output data sets and automation
6 | Page
FireView Desktop Deployment
3. FireView Application Configuration Timeline: September 15th, 2012
3.1. Omega will add GIS layers to map document and design base map cartography,
public safety symbology, labeling and layout template
3.2. Omega will create saved queries database
3.2.1. Client will provide pick list values in tabular format
3.2.2. Define saved queries (not to exceed 5 saved query categories per import
dataset)
3.3. Create Cost Matrix for response analysis tools
3.4. Configure Crystal Report templates
3.4.1. Incident Detail and Summary (Incident)
3.4.2. Apparatus Detail (Apparatus)
3.4.3. Incident Repeat Calls (Incident)
3.4.4. Exception Report (Incident)
3.4.5. Response Comparison Report (Apparatus)
3.4.6. Apparatus Response Time (Apparatus)
Optional Reports, Client will select no more than five (5) from the following
list:
3.4.7. Response Time Fractals (Incident)
3.4.8. Response Time Percentiles (Incident)
3.4.9. Stacked/Concurrent Calls (Incident)
3.4.10. Incident Loss Value (Incident)
3.4.11. Apparatus 1710 Response (Apparatus)
3.4.12. Incident Audit (Incident)
3.4.13. Call Frequency (Incident)
3.4.14. Temporal Response Time (Apparatus)
3.4.15. Resource Allocation (Apparatus)
3.4.16. Effective Response Force (Apparatus)
4. FireView Application Deployment (Remote) Timeline: October 15th, 2012
4.1.1. Client will install/license ArcGIS Desktop on each workstation
4.1.2. Client will install/license FireView Desktop on each workstation
4.1.3. Client/Omega will establish a centralized location for the GIS data and
shared application resources
4.1.4. Omega will test the import process and FireView Desktop application
4.1.5. Omega will import up to three (3) months of historical data for each
dataset; the client will be responsible for importing data beyond three (3)
months
4.1.6. Omega will configure the profile import automation with the client’s
assistance
5. FireView Application Training (At Client Site) Timeline: November 1st, 2012
5.1. FireView Desktop on-site training
5.1.1. Up to six (6) computers for training; Recommended participants include
the following:
7 | Page
5.1.1.1. Public Safety analyst
5.1.1.2. GIS manager
5.1.1.3. Command staff representative
5.1.1.4. IT representative
5.1.1.5. Records or data entry clerk
5.1.1.6. Database administrator
5.1.2. One (1) Omega trainer will conduct the training session
5.1.3. Training will be approximately twelve (12) hours over the course of two (2)
days
5.1.4. Client will ensure that the appropriate ESRI software is installed on the
training workstations, prior to the arrival of Omega trainer
5.2. Omega will provide FireView Desktop refresher tutorials
6. Final Application Review Timeline: November 15th, 2012
6.1. Following FireView Desktop training, there will be a fourteen (14) day review
period. The review period serves as quality assurance/control to ensure the
project has been completed and the deliverables conform to the scope. Areas
to review:
6.1.1. FireView saved queries are working properly and the correct pick list values
are included
6.1.2. FireView saved queries return anticipated results (records)
6.1.3. Data shown in the selection table and reports matches source data
6.1.4. Omega Street network is accurately tuned
6.1.5. Geocode process is configured properly
6.2. Omega will send the client a project completion sign-off form; the client will
sign/date the form and e-mail/fax back to Omega and the project will be
marked as complete.
FireView Dashboard Deployment
7. FireView Dashboard Application Configuration Timeline: December 1st, 2012
7.1. The Dashboard will include a rolling thirty-six (36) months of historical data for each
dataset
7.2. Omega will configure each dataset to display up to twenty (20) fields
7.3. Omega will use the Bing geocoding service unless the client requests that their own
spatial reference data be used in which case Omega will create the address locator
7.4. Omega will configure up to ten (10) geographic query layers
7.5. Omega can configure up to five (5) operational layers
7.6. Omega will create up to five hundred (500) total saved query pick list items per query
layer
7.7. Omega will use Bing maps for the application’s background layers or can possibly
integrate with a client’s existing map caches (hosted on a different server at the client’s
site)
7.8. Configure FireView Dashboard design
7.8.1. Briefing Books
8 | Page
7.8.1.1. Omega will configure one (1) Briefing Book which will include RMS-
NFIRS data
7.8.1.1.1. One (1) Executive Briefing Book with approximately (48)
Widgets
7.8.2. Pages
7.8.2.1. Incident trends
7.8.2.2. Recent activity
7.8.3. Widgets
7.8.3.1. Filter/Pin Map/Heat Map
7.8.3.2. Density Map
7.8.3.3. Trend Chart
7.8.4. Hot Sheet; Omega will configure up to five (5) Alerts
8. FireView Dashboard Deployment Timeline: January 1st, 2013
8.1. Omega will deploy the FireView Dashboard application
8.2. Omega will configure data import profiles for data transfer to the FireView Dashboard
8.3. Omega will import up to three (3) months of historical data for each dataset; the client
will be responsible for importing beyond three (3) months
8.4. Omega will schedule automated data import/extractor process
8.5. Dashboard Widgets will refresh at least one (1) time per day and up to four (4) times per
day if the resources and configuration will allow for that
9. FireView Dashboard Application Training Timeline: January 15th, 2013
9.1. Omega will provide up to six (6) hours of remote Administrator/Designer training for up
to two (2) trainees
9.1.1. The FireView Dashboard Admin Designer Tutorial PDF document will be e-mailed
to the Administrator/Designer trainees following training
9.2. Omega will provide up to two (2) sessions of up to four (4) hours of training on
functionality features for up to ten (10) trainees per session (on-premise training).
9.2.1. The FireView Dashboard End User Tutorial PDF document will be e-mailed to the
End User trainees following training
10. Final Application Review Timeline: February 1st, 2013
10.1. Following End User training, there will be a fourteen (14) day review period.
The review period serves as quality assurance/control to ensure the project has been
completed and the deliverables conform to the scope. Areas to review:
10.1.1. Saved queries are working properly and the correct pick list values are included
10.1.2. Data shown in the report grid and identify box matches source data
10.1.3. Geographic query layers and selection fields are correct
10.1.4. Operational layers are working properly and are labeled with the correct field
10.1.5. Geocoding process is configured properly
10.1.6. Dashboard queries return anticipated results (records)
10.1.7. Dashboard is functioning properly
9 | Page
10.2. The application content is configurable around your data; the application
interface is not customizable
10.3. Omega will send the client a project completion sign-off form; the client will
sign/date the form and e-mail/fax back to Omega and the project will be marked as
complete.
10 | Page
Deliverables
For each deliverable, the response of “Both” indicates that FireView Dashboard and Desktop
satisfy the requirement. Response of “Desktop” or “Dashboard” indicates one or the other
application satisfies the requirement, but not both. Response of “Not Available” indicates
Omega does not meet the deliverable. These responses are shaded.
Required Service/Deliverable Application Methodology
Analyze response performance Both Out of the box capability for both applications
Specify alternate fire apparatus locations and scenarios Desktop Station Analysis is a routine in Desktop for
analyzing how well a configuration of
resources is able to deliver services to
geographic areas within a community.
Calculate response performance and provide graphical
displays
• Provide reports by call category Both Out of the box capability
• Provide reports by individual fire management zones Both Out of the box capability
Automatic color-coding of the service area according to
hazard type and time targets
Both Out of the box capability for both applications
Calibrate response model to mimic real world street
network
Desktop Street speed information will be adjusted (or
tuned) to reflect speeds commensurate with
actual unit response data. This is done by using
ArcGIS and FireView routines to raise/lower
street speeds in areas around each existing
station and throughout the street network
based upon actual apparatus drive time
response data.
Estimate of response travel distance based on actual street
network
Desktop Out of the box capability
Call-to-scene time estimates based on historical CAD data Desktop Out of the box capability.
Apparatus run-loads and availability for new location
scenarios based on historical distribution of incidents
Desktop Out of the box capability, Station analysis
calculates run loads relative to hypothetical
distribution coverage
Response performance projections for apparatus
relocations calculated to match actual recorded
performance
Desktop,
Future
Release
Future release, 2013
Calculations of both average and percentile response
performances for the jurisdiction, station areas and various
fire management zones within the service area. Analyze
selected incidents in multiple ways using multiple criteria:
• Shift Both Out of the box capability.
• Time of day Both Out of the box capability.
• Day of week Both Out of the box capability.
• Month Both Out of the box capability.
• Type of call Both Out of the box capability.
• Specific unit areas Both Out of the box capability.
Displays of response performances for any designated call
type (fires, medicals, rescues, hazardous materials etc.)
Both Out of the box capability.
Capabilities for using, deleting, saving, retrieving, and
comparing different analysis scenarios
11 | Page
Capabilities for specifying and reviewing response
performance at specific locations
Both Out of the box capability.
Compatible with Windows Operating System Both Out of the box capability.
Taps into historical CAD data and reviews current workloads
and response performance
Both Out of the box capability.
Performs on-the-spot “what if” analysis of the department’s
current performance
Desktop Out of the box Station Analysis
Generates objective, factual data to explain departmental
performance at all levels
Both Both applications use factual data derived
from CAD or RMS records
Enables decision-makers to gain insights into current
performance
Both Out of the box capability
Prints easy-to-understand, color-coded maps for analysis
and reporting
Desktop Out of the box capability.
Exports color-coded maps to other formats including
Microsoft Excel, Word, PowerPoint and in PDF format.
Desktop Out of the box capability.
Zooms in for a view of all incident data and factors including
landmarks, schools, or other specific identified risks
Both Out of the box capability.
Calculate workload and response performance for
specifying days of the week, times of day, seasons of the
year, and incident type groups. Extract incidents of a given
type or time period and display their density thematically in
a map.
Both Out of the box capability.
Displaying thematically the percentage of incidents meeting
performance targets.
Dashboard Out of the box capability.
Zoom controls for close-up viewing of all color-coded
incidents in an area. ID control to obtain all details about an
incident including number, date, location, etc.
Both Out of the box capability.
Review current coverage using different response criteria Both Out of the box capability.
Experiment with different time targets Both Out of the box capability.
Calculate response performance reports by individual fire
management zones
Both Out of the box capability.
Plot incident plots along with the line-up and response
performance info
Desktop Out of the box capability. Response
Comparison report and map to see variance
between target time and actual time for first
unit arrival
Plot unit response plots along with their response
performance
Desktop Out of the box capability. Response
Comparison report and map to see variance
between target time and actual time for all
units
Analyze the frequency with which units respond outside
their first due areas for purposes of response reliability
Desktop Out of the box capability. Response Reliability
12 | Page
Qualifications and Experience
Corporate Background
The Omega Group, Inc. is a California S Corporation, founded in 1992 to provide GIS solutions to
public safety organizations, school districts, and municipalities. The Company’s product portfolio
has evolved from desktop offerings of high end tools for crime & fire analysts to a portfolio of
analysis-driven decision support, performance management and electronic briefing services
delivered from the cloud to all levels of the modern public safety agency. We have repositioned
analysis and mapping from a specialist function to an organization-wide mission-critical solution.
Our corporate headquarters are located in San Diego, with a regional office in Philadelphia.
Industry Experience
On premise GIS and analysis-powered performance management systems for Standards of
Coverage (SOC) for fire make it possible to look past the daily demands of dispatch and begin to
see a bigger picture of incident activity in neighborhoods and measure the performance of fire
service managers. While some solutions prove effective, they can be costly, inflexible and have
less impact by virtue of limited distribution of sophisticated analytical output to a relatively
small group of command staff with the opportunity and understanding to interpret it.
The current economic climate demands that fire departments find ways to maximize
organizational efficiency & effectiveness while providing equal or improved service levels with
less resources and cost.
The Omega solution strategy is based upon the simple tenet that to achieve maximum
organizational efficiency & effectiveness in a dynamic operating environment requires the ability
to analyze data and act on insights in real-time in the context of current fire priorities.
Significant investments have been made in data-generating applications such as computer-aided
dispatch and records management, and a myriad of other tactical, administrative, financial and
compliance reporting systems without a comparative investment in data integration, analytics
and visualization capabilities.
Standard of Cover
FireView Dashboard and FireView Desktop examine and analyze response times and
performance standards established by the fire agency. Call processing, turnout, travel, and total
reflex times are evaluated in regard to averages, percentiles, and compliance percentages. The
chart drill-down capability within the FireView Dashboard application allow management to
easily focus on problems within specific geographic areas, times/days, stations, shifts, and staff.
The Response Model in FireView Desktop enables departments to look at their response
capabilities relative to coverage standards and to analyze how fire station and apparatus
placement will affect their ability to meet the agency’s Standards of Cover.
The Omega Group solution is built on four cornerstones:
1. Aggregation of multiple sources of traditional & non-traditional data relevant to public
safety…’Big Data’
13 | Page
2. Availability of full spectrum analytics that can process multi-source aggregated public
safety data to derive new insights for improved decision-making and resource
allocations…’Big Analytics’
3. Better integration of derived insights with fire response via actionable delivery channels
and formats that touch all levels of the organization…’Big Visualization’
(mapping/dashboards)
4. Delivery of these capabilities from a private ‘Cloud’…’Big Savings’
References
Agency Name, Address, Contact,
Title, Phone Number, E-Mail
Approximate
Service Area
Population
Operational
Applications
Version/
Release
Installation
Dates
Key
Interfaces
South Metro Fire Rescue
9195 E. Mineral Avenue,
Centennial, CO 80112
Dan Qualman, Fire Chief
Dan.Qualman@southmetro.org
198,000 FireView
Desktop
Current
Version 5.0
2/2005
(formally a
Parker Fire
Contract)
High
plains
RMS
Aurora Fire Department
15151 E. Alameda Pkwy,
Ste. 4100
Aurora, CO 80012
Deputy Chief Danny Willcox
Dwillcox@auroragov.org
325,000 FireView
Desktop
Current
Version 5.0
5/2006 Motorola
RMS
Boise Fire Department
150 N. Capitol Blvd
Boise, ID 83702
Eric Quinn, RMS DBA
equinn@cityofboise.org
205,000 FireView
Desktop
FireView
Dashboard
Current,
14 | Page
List of Project Personnel
Brandon Stam, our proposed project manager is responsible for the oversight, coordination,
technical development, implementation, & on-going assurance of client satisfaction. Typical
responsibilities include the development of a Work Breakdown Structure (WBS), data extraction
from CAD/RMS databases, geocoding, map/report customization, software training, & technical
support. Mr. Stam has built, customized, & implemented applications for more than 60 law
enforcement agencies and fire departments.
Mike Fowler, our implementation engineer has over six years of experience working with
geographic information systems and cartography in assisting all Omega Web clients with their
deployment needs. Mr. Fowler has broad experience in deploying websites using IIS,
configuration, deployment and maintenance of web technologies.
15 | Page
Resumes
Brandon Stam Project Manager/Implementation Specialist
Synopsis Mr. Stam’s responsibilities include management, coordination, technical development, implementation, &
on-going quality assurance of software and consulting projects. As a FireView product manager, he
contributes to ongoing research on fire service topics and priorities and drives product, process, and
content development. Mr. Stam has worked directly with over 60 agencies and provided support and
advising for dozens more.
Professional
Highlights Challenge 1: Heartland Communications JPA, San Diego County, CA
• Create a daily import process to merge overlapping data from 10 fire agencies into
combined datasets and applications
• Implement a regional FireView Dashboard application with focused content serving
each agency and a central FireView Desktop application enabling Heartland’s GIS
analyst to provide additional analysis
• Provide training and support to fire chiefs, assistant chiefs, and support staff
Challenge 2: San Diego City and County Standards of Cover Fire Studies
• Data collection, extensive GIS and tabular analysis, and provision of methodologies,
maps, data, and reports in support of two Standards of Cover studies for the County
of San Diego and San Diego City Fire Department
• The results of this study led to policy and deployment changes seeking to improve
emergency response in the city and county
Challenge 3: Greek National Police
• Implement a Greek language CrimeView Server application on a two week timeline
• Coordinate and execute project utilizing Greek police and business partner staff for
support and translation
• Provide ongoing indirect support for application
Challenge 4: Los Angeles County Fire Department
• Implement a FireView Desktop application supporting analysis of a large geographic
area (300,000 incidents/year) and coverage analysis of 170 existing and numerous
planned fire stations
• Create workflows and models to enable agency staff to update and maintain non-
automated portions of the application with minimal effort
Challenge 5: Detroit Fire Department
• Implement a FireView Dashboard application enabling large scale, high-frequency
analysis and tracking of daily workload and response performance
• Deliver custom content enabling users from the fire department, police
department, and mayor’s office to track rampant arson activity during Angel’s Night
and other peak activity periods
• Configure various automated import processes to bring in data hourly to all
FireView applications during peak activity periods
Skills
ArcGIS 8-10
Spatial Analyst
Network Analyst
ArcSDE & ArcGIS Server
SQL for SQL Server, Oracle, AS400
Standards of Cover / NFPA 1710
NFIRS
Crystal Reports 11
16 | Page
Project History
Fire Department Detroit, MI FireView Dashboard
Fire Department Los Angeles County, CA FireView Desktop
Fire Dispatch Authority Heartland JPA, San Diego, CA FireView Desktop
Fire Department Norfolk, VA FireView Desktop & Server
Fire Department Boise, ID FireView Dashboard
Police Department Rialto, CA CrimeView Dashboard
Police Department Glendale, CA CrimeView Dashboard/Server
Fire Department Henrico County, VA FireView Desktop & Dashboard
Education
BA Geography, University of California, Santa Barbara, 2003
Professional Certification in Project Management, San Diego State University, 2012
17 | Page
Michael Fowler Dashboard Deployment Specialist
Synopsis Mr. Fowler has over six years of experience working with geographic information systems and cartography in
assisting all Omega Web clients with their deployment needs. Mr. Fowler has broad experience in deploying
websites, application configuration, application deployment and maintenance of web technologies, in a multitude
of different client-server environments
Professional Challenge: Maintain a reliable and efficient hosting environment supporting many clients
Highlights using our different web-based applications
• Oversee and execute deployments of new applications, minimizing or eliminating impact to
users
• Maintain total awareness of all applications and processes to avoid conflicts
• Provide the highest level of service possible for every client
Responsibility: Provide support for existing applications
• Troubleshoot and fix issues with data in a variety of Omega products
• Troubleshoot and fix issues with product configurations
• Troubleshoot and fix environmental issues in unfamiliar environments
Responsibility: Deploy web-based applications
• Assist clients acquiring hardware and software for new projects
• Working with project builders to assure correct configuration and testing
• Remotely installing necessary software and project components to deploy applications
Responsibility: IT Support
• Maintain client applications in the Omega Hosting Environment
• Provide assistance with day-to-day IT support issues for co-workers
Skills
Microsoft SQL Server
Microsoft IIS
HTML, XML, Web Services, JavaScript,
Other
Cisco Certified Network Associate (CCNA)
Windows Server 2008 R2
ESRI ArcGIS
Omega CrimeView Dashboard
Omega CrimeMapping.com
Omega FireView Dashboard
ESRI ArcSDE
ESRI ArcGIS Server
Project History
Inter-departmental Crime Data Access /
Community-Oriented Policing
Inter-departmental Crime Data Access /
Community-Oriented Policing
Inter-departmental Crime Data Access
Inter-departmental Crime Data Access
Peoria PD/Sheriff, IL
Norfolk PD, VA
Los Angeles PD / Los Angeles
County Sheriff, CA
CrimeView Community
CrimeView Server
CrimeView Dashboard /
CrimeView Community /
CrimeMapping.com
CrimeView Dashboard
Education
• BS Information Sciences & Technology, Pennsylvania State University
• BA Telecommunications Pennsylvania State University
18 | Page
Organization Chart/Proposed Project Team
The Omega Group project team includes a project manager who is supported by a Project
Implementation Specialist and Web Application Implementation Specialist. Our project manager
will work directly with the Poudre Fire Authority project manager as well as other staff
authorized by the Poudre Fire Authority to facilitate the project activities. These individuals will
be responsible for ensuring a productive and collaborative project implementation.
The Omega Group project team organizational structure is designed to support all phases of the
implementation. While the project staffing is sufficient for carrying out the deliverables of our
proposal, we have at our disposal additional administrative and technical resources to support
our team and Poudre Fire Authority. The Omega Group reserves the right to propose changes to
the team structure prior to project commencement.
Client Roles and Responsibilities
Critical to the success of every implementation is having the appropriate client staff prepared to
be active participants and to understand what is expected from them for the duration of the
implementation.
Client Project Manager
The client project manager is responsible for the timely coordination of assigned project tasks.
Database Administrator
The client database administrator is responsible for providing information about the CAD/RMS
database and assisting with the collection of source data, including provision of an ODBC
database connection when necessary.
19 | Page
IT Specialist
The client IT specialist is responsible for installing/licensing the Esri/Omega software, providing a
method of remote access, and creating a sub-domain host header.
GIS Analyst
The client GIS analyst is responsible for providing and maintaining base map data in an ESRI
compatible format.
Public Safety Analyst
The public safety analyst should have experience working with CAD/RMS data. The public safety
analyst should provide input during the project’s development.
Dashboard Administrator
The Dashboard Administrator is responsible for adding/maintaining user accounts. The
Dashboard Administrator can also be the Dashboard Designer.
Dashboard Designer
The Dashboard Designer is responsible for creating/maintaining Dashboard content (Widgets,
Pages, Alerts, Queries on Demand, etc).
Omega Roles and Responsibilities
Omega Project Manager/Implementation Specialist
The Omega project manager/Implementation Specialist is responsible for the coordination,
development and implementation of a project. A project manager/ Implementation Specialist
has both the technical proficiency and management skills to carry out all project tasks from
inception to completion. Project managers will prioritize project tasks in accordance with
project schedules and delegate work to project staff as necessary. Responsibilities include:
• Leading internal and/or external meetings on project kickoff, implementation,
scheduling, project status and project evaluation
• Planning, executing, tracking and measuring all project activities required for the
successful delivery of Omega application(s)
• Identifying priorities and managing the resources required to meet the project
objectives
• Performing and/or managing the technical tasks involved in the GIS application
development process to include, but not limited to: data collection, geocoding, queries,
report writing, and map production
• Delivering project in compliance with both client and internal quality control standards
and guidelines
• Conducting training
Dashboard Deployment Specialist
The Omega Deployment Specialist is responsible for remotely installing each server-based
Omega application within the client’s environment or at Omega’s hosting facility. This takes
place once the project build has been completed and the application has been fully tested at
Omega. Responsibilities include:
20 | Page
• Verifying that the required hardware and software is in place to run the application
• Installing all ESRI software required by the application (as well as SQL Server, where
necessary)
• Installing all FireView Dashboard software
• Configuring the application to function within the specified environment
• Troubleshooting any environmental issues that may arise during deployment
Availability
Project staff maintains multiple projects and will perform work for others during the terms of this
Agreement.
The Omega Group will be available for a “webinar-style” demonstration/interview meeting during
the week of July 16th.
Estimated Hours by Task
Desktop and Dashboard Combined Services
1. Project Planning/Management Estimated Project Hours: 42.2 Hours
2. Omega Import Wizard Configuration Estimated Project Hours: 12.2 Hours
FireView Desktop Deployment
3. FireView Application Configuration Estimated Project Hours: 25.1 Hours
4. FireView Application Deployment (Remote) Estimated Project Hours: 6.3 Hours
5. FireView Application Training (At Client Site) Estimated Project Hours: 23.2 Hours
6. Final Application Review Estimated Project Hours: 17.4 Hours
FireView Dashboard Deployment
7. FireView Dashboard Application Configuration Estimated Project Hours: 25.5 Hours
8. FireView Dashboard Deployment Estimated Project Hours: 9.3 Hours
9. FireView Dashboard Application Training Estimated Project Hours: 24 Hours
10. Final Application Review Estimated Project Hours: 18.8 Hours
Total Task Hours: 204 Hours
21 | Page
Schedule of Rates and Cost by Task
The Omega Group’s presentation of costs is for a fixed-fee deployment. All software and
services described under the headings of FireView Dashboard Hosted Deployment and FireView
Desktop Deployment will be performed for the stated amounts due during the first and second
year of service.
Year 1 Year 2
Total Budget $48,550.00 $10,200.00
Discounts $1,080.00 $1,530.00
Amount Due: $47,470.00 $8,670.00
_________________________________________________________________________________
FireView Dashboard Hosted Deployment Year 1 Year 2
Professional Service Package $ 12,500.00
• Project Planning and Management
• Configuration for two (2) data connections
o Incident Reports
o Apparatus Reports
• Application configuration and deployment
• Briefing Book configuration
• Login configuration
• Training
o Web-based training for Administrators
o On-site training for Shared Users
Subscription Service $ 7,200.00 $7,200.00
• Briefing Books
o Executive Briefing Book
• Logins:
o One (1) Shared user login
o One (1) Designer user login
o One (1) Administrator user login
• Data Connection/Storage
o Two (2) data sources
o Three (3) years of data
Travel $2,000.00
_______________________________________________________________________________________________________
FireView Desktop Deployment Year 1 Year 2
Software $6,850.00
FireView Desktop Software
• One (1) FireView Desktop licenses
• One (1) Import Wizard license
FireView Desktop Software Maintenance $3,000.00
• FireView Desktop Maintenance
22 | Page
Services $18,000.00
Professional Service Package
• Project Planning and Management
• Configuration for two (2) data connections
o Incident Reports
o Apparatus Reports
• Software Installation
• Application Configuration and deployment
o Response data model configuration
o Report configuration
• Training
o On-site functionality training for end-users
Travel $2,000.00
________________________________________________________________________
Billing Rates
All services performed by Omega staff are billed at the rate of $185.00 per hour
________________________________________________________________________
Subscription and Maintenance Fees
Subscription and Maintenance fees represent the ongoing cost of maintaining the proposed
applications. Fee payment will commence upon completion of installation and training of the
system and cover the first twelve months of use of applications. The first year of subscription
fees are included in the total year one costs.
Enterprise Discount
The enterprise discount is offered when more than one enterprise solution module is
purchased. The enterprise discount applies to subscription services and maintenance costs. The
current enterprise discount is 15%.
Additional Requirements
• The current enterprise discount rates are subject to change without notice.
• First year enterprise discounts are limited to subscription fees only. Second year
enterprise discounts are for both maintenance fees and subscription fees.
• The enterprise discount will not apply when only one enterprise solution module is
purchased. Furthermore, if at any time the purchaser decides to discontinue paying
subscription fees and/or maintenance for all but one enterprise solution module, the
remaining enterprise solution module’s annual maintenance or subscription fee will
revert to annual rates with no discounts.
• Annual fees are subject to a maximum 3% increase per year.
________________________________________________________________________
23 | Page
Third Party Software and Hardware Requirements/Price Summary
The following software and hardware is required, however NOT included are part of the
deliverables from Omega. The client should use this table as a requirement/budgetary checklist.
For more details regarding software and hardware requirements, please refer to the table of
contents to direct you to the correct page.
Software Year 1 Year 2
Esri Software
• ArcGIS 10 2 single or concurrent $3,000.00 $1,000.00
• Spatial Analyst 1 single or concurrent $2,500.00
Hardware
• Import Server $5,000.00 estimate
Data
• Tom Tom Dynamap Transportation Data $6,000.00 $2,500.00
Payment Schedule
In consideration of the services to be performed and delivered, Omega shall be entitled to
compensation in the total amount of $47,470.00. The payment schedule consists of six (6)
payments and is due as follows:
FireView Desktop Application
• FireView Desktop
software license costs
and travel costs
$8,850.00 Payment due upon completion of Project Planning
Meeting (Task 1)*
• FireView Desktop 40%
of Professional
Services Costs
$7,200.00 Payment due upon completion of FireView Desktop
Application Deployment (Task 4)*
• FireView Desktop 40%
of Professional
Services Costs
$7,200.00 Payment due upon completion of FireView Desktop
Training (Task 5)*
• FireView Desktop 20%
of Professional
Service Costs
$3,600.00 Payment due upon completion of FireView Desktop
Final Application Review (Task 6)*
FireView Dashboard Application
• Set up/ Training/
Travel
$14,500.00 Payment due upon project initiation
• Subscription Fee for
Year 1
$6,120.00 Payment due upon completion of installation and
training (Task 5)*
* See Task Order
24 | Page
General System Requirements
Software Specifications
FireView Desktop: the following software will be required for the deployment:
• Omega Import Wizard
• Esri’s ArcGIS (ArcView), version 10
• Esri’s ArcGIS (Spatial Analyst) version 10
FireView Dashboard: the following software will be required for our Cloud-based
deployment:
• Omega Import Wizard (Only one license required and will be shared with FireView
Desktop, see above)
• Omega Extractor
• Esri’s ArcGIS (ArcView), version 10
Data Specifications
FireView Dashboard automates the import of source data via an application called the Import
Wizard. Each FireView Dashboard dataset (layer) is imported daily via Import Wizard profiles
(licensed individually). The profile license contains configuration information for extracting
data from an RMS (via a SQL Statement), geocoding, data processing, & subsequently
outputs/appends the result into a GIS feature class format. It is important to consider that
source data originating from a relational database will be transposed into a de-normalized (flat
file) format. As a result, there will be one “dot” on the map per record in the FireView
Dashboard dataset. The maximum number of records returned on a Dashboard widget or
query is 5,000 records
Dataset Data Source Dataset Data Source
Incident Reports High Plains RMS Apparatus Reports High Plains RMS
Data Schema
The following data fields will be included within the standard offering of the FireView Dashboard
and Desktop. If these fields are not readily available within the RMS database, this information
will not be included in either application. No substitutions will be made for other available fields
unless identified during contract negotiations.
Incident Data
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INCIDENT NUMBER 2 INCIDENT_NUM YES
INCIDENT CATEGORY 3 FV_LEGEND YES YES YES YES
INCIDENT TYPE 4 INC_TYPE YES YES YES YES
SHIFT 5 SHIFT YES YES YES YES
ADDRESS 6 FV_ADDRESS YES
APARTMENT 7 APT YES
25 | Page
AREA 1* 8
YES
YES YES
AREA 2* 9
YES
YES YES
AREA 3* 10
YES
YES YES
STATION 11 STATION YES YES YES YES
RESPONSE
TYPE/PRIORITY
RESPONSE 12 RESP_TYPE_DESC YES YES YES YES
911 DATE 13 911_DATE YES
NOTIFY DATE 14 NOTIFY_DATE YES
ARRIVAL DATE 15 ARRIVAL_DATE YES
LAST UNIT CLEAR
DATE 16 CLEAR_DATE YES
PROCESS TIME 17 PROCESS_TIME YES YES**
DEPT RESPONSE
TIME 18 DEPT_RESP_TIME YES YES**
TOTAL REFLEX TIME 19
TOTAL_REFLEX_TI
ME YES YES**
ACTION TAKEN 20 ACTION1_DESC YES YES YES YES
PROPERTY USE 21 PROP_USE_DESC YES YES YES YES
PROPERTY LOSS 22 PROP_LOSS YES
PROPERTY VALUE 23 PROP_VALUE YES
PROPERTY SAVED
(percent value) 24
PROP_LOSS,
PROP_VALUE YES
MUTUAL AID 25
MUTUAL_AID_DE
SC YES YES YES YES
CAUSE OF IGNITION 26 CAUSE_IGN_DESC YES YES YES YES
INJURY_FATALITY*** 27
FS_FATAL,
FS_NONFATAL,
OTHER_FATAL,
OTHER_NONFATA
L YES YES
REPORT COMPLETED 28 COMPLETED YES YES YES YES
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip Code,
etc.
** Part of "Response Times" query group
*** If possible, created by using a formula to combine RMS/CAD fields into single Dashboard
field
Apparatus Data
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INCIDENT NUMBER 2 INCIDENT_NUM YES
26 | Page
UNIT 3 UNIT YES
YES YES
APPARATUS TYPE 4 UNIT_TYPE_DESC YES YES YES YES
ARRIVAL ORDER 5
ARRIVAL_ORDER_
OVERALL YES YES YES YES
INCIDENT CATEGORY 6 FV_LEGEND YES YES YES YES
INCIDENT TYPE 7 INC_TYPE_DESC YES YES YES (TOP 20)
YES (TOP
20)
ADDRESS 8 FV_ADDRESS YES
APARTMENT 9 APT YES
AREA 1* 10
YES YES YES
AREA 2* 11
YES YES YES
AREA 3* 12
YES YES YES
STATION 13 STATION YES YES YES YES
SHIFT 14 SHIFT YES YES YES YES
RESPONSE
TYPE/PRIORITY
RESPONSE 15 RESP_TYPE_DESC YES YES YES YES
911 DATE 16 911_DATE YES
NOTIFY/DISPATCH
DATE 17 DISPATCH_DATE YES
ENROUTE/ROLL DATE 18 ENROUTE_DATE YES
ARRIVAL DATE 19 ARRIVAL_DATE YES
CLEAR DATE 20 CLEAR_DATE YES
TURNOUT TIME 21 TURNOUT_TIME YES YES***
TRAVEL TIME 22 TRAVEL_TIME YES YES***
DEPT RESPONSE
TIME 23 DEPT_RESP_TIME YES YES***
TOTAL REFLEX TIME 24
TOTAL_REFLEX_TI
ME YES YES***
RESOURCE TIME 25
TOTAL_RESOURCE
_TIME YES YES***
PROPERTY USE 26 PROP_USE YES YES*** YES YES
ACTION TAKEN 27 ACTION1_DESC YES YES YES YES
MUTUAL AID 28
MUTUAL_AID_DE
SC YES YES YES YES
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip
Code, etc.
**If not available, Omega can create the UNIT_NUMBER field when technically feasible
** Part of "Response Times" query group
GIS Data Specifications
Boundary and Landmark Features: The client shall provide files of relevant boundaries and
landmarks within the area of interest. Typical features include:
27 | Page
• Boundaries and jurisdictions such as beats and reporting districts
• Landmark information such as schools, parks, and other locations of interest
Networkable Street Centerline File FireView Desktop Only
It is important that the street network file accurately support networking functions, including
travel speeds, one-way streets, prohibited turns, overpasses, underpasses, and closed streets,
where appropriate. It will be the client’s responsibility at all times to ensure that the Street
Network is accurate and compliant with the FireView application.
Geocoding Reference Data
The client is responsible for providing accurate reference data that will be used to generate a
geocoding service. Reference data may include the following geography: street centerline file,
address points or a parcel layer.
Background Layers FireView Dashboard Only
The FireView Dashboard supports the use of one or more Background Layers (or map caches).
These Background Layers are used to display a base map as a backdrop to the Geoprocessing
results.
Bing maps are the default map cache for the application’s background layers. The following
alternatives for map caches are available for Omega-Hosted and On Premise deployments:
1) MS Bing* or Esri Maps
- Both street and air photo for the application’s background layers.
2) Client map caches
- The following criteria must be met if the client wishes to use their own maps
caches:
a. Caches must be built using the Web Mercator Auxiliary Sphere (102100 or
3857) projection
b. If multiple caches will be used in the Dashboard, the zoom levels must
match between caches
c. The caches must be accessible by URL to all intended end-users
d. The client is responsible for maintaining the map cache(s) and assuring its’
availability and accessibility.
* At any time, The Omega Group maintains the exclusive right to determine a third party map
cache source to be used in the FireView Dashboard application. At its sole discretion, The
Omega Group may replace one third party map cache source for another.
Application Specifications
Report Specifications FireView Dashboard Only
Reporting is designed in Microsoft Silverlight. Capabilities include sorting and grouping of
records, dynamic mapping and charting.
28 | Page
Report Specifications FireView Desktop Only
Crystal Reports is the standard reporting tool for FireView Desktop. FireView includes a set of
standard report templates. Omega can design additional reports at the request of the client
(additional fees apply).
Symbology
All applications include standard Omega symbology for each data source.
Operational Layers FireView Dashboard Only
An operational layer represents a set of geographic features, typically boundaries or landmarks
that can be displayed on top of the base geography.
Saved Queries
Saved queries are a set of pre-defined data queries organized in folders. Data queries are based
on data available from the RMS system and vary in design from one application to another.
Geographic Queries
Geographic queries filter your data query by location, a known boundary, point of interest,
address or intersection. This will limit your search results to those records occurring within the
selected boundary, or within the specified radius of the point of interest, address or
intersection.
Windows Specifications
A local administrator account is required for Omega use on all servers involved in the project.
This account must be the same across all servers and must use the same, non-expiring
password.
Remote Access Requirement
• Establishing remote connection to the server(s)
o Data collection, installation and technical support will be performed through
remote connection
o Omega recommends VPN or Citrix’s GoToMyPC for remote connections
Client must provide the necessary remote access details
Hardware Specifications
Import Server
• Quad-Core Intel® Xeon® processor
• 6 GB RAM
• RAID 1 or RAID 5 disk configuration using SAS 15K RPM 146GB disks or better
• Gigabit Ethernet network card
FireView Desktop End-user Workstations
• Processor: Intel Core 2 Duo Processor (not less than 2.6 Ghz)
• RAM: 4 GB
• Hard drive: 250 GB
29 | Page
• Graphics Card: 256 MB RAM or better
• Network Card: Gigabit Ethernet
• OS: Windows XP/Vista/Windows 7
• Other: DVD drive
FireView Dashboard End-user Workstations
• Processor: 2.00 GHz Dual-core Intel processor (or faster)
• RAM: 2 GB
• Network Card: 1 Gb (1000 Mb) Gigabit
• Monitor: Minimum resolution: 1024px X 768px
• OS: Windows XP SP3 or newer
• Browser Support: Firefox, Safari, Chrome, or IE7 (or higher)
• Other: Silverlight 4 (or higher)
Configuration Diagram
The diagram below depicts a typical data flow from the client databases to the FireView Desktop
The diagram below depicts a typical data flow from the client databases to the FireView
Dashboard
30 | Page
Customer Support Program
The Customer Support Program is limited to the policies below:
Definitions
Customer Support Program: The software and application maintenance package.
Support Activation Date: The date support begins. This occurs on the installation date of the
software application.
Term Date: The due date for annual payment of the Customer Support Program will be referred
to as the Term Date. The Term Date is established as the day and month that the software is
installed on.
Payment Guidelines
1. The cost of the Customer Support Program is calculated to be 20% the cost of software
and data connections.
2. Payment for the Customer Support Program is collected annually on the Term Date. The
first annual payment is due one (1) year after the Installation of software.
3. Approximately 45 days prior to the annual Term Date, The Omega Group will send
notice of payment in the form of an invoice to the client by email.
4. After the first annual payment, all future payments for the Customer Support Program
are subject to a 3% increase, annually.
5. The Software Maintenance for additional software licenses that are purchased after the
Support Activation Date will be paid on the Customer Support Program’s Term Date.
a. The first annual payment for the additional Software Maintenance will be
prorated based on the number of days during the term that preceded the
licensing of the additional software.
b. Following the first annual (prorated) payment, annual payments for additional
Software Maintenance will be paid in full on the Customer Support Program’s
Term Date.
General Terms
To be eligible for Omega support services, users should be aware of, and adhere to the following
terms:
1. The software license will be registered with The Omega Group. The Omega Project
Manager may assist with software registration.
31 | Page
2. The Omega Group provides technical support for Omega software and the Omega
Import Wizard interface(s) only. Specific items not included under technical support are
provided below (Section: Limitations).
3. The initial Omega software application implementation and installation must be
performed by an Omega Project Manager. This requirement assures that telephone
support, future software service packs, and major version upgrades can be administered
effectively.
4. By paying for support, the client agrees to receive support services from The Omega
Group and accepts the terms and limitations of the Customer Support Program.
5. The Customer Support Program will automatically renew each term unless cancelled
prior to the term date with 60 days written advance notice by sending an email to
ap@theomegagroup.com.
6. Should there be a lapse in payment, all past due fees must be paid to restart service.
Limited to three years of past due payments.
Limitations
Users should be aware of the following limitations regarding support services:
1. Omega’s technical support is limited to unmodified, “off-the-shelf” Omega software
technology. Any issues that arise from the client modifying the application’s files,
configuration, or environment without Omega approval will not be covered under this
agreement. The client will be charged an additional fee per incident or per hour to
troubleshoot and resolve the issue.
2. Technical support is not a replacement for training. Additional application training is
available from Omega at an additional cost.
3. Technical support does not cover configuration changes to existing applications and/or
additional development to the Omega application (i.e. building new profiles, reports,
saved queries, etc.). These professional services can be provided for an additional cost.
4. Technical Support only covers issues with Omega software and excludes any issues with
3rd party applications that interface with Omega software.
5. Technical support does not cover issues that arise from changes/upgrades in the client’s
hardware, operating system, source databases (RMS, CAD and other Databases), source
data (geographic layers: including streets, boundaries, points or any reference data) or
network environment. The client will be charged an additional fee per incident or per
hour to troubleshoot and resolve the issue.
6. The Omega Group is not responsible for maintaining back-up files of the client’s
software application. The Omega Group may have copies of the client’s application files
32 | Page
stored at our offices (acquired during the application building and testing process),
however, this data is limited to the extractions or samples received during the
application development and can quickly become out-of-date.
7. In the event of complete data loss due to a client’s server crashing or other
circumstances unrelated to the Omega software, The Omega Group can assist as
resources permit, but will not be held financially responsible for reinstalling and
reconfiguring the application. The Omega Group will provide these services at an
additional charge for time, materials, and travel.
8. The Omega Group’s Customer Support Program is not a replacement for ESRI’s software
Customer Support Program and does not include costs for ESRI’s suite of software
products, including costs to install/uninstall ESRI software components.
9. The Omega Group’s Customer Support Program includes software bug fixes and
software enhancements for existing, unmodified applications. The Omega Group will
contact the client to schedule updates to the application as they become available.
10. Omega software is dependent upon specific versions of 3rd party software applications.
Upgrades to 3rd party software used to run Omega software will require a new version
of Omega software to be installed to remain compatible. Upgrades to Omega software
are only provided for products that have not reached the “mature” or “retired” phase of
the product lifecycle. Full-version upgrades of Omega software in support of upgrading
3rd party applications are not covered under support and will require additional charges
for time and materials. Please contact The Omega Group before planning any upgrade
to supporting 3rd party software applications.
Remote Connectivity
1. Technical Support will be performed through a remote connection.
2. Omega recommends a VPN or Cirtrix’s GoToMyPC for remote connections. Client must
provide the necessary remote access details if a VPN is used.
3. If the client is unable to provide a high speed remote connection, a fee will be incurred
based on the additional time required for troubleshooting the support request.
Support Hours
Technical support hours are Monday through Friday, from 7:00 AM to 5:30 PM Pacific.
Technical support can be reached by calling (800) 228-1059 or by sending email to
Support@theomegagroup.com. It is Omega’s intent to respond to all technical support inquiries
within twenty-four (24) hours of receiving the request, during normal business hours.
33 | Page
Addendum to Omega Maintenance Program
The FireView Dashboard Application Support Plan is intended to provide product
enhancements, bug fixes, and on-going software support for the original, unmodified
configuration of any FireView Dashboard application.
This support plan includes the following:
• Diagnosis of Omega (Dashboard application) software issues1
• Resolution of Omega (Dashboard application) software issues2
• Diagnosis of configuration issues3
• Resolution of configuration issues4
• Omega Software Updates
o Updates to Omega software functionality (as new product releases become
available)
o Bug fixes to Omega software for known issues
o Version-compatibility upgrades to Omega software5
• Limited Dashboard Designer & Administrator assistance6
• Access to help & tutorial documentation
• Map Cache Updates (for applications using Omega-built/maintained map caches)
o Clients are entitled to two (2) map cache rebuilds annually (only if originally
built by The Omega Group)
o Map cache rebuilds are by client request when updated geographic data is
made available
• Geography Layer Updates
o Clients are entitled to two (2) geographic query (filter) layer updates annually7
o Geography layer updates are by client request when new data is made available
• Saved Query Updates
o Clients are entitled to two (2) saved query updates annually8
o Saved Query updates are by client request when new query values are made
available
This support plan is NOT intended to provide the following Omega Professional Services:
Upon completion of any FireView Dashboard application project, the following requests for
service will incur an additional cost for time and materials:
• Changes to data fields, data schema, or import profiles required as a result of a change
to or switch of source RMS/CAD database systems
• Lookup table updates that result in changes to the original FireView Dashboard
application configuration
• Identify/Report Grid field changes
• Symbology legend changes
• Query layer changes or the addition of new query layers
• Re-import of historical data
• End-user support9
• Dashboard Designer tasks (create, edit, & manage Dashboard content, Briefing Books,
Pages, Widgets, Alerts, Queries on Demand, etc.)
• Administrator tasks (create, edit, & manage Dashboard logins & permissions)
34 | Page
• Training (End-User, Designer, or Administrator) 6
• Moving of a FireView Dashboard application (or single component of a FireView
Dashboard application) to a new physical server (On-Premise Deployments Only)
• Restoring of a FireView Dashboard application (or single component of a FireView
Dashboard application) after a catastrophic event (On-Premise Deployments Only)
1 “Software issues” include technical questions that are directly related to the Omega software application
including error messages, unexpected behaviors, etc. “Software issues” do not include training-related
questions.
2 Omega will troubleshoot and fix “software issues” that are completely diagnosed to be an issue with the
FireView Dashboard application under this agreement. Issues that result from conflicts with any other
software applications being installed alongside of a FireView Dashboard application on the same
computer hardware are not covered under this support agreement. The Omega Group will not provide
support unless the FireView Dashboard application remains in a dedicated environment. This support
agreement does not cover the resolution of any issues that may arise with a FireView Dashboard
application as a result of non-Omega personnel interfering with the configuration and/or operation of the
application. Resolution of these issues is billable to the client for time and materials.
3 “Configuration issues” include questions that are directly related to the settings and configuration of the
FireView Dashboard application. “Configuration issues” do not include training-related questions.
4 Omega will troubleshoot and fix any mis-configuration of the original FireView Dashboard application if it
is shown to differ from the client’s original requirements for the application. The original requirements
for the application must be shown in writing by the client to have preceded the completion date of the
FireView Dashboard application project.
5 The Omega Group will develop upgrades to the FireView Dashboard application to remain compatible
with the latest version of any supporting ESRI software applications. Until a supporting release of the
FireView Dashboard application is completed by the Omega Group, the version of ESRI software must not
be changed from the originally deployed version. If requested by the client, upgrades will be performed
by The Omega Group for an additional charge for time and materials. Migrations to a newer Omega
software product are not covered. Newer Omega software products may be purchased from The Omega
Group.
6 Dashboard Designer, Administrator & End-User training can be purchased for an additional cost.
7 Geography layer updates are required to have an identical field schema to the original layer’s format.
Changes to the schema require changing the application’s configuration and will incur an additional cost.
8 Saved query updates are limited to the saved queries groups included within the original application
configuration and based on the original source field. Adding a new saved query group(s) or changing the
source field will incur an additional cost.
9 The client’s Dashboard Designer and/or Administrator will serve as the first point of contact for all end-
user support requests. For requests that cannot be resolved by the appointed client Dashboard Designer
and/or Administrator, it is the responsibility of the client Dashboard Designer or Administrator to contact
The Omega Group for technical support where appropriate.
35 | Page
Addendum to Omega Maintenance Program
The FireView Desktop Support Plan is intended to provide on-going software support for the
original configuration of the Omega Desktop product. This support plan includes the following:
• Omega software updates (minor)
o Compatibility with the current ArcGIS release
o Updates for the Omega Desktop software routines / functionality
o Hotfixes
• Assistance with the setup of Omega Desktop on a new server and/or user’s computer.
• Provision of the current Omega Desktop tutorial (digital format)
• Diagnosis of Omega Desktop software issues1
• Resolution of Omega Desktop software errors
2
• Diagnosis of Configuration issues
3
• Resolution of Configuration errors
4
The Basic Support Plan is NOT intended to provide services for the following tasks:
Under the Basic Support Plan, the following requests for service will incur an additional cost:
• Change RMS/CAD vendor(s)
• RMS/CAD database schema updates (field length, type, size… table name change, etc…)
• Lookup table updates (code/description)
• Saved query updates
• Crystal Report updates
• GIS source file updates
• Geocoding rate enhancement
• Re-import of historical data
• Assistance with the setup of Omega Desktop on a new server or user’s computer.
• Change the GIS format (Shapefile, Personal Geodatabase, File Geodatabase, ArcSDE
Geodatabase, etc…) of the reference data or Import Wizard output data.
• Add/remove Import Wizard profile fields
• GIS editing
• Other source file integration
• Additional profiles
• Consulting
• Street network & cost matrix updates (integrating new/updated street data into the
cost matrices)
1 “Software issues” include technical questions that are directly related to the Omega Desktop software.
“Software issues” do not include training-related questions.
2 “Software errors” include software problems that impede the successful completion of an Omega
Desktop routine (i.e. software bug and/or error message).
3 “Configuration Issues” include questions that are directly related to the Omega configuration files.
“Configuration issues” do not include training-related questions.
4 “Configuration Errors” include any mis-configuration of the original Omega Desktop product that would
impede the successful completion of an Omega Desktop routine (i.e. error message).
36 | Page
“Configuration Files” include the following:
1. The Omega Import Wizard’s profile configuration
a. SQL Statement
b. Composite fields
c. OmegaGIS fields
d. Lookup fields
e. Data cleaning
f. Spatial query
g. Address locators
h. Standardization fixes
i. Geocoding steps
j. Preferences
k. Output steps
2. The Omega Import Wizard job configuration (including scheduled task)
3. Crystal Reports
4. Saved Queries
5. GIS and/or other data
6. Map configuration (.mxd & .mxt)
7. Cyclical Reports
8. Threshold Alerts
Version 5.0
Current,
Version
2.08
12/2010
5/30/2012
Firehouse
RMS
Detroit Fire Department
13331 Lyndon St.,
Detroit, MI 48227
Lt. Orlando Watkins
Orlando@dfd.ci.detroit.mi.us
720,000 FireView
Desktop
FireView
Dashboard
Current,
Version 5.0
Current,
Version
2.08
9/24/2007
9/30/2012
Tiburon
FireRMS
Metro Cities Fire Authority
201 S. Anaheim Blvd., Suite 302
Anaheim, CA 92805
Gary Gionet, Operations
Manager
gary@metronetfire.com
1,108,000 FireView
Desktop
FireView
Server
Current
Version 5.0
FireView
Server,
Version
2.2.3.23
2/18/2010 Keystone
CAD
Report
Compare peak vs. non-peak response times Both Out of the box capability. Temporal Heat Index
charting and Reporting for comparing
response times 24x7
Identify whether the CAD is dispatching the wrong units Not
Available
Analyze the effect of changes in deployment Desktop Out of the box, Reliability Report and Station
Analysis
Software vendor will provide adequate training on the use
of both/each product
Both Package service, onsite training for both
applications provided.
Both Out of the box capability.
An easy-to-use interface Dashboard Please check our references