HomeMy WebLinkAboutC2019-662 - 12/10/2019 - Approved CIS CIZ11
/raw: SERVICE AGREEMENT NO. 2325
ver
Records Management System for CCFD
ORPOR EO
/852
THIS Records Management System for CCFD Agreement ("Agreement") is entered
into by and between the City of Corpus Christi, a Texas home-rule municipal
corporation ("City") and ESO Solutions, Inc. ("Contractor"), effective upon execution
by the City Manager or the City Manager's designee ("City Manager").
WHEREAS, Contractor has bid to provide Records Management System for CCFD
in response to Request for Bid/Proposal No. 2325 ("RFB/RFP"), which RFB/RFP includes
the required scope of work and all specifications and which RFB/RFP and the
Contractor's bid or proposal response, as applicable, are incorporated by reference
in this Agreement as Exhibits 1 and 2, respectively, as if each were fully set out here in
its entirety.
NOW, THEREFORE, City and Contractor agree as follows:
1. Scope. Contractor will provide Records Management System for CCFD
("Services") in accordance with the attached Scope of Work, as shown in
Attachment A, the content of which is incorporated by reference into this
Agreement as if fully set out here in its entirety, and in accordance with Exhibit 2.
2. Term. This Agreement is for five years, with performance commencing upon the
date of issuance of a notice to proceed from the Contract Administrator or the
Contracts and Procurement Department. The parties may mutually extend the
term of this Agreement for up to zero additional zero-year periods ("Option
Period(s)"), provided, the parties do so by written amendment prior to the
expiration of the original term or the then-current Option Period. The City's
extension authorization must be executed by the City Manager or designee.
3. Compensation and Payment. This Agreement is for an amount not to exceed
$104,920.00, subject to approved extensions and changes. Payment will be made
for Services completed and accepted by the City within 30 days of acceptance,
subject to receipt of an acceptable invoice. Contractor shall invoice no more
frequently than once per month. All pricing must be in accordance with the
attached Bid/Pricing Schedule, as shown in Attachment B, the content of which
is incorporated by reference into this Agreement as if fully set out here in its
entirety. Any amount not expended during the initial term or any option period
may, at the City's discretion, be allocated for use in the next option period.
Invoices will be mailed to the following address with a copy provided to the
Contract Administrator:
Service Agreement Standard Form Page 1 of 7
Approved as to Legal Form July 11, 2019
SCANNED
City of Corpus Christi
Attn: Accounts Payable
P.O. Box 9277
Corpus Christi, Texas 78469-9277
4. Contract Administrator. The Contract Administrator designated by the City is
responsible for approval of all phases of performance and operations under this
Agreement, including deductions for non-performance and authorizations for
payment. The City's Contract Administrator for this Agreement is as follows:
Richie Quintero
Fire Department
361-826-3936
RichieQ@cctexas.com
5. Insurance; Bonds.
(A) Before performance can begin under this Agreement, the Contractor must
deliver a certificate of insurance ("COI"), as proof of the required insurance
coverages, to the City's Risk Manager and the Contract Administrator.
Additionally, the COI must state that the City will be given at least 30 days'
advance written notice of cancellation, material change in coverage, or intent
not to renew any of the policies. The City must be named as an additional insured.
The City Attorney must be given copies of all insurance policies within 10 days of
the City Manager's written request. Insurance requirements are as stated in
Attachment C, the content of which is incorporated by reference into this
Agreement as if fully set out here in its entirety.
(B) In the event that a payment bond, a performance bond, or both, are
required of the Contractor to be provided to the City under this Agreement before
performance can commence, the terms, conditions, and amounts required in the
bonds and appropriate surety information are as included in the RFB/RFP or as
may be added to Attachment C, and such content is incorporated here in this
Agreement by reference as if each bond's terms, conditions, and amounts were
fully set out here in its entirety.
6. Purchase Release Order. For multiple-release purchases of Services to be
provided by the Contractor over a period of time, the City will exercise its right to
specify time, place and quantity of Services to be delivered in the following
manner: any City department or division may send to Contractor a purchase
release order signed by an authorized agent of the department or division. The
purchase release order must refer to this Agreement, and Services will not be
rendered until the Contractor receives the signed purchase release order.
Service Agreement Standard Form Page 2 of 7
Approved as to Legal Form July 11, 2019
7. Inspection and Acceptance. City may inspect all Services and products supplied
before acceptance. Any Services or products that are provided but not
accepted by the City must be corrected or re-worked immediately at no charge
to the City. If immediate correction or re-working at no charge cannot be made
by the Contractor, a replacement service may be procured by the City on the
open market and any costs incurred, including additional costs over the item's
bid/proposal price, must be paid by the Contractor within 30 days of receipt of
City's invoice.
8. Warranty.
(A) The Contractor warrants that all products supplied under this Agreement
are new, quality items that are free from defects, fit for their intended purpose,
and of good material and workmanship. The Contractor warrants that it has clear
title to the products and that the products are free of liens or encumbrances.
(B) In addition, the products purchased under this Agreement shall be
warranted by the Contractor or, if indicated in Attachment D by the
manufacturer, for the period stated in Attachment D. Attachment D is attached
to this Agreement and is incorporated by reference into this Agreement as if fully
set out here in its entirety.
(C) Contractor warrants that all Services will be performed in accordance
with the standard of care used by similarly situated contractors performing similar
services.
9. Quality/Quantity Adjustments. Any Service quantities indicated on the Bid/Pricing
Schedule are estimates only and do not obligate the City to order or accept more
than the City's actual requirements nor do the estimates restrict the City from
ordering less than its actual needs during the term of the Agreement and including
any Option Period. Substitutions and deviations from the City's product
requirements or specifications are prohibited without the prior written approval of
the Contract Administrator.
10. Non-Appropriation. The continuation of this Agreement after the close of any
fiscal year of the City, which fiscal year ends on September 30th annually, is subject
to appropriations and budget approval specifically covering this Agreement as
an expenditure in said budget, and it is within the sole discretion of the City's City
Council to determine whether or not to fund this Agreement. The City does not
represent that this budget item will be adopted, as said determination is within the
City Council's sole discretion when adopting each budget.
11. Independent Contractor. Contractor will perform the work required by this
Agreement as an independent contractor and will furnish such Services in its own
manner and method, and under no circumstances or conditions will any agent,
servant or employee of the Contractor be considered an employee of the City.
Service Agreement Standard Form Page 3 of 7
Approved as to Legal Form July 11, 2019
12. Subcontractors. Contractor may use subcontractors in connection with the work
performed under this Agreement. When using subcontractors, however, the
Contractor must obtain prior written approval from the Contract Administrator
unless the subcontractors were named in the bid or proposal or in an Attachment
to this Agreement, as applicable. In using subcontractors, the Contractor is
responsible for all their acts and omissions to the same extent as if the
subcontractor and its employees were employees of the Contractor. All
requirements set forth as part of this Agreement, including the necessity of
providing a COI in advance to the City, are applicable to all subcontractors and
their employees to the same extent as if the Contractor and its employees had
performed the work. The City may, at the City's sole discretion, choose not to
accept Services performed by a subcontractor that was not approved in
accordance with this paragraph.
13. Amendments. This Agreement may be amended or modified only in writing
executed by authorized representatives of both parties.
14. Waiver. No waiver by either party of any breach of any term or condition of this
Agreement waives any subsequent breach of the same.
15. Taxes. The Contractor covenants to pay payroll taxes, Medicare taxes, HCA
taxes, unemployment taxes and all other applicable taxes. Upon request, the City
Manager shall be provided proof of payment of these taxes within 15 days of such
request.
16. Notice. Any notice required under this Agreement must be given by fax, hand
delivery, or certified mail, postage prepaid, and is deemed received on the day
faxed or hand-delivered or on the third day after postmark if sent by certified mail.
Notice must be sent as follows:
IF TO CITY:
City of Corpus Christi
Attn: Richie Quintero
Deputy Fire Chief
2406 Leopard St., Corpus Christi, TX 78408
Phone: 361-826-3936
Fax: 361-826-4333
IF TO CONTRACTOR:
ESO Solutions, Inc.
Attn: Darrell Hagans
Director of Account Management
11500 Alterra Parkway, #100, Austin, TX 78758
Phone: 866-766-9471 ext. 7949
Fax: n/a
Service Agreement Standard Form Page 4 of 7
Approved as to Legal Form July 11, 2019
17. CONTRACTOR SHALL FULLY INDEMNIFY, HOLD HARMLESS AND DEFEND
THE CITY OF CORPUS CHRISTI AND ITS OFFICERS, EMPLOYEES AND
AGENTS ("INDEMNITEES') FROM AND AGAINST ANY AND ALL LIABILITY,
LOSS, CLAIMS, DEMANDS, SUITS, AND CAUSES OF ACTION OF
WHATEVER NATURE, CHARACTER, OR DESCRIPTION ON ACCOUNT OF
PERSONAL INJURIES, PROPERTY LOSS, OR DAMAGE, OR ANY OTHER KIND
OF INJURY, LOSS, OR DAMAGE, INCLUDING ALL EXPENSES OF
LITIGATION, COURT COSTS, ATTORNEYS' FEES AND EXPERT WITNESS FEES,
WHICH ARISE OR ARE CLAIMED TO ARISE OUT OF OR IN CONNECTION
WITH A BREACH OF THIS AGREEMENT OR THE PERFORMANCE OF THIS
AGREEMENT BY THE CONTRACTOR OR RESULTS FROM THE NEGLIGENT
ACT, OMISSION, MISCONDUCT, OR FAULT OF THE CONTRACTOR OR ITS
EMPLOYEES OR AGENTS. CONTRACTOR MUST, AT ITS OWN EXPENSE,
INVESTIGATE ALL CLAIMS AND DEMANDS, ATTEND TO THEIR SETTLEMENT
OR OTHER DISPOSITION, DEFEND ALL ACTIONS BASED THEREON WITH
COUNSEL SATISFACTORY TO THE CITY ATTORNEY, AND PAY ALL
CHARGES OF ATTORNEYS AND ALL OTHER COSTS AND EXPENSES OF
ANY KIND ARISING OR RESULTING FROM ANY SAID LIABILITY, DAMAGE,
LOSS, CLAIMS, DEMANDS, SUITS, OR ACTIONS. THE INDEMNIFICATION
OBLIGATIONS OF CONTRACTOR UNDER THIS SECTION SHALL SURVIVE
THE EXPIRATION OR EARLIER TERMINATION OF THIS AGREEMENT.
18. Termination.
(A) The City Manager may terminate this Agreement for Contractor's failure to
comply with any of the terms of this Agreement. The Contract Administrator must
give the Contractor written notice of the breach and set out a reasonable
opportunity to cure. If the Contractor has not cured within the cure period, the
City Manager may terminate this Agreement immediately thereafter.
(B) Alternatively, the City Manager may terminate this Agreement for
convenience upon 30 days advance written notice to the Contractor. The City
Manager may also terminate this Agreement upon 24 hours written notice to the
Contractor for failure to pay or provide proof of payment of taxes as set out in this
Agreement.
19. Owner's Manual and Preventative Maintenance. Contractor agrees to provide a
copy of the owner's manual and/or preventative maintenance guidelines or
instructions if available for any equipment purchased by the City pursuant to this
Agreement. Contractor must provide such documentation upon delivery of such
equipment and prior to receipt of the final payment by the City.
Service Agreement Standard Form Page 5 of 7
Approved as to Legal Form July 11, 2019
20. Assignment. No assignment of this Agreement by the Contractor, or of any right
or interest contained herein, is effective unless the City Manager first gives written
consent to such assignment. The performance of this Agreement by the
Contractor is of the essence of this Agreement, and the City Manager's right to
withhold consent to such assignment is within the sole discretion of the City
Manager on any ground whatsoever.
21. Severability. Each provision of this Agreement is considered to be severable and,
if, for any reason, any provision or part of this Agreement is determined to be
invalid and contrary to applicable law, such invalidity shall not impair the
operation of nor affect those portions of this Agreement that are valid, but this
Agreement shall be construed and enforced in all respects as if the invalid or
unenforceable provision or part had been omitted.
22. Order of Precedence. In the event of any conflicts or inconsistencies between this
Agreement, its attachments, and exhibits, such conflicts and inconsistencies will
be resolved by reference to the documents in the following order of priority:
A. this Agreement (excluding attachments and exhibits);
B. Attachments A, B, C, and D;
C. Attachment E;
D. the bid solicitation document including any addenda (Exhibit 1); then,
E. the Contractor's bid response (Exhibit 2).
23. Certificate of Interested Parties. Contractor agrees to comply with Texas
Government Code Section 2252.908, as it may be amended, and to complete
Form 1295 "Certificate of Interested Parties" as part of this Agreement if required
by said statute.
24. Governing Law. Contractor agrees to comply with all federal, Texas, and City laws
in the performance of this Agreement. The applicable law for any legal disputes
arising out of this Agreement is the law of the State of Texas, and such form and
venue for such disputes is the appropriate district, county, or justice court in and
for Nueces County, Texas.
25. Specific Terms and Conditions. This Agreement is subject to the Master
Subscription License Agreement between the Parties, which has been attached
as Attachment E, the content of which is incorporated by reference into this
Agreement as if fully set out here in its entirety.
26. Entire Agreement. This Agreement constitutes the entire agreement between the
parties concerning the subject matter of this Agreement and supersedes all prior
negotiations, arrangements, agreements and understandings, either oral or
written, between the parties.
Service Agreement Standard Form Page 6 of 7
Approved as to Legal Form July 11, 2019
CONTRACTOR
Signature
Printed Name: C r'S 0 I I t I t?
Title: LEG 4 Ftte5JLi t
Date: 1i 1sl�Cil�
CITY OF CORPUS CHRISTI
Kim Baker
Director of Contracts and Procurement
�2-, ATTEST: Re-
Date: l2. tq
tiat.A/tb.,
REBECCA HUERTA
CITY SECRETARY
APPROVED AS TO LEGAL FORM:
Assistant City Attorney Date
Attached and Incorporated by Reference:
Attachment A: Scope of Work
Attachment B: Bid/Pricing Schedule
Attachment C: Insurance and Bond Requirements
Attachment D: Warranty Requirements
Attachment E: Master Subscription License Agreement
Incorporated by Reference Only: L____,-_ l_ •AU I HUiciai,
Exhibit 1: RFB/RFP No. 2325
Exhibit 2: Contractor's Bid/Proposal Response BY t'waL- 1_ 1 D
SECRETARv
Service Agreement Standard Form Page 7 of 7
Approved as to Legal Form July 11,2019
Attachment A: Scope of Work
1.1. General Requirements
A. System must be capable of supporting National Fire Incident Reporting System
(NFIRS). Must be current version and subsequent versions.
B. System must be capable of importing legacy records adhering to the NFIRS file
formats.
C. System must allow the ability to attach documents including, but not limited to
the following types:
1 . Video
2. Pictures
3. Documents (spreadsheets, word docs., notepad, etc)
4. PDF's
D. Fire incidents using data elements from National Fire Protection Association
(NFPA) 1710/1720. (see Appendix A for details)
E. Department leaders must be able to access certain system level configurations
and run date queries and reports based on records entered by their department.
F. System must have an audit trail in order to show if any changes were made for
quality assurance or legal purposes. Audit trail should:
1 . Track
2. Capture
3. Display key-stroke entry level changes
4. Include all changes made to any records, not just last update
G. Software must provide a means to display administrative messages or notes
entered and link to individual event records and/or users (e.g. internal messaging
or notes) (see Appendix B for details)
H. System must have Quality Control (QC) Reports for completeness and accuracy
(NFIRS reports).
I. System must have active directory functionality.
J. System must be capable of viewing previous, current, and future schedules with
a task manager to create schedules (see Appendix C for details)
K. System must be able to add and update department of employee's
certification, notify department of certification nearing expiration date.
RFP Template 04.05.19 Page 1 of 41
L. System must be able to add full employee information such as: (see Appendix D
for details)
1 . Employee contact
2. Social Security Number (SSN)
3. Driver license number and expiration date
4. Certification
5. Notes
6. Employee ID
7. Rank
M. System must be able to customize data and label fields.
N. System must hold historical data with import/export capabilities (see Appendix E
for details)
0. System must be able to search for record by:
1 . Date
2. Address
3. Name
4. Incident #
5. Etc.
P. System must have the capability to track and manage Fire equipment
maintenance record on all:
1 . Apparatus
2. Equipment
3. Inspection records,with due date, status, and maintenance inspections notes
(history)
4. Link maintenance records to inspection records
5. Perform inspection on a mobile environment (tablet, cell phone, etc.)
6. Capability to trigger a scheduled maintenance and submit a workorder
7. Apparatus daily readiness report (see Appendix F for details)
Q. System must have the capability to track and manage fleet and vehicle
maintenance:
1 . Automated vehicle system for maintenance on vehicle mileage/engine
hours
2. Schedule and submit a workorder
3. Track fuel usage
4. Inspection records: with due dates, status, and maintenance inspections
notes (history)
5. Log all maintenance history records per vehicle
6. EMS unit daily readiness report (see Appendix G for details)
RFP Template 04.05.19 Page 2 of 41
R. System must have daily EMS inventory real time capabilities interfaced with run
reports and bar coding for inventory tracking.
S. System must be able to track weekly medic unit inventory and EMS supply lockers
by station (see Appendix H for details)
T. System shall integrate with Maximo, ESRI, Infor, CE Solutions and share at
minimum, incident demographic and time data.
U. System software solution must work with any hardware including PC's, laptops,
android, and mobile devices with the exception of any devices that are
unsecure.
V. System shall be able to create and customize dashboards in real time.
W. System shall provide electronic signatures for maintenance checkoffs and other
items, such as permits, occupancy.
1.2. System Requirements
A. System must allow tiered permissions for various access:
1 . System settings
2. Agency settings
3. Data entry forms
4. Patient data
5. Print forms
6. Data Analysis tools
B. System administrator must have the ability to manage all users and control their
ability to manage their profiles or add new users.
C. System administrator must have the ability to manage locations: (see Appendix
I for details)
1 . Streets
2. Districts
3. Stations
4. Etc.
D. System administrator must have the ability to: (see Appendix J for details)
1 . Manage and modify data entry forms
2. Selective dynamic display with the data entry form, and the dataset
3. Print layouts
4. Point-of-entry business rules
RFP Template 04.05.19 Page 3 of 41
E. System and department administrator must have ability to manage the display
of other agencies at an incident. For example, adding a unit from a different
City that has responded to the incident. (see Appendix K for details)
F. System must define when incident is complete with time stamp and related
status changes for administrative purposes.
G. System must export records to excel, PDF, or print.
H. System must customize toolbars (shortcuts, favorites for reporting, queries or any
screen and modify user view (user preferences).
I. System must create system rules and default values - required fields.
J. System must have a query tool with delivered queries and modifiable
parameters.
K. System must have a reporting tool with delivered reports, including modifiable
parameters.
1.3. Import/Export Requirements
A. System must interface with existing Integraph Computer Aided Dispatch (CAD)
software v9.3.
B. System must allow integration with data exported from CAD systems. The CAD
system software vendor will provide an output file or other agreed upon secure
method for the solution vendor to map and import.
C. Contractor must have pre-established integrations and data relationships with
the major CAD vendors to make this process more efficient for agencies to
implement.
D. System must provide means to import to CAD, at minimum:
1 . All Fire event times
2. Incident address
3. Type of service requested
4. Responding unit numbers and call signs
5. Incident numbers
RFP Template 04.05.19 Page 4 of 41
E. CAD integration must have capacity to re-import data into a record as new
data is added to the CAD record (for example, more times are added as the
incident progresses) overwriting or updating the previous data.
F. CAD Data integration will be accessible to use by user with fixed devices (e.g.
desktops) or mobile devices, provided the device is online.
G. Imports and Exports will be in compliance with NFIRS validations and data rules
for import/export (see Appendix M for details)
H. System must be able to import/export reports, photos, records, and attachment.
1.4. Journal
System must have a monthly activity tracker for any entry for a specific date to
include: (see Appendix N for details)
A. On/off feature
B. NFIRS activities
C. Non-incident activities
D. Department events
E. Training classes
F. Occupancy inspections
G. Activities
H. Permits
I. Equipment maintenance
J. Testing
K. Hydrant Activities
L. Filtering by:
1 . Station
2. Shift
3. Units
4. Staff
1.5. Data Entry
A. System must have default values and require values to be read only, or have
them hidden with the value still part of the incident data (e.g. all incidents are in
the US) (see Appendix 0 for details)
B. System must limit the provider ability to enter one value, but have that value
autofill related values without letting them access the linked elements. For
example, limiting users to only enter an incident zip code, which will autofill the
RFP Template 04.05.19 Page 5 of 41
incident city, county, and state without letting the user access the auto filled
fields to prevent conflicting or poor quality data.
C. Layout for online and mobile/offline data will be the same without needing to
build the forms separately for each system.
D. System will have a dynamic sizing display that will by able to adjust to screen size.
Change with minimal effect on the layout displayed to the user.
E. Display of single or multi-select drop-down lists must accommodate popup on
screen keyboards on tablets such that the keyboard does not obscure the drop-
down value list.
F. Users must be able to navigate between elements in the data entry form using
touch, mouse, or keyboard tabs and arrows.
G. Data entry forms will clearly display elements and values that have an
outstanding point of entry business rule to be resolved so users can quickly
identify and resolve shortcomings.
H. Incident form will provide display of the data entry and review status for
administrative purposes.
I. Incident form will provide easy interface to import CAD data.
J. Incident form will provide means for agencies to create and apply localized
custom fields.
K. Capability of adding narratives on all modules and narrative will be able to print
on reports.
1.6. Scheduling
A. System must manage personnel schedules.
B. System must create daily schedules for firefighters.
1 . Employee roster
2. Station location
3. Employee availability
4. Per shift
C. Schedule crews with stations and/or apparatus.
D. Schedule inspections.
E. Schedule maintenance on equipment.
RFP Template 04.05.19 Page 6 of 41
F. List leave status
G. Create leave and payroll codes (customize codes)
H. Flexibility to add additional scheduling items, such as available for overtime, out
on leave, temp driver, etc.
1.7. Investigations
A. System must link investigations to incidents and locations.
B. System must be able to maintain, and access history of incidents and
investigations attached to locations.
C. System must conduct and document investigations.
D. System must be able to create an investigation report. Investigation report need
the following fields: (see Appendix Q for details)
1 . Referrals
2. Evidence
3. Leads
4. Scene
5. Activities
6. Narrative
7. Print capabilities of attachments
1.8. Inspections
A. System must be able to capture various types of inspections such as life safety,
building and occupancy based on NFIRS codes.
B. System must link inspection to incidents and locations.
C. Must be able to perform inspections in the mobile environments.
D. System must be able to cross validate to ensure no duplicate records in
occupancies.
E. System must be able to add new inspection codes.
F. System must be able to merge occupancy CAD information into inspection
records.
G. System must be able to schedule daily inspections for inspector.
H. System shall interface inspection schedule to Office 365 calendar.
RFP Template 04.05.19 Page 7 of 41
1.9. Permits
A. System must track and manage all permits.
B. Permits must be managed through the Fire RMS.
C. System must manage permit fees, receipts, and adjustments through the City's
payment gateway.
D. System must allow users to print or email permits, receipts, and mailing labels.
E. System must maintain a record of historical permit information.
F. System must provide pre-formatted permit reports.
G. System must create various types of permits.
1.10. Validations
System must be able to trigger time conflict rules against the current time the record
is being entered to prevent any time in the future being entered for point of entry
validations/business rules.
1.11. Printing
A. System Administrator must have the ability to:
1 . Design, format, and manage report printout
2. Create multiple formats
B. System must print document attachments and addendums as part of the
primary printing based on the print layout design by the System Administrator.
C. System must allow print layout and design for agency name, address, and logo
to be configures and automatically applied to a printing template.
D. System must allow print layout to provide a means to configure a header and
footer for each page such that incident information such as date, incident
number, patient name can be displayed on each page of the record.
1.12. Vehicle and Equipment Inventory Records
A. System must tract specifications on the following:
1 . Personal Protection Equipment (PPE)
2. Hose
3. Self-contained breathing apparatus (SCBA)
4. Vehicles
5. Pump hoses
6. Ladders
7. All items on inventory
RFP Template 04.05.19 Page 8 of 41
8. Upload fuel report from excel to application
B. System must maintain vehicle maintenance records and requests with
notifications of when vehicle is due for maintenance.
C. System must maintain usage/purchased - date/time code, quantity, cost,
mileage, staff, description.
1.13.Occupancy: Fire Prevention
A. System must keep track of owners & contacts of buildings
B. System must track inspections & activities
C. System must track additional Fire service records - chem inventory, hydrants,
storage tanks, need fire flows, permits, supplemental history.
D. System must have the capability of merging occupancies when address is same,
must be able to keep all history when merging occupancies.
E. System must keep track of occupancy statistics.
1.14. Training Module (Appendix R)
A. System must list classes with description, data/time, location, etc.
B. System must have casualty report for injury during training to include:
1 . Vehicle accidents
2. CE hours tracking
C. System shall have scheduled training classes to interface to Office 365 calendar.
1.15. Hydrants
A. System must list basic hydrant information, such as location, hydrant number,
specifications, etc.
B. System must list activities and repairs for each hydrant.
C. System must list all flow tests.
D. System must integrate with Maximo for water usage and work orders.
1.16. Reports Module
A. System must set up rules for report fields.
B. System must provide the following reports:
1 . NFIRS
RFP Template 04.05.19 Page 9 of 41
2. Basic fire reports
3. List units and personnel
4. Casualty reports
5. Property involvement reports
6. Additional fire service reports
7. Canned statistical or list reports with modifiable parameters
8. 90 Percentile reports
9. NFPA report
10.Alarm response analysis
1 1 .Incomplete report list
12.Not QC'd report list
13.Fire investigation reports
14.Fire/Arson reports
15.Reports notification
16.Report repository for all items including reports, inspections, occupancy
records, permits, etc.
17.Query tool
18.Customizable reports
19.Logistics requisition form
20.Maintenance report (vehicle and equipment)
21 .Ad hoc reporting
1.17. Technical Requirements
A. Application
1 . System application must work with IE 11 and Microsoft Edge and the latest
version of Java, .net framework. No outdated agents of these applications
will be supported.
2. If system application requires install, it must be remotely managed and patch
with ManageEngine Patch Manager Plus version 10.0.326.
3. System application must work with Netmotion on mobile computers.
4. System application must be a mobile application.
5. System application must be windows 10 compatible.
6. System application must have 24/7 technical support.
RFP Template 04.05.19 Page 10 of 41
B. Network
1 . System must be able to communicate over Ethernet technology and be
compatible with wireless, copper and fiber optic methods of data transport.
2. Requirements must fit into a minimum throughput constraint to reach
endpoints and a reasonable latency (no more than 100ms) and must be able
to recover function after periods of packet loss which may occur.
3. Consideration must be demonstrated for reducing the amount of throughput
required from end to end across the WAN.
4. Any wireless host/AP support requirements must be made known.
5. The specific services must be made known in the proposal as to which
protocols will be needed and whether they are considered connection or
connectionless.
6. A logical network diagram must be provided that exhibits traffic flow to and
from application, database, repositories, end points and demarcations.
C. Security
1 . System must accommodate the City's intent to apply security patches to its
system within 30 days of release.
2. User authentication and access rights can be managed via Active Directory.
3. Remote 3rd party support access requires the 3rd party to use an HTML5 -
compliant web browser.
4. Contractor must provide a point of contact.
5. Contractor must provide security updates to its product.
6. Contractor must list any required ports, protocols, web domains, firewall
allowances needed for the system to function properly.
D. Server/Storage Backup
1 . System must have server/storage backup on premises, in the cloud, or in a
hybrid solution.
2. System must support a virtualized environment.
3. Contractor must provide server requirements for memory, CPU, storage and
operating system.
4. Contractor must provide any cloud storage requirements to include provider,
services, and size requirements to accommodate our current Nimble storage.
RFP Template 04.05.19 Page 11 of 41
5. Contractor is required to support current backup solution which is Commvault
version 11 service pack 14.
E. End User Support
1 . System application must require admin rights.
2. Contractor must provide minimum requirements for:
a. Memory
b. Processor
c. Storage
d. Operating System (OS)
3. Application must not be dependent on any software that may or may not
already be installed on the OS.
4. Antivirus must not cause any known issues.
F. Geographic Information System (GIS)
1 . Application must integrate with ESRI solutions.
2. Application must interact and consume with data from the GIS database.
3. GIS data must require local storage.
4. Application must require GIS editing capabilities. Editing rights are subject to
license purchasing.
5. Application must be compatible to Portal for ArcGIS version 10.3.1 .
6. Solution must be for city and/or public use.
1.18. Overall Business Requirements
The Attached matrix (see Attachment A-1 ) outlines all of the requirements
necessary to have a complete system. This matrix is part of the Agreement and will
be used throughout the implementation phase to ensure compliance with all
requirements.
RFP Template 04.05.19 Page 12 of 41
GENERAL REQUIREMENTS: Appendix A
Number 5
A �t „ii Q� t }'J1 n- ' jai , • 1y 147:• 4 tis 'S 1 r>t„fi GIff" i r t1- dory. -f
d v-3 ! K "9.1,44•, f,c t ..—.4/...-..t-d .ate ;r2 . dS_• c ti o ..,L.,4,..-.i4.•.;4„,..;.....• +,,r 1„..;.3,+!
I z t.,;' ' f 1 1 r 41 9, vv n.,p.--41.15.T
• -0 n 1 _t r q
4:• ytn i•�1 k s``ix,f ,fir i;• - Itr , ;i -, ?tvy"1 ",qe-,' :1�.-.• ,-. y
>6..uFa2P.w.0..i.+lit va*.1e5+":•�.eK•..Y.•ax4NNr1•r+J9 rc�.CTIn=SS:W+h'AAn<aHMf�4AFAd#�kF,xw,•SNYiU u,f�•).,.rtft<Mia,�AiM-tom..i•v+'iiF•YHN.,.,lt„-.+ ,t,:ri-.. K4,,..1,r�l�.....t:ie-94,F .Red.
75.4k1 J yi! 18 t fti s g:, s � ,vssl �..p� ,{ tyr (-. [, , •T v ;}'
',IF-q-- yLrf�INLS�F.T n NLi T '!t'Hi o 4i - F'` I.sz�va, r 5,t,v.i;kw:ii Nt'.41 .16:),ti Nu7'1t4R_zCv_1 i ,:1
t N>dNTt�t xn,, cYr,-,4-0,1y�.yq.`F,.a•,.r i 4 :ah 'r j •` , i ilio�l7(t4 --i,:-44,4' ��*k r.ri
lt'ff i� A 7L A!. A.:.i-X 11 Vi a r tt a i `4.�y S Tire. f r `t
-S.1 W `N - j�F>,� !C azo V: "L R Y HKi � � aO���.`��Vµ. �1�,kf�1 n,� � lir',R
JIn • i;',,,C,;(--,::, J o5 :,,ht 14i iC{k! iy' l��N 1
4 s rL h4 '.',.,,,..-t1*.:',ki, i4'
h'{5 ,_ Y�,t.t ii(: x f 3 1 ,E t 1r -J4 t w Ib • i ,AL1
rvnlj c90 " 44�Sz(7 lr Ai: 47z 7t r :: t 1', i4-:'. rir , it• r 7 h# 1 t pts; ltf�r r 'u! +}t.
.•,.,..477.7,•75-7-:,� rs F d„tdt�]• �1,. ?�,�.••'� - � a �� th 17 Pt�yah'i�s�ry�1f i bra moi' t���.0 t$ yr6
is� ( rc u �k, , f t • t : tr ?' ;� r6, r{",,iT t
J S537.59 . i S' F' Aho ,h 5 �a, (air.41 **•-. �. ? ,; r � t d=�,
!l ersn'z n h s r •r3 q kon r:rz!3t �t y1 3 'r
• { ;,,,,..2„...,,„as x -f zM 1t t ! , ,y e 6 e - r{ av , }s
rr Suppression Uri4 En Route' a to•>�,; ;.,,,,,r,,it : � i ' ;�1:� is�,• '.�e } .✓t f~
1i r, , y a•v.'v i"t: t::,..f, k.0 ' -,..,..1,,,.,...-e_ '` Hnia z J � a,, is.+ c
�' F V 1 M
05-38.54 Sarrte as Rt i', t YS5 '1,-- 05:38 50 • iN•;� is`31,1 .1 i hsdt.._ 1 r '1 y
�,. C ,! ,r �`T/ 1•f.. y „ . "�.f'. p x T'r '�li",I 1"`ottAe 8 tl
Anil.*� Arrived BLS,..n,Attved ,�. y i,A.-lk0,. b �bt. * + v.,,i,
ty . :. r SKY i.,,.0,....v.0,,,,,I,,,. • �,l„w a t i Ott
l 05.4e 06 Same as Response.. I ( • ifff t,'t i.-1.-•
. }{e
,ti. �..r hd.l i -,..,..44,..,..� .,4,4,411),..#5. �x,l b. x
J • ei
(A' Alarm AssiQrunent Arrived ALS Unit Arrived ` ryr fit T sjx ,y 3 t`x4., •p l• {
'd;',l ": >
Same as R®sponse I Same as Company T me+ Iatr�as Response
I
Required Resources Assembled C d to Inititate Attack ��t
NEPA 1720 , E Incident Rsgtmed a Vblurkteet 5upptess on Flesponse
votuntet,Fie aPab'�y +tairr�
SuPPieiimm, f E ,t,
u
,� J Same as F9esponre... , I
�� `� ,
II Save ( X Delete JL+Close
Page 13 of 41
GENERAL REQUIREMENTS: Appendix B
Number 9
Deite' ., •' ',.Tine Station `SNR Ung De ;T${iti*: ,, •
:' 04/13/2018 16:05 - Message from 10871:GARCIA,ANTHONY G
:1 04/13/2018 12:34 - �! I- Message from 10871:GARCIA,ANTHONY G
•
t
I
4.
i
r
4
y:
3
ss
r
1
Unread reminders are
higgighted in GREEN. I -�����1d��A J
1.r Show Hilden Items � Show Rerturxle�s 30 ; days in advance I a"�J �t t � �.,� � �1 P�1 � �
FI ettlp. 'NOW- I €dit Delete aerint . 4:1«Oo'se
•.#A`Rfiifei r,,zs?xw .,“...,itcs ;1,t„ a'q:riAt; m7=4**44/taatitxtta+rg M1Xranssa4714.AAVai.Ta.ra:1a,,rKRr.Mftoi-4t.i:.iMPAK4VAIVs_•c4:4.5.,Nnssrrs/ a4u wr.er.-Me
i Thu May 2.2019
f May ' 2019 ' Slat. End:' IDedcrpUofl "... �„
•
•05/02/2019 05/02/2019!019-0017064:Rescue.EMS incident-other•6717 S PADRE ISLAND t
k __0623:06 X06:46:24 DR EB
65702/2019105/022019 Station FP.ShA 4,Unit F806:INSPECTION-Certificate of Occupancy i
® OB 00 -1000 PEDIATRIC CLINIC.1504 WALDRON RD/CORPUS CHRISTI,TX 1 r
Sun Men Tue .Wed Thu Fri Sat 78414 Inspector:GOSSON,DONIEL
0:57.13 191057022019 019-0017082 Rescue,EMS incident,other•1701 THAMES DR/18 1
08:57:13 09:30:41
1 1i• 2 •ij• 3 •1j• 4 it 05702/2019105/022019 Station FP.ShJl4•UniOF806 INSPECTION ExtnguisNngSystem I
10:30 10:55 CCISD MOODY HIGH SCHOOL•1818 TROJAN DR Inspector .
GOSSON-DONIEL 1.1
# 'fl a fl05/02/2019105/022019 019-0017098 Medical assist,assist EMS aew•4229 S PADRE I
�•• 10:52:30 11:09:23 !ISLAND DREG
05/02/2019105//022019.Station FRS hilt 4.Unit F806'INSPECTION.General•CITY BAKERY 1
I
..5 I. - 6 •$• 7 •lt• 8 •1{• 9 •1i. - 10•l�• 111•$• 11:20 '11:50 808 S 19TH ST Inspector.GOSSON,DONIEL
,u 05/02/2019.05/02/20191019-0017103:Medical assist.assist EMS cret,•5518 LIPES BLVD 111;
y ® ® 1�1 11:37:42 1300:52_ /305[Quaky i
8 -Station FP.Shdt 4,Unit F806-INSPECTION•Extinguishing System- :r
f. - 05/02/2019105/132/2019 DEL MAR RESTURANT MANAGEMENT BUILDING•4101 OLD
I' ® 14:00 14:30 BROWNSVILLE RD/CORPUS CHRISTI,TX 78405In Inspector tF 12•$• 13•$• 1 a•};• 15$j• - 16•1�• 17•lj• 18- .1{• sP f)
4' 'GOSSON.DONIEL
05/022019105/02/20191519.0017130:Medical assist-assist EMS Clew-3509 HWY 358 F WY I i
r:' tplfl >w) m15:25:32 15:48:16 EB
0r5/02/2019105/02/201911119-001716a Rescue,EMS incident-other-4513S STAPLES ST 11
. 18:40:03 19:0326 /104
1'
19� •$
' 20 ' 21•$• 22 - 23 24 25 ---- ---- — -- -- ----- -------. _..----- 11.
05/022019105/02/20191
er019-0017174:Rescue-EMS incident.other•
205226 TARTAN DR '
34:46 `21:06:52
•
ci. •05/02/2019105/02/2019 819-0017187:Medical assist-assist EMS crew•305 ROSEBUD AVE i'
j -I - - �� • 2230:27 .23:01:42 (Qual Checkedl__- 1U
l:26 27 :28 29-----30 31
}
m m f5 15
.J •
d
R I IC* 1���
r Use Selected Calends Date f
Fetesm9 I Shit Tines I Qptiore 1 ." I _ I e I I l(1?Close
> 1 y
new... Edo Ue!et �Ernt _�
Page 14 of 41
GENERAL REQUIREMENTS: Appendix C
Number 13
I1- • :.,..4,4.:J.E.ii..,42,. .---,•:,,ik:-4.110,..!„-:,u.,4,if.:03p,-..;-4---,44r-..,-;44-..,-.,...:11,.:.4z7-.:..,-4Ft-;&44*Fstvf.. -1/0.411,?..--,..%:,.,,,prk-.1,:......i,.-,4, 4, -;-,,,. .):..,;4, .,..;,:,.!....-i..fA zr.,w41
' ''''''..".'': ''. -;'--'''''''''' ' '''''''''' '','''-...',',-::',...,.-.--.--i' ,....:---!:!!--f-2/..,7;•:- - •....'":'-ciRPi7 VA.T4iV.:AVA..,11.;:f:r;;,-.,..' sf:.:•.44,,P.';',CV'')i,VE,,,......, ..1',",::: :..,,,.:".?".,:''',
...1...:j.,..••1::',:.:;'...;,:,.. ,-...,,,,:,:,:.,. H....:-;',',.,.:::.'.....!.i'.:4:4',.. ..,:ii...;., ;.:'0..:;,•t.'.,•;:.;:.,;:-.'i±;"li:r47,4*^;,,yg66-r,.• .:4itiitit4....ki,,, .4.44.0..rifi..-4...,' 7.L,..,,,:j,11,;,..'44? ;:',1 .
!..:144460.*001-40.C.11*Oe''-fci4 :-, -:!i-,‘,:oiy:-i';:.;;.:;:,:i:.4:::=' ....'!x'. ;ti.i.'6.{i'.14,„;',,.;":::',-:. ,,:tf.-.,11.:',A-4:.:•-•••:•-•`:-...•") WAKWI;('4.,P.ii'..''.4i$1,4 1
• •,;:',- IJpdate Schedulinq zi t t
,_,c...r..1..y n ,. •,,,:,„.:,..f,„..f......-.:.„,-..,..z.,.74„..i
:1:,...
',*1:••1.--.4:„.,,':',.. -.',',,'4'i tt:•-. .
,.:,,..,-,, :4::i.,,,,:t-V:i•,,,K= 4`,S..',...A -
• ..,,1
,•,,,.
:.....
41:17420'3%eiti
:','..f'2'77''''',:i.•-..f:-.,',:%2-tii:,..:r:: :-;
-ii:144%,.,.!'''''''?._•:,".4,)1,1fre.,1,;!1; .
•'-:::i VAV.' 7,-;'---...14,t44: ,,•1
:':..:,',::'d:Vi.r7',4i.•;',:-:,)4,i,.:::,i-,:',,,....,-.
JjAlt....:ic!Ario:IfitM-fik:.1
,::,',C.ti-;',,,'?4'.• 70',.:1;),":„,.,i-,:..,.1?-!...1.4;t:'.,
•
.
.
..--- : :-. .. • . '
• „ : ..-
. .•
r Show automated task;assigned to this workstation only -- . .,- :-.,-
- •, . . . ' ..
. .
Task Processor Status - , • • , . ' .' • , ..,
,., ' ...
..Stopped . • ,' . Start ,.. • Suspend - Slop .
• .
• .
Task processor is stopped-unable to retrieve task count .Cielse:
Page 15 of 41 if\
GENERAL REQUIREMENTS: Appendix D
Number 15
L4at .. Fist, Middle Suffiit .Staff ID Alternate ID
llIllMl111111111111111 'STEVE 1----J 12435 1
Vlasic 1 Contacts I Activities I Training I AdcironalRecords I notes I ,other.., I
Flesfdence Address FDID EMS Service# Station Shit
;i Street Mks to Station I 1 J 1 J(
I 1 0 00 Unit Rank Effective Date
1 1 _1 I FFIID ...I 110112/1927
J
City. State ZIP Code Status Effective Date
1 CORPUS CHRISTI
FT 1 78411 I PE J1 Retired 01!10!2016 11
Date of Birth Hire Date Adjusted Hite Date^End Service Date CareerNolunteer Current Age 611
107/12/1957 109/07/1982 I-- 1 01/10/2016 171— .,,11 Career Years of Service 35.34'
Other Stations Phone Numbers 1 E-Mai/InternetAddiesses I
Code ? Description + Type ? Phone Number Extension _4,
++ •HM J 361-999-9999
,,
T LT, W
111
III I I H ❑ New Browse I Save ' I x Delete a Print... Cancel
Last First Middle Suffix I Staff ID Alternate ID
4i):14`ir `: aukVkxz .z i c..:';;::;.': L-11.11A';'"744:.7:..:� x. STEVE ,...,j 12435 I
gaic` tLontacts}I Activities I Training I AdditionalRecords I notes I Ohm.. I
Sequence Name/Tiiie Type Phone Emgcy Cont
2 SALINASAWIlle 2EMER 956 Y
Ji
T
12 Staff Contacts records listed JLILle add I OP
n I Deleee I
III I I ► 1 N ( D New I eP Browse 1 •Save - I x Delete I a Print.. I eCancei I
Page 16 of 41
GENERAL REQUIREMENTS: Appendix E
Number 17
,; 0 2019
Occupancy Name : Occtyany ID S*0 Propet(y ID
16358SPID I .
F806:INSPECTION.Extrngushing System-
11141x4 l•Owners 6 J;antacts I jnsp 6Activtties I AddtlionaJ Records I Jydes I F
RS Si Inspector G-SSONGener DONIEL
F806 INSPECTION -CORPUS
FOIA I GAS REPAIR•2213 GOLLIHAR RD
X 78416Ins.ector GOSSON,DONIEL
F806 INSPECTION-Annual G.AF.
19 DOMINICA DR q nRPIIS CHRISTI Ts.
Required Completed ;cnni nn nn
.. _ -
13
1:1 18esic other I
Dote Tine
- I 15:18 r Recitrte occwancy admiisttative rights to view
13 13
Code
JIOccupancy Name or Burldng Information has Changed
Notes
Name changed Item TEXAS EXCELLENCE to TEXAS EXCELLENCE J i
14IA ( ► Ltd CINew I 7symne 4 ■
..._..- .._ , ._ ..... _ 0 New I I♦Save .I X Delete I Close I
Page 17 of 41
Appendix F
Corpus Christi Fire Department
Daily Readiness Report
(Fire Apparatus)
Station# Unit# Company# Saturday's Odometer:
Next Service Hrs. Saturday's.Hr. Meter:
Date marked above each day
Sun Mon Tue Wed Thur Fri Sat RFM#
1. Service Sticker Checked
2. Vehicle Inspection Sticker Checked
3. Fuel(3/4 or above)
4. Engine Oil Level
5. Radiator Water Level
6. Engine Drive Belts—Inspect for excess Wear
7. Power Steering Fluid Level
8. Auto Transmission Fluid Level
9. Primer Pump Checked &Oil Reservoir level
10. Booster Tank Water Level
11. Battery Water Level&Clean Cables
12. Tires(Check Wear and Pressure)
13. Lights(Emergency,Clearance, Flood, etc.)
14. Horn &Siren
15. Brakes&Air System Checked •
16. Bleed All Air Tanks
17. Cab Instrumentation(Gauges)
18. Pump Engagement
19. Pump Panel Gauges
20. Intake&Discharge Outlets
21. Intake& Discharge Levers
22. Wipers
23. Windshield& Windows(Cracks& Dings)
24. All Door Operations (Opening& Closing)
25. Gas powered Equipment(Run daily)
26. Body Condition&Cleanliness
27. SCBA SEMS device checked for Operation
28. Engineers Initials
29. Captains Initials
I j
130. Battalion Chiefs Initials
Use the back of this form for comments
Under the daily columns, mark with an"OK" or an"X". Explain any item marked with an "X" indicating the
corresponding number and the problem. Follow up with a RFM and notify the Battalion Chief. Any tools that
are missing, report to the Battalion Chief so they can forward to Support Services.
If any fluids are added to the unit then a RFM must be put in.
Revised 9/3/13
Page 18 of 41
Appendix G •
-
Corpus Christi Fire Department
Daily Readiness Report
(EMS Units)
Station# Unit# Medic Saturday's Odometer:
Next Service Hrs. Saturday's. Hr. Meter:
Date marked above each day
Sun Mon Tue Wed Thur Fri Sat 1 RFM#
1. Service Sticker Checked
2. Vehicle Inspection Sticker Checked
3. Fuel(3/4 or above)
4. Engine Oil Level
5. Radiator Water Level
6. Fan Belt—Inspect for excess Wear
7. Power Steering Fluid Level
8. Auto Transmission Fluid Level
9. Battery Water Level &Clean Cables
10. Tires (Check Wear and Pressure) •
11. Lights(Emergency,Clearance, Flood, etc.)
12. Horn & Siren
13. Brakes System Checked
14. Cab Instrumentation (Gauges)
15. Windshield Wipers/ Washer Fluid
16. Windshield&Windows(Cracks&Dings)
17. All Door Operations(Opening&Closing)
18. Generator Checked(Run daily)
19. Body Condition&Cleanliness
20. Vehicle Tools Inventory
21. Medical Equipment Checked
22. Medical Supplies Checked
23. SCBA SEMS device checked for Operation
24. Driver's Initials
25. Captains Initials
26. 623's Initials
Use the back of this form for comments
Under the daily columns,mark with an"OK"or an"X". Explain any item marked with an"X" indicating the
corresponding number and the problem. Follow up with a RFM and notify the Battalion Chief. Any tools that
are missing, report to the Battalion Chief so they can forward to Support Services.
If any fluids are added to the unit then a RFM must be put in.
Revised 9/3/13
Page 19 of 41
P1[J[JCI IUTA 11
CORPUS CHRISTI FIRE DEPARTMENT
WEEKLY MEDIC UNIT INVENTORY
Front Line and 1-B Only
DATE:
UNIT DESIGNATION: M — UNIT# 55
INVENTORIED BY: CAPTAIN:
AIRWAY BAG SUCTION or AIRWAY BAG MEDICATIONS IN MED BOX
0 1 ADULT BVM 111 PORTABLE SUCTION W/TUBING 'Replace meds within 30 days of ex>l date.
[j 1 Each BP CUFFS:ADULT/THIGH 0 1 YANKAUER TIP (1 1 ACETAMINOPHEN BOTTLE 500mg
111 STETHOSCOPE [11#6 or#8 FRENCH CATHETER []1 ACETAMINOPHEN ELVER 160mg/5m1
01 LARYNGOSCOPE HANDLE 01#14 or#18 FRENCH CATHETER 0 3 ADENOSINE 6mg/2m1
0 1 EACH INTUBATION BLADES PEDIATRIC BAG (33 ALBUTEROL 3m1/.083%
MILLER 4 & MAC 4 [11 BROSELOW TAPE or PEDI SLIDE 0 4 AMIODARONE 150mgl3m1
[]1 EACH ET TUBE:6, 7, 7.5, 8, 8.5, 9 [11 SET PEDI ORAL AIRWAYS 0 1 ASPIRIN BOTTLE 81mg/tablet
0 1 EACH KING TUBE: 3,4,5 0 1 EACH BVM:CHILD&INFANT 0 2 ATROPINE 1mg/10m1
[1 1 ADULT TUBE HOLDER 0 1 PEDI LARYNGOSCOPE HANDLE [II CA GLUCANATE 10%IV 1gm/10m1
[11 ADULT ETCO2 DETECTOR 0 1 INTUBATION BLADE EACH 0 1 CA GLUCANATE 2.5%GEL 25gm/tube
(]1 ADULT STYLET MILLER 0, 1, 2, 3, 0 1 DEXTROSE 50% 25gm/50m1
[]1 BOUGIE TRACHEAL TUBE INTRO MAC 2, 3 0 2 DIAZEPAM(Valium®) 10mg tubex
0 1 LARGE MAGILL FORCEPS 0 1 PEDI STYLET 0 1 DIPHENHYDRAMINE(Benadryl®)SOmg/1m1
0 1 ALUMINUM 02"D"CYLINDER WI REG. 0 1 SMALL MAGILL FORCEPS [11 DOPAMINE 200mg!5m1
0 1 02 WRENCH 0 1 EACH ET TUBE. 3, 3.5, 4 []1 EPI 1:1000 trng 11ml
0 1 SET ADULT ORAL AIRWAYS 0 2 TONGUE DEPRESSORS 0 3 EPI 1:10,000 ling/10m1
0 1 10 CC SYRINGE 0 1 PEDI ETCO2 DETECTOR 0 1 FUROSEMIDE(LASIX®) 40mg/4m1
[]1 HAND SUCTION 0 1 MECONIUM ASPIRATOR
01 BULB SYRINGE 01 PEDI TUBE HOLDER []1 GLUCAGON 1mg/m1
0 1 GLUCOSE PASTE 15 grams
[1 2 TONGUE DEPRESSORS [Ji#6 or#8 FRENCH CATHETER
0 1 ROLL TRANSPORE TAPE [1 1#14 or#18 FRENCH CATHETER 0 1 LABETALOL(Normodyne) 20mg/4m1
0 2 LIDOCAINE 100mg!5m1
0 1 2"ROLL CLOTH TAPE 111 BULB SYRINGE 0 1 MAGNESIUM SULFATE 50% 5gm/10m1
[]1 NASAL CANNULA 02 1CC SYRINGE 0 1 METHYLPRED(Solu-Medrol®)125mg/3m1
[]1 NON-REBREATHER []3 18 GAUGE HYPO(DRAW)NEEDLES 0 2 MIDAZOLAM(Versed®) 525mg/3
0 1 NEBULIZER SETUP 0 1 INFANT 02 MASK 0 2 MORPHINE SULFATE mgI I I
0 1 ADULT AEROSOL MASK 0 1 PEDI 02 MASK 2 MORPHINE(Narcan®)FATE10mg/ 2
m1
[]1 CHEST DECOMPRESSION KIT 0 1 PEDI AEROSOL MASK []1 NNITROSTAT SPRAY 2mmg i m.dose
2m1
[]2 AMMONIA CAPSULES 0 1 INFANT B/P CUFF 0 1 ONDANSETRON(Zofran®) 0.4mg/ l
[]1 AD PULSE OXIMETER(if not on monitor) 0 1 CHILD B/P CUFF [11
SODIUMNANETRON 4mg!2 !50mi
01 EACH CPAP Mask S,M.L [1 1 STETHOSCOPE 0t0meq /50m1
04 PREFILLED SALINE FLUSHES 01 TRANEXAMIC ACID(TXA) 9
[12 NS 100 ML
0 2 MINI DRIP SET MED BOX SUPPLIES
0 2 START PAKS [1 1 GLUCOMETER
TRAUMA BAG LI 2 I-PADS 0 1 BOTTLE GLUCOMETER STRIPS
0 BANDAGE SHEARS []2 of each size angios 0 METER CHECK PERFORMED
[]1 PENLIGHT 20,22,24 GAUGE [[10 LANCETS
111 B/P CUFF-ADULT 0 1 ROLL t"TRANSPORE TAPE []1 THERMOMETER WITH COVERS
0 1 STETHOSCOPE 0 6 2X2 SINGLES []10 BANDAIDS
[12 NS 1000 ML 0 4 4X4 SINGLES []6 I-PADS
0 2 MAXI DRIP SETS []10 PEDI BANDAIDS 0 10 MEDICATION LABELS
0 6 START PAKS 0 2 PEDI IV BOARDS []1 CARPOJECT OR TUBEX INJECTOR
[]4 EACH 16,18,20 G.ANGIOS [1 1#5 FR FEEDING CATHETER 0 2 NS 500 ML
[1 2 22 GAUGE ANGIOS 0 1 EACH DRIP SET: MINI&MAXI
0 2 24 GAUGE ANGIOS TRIAGE BAG []6 START PAKS
[12 TONGUE DEPRESSORS [11 EACH TRIAGE TAPE: 0 10 ALCOHOL PREPS
[I 5 VASELINE®GAUZE GREEN,YELLOW,RED.BLACK [1 3 EACH NEEDLES:18,21 or 22 GAUGE
[1 3 4X4 TRAYS(BOATS) 0 25 TRIAGE CARDS 0 4 PRE-FILLED SALINE FLUSHES
[)5 4X4 SINGLES 0 1 TRIAGE BELT 0 2 1 CC SYRINGE
[1 5 2X2 SINGLES 0 1 CLIPBOARD 0 2 10 CC SYRINGE
0 2 STERILE DRESSINGS 03 16 GAUGE ANGIOS
0 2 MULTI—TRAUMA DRESSINGS EZ-IO KIT [16 EACH SIZE ANGIOS: 18,20,22
[]4 2"KLING 0 1 EACH EZ-IO®NEEDLE: 45,25&15MM 0 1 ROLL TRANSPORE TAPE
0 3 KERLIXT"' 0 1 EZ-100 DRIVER 0 4 MUCOSAL ATOMIZATION DEVICES(MAD)
0 4 TRIANGULAR BANDAGES
111 TOURNIQUET DIAGNOSTIC EQUIPMENT CAB
0 2 1"TRANSPORE TAPE 01 CARDIAC MONITOR w/ 0 1 TOUGHBOOK
[12 2"CLOTH TAPE ROLLS 2 ADULT HANDS FREE PADS 0 1 PAIR BINOCULARS
0 1 RING CUTTER 1 PEDI HANDS FREE PADS 0 2 FLASHLIGHTS
0 1 BOX ADULT BANDAIDS 5 6-PK.ADULT ELECTRODES 0 1 HAZMAT GUIDE .
[12 COLD PACKS 5 4-PK.ADULT ELECTRODES [11 BOX EXAM GLOVES
[l 1 BOTTLE ALCOHOL 12 PEDI ELEC1RODES
[1 1 BOTTLE PAPAIN MEAT TENDERIZER 2 in line ETCO2 DETECTORS
0 2 SHUR GLENS®WOUND CLEANSER
0 2 ROLLS COI3ANIM Revised: March 12,2018
Page 20 of 41
SYSTEM REQUIRMENTS: Appendix
Line 40, Number 3
ill Incident Report Codes n
p ` k
al Occupancy Management Codes Setu ! t
0 Staff Activity and Training Codes
0 Equipment and Inventory Codes s
II Hydrant Management Codes .QPbons••• f
;'
El Invoicing and Accounts Receivable Codes
11 System-Wide Codes I y
Battalions 1 t
Census Tracts
-Counties r
--Country
-Departmental Event Types
-Districts
-Divisions
-Ethnicity i
••FDID Numbers
-FIPS County Codes
I
••Gender ( '
Insurance Companies/Agents
Phone Number Types
Race i
Shifts
-Stations
•-Townships
--Units
Zones
Il Cities,States and ZIP Codes
DM Individual Name & Identification
*Property Information Codes
Iji
Streets Close
-Street Names y l
FDID AYsmDate AlgmTine InoiledWurraer Erpoeue, ,-Simon Occupancy.
ccupan IDID
05/2/2019 Fh.#¢ ? 14001^9989 D�0 . 1.x j 1620SPID
SPms � �� z. I �� �� I j
Basic I-Artm
s&Persael I$03131 7110 1 Pioperty&involvement I Additional Repass I Incident Ha tredve I Other...I r Onside Lock
Scene Addwss Number Praia SeeeUHgixvey _ T SAN 1 _ --
T 162o I' F ,� Y
.i.. av .., .{ .i -.N .'�,."fir .6: > up s F`r 1Fi1.. -
Vi016 ,.:-.2.,i,,,Y:.' Y Address LAO 2
Palk 4... . . • IShe'SheetIType IShcir IDistict ICensus ICom*A
r Address onwddandR podI i AGUA DULCE AGUA DULCE 11 Frd..
--------- ®ALICE ALICE
IAid Given etReceved Cay til CC CORPUS CHRISTI - aaw
10TH ST
,P 'jiName I .r rIrrr;:'j"�} r 11TH ST
127H ST
_1 Sppn4ic Propestp Us. .IncidentType 14TH ST €A I
5 • JJ Day care,or commercial -J 15TH Si
16TH ST Delete
17TH ST
Time I11LM-0CLR:000537) Actions Taken - 17TH ST S8 Y.erge.
Oepetd1Noti fie• : j 1852PASS
Code-- ? Desch 18TH ST f
-N 19TH ST 1i'Wrs-- I
NAM Scene ! h x ,.5 19TH ST
11 201 ST
_ 20TH ST
LastCYScene ai'. ': 21ST ST
_ 22ND ST V
14 4 I .► I oil t�Naw hirer rs ..wddenrode: .. .. - rDefault Sart byDesaip5on
iiiiimi c
A
Page 21 of 41
SYSTEM REQUIREMENTS: Appendix J
Number 4
J SP7 B j' D5/W2O19 .J 19-0(9%9 I MO J J J 116220 P Dr'D
FDID • detmDee, �' I entNumber Eipostse Skprin
Ste"
Aasio I Units;Personnel I He*voore I Propbrty&Involvement I AddiiioneeReports I Incidentlienalive,I Qther...,I r-Nerrisie Lock
Scare Address Nimbi Refs SdeelMiSpeey Type Suffix ,.
Type .el 1620 I' DR we
Y :0 AddressL se ._._.
r Address on Wildland Report
Eield-Level'Rulas and DetauRValu9s (r1'r.;rrd Lai el P,ul.s I Custom Form Caption I]
AO Given or Received Cry
Hi¢i¢rt a field name n the fat on the left to view n1x and default vaMee associated wrlFi that field on the right.Use the buttons
ni J I None D below the let at right to modify default values or riles for this field.
Specific PsopertD Use Incident T! .Field Name Caption
STREET Street Name Require field when:ADOR TYPE=1 OR ADDR_TYPE=
Day care.In commercial 1-- 1 I Disable held when IEMPTY(OCCUP_ID I AND!goApp.In
Times(AUL)CI.A:00:05:31) Actions Ti
Dispatch Not >' J code
Fast avScene J
Coirolled J
Last CY Scene £,31
I/14 I ► I 11 I D New, I
I •Sister, n'
UseeDe1i ed
•
J Add OpQrr I Delete
r Show only user-defined rules
Disable al non retpied Fields I Enable al non-required Fields I genet I 0K Cerrcel
Page 22 of 41
SYSTEM REQUIREMENTS: Appendix K
Number S
FOU' lys!°#4 Ali1i .Ylotii iilhulbM 404'6, Slam ; 04ig n. ID
(SNOB j {05/2//2819 Jmom1&081998H 1000 J i J I1620SPID
lase 11n1s k Peed Y
Uig Name LillF
M10 MEDIC 10 '11..i.I em mi I*kit(lelllalt code •LD.sci I TYPe''Erns Type IFdd 'A 1 r
U5 U TILITY VEHICLE 5 00 SP706 —, I
Hawse COB - li ADM ADMINISTRATION
- r ,gency - - I ANNAV ANNAVILLE �eW 1
•-AV700 ENGINE 700 11 SP502
(2UdlecabkIed -E71 ENGINE 71 11 SP502 I
•M71 MEDIC 71 76 SP502 DM
Pelaonnei f TMip Tit-,91 S SB:SEtV M72 MEDIC 72 76 SP502
Stall) Nom IU EMS EMERGENCY MEDICAL SERVICES �a�
I UtIt NaLlled `, FB FLOUR BLUFF p 1
-E94
UniEnsnENGINE 94 11 SP508
is 'J I-E95
ENGINE 95 11 SP508 f��8,.,
-FBFD FLOUR BLUFF SUPERVISOR 92 SP508 I
Canc0led .JIII
FP FIRE PREVENTION
LOCAL EMERGENCY PLANNING COMMITTEE
LEPC JiKM*..
mod,sc IU LOGIST LOGISTICAL SUPPORT —��•J
4I - i —,j 0 NAVY NAVY
•NAW1 ENGINE 11 SP706
0PeigisdrxWdt61/ •-NAW2 CHIEF SUPERVISOR 92 SP706
ElsaledJ R, INAW3 TRUCK• •^'.^ 12 SP706
f-NAWM1 MEDIC UNIT 70 SP706 �.
1 ( SacknSYc 1 , -
1/ ► ►� .. i Shoe/HiidenCcdeo...._ rDefault Soft byDescription
Back atHome r-".l'
I
11
IIII111 ► I ►1-I
.z.1 Cancel I
Page 23 of 41
SYSTEM REQUIREMENTS: Appendix L
Number 10
a , ,-
Select a Quits, . '
' 'List NFIRS Incidents by Alarm Date Jdew Quer ' Qey Primte:. -I
Ina;N 'Exp Alm Date Ah Time ®Inc'Type Addiess GboCrtaUr rt ®',
19.0020041 0 05/21/2019 16:42:10 03 8E29':•vOOLDRIDGE RD II
19-0020040 005/21/2019 16.40.43 08 2145 KAREN DR
19.0020039 0 05/21/2019 16:26.53
19.0020038 0 05/21/2019 16:26:43 15 15937 SAN FELIFE DR
19-0020037 0 05/21/2019 16:25:49 10 HV,h'286
19-0020036 0 05/21/2019 16.21.16 11 4710 EVERHART RD
i. 19.0020034 0 05/21/2019 16:20:24 07 622 OCEAN DR No Incident found on arrival at di<patch a
19.0020035 0 05/21/2019 16:20:13 01 546 SCOTT DR
190020032 0 05/21/2019 16:15:04 05 1301 ANTELOPE ST
; 19.0020033 0 05/21/2019 16:14:47 17 7018 CHISWICK DR
19-0020031 0 05/2112019 16:0919 06 4713 COVENTRY LN
19.0020029 0 05/21/2019 15:54:14 03 2002 MORGAN AVE
19.0020030 0 05/21/2019 15:53:32 11 100 BUCCANEER DR ID
190020028 0 05/21/2019 15:53:26 08 5201 KOSTORYZRD
q. n7nn77 n nI71/7n1 q 15 ci nq nq aqn VCM rr FVF DR w
4
A9Appficable Recede I 60,000 Records/9 Selected 114114 CI Ltd 12II
ep6als... I OK I Cancel I
Page 24 of 41
IMPORT/EXPORT REQUIREMENTS: Appendix M
Number 8
Edit Reports Graphs Maps tools Administration Form Window Help
NFIPS 5 Incident Fc nrrino F %Y»se721', .'''':';''','.S�Yrti l it > P
._:_,,,.....,4,,,,7,t..1.1...,:.,,.,p +w , r y,3 I d� 'i; $ *a'`,,,,t "] 54 h x i r e ai i
........A 'I'k.,:� 'r rs t�� `I .(.'34ar ri`lsi`'n �I=.n 't r ..: 3r•E ;,it 1 i; hlrt c a� KIt'Armi Qer
{;, ,W**f •k : yiiirir ,ii yf % E ort tlFlN . Ir.m-ari r FiIi,
T �.R't A .IFaVN.ur�xY�"ra 13 �` �0 f .�1
';'''.1,"4,,,11,', 4';3if --- fR'r ' ::, � dy l rI f y. k''''Ap Sti ` r.Ir.OA;
rk,L: i". I I pl r
01:.';,.. ..: •i Mlit nt ;�;} �°i gat W r 4r M:m , I :I I ':ii1
fl '' t� h ', �44 i rF , ±.,
t`:.i'•- til., t 'i4,t•r it Ari a? rF i'4 ,1�7,,_� a�wvC,,4.-.4.,...
$4 , •,,,,;,,,,,IA, f O'Onde':
Itt-' It 1 'qt ISy� tT.l j> 1�f1us5 Repot CR I 7",
fet '''.. f0''''''' ..':*'-' ,:r.< • .. ReJtew Impitiited HEIRS Data 41 ilrrl;• ''' rid I'
Classe
*i7i'tiiHrici Pregre res and Certifications ►. C,,-.I r r npe
i#Staff 5i:bed inq
Rpperatus,Equipment and Inventory i ii
FcI J I
(er tior Records
Dhifle&Al trma 1
i tb'drgnt Mar anent ._
�r:, Su' '-�cr
Add
Ag E4 �.
kal trlvdl7n0and Paibhr rMs >
I I.r.,
it Departrrr+xrst 2ournal LI i-
. 1 1 I 11
iPtiOn
�ePartmeratE�ents 911 Uses
5 Daly Reminders ' J I M etrocamn
�y .
'Name Search M c . Type r,'plarrn
eR 5tatioh Management l -J
fa Lock Workstation Shift+F9 _
41.4 Ept 1 w Ea'e X Delete JI Pic ktCkrse
This wizard will guide you through the process of exporting information to a transaction file that can I
be imported into a State or National database. Select an operation to perform: l
i
':[Export Completed Ineident Transactions Only;
This option will export completed incident reports for a selected FDID within a date range youl
specify.Departmental information will NOT be exported.
r Export Completed Incident Transactions and Department Information
This option will export completed incident reports for a selected FDID within a date range you I
specify.Departmental information WILL be included. ,
{
C Export Department Information Only }
This option will export a fire department base information only.Before any incident
report files can be exported and imported at the state,a Department Information file I
must be exported and imported by the state agency. An export file must be created
for each FDID number you are reporting for. All Department files created end with
a".dep extension unless otherwise changed at the time of export.
Help I << Back I Next>> I Finish Cancel
t
Page 25 of 41
JOURNAL: Appendix N
Number 1
W
Lina Display to items iro.voiving x
Stations(s) Shuts) Units)
I J (-JE3
s Staff Member(s)
I .
r Hide items with no Station set
r Hide items with no Shift set
r Hide items with no Unit set
r Hide items with no Staff set '"
Clear Filter ( I •Apply Filter Close
,„ t
;:i.;. -:. . 7�::. r :..: e xry..>f:;-., z.ll k..J: s'-'''-1...''' I,�• .: . ., Y?:xn,.r.4...,.n 1,`' , r_..c,:, .„ ,,.'-:4'-',11'.1, {... s�s'�:�i
Tue May 21,2019
., May 2019 Stmt t End I Desc iption
' 05/21/2019 05/21/20191 I:
'�• 1119.0019947 2928 MORRIS ST
• 0757:50 0816:13
n - -
� O52/02019 OB5nB0
19i1.1.1-9--00-19944 SA8INAS ST
Sun Mon Tue ...
.-._
Wed Thu Fri SM 05/21/2019 05/21/20191
09 55.58 -1014 04 019-0019962 •3829 DAVID ST SB
05/21/2019'05/21/2019 -i
. 1 ,$, 2 ,�, 3 d �, 1248:25 '13:16:43 819.0019995: .134CLEMMERST
osnlnms asnlnols — — -_I
1.1 15:1Z21 I15:30:44 8190020022 721 WEST POINT RD
3 - Station FP.SNR 4:CONSULTATION-GGenial-ARAS SEAFOOD -1
05/21/2019'05 212019EAND STEAKS-6917 S STAPLES ST/CORPUS CHRISTI,TX 78414 1
_ 15:45 16:00 'Inspector MAR TINEZ,DAVID
..
12.5• 131. ::.
151617$• 113 ll
19•$• 0i• 22 23 24 25 '
LI i26 i
27 -----28 29 33 31 i1
1
I
JI RIS r�
-C"Use Selected Calendar Date Requay I I'm- *I� j j1 7 �I>t 7
Fdta.mg SNtTmes I Elptions I New. Edd I pelete I obit I P Gose I'
Page 26 of 41
DATA ENTRY: Appendix 0
Line 61, Number 1
Sled the data table la which you wart to edit a view system ralesIr Sets4c
,.I iso_flyv Fire"Factors Contributing to Ignition ` I
Inc fist Fire"Human Factors Contributing to Ignition
Inc
sup Fire"Suppression Factors -- - - - - - -- -
Inc_slru Structure Fire Reports '.t Is
. ,, ..,�...,:s .-
•
..`,
.Inc etas Civilian Casualty Reports ' y -
Inc cchf Civilian Casualty"Human Factors Contributi ,Bad-Level Rhes and Default Values I Bec/M•Level Rubs I Custom Fam,cappp'1,1 •
Inc_cd Civilian Casualty-Factors Contributing to Ps
•Incises Fire Service Casually Reports '
Highlight a field name it the lid on the left to vew miss end default values asso&laOd wit that field on the right Use the aslant
Inc tceq Fire Service Casualty-Equipment Failures below the ist at right to modify default values a rales Its this fell
-Inc_toss Property Loss and Value Feb Name Caption D • � _
klne_�nsu Insurance Information ipyq}7/hCsjfffJibarMfssI n
=Inc haz HazMat Reports STRU_TYPE Structure Type 1 Disable field when:IEMPTYIInc denlRecord OccuD_IdIF
r-Inc hacl HazMat-Actions Taken BLDG_STAT Building Status
•Inc_hmal HazMat-Materials Released FLOORS__ABO'VE Flcsstn Above
I-Inc_hrl HazMat-Factors Contributing to Release FLOORS_BE LOW Floors Below
e-Inc hmt HazMat-Factors Affecting Mitigation BLOG_LEN Building Length •
rInc wild Wildland Fire Reports BLDG WIDTH Building Width •
Inc wcrp Wildland Fire•Primary Crops Burned " TOTAL AREA Total Area •
1-Inc wthr Weather Conditions -
Inc wign Wildland Fire-Factors Contribuon•',, x�: •
I-Inc wsup Wildland Fire-Fire Suppression Fe,.' •v s 5s..r/-,,,,,,,,,Y,. r, y v';" tai.."�'. .y„ -- P-,".,_...1,,,n,(7.—:
.r""'{.
*-Inc whf Wildland Fire•Human Factors Cort( Require fieldefways
;Inc ars Investigation Reports I` f
-Inc amot Investigation-Suspected Motivatie,,_Require field when the following expresalon evaluates to true J _ ."
Inc_ainv Investigation"Apparent Group INUST(LEFT(STRU_TYPE,1L1";'TJAND FLOORS_BELOW-O J
1-Inc_ainf Investigation"Other Investigative •
•
-Inc aobs Investigation-Initial Observations
.-Inc J ''jalab Investigation-Laboratories Used J II
;"Inc aevi Investigation-Evidence Collected':
I].UserDefned
Dose
I_ c,.... Opel Delete I
InCT n000 J
r Show only suer-defined rales
Disable al rhorrreglied Rebs I Enable al rhorttegi ed Fabs Hetet , OK I Centel I
Page 27 of 41
Appendix P
RMS Scheduling Module Request:
On-Duty Daily Staff list section:
SW.10,i,,. ...:I NMI* ': . . '''.:1 Ate Cone l HOW I Pwai:I Stiatlinti I HaufetAll Stilt I NahaiSI i I Stitt Doti ILEnd D&e 1 End Ti iw i.A
0 Working Stall on Duty
f Station 01
IlUnit E1 (1 ACTC.1 ACID,3 total personnel) (1 FF,2 LM,3 total personnel)
-11789 SCANLAN,GARRETT T ACTC ACTC LM 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
-8571 SHELBY,NICHOLAS C ACID ACID FF 0800:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
. r_
IlUnit M1 (1 ACTE,2 total personnel) (1 FF,1 LM,2 total personnel)
110636 PENA,HERMILO ACTE ACTE FF 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 0800:00
7552 WARD,BRYAN K OD LM 08:0000 24 Yes Yes 05/16/2019 05/17/2019 08:00:00 :
("Unit T1 (1 ACTC,3 total personnel) (1 EN,1 FF,1 LM,3 total personnel)
2591 RODRIGUEZ,ANTHONY OD EN 08:00 00 24 Yes Yes 05/16/2019 05/17/2019 08:0000
13872 SHICK,CASEY L OD FF 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00 •
6000 YANEZ,ALONZO ACTC ACTC LM 08:0000 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
E Station 02
Unit L2 (1 ACTD,3 total personnel) (1 FC,1 FF,1 LM,3 total personnel)
2392 CORDOVA,RAY) OD ACTD LM 08.00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
4151 PINKERTON.MICHAEL S OD FC 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08 00:00
10640 RENKEN,ERIC L 00 FF 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
Unit 142 (2 LM,2 total personnel)
14141 DENTON,JAMES R OD LM 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
8589 PIERCE,BRENDAN S OD LM 08:00:00 24 Yes Yes 05/16/2019 05/17/2019 08:00:00
(Staff ID, Name, Activity Code, Role, Position, Start Time, Hours,All Shift or Not, Is It Normal Shift, Start
Date, End Date and End Time)
Stations listed
Units by Stations
Personnel by Units
All Staff as normally assigned list section:
Staff)D . :Name .l Act Code I Role(s)'Position I Start Tine I Flouts I AI Shit I Normal Slit I Start Date`l End Date. I End Time I A
NI All Involved Staff
f Station 01
Unit El 1 ACTC 1 ACID.3 total iersonnell 1 FF,2 LM 3 total ersonnel)
(;r=#ir ;•x yr iw r T a'L� Ln �,aa 7 "'H i SII 6 5� t i �;,1 A'h'� ae Pi i it y
1 ti ! o.: .1f53 i;, ,,� � V Y r IiI1ii', [wi t4i,J .* a _i,, .::. i;,
-11789 SCANLAN,GARRETT T ACTC ACTC LM 08:00:00 24 Yes 05/16/2019 05/17/2019 0800.00
-8571 SHELBY,NICHOLAS C ACTD ACTD FF 08:00.00 24 Yes 05/16/2019 05/17/2019 08:00:00
i/ C;,..'.(..1''':e�.._,#1 Sr Iia .A .#--t6 1 :�y,c s�R`9 4.` i HI 1A. ! i 9p Rt.14 :-.I1 111' I i j I. 1 ] i.IF
?' ' i-V,.i. TF# <.�, i .A C 1 t is l_i i ?e -.!' 'ar.S .,,,::‘.i •:I t`,
,d. �I. 11 li, � a, I yl�;k+ L .E� �. tf 7. is ).;; ..P. i1 1. -.
Unit M1 (1 ACTE,2 total personnel) (1 FF,1 LM,2 total personnel)
F10636 PENA,HERMILO ACTE ACTE FF 080000 24 Yes 05/16/201905/17/2019080000
7552 WARD,BRYAN K OD LM 08:00:00 24 Yes 05/16/2019 05/17/2019 08:00.00
Unit T1 (1 ACTC,3 total ersonnelJ 1 EN 1 FF,1 LM,3 totalpersonnel
2591 RODRIGUEZ,ANTHONY OD EN 08:00:00 24 Yes 05/16/2019 05/17/2019 08:00:00
13872 SHICK,CASEY L OD FF 08:00:00 24 Yes 05/16/2019 05/17/2019 08:00.00
6000 YANEZ,ALONZO ACTC ACTC LM 08:00:00 24 Yes 05/16/2019 05/17/2019 08:00:00
I—Station 02
Il Unit L2 11 ACTD,3 total ersonnel (1 FC,1 FF,1 LM,3 total personnel)
6JEliA�l Otho 1�V1 €+"' ,4IXEM _ . �i2 .t :: 1 k#4.c .E .
k2392 CORDOVA,RAY J OD ACTD LM 08:00:00 24 Yes 05/16/2019 05/17/2019 08.00:00
FLF 4151 PINKERTON,MICHAEL S OD FC 08:00:00 24 Yes
05/16/2019 05/17!2019 08:00:00
10640 RENKEN.ERIC L OD FF 08.0000 24 Yes 05/16/2019 05/17/2019 08:00.00
IlUnit 142 (2 LM,2 total personnel)
14141 DENTON,JAMES R 00 LM 000000 24 Yes 05/16/2019 05/17/2019 08:0000
8589 PIERCE,BRENDAN S OD LM 08:00:00 24 Yes 05/16/2019 05/17/2019 08:00:00
(Staff ID, Name, Activity Code, Role, Position, Start Time, Hours, All Shift or Not, Is It Normal Shift, Start
Date, End Date and End Time)
Stations listed
Units by Stations
Page 28 of 41
INVESTIGATIONS: Appendix Q
Number 4
Di»p. Irne*etign ID . FDID Alarm Date Incident Nrfmber`
111320oo2 SP7o6 105102%2019 1190117168 J
Bye I$efeaais I Evidence I 010102.1 Fire/irson'I Leadtljrwoivements I Sger e I MOvitied Narrative I tither I
Stat Date Case States Stet*DaDate Corapl
• 105/02/2019 J ..I Investigation closed 05/13/2019 J 0 Linked Investigations I
Case Investigators Laboratories Used r None
Code- ? Description i .+ I Code ®Description 1 ` +
C, F210 J Johnson,D . ,++ 1 N N None ++
. T ,
:1 4, 1 I 4.
Initial Observations Othel In esfigalive lrrforeration
Code ? Description J + Code ? Description i J +
4 Doors unlocked ++ 1A ,I No Involvement _ ++
r *6 =J
ii I i I I N I D New I 4fi Browse • Save I )C,Delete I rje Print... I k1 C1ose I
.6 .. s c,,. .r. ,,*.) 4; J. .t,4-".5; ,._:tnr 1,"-•,`,1', r3 .:-V• a , ,` ..1_ 1.ra r,5.,..r
Description Investigation ID FDID Alarm Date Incident Number
A l'`.;–i , l `,.'r l , s txl,lifI . „s. xE . ,x 111320°02 St 706 05/0212019 190017168 J
Basic I fieferrals I Evidence I Photos [rel son I Leads/jnvolvements I Scene I Activities I Narrative I Other I
Extent of Fire Involvement on Arrival
f3 J I Flame and smoke showing Suspected Motivation Factors r Unknown
Property Ownership Code ? Description +
r—J I Private
001 N/A Accidental Fire ++
Avariabity of Material First Ignited is
U1 J(NIA Accidental Fire y.
Entry Method Apparent Group '••i
001 IIN/A•Accidental Fire Involvement r None r Unknown
Incendiatyrr Methods/Devices Code ? Description +
Ni •
J NIA-Accidental Fire ++ontaier
—
NN1 JN/A.Accidental Fire ._
dDelay Device -I
Ni -1 ,,,II N/A Accidental Fire
Fuel r Person involved in ignition of fire was a chid or juvenile
FT 1 _JI N/A Accidental Fire under the age of 18. •
ii 1 ► N I D New tli0 Browse ® Save X Delete to Print... kI Close
Page 29 of 41
Appendix R
RMS ITEMS -SPECIAL SERVICES NEEDS
STAFF MANAGEMENT-
A. Basic
1. Name
2. ID number
3. Address
4. Phone number
5. DOB
6. Hire date
7. FIDO PIN
8. EMS Reg#
9. PID #
10. FEMA SSID
11. Rank
a. Effective date
12. Status
a. Active/inactive
i. Effective date
b. Deceased
i. Effective date
c. Part time
i. Effective date
d. Retired
i. Effective date
e. Resigned
i. Effective date
f. Terminated
i. Effective date
g. Temporary
i. Effective date
h. Volunteer
i. Effective date
13. Shift
14. Station
15. Unit
16. Current Age
17. Years of service
B. Certifications/qualifications
a. Expirations > notifications of upcoming exp.
b. Sorting capability by certifications, rank, shift
Page 30 of 41
c. Upload Certifications
****Ability to generate lists by
• Rank
• Seniority/promotional date/hire date
• Certification
TRAINING MODULE -
1. Class— bridge information to personnel information staff page
a. Description
b. Date/time
c. Location
d. Agency providing training (CCFD, TEEX, TDEM, etc.) Customizable.
e. Type of training (Fire, Medical, Hazmat, Rescue, Other)
f. Shift
g. Station
h. Hours
i. Method (Classroom, drill, online, etc.)
j. Attendees
k. Certificate Awarded — Upload Ability
2. Notes
3. ISO Categories
a. Night Drill (Yes or No)
b. Multi Company Drill (Yes or No)
c. Single Company Drill (Yes or No)
d. Auto Aid Training (Yes or No)
e. Driver Training (Yes or No)
f. New Driver Training (Yes or No)
g. Officer Training (Yes or No)
h. Company Training (Yes or No)
4 Casualty a `orE `dura g t'aJn fl
a. Name
b. Gender
c. Age
d. Prior responses during previous 24 hours
e. Usual assignment
i. Suppression
ii. EMS
iii. Prevention
Page 31 of 41
iv. Training
v. Administration
vi. Logistics
vii. Maintenance
f. Physical Condition prior to injury
i. Rested
ii. Fatigued
iii. III or injured
iv. Other
g. Severity
i. Report only
ii. First aid only
iii. Treated by physician, no lost time injury
iv. Moderate severity, lost time injury
v. Severe, lost time injury
vi. Life threatening, lost time injury
vii. Death
h. Taken to
i. Hospital
ii. Doctor's office
iii. Morgue or funeral home
iv. Residence
v. Station or quarters
vi. Not transported
i. Activity at time of injury
i. Driving or riding in vehicle
ii. Operating fire department apparatus
iii. Extinguishing fir or neutralizing incident
iv. Fireground activity/Suppression support
v. EMS/Rescue
vi. Station Activity/Training
j. Injury
i. Primary symptom
ii. Primary area of body injured
iii. Cause of injury
iv. Factor contributing to injury
v. Object involved in injury
vi. Where injury occurred
vii. Relationship to structure
viii. Specific location
ix. Vehicle type
Page 32 of 41
x. Protective equipment contributed to injury
k. Narrative
SAFETY& HEALTH—
1. Injuries
a. Location
i. Fireground
ii. Non-fire Incident scene
iii. Responding to or from incident
iv. Training
v. Station activities
b. Type
i. Burn
ii. Smoke inhalation
iii. Other respiratory
iv. Burn and smoke inhalation
v. Wound, cut, bruise
vi. Dislocation, fracture
vii. Heart attack or stroke
viii. Strain, sprain, muscle pain
ix. Thermal stress (Heat exhaustion, frostbite)
x. Exposure to infectious disease
xi. Other
c. Cause
i. Exposure to fire products
ii. Exposure to chemicals or radiation
iii. Fall,jump, slip, trip
iv. Overexertion, strain
v. Contact with object
vi. Struck by
vii. Extreme weather
viii. Other
d. Exposures
2. Light Duty/Lost time
a. Days/time
3. Vehicle Accidents
a. Preventable
b. Non-preventable
c. Disciplinary action completed
**Nice to have -Tie injuries, light duty/lost time, & accidents to personal profile page
Page 33 of 41
6/12/2019
Attachment A-1 1
1 -Technical Proposal
2-Demonstration Scoring Matrix
Fire RMS Business Requirements Matrix I Priorty Vendor
Response Comments
IReq# I Requirement Description I M/E/N Y/M/N
A General Requirements ,
f System will be capable of supporting NFIRS(current version and subsequent
1 versions) M
System will be capable of importing legacy records adhering to the NFIRS
2 file formats M
Integrated with Maximo, ESRI, Infor,CE Solutions and share at minimum,
3 incident demographic and time data E
The system will allow the ability to attach documents including,but not
limited to the following types:
a.video
b.pictures
c.documents(spreadsheets,word docs,notepad,etc)
4 d.PDFs M
Fire incidents using data elements from NFPA 1710/1720(Appendix A for
51details) M
Department Leaders can access certain system level configurations and run
6ldata queries and reports based on records entered by their department M
System must have an audit trail in order to show if any changes were made
for quality assurance or legal purposes. Audit trail should:
a.track
b.capture
c.display key-stroke entry level changes
d. To include all changes made to any records,not just last update.
7 M
Software solution must work with any hardware including PCs, Laptops,
Android and mobile devices with the exception of any devices that are
8 unsecure. E
Software must provide means to display administrative messages or notes
entered and link to individual event records and/or users(e.g. internal
9 messaging or notes)(Appendix B) M
10IQC Reports for completeness and accuracy(NFIRS reports) M I
Electronic signatures for maintenance checkoffs and other items,such as
11 permitsoccupancy E
12IActive Directory functionality M I
Scheduling system capable of viewing previous,current and future schedules
13 with a task manager to create schedules(Appendix C) M
Add and update department of employees certification. Notify department of
14 certification nearing expiration date. M
Add fii11 employee information such as:
a. Employee contact
b. SSN
c. Drive license number and expiration date
d. Certification
e. Notes
I EmpI ID
g. Rank
15 (Appendix D) M
16ICustomize data and label fields { M
17 Historical data with import/export capabilities(Appendix E) I M
18ICreate and customize dashboards (real-time) I E
Priorty
M=Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N=Nice to have N=Not available or included Page 34 of 41
6/12/2019
2
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N YAWN
Search for record by:
a. Date
b. Address
c. Name
d. Incident#
19 e. Etc M
Capability to track and manage Fire equipment maintnance record on all:
a.Apparatuses
b.Equipment
c.Inspection records;with due date,status,and maintenance inspections
notes(history)
d. Link maintance records to inspections records.
e. Perform inspections on a mobile environment(tablet,cell phone,etc..)
f. Capability to trigger a scheduled maintance and submit a workorder.
g. Apparatus daily readiness report(Appendix F)
20 M
Capability to track and manage fleet and vehicle maintenance:
a. Automated vehicle system for maintenance on vehicle mileage/engine
hours
b. Schedule and submit a workorder
c. Track fuel usage
d. Inspection records:with due date,status,and maintenance inspections
notes(history)
e. Log all maintenance history records per vehicle
21 f.EMS unit daily readiness report(Appendix C) M
Daily EMS Inventory real time capabilities interfaced with run reports. Bar
22 Coding for inventory tracking. M
Weekly Medic Unit inventory and EMS supply lockers by station(Appendix
23 H) M
8 System Requirments
Allow tiered permissions for various access:
a. to system settings
b. agency settings
c. data entry forms
d. patient data
e. print forms
1 E data analysis tools M
System administrator ability to manage all users and control their ability to
2 manage their profiles or add new users M
System administrator ability to manage locations
a.streets
b.districts
c.stations
d.etc
3 (Appendix I) M
System administrator ability:
a. manage and modify data entry forms
b. selective dynamic display within the data entry form,and the dataset
c. print layouts
d. point-of-entry business rules
4 (Appendix J) E
System and department administrator ability to manage the display of other
agencies at an incident. For instance,adding a unit from a different City that
5 responded to the incident(Appendix K) M
Define when incident is complete with time stamp and related status changes
6 for administrative purposes M
'riorgy Export records to excel.PDF or print M
M= Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N=Nice to have N=Not available or included
Page 35 of 41
6/12/2019
3
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N Y/M/N
Customizeable toolbars(shortcuts, favorites for reporting,queries or any
8 screen and modify user view(user preferences) M
9 Create system rules and default values-required fields M
10 Select multiple items(streets) for any records(Appendix L) M
11 Query tool with delivered queries and modifiable parameters M
12 Reporting tool with delivered reports,includes modifiable parameters M
C Import/Export Requirements
Interface with existing Integraph CAD(Computer Aided Dispatch)software
1 v.9.3 M
Allow integration with data exported from CAD systems.The CAD system
software vendor will provide an output file or other agreed upon secure
2 method for the solution vendor to map and import M
Vendor will have pre-established integrations and data relationships with the
major CAD vendors to make this process more efficient for agencies to
3 implement M
Provide means to import to CAD,at minimum:
-All Fire event times
-Incident address,
-Type of service requested,
-Responding unit numbers and call signs
4 -Incident numbers M
CAD integration will have capacity to re-import data into a record as new
data is added to the CAD record(for example,more times are added as the
5 incident progresses) overwriting or updating the previous data. M
• CAD Data integration will be accessible to use by users with fixed devices
6 (e.g.desktops)or mobile devices,provided the device is online M
7 Import/Export reports, photos,records and attachments M
Imports and Exports will be in compliance with NFIRS validations and data
8 rules for import/export(Appendix M) M
D Journal
Monthly activity tracker for any entry for a specific date to include:
a. on/off feature
b. NFIRS activities
c. non-incident activities
d. dept events
e. training classes.
f. occupancy inspections
g. activities
h. permits
i. equipment maintenance
j. testing,
k. hydrant activities
I. Filtering by:
a. station
b shift
c. units
d. staff
1 (Appendix N) M
E Data Entry
Default values and make them read only or hidden with the value still part of
1 the incident data. (e.g. all incidents are in the US)(Appendix 0) M
Limit provider ability to enter one value,but have that value autofill related
values without letting them access the linked elements. For example. limiting
users to only entering an incident zip code.which will autofill the incident
city,county and state without letting the user access the auto filled fields to
Prior/prevent conflicting or poor quality data. M
M= Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N= Nice to have N=Not available or included
Page 36 of 41
6/12/2019
4
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N Y/M/N
Layout for online and mobile/offline data will be the same without needing to
3 build the forms separately for each system M
System will have a dynamic sizing display that will be able to adjust to screen
size changes with minimal effect on the layout displayed to the user
4 M
5 Where possible,any data entry buttons should be touch-friendly E
Display of single or multi-select drop-down lists must accommodate popup
on screen keyboards on tablets such that the keyboard does not obscure the
6 drop down value list M
Users should be able to navigate between elements in the data entry form
7 using touch,mouse,or keyboard tabs and arrows M
Data Entry form will clearly display elements and values that have an
outstanding point-of-entry business rule to be resolved so users can quickly
8 identify and resolve shortcomings M
Incident form will provide display of the data entry and review status for
9 administrative u oses e. .In Progress,Complete) M
10 Incident formprovide easy interface to import CAD data M
Incident form will provide means for agencies to create and apply localized
11 custom fields. M
Capability of adding narratives on all modules and narrative will be able to
12 print on reports. M
F Scheduling (Appendix P)
1 Manage personnel schedules M
Daily schedules
a. Employee roster.
b. Station location
c. Employee availablility
2 d. Per shift M
Print daily schedule per:
a. Employee roster.
b. Station location
c. Employee availablility
3 c. Per shift M
4 Schedule crews with stations and/or apparatus M
S Schedule inspections M
6 Schedule maintenance on equipment M
7 List leave status M
8 Create leave and payroll codes(customize codes) M
Flexibility to add additional scheduling items,such as available for OT.out
9 on leave,temp driver,etc. M
G Investigations
1 Link investigations to incidents and locations M
Maintain and access history of incidents and investigations attached to
2 locations M
3 Conduct and document investigations M
Investigation report needs the following fields:
a. referrals
b. evidence
c. leads
d. scene
e. activities
f. Narrative
Print capabilites of attachments
4 (Appendix Q) M
Inspections
M=Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N= Nice to have N=Not available or included Page 37 of 41
6/12/2019
5
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N Y/M/N
Conduct various types of inspections such as life safety,building and
1 occupancy based on NFIRS codes M
2 Link inspections to incidents and locations M
3 Perform inspections in the mobile environment M
4 Inspector daily scheduling with inspections scheduled for the day by inspector M
5 Inspection schedule interface to Office 365 calendar N
6 Cross validation to ensure no duplicate records in Occupancies M
7 Add new inspection codes M
8 Merge occupancy CAD information into inspection records M
Permits
1 Track and manage all permits M
2 Permits can be managed through the Fire RMS, M
Manage permit fees,receipts,and adjustments through the City's payment
3 gateway M
4 Users can print or email permits,receipts,and mailing labels M
5 Maintain a record of historical permit information M
6 System to provide pre-formatted permit reports M
7 System to create various types of permits M
1 Validations
Point-of-entry validations/business rules must be able to trigger time conflict
rules against the current time the record is being entered to prevent any time
1 in the future being entered. M
K Printing
System Administrator ability to:
a.design, format and manage report printout
1 b.create multiple formats M
Document attachments and addendums can be printed as part of the primary
printing based on the print layout design by the System administrator
2 M
Print layout and design will allow for agency name,address and logo to be
3 configured and automatically applied to a printing template N
Print layout will provide means to configure a header and footer for each page
such that incident information such as date, incident number,patient name
4 can be displayed on each page of the record E
Vehicle and Equipment Inventory Records
Track specifications on the following-PPE,hose, SCBA,vehicles,pumps
1 hoses. ladders(all items in inventory) M
Vehicle maintenance records and requests with notifications of when vehicle
2 due for maintenance M
3 Usage/Purchased-date/time,code,quantity,cost, mileage,staff,description M
Upload from a Valero fuel report(personell ID,re-fuel ct valero.unit
4 number.fuel,etc) N
M Occupancy:Fire Prevention
1 Owners&Contacts M
2 Inspections&activities M
Add'I Fire service records-chem inv,hydrants,storage tanks,needed fire
3 flows, permits,supplemental history M
Capability of merging occupancies when address is same,must be able to
4 keep all history when merging occupancies. M
5 Tracking of occupancy statistics M
N Training Module(Appendix R)
prior*List classes with description, Date/Time, Location.etc M
M=Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N=Nice to have N=Not available or included
Page 38 of 41
6/12/2019
6
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N V/M/N
2 Casualty report for injury during training to include M
3 Vehicle Accidents N
4 CE hours tracking E
S Scheduled training classes to interface to Office 365 calendar N
O Hydrants
List basic hydrant information,such as location,hydrant number,
1 specifications,etc. M
2 Activities and repairs M
3 All flow tests M
4 Integrated with Maximo for water usage and work orders E
P Reports Module
1 NFIRS M
2 Basic fire reports M
3 List units and personnel M
4 Casualty reports M
5 Property involvement reports M
6 Additional Fire Service reports M
7 Canned statistical or list reports with modifiable parameters M
8 90 percentile report M
9 NFPA report M
10 Alarm response analysis M
11 Incomplete report list M
12 Not QC'd report list M
13 Fire investigation reports M
14 Fire/Arson reports M
15 Add'l reports for actual fires M
16 Set up rules for report fields M
17 Report notifications M
Report repository for all items including reports,inspections,occupancy
18 records,permits,etc. M
19 Query tool M
20 Customizable reports M
21 Ability to set up rules for report fields(required fields) E
22 Logistics Requisiton Form M
23 Maintenance Report(Vehicle and Equipment) M
24 Ad hoc reporting M
kY _. J, - ,is?z'?i f X'rP.ktta r T � .�Y ;i, 1.` t � € ? t} 5 ,y5
T1 Application
1 If browser based, it should work with IE 11 and Edge M
2 Does the application require any install of files on the user's computer
3 If application requires install,can it be remotely managed and patched
with ManageEngine Patch Manager Plus version 10.0.326?
4 We use Netmotion on mobile computers.does your application work with
Netmotion?
5 Application must be a mobile application M
6 Windows 10 compatible M
7 Application must have 24/7 technical support M
T2 End User Support
1 Will application require admin rights?
2 What are the minimum requirements for:
a Memory
Priorty b Processor
M= Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N=Nice to have N=Not available or included
Page 39 of 41
6/12/2019
7
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N Y/M/N
c Storage
d OS
Application must work with IE II or Microsoft Edge and the latest version of
Java, .net framework,etc. No outdated agents of these applications will be
3 supported. M
4 Will an application or client have to be installed?
5 Will Antivirus cause any known issues?
Is your application a standalone application,not dependent on any software
6 that may or may not already be installed on the operation system?
13 . Seryer/Stotyige/Backup
Will the solution run on premises,in the cloud,or in a hybrid solution?
1 Provide the architectural drawings of the complete solution.
Does your solution support a virtualized environment? List supported
2 virtual machines.
What are the minimum server requirements for Memory,CPU,storage
3 and operating systems? List all specifications for all servers.
What are your SAN storage requirements? We currently run Nimble storage
with CS240G.CS260G.CS460G-X2,and CS500arrays. Provide any cloud
4 storage requirements to include provider,services,and size requirements.
On-premises backup solution utilizes Commvault version 11 service Pack
14. All compute data and application data require support of current
backup solution. Provide complete backup requirements including
5 compute, data,and databases.
14 Security
How are security vulnerabilities about the product communicated,and can the
proposed system accommodate the City's intent to apply security patches to
2 its systems within 30 days of release?
Who is the point of contact to raise security concerns or findings about this
3 system?
Will the vendor or the City be responsible for applying security updates to its
4 product?
Remote 3rd party suppport access requires the 3rd party to use an HTML5-
compliant web browser. This can be used to access systems via RDP.
5 HTTP(S)and SSH which is what the city uses. M
6 User authentication and access rights can be managed via Active Directory. M
Please list any required ports,protocols,web domains, firewall allowances
7 needed for the proposed system to function properly as described.
T5 Network •
Must be able to communicate over Ethernet technology and be compatible
1 with wireless,copper and fiber optic methods of data transport. M
Requirements must fit into a minimum throughput constraint to reach
endpoints and a reasonable latency(no more than 100ms)and must be able to
2 recover function after periods of packet loss which may occur. M
Consideration must be demonstrated for reducing the amount of throughput
3 required from end to end across the WAN. M
4 Any wireless host/AP support requirements must be made known. M
The specific services need to be made known in the proposal as to which
protocols will be needed and whether they are considered connection or
5 connectionless. M
For our understanding,a logical network diagram will be provided that
exhibits traffic flow to and from application.database,repositories.end
Priorey points and demarcations. M
M=Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N=Nice to have N=Not available or included Page 40 of 41
6/12/2019
8
Fire RMS Business Requirements Priorty Vendor
Response Comments
Req# Requirement Description M/E/N V/M/N
■Ti►+�ra� F _ '41, i. F �' ll� n y1 ,(.sT �1' �C f: y�
';f4
1 Recommend that the application integrate with ESRI solutions.
Will the application be consuming or interacting with data from the GIS
2 database?
3 Will the GIS data require local storage?
Will the application require GIS editing capabilities?Editing rights are
4 subject to license purchasing.
We are on Portal for ArcGIS version 10.3.1. Is your application
5 compatible?
6 Will the solution be for city and/or public use?
Priorty
M=Must have Y=Yes without modification
E=Expected to have M=Yes with modification
N= Nice to have N=Not available or included Page 41 of 41
Attachment B: Bid/Pricing Schedule
UCENSED SOFTWARE SCHEDULE
(Applications-ESO Billing,ESO Dispatch,FIREHOUSE by ESO,IFC Codes)
1. The Licensed Software term shall begin the earlier of 90 calendar days after the Effective Date or the first day the Licensed Software is used in production
mode("Activation Date").Customer shall be deemed to have accepted the Licensed Software on the Activation Date.The parties will make reasonable
efforts to ensure that Customer is able to use the Licensed Software as quickly as possible,but in no event will the Activation Date be modified for
implementation delays.
2. The following Licensed Software may be ordered under this Exhibit:
2.1. ESO Billing is on premise software for EMS billing(http://www.esosolutions.com/software/billing).
2.2. ESO Dispatch is on premise software for medical dispatch and transports(htto://www.esosolutions.com/software/disoatch).
3. The following Third-Party Data may be ordered under this Exhibit: 2018 International Fire Code,2015 International Fire Code 2012 International Fire
Code.
4. Third-Party Payer is responsible for the following products and Fees:
N/A
5. Customer hereby agrees to timely pay for the following products according to the schedule below:
Contact and Billing Details
Sold to: Kim Baker Contact: Kim Baker Address: Accts Payable 2406
Leopard St Suite 300
Bill To: Corpus Christi Fire Department Phone: 3618263907 Corpus Christi,Texas
78401
Email: Email: United States
Subscription and/or License Terms
Initial Term(Years): 5 Billing Frequency: Annual Customer ID: 201712-13517
Renewal Term(NIA): 0 Billing Method: Email Total Recurring Fees: $20,984.00
Terms: Net 30 Total One-Time Fees: $ 0.00
Product Name Product Description quantity Total Price/
Discounts
FH Cloud Annual Fee Includes 30 Concurrent licenses with Fire,Training,Inventory, 1/Each $20,984.00 x
Occupancy,Hydrants,Staff Scheduling,CAD Monitor and VPN 5 years=
$104,920
Fee T A be:Recumn•for 5 ears
List Price: $104,920.00
Discounts: $0.00
Tax: $0.00
Total: $104,920.00 p
z
•
w
0
U.
6. All Fees above will be invoiced by ESO as follows:
to
6.1. Training and Training Travel Fees,if any,shall be invoiced on the Effective Date.
rn
6.2. During the first year,the remaining Fees shall be due on the Activation Date.
6.3. During the second year and any renewal years thereafter,100%of the recurring Fees shall be due on the anniversary of the Activation Date.
ca2
0
co
ou
CZ
a
Page 1 of 1
Attachment C: Insurance and Bond Requirements
A. CONTRACTOR'S LIABILITY INSURANCE
1. Contractor must not commence work under this contract until all insurance required
has been obtained and such insurance has been approved by the City. Contractor
must not allow any subcontractor, to commence work until all similar insurance
required of any subcontractor has been obtained.
2. Contractor must furnish to the City's Risk Manager and Contract Administer one (1)
copy of Certificates of Insurance with applicable policy endorsements showing the
following minimum coverage by an insurance company(s) acceptable to the City's
Risk Manager. The City must be listed as an additional insured on the General liability
and Auto Liability policies by endorsement, and a waiver of subrogation
endorsement is required on all applicable policies. Endorsements must be provided
with Certificate of Insurance. Project name and/or number must be listed in
Description Box of Certificate of Insurance.
TYPE OF INSURANCE MINIMUM INSURANCE COVERAGE
30-day advance written notice of Bodily Injury and Property Damage
cancellation, non-renewal, material Per occurrence - aggregate
change or termination required on all
certificates and policies.
ERRORS & OMMISSIONS $1,000,000 Per Occurrence
$1,000,000 Aggregate
CYBER LIABILITY $1,000,000 Per Occurrence
$1,000,000 Aggregate
3. In the event of accidents of any kind related to this contract, Contractor must furnish
the Risk Manager with copies of all reports of any accidents within 10 days of the
accident.
B. ADDITIONAL REQUIREMENTS
1. Applicable for paid employees, Contractor must obtain workers' compensation
coverage through a licensed insurance company. The coverage must be written on
a policy and endorsements approved by the Texas Department of Insurance. The
workers' compensation coverage provided must be in statutory amounts according
to the Texas Department of Insurance, Division of Workers' Compensation. An All
States Endorsement shall be required if Contractor is not domiciled in the State of
Texas.
2. Contractor shall obtain and maintain in full force and effect for the duration of this
Contract, and any extension hereof, at Contractor's sole expense, insurance
coverage written on an occurrence basis by companies authorized and admitted
Page 1 of 3
to do business in the State of Texas and with an A.M. Best's rating of no less than A-
VII.
3. Contractor shall be required to submit renewal certificates of insurance throughout
the term of this contract and any extensions within 10 days of the policy expiration
dates. All notices under this Exhibit shall be given to City at the following address:
City of Corpus Christi
Attn: Risk Manager
P.O. Box 9277
Corpus Christi, TX 78469-9277
4. Contractor agrees that, with respect to the above required insurance, all insurance
policies are to contain or be endorsed to contain the following required provisions:
• List the City and its officers, officials, employees, and volunteers, as additional
insureds by endorsement with regard to operations, completed operations, and
activities of or on behalf of the named insured performed under contract with the
City, with the exception of the workers' compensation policy;
• Provide for an endorsement that the "other insurance" clause shall not apply to the
City of Corpus Christi where the City is an additional insured shown on the policy;
• Workers' compensation and employers' liability policies will provide a waiver of
subrogation in favor of the City; and
• Provide thirty (30) calendar days advance written notice directly to City of any,
cancellation, non-renewal, material change or termination in coverage and not less
than ten (10) calendar days advance written notice for nonpayment of premium.
5. Within five (5) calendar days of a cancellation, non-renewal, material change or
termination of coverage, Contractor shall provide a replacement Certificate of
Insurance and applicable endorsements to City. City shall have the option to
suspend Contractor's performance should there be a lapse in coverage at any time
during this contract. Failure to provide and to maintain the required insurance shall
constitute a material breach of this contract.
6. In addition to any other remedies the City may have upon Contractor's failure to
provide and maintain any insurance or policy endorsements to the extent and within
the time herein required, the City shall have the right to order Contractor to stop work
hereunder, and/or withhold any payment(s) which become due to Contractor
hereunder until Contractor demonstrates compliance with the requirements hereof.
7. Nothing herein contained shall be construed as limiting in any way the extent to
which Contractor may be held responsible for payments of damages to persons or
property resulting from Contractor's or its subcontractor's performance of the work
covered under this contract.
Page 2 of 3
8. It is agreed that Contractor's insurance shall be deemed primary and non-
contributory with respect to any insurance or self insurance carried by the City of
Corpus Christi for liability arising out of operations under this contract.
9. It is understood and agreed that the insurance required is in addition to and separate
from any other obligation contained in this contract.
2019 Insurance Requirements
Ins. Req. Exhibit 7-B
IT Contracts - Software Support, Configuration, Implementation and Maintenance
04/26/2019 Risk Management- Legal Dept.
No bond is required for this service agreement; therefore, Section 5, Insurance; Bonds,
subsection 5 (B) is null and void.
Page 3 of 3
Attachment D: Warranty Requirements
Product warranty is not required for this service agreement; therefore,
Section 8, Warranty, subsection 8 (A) and (B) is null and void.
Page 1 of 1
Attachment E: Master Subcription License Agreement
esoORDER INSTRUCTIONS
1. Fill in Contact Info Below
Contact Name Email Phone
Primary Business Contact
Invoicing Contact
Legal Contact
Software Administrator
Contact
Privacy/HIPAA Contact
Tax Exempt? YES OR NO If YES, return Exempt Certificate with Agreement
Purchase Order Required? YES OR NO If YES, return PO with Agreement
2. Sign page 5.
3. Email entire contract to legal@esosolutions.com and your sales representative.
4. Enjoy your ESO Software
MASTER SUBSCRIPTION AND LICENSE AGREEMENT
This Master Subscription and License Agreement(this"Agreement')is entered into as of October 1,2019("Effective Date"),by and between ESO
Solutions,Inc.,a Texas corporation having its principal place of business at 11500 Alterra Parkway,Suite 100 Austin,TX 78758,including its controlled
subsidiaries,(collectively,"ESO")and the City of Corpus Christi,having its principal place of business at 1201 Leopard Street,Corpus Christi,TX 78401
("Customer').This Agreement consists of the General Terms&Conditions below and any Addenda(as defined below)executed by the parties,including any
attachments to such Addenda.
The parties have agreed that ESO will provide Customer certain technology products and/or services and that Customer will pay ESO certain fees.
Therefore,in consideration of the covenants,agreements and promises set forth below,and for other good and valuable consideration,the receipt and
sufficiency of which is hereby acknowledged,the parties,intending to be legally bound,hereby agree as follows.
GENERAL TERMS AND CONDITIONS
1. DEFINITIONS.Capitalized terms not otherwise defined in this Agreement "SaaS'means software-as-a-service that ESO hosts(directly or indirectly)for
shall have the meanings below: Customer's use.For the avoidance of doubt,SaaS does not include Licensed
Software,but does include Add-on Software and Interoperability Software.
"Add-On Software"means any complementary software components or
reporting service(s)that ESO makes available to customer through its "Scheduled Downtime" means periods when ESO intentionally interrupts the
Licensed Software,Interoperability Software or SaaS. SaaS for the performance of system maintenance or to otherwise correct
service errors.
"Addendum"means a writing addressing an order of a specific set of products
or services executed by authorized representatives of each party.An "Software'means any ESO computer program,programming or modules
Addendum may be(a)a Software Schedule,(b)a Statement of Work,(c)Sales specified in any Software Schedule or SOW.For the avoidance of doubt,Add-
Order,or(d)another writing the parties intend to be incorporated by reference on Software,SaaS,Interoperability Software,and Licensed Software are
into this Agreement. collectively referred to as Software.
"AnonymizedData"means Customer Data from which all personally "Software Schedule"refers to an Addendum under which Customer has
identifiable information has been removed,as well as the names and ordered either Add-on Software,Licensed Software,Interoperability Software
addresses of Customer and any of its Users and/or Customer's clients(and or SaaS.
which,as a consequence,is neither PHI nor identifiable to or by Customer).
"Statement of Wore or"SOW'refers to an Addendum in which Customer has
"Customer Data"means information,data and other content in electronic ordered Professional Services or a Deliverable from ESO.
form that is submitted,posted,or otherwise transmitted by or on behalf of
Customer through the Software. "Support Services"means those services described in Exhibit B.
"Deliverable"means software,report,or other work product created pursuant "Third Party Data"means data not owned by ESO but which is(or access to
to a Statement of Work. which is)provided by ESO under a Software Schedule.
"Documentation"means user guides,operating manuals,and specifications "Third PartyService"means a service not provided by ESO but which is(or
regarding the Software. access to which is)offered by ESO in connection with its Software under a
Software Schedule or Addendum.
"Feedback'refers to any suggestion or idea for improving or otherwise
modifying ESO's products or services. "Third-Party Software"means software not owned by ESO but which is(or
access to which is)provided by ESO under a Software Schedule or Addendum.
%ncident'refers to a locked and uploaded record within the system on a per-
encounter basis,regardless of the number of patients involved in said "Use Restrictions'means the restrictions imposed on Customer's use of
individual encounter. Software as described in Section 3.3.
"Intellectual Property'means trade secrets,copyrightable subject matter, "User means any individual who uses the Software on Customer's behalf or
patents and patent applications,and other proprietary information,activities, through Customer's account or passwords,whether authorized or not.
and any ideas,concepts,innovations,inventions and designs. 2. SOFTWARE ORDERS.During the Term,Customer may order Software
"Interoperability Software"means SaaS that allows Customer to exchange from ESO by signing an appropriate Software Schedule. Customer's
healthcare data with others.For the avoidance of doubt,Interoperability license to Licensed Software and its subscription to SaaS are set forth
Software does not include Add-on Software or Licensed Software. below.Each such Software Schedule is incorporated herein by reference.
"Licensed Software"means the executable,object code version of software 3. LICENSE/SUBSCRIPTION TO SOFTWARE
that ESO provides to Customer for its use and installation on Customer's own 3.1. Grant of Subscription: SaaS.For SaaS,during the Term Customer may
equipment.For the avoidance of doubt,Licensed Software does not include access and use the SaaS and Reporting Services,in such quantities as
Add-on Software,Interoperability Software or SaaS. are set forth on the applicable Software Schedule,subject to
"New Version"means any new version of Licensed Software that ESO may Customer's compliance with the Use Restrictions and other limitations
from time to time introduce and market generally as a distinct licensed contained in this Agreement.
product,as may be indicated by Licensor's designation of a new version 3.2. Grant of License: Licensed Software.For Licensed Software,during the w
number,brand or product. Term ESO hereby grants Customer a limited,non-exclusive,non-
transferable,non-assignable, non-sublicensable,revocable license to z
"Outage"means Customer is unable to access SaaS,or such access is 0
materially delayed,impaired or disrupted,in each case as caused or controlled copy and use the Licensed Software,in such quantities as are set forth o
by ESO. on the applicable Software Schedule and as necessary for Customer's
internal business purposes,in each case subject to Customer's o
"Professional Services"means professional services provided by ESO under a compliance with the Use Restrictions and other limitations and
Statement of Work. obligations contained in this Agreement.
N
"Protected Health Information"or"PHI shall have the meaning set forth in 3.3. Use Restrictions.Except as provided in this Agreement or as otherwise 8.
HIPAA.All references herein to PHI shall be construed to include electronic authorized by ESO,Customer has no right to,and shall not:(a)
PHI,or ePHI,as that term is defined by HIPAA. decompile,reverse engineer,disassemble,print,copy or display the 0
Software or otherwise reduce the Software to a human-perceivable form w
"ReportingServices'means,collectively,the different tools or features in the in whole or in part;(b)publish,release,rent,lease,loan,sell,distribute H
Software allowing Customer to generate compilations of data,including but or transfer the Software to another person or entity;(c)reproduce the
not limited to ad-hoc reports,analytics,benchmarking or any other reportingSoftware for the use or benefit of anyone other than Customer;(d)alter, a
tool provided through the Software. modify or create derivative works based upon the Software either in
whole or in part;or(e)use or permit the use of the Software for 4.4. Su000rt and Updates. During the Term,ESO shall provide to Customer
commercial time-sharing arrangements or providing service bureau, the Support Services,in accordance with Exhibit B,which is
data processing,rental,or other services to any third party(including incorporated herein by reference.
any affiliate not specifically listed in the applicable Software Schedule).
5. FEES
3.4. Ownership. The rights granted under the provisions of this Agreement
do not constitute a sale of the Software.ESO retains all right,title,and 5.1. Fees.In consideration of the rights granted,Customer agrees to pay
interest in and to the Software,including without limitation all software ESO the fees for the Software and Professional Services as set forth in
used to provide the Software and all graphics,user interfaces,logos the Software Schedule(s)or SOW(s)(collectively,"Fees").The Fees are
and trademarks reproduced through the Software,except to the limited non cancelable and non-refundable,except as expressly provided
extent set forth in this Agreement.This Agreement does not grant herein.Customer shall pay all invoices within 30 days of receipt.
Customer any intellectual property rights in the Software or any of its 5.2. Third-Party Payer. If Customer desires to use a third-party to pay some
components,except to the limited extent that this Agreement or all of the Fees on behalf of Customer(a"Third-Party Payer), then(i)
specifically sets forth Customer's rights to access,use,or copy the each applicable Addendum will identify such arrangement,(ii)the Third-
Software during the Term.Customer acknowledges that the Software Party Payer will enter into a written agreement with ESO regarding such
and its components are protected by copyright and other laws. arrangement,(iii)Customer may replace the Third-Party Payer by written
3.5. Third-Party Software and Services. ESO neither accepts liability for,nor notice to ESO(provided that no such change shall be made until the
warrants the functionality,utility,availability,reliability or accuracy of, then current Term's renewal),and(iv)Customer shall remain
Third-Party Software or Third-Party Services. The Third-Party Software responsible for payment if the Third-Party Payer does not pay the Fees.
"EMS1 Academy"and/or"FireRescuel Academy"and/or"EMS1& 5.3. Intentionally Omitted.
FireRescuel Academy-Implementation and Configuration"and/or
"Learning Management System"and/or"EVALS Implementation" 5.4. Taxes and Fees. The Fees are exclusive of all taxes and credit card
(collectively,"Education")is offered by ESO in collaboration with Lexipol, processing fees,if applicable.Unless and until Customer provides ESO
f/k/a The Praetorian Group.If Customer subscribes to Education, a tax exemption certificate,Customer will be responsible for and will
Customer acknowledges and agrees to the terms and conditions of the remit(or will promptly reimburse ESO for)all taxes of any kind,including
Praetorian license agreement,located at sales,use,duty,customs,withholding,property,value-added,and other
http://www.praetoriandigital.com/LMS-Master-Service-Agreement, similar federal,state or local taxes(other than taxes based on ESO's
which shall supersede this Agreement as it applies to Customer's use of income)related to this Agreement.
Education and any Customer Data stored therein.
5.5. Appropriation of Funds.If Customer is a city,county or other
3.6. Third-Party Data. If Customer(as indicated on an Addendum)elects to government entity,Customer will have the right to terminate the
license Third-Party Data(e.g.,fire codes),then subject to the terms Agreement at the end of the Customer's fiscal term if Customer
hereof,ESO hereby grants Customer a non-exclusive,non- provides evidence that its governing body did not appropriate sufficient
sublicensable,and non-transferable license during the Term to use funds for the next fiscal year.Notwithstanding the foregoing,this
such Third-Party Data via the Software solely for Customer's internal provision shall not excuse Customer from past payment obligations or
purposes. Customer will not(i)allow greater access than that set forth other Fees earned and unpaid.
in the applicable Software Schedule,(ii)disclose,release,distribute,or
deliver Third Party Data,or any portion thereof,to any third party(iii) 5.6. Usage Monitoring.Customer is solely responsible for its own adherence
copy,modify,or create derivative works of Third-Party Data,(iv)rent to volume and use limitations indicated on the applicable Software
lease,lend,sell,sublicense,assign,distribute,publish,transfer,or Schedule. ESO may monitor Customer's use of the Software,and if
otherwise make available Third-Party Data,(v)attempt to output in any Customer's usage exceeds the level for which Customer has paid in the
form more than 10%of the Third-Party Data or otherwise circumvent applicable Software Schedule(an"Overage'),Customer shall owe ESO
the usage limitations included in the Software,(vi)remove any the Fee corresponding to such usage level based on the Software
proprietary notices included within Third-Party Data or Software,or(vii) Schedule(or if none,ESO's then-current rates).ESO may invoice for
use Third-Party Data in any manner or for any purpose that infringes or Overages immediately.
otherwise violates any proprietary right of a person,or that violates 6. TERM AND TERMINATION
applicable law.ESO does not warrant the functionality,reliability,
accuracy,completeness or utility of,Third-Party Data,or accept any 6.1. Intentionally omitted.
liability therefor. Additional terms and limitations applicable to Third-
Parry Data may be provided on the applicable Addendum. 6.2. Intentionally omitted.
3.7. New Versions&Sunset. If ESO releases a New Version of Licensed 6.3. Effect of Termination.
Software,Customer may elect to receive such New Version,subject to a 6.3.1. If Customer terminates this Agreement or any Software Schedule as
relicense fee of 75%of the standard price for such new version.All New a result of ESO's material breach,then to the extent that Customer
Versions provided under this Agreement will constitute Licensed has prepaid any Fees,ESO shall refund to Customer any prepaid
Software and be subject to the terms and conditions of this Agreement. Fees on a pro-rata basis to the extent such Fees are attributable to
ESO may discontinue Support Services for Licensed Software upon 12 the period after the latter to occur of the(i)termination date or(ii)
months'notice to Customer. the date on which Customer actually ceases use of the Software.
J
4. HOSTING,SLA&SUPPORT SERVICES 6.3.2. Upon termination of this Agreement or any Software Schedule,
4.1. Hosting&Management.Customer shall be solely responsible for Customer shall cease all use of the Software and delete,destroy or o
hosting and managing any Licensed Software.ESO shall be responsible return all copies of the Documentation and Licensed Software in its LL
for hosting and managing any SaaS. possession or control,except as required by law. Customer shall z
remain obligated to pay appropriate Fees at ESO's then-current coi
4.2. Service Level Agreement. If an Outage,excluding Scheduled Downtime rates if Customer continues to use or access Software after the o
(as defined below),results in the service level uptime falling below 99% termination or expiration of this Agreement. If Customer received o
for three months in any rolling 12-month period(the"Uptime discounts for any of the two years prior to the date of termination,
Commitment"),then Customer may immediately terminate this Customer shall promptly pay ESO's invoice recouping such N
Agreement,in which case ESO will refund any prepaid,unearned Fees discounts.
to Customer.This is Customer's sole remedy for ESO's breach of the
Uptime Commitment. 6.3.3. Termination of this Agreement is without prejudice to any other right w
or remedy and shall not release a party from any liability. 2
4.3. Scheduled Downtime. ESO will provide reasonable notice to the v)
Customer(Software Administrator Contactor otherwise)of Scheduled 6.4. Delivery of Data. If Customer requests its data within 60 days of w
Downtime(usually at least 72 hours in advance),and will plan expiration or termination of this Agreement,ESO will provide Customer
Scheduled Downtime to occur during non-peak hours(midnight to 6 its Customer Data in a searchable.pdf format. Customer acknowledgesN
a.m.Central Time). Scheduled Downtime shall never constitute a that ESO is under no obligation to retain Customer Data more than 60 OD
failure of performance or Outage by ESO. days after expiration or termination of this Agreement. a
7. REPRESENTATIONS AND WARRANTIES such required disclosure shall be given promptly and without
unreasonable delay by the receiving party in order to give the disclosing
7.1. Material Performance of Software.ESO represents and warrants that party the opportunity to object to the disclosure and/or to seek a
the Software will perform in material accordance with any protective order.The receiving party shall reasonably cooperate in this
Documentation provided by ESO. effort.In addition,Customer may disclose the contents of this
7.2. Due Authority.Each party's execution,delivery and performance of this Agreement solely for the purpose of completing its review and approval
Agreement and each agreement or instrument contemplated by this processes under its local rules,if applicable.
Agreement has been duly authorized by all necessary corporate or 10. Intentionally omitted.
government action.
11. Intentionally omitted.
7.3. Customer Cooperation.Customer agrees to use current operating
systems and reasonably and timely cooperate with ESO,including 12. Intentionally omitted.
providing ESO reasonable access to its equipment,software and data.
13. CUSTOMER DATA&PRIVACY
8. DISCLAIMER OF WARRANTIES.EXCEPT AS OTHERWISE PROVIDED IN
SECTION 7,ESO DISCLAIMS ALL WARRANTIES,EXPRESS OR IMPLIED, 13.1. Ownership of Data.As between ESO and Customer,all Customer Data
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS shall be owned by Customer.
FOR A PARTICULAR PURPOSE,PERFORMANCE,SUITABILITY,TITLE,NON- 13.2. Use of Customer Data.Unless it receives Customer's prior written
INFRINGEMENT,OR ANY IMPLIED WARRANTY ARISING FROM STATUTE, consent,ESO shall not:(a)access,process,or otherwise use
COURSE OF DEALING,COURSE OF PERFORMANCE,OR USAGE OF TRADE. Customer Data;and(b)intentionally grant any third-party access to
WITHOUT LIMITING THE GENERALITY OF THE FOREGOING,ESO DOES Customer Data,including without limitation ESO's other customers,
NOT REPRESENT OR WARRANT THAT CUSTOMER DATA WILL REMAIN except subcontractors that are subject to a reasonable nondisclosure
PRIVATE OR SECURE,OR THAT THE SOFTWARE(X)WILL PERFORM agreement or authorized participants in the case of Interoperability
WITHOUT INTERRUPTION OR ERROR,OR(Y)IS SECURE FROM HACKING Software.Notwithstanding the foregoing,ESO may use and disclose
OR OTHER UNAUTHORIZED INTRUSION.EXCEPT AS EXPRESSLY Customer Data to fulfill its obligations under this Agreement or as
PROVIDED IN SECTION 7,CUSTOMER ACCEPTS THE SOFTWARE"AS-IS" required by applicable law or legal or governmental authority.ESO
AND"AS AVAILABLE." shall give Customer prompt notice of any such legal or governmental
9. CONFIDENTIALITY demand and reasonably cooperate with Customer in any effort to seek
a protective order or otherwise to contest such required disclosure,at
9.1. "Confidentiallnformation"refers to the following items: (a)any Customer's expense.
document marked"Confidential";(b)any information orally designated
as"Confidential"at the time of disclosure,provided the disclosing party 13.3. Anonvmized Data. CUSTOMER ACKNOWLEDGES AND AGREES THAT,
confirms such designation in writing within five business days;(c)the NOTWITHSTANDING ANY OTHER PROVISION HEREIN,ESO MAY USE
Software and Documentation,whether or not designated confidential; ANONYMIZED DATA FOR INTERNAL AND EXTERNAL PURPOSES
(d)ESO's security controls,policies,procedures,audits,or other (INCLUDING BENCHMARKING AND RESEARCH),PROVIDED THAT ESO
information concerning ESO's internal security posture;(e)any other WILL NOT SELL ANONYMIZED DATA TO THIRD PARTIES FOR
nonpublic,sensitive information reasonably treated as trade secret or COMMERCIAL USE. Without limiting the foregoing,ESO will own all
otherwise confidential;and(f)Customer Data which does not comprise right,title and interest in all Intellectual Property of any aggregated
PHI.Notwithstanding the foregoing,Confidential Information does not and de-identified reports,summaries,compilations,analysis,statistics
include information that:(i)is in the other party's possession at the time or other information derived therefrom.
of disclosure free of duty of non-disclosure;(ii)is independently 13.4. Risk of Exposure.Customer acknowledges and agrees that hosting
developed without use of or reference to Confidential Information;(iii) data online involves risks of unauthorized disclosure and that,in
becomes known publicly,before or after disclosure,other than as a accessing and using the SaaS,Customer assumes such risks.
result of the receiving party's improper action or inaction;(iv)is Customer has sole responsibility for obtaining,maintaining,and
approved for release in writing by the disclosing party;or(v)PHI(which securing its network connections.ESO makes no representations to
shall be governed by the Business Associate Agreement rather than Customer regarding the reliability,performance or security of any
this Section). network or provider.
9.2. Nondisclosure.Each party shall use Confidential Information of the 14. FEEDBACK RIGHTS&WORK PRODUCT
other party solely to fulfill the terms of this Agreement(the"Purpose").
Each party shall(a)ensure that its employees or contractors are bound 14.1. Feedback Rights.ESO does not agree to treat as confidential any
by confidentiality obligations no less restrictive than those contained Feedback that Customer provides to ESO.Nothing in this Agreement
herein,and(b)not disclose Confidential Information to any other third will restrict ESO's right to use,profit from,disclose,publish,keep
party without prior written consent from the disclosing party.Without secret,or otherwise exploit Feedback,without compensation or
limiting the generality of the foregoing,the receiving party shall protect crediting Customer.Feedback will not constitute Confidential
Confidential Information with the same degree of care it uses to protect Information,even if it would otherwise qualify as such pursuant to
its own confidential information of similar nature and importance,but Section 9(Confidential Information).
with no less than reasonable care.A receiving party shall promptly
notify the disclosing party of any misuse or misappropriation of 14.2. Work Product Ownership.In the event Customer hires ESO to perform
Professional Services,ESO alone shall hold all right,title,and interest a
Confidential Information of which it is aware.
to all proprietary and intellectual property rights of the Deliverables w
9.3. Termination&Return.With respect to each item of Confidential (including,without limitation,patents,trade secrets,copyrights,and o
Information,the obligations of nondisclosure will terminate three years trademarks),as well as title to any copy of software made by or for
after the date of disclosure;provided that,such obligations related to Customer(if applicable).Customer hereby explicitly acknowledges and o
Confidential Information constituting ESO's trade secrets shall continue agrees that nothing in this Agreement or a separate SOW gives the
so long as such information remains subject to trade secret protection Customer any right,title,or interest to the intellectual property or
r
pursuant to applicable law.Upon termination of this Agreement,a party proprietary know-how of the Deliverables.
shall return all copies of Confidential Information to the other or certify
the destruction thereof. 15. GOVERNMENT PROVISIONS
9.4. Retention of Rights.This Agreement does not transfer ownership of 15.1. Compliance with Laws. Both parties shall comply with and give all g
Confidential Information or grant a license thereto. notices required by all applicable federal,state and local laws,
ordinances,rules,regulations and lawful orders of any public authority o
9.5. Open Records and Other Laws.Notwithstanding anything in this Section bearing on use of the Software and the performance of this Agreement w
to the contrary,the parties expressly acknowledge that Confidential
Information may be disclosed if such Confidential Information is 15.2. Business Associate Addendum.The parties agree to the terms of the M
required to be disclosed by law,a lawful public records request,or Business Associate Addendum attached hereto as Exhibit C and �'
incorporated herein byLaiL
judicial order,provided that prior to such disclosure,written notice of reference. co
a
15.3. Equal Opportunity.The parties shall abide by the requirements of 41 hurricanes,earthquakes,other acts of God or of nature,strikes or
CFR 60-1.4(a),60-300.5(a)and 60-741.5(a),and the posting other labor disputes,riots or other acts of civil disorder,embargoes,or
requirements of 29 CFR Part 471,appendix A to subpart A,if other causes beyond the performing party's reasonable control
applicable.These regulations prohibit discrimination against qualified (collectively,"Force Majeure").In such event,however,the delayed
individuals based on their status as protected veterans or individuals party must promptly provide the other party notice of the Force
with disabilities,and prohibit discrimination against all individuals Majeure.The delayed party's time for performance will be excused for
based on their race,color,religion,sex,sexual orientation,gender the duration of the Force Majeure,but if the event last longer than 30
identity or national origin. days,the other party may immediately terminate the applicable
Software Schedule.
15.4. Excluded Parties List.ESO agrees to immediately report to Customer if
an employee or contractor is listed by a federal agency as debarred, 17.8. Marketing.If requested by ESO,Customer agrees to reasonably
excluded or otherwise ineligible for participation in federally funded cooperate with ESO's preparation and issuance of a public
health care programs. announcement regarding the relationship of the parties.
16. PHI ACCURACY&COMPLETENESS 17.9. Intentionally omitted.
16.1. ESO provides the Software to allow Customer(and its respective 17.10. Survival of Terms.Unless otherwise stated,all of ESO's and
Users)to enter,document,and disclose Customer Data,and as such, Customer's respective obligations,representations and warranties
ESO gives no representations or guarantees about the accuracy or under this Agreement which are not,by the expressed terms of this
completeness of Customer Data(including PHI)entered,uploaded or Agreement,fully to be performed while this Agreement is in effect
disclosed through the Software. shall survive the termination of this Agreement.
16.2. Customer is solely responsible for any decisions or actions taken 17.11. Ambiguous Terms.This Agreement will not be construed against any
involving patient care or patient care management,whether those party by reason of its preparation.
decisions or actions were made or taken using information received
through the Software. 17.12. Intentionally omitted.
17. MISCELLANEOUS 17.13. Bench Trial.The parties agree to waive,to the maximum extent
permitted by law,any right to a jury trial with respect to any Dispute.
17.1. Independent Contractors.The parties are independent contractors.
Neither party is the agent of the other,and neither may make 17.14. No Class Actions.NEITHER PARTY SHALL BE ENTITLED TO JOIN OR
commitments on the other's behalf.The parties agree that no ESO CONSOLIDATE CLAIMS BY OR AGAINST OTHER ESO CUSTOMERS,OR
employee or contractor is or will be considered an employee of PURSUE ANY CLAIM AS A REPRESENTATIVE OR CLASS ACTION OR IN
Customer. A PRIVATE ATTORNEY GENERAL CAPACITY.
17.2. Notices.Notices provided under this Agreement must be in writing and 17.15. Limitation Period.Neither party shall be liable for any claim brought
delivered by(a)certified mail,return receipt requested to a party's more than two years after the cause of action for such claim first
principal place of business as forth in the recitals on page 1 of this arose.
Agreement,(b)hand delivered,(c)facsimile with receipt of a 17.16. Dispute Resolution.Customer and ESO will attempt to resolve any
"Transmission Confirmed"acknowledgment,(d)e-mail to a person Dispute through negotiation or by utilizing a mediator agreed to by
designated in writing by the receiving party,or(e)delivery by a the parties,rather than through litigation.Negotiations and
reputable overnight carrier service.In the case of delivery by facsimile mediations will be treated as confidential.If the parties are unable to
or e-mail,the notice must be followed by a copy of the notice being reach a resolution within 30 days of notice of the Dispute to the other
delivered by a means provided in(a),(b)or(e). The notice will be party,the parties may pursue all other courses of action available at
deemed given on the day the notice is received. law or in equity.
17.3. Merger Clause. In entering into this Agreement,neither party is relying 17.17. Technology Export.Customer shall not:(a)permit any third party to
upon any representations or statements of the other that are not fully access or use the Software in violation of any U.S.law or regulation;
expressed in this Agreement;rather each party is relying on its own or(b)export any software provided by ESO or otherwise remove it
judgment and due diligence and expressly disclaims reliance upon any from the United States except in compliance with all applicable U.S.
representations or statement not expressly set forth in this Agreement. laws and regulations.Without limiting the generality of the foregoing,
In the event the Customer issues a purchase order,letter or any other Customer shall not permit any third party to access or use the
document addressing the Software or Services to be provided and Software in,or export such software to,a country subject to a United
performed pursuant to this Agreement,it is hereby specifically agreed States embargo(as of the Effective Date-Cuba,Iran,North Korea,
and understood that any such writing is for the Customer's internal Sudan,and Syria).
purposes only,and that any terms,provisions,and conditions
contained therein shall in no way modify this Agreement. 17.18. Intentionally omitted.
17.4. Intentionally omitted. 17.19. Counterparts.This Agreement may be executed in one or more
counterparts.Each counterpart will be an original,and all such
17.5. Intentionally omitted. counterparts will constitute a single instrument.
J
17.6. Intentionally omitted. 17.20. Signatures.Electronic signatures on this Agreement or on any
Addendum(or copies of signatures sent via electronic means)are w
17.7. Force Majeure.No delay,failure,or default will constitute a breach of
this Agreement to the extent caused by acts of war,terrorism, the equivalent of handwritten signatures. LT
z
0
0
U)
V4
O
m
0
O
N
U)
2
0
U)
w
a)
a)
Co
m
a
IN WITNESS WHEREOF,the parties have executed this Agreement as of the Effective Date.
ESO Solutions,Inc. Customer
BY: BY:
(signature) (signature)
Name: Name:
(print name) (print name)
Title: Title:
(print title) (print title)
-J
F
z
W
O
LL
Z
O
O
Ln
'-I
r
O
O
-1
O
Co
2
O
O
'^w
u J
a)
m
a
EXHIBIT A
LICENSED SOFTWARE SCHEDULE
(Applications-ESO Billing.ESO Dispatch.FIREHOUSE by ESO.IFC Codes)
1. The Licensed Software term shall begin the earlier of 90 calendar days after the Effective Date or the first day the Licensed Software is used in production
mode("Activation Date").Customer shall be deemed to have accepted the Licensed Software on the Activation Date.The parties will make reasonable
efforts to ensure that Customer is able to use the Licensed Software as quickly as possible,but in no event will the Activation Date be modified for
implementation delays.
2. The following Licensed Software may be ordered under this Exhibit:
2.1. ESO Billing is on premise software for EMS billing(http://www.esosolutions.com/software/billing).
2.2. ESO Dispatch is on premise software for medical dispatch and transports(http://www.esosolutions.com/software/dispatch).
3. The following Third-Party Data may be ordered under this Exhibit: 2018 International Fire Code,2015 International Fire Code 2012 International Fire
Code.
4. Third-Party Payer is responsible for the following products and Fees:
N/A
5. Customer hereby agrees to timely pay for the following products according to the schedule below:
Contact and Billing Details
Sold to: Kim Baker Contact: Kim Baker Address: Accts Payable 2406
Leopard St Suite 300
Bill To: Corpus Christi Fire Department Phone: 3618263907 Corpus Christi,Texas
78401
Email: Email: United States
Subscription and/or License Terms
Initial Term(Years): 5 Billing Frequency: Annual Customer ID: 201712-13517
Renewal Term(N/A): 0 Billing Method: Email Total Recurring Fees: $20,984.00
Terms: Net 30 Total One-Time Fees: $ 0.00
Product Name Product Description Quantity Total Price/
Discounts
FH Cloud Annual Fee Includes 30 Concurrent licenses with Fre,Training,Inventory, 1(Each $20,984.00 x
Occupancy,Hydrants,Staff Scheduling,CAD Monitor and VPN 5 years=
$104,920
Fee T lie:Recurrin L for 5 ears
List Price: $104,920.00
Discounts: $0.00
Tax: $0-00
Total: $104,920.00
w
0
it
z
6. All Fees above will be invoiced by ESO as follows: o
Ln
6.1. Training and Training Travel Fees,if any,shall be invoiced on the Effective Date.
rn
6.2. During the first year,the remaining Fees shall be due on the Activation Date. N
6.3. During the second year and any renewal years thereafter,100%of the recurring Fees shall be due on the anniversary of the Activation Date. co
2
com
no
m
EXHIBIT B
SUPPORT SERVICES ADDENDUM
1. DEFINITIONS.Capitalized terms not defined below shall have the same meaning as in the General Terms&Conditions.
1.1. "Enhancement"means a modification,addition or new release of the Software that when added to the Software,materially changes its utility,
efficiency,functional capability or application.
1.2. "E-mail Support"means ability to make requests for technical support assistance by e-mail at any time concerning the use of the then-current release
of Software.
1.3. "Error"means an error in the Software,which significantly degrades performance of such Software as compared to ESO's then-published
Documentation.
1.4. "Error Correction"means the use of reasonable commercial efforts to correct Errors.
1.5. "Fix"means the repair or replacement of object code for the Software or Documentation to remedy an Error.
1.6. "Initial Response"means the first contact by a Support Representative after the incident has been logged and a ticket generated.This may include
an automated email response depending on when the incident is first communicated.
1.7. "Management Escalation"means,if the initial Workaround or Fix does not resolve the Error,notification of management that such Error(s)have been
reported and of steps being taken to correct such Error(s).
1.8. "Severity 1 Error"means an Error which renders the Software completely inoperative(e.g.,a User cannot access the Software due to unscheduled
downtime or an Outage).
1.9. "Severity 2 Error"means an Error in which Software is still operable;however,one or more significant features or functionality are unavailable(e.g.,a
User cannot access a core component of the Software).
1.1. "Severity 3 Error"means any other error that does not prevent a User from accessing a significant feature of the Software(e.g.,User is experiencing
latency in reports).
1.2. "Severity 4 Error"means any error related to Documentation or a Customer Enhancement request.
1.3. "Status Update"means if the initial Workaround or Fix cannot resolve the Error,notification of the Customer regarding the progress of the
Workaround or Fix.
1.4. "Online Support"means information available through ESO's website(www.esosolutions.com),including frequently asked questions and bug
reporting via Live Chat.
1.5. "Support Representative"shall be ESO employee(s)or agent(s)designated to receive Error notifications from Customer,which Customer's
Administrator has been unable to resolve.
1.6. "Update"means an update or revision to Software,typically for Error Correction.
1.7. "Upgrade"means a new version or release of Software or a particular component of Software,which improves the functionality or which adds
functional capabilities to the Software and is not included in an Update.Upgrades may include Enhancements.
J
1.8. "Workaround"means a change in the procedures followed or data supplied by Customer to avoid an Error without substantially impairing Customer's
use of the Software. w
2. SUPPORT SERVICES.
LU
2.1. Customer will provide at least one administrative employee(the"Administrator"or"Administrators")who will handle all requests for first-level support o
from Customer's employees with respect to the Software.Such support is intended to be the"front line"for support and information about the rn
Software to Customer's Users. ESO will provide training,documentation,and materials to the Administrator to enable the Administrator to provide
technical support to Customer's Users. The Administrator will notify a Support Representative of any Errors that the Administrator cannot resolve and
assist ESO in information gathering.
U)
2
2.2. ESO will provide Support Services consisting of(a)Error Correction(s);Enhancements,Updates and Upgrades that ESO,in its discretion,makes o
generally available to its customers without additional charge;and(c)E-mail Support,telephone support,and Online Support.ESO may use multiple w
forms of communication for purposes of submitting periodic status reports to Customer,including but not limited to,messages in the Software,
on
CO
CL
messages appearing upon login to the Software or other means of broadcasting Status Update(s)to multiple customers affected by the same Error,
such as a customer portal.
2.3. ESO's support desk will be staffed with competent technical consultants who are trained in and thoroughly familiar with the Software and with
Customer's applicable configuration.Telephone support and all communications will be delivered in intelligible English.
2.4. Normal business hours for ESO's support desk are Monday through Friday 7:00 am to 7:00 pm CT.Customer will receive a call back from a Support
Representative after-hours for a Severity 1 Error.
3. ERROR PRIORITY LEVELS.Customer will report all Errors to ESO via e-mail(support@esosolutions.com)or by telephone(866-766-9471,option#3).ESO
shall exercise commercially reasonable efforts to correct any Error reported by Customer in accordance with the priority level reasonably assigned to such
Error by ESO.
3.1. Severity 1 Error.ESO shall(i)commence Error Correction promptly;(ii)provide an Initial Response within four hours;(iii)initiate Management
Escalation promptly;and(iv)provide Customer with a Status Update within four hours if ESO cannot resolve the Error within four hours.
3.2. Severity 2 Error.ESO shall(i)commence Error Correction promptly;(ii)provide an Initial Response within eight hours;(iii)initiate Management
Escalation within 48 hours if unresolved;and(iv)provide Customer with a Status Update within forty-eight hours if ESO cannot resolve the Error within
forty-eight hours.
3.3. Severity 3 Error.ESO shall(i)commence Error Correction promptly;(ii)provide an Initial Response within three business days;and(iii)provide
Customer with a Status Update within seven calendar days if ESO cannot resolve the Error within seven calendar days.
3.4. Severity 4 Error.ESO shall(i)provide an Initial Response within seven calendar days.
4. CONSULTING SERVICES.If ESO reasonably believes that a problem reported by Customer is not due to an Error in the Software,ESO will so notify Customer.
At that time,Customer may request ESO to proceed with a root cause analysis at Customer's expense as set forth herein or in a separate SOW.If ESO
agrees to perform the investigation on behalf of Customer,then ESO's then-current and standard consulting rates will apply for all work performed in
connection with such analysis,plus reasonable related expenses incurred.For the avoidance of doubt,Consulting Services will include customized report
writing by ESO on behalf of Customer.
5. EXCLUSIONS.
5.1. ESO shall have no obligation to perform Error Corrections or otherwise provide support for:(i)Customer's repairs,maintenance or modifications to
the Software(if permitted);(ii)Customer's misapplication or unauthorized use of the Software;(iii)altered or damaged Software not caused by ESO;
(iv)any third-party software;(v)hardware issues;(vi)Customer's breach of the Agreement;and(vii)any other causes beyond the ESO's reasonable
control.
5.2. ESO shall have no liability for any changes in Customer's hardware or software systems that may be necessary to use the Software due to a
Workaround or Fix.
5.3. ESO is not required to perform any Error Correction unless ESO can replicate such Error on its own software and hardware or through remote access
to Customer's software and hardware.
5.4. Customer is solely responsible for its selection of hardware,and ESO shall not be responsible the performance of such hardware even if ESO makes
recommendations regarding the same.
6. MISCELLANEOUS.The parties acknowledge that from time-to-time ESO may update its support processes specifically addressed in this Exhibit and may do
so by posting such updates to ESO's website or otherwise notifying Customer of such updates.Customer will accept updates to ESO's support procedures
and any other terms in this Exhibit;provided however,that they do not materially decrease the level of Support Services that Customer will receive from
ESO.THESE TERMS AND CONDITIONS DO NOT CONSTITUTE A PRODUCT WARRANTY.THIS EXHIBIT IS AN ADDITIONAL PART OF THE AGREEMENT AND DOES
NOT CHANGE OR SUPERSEDE ANY TERM OF THE AGREEMENT EXCEPT TO THE EXTENT UNAMBIGUOUSLY CONTRARY THERETO.
z
w
0
U-
z
0
0
U)
r-I
O
O
O
N
2
coo
Mw
W
nu
m
a
EXHIBIT C
HIPAA BUSINESS ASSOCIATE ADDENDUM
Customer and ESO Solutions,Inc.("Business Associate")agree that this HIPAA Business Associate Addendum is entered into for the benefit of Customer,
which is a covered entity under the Privacy Standards("Covered Entity").
Pursuant to the Master Subscription and License Agreement(the"Agreement")into which this HI PAA Business Associate Addendum(this"Addendum")has
been incorporated,Business Associate may perform functions or activities involving the use and/or disclosure of PHI on behalf of the Covered Entity,and
therefore,Business Associate may function as a business associate.Business Associate,therefore,agrees to the following terms and conditions.
1. Scope. This Addendum applies to and is hereby automatically incorporated into all present and future agreements and relationships,whether written,oral
or implied,between Covered Entity and Business Associate,pursuant to which PHI is created,maintained,received or transmitted by Business Associate
from or on behalf of Covered Entity in any form or medium whatsoever.
2. Definitions.For purposes of this Addendum,the terms used herein,unless otherwise defined,shall have the same meanings as used in the Health
Insurance Portability and Accountability Act of 1996("HIPAA"),or the Health Information Technology for Economic and Clinical Health Act("HITECH"),and
any amendments or implementing regulations,(collectively"HIPAA Rules").
3. Compliance with Applicable Law.The parties acknowledge and agree that,beginning with the relevant effective date,Business Associate shall comply with
its obligations under this Addendum and with all obligations of a business associate under HIPAA,HITECH,the HIPAA Rules,and other applicable laws and
regulations,as they exist at the time this Addendum is executed and as they are amended,for so long as this Addendum is in place.
4. Permissible Use and Disclosure of PHI.Business Associate may use and disclose PHI as necessary to carry out its duties to a Covered Entity pursuant to the
terms of the Agreement and as required by law.Business Associate may also use and disclose PHI(i)for its own proper management and administration,
and(ii)to carry out its legal responsibilities.If Business Associate discloses Protected Health Information to a third party for either above reason,prior to
making any such disclosure,Business Associate must obtain:(i)reasonable assurances from the receiving party that such PHI will be held confidential and
be disclosed only as required by law or for the purposes for which it was disclosed to such receiving party;and(ii)an agreement from such receiving party to
immediately notify Business Associate of any known breaches of the confidentiality of the PHI.
5. Limitations on Use and Disclosure of PHI.Business Associate shall not,and shall ensure that its directors,officers,employees,subcontractors,and agents
do not,use or disclose PHI in any manner that is not permitted by the Agreement or that would violate Subpart E of 45 C.F.R.164("Privacy Rule")if done by
a Covered Entity.All uses and disclosures of,and requests by,Business Associate for PHI are subject to the minimum necessary rule of the Privacy Rule.
6. Required Safeguards to Protect PHI.Business Associate shall use appropriate safeguards,and comply with Subpart C of 45 C.F.R.Part 164("Security Rule")
with respect to electronic PHI,to prevent the use or disclosure of PHI other than pursuant to the terms and conditions of this Addendum.
7. Reporting to Covered Entity.Business Associate shall report to the affected Covered Entity without unreasonable delay:(a)any use or disclosure of PHI not
provided for by the Agreement of which it becomes aware;(b)any breach of unsecured PHI in accordance with 45 C.F.R.Subpart D of 45 C.F.R.164
("Breach Notification Rule");and(c)any security incident of which it becomes aware. With regard to Security Incidents caused by or occurring to Business
Associate,Business Associate shall cooperate with the Covered Entity's investigation,analysis,notification and mitigation activities,and except for Security
Incidents caused by Covered Entity,shall be responsible for reasonable costs incurred by the Covered Entity for those activities.Notwithstanding the
foregoing,Covered Entity acknowledges and shall be deemed to have received advanced notice from Business Associate that there are routine occurrences
of:(i)unsuccessful attempts to penetrate computer networks or services maintained by Business Associate;and(ii)immaterial incidents such as"pinging"
or"denial of services"attacks.
8. Mitigation of Harmful Effects.Business Associate agrees to mitigate,to the extent practicable,any harmful effect of a use or disclosure of PHI by Business
Associate in violation of the requirements of the Agreement,including,but not limited to,compliance with any state law or contractual data breach
requirements.
9. Agreements by Third Parties.Business Associate shall enter into an agreement with any subcontractor of Business Associate that creates,receives,
maintains or transmits PHI on behalf of Business Associate.Pursuant to such agreement,the subcontractor shall agree to be bound by the same or greater
restrictions,conditions,and requirements that apply to Business Associate under this Addendum with respect to such PHI.
J
10. Access to PHI.Within five business days of a request by a Covered Entity for access to PHI about an individual contained in a Designated Record Set,
Business Associate shall make available to the Covered Entity such PHI for so long as such information is maintained by Business Associate in the
0
Designated Record Set,as required by 45 C.F.R.164.524.In the event any individual delivers directly to Business Associate a request for access to PHI, u
Business Associate shall within five(5)business days forward such request to the Covered Entity. zo
U
11. Amendment of PHI.Within five business days of receipt of a request from a Covered Entity for the amendment of an individual's PHI or a record regarding an
individual contained in a Designated Record Set(for so long as the PHI is maintained in the Designated Record Set),Business Associate shall provide such rn
information to the Covered Entity for amendment and incorporate any such amendments in the PHI as required by 45 C.F.R.164.526.In the event any
individual delivers directly to Business Associate a request for amendment to PHI,Business Associate shall within five business days forward such request cy
to the Covered Entity.
coco
12. Documentation of Disclosures.Business Associate agrees to document disclosures of PHI and information related to such disclosures as would be required
for a Covered Entity to respond to a request by an individual for an accounting of disclosures of PHI in accordance with 45 C.F.R.164.528 and HITECH. w
a�
no
m
o_
13. Accounting of Disclosures.Within five business days of notice by a Covered Entity to Business Associate that it has received a request for an accounting of
disclosures of PHI,Business Associate shall make available to a Covered Entity information to permit the Covered Entity to respond to the request for an
accounting of disclosures of PHI,as required by 45 C.F.R.164.528 and HITECH.
14. Other Obligations.To the extent that Business Associate is to carry out one or more of a Covered Entity's obligations under the Privacy Rule,Business
Associate shall comply with such requirements that apply to the Covered Entity in the performance of such obligations.
15. Judicial and Administrative Proceedings.In the event Business Associate receives a subpoena,court or administrative order or other discovery request or
mandate for release of PHI,the affected Covered Entity shall have the right to control Business Associate's response to such request,provided that,such
control does not have an adverse impact on Business Associate's compliance with existing laws.Business Associate shall notify the Covered Entity of the
request as soon as reasonably practicable,but in any event within seven business days of receipt of such request.
16. Availability of Books and Records.Business Associate hereby agrees to make its internal practices,books,and records available to the Secretary of the
Department of Health and Human Services for purposes of determining compliance with the HIPAA Rules.
17. Breach of Contract by Business Associate.In addition to any other rights a party may have in the Agreement,this Addendum or by operation of law or in
equity,either party may:i)immediately terminate the Agreement if the other party has violated a material term of this Addendum;or ii)at the non-breaching
party's option,permit the breaching party to cure or end any such violation within the time specified by the non-breaching party.The non-breaching party's
option to have cured a breach of this Addendum shall not be construed as a waiver of any other rights the non-breaching party has in the Agreement,this
Addendum or by operation of law or in equity.
18. Effect of Termination of Agreement.Upon the termination of the Agreement or this Addendum for any reason,Business Associate shall return to a Covered
Entity or,at the Covered Entity's direction,destroy all PHI received from the Covered Entity that Business Associate maintains in any form,recorded on any
medium,or stored in any storage system.This provision shall apply to PHI that is in the possession of Business Associate,subcontractors,and agents of
Business Associate.Business Associate shall retain no copies of the PHI.Business Associate shall remain bound by the provisions of this Addendum,even
after termination of the Agreement or Addendum,until such time as all PHI has been returned or otherwise destroyed as provided in this Section.For the
avoidance of doubt,de-identified Customer Data shall not be subject to this provision.
19. Iniunctive Relief.Business Associate stipulates that its unauthorized use or disclosure of PHI while performing services pursuant to this Addendum would
cause irreparable harm to a Covered Entity,and in such event,the Covered Entity shall be entitled to institute proceedings in any court of competent
jurisdiction to obtain damages and injunctive relief.
20. Owner of PHI.Under no circumstances shall Business Associate be deemed in any respect to be the owner of any PHI created or received by Business
Associate on behalf of a Covered Entity.
21. Safeguards and Appropriate Use of Protected Health Information.Covered Entity is responsible for implementing appropriate privacy and security
safeguards to protect its PHI in compliance with HIPAA.Without limitation,it is Covered Entity's obligation to:
21.1. Not include PHI in information Covered Entity submits to technical support personnel through a technical support request or to community support
forums.In addition,Business Associate does not act as,or have the obligations of a Business Associate under the HIPAA Rules with respect to
Customer Data once it is sent to or from Covered Entity outside ESO's Software over the public Internet;and
21.2. Implement privacy and security safeguards in the systems,applications,and software Covered Entity controls,configures and connects to ESO's
Software.
22. Third Party Rights.The terms of this Addendum do not grant any rights to any parties other than Business Associate and the Covered Entity.
23. Signatures.The signatures to the Agreement(or the document evidencing the parties'adoption thereof)indicate agreement hereto and shall be deemed
signatures hereof,whether manual,electronic or facsimile.
J
H
z
W
LL
Z
O
U
LU
N-
r
O
O
ei
O
N
5
2
O
W
0
N
h0
I
a