HomeMy WebLinkAbout5.758 Original Contract
t
..
5. 758
,..
I>
Computer System Services Agreement
This Computer System Services Agreement ("Agreement") is made and entered
into this 7th day of December, 2005 (the Effective Date") by and between
Reporting Systems, Inc. ("RSI") a Washington corporation having corporate
offices at 851 Coho Way, Suite #307, Bellingham, W A 98225, and the City of Port
Angeles ("City"), a Non-Charter, Code Municipal Corporation of the State of
Washington located at 321 E. 5th Street, Port Angeles, W A 98362.
Recitals
Whereas RSI provides a Web-based, remote-access Fire and Emergency Medical
Services Records Management System ("Fire/EMS RMS"); and
Whereas RSI has the capability and desires to provide these services to the
Agency; and
Whereas the City desires to obtain these services on behalf of it's subscriber fire
agencies from RSI solely in accordance with terms and conditions set forth in this
Agreement:
Now, Therefore, the parties hereto agree as follows:
1.0 DEFINITIONS
1.1 "Fire/EMS RMS" means the Fire and Emergency Medical Service Records
Management System provided by Reporting Systems, Inc.
1.2 "Website" means the internet website accessible at
"http/ /www.emergencyreporting.com.. that is maintained by Reporting
Systems, Inc. provides access to Fire/EMS RMS.
1.3 "Station" means each separate physical fire station. Each of these Stations
may have multiple computers with access to the Website.
1.4 "Fire Agencies" means all the Peninsula Communications subscriber fire
agencies and districts listed in Exhibit 1 - Fire Agency Listing.
1.5 "Emergency Response Data" means all information entered by the Fire
Agencies related to the Fire Agencies response to fire and emergency
medical incidents and as required by the current and future National Fire
1
..
..
Incident Reporting System (NFIRS) and National Highway Traffic Safety
Administration (NHTSA) standards.
2.0 SERVICES
2.1 RSI shall provide to the Fire Agencies access to the Fire/EMS RMS via the
Internet utilizing the current version of Microsoft Internet Explorer.
2.2 RSI shall collect emergency response data via a website accessible at
http/ /www.emergencyreporting.com or through a participating Fire
Agencies website, in which the Fire Agencies is an active member.
2.3 All data collected via the website above shall be compliant with FEMA's
National Fire Incident Reporting System (NFIRS) Release 5.0 or the
National Highway Traffic Safety Administration (NHTSA) Release 2.0
Federal Department of Transportation's Uniform Pre-Hospital Emergency
Medical (EMS) Data Conference.
2.4 RSI shall provide ongoing updates, changes, and bug fixes, at no
additional charge, to remain compliant with NFIRS and NHTSA
standards and to remain operational with new releases of Internet
Explorer and other software necessary for the operation of Fire/EMS
RMS.
2.5 RSI shall upload Via the Internet, transfer via electronic media, or
otherwise transmit appropriate NFIRS and/ or NHST A data to the
appropriate state office as necessary to meet the individual Fire Agencies
reporting requirements.
2.6 RSI shall export the Fire Agencies data to the Fire Agencies on electronic
media four times per year.
2.7 RSI shall provide to the Fire Agencies designated personnel a train-the-
trainer course in the proper use of the Fire/EMS RMS and the website, to
include all aspects of the program.
2.8 RSI shall ensure appropriate security and privacy of all data transmitted
to the website in compliance with HIP AA regulations and all other
applicable federal, state and/ or local rules, regulations and/ or laws.
2.9 RSI shall maintain the Website and store the Fire Agencies data at the
Bellingham Fibercloud Data Center. If RSI utilizes another data center in
2
the future, it shall meet or exceed the accessibility, reliability, and security
standards of the Fibercloud Data Center.
2.10 RSI shall provide the Website to be accessible by current browser
technology (Internet Explorer 5.5) as standardized by the W3C (World
Wide Web Consortium). In the event that non-standard browsers must be
supported, additional time and funding may need to be negotiated
separately from this Agreement.
2.11 RSI shall provide at least daily data backups to guard against data loss in
the event of catastrophic system failure.
2.12 RSI shall maintain all data submitted on the Website for a period of eight
years (96 months) from the time of submission by the Fire Agencies. Data
older than eight years shall be archived and removed from the servers, but
may be reloaded for a nominal fee if the data is needed.
2.13 RSI shall begin these services within thirty days of execution on this
Agreement.
3.0 FUTURE SERVICES AND MODIFICATIONS
3.1 RSI shall make available to the Fire Agencies the ability to download the
Fire Agencies specific reports from the Website to the Fire Agencies
computer upon re-release of the reporting program.
3.2 RSI shall make available to the Fire Agencies the ability to track and view
reports for the individual Fire Agency's personnel hours on incidents,
training, etc. and points received during incidents, training, etc., and shall
become part of the standard system at no additional cost.
3.3 RSI shall make available to the Fire Agencies the training classes/codes
submitted by the Fire Agencies. These classes/ codes will display in the
training section as available training and shall be available to the regional
capabilities. These classes/codes can only be modified by RSI after a
designated Fire Agencies person approves the modifications/ changes and
will not populate all other Fire Agencies databases within the regional
capabilities.
3.4 RSI shall convert the Fire Agencies existing Fire/EMS records from the
records current format in the Fire Agencies system to the Fire/EMS RMS
format and import the records into the Fire/EMS RMS for a fee of $0.07 to
3
$0.10 per record, depending on the total number of records to be
converted, and depending if the Fire Agency orders the work.
3.5 Support services shall be provided by RSI to individual Fire Agencies. RSI will
provide telephone and/or Internet based technical support. RSI technical support
shall be limited to inquiries regarding the records management system and shall
NOT cover hardware or operating system problems including, but not limited to,
local area networks, firewall issues, or modems, etc.
4.0 SERVICE AVAILABILITY COMMITMENT
4.1 RSI warrants that the Fire/EMS RMS shall be operational and available
for access by the Fire Agencies 99% of the time during any given month.
4.2 RSI shall not be responsible for Service Interruptions for reasons outside
RSI's and/ or the Bellingham Fibercloud Data Center's reasonable control
such as failures of the Fire Agencies ISP or failure of the Internet.
4.3 Service suspensions due to scheduled system maintenance or upgrades
shall not be considered a Service Interruption so long as RSI has notified
the Fire Agencies of such suspension at least twenty-four hours in
advance.
4.4 When the Fire Agencies notices a Service Interruption or believes there
has been a service interruption, the Fire Agencies shall notify RSI of such
interruption bye-mail or in writing within five working days of first
notice. Failure to comply with this requirement will forfeit the Fire
Agency's right to a remedy for the Service Interruption.
4.5 If a- Service Interruption occurs despite the fact that the Fire Agencies
fulfills all of its obligations under this Agreement, the Fire Agencies shall
have the following remedy: RSI will provide a pro-rata credit on the
Agency's fee for the month in which the Service Interruption occurred.
The pro-rata credit shall be calculated by multiplying the Service
Interruption percentage by the Agency's total monthly fee for the month
in which the Service Interruption occurred. This credit will be applied
against the next invoice from RSI. Furthermore, if the Fire Agencies
experiences a Service Interruption within three consecutive months, the
Agency has the option to terminate the Agreement.
4
.
5.0 CITY RESPONSIBILITIES
5.1 The Fire Agencies shall maintain an active user list of accounts that are
authorized to access the Website.
5.2 The City shall pay all valid invoices in a timely manner.
5.3 The individual Fire Agencies shall provide an active Internet Service
Provider (ISP) to access the Website. Such ISP charges are not included in
this Agreement. ISP failures are not the responsibility of RSI.
5.4 The Fire Agencies shall enter emergency response data into the Website
per instructions included in the training provided by RSI.
6.0 FEES AND PAYMENTS
6.1 The billing cycle shall occur fifteen days prior to next month's service, and
payments are to be made by the City on a net 30 days basis. Yearly or
quarterly payments may be made at the City's option. If yearly or
quarterly payment options are selected, the billing cycle shall occur fifteen
days prior to the next year or quarter's service, and are to be made by the
City on a net 30 days basis.
6.2 The fees shall remain the same for the term of this Agreement, The fee
agreed upon by RSI and the City is $99.00 per month, per Reporting
Station, per Fire Agency, except for a yearly adjustment based on the
"West Coast-Consumer Price Index" up to, but not to exceed 5%. For the
purposes of this contract the City shall be responsible for all fees
associated with providing the above-described services to each Fire
Agency identified in Exhibit 1 - Fire Agency Listing.
6.3 In the event that a Fire Agency adds a station or changes the location of a
station during the initial term of this Agreement, the fee for the new
station shall be the same as the fee for the existing station(s).
6.4 In the event that a Fire Agency reduces the number of stations, the fee for
that station(s) shall be eliminated.
6.5 The fees may be renegotiated upon renewal of this Agreement. RSI must
notify the City of any changes in the fees at least forty-five (45) days prior
to renewal. In no event will the fees exceed the standard, advertised fees
RSI charges for equivalent services at the time of renewal.
5
6.6 All amounts payable hereunder shall be payable in United States funds
without deductions for taxes or assessments.
6.7 The City shall be responsible for paying sale, use, excise, value-added, or
other tax or governmental charges impose on the use of the services
provided for herein.
7.0 DATA OWNERSHIP AND CONFIDENTIALITY
7.1 All data transmitted to the website shall remain the property of the Fire
Agencies. Retransmission of this data to the State of Washington and
FEMA is authorized. Modifying, deleting or other modifications of
submitted data by RSI is prohibited. Scientific research that is based on
broad data trends is authorized, but no Fire Agencies specific data must
be visible to any third parties.
7.2 Each party agrees to keep confidential information disclosed to it by the
other party in accordance herewith, and to protect the confidentiality
thereof in the same manner it protects the confidentiality of similar
information and data of its own (at all times exercising at least a
reasonable degree of care in the protection of confidential information);
provided, however, that neither party shall have any such obligations
with respect to use of disclosure to other parties of this Agreement of such
confidential information as can be established to: (a) have been known
publicly; (b) have been known generally in the industry before
communication by the disclosing party to the recipient; (c) have become
known publicly, without the fault on the part of the recipient, subsequent
to disclosure by the disclosing party; (d) have been known otherwise by
the recipient before communication by the disclosing party; or (e) have
been received by the recipient without any obligation of confidentiality
from a source, other than the disclosing party, lawfully having possession
of such information. Notwithstanding the above, the parties agree to keep
confidential all confidential information except as legally required under
Washington State law or as otherwise required under applicable statute.
7.3 The parties obligations under this Article 7 will survive the termination of
this agreement.
8.0 TERM
8.1 The term of this Agreement is the period from the date of the last
signature through December 31, 2008.
6
8.2 At the end of the initial term and any subsequent terms, this Agreement
shall be assumed renewed by the City and RSI, unless written notice to the
City and/ or RSI is sent at least thirty days prior to the end of each term.
9.0 NON-ASSIGNABILITY
Neither Party may assign their rights or obligations under this Agreement
without the prior written consent of the other Party.
10.0 DEFAULT AND TERMINATION
10.1 This Agreement may be terminated by the non-defaulting party if any of
the following events of default occur: (a) if either party materially fails to
perform or comply with this Agreement or any provision hereof; (b) if
either party fails to strictly comply with the provisions of Section 7 - Data
Ownership and Confidentiality or makes an assignment in violation of
Section 9 - Non-assignability; (c) if either becomes insolvent or admits in
writing its inability to pay its debts as they mature, or makes an
assignment for the benefit of creditors; (d) if a petition under any foreign
state, or the United States bankruptcy act, receivership statute or the like,
as they now exist, or as they may be amended, is filed by a party; or (e) if
such a petition is filed by any third party, or an application for a receiver
is made by anyone and such petition or application is not resolved
favorably within ninety days.
10.2 Termination due to a material breach of Section 7 - Data Ownership and
Confidentiality shall be effective upon notice. In all other cases,
termination shall be effective thirty days after notification of termination
to the defaulting party if the defaults have not been cured within such
thirty-day period.
10.3 Within thirty days of termination, RSI shall issue a pro-rata refund to the
City. The pro-rata refund shall be calculated by multiplying the
annualized fee by the percentage of time remaining in the prepaid service
period.
10.4 Any waiver by either party of any default or breach hereunder shall not
constitute a waiver of any provision of this Agreement or of any
subsequent default or breach of the same or different kind.
7
..
11.0 COPYRIGHT AND INDEMNIFICATION
11.1 The City recognizes that the RSI website is protected under u.s. copyright
and trademark law, international conventions and other applicable law.
The City agrees not to license, sell, publish or create any kind of derivative
system using the RSI website as a source of information.
11.2 RSI shall indemnify, hold harmless and defend the City and Fire Agencies
against any claim that use of the RSI Website, the Fire/EMS RMS, or any
other RSI product infringes third party propriety rights and shall
indemnify the City and member Fire Agencies against any loss, damage,
or expense arising from such claim, provided that the City and member
Fire Agencies provides prompt notice to RSI of any such claim and further
provided that RSI shall have sole control of the defense of any such action
and all negotiations for its settlement or compromise.
12.0 NOTICES
All notices, authorizations, and requests in connection with this
Agreement will be deemed given (a) five days after being deposited in the
U.s. mail postage prepaid, certified or registered, return receipt requested;
or (b) one day after being sent by overnight courier, charges prepaid, with
a confirming FAX.
13.0 GOVERNING LAW AND VENUE
The validity, interpretation, construction, and performance of this
Agreement will be governed by the laws of the State of Washington. Sole
and exclusive jurisdiction for any action or proceeding arising out of or
related to this Agreement will be in Clallam County Superior Court.
14.0 SEVERABILITY
14.1 If a court of competent jurisdiction holds any part, term, or provision of
this Agreement to be illegal or invalid in whole or in part, the validity of
the remaining provisions shall not be affected, and the parties' rights and
obligations shall be construed and enforced as if the Agreement did not
contain the particular provision held to be invalid.
14.2 If any provision of this Agreement is in direct conflict with any state
and/ or federal statutory provision, that provision which may conflict
shall be deemed inoperative and null and void insofar as it may conflict
and shall be deemed modified to conform to such statutory provision(s).
14.3 Should the City or RSI determine that the severed portions substantially
alter this Agreement so that the original intent and purpose of the
8
.'
Agreement no longer exist, the City or RSI may, in its sole discretion,
terminate this Agreement. Within thirty (30) days of such termination,
RSI shall issue a pro-rata refund to the City. The pro-rata refund shall be
calculated by multiplying the annualized fee by the percentage of time
remaining in the prepaid service period. .
15.0 CAPTIONS AND HEADINGS
All captions and headings in this Agreement are for purposes of
convenience only and shall not affect the construction or interpretation of
any of its provisions.
16.0 ENTIRE AGREEMENT
This Agreement and its Exhibits contain the entire understanding and
agreement between the parties respecting the subject matter hereof. This
Agreement may not be supplemented, modified, amended, released, or
discharged except by an instrument in writing signed by each party's duly
authorized representative. This Agreement may not be modified by
acceptance of a purchase order with conflicting terms; in such an event the
terms of this Agreement shall control.
IN WITNESS WHEREOF the parties have executed this Agreement by their duly
authorized representatives as of the day and year first above written.
City of Port Angeles
Reporting Systems, Inc.
By:
71/-auL-~. 7?1.f7<~'
_By:
4eu 4/--
(Authorized Signatory)
Name
Mark E. Madsen
Name:
OAve 1JnhvY15
Pie l?S/Oe'1Vi
O~?(,.7/tW1eyZ I G, 2 Oos
Title:
City Manager
Title
Date: j) tvc.-t!.Hf, 6-~ ~ ZOtI'Jr-- Date:
Address for Notice:
Address for Notice:
City of Port Angeles
102 E. 5th Street
Port Angeles, W A 98362
Reporting Systems, Inc.
851 Coho Way, Suite #307
Bellingham, W A 98225
9
Exhibit 1
Fire Agency Listing
CityfDistrict
City of Port Angeles
Clallam County Fire District # 2
Clallam County Fire District # 3
Clallam County Fire District # 4
Clallam County Fire District # 5
Number of
Stations
1
1
2
1
1
10
Reporting
Stations
1
1
2
1
1
. .
..
Exhibit 2
EMERGENCY
REPORTING™
FIRE I EMS RECORDS MANAGEMENT
Emergency Reporting; 851 Coho Way, SUite #307, Bellingham, WA 98225
Telephone: 360.647.6003, Toll free: 866.773.7678; Fax: 360.527.0401
Emall: sales@emergencyreporting.com; Webslte: www.emergencyreportlng.com
Account Information
Agency Name: City of Port Angeles Peninsula Communications EMS 10#: FDID#:
Mail Address: P.O. Box 1150 City: Port Angeles
State: WA Zip Code: 98362 Telephone: 360-417-4911 Fax:
Name!Tltle of primary contact: Naomi Riggins, PenCom Manager
Name/TItle of other contact: Keith Bogues, Port Angeles Fire Department
Telephone number other than above: 360-417-4652 Best time to call:
Account established through: John Hall
Sales representative: Kleve Other - be specific:
(~g
ORDER
FORM
INTERNAL USE ONLY
Order #: ERS-298
Date Received:
Rep: Kleve
Total number of stations: 6
D EMS Package
D NFIRS Only D Fire Package
Package Ordered
NFIRS Only
$52 per month / per station
. NFIRS 5.0 forms
. Reports
. Administration
. Personnel Management
Fire Package
$90 per month / per station
. NFIRS 5.0 Forms
. Fire Inspections
. Occupancy Prefire Plans
. Apparatus Maintenance
. Equipment Maintenance
. Hydrant Maintenance
. Training Records
. Library Module
. Calendar Module
. Daily Roster
. Reports
. Administration
. Personnel Management
EMS Package
$90 per month / per
station
. EMS Forms
. Pre-hospital PCR
. Training records
. Apparatus Maintenance
. Equipment Maintenance
. Library Module
. Calendar Module
. Daily Roster
. Reports
. Administration
. Personnel Management
~ Full ERS Package
Full ERS Package
$129 per month / per
station
. NFIRS 5.0 forms
. All EMS forms
. Occupancy Prefire Plans
. Fire Inspections
. Apparatus Maintenance
. EqUipment Maintenance
. Hydrant Maintenance
. Training Records
. Library Module
. Calendar Module
. Daily Roster
. Reports
. Administration
. Personnel Management
X Rate $99.00 = Monthly Fee $594.00
Monthly Fee Number of stations 6
Start Date 1/1/2006
CAD Link & Interface Fee $12,500.00
Misc. Fee(s) $5,000.00
11
Startup Fee $3,000.00
.' .
Billing Information
Check One: D Monthly D Quarterly ~ Yearly
CAD link and CAD Interface cost is $12,500. Miscellaneous cost is for a link to your medical billing company
$5,000. Both have 50% due when project started and balance due when completed and 20% annual maintenance
fee after the first year. A single CAD link fee will be charged at the above rate.
Billing Address
(If different than above):
City:
State:
Zip:
Approval
Title:
Date:
12
.
.
Individual Fire Agency Account Information
Fire Agency Name: Port Angeles Fire Department
Mall Address: 102 E. 5th St.
State: W A Zip Code: 98362 Telephone:
Name{ntle of primary contact: Keith Bogues, Training Officer
Name{fltle of other contact: Ken Dubuc, Fire Marshal
Telephone number other than above: 360-417-4653
Account established through: Keith Bogues
Sales representative: Kleve
EMS ID#:
FDID#: 05M03
City: Port Angeles
360-417-4652 Fax: 360-417-4659
Best time to call:
Other - be specific:
Total number of stations within department: 1
Individual Fire Agency Account Information
Fire Agency Name: Clallam County Fire District #2
Mail Address: P.O. Box 1391
State: W A Zip Code: 98362
Name[Title of primary contact: Jon Bugher, Fire Chief
Name[Title of other contact: Joan Noal, District Secretary
Telephone number other than above:
Account established through: Keith Bogues
Sales representative: Kleve
EMS ID#:
City: Port Angeles
Telephone: 360-452-7725 Fax: 360-452-9235
FDID#: 05D02
Best time to call:
Other - be specific:
Total number of stations within department: 1
Individual Fire Agency Account Information
Fire Agency Name: Clallam County Fire District #3
Mail Address: 323 North Fifth Ave.
State:
Zip Code: 98382
EMS ID#:
City: Sequim
T I h 360-683-4242
e ep one: 802
ext.
FDID#: 05D03
WA
Fax: 360-683-6834
13
. .'
.
NamefTltle of primary contact: Tony Hudson, Captain
Name/Title of other contact: Ben Andrews, Assistant Chief
Telephone number other than above: 360-683-4242 ext.117
Account established through: Keith Bogues
Sales representative: Kleve Other - be specific:
Best time to call:
Total number of stations within department: 2
Individual Fire Agency Account Information
Fire Agency Name: Clallam County Fire District #4
Mall Address: P.O. Box 106
State: W A Zip Code: 98343
Name/Tltle of primary contact: Dave Chastain, Fire Chief
Name/Title of other contact: Ann Chastain, District Secretary
Telephone number other than above:
Account established through: Keith Bogues
Sales representative: Kleve
EMS 10#:
CIty: Joyce
Telephone: 360-928-3132
FDIO#: 05D04
Fax: 360-928-9604
Best time to call:
Other - be specifiC:
Total number of stations within department: 1
Individual Fire Agency Account Information
Fire Agency Name: Clallam County Fire District #5 EMS 10#: FDIO#: 05D05
Mail Address: P.O. Box 530 City: Clallam Bay
State: WA Zip Code: 98326 Telephone: 360-963-2371 Fax:
Name/Title of primary contact: Gene Laes, Fire Chief
Name/Title of other contact:
Telephone number other than above: 360-963-2329 Best time to call:
Account established through: Keith Bogues
Sales representative: Kleve Other~- be specific:
Total number of stations within department: 1
14
~ j/
.
.
.
@ 2004 Reporting Systems, Inc. See Terms & Conditions Reverse - Or - Computer System Services Agreement
15
O. '758 (,;1-
-'..
f>
AGREEMENT V.2.3
Computer System Services Agreement -
CAD Interface Software Program, CAD Link & EMS Data Link
for the City of Port Angeles
This Computer System Services Agreement ("Agreement") is made and entered into this ih day
of December, 2005 the ("Effective Date") by and between Reporting Systems, Inc. ("RSI") a
Washington State "s" corporation, doing business as Emergency Reporting, located at 851 Coho
Way, Suite #307, Bellingham, WA 98225, and the City of Port Angeles ("City"), a Non-Charter,
Code Municipal Corporation ofthe State of Washington located at 321 E. 5th Street, Port
Angeles, W A 98362.
1.0 FUTURE SERVICES AND MODIFICATIONS
1.1 CAD Interface Software Program. Upon execution of this Agreement, RSI shall begin
computer system services defined as a custom interface to reside on the City's network in
order to pull data from the City's CAD, enabling the CAD Link (see 1.2) to be effective.
The custom interface is defined in Exhibit 1 - CAD Interface Program. The cost of this
interface shall not exceed Five thousand dollars ($5,000).
1.2 CAD Link. Upon execution of this Agreement, RSI shall begin computer system
services defined in Exhibit 2 - CAD Link to Records Management System. The cost of
this CAD Link shall not exceed Seven thousand five hundred dollars ($7,500).
1.3 EMS Billing Link. Upon execution of this Agreement, RSI shall begin computer system
services defined in Exhibit 3 - EMS Billing Link to City's Medical Billing Company.
The services are estimated to take 60 business days and are contingent on the medical
billing company's ability and cooperation to work with RSI. The cost ofthis interface
shall not exceed five thousand dollars ($5,000).
2.0 CITY RESPONSIBILITIES
2.1 The City shall pay all valid invoices in a timely manner.
2.2 The City shall provide an Internet connection to the Emergency Reporting system for a
CAD interface. Internet Service Provider (ISP) charges, if necessary, are not included in
this Agreement. ISP failures are not the responsibility ofRSI and will not be considered
"down-time" of the system.
2.3 City agrees to cooperate with RSI to design a CAD interface software program to reside
on the City's server in a manner agreeable to all parties, provided the work fits within the
scope of the RSI work outlined in the Exhibit.
2.4 City agrees to cooperate with RSI and the appropriate dispatch vendors to design a CAD
link and transmission method that is agreeable to all parties.
Emergency Reporting
City of Port Angeles Peninsula Communications
1
,
.., ,
2.5 City agrees to cooperate with RSI and the medical billing company to design an
electronic interface for the secure submittal of patient related medical records as required
for medical billing purposes.
3.0 FEES AND PAYMENTS
3.1 All amounts payable hereunder shall be payable in United States funds without
deductions for taxes or assessments. A sum of 50% is due at time of signing and the
balance is due upon completion by RSI and activation to City's live account. City will
use reasonable cooperation to bring the finished product live. If the City elects to delay
the electronic interface activation dates for more than 30 days following the time the
work is declared complete by both parties, then the final payment is due immediately.
3.2 The City shall be responsible for paying sales, use, excise, value-added, or other tax or
governmental charges impose on the use of the services provided for herein.
3.3 If City decides to cancel the project prior to completion all funds paid will be considered
to be payment in full and no refund will be given.
\
3.4
This Agreement applies to RSI only. Other third parties (dispatch vendors, medical
billing companies, etc.) may charge additional fees, and these fees are beyond the control
of RSI.
4.0 NON-ASSIGNABILITY
4.1 Neither Party may assign their rights or obligations under this Agreement without the
prior written consent of the other Party.
5.0 DEFAULT AND TERMINATION
5.1 This Agreement may be terminated by the non-defaulting party if any of the following
events of default occur: (a) if either party materially fails to perform or comply with this
Agreement or any provision hereof (b) if a petition under any foreign state, or the United
States bankruptcy act, receivership statute or the like, as they now exist, or as they may
be amended, is filed by a party; or (c) if such a petition is filed by any third party, or an
application for a receiver is made by anyone and such petition or application is not
resolved favorably within ninety days.
5.2 In all cases, termination shall be effective thirty days after notification oftermination to
the defaulting party if the defaults have not been cured within such thirty-day period.
5.3 Any waiver by either party of any default or breach hereunder shall not constitute a
waiver of any provision of this Agreement or of any subsequent default or breach of the
same or different kind.
Emergency Reportmg
City of Port Angeles
2
6.0
6.1
7.0
7.1
7.1.1
7.1.2
7.1.3
7.1.3.1
7.1.3.2
7.1.3.3
7.1.3.4
7.1.3.5
7.1.3.6
NOTICES
All notices, authorizations, and requests in connection with this Agreement will be
deemed given (a) five days after being deposited in the U.S. mail postage prepaid,
certified or registered, return receipt requested; or (b) one day after being sent by
overnight courier, charges prepaid, with a confirming FAX.
WARRANTY OF PERFORMANCE
Service Level Definitions
"Performance Problem" refers to an occurrence where mission critical components of the
system are accessible, but are not performing at 100% of normal operation. Examples of
a performance problem would be if the EMS Export Link were down.
"Service Interruption" refers to any unscheduled network event that results in the user
being unable to connect to Emergency Reporting servers for a period of 30 minutes or
more.
"System Notice" refers to any of the following methods of communications between RSI
and the City:
A electronic Message on the "Daybook" portion of the system
A electronic message on the login portion of the main screen
emergencyreporting.com<http://www.emergencyreporting.com/
A electronic mail (e-mail) message containing a notice of the event
A "pop-up" notice to users currently logged onto the system
A letter delivered by the US Postal Service
A written notice delivered by FAX
7.1.4 "Unscheduled Event" means any service interruption, in which the City was not provided
a minimum of 24-hours prior notification via a System Notice.
7.1.5 "Outside Factors" refers to factors outside RSI's control. Broad Internet problems, ISP
failures, power failures, CAD vendor issues, etc. are not the responsibility ofRSI and do
not constitute an "Unscheduled Event" or "Performance Problem.
7.1.6 "System Maintenance" refers to scheduled system maintenance performed on RSI's
systems.
7.1.7 RSI shall not be responsible for service interruptions caused by outside factors beyond
the control ofRSI.
7.2 RSI warrants that the CAD Interface Software Program, the CAD Link and the EMS
Billing Link shall be operational and available for use by the City 99% of the time during
any given month.
City of Port Angeles
Emergency Reporting
3
7.3 Service interruptions due to system maintenance or upgrades shall not be considered a
Service Interruption so long as RSI has notified the City of such suspension at least
twenty-four hours in advance via a system notice.
7.4 In the event of a system failure, the City will follow the failure procedures as provided by
RSI in the technical documentation. These procedures outline troubleshooting tasks,
restart procedures and RSI technical assistance contact information in the event the
system fails. Technical assistance is available 24/7 for emergency support. Non-critical
assistance is available during normal business hours, Monday - Friday 8:00am to 5:00
pm PST. Failure to comply with this requirement will forfeit the City's right to a remedy
for the Service Interruption.
7.5 In the event of five (5) or more service interruptions or a performance problem in excess
of five (5) days in length within any calendar month, the City shall have the following
remedy: RSI will provide a pro-rata credit on the City's fee equal to 1I30th ofthe monthly
fee for each calendar day the system was available. Any credit(s) accrued during a month
will be applied to the following month's invoice for services.
In no case will the out of service credit exceed the monthly fee paid by the City to RSI.
7.6 RSI shall provide ongoing updates, changes, and fixes, at no additional charge, to remain
operational with new improved operating systems and other software necessary for the
operation of CAD Interface Software Program, the CAD Link and the EMS Billing Link,
as identified in Exhibits 1,2, and 3.
8.0 GOVERNING LAW AND VENUE
8.1 The laws ofthe State of Washington will govern the validity, interpretation, construction,
and performance of this Agreement. Sole and exclusive jurisdiction for any action or
proceeding arising out of or related to this Agreement will be in Clallam County Superior
Court, or the United States District Court for the Western District of Washington State.
9.0 SEVERABILITY
9.1 If a court of competent jurisdiction holds any part, term, or provision of this Agreement
to be illegal or invalid in whole or in part, the validity of the remaining provisions shall
not be affected, and the parties' rights and obligations shall be construed and enforced as
if the Agreement did not contain the particular provision held to be invalid.
9.2 If any provision ofthis Agreement is in direct conflict with any state and/or federal
statutory provision, that provision which may conflict shall be deemed inoperative and
null and void insofar as it may conflict and shall be deemed modified to conform to such
statutory provision(s).
9.3 Should the City or RSI determine that the severed portions substantially alter this
Agreement so that the original intent and purpose of the Agreement no longer exist, the
City or RSI may, in its sole discretion, terminate this Agreement. Within thirty (30) days
Emergency Reporting
City of Port Angeles
4
of such termination, RSI shall issue a pro-rata refund to the City. The pro-rata refund is
determined by multiplying the annualized fee by the percentage of time remaining in the
prepaid service period.
10.0 TECHNICAL SUPPORT AND UPGRADES
10.1 Support services shall be provided by RSI to City in order to maintain the CAD interface.
RSI will not provide support to City in those instances where City has not elected to
purchase RSI Fire / EMS records management services. RSI will provide telephone
and/or Internet based technical support. RSI technical support shall be limited to inquiries
regarding the CAD interface to the records management system and shall not cover
hardware or operating system problems including, but not limited to, local area networks,
firewall issues, or modems.
10.2 City agrees to pay a yearly maintenance fee of20% ofthe CAD Interface Software and
the CAD Link, in order to cover the technical labor costs directly associated with support,
improvements, and upgrades.
11.0 LIMITATION OF LIABILITY
11.1 RSI shall not be liable for any damages of any type, including but not limited to, lost
revenue, loss of expected benefits or other incidental or consequential damages arising
out of the use or inability to use the CAD interface software, whether arising out of
contract, negligence, strict tort, or under any warranty, or otherwise, even if City has been
advised of the possibility of such damages or for any other claim by any other party. The
City acknowledges there are circumstances in which the CAD provider may prevent or
otherwise prohibit the CAD interface or CAD link from operating properly. RSI's
liability for damages in no event shall exceed the fees paid for the electronic interfaces.
12.0 CAPTIONS AND HEADINGS
12.1 All captions and headings in this Agreement are for purposes of convenience only and
shall not affect the construction or interpretation of any of its provisions.
13.0 ENTIRE AGREEMENT
13.1 This Agreement and its Exhibits contain the entire understanding and agreement between
the parties respecting the subject matter hereof. This Agreement may not be
supplemented, modified, amended, released, or discharged except by an instrument in
writing signed by each party's duly authorized representative. This Agreement may not
be modified by acceptance of a purchase order with conflicting terms; in such an event
the terms of this Agreement shall control.
Emergency Reporting
City of Port Angeles
5
IN WITNESS WHEREOF the parties have executed this Agreement by their duly authorized
representatives as of the day and year first above written.
City of Port Angeles
Reporting Systems, Inc.
A(2" /Y~
...
By:
By: ~f.">>l-t.""')
Name Mark E. Madsen
Name: DA-ve:-- jC)OArYJ.5
Title: Ci ty Manager
Title: I?I,,<e"5/&/i?/vr
Date: /~C:t?mt3t-re It, '1--60~
Date: p~~ ~ ~e:x:::e;-
.
Address for Notice:
City of Port Angeles
321 E. 5th Street
Port Angeles, W A 98362
Address for Notice:
Reporting Systems, Inc.
851 Coho Way, Suite #307
Bellingham, W A 98225
Emergency Reporting
City of Port Angeles
6
Exhibit 1 - CAD Interface Software
The Emergency Reporting is providing the City with a custom software interface to operate
between the CAD vendor and the Emergency Reporting CAD link; the CAD link interfaces with
the records management system. The Interface Software has two primary services:
1. Extracts 911 CAD data and imports it into a local database residing on the City's
network. The CAD data is then translated and converted as needed.
2. Transmits required converted CAD data via the CAD Link to the Emergency Reporting
data servers over the internet. This service requires an Internet connection to work. It can
operate over the native Internet (unencrypted) or VPN (encrypted). It's designed to be
redundant and will operate with minimal maintenance and tweaking.
The interface software is currently in development. The completion date of the software is
expected to be on or before March 31, 2006. In order for the deployment to be successful, the
following is required:
1. The Interface Software must be installed on Windows 2003 Server or the Windows XP
operating system.
2. The Interface Software requires the ability to perform SQL queries on a CAD database or
a CAD database mirror.
3. The CAD database must be ODBC compliant.
4. The private leased circuits, such as T1lines or frame relay, are not supported for
transmission of data to ERS.
Graphical summary of CAD interface process:
CAD Database
Main CAD
DB -or- DB
MUTor
ERS CAD Interface
Program
Queries any ODBC
compliant CAD DB and
extracts needed data.
Main ERS
Servers
Data is transmitted via
web services tQ ERS. In
the event the remote
$l!lrver is unreachable
then the data is cached
unlillhe connection is
restored.
ERS CAD Interface program reSides on a
local computer In the Dispatch Center or
on a Fire Department machine that can
see the database. Dala is imported Inlo a
local DB.
Emergency Reporting
City of Port Angeles
7
Exhibit 2 - CAD Link to Records Management System
Dispatch Integration with the
Emergency Reporting System
Technical Manual - July 2005
EMERGENCY
REPORTING'"
FIRE I EMS RECORDS MANAGEMENT
Emergency Reportmg
CIty of Port Angeles
8
Table of Contents
Overview....................................................................................................................... ............ 10
Definitions & Acronyms......................... ............... ................................................... .................. 11
Testing Process........................................................................................................................ 12
Service Description................................................................................... ................................13
Submission Process................ ................................................. ...................... .......................... 14
Record Components... ............................ ......................... ................. ........................................15
Dispatch Header. .............................. ............. ....................................................................... 17
ApparatusEvent................................................................................................................. .... 18
IncidentNarrative......................... ......................................................... ......................... ........18
IncidentLocation .................................................................................................................... 19
Peoplelnvolved................................................................................................................ ......20
I ncidentEvent ........................................................................................................................ 22
Failure Procedu re ..................................................................................................................... 23
Appendix...................................................................................................................... .............24
Emergency Reportmg
CIty of Port Angeles
9
Overview
This document describes the web services method of importing 911 data into the
Emergency Reporting System (ERS). The intent is to provide a seamless integration that
allows dispatch information to be passed into the ERS system in a real-time manor, while
maintaining acceptable security of dispatch data.
Technical coordination between the dispatch center and Emergency Reporting is vital.
The testing process outlined on page 3 specifically outlines the steps required to bring a
CAD link live.
Emergency Reporting
Port Angeles Agreement
10
Acronyms & Definitions
Agency: The Fire / EMS Agency(ies) that wish to receive CAD 911 data from their
CAD center( s) to Emergency Reporting.
CAD: Computer Aided Dispatch
CAD Center: The 911 dispatch center that process 911 calls and dispatches the
appropriate agency(s). The CAD center will generally be responsible for transmitting
this 911 information to Emergency Reporting.
CAD Vendor: The company that sells and licenses some kind of CAD software.
ERS: Emergency Reporting System.
NDA: Non-disclosure agreement.
XSD: XML Schema Definition.
Emergency Reporting
Port Angeles Agreement
11
'.
Testing Process
In order to build and test the CAD link properly, the following steps must be followed:
Action Responsible Expected
Party Time
1. Agency makes request to CAD center to contact
Emergency Reporting and identify costs and Agency 1 week
timelines.
2. CAD Center contacts Emergency Reporting and has
an initial technical meeting to identify required
actions and timeline. It is the responsibility of the CAD Center 1 week
CAD Center to bring the CAD Vendor into the
meeting if necessary.
3. Emergency Reporting provides NDAs to the CAD ERS 1 - 2 weeks
Vendor if necessary.
4. Emergency Reporting provides necessary technical ERS 1 week
documentation (this document) to various parties.
5. CAD Vendor and / or CAD Center write needed CAD Vendor
interface(s) to import data into ERS. Link is / CAD Center 8 weeks
pointed to a test account for development purposes.
6. Agency reviews data and import process and Agency 1 week
determines if link has been successfully built.
7. ERS reviews data and import progress and approves ERS 1 week
link when it is operating properly.
8. Link is reconfigured to point to the live account(s)
on ERS. Ongoing monitoring is initiated to ensure ERS 1 day
link remains live.
Total Time: 15 weeks*
* This timeframe is contingent on the CAD interface work, as the interface work
must be completed prior to the activation of the CAD link.
Emergency Reporting
Port Angeles Agreement
12
Service Description
The web services method for transmitting CAD data to ERS is ideally suited to transmit
data in real-time across the internet. The process is also well suited to operate over
foreign operating systems, such as from Unix based systems to Windows based servers
located on the Emergency Reporting side.
The figure below diagrams how this method works.
In short, the web services method "posts" web services data to an Emergency Reporting
server, using a specific format. When this data is received in the right format, and if the
remote computer is credentialed properly, the Emergency Reporting servers insert the
needed data into the database server. The entire process is real-time and secure.
Dispatch
Side
Firewall ~ YEnCrypted VPN Link~
~ across the Internet
/.
,
I
/ Web Server
/ (Optional, can come directly
I from the DB server)
/
/
,/
./
--
Database
Server
Web Services method of CAD data
submission to ERS.
Emergency Reporting
Port Angeles Agreement
.t
-,yC,
.::'<eX'",-"
ERS
Side
~ Firewall
~
Web
Server
Database
Server
13
Submission Process
Two methods are available for submitting data to ERS:
1. The All-at-Once method involves submitting a single record type, titled
ReportIncident, at the end of an incident.
The advantage ofthe All-at-Once method is that only one data packet is sent at the
end of the call. The disadvantage is that the call will not be generated on the ERS
side until this data has been sent. In other words, the call will not be sent until after
the incident is closed. If the incident is lengthy, the field personnel cannot begin
filling out the report until after the data has been sent.
2. The Piecemeal approach receives data when there is a status change on the CAD
side. This could be when an apparatus goes enroute, arrives on scene, etc. Each
change can trigger transmission of a small piece of data to ERS.
The advantage of the Piecemeal method is that as soon as a call has been created it
will appear in ERS. This means that a field crew can return to the station and begin
filling out the report while other units remain on scene. The disadvantage of this
method is that there can be additional bandwidth that can be taken up by the constant
stream of piecemeal data.
In most cases, customers prefer the Piecemeal approach.
Emergency Reporting
Port Angeles Agreement
14
Record Components
The chosen Submission Method dictates which components are involved for a web
services CAD linle For specific information for each component, refer to the following
pages.
For the All-in-One method, there are two components involved:
One (1) Dispatch Header
One (1) Action Type, titled ReportIncident. The ReportIncident type is designed to
be used as the single All-at-Once submission method. This record type contains all
data elements for the entire call rolled up into a single submission type.
For the Piecemeal method, there are six components involved:
One (1) Dispatch Header
Five (5) Action Types, listed below
1. ReportApparatusEvent - This event type should be sent when an apparatus status
changes, such as when a unit responds or arrives on scene.
2. ReportlncidentNarrative - This event type transmits dispatcher notes to ERS.
These dispatch notes are then listed as "read-only" on the ERS side, and are visible
from the narrative section of the report.
3. ReportlncidentLocation - This event type contains detailed information regarding
the location of the incident. This can include a physical address (123 Main St.) a
place name (Lake Shannon boat launch) or a GIS coordinate of some kind
(123.123450 North Latitude by 45.768760 West Longitude).
4. ReportPeoplelnvolved - This event type records the names and contact
information for people that are involved in the incident in some way. Examples
include Reporting Party, Patient, Witness, etc.
5. ReportlncidentEvent - This record type reports different time elements related to
the incident. If these times are not submitted ERS will reverse calculate the needed
times from the apparatus that responded to the call.
The standard for each record type, regardless of the submission method, is located at:
http://www.emergencyreporting.com!ers/webservices/ dispatch/Call Center. asmx
If needed, the XSD file for this link is located at:
http://www.emergencyreporting.com!ers/webservices/ dispatch/documentation! dispatch.x
sd
All data that is submitted to ERS is logged in the Submissions table. To view this table go
to:
http://www.emergencyreporting.com!ers/webservices/ submissions/
Unless otherwise noted, there is no minimum data length for CAD data submitted to
ERS. If a particular code is required it will be listed in the Data Dictionary column.
Emergency Reporting
Port Angeles Agreement
15
Whenever a number is entered that is less than the maximum field length, leading zeros
or spaces are not required.
Date / Time entries must be submitted in 24-hour format. Example: March 19,2003 at
3:00 PM should be sent as 2003/03/19 15:00:00.
Emergency Reporting
Port Angeles Agreement
16
DispatchHeader
Code Required? Data Dictionary / Notes
Acceptable codes
AgencyldentifierCode Yes Must be unique for each
agency in ERS.
DispatchlncidentNumber* Yes* Not required if OUID is
provided.
If provided from CAD this
number will be used; if not
Must be 7 digits or submitted ERS generates the
AgencylncidentNumber No next sequential number for the
less. calander year. The number will
reset to "1" for the first call for
this agency after January 1.
PrimaryStation No Must be 3 digits or
less.
Must be 3 digits,
and must use one
IncidentType No ofthe NFIRS
incident type codes
listed in Appendix
A.
U sed to assign a call to a
particular person for
AssignedTo No completion. A ERS assigned
user ID must be submitted;
contact ERS if this feature is
needed.
Not required if
SubmissionOUID* Yes* DispatchlncidentNumber is
provided.
* A Dispatch Header record type must be submitted any time data is submitted to ERS.
Either SubmissionGUID or DispacchlncidentNumber must be unique for the particular
call.
Emergency Reporting
Port Angeles Agreement
17
ApparatusEvent (Piecemeal)
Code Required? Data Dictionary / Notes
Acceptable codes
Apparatus Yes Must be 5 digits or less Must match the apparatus
codes in ERS.
Must be one of the
following:
Dispatch
Enroute
Alarm
Type Yes Arrived
Cancelled
InService
Clear
InQuarters
AtHospital
ClearedHospital
Must be submitted as a
DateTime Yes valid date / time
combination as described
on page 6.
If submitted, must
PersonIDs No correspond to ERS side
user ID's.
ResponseCode No Must be one of the values
listed in Appendix A.
IncidentN arrative (Piecemeal)
Code
Required?
Data Dictionary /
Acce table codes
Must be submitted as a
valid date / time
combination as described
on a e 6.
Notes
DateTime
Yes
NoteText
Yes
Any text, no limit
If submitted, NoteText
must be accompanied by a
DateTime ent .
Emergency Reporting
Port Angeles Agreement
18
Incident Location (Piecemeal)
Code Required? Data Dictionary / Notes
Acceptable codes
District No Reserved for future use;
not used at this time.
The zone the call occurs in.
Zone No Must match user defined
codes in ERS.
MapPage No
LocationTypeCode No See Appendix A for
code list.
AddressNumber No Must be 6 characters
or less.
Must be N, S, E, W,
S trretPrefix No NW, SW, SE, or NE
in all capitals.
StreetOrHighwayN ame No Must be 30 characters
or less.
StreetType No See Appendix A for
code list.
Must be N, S, E, W,
S treetSuffix No NW, SW, SE, or NE
in all capitals.
ApartmentSuiteNumber No
ConsolidatedAddressS tring No See note below
State No See Appendix A for
code list.
City No
ZipPlus4 No Can be 5 or 9 digits.
CrossStreetOrDirections No Must be 30 characters
or less.
Latitude No Can be any text value, with
decimals or without.
Longitude No Can be any text value, with
decimals or without.
For street addresses, ERS recommends address information be submitted in six (6)
separate fields:
1. Street Prefix
2. Address
3. Apartment # / Suite
4. Street Name
5. Street Type
6. Street Suffix
Emergency Reporting
Port Angeles Agreement
19
This format is known as the Segregated address format. In the event the dispatch
program doesn't store address information in this Segregated address format, the alternate
field titled "Consolidated Address String" can be used instead. This field is designed to
store the street address information as one single field.
Peoplelnvolved (Piecemeal)
Code Required? Data Dictionary / Notes
Acceptable codes
Free text entry describing
Involvement No the person's involvement
in the incident.
Must be one of the
NamePrefix No following: MR, MRS,
MS, DR, or REV in
all capitals.
FirstName No Must be 20 characters
or less.
Middlelnitial No Must be 1 character in
length.
LastN ame No Must be 30 characters
or less.
Must be one of the
NameSuffix No following: JR, SR, I,
II, II, IV, MD, or
DDS in all capitals.
Free text entry describing
BusinessName No the name of the business, if
applicable.
The telephone number of
ContactT elephone No the contact. Can be
submitted with or without
brackets or dashes.
AddressNumber No Must be 6 characters
or less.
Must be N, S, E, W,
StrretPrefix No NW, SW, SE, or NE
in all capitals.
StreetOrHighwayN ame No Free text entry describing
the street or highway name.
StreetType No See Appendix A for
code list.
Must be N, S, E, W,
StreetSuffix No NW, SW, SE, or NE
in all capitals.
ApartmentSuiteNumber No
State No See Appendix A for
Emergency Reporting
Port Angeles Agreement
20
code list.
City No
ZipPlus4 No Can be 5 or 9 digits.
ConsolidatedAddressString No See note above.
Emergency Reporting
Port Angeles Agreement
21
IncidentEvent (Piecemeal)
Code Required? Data Dictionary / Notes
Acceptable codes
Must be one of the
following:
IncidentOccurred If submitted, Type must be
Type Yes Alarm accompanied by a DateTime
CallReceived entry .
AgencyNotified
IncidentControlled
Must be submitted as a valid
DateTime Yes date / time combination as
described on page 6.
Emergency Reporting
Port Angeles Agreement
22
Failure Procedure
Follow the steps below if / when the CAD link has failed.
1. Confirm data is being sent to ERS.
a. Confirm calls are occurring in the CAD system.
b. Confirm network connectivity
i. From a command line, attempt to ping emergencyreporting.com. If
ping is successful connectivity is probably ok.
11. Confirm firewall is properly configured to allow outgoing traffic over
port 80 to emergencyreporting.com.
111. Confirm VPN link is operating as designed.
IV. Confirm transmitting computer / process is functioning properly and is
sending data as it is designed to do.
2. If data appears to be sending properly to ERS:
a. Confirm Emergency Reporting is up. Use a web browser and visit
www.emergnecyreporting.com. If page loads properly ERS is likely online.
b. Login to ERS and see if calls have been properly generated. If there has been
a longer delay then normal, then there is likely something wrong.
c. Review the submissions table to see if data has been properly submitted and
formatted to ERS. This page can be found at:
http://www.emergencyreporting.com!ers/webservices/ submissions/ If data
appears in the submissions table but not in the live system, the problem is
likely on the ERS side.
3. Contact ERS at 360-647-6003 or toll free at 866-773-7678. Ifthe call is after hours,
follow the telephone prompts to speak with an after hours tech to help resolve the
problem. ERS staff are available 24 hours a day to resolve these kinds of emergency
Issues.
Emergency Reporting
Port Angeles Agreement
23
Appendix A
A
NFIRS
T
C d
cceptable InCIdent .'ype o es
Incident Type Name
100 FIre, other
111 Buildml!: fIre
112 FIres in structure other than in a building
113 Coo1an1!: fIre, confmed to contamer
114 Chimnev or flue fIre, confmedto chimney or flue
115 Incmerator overload or malfunction, fIre confmed
116 Fuel bumer/boiler malfunction, fIre confmed
117 Commerclal Compactor fIre, confmed to rubbish
118 Trash or rubblsh fIre, contained
120 Fire in mobile prop. used as a fIxed struc., other
121 Fire in mobile home used as fIxed residence
122 Fire m motor home, camper, recreational vehicle
123 Fire m portable bUlldmg, fIxed 10catlOn
130 Mobile pronertv (vehicle) fIre, other
131 Passenl!:er vehicle fIre
132 Road freil!:ht or transport vehlcle fIre
133 Rail vehicle fIre
134 Water vehlcle fIre
135 Aircraft fIre
136 Self-nropelled motor home or recreational vehicle
137 Camner or recreational vehicle (RV) fIre
138 Off-road vehicle or heavy equipment fIre
140 Natural vegetation fIre, other
141 Forest, woods or wlldland fIre
142 Brush or brush-and-grass mlXture fIre
143 Grass fIre
150 Outside rubbish fIre, other
151 Outslde rubbish, trash or waste fIre
152 Garbage dumn or sanitary landfIll fIre
153 Construction or demolition landfIll fIre
154 Dumnster or other outslde trash receptacle fIre
155 Outside stationary compactor/compacted trash fIre
160 Speclal outside fIre, other
161 Outside storal!:e fIre
162 Outside eaumment fIre
163 Outslde gas or vapor combustion explosion
164 Outside mailbox fIre
170 Cultivated vegetation, crop fIre, other
171 Cultivated I!:rain or crop fIre
172 Cultivated orchard or vmeyard fIre
173 Cultivated trees or nursery stock fIre
Emergency Reporting
Port Angeles Agreement
24
200 Overpressure rupture, explosIOn, overheat, other
210 Ovemressure ruoture from steam, other
211 Overpressure rupture of steam PIPe or PIPeline
212 Overpressure rupture of steam boller
213 S team rupture of pressure or process vessel
220 Overpressure rupture from air or gas, other
221 Ovemressure ruoture of air or gas pipe/ptpelme
222 Ovemressure ruoture of boiler from air or gas
223 Air or llas ruoture of pressure or process vessel
231 Chemical reaction rupture of process vessel
240 Exolosion (no fIre), other
241 Munitions or bomb explosion (no fIre)
242 Blastinll allent explosIOn (no fIre)
243 Fireworks explosion (no fIre)
251 Excessive heat, scorch bums with no ignition
300 Rescue, EMS incIdent, other
311 Medical assIst, assist EMS crew
321 EMS call, excluding vehicle accident with iniury
322 Motor vehIcle accident with imuries
323 Motor vehlcle/oedestnan accident (MY Ped)
324 Motor vehIcle accident WIth no iniuries
331 Lock-m (if lock out, use 511 )
340 Search for lost person, other
341 Search for person on land
342 Search for person in water
343 Search for person underground
350 Extrication, rescue, other
351 Extrication ofvictim(s) from building/structure
352 Extrication ofvictim(s) from vehicle
353 Removal ofvictim(s) from stalled elevator
354 Trench/below-llrade rescue
355 Confmed soace rescue
356 Hlgh-anllle rescue
357 Extrication ofvictim(s) from machinery
360 Water & ice-related rescue, other
361 Swimming/recreational water areas rescue
362 Ice rescue
363 SWIft water rescue
364 Surf rescue
365 Watercraft rescue
370 Electrical rescue, other
371 Electrocution or potential electrocution
372 Trapped bv power lines
381 Rescue or EMS standby
400 Hazardous condition, other
Emergency Reporting
Port Angeles Agreement
25
410 Combustible/flammable gas/liquid conditlOn, other
411 Gasoline or other flammable hQUId spill
412 Gas leak (natural !!:as or LPG)
413 011 or other combustible liqUId spill
420 TOXIC condition, other
421 Chemical hazard (no spill or leak)
422 ChemIcal spill or leak
423 Refrigeration leak
424 Carbon monoxide mcident
430 RadlOactive conditlOn, other
431 RadiatIon leak, radioactive matenal
440 Electncal wirin!!:/eQUIpment problem, other
441 Heat from short CirCUIt (wiring), defective/worn
442 Overheated motor
443 Breakdown of hght ballast
444 Power lme down
445 Arcing, shorted electncal eqUIPment
451 Biological hazard, confmned or suspected
460 ACCIdent, potential accident, other
461 Building or structure weakened or collapsed
462 Aircraft standbv
463 VehIcle accident, !!:eneral cleanup
471 Exolosive, bomb removal (for bomb scare, use 721)
480 Attemoted burnin!!:, illegal action, other
481 Attemot to bum
482 Threat to bum
500 Service Call, other
510 Person in distress, other
511 Lock-out
512 Ring or iewelrv removal
520 Water oroblem, other
521 Water evacuation
522 Water or steam leak
531 Smoke or odor removal
540 Animal oroblem, other
541 Animal problem
542 Animal rescue
550 Public servIce assistance, other
551 ASSISt oohce or other governmental agency
552 Police matter
553 Public servIce
554 Assist invalid
555 DefectIve elevator, no occupants
561 Unauthorized burning
571 Cover assignment, standby, moveup
Emergency Reporting
Port Angeles Agreement
26
600 Good intent call, other
611 DIspatched & canceled en route
621 Wron!! locatIon
622 No incident found on arrival at dIspatch address
631 Authorized controlled burning
632 Prescribed fire
641 Vlcmitv alarm (incIdent in other locatIOn)
650 Steam, other gas mistaken for smoke, other
651 Smoke scare, odor of smoke
652 Steam, vanor, fo!! or dust thought to be smoke
653 Smoke from barbecue, tar kettle
661 EMS call, nartv transported by non-fire agency
671 HazMat release investigation wino HazMat
672 BIOlo!!ical hazard mvestigatIon, none found
700 False alarm or false call, other
710 MahcIOus, miscmevous false call, other
711 Mumcipal alarm system, malicious false alarm
712 Drrect tie to FD, malicious false alarm
713 Telephone, malicious false alarm
714 Central station, malicious false alarm
715 Local alarm system, mahcIOus false alarm
721 Bomb scare - no bomb
730 System malfunction, other
731 Sprmkler activation due to malfunction
732 Extm!!uishing system activation due to malfunction
733 Smoke detector activation due to malfunction
734 Heat detector activation due to malfunction
735 Alarm system sounded due to malfunctIOn
736 CO detector activation due to malfunctIon
740 Unmtentional transmission of alarm, other
741 Sprinkler activation, no frre - unintentional
742 Extin!!uishin!! svstem activation
743 Smoke detector actIvatIOn, no frre - unintentIOnal
744 Detector activation, no frre - unintentional
745 Alarm system actIvation, no frre - unintentIonal
746 Carbon monoxide detector activation, no CO
751 BIOlogICal hazard, malicious false report
800 Severe weather or natural dIsaster, other
811 Earthauake assessment
812 Flood assessment
813 Wmd storm, tornado/hurncane assessment
814 Li!!htnin!! strike (no frre)
815 Severe weather or natural disaster standby
900 Special type of incident, other
911 CItizen complaint
Emergency Reporting
Port Angeles Agreement
27
Res onse Code
380
385
390
395
A
t hI L
f T
Cd
ccep1a e oca Ion ype o es
Location Code Name
I Street Address
2 Intersection
3 In front of
4 Rear of
5 Adlacent to
6 Directions
7 National Grid
A
hI S
T
C d
ccepta e treetype o es
Name Code
Alley ALY
Annex ANX
Arcade ARC
Avenue AVE
Beach BCH
Bend BND
Bluff BLF
Bluffs BLFS
Bottom BTM
Boulevard BLVD
Branch BR
Bridge BRG
Brook BRK
Brooks BRKS
Burg BG
Burgs BGS
Bypass BYP
Canyon CYN
Cape CPE
Causeway CSWY
Center CTR
Centers CTRS
Circle CIR
Circles CIRS
Cliff CLF
Cliffs CLFS
Emergency Reporting
Port Angeles Agreement
28
Club CLB
Common CMN
Commons CMNS
Corner COR
Corners CaRS
Court CT
Courts CTS
Cove CV
Coves CVS
Creek CRK
Crescent CRES
Crest CRST
Crossing XING
Crossroad XRD
Crossroads XRDS
Curve CURV
Dale DL
Dam DM
DIVIde DV
Dove DR
Doves DRS
Estate EST
Estates ESTS
Expressway EXPY
Extension EXT
Extensions EXTS
Fall FALL
Falls FLS
Ferry FRY
Field FLD
Fields FLDS
Flat FLT
Flats FLTS
Ford FRD
Fords FRDS
Forest FRST
Forge FRG
Forges FRGS
Fork FRK
Forks FRKS
Fort FT
Freeway FWY
Garden GDN
Gardens GDNS
Gateway GTWY
Emergency Reporting
Port Angeles Agreement
29
Glen GLN
Glens GLNS
Green GRN
Greens GRNS
Grove GRV
Groves GRVS
Harbor HBR
Harbors HBRS
Haven HVN
HeIghts HTS
Highway HWY
Hill HL
Hills HLS
Hollow HOLW
Inlet INLT
Island IS
Islands ISS
Isle ISLE
JunctIOn JCT
Junctions JCTS
Key KY
Keys KYS
Knoll KNL
Knolls KNLS
Lake LK
Lakes LKS
Landmg LNDG
Lane LN
Light LGT
Lights LGTS
Loaf LF
Lock LCK
Locks LCKS
Lodge LDG
Loop LOOP
Mall MALL
Manor MNR
Manors MNRS
Meadow MDW
Meadows MDWS
Mews MEWS
Mill ML
Mills MLS
Mission MSN
Motorwav MTWY
Emergency Reporting
Port Angeles Agreement
30
Mount MT
Mountain MTN
Mountains MTNS
Neck NCK
Orchard ORCH
Oval OVAL
Park PARK
Parkway PKY
Parkways PKYS
Pass PASS
Passage PSGE
Path PATH
PIke PIKE
Pine PNE
Pines PNES
Place PL
Plaza PLZ
Point PT
Pomts PTS
Port PRT
Ports PRTS
Prarrie PR
Radial RADL
Ramp RAMP
Ranch RNCH
RapId RPD
RapIds RPDS
Rest RST
Ridge RDG
Ridges RDGS
River RIV
Road RD
Roads RDS
Route RT
Row ROW
Rue RUE
Run RUN
Street ST
Shoal SHL
Shoals SHLS
Shore SHR
Shores SHRS
Skyway SKWY
Spring SPG
Sprmgs SPGS
Emergency Reporting
Port Angeles Agreement
31
Sour SPUR
Sours SPRS
Square SQ
Squares SQS
Station STA
Stravenue STRA
Stream STRM
Street ST
Streets STS
Sumnut SMT
Terrace TER
Throul!hwav TRWY
Trace TReE
Track TRAK
Trafficway TRFY
Trail TRL
Trader TRLR
Tunnel TUNL
Turnpike TPKE
Undemass UPAS
Union UN
Unions UNS
Valley VLY
Valleys VLYS
Viaduct VIA
View VW
V leWS VWS
Villal!e VLG
Villal!es VLGS
Ville VL
Vista VIS
Walk WALK
Walks WALK
Wall WALL
Way WAY
Well WL
Wells WLS
Emergency Reporting
Port Angeles Agreement
32
A
t bI S
C d
ccepla e tate o es
Name Code
Alabama AL
Alaska AK
Arizona AZ
Arkansas AR
CalifornIa CA
Colorado CO
Connecticut CT
Delaware DE
District of Columbia DC
Florida FL
GeorgIa GA
Hawaii HI
Idaho ill
Illinois IL
Indiana IN
Iowa IA
Kansas KS
Kentucky KY
Louisiana LA
Maine ME
Maryland MD
Massachusetts MA
MIchigan MI
Minnesota MN
Mississippi MS
Missouri MO
Montana MT
Nebraska NE
Nevada NV
New Hampshire NH
New Jersey NJ
New Mexico NM
New York NY
North Carolina NC
North Dakota ND
OhlO OH
Oklahoma OK
Oregon OR
Pennsylvania PA
Rhode Island RI
South Carolina SC
South Dakota SD
Tennessee TN
Emergency Reporting
Port Angeles Agreement
33
.
,
Texas TX
Utah UT
Vermont VT
V rrgmia VA
Washington WA
West V rrginla WV
W Isconsm WI
Wyoming WY
American Samoa AS
Canal Zone CZ
Department of Defense DD
Guam GU
Federated States of Micronesia FM
Marshall Islands MH
NatIve American Tribal Authonty NA
Northern Mariana Islands MP
Palau PW
Puerto Rico PR
US Minor Outlying Islands UM
Virgin Islands VI
Other 00
Emergency Reporting
Port Angeles Agreement
34
r
Exhibit 3 - EMS Billing Link to
City's Medical Billing Company
EMS Billing Link
The data export file from Emergency Reporting, sent to the EMS billing company, will
fully conform to the NEMSIS 2.2 standard. The file format will be XML, as defined by
the national standard.
The file will be encrypted and transported to the medical billing provider of choice, as
determined by the individual fire agencies identified in the Computer System Services
Agreement.
The export frequency will be determined by the submitting fire agency; the fire agency
will be responsible for triggering the export when data needs to be exported to their
medical billing provider; the system is user-driven for exports.
The XML specifications and sample files are available at www.nemsis.org.
Unless otherwise agreed upon, there will be no deviation from the national standard in
the XML specifications.
Emergency Reporting
Port Angeles Agreement
35