HomeMy WebLinkAbout21-1231 LevrumCODE3 STRATEGIST SOFTWARE SUPPORT AGREEMENT
This SOFTWARE SUPPORT AGREEMENT ("this Agreement") is made and entered into this
:3 / V,
day of _2021, by and between the City of Elgin Illinois, a municipal corporation
(hereinafter referred to as ("City") and Levrum, Inc., an Oregon corporation, (hereinafter referred to as
"Levrum" or "Seller").
RECITALS
WHEREAS, Levrum and the City each intend to enter into an End -User Agreement (the "License
Agreement') under which City shall obtain a nonexclusive, nontransferable license to use certain computer
programs in object code form and related user documentation known as Code3 Strategist (the "Software
Application") on certain terms and conditions; and
WHEREAS, Levrum desires to offer City certain services with respect to the Software Application on the
terms and conditions set forth herein and as described by Attachments A through E, attached hereto and
made a part hereof;
WHEREAS, City shall purchase, and Levrum shall sell the goods and/or services described by Attachments
A through E.
NOW, THEREFORE, for and in consideration of the mutual promises and covenants contained herein,
the sufficiency of which is hereby mutually acknowledged, the parties hereto, hereby agree as follows:
The above recitals are hereby incorporated into and made a part of this Agreement as if fully recited hereby.
Section 1. DEFINITIONS
For the purposes of this Agreement, the following definitions shall apply to the respective capitalized terms.
1.1 "Enhancement." Any modification or addition that, when made or added to the Software Application,
materially changes its utility, efficiency, functional capability, or application, but that does not constitute
solely an Error Correction. Enhancements may be designated by Levrum as minor or major, depending on
Levrum's assessment of their value and of the function added to the preexisting Software Application.
1.2 "Error." Any failure of the Software Application to conform substantially to its functional
specifications as published from time to time by Levrum. However, any nonconformity resulting from
City's misuse, improper use, alteration, or damage of the Software Application, or City's combining or
merging the Software Application with any hardware or software not supplied or identified as compatible
by Levrum, shall not be considered an Error.
1.3 "Error Correction." Either a modification or an addition that, when made or added to the Software
Application, establishes material conformity of the Software Application to the functional specifications,
or a procedure or routine that, when observed in the regular operation of the Software Application,
eliminates the practical adverse effect on City of such nonconformity.
Page 1 of 6
1.4 "Software Application." The computer programs known as Code3 Strategist, including any extracts
from such programs, derivative works of such programs, or collective works including such programs (such
as subsequent Releases) to the extent offered to City under this Agreement or the License Agreement.
1.5 "Releases." New versions of the Software Application, which may include both Error Corrections and
Enhancements.
1.6 "Term." An initial period terminating on December 31, 2022. Thereafter, the Term shall automatically
renew for successive periods of one (1) year each unless and until terminated pursuant to Section 6 hereof.
In no event, however, shall the Term extend beyond the term of the License Agreement.
1.7 "Valid Support Issue." A suggestion, question or problem originated or experienced by an employee
or agent of City relating to: (1) installation or configuration of the Software Application; (2) proper
operation of an Enhancement newly developed since such employee or agent received training on the
Software Application; (3) suspected or actual Errors in the Software Application; (4) suggestions for
Enhancements to the Software Application.
1.8 "Valid Support Contact." Any contact initiated by an employee or agent of City who has been trained
by Levrum in the operation of the Software Application, where such contact is related to a Valid Support
Issue.
Section 2. SCOPE OF SERVICES
During the Agreement term, Levrum shall render the following services in support of the Software
Application, subject to the compensation fixed for each type of service in Levrum's rate schedule as
provided for herein.
2.1 Levrum shall maintain an online electronic forum and provide telephone support access during its
normal business hours that allows Customer to report system problems and to seek assistance in use of the
Software Application.
2.2 Levrum shall maintain a trained staff capable of rendering the services set forth in this Agreement.
2.3 Levrum shall not be responsible for correcting Errors in any version of the Software Application other
than the most recent Release of the Software Application.
2.4 Levrum may, from time to time, issue new Releases of the Software Application to its customers
generally, containing Error Corrections, minor Enhancements, and, in certain instances if Levrum so elects,
major Enhancements. Levrum shall make such new Releases available to City, without additional charges.
2.5 Levrum may, from time to time, offer major Enhancements to City generally for an additional charge
upon written agreement by the parties.
2.6 Levrum shall consider and evaluate the development of Enhancements for the specific use of City and
shall respond to City's requests for additional services pertaining to the Software Application (including,
without limitation, data conversion, report -formatting assistance and consultation regarding data analysis
Page 2 of 6
and subject matter expertise), provided that such assistance, if agreed to be provided, shall be subject to
supplemental charges mutually agreed to by Levrum and City.
2.7 Levrum shall employ its best reasonable efforts to resolve Valid Support Issues in a timely fashion.
Levrum shall have no obligation to address issues other than those arising from contacts deemed in
Levrum's sole discretion to be Valid Support Contacts, but may do so from time to time, with or without
charge, without prejudice to the operation of this provision. City shall cooperate to the greatest extent
reasonable to assist Levrum in performing this duty by providing diagnostic information, allowing Levrum
reasonable access to City's computer systems for diagnostic purposes, and such other means as Levrum
may reasonably request.
Section 3. FEES AND CHARGES
3.1 City shall pay Levrum its fees and charges as provided for herein. Levrum reserves the right to change
its rate schedule from time to time, provided that no such change will be effective until at least 30 days
after Levrum has given City written notice of such change, and until City has provided written agreement
as to such change.
3.2 City shall reimburse Levrum for travel expenses (i.e., transportation, lodging, and meals) and other
expenses incurred by Levrum in rendering services to City, as agreed in advance in writing by City.
3.3 Levrum shall invoice City annually for base support and monthly at the beginning of each calendar
month for all other fees and charges accrued, and all reimbursable expenses incurred as provided above,
during the previous month. City shall pay the invoiced amount within 30 days of receipt of such invoice.
All fees shall be inclusive of all freight, shipping and applicable taxes. Levrum hereby waives any and
all claims or rights to interest on money claimed to be due pursuant to this Agreement, and waives any and
all such rights to interest to which it may otherwise be entitled pursuant to law, including, but not limited
to, pursuant to the Local Government Prompt Payment Act (50 ILCS 50511, et seq.), as amended, or the
Illinois Interest Act (815 ILCS 205/1, et seq.), as amended. The provisions of this paragraph shall survive
any expiration, completion and/or termination of this Agreement.
3.4 City shall be responsible for procuring, installing, and maintaining all computers, telephone lines,
networks, communications interfaces, and other equipment and conditions necessary to operate the
Software Application and to obtain from Levrum the services called for by this Agreement.
Section 4. PROPRIETARY RIGHTS
4.1 Error Corrections or Enhancements or any other program, including any new programs or components,
or any compilations or derivative works provided by Levrum shall be subject to the terms of the License
Agreement.
4.2 The Software Applications and all related software provided by Levrum under this Support Agreement,
including any associated intellectual property rights, are and shall remain the sole property of Levrum,
regardless of whether City, its employees, or contractors may have contributed to the conception of such
work, joined in the effort of its development, or paid Levrum for the use of the work product. City shall
from time to time take any further action and execute and deliver any further instrument, including
documents of assignment or acknowledgment, that Levrum may reasonably request in order to establish
Page 3 of 6
and perfect its exclusive ownership rights in such works, including any associated intellectual property
rights.
Section 5. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY
5.1 EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT AND THE LICENSE
AGREEMENT, LEVRUM EXPRESSLY DISCLAIMS ANY WARRANTY CONCERNING THE
SOFTWARE APPLICATION OR THE SERVICES TO BE RENDERED HEREUNDER, WHETHER
EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF FITNESS
FOR A PARTICULAR PURPOSE; PROVIDED, HOWEVER, THAT AN IMPLIED WARRANTY OF
MERCHANTIBILITY SHALL BE IN EFFECT.
5.2 In no event shall either party hereto be subject to cumulative liability for any claim arising in connection
with this Agreement exceed the total fees and charges paid to Levrum by City within the year prior to the
event giving rise to the liability. In no event shall either party be liable for any indirect, consequential,
special, exemplary, or incidental damages of whatever kind and however caused, even if such party knew
or should have known of the possibility of such damages.
5.3 No action, whether based in contract, strict liability, or tort, including any action based on negligence,
arising out of the performance of services under this Agreement, may be brought by either party and/or its
affiliates, officers, employees, agents, attorneys, boards and commissions more than one year after such
cause of action accrued, except that an action for nonpayment may be brought within two years of the date
of the last payment.
Section 6. TERMINATION
6.1 This Agreement may be terminated as follows:
6.1.1 This Agreement shall immediately terminate upon the termination of the License Agreement;
6.1.2 This Agreement may be terminated by either party upon the expiration of the then current
term of this Agreement, provided that at least sixty days' prior written notice is given to the other
party; or
6.1.3 This Agreement may be terminated by either party upon sixty days' prior written notice if the
other party has materially breached the provisions of this Agreement and has not cured such breach
within such notice period.
6.2 Following termination of this Agreement, Levrum shall immediately invoice City for all accrued fees
and charges and all reimbursable expenses, and City shall pay the invoiced amount within 30 days of receipt
of such invoice. City may continue to use any work supplied to City by Levrum for the remaining term of
the License Agreement.
6.3 The fiscal year of the City is the 12 month period ending December 31. The obligations of the City
under any contract for any fiscal year are subject to and contingent upon the appropriation of funds
sufficient to discharge the obligations which accrue in that fiscal year and authorization to spend such
funds for the purposes of the contract.
Page 4 of 6
If, for any fiscal year the term of the CONTRACT, sufficient funds for the discharge of the City's
obligations under the contract are not appropriated and authorized, then the CONTRACT shall terminate
as of the last day of the preceding fiscal year, or when such appropriated and authorized funds are
exhausted, whichever is later, without liability to the City for damages, penalties or other charges on
account of such termination.
Section 7. MISCELLANEOUS
7.1 Each party acknowledges that it has read this Agreement, understands it, and agrees to be bound by its
terms. The parties further agree that this is the complete and exclusive statement of the agreement of the
parties with respect to the subject matter hereof and that it supersedes, controls and merges all prior
proposals, understandings, and agreements, whether oral or written, between the parties with respect to the
subject matter hereof. This Agreement may not be modified except by a written instrument duly executed
by the parties hereto.
7.2 This Agreement and the parties' obligations hereunder shall be governed, construed, and enforced in
accordance with the laws of the State of Illinois. Venue for the resolution of any disputes or the
enforcement of any rights arising out of or in connection with this Agreement shall be the Circuit Court of
Kane County, Illinois. Levrum hereby irrevocably consents to the jurisdiction of the Circuit Court of Kane
County, Illinois for the enforcement of any rights, the resolution of any disputes and/or for the purposes
of any lawsuit brought pursuant to this Agreement or the subject matter hereof, and Levrum agrees that
service by first class U.S. mail to Levrum, Inc., 408 SW Monroe Ave., Suite M240, Corvallis, OR 97333
shall constitute effective service. Both parties hereto waive any rights to a jury.
7.3 In the event that any provision of this Agreement is held invalid, illegal, or unenforceable, the remaining
provisions shall be enforced to the maximum extent permitted by applicable law.
7.4 Neither party may assign its rights or duties under this Agreement without the prior written consent of
the other party, except to a successor of all or substantially all of its business and properties.
7.5 The waiver by either party of any term or condition of this Agreement shall not be deemed to constitute
a continuing waiver thereof nor of any further or additional right that such party may hold under this
Agreement.
7.6 Notwithstanding any other provision of this Agreement, it is expressly agreed and understood that in
connection with the performance of this Agreement, Levrum shall comply with all applicable federal, state,
city and other requirements of law, including, but not limited to, any applicable requirements regarding
prevailing wages, minimum wage, workplace safety and legal status of employees. Without limiting the
foregoing, Levrum hereby certifies, represents and warrants to the City that all of Levrum's employees
and/or agents who will be providing products and/or services with respect to this Agreement shall be legally
authorized to work in the United States. Levrum shall also, at its expense, secure all permits and licenses,
pay all charges and fees, and give all notices necessary and incident to the due and lawful prosecution of
the work, and/or the products and/or services to be provided for in this Agreement. The City shall have
the right to audit any records in the possession or control of Levrum to determine Levrum's compliance
with the provisions of this section. In the event the City proceeds with such an audit, Levrum shall make
available to the City Levrum's relevant records at no cost to the City. City shall pay any and all costs
associated with any such audit.
Page 5 of 6
7.7 This Agreement may be executed in counterparts, each of which shall be an original and all of which
shall constitute one and the same Agreement. For the purposes of executing this Agreement, any signed
copy of this Agreement transmitted by fax machine or e-mail shall be treated in all manners and respects
as an original document. The signature of any party on a copy of this Agreement transmitted by fax
machine or e-mail shall be considered for these purposes as an original signature and shall have the same
legal effect as an original signature. Any such faxed or e-mailed copy of this Agreement shall be
considered to have the same binding legal effect as an original document. At the request of either party
any fax or e-mail copy of this Agreement shall be re -executed by the parties in an original form. No party
to this Agreement shall raise the use of fax machine or e-mail as a defense to this Agreement and shall
forever waive such defense.
7.8 The terms of this Agreement shall be severable. In the event any of the terms or the provisions of this
Agreement are deemed to be void or unenforceable for any reason, the remainder of this Agreement shall
remain in full force and effect.
7.9 In the event of any conflict between the terms and provisions of this Agreement and any Attachments
hereto, the terms and provisions of this Agreement shall supersede and control. In the event of any conflict
between Attachment A and any other attachments hereto, Attachment A shall supersede and control.
7.10. Notwithstanding anything to the contrary provided for herein, City shall retain exclusive ownership
of all City generated and/or supplied data. In no event shall such City related data or information be used
by Levrum without the prior written consent of the City.
IN WITNESS WHEREOF, the parties have caused this Agreement to be executed by their duly authorized
representatives as set forth below.
LEVRUM, INC. CITY OF ELGIN
_Douglas Baily
Print Name
Signature
_President
Title
� i 6"4 G - V��_ 'W
Ric and G. Kozal, City Manager
Attest:
Ci1WIerk
Legal Dept\Agreement\Levrum-Code3Strategist.SupportAgreement-Clean-12-29-21.docx
Page 6 of 6
ATTACHMENT A
PROPOSAL FOR PROVISION OF CODE3STRATEGIST
SOFTWARE AND ASSOCIATED SERVICES
Date: 19 March 2021 Customer: City of Elgin
SCHEDULE OF GOODS AND SERVICES
Item
I Description
Price
la
Code3Simulator 2.9.3 software enterprise license, valid for simulating up to
$14,880.00*
13,000 events annually, related to the normal operations of, and for the sole use
of authorized employees and agents of City. Enterprise license allows any
*Reflects CPSE
authorized agent of City to operate Software, subject only to geography and
discount provided on
incident volume restrictions inherent in the License terms. License price
quote dated 16 March
includes 3 days of training at Levrum's premises, software installation media or
2021.
download and current documentation. Year one support is included in the
license price. Software sale, installation and use is subject to a separate Software
License Agreement attached to this proposal.
lb
Code3Simulator 2.9.3 software term limited enterprise license, valid for
$27,900.00**
simulating up to 13,000 events annually, related to the normal operations of, and
($9,300.00/year, years 1 — 3)
for the sole use of authorized employees and agents of City. Term limited
enterprise license allows any authorized agent of City to operate Software,
** Reflects CPSE discount
subject only to geography and incident volume restrictions inherent in the
provided on quote dated 16
License terms. License price includes 3 days of training at Levrum's premises,
March 2021.
software installation media or download and current documentation. Year one
support is included in the license price. Software sale, installation and use is
subject to a separate Software License Agreement attached to this proposal.
After third payment, license will convert from a term limited enterprise license to
a perpetual enterprise license.
2a
Code3Simulator software annual support package, entitling City to online
$5,580.00
technical support, periodic maintenance software releases and standard product
software upgrades, as governed by the separate Software Support Agreement
attached to this proposal. Begins year two.
$5,580.00
2b
Code3Simulator software annual support package, entitling City to online
technical support, periodic maintenance software releases and standard product
software upgrades, as governed by the separate Software Support Agreement
attached to this proposal. Begins year four.
$0.00
3
Code3 Simulator user training, three days, for up to six users, per Course Syllabus
attached to this proposal. Training to be delivered at Levrum's premises unless
(see NOTE 1)
otherwise mutually agreed in advance. NOTE 1: direct expenses without markup
are charged for training delivered at location of Customer's choice.
4
Data conversion services necessary to import City's incident, geographic and
Not presently anticipated.
operational data, supplied according to the Data Specification attached to this
proposal. Data not conforming to the Data Specification will result in
additional charges.
5
Additional services as detailed in Attachment A to this Proposal.
Not presently anticipated; may
be added b� mutual agreement.
Total of charges
TBD based on option 1 a or
lb above.
M aJO L i
One third (33%) due at contract
signing.
One third (33%) due at completion of
training.
Final Payment (34%) due at
acceptance; 10 business days after
completion of training and within 30
days of receipt of invoice, whichever
is later.
FALegal Dept\Agreement\Levrum-Code3Strategist.SupportAgreement-Attachment A-Clean-4-27-21.docx
ATTACHMENT B
LICENSE AGREEMENT FOR
CODE3 STRATEGIST SOFTWARE
LICENSE TERMS
Levrum grants you a non-exclusive, non -transferable, limited right to use the Software
Application only for your governmental agency under the following terms.
Use on a PC. You have the right to obtain an unlimited number of licenses to an unlimited
number of copies of the Software Application only for your internal use by your employees
on computers under the control of your agency. You are responsible for installing the
Software Application on computers and equipment that comply with Levrum specifications
and documentation.
OTHER LIMITATIONS
You may not rent, lease, re -license, transfer, nor lend the Software Application. You may
not reverse engineer, decompile, modify, or disassemble the Software Application, except and
only to the extent that such activity is expressly permitted by applicable law notwithstanding
this limitation. You agree not to remove any copyright or other notice of proprietary rights in
the Software Application. You are responsible for ensuring that all users of the Software
Application comply with the terms of this Agreement.
Levrum may provide you with support services related to the Software Application
("Support Services"). Use of Support Services is governed by Levrum policies and programs
described in the user manual, in online documentation, and/or in other Levrum-provided
materials. Any supplemental software code provided to you as part of the Support Services
shall be considered part of the Software Application and subject to the terms and conditions
of this Agreement. With respect to technical information you provide to Levrum as part of the
registration of your license to the Software Application or in connection with the Support
Services, Levrum may use such information for its business purposes, including for product
support and development.
When you cease using the Software Application or upon termination of the license, you
agree to return all copies of the Software Application (including all component parts, the
media and printed materials, any upgrades and your registration), and certify the destruction
of all digital or electronic copies thereof.
Without prejudice to any other rights, Levrum may terminate this Agreement if you fail to
comply with the terms and conditions of this Agreement. In such event, you must destroy all
copies of the Software Application and all of its component parts, certify such destruction,
and Levrum may suspend or deactivate your use of the Software Application with or without
notice.
GOVERNING LAW
This Agreement shall be governed by the laws of the State of Illinois.
Pagel of 3
PROPRIETARY RIGHTS
Copyright. All ownership, title and copyrights in and to the Software Application
(including, without limitation, any images, photographs, animations, video, audio, music, text,
and "applets" incorporated into the Software Application), the accompanying media and
printed materials, and any copies of the Software Application are owned by Levrum or its
suppliers. The Software Application is protected by copyright laws and international treaty
provisions. Therefore, you must treat the Software Application like any other copyrighted
material, subject to the provisions of this Agreement.
U.S. Government Restricted Rights. The Software Application and documentation are
provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data
and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of
the Commercial Computer Software -- Restricted Rights at 48 C.F.R. 52.227-19, as
applicable. Manufacturer for such purpose is Levrum Incorporated., PO Box 2292, Corvallis,
OR 97339. You agree not to export the Software Application or any results obtained from its
use in violation of any export restriction laws or regulations.
Submissions. Should you decide to transmit to any electronic medium controlled by
Levrum by any means or by any media any materials or other information (including, without
limitation, ideas, concepts or techniques for new or improved services and products), whether
as information, feedback, data, questions, comments, suggestions or the like, you agree such
submissions are unrestricted and shall be deemed non -confidential and you automatically
grant Levrum and its assigns a nonexclusive, royalty -free, worldwide, perpetual, irrevocable
license, with the right to sublicense, to use, copy, transmit, distribute, create derivative works
of, display and perform the same.
Open Source Software. The Software Application makes use of Open Source Software
components. Notwithstanding anything herein to the contrary, Open Source Software is
licensed to you under such Open Source Software's own applicable license terms, which can
be found at the "Help I Open Source License Info" option of the Software Application's main
menu. The documentation or, as applicable, the corresponding source files for the software,
are available via links contained in the information provided by the "Help I Open Source
License Info" option of the Software Application's main menu. These Open Source Software
license terms are consistent with the license granted in this Agreement and may contain
additional rights benefiting you. The Open Source Software license terms shall take
precedence over this agreement to the extent that this Agreement imposes greater restrictions
on you than the applicable Open Source Software license terms. Notwithstanding the
foregoing, Levrum will have no obligation under this Agreement or otherwise with respect to
any claim based on: (i) a combination comprised of primarily Open Source Software with
Levrum's Software Application; (ii) use for a purpose or in a manner for which Levrum's
Software Application was not designed; (iii) use of any older version of Levrum's Software
Application when use of a newer revision would have avoided the infringement; (iv) any
modification to Levrum's Software Application made without Levrum's express written
approval; (v) any claim that relates to Open Source Software or freeware technology or any
derivatives or other adaptations thereof that is not embedded by Levrum; or (vi) any other
claim or action of liability or infringement arising from the use of such Open Source
Software. This provision states your sole and exclusive remedy and Levrum's entire liability
for any infringement claims or actions.
Page 2 of 3
DISCLAIMER OF WARRANTY
This software application and the accompanying files are provided subject to the LIMITED
WARRANTY that the software shall perform substantially in accordance with its published
specifications for an acceptance period of 60 days subsequent to execution of this Agreement.
Levrum's liability for a defective copy of the software application shall be limited exclusively to:
(a) Levrum's best professional efforts to remedy such defects in accordance with the terms of the
current Code3 Strategist Software Support Agreement referencing this agreement; (b) replacement
of your copy of the software application with another copy; or refund of the initial license fee
Levrum received from you for the defective copy of the product.
Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or
special damages, or the exclusion of implied warranties or limitations on how long a given warranty
may last, so the above limitations may not apply to you.
Page 3 of 3
LEv;2UM
DATA TEC H N O LOG I E S
www.levrum.com
Elgin IL: Attachment C
Schedule of Additional Services
Services outside the scope of these deliverables will incur additional hourly charges according to
Table 1. Such services shall be undertaken only upon prior approval by an authorized official
of Customer after having been provided with sufficient and accurate information by Levrum
concerning the nature and necessity of the deviation. Customer and Levrum may negotiate fixed
fees for such work on a case -by -case basis, by mutual agreement, in advance of any such work.
Table 1: Hourly Rates for Work Outside of Scope
Level of Work
Hourly Rate
Engineer l / Data Analyst
$70.00
Engineer II / Software Architect
$110.00
Engineer III / Data Scientist / Domain Expert
$140.00
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVUM
DATA TECH NO LOG I E S
www.levrum.com
Elgin IL: Attachment D
Training Syllabus
This document presents an overview of prerequisites necessary for, and topics covered in Code3
Strategist user training at the awareness, operations, and technician levels. It is an outline only;
content may vary based on attendees' expertise, interests, abilities, and the specific needs of the
organization.
Preparation and Prerequisites
Training Environment
1. Every class attendee should have a Windows -based laptop computer. Minimum suggested
configuration is:
1.1. Windows 7TM or later operating system (64-bit required)
1.2. 8Gb RAM
1.3. 30Gb hard drive space free
1.4. Attendee must have permission to install software on this computer.
1.5. Attendee must have permission to create subdirectories of the main drive root (e.g., c:\).
2. Having Microsoft OfficeTM (Excel, Word and PowerPoint) on the same computer will be
helpful but is not required.
3. Attendee must have the ability to access internet via his/her laptop computer.
4. Classroom should have space for projecting video displays that are comfortably visible to
attendees. Whiteboards in proximity to video projection are helpful. It should be reasonably
free from interruptions (we are realistic, and know you have a fire department to run!)
Data and Installation Prerequisites
The following steps must be completed prior to beginning Code3 Strategist training:
1. Current Code3 Strategist software must be installed on the appropriate computer for each
trainee. (It is acceptable for students to pair up, two per computer, if necessary).
2. The following data must be supplied to Levrum at least 14 days prior to the beginning of
training. This enables us to prepare your environments so that you can begin modeling
immediately on Day 1 of training. You will learn the steps necessary to clean and import
data on Days 2 and 3 of training:
a. Call/incident and unit response data as described in the Code3 Strate ist Data
Specification.
b. Station locations and apparatus and staff complements for typical operational units,
e.g., engine, truck, medic, and command units.
c. Categorization of nature codes from item (a) into basic incident cause groupings
d. An overview of typical response rules
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
L_EV;2U
DATA T EC H NO LOG I E S
www.levrum.com
e. OPTIONAL: shapefiles for any regions you desire to use within Code3 Strategist
during training, compatible with the Code3 Strategist shapefile import tool. (We will
train you in the shapefile import process).
Day One
1. Introductions, contact information
2. Verify installation of Code3 Strategist software
3. Theory: why do we plan?
3.1. What is deployment analysis?
3.1.1. How big a problem space is this?
3.2. What are simulation and modeling and how can they help?
4. Class Exercise 1.1: load training base model
5. Theory: how does simulation work?
5.1. Cause/Time/Geography —effects on resource allocation
6. Practical: basic editing; what is a "model?"
7. Class Exercise 1.2: basic model editing
7.1. Creating, deleting, copying, renaming, importing, exporting models
7.2. Locking models
7.3. Basic model editing — moving people, apparatus, stations.
8. Theory: Running simulations. What happens "under the hood?" Q&A discussion.
8.1. Contents of a call file
8.2. Run options: routing, audit
8.3. Call file consistency checker
9. Class Exercise 1.3: run a model, look at results.
9.1. Call details
10. Demo: looking at simulation results
11. Class Exercise 4: analyzing individual simulation results
11.1. What does "(A)" mean?
11.2. Filtering results
11.3. `Enhanced Details"
11.3.1. Audit and route info
11.3.2. Data grid operations
11.3.3. Data charting
11.3.4. Details map operations
11.4. Group summary report
12. Practical: Time filtering
13. Class Exercise 1.5: building alternate models with time filters
14. Practical: Basic model comparison
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVRUM
DATA T E C H NO LOG I E S
www.levrum.com
15. Class Exercise 1.6: build, run and compare two models.
16. Q&A / Discussion
17. Homework assignment / challenge (assign study groups)
Day Two
1. Review, Q&A
2. Present homework results. Collectively assign scorn and applause.
3. Theory: cause/time/geography — dispatching rules
4. Class Exercise 2.1:
4.1. modifying dispatch rules
4.2. the cause/nature hierarchy
4.2.1. Importing nature codes
5. Theory/Demo: tools to make model maintenance easier
6. Class Exercise 2.2: Model Diffs
7. Class Exercise 2.3: Consistency Checker
8. Theory: How do we know what model is best?
8.1. Evaluation metrics
8.2. Derived metrics
8.3. Modes of comparison
9. Class Exercise 2.4: Comparing models
9.1. Standard comparison
9.1.1. Comparison map
9.1.2. Raw comparison data
9.1.3. Utilization and percentile charts
9.2. Aggregate comparison
10. Class Exercise 2.5: Comparing different datasets — Agnostic comparison
11. Theory: validating simulation results
12. Demo: validation techniques
13. Class Exercise 2.6: validation tools
13.1. Selected audit
13.2. Sensitivity analysis
13.3. Real -world comparison
14. Theory/Demo: Exploring your data
15. Class Exercise 2.7: data exploration
15.1. Data grid operations — aggregate, crosstab,
15.2. Data charting
15.3. Call mapping
15.4. Exporting data
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV;2U{w1►!
DATA T E C H NO LOG I E S
www.levrum.com
15.5. Inter -operating
16. Class Exercise 2.8: Debugging I — find a problem in a "broken" model
17. Q&A / Discussion
18. Homework assignment / challenge
Day Three
1. Review, Q&A
2. Homework presentation, evaluation
3. Sharing work: importing and exporting models and results
4. Class Exercise 3.1: importing/exporting each other's work
5. Ongoing maintenance
5.1. Downloading software and map file updates
5.2. Importing licenses
5.3. Getting support — online or telephone
5.4. Diagnostic procedures
6. Class Exercise 3.2: cause an error and email us a problem report
7. Class Exercise 3.3: Debugging II (harder debugging problems)
8. Inter -operating with other systems
8.1. Routing: Taxi, OSM, ESRI (and maybe Google)
8.2. Exporting shapefiles
8.3. Exporting data
8.4. Importing call data
9. Class Exercise 3.4: exporting shapefiles
10. Predicting growth effects — Incident Builder
11. Class Exercise 3.5: Simulating a new development with Incident Builder
12. Real World Data
12.1. Comparison
12.2. Generating real -world datasets
13. Advanced maintenance
13.1. File locations
13.2. Configuration file settings
14. Best practices
15. Base model project plan
16. Introduction to related applications:
16.1. Building future event models with Code3 Visionary
16.2. Web visualizations with Code3 Firewatch
17. Theory: the future of deployment analysis
18. Discussion: where do you think this needs to go?
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
REV UM
DATA T EC H NO LOG I E S
www.levrum.com
Elgin IL: Attachment E
Data Specifications — Version 2.9
Revision November 26, 2018
Contents
1 Introduction 1
1.1 Scope and Applicability 1
1.2 Definition of Terms 1
1.3 CSV Import Format 2
1.4 Hints and Precautions 3
2 Importing Call and Unit Response Data 3
2.1 Overview 3
2.2 Call Data 5
2.3 Unit Response Data 7
2.3.1 Unit Response Field Semantics 8
3 Cause/Nature Code Import 10
4 Geospatial Projection Format 11
1 Introduction
1.1 Scope and Applicability
This document describes external data interface specifications for Levrum's Code3 Strategist
product. This document version is believed to be correct and complete as of the 2.9 product
version.
1.2 Definition of Terms
The following jargon, acronyms and domain -specific terms are used in this document:
• CAD: acronym for "Computer Aided Dispatch" — generic term for computerized system
that dispatches incidents and (typically) records timing benchmarks.
• "Call data" (also called "incident data") is data that applies to a single emergency
incident. Call data has one row per incident, and typically contains an incident ID, date/time,
nature code and location, among other items.
• CSV: "Comma -Separated Value" — a data format that allows data interchange among
Code3 Strategist and spreadsheet and database tools.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVRUM
DATA TECH NO LOG I E S
www.levrum.com
• HIPAA: the Health Insurance Portability and Accountability Act of 1996 and
amendments. Its privacy requirements are directly relevant to the incident data whose format
is specified in this document.
• RMS: "Records Management System" — a database application used by fire/EMS
agencies to maintain all information relevant to emergency incidents.
• "Unit response data" is data that applies to a single unit's response to an emergency
incident. Unit response data has one row for each unit that responded to an incident,
typically contains timing information about the unit's response, and must contain an incident
ID to link to the appropriate call data record.
1.3 CSV Import Format
Many of the import functions in Code3 Strategist allow you to use the popular "CSV"
(for Comma -Separated Value) format for your input data, as specified by IETF RFC4180
(http://tools.ietf.orL,/html/rfc4l 8O). This is the CSV format familiar to users of Microsoft
Exce1TM, SQL ServerTM and other spreadsheets and database tools. Note that field values with
embedded spaces are typically enclosed in double quotes. Field values with embedded commas
must be enclosed within double quotes.
Each CSV file consists of a header record, followed by one or more data records. The header
record specifies the names of fields that appear in subsequent data records. Field names in
header records and field values in data records are separated by commas. Field names or values
may be enclosed in quotation marks as specified in IETF RFC4180.
The standard import tool allows CSV file fields to be laid out in any order, so long as the correct
fieldnames are specified in the header record.
The header record contains a comma -separated string of field names, in an order exactly
corresponding to their appearance in the data records. The header record is mandatory, and it
must be the first record in the file.
The example below shows part of an example CSV-formatted call file.
UniqueId,NatureCode,DispatchDate,DispatchTime,StreetAddr,XLoc,YLoc,TransportFlg
XFD201408220412,DCXP,08-22-2014,14:28:42,"1200 NW Jefferson",7432918,334201,Y
XFD201408220419,CARFIR,08-22-2014,14:58:11,"2700 SW Wilkins",7419096,335575,N
1.3.1 Specific Headers Not Required
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVUM
DATA TECH NO LOG I E S
www.levrum.com
NOTE: as of Version 2.9, Code3 Strategist no longer requires specific headers in input files.
Instead, it relies on "field mappings" that you establish in advance in the import tool (described
in the Code3 Strategist 2.9 User Manual Section 4.4.1.1) to identify which fields in the input files
will be imported into what fields in Code3 Strategist.
1.4 Hints and Precautions
There are a few considerations you should keep in mind when importing data into Code3
Strategist via CSV files:
1. The ordering of columns in the import CSV files is not important. However, spelling the
names of the column titles correctly is essential.
2. For backward compatibility reasons, the call file and the unit response file use slightly
different date/time formats. The call file has two separate columns for date and time, while
the unit response file uses a combined "MM/DD/YYYY hh:mm:ss" format for its time fields.
3. It is important to have data precise to seconds in both the call and the unit response files,
so that internal timing factors will be calculated accurately. NOTE that Microsoft Exce1TM
defaults time formats to minutes only, even though the internal date may be precise to
seconds. This means that if you open a CSV file in Excel and subsequently save it, Excel
will strip the seconds out of the saved CSV file! In order to avoid this problem, if you edit a
CSV file in Excel, you should make sure to format columns involving time as "hh:mm:ss",
and date/times as "mm/dd/yyyy hh:mm:ss", using Format Cells I Number I Custom right -
click menu item. The figure below illustrates the problem (the upper box showing the
internal data precise to seconds, and the lower showing the default formatting truncated to
minutes that would be saved to the CSV file) and the solution (Custom formatting as
described above):
ISY 12/15 f 2015 8:31:47 AM
A 6
1
2 Incident ID Dispatched
3 1 IV15/2016
�4
5
Categ o ry.
General
Sample
Number
12/15/20160831:47
Currency
Accounting
Type;
Date
/dd mm i
/yyyy hh,mm:ss
Time
Percentage
d-mmm
Fraction
mmm-yy
Scientific
h:mm AM/PM
Text
h:mm:ss AM/PM
Special
h.mm
IM-WMIR I
h!mm!cc
2 Importing Call and Unit Response Data
2.1 Overview
Code3 Strategist uses call and unit response data in its process of predictive modeling:
• Call data:
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV;2UM
DATA TECH NO LOG I E 5
www.levrum.com
o Is "replayed" against alternate deployment models to simulate and analyze their
behavior
o Is used for analysis and mapping of your incident history
o Is require (at least the required fields listed below) to operate the simulator
o Has one record per incident
Unit response data:
o Is desirable, but not required for operating the simulator
o Is used to calculate statistics used by the simulator, such as average scene time by
unit and nature, typical travel speeds, etc.
o Can be used to understand your agency's performance using Code3 Strategist's
data exploration features.
o Has one record per unit that responded to each incident.
Example call and unit response data are shown in the example below. (Note that this view is
simplified, and column names are not shown as they would be for an actual data import). In this
example, the blue columns represent call data and tan columns represent unit response data. The
red lines show the association between call records and unit response records. In this example,
only M122 responded to the 8:11 chest pain call, but T151, E134 and C210 responded to the
9:05 fire alarm call.
Call Data
Unit Rasponce Data
Incident ID
Dispatch Date
Dis tch Time
Nature
Address
Incident ID
Unit
Di tched
Arrived
Cleared
I 1
12/15/2016
9:31:47
CHXPAIN
1200 NW MAPLE
1
MM
12/15/201608:31:47
W15/201609:35.14
17J75/201609:41:11
2
12/25/2016
852:31MVA-INJ
HWY34E/I-5N
2E131
1Y/15/20160a:52:11
W15/20160857.21
VJ151201609:25:15
3
15 2016
9.05:2
AFA-HIRISK
OSU/SMRH HALL
2
M123
121151201608:52:11
12/15/201609.02.34
12/35/201609:55.49
_
2
C110
12/15/20160852:11
IV15/201609.05:27
17/15/2016095952
12/15/201509:09:03
12/15/201609:26:12
12/15/201609:21:45
3
T151
3
E134
Uj /201609:05:2
12/15/2016:7A9
17f15/201609:21:45;
3
C210
12/1S/201609:0.5:2
12/15/Z01609:14:31
17125/201609:M45:
Code3 Strategist's call import feature imports both call and unit response data simultaneously:
unit response data must reference call data to build a complete set of real -world data. Both
forms of data can be imported from CSV files as described in Section 1.3 and follow the data
specifications described in the following subsections.
2.2 Custom Field Definition and Import
As of Version 2.9, Code3 Strategist supports defining importing an unlimited number of custom
fields associated with either call or response data. These fields can be one of three types:
1. Category fields: these are character data that can be used in reports, data
visualizations and dashboards to classify or break down data. Examples might include
shift designation, battalion, division, political subdivisions, special incident flags, patient
gender, etc.
2. Numeric fields: these fields contain numeric data related to either an incident or
a response — e.g., building square footage, patient age, property value saved, vertical
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV:;2UM
DATA TECH NO LOG I E S
www.levrum.com
access height. Numeric fields can be used in reports, data visualizations and dashboards
to perform statistical analyses such as percentiles, fractile compliance and descriptive
statistics.
3. Timestam fields: these are timing data related to incidents or responses. You
can use these to supplement the built-in timing fields provided by Code3 Strategist. For
example, you might use timestamp fields to measure the delay from first company arrival
at a structure fire to the establishment of a permanent water supply, or the bed wait delay
at various hospitals.
The methods for defining and importing custom fields are described in detail in Section 4.4.1.1
of the Code3 Strategist V2.9 User Manual. The important point in the current context is that
you can include almost any fields you want in the call and response files, and these fields can
almost always be imported into Code3 Strategist. The general rule
is, if you think you might.need it, it's worth putting into your import files — Code3 Strategist will
simply ignore any fields you don't tell it to import.
2.3 Call Data
Syntax and semantics of fields within call files are described in the following table. As noted
above, sequencing of fields is not significant within CSV files; nor is the exact title
of the field in the file's header row, as described in Section 1.3.1. Also, the
Code3Strategist importer will ignore fields other than the ones shown below.
Field
Sequence
Field
Number
Name
Required?
Description
1
UniqueId
Yes
a unique identifier for the incident
described by the current record
2
NatureCode
Yes
the nature code describing the cause of the
incident described by the current record.
These are typically provided by your CAD
or RMS system.
3
DispatchDate
Yes
The date on which the incident was
dispatched. Format: mm/dd/yyyy — e.g.,
"10/23/2013". Other formats may be
supported.
4
DispatchTime
Yes
The time at which the incident was
dispatched, in military format, precise to
seconds, e.g., "14:37:22". UTC offsets
are not required.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV72UM
DATA T EC H NO LOG I E S
www.levrum.com
5
StreetAddr
Recommended
A street address for the incident.
This field is not required to operate Code3
Strategist. (To omit this or any field,
leave it empty by appending two
consecutive pipe characters: "I I").
However, we recommend including it,
because doing so makes detailed
simulation results easier for humans to
understand. For HIPAA compliance
purposes, Code3
Strategist r obscures addresses to the
nearest hundred -block in any output.
6
XLoc
Yes
The "X" or east -west location of the
incident, provided either in degrees or
rectangular units. If XLoc units are
rectangular, its coordinate system
must be consistent with the geographic
projection transform described in Section
4.
If not, XLoc should be provided in decimal
degrees of longitude (six decimal digits'
precision preferred) relative to the Prime
Meridian. NOTE: Western Hemishphere
points should be represented as negative
longitude numbers.
7
YLoc
Yes
The "Y" or north -south location of the
incident, provided either in degrees or
rectangular units. If YLoc units are
rectangular, its coordinate system must be
consistent with the geographic projection
transform described in Section 4.
If not, YLoc should be provided in decimal
degrees of latitude (six decimal digits'
precision preferred) relative to the Equator.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVUM
DATA T E C H NO LOG I E S
www.levrum.com
8
TransportFlg
No
Optional field indicating whether or not a
patient was transported on the call. If
present, this field should contain "TRUE"
or "FALSE" to indicate the patient
transport status associated with the call.
9
CancelFlg
No
Optional field indicating whether or not
the call was cancelled prior to the arrival
of any units.
10
CustomContentl
No
Optional field containing customer content
associated with the call. This can be any
string value. This field is included with
the call for filtering and statistical
reporting purposes throughout Code3
Strategist. It can be used for grouping
calls into categories not explicitly
recognized by Code3 Strategist r.
11
CallReceived
Recommended
Date/time call was received by the
dispatch center. Enables calculation of
call processing time, if available. (Call
processing time is calculated as the
difference between dispatch date/time and
call receipt date/time). Format is
MM/DD/YYY
HH:MM:SS — e.g., "2018-02-19 11:37:22"
Additional
Optional
Code3 Strategist versions starting with
Custom fields
2.9 support unlimited custom category,
numeric and timestamp fields, as described
in Section 2.2.
Accordingly, it is recommended that ANY
desirable classifying, numeric or
timestamp information be appended to the
call file.
2.4 Unit Response Data
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV;?,UM
DATA T E C H NO LOG I E S
www.levrum.com
Unit response data, also called "real world data," provides information about how your
jurisdiction performed on calls in your incident history. It provides a basis for comparison to
simulation results from alternate deployment strategy models. The data conversion tool enables
you to import real -world data in a CSV file format as described below.
Unit response import files adhere to the CSV formatting standard as described in Sectionl.3.
Within this formatting convention, they are organized into a sequential text file, with one record
per unit response. Each record covers all aspects of behavior for one unit on a single call. Note
that each record contains a unique ID, which must be identical to the ID specified in the
associated call file (Section 2.3) for the same call. As for call files in CSV format, fields in this
format do not need to be laid out in the order given in the table, so long as the header record
contains the correct field names in the order corresponding to the layout of the data records.
Thus, it is valid to create a file with just the fields to be imported, in any convenient order. Note
that all required fields must be included.
2.4.1 Unit Response Field Semantics
The table below summarizes the semantics of the data fields in a real -world data file. NOTE:
date/time formats are slightly different for unit response files vs. call files — date and time are
separate fields in call files, but the several date/time fields in unit response files are combined
into date/time fields in "MM/DD/YYYY hh:mm:ss" format.
Field
Name Required?
Description
a unique identifier for the incident described by the current record.
UniqueId Yes
This value must correspond exactly to a call specified separately in
an associated call file.
UnitId
Yes
The string identifier for the unit to which the record applies,
e.g., "Engine 82", "M-124" or "373".
UnitType
Suggested
A type designation for the unit. This value can be any string, e.g.,
No
"Medic", "Engine", "Truck", "Tender".
Optional number of staff arriving with the unit. This value must be
NumStaff
an integer.
FromQtrs
Suggested
Flag value indicating whether or not the unit responded from
quarters. Valid values are "TRUE", "FALSE" and no value (empty
string). If no value is supplied, the response origin is considered
indeterminate.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEVRUM
DATA TECHNOLOGIES
www.levrum.com
Dispatched
Yes
Date/time of dispatch. This should be in the MM/DD/YYYY
hh:mm:ss format, called "standard timestamp format" for the
remainder this section. Example: "05/12/2015 18:32:11". Other
reasonable formats are often acceptable, but not guaranteed to be
accepted by the importer.
Responding
Suggested
Timestamp for beginning of response, in standard timestamp format.
Leave this field empty to indicate no data.
OnScene
Yes
Timestamp for unit arrival on -scene. This field should be
populated for all non -cancelled calls. Standard timestamp format
or empty.
C1earScene
Suggested
Time the unit departed the scene. Leave empty for missing data.
Standard timestamp format or empty.
PtDest
No
Patient transport destination if any (e.g., hospital name). Leave
empty if no patient transported.
PtHandoff
No
Time the unit arrived at the patient destination, standard timestamp
format. Leave empty for missing data.
InService
Suggested
Time the unit became available, standard timestamp format. Leave
empty for missing data.
InQuarters
Suggested
Time the unit returned to quarters, standard timestamp format.
Leave empty for missing data.
Urgency
Suggested
Urgency of initial response (string code). "1" = nonemergency;
"3" = emergency.
Missing data is assumed to be emergency response.
Custom
Optional
Code3 Strategist versions starting with 2.9 support unlimited custom
Fields
category, numeric and timestamp fields, as described in Section 2.2.
Accordingly, it is recommended that ANY desirable classifying,
numeric or timestamp information be appended to the response file.
The example below shows part of a sample CSV unit response file with all required fields and
several suggested/optional fields. Note that the "Acknowledged" field is assumed to be a
custom field previously defined and mapped in Code3 Strategist, as described in the Code3
Strategist User Manual Section 4.4.1.1. If the field is not defined and mapped, it will be ignored
during the import process.
UniqueId,UnitId,UnitType,NumStaff,Dispatched,OnScene,FromQtrs,Urgency,Acknowledged
HELPING BUILD ORGANIZATIO�INNAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEV;;2UM
DATA T E C H NO LOG I E S
www.levrum.com
XFD201408220412,M 123,als,2,"08-22-2014 14:28:42","08-22-2014 14:34:11 ",FALSE,3,"08-
22-2014 14:28:55" XFD201408220419,E131,eng,4,"08-22-2014,14:58:11","08-22-2014
15:02:22",FALSE,3,"08-22-2014 14:59:31"
XFD201408220419,C 117,cmd,1,"08-22-2014,14:58:11 ","08-22-2014 15:03:30",FALSE,3,"08-
22-2014 14:59:05"
3 Cause/Nature Code Import
Incident "nature codes" are codes specifying the types of incidents to which your organization
responds. Typically, your CAD or RMS system provides these codes, and you have little
control over them. Grouping nature codes into cause categories (which you do control) allows
you to organize your incidents in a logical fashion and enables you to model operational policies
accurately and analyze statistics according to how your organization actually operates.
Code3 Strategist enables you to import the cause/nature classification scheme from a CSV file
that adheres to the guidelines laid out in Section 1.3. The fields in such fields have the
semantics shown in the following table.
Field
Name
Required?
Description
NatureCode
Yes
Incident nature code. This is typically a brief
(see notes
mnemonic code provided by your CAD or RMS
below)
system. This field is a character string with no
maximum length, but it is recommended to keep values
to 10 or fewer characters to ensure readability in Code3
Strategist charts, data grids, maps and reports.
Description
Optional
Optional free text describing the nature code.
CauseCategory
Yes
A code or brief caption for the category to which the
incident belongs. If you choose not to categorize your
incidents, supply a single value for this field in all rows
of data — e.g., "All".
CategoryDescription
Suggested
This field describes the cause category. Its value should
be the same for all records with the same CauseCategory.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
L_E V U
DATA TECH NOLOGI ES
www.levrum.com
ParentCause Optional This optional field enables you to establish a hierarchy of
cause categories. The value of this field, if supplied,
should specify the CauseCategory that contains the
current CauseCategory. For example, you might import
a CauseCategory of "car fire" with a ParentCause of
"Fire". Top-level categories should leave this field
You may use this import feature to build arbitrarily deep cause hierarchies, and you may include
cause categories without any nature codes in order to do so. The following example builds the
following simple cause hierarchy (with nature codes shown in all caps following the category
names; category descriptions are omitted for brevity):
Cause Tree Cause: 'Fkmddfertial'Assig
B.- Any Incident APART: Apartment Fire
.... EMS HOUSE: House Fire
B.- Nre
NatureCode,Description, CauseCategory,CategoryDescription,ParentCause
„Any Incident„
„Fire„Any Incident
HOUSE,House Fire,Residential„Fire
APART,Apartment Fire,Residential„Fire
„EMS„Any Incident
If you are accustomed to normalized database schemas, this arrangement may seem counter-
intuitive: the parent cause relationship is repeated once for each nature code belonging to the
child cause ("Fire" is shown as the parent of "Residential" for both HOUSE and APART nature
codes in the example above).
4 Geospatial Projection Format
Code3 Strategist uses a standard set of "coordinate transformations" (mathematical functions that
convert latitude and longitude to and from rectangular distance coordinates such as feet, meters
or miles) internally to compute distances and render information on maps.
In order to display your incident information correctly, prior to the initial installation of Code3
Strategist, you must supply us with the projection transform that describes the coordinate system
for the X/Y locations of incidents to be used by Code3 Strategist.
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential
LEv;2UM
DATA T EC H NO LOG I E S
www.levrum.com
You must supply enough information to uniquely identify the projection appropriate for your
jurisdiction. (If you have questions, please ask us during the preparation phase prior to your
training and installation. We have considerable experience in identifying and validating
projection transforms). You may either supply a unique projection name, as defined by
www.spatialreference.org. or supply the projection transform in the "Well-known Text" format
as specified by www.spatialreference.om..
For example, a common projection for the northern portion of Oregon is identified by
www.spatialreference.or6, as follows:
Projection name: "EPSG:2913 NAD83(HARN) / Oregon North (ft)"
Projection transform (well-known text format):
PROJCS["NAD83(14ARN) / Oregon North",
GEO GC S ["NAD 8 3 (HARN)",
DATUM [ "NAD 83_High_Accuracy_Regional_Network",
SPHEROID["GRS 1980",6378137,298.257222101,
AUTHORITY[ "EPSG", "7019"] ],
AUTHORITY ["EPSG","6152"] ],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901 "]],
UNIT["degree",0.01745329251994328,
AUTHORITY ["EPSG","9122"] ],
AUTHORITY["EPSG","4152"]],
UNIT[ "metre", 1,
AUTHORITY["EPSG","9001 "]],
PROJECTION ["Lambert_ Conformal_ Conic_2 SP"],
PARAMETER["standard_parallel_1 ",46],
PARAMETER["standard_parallel_2",44.33333333333334],
PARAMETER[" latitude —of _origin ",43.66666666666666],
PARAMETER["central_meridian",-120.5],
PARAMETER["false_easting",2500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","2838"],
AXIS ["X ",EAST],
AXIS ["Y",NORTH]]
HELPING BUILD ORGANIZATIONAL RESILIENCE
info@Levrum.com 1 (541) 714-5882 1 408 SW Monroe Ave. Corvallis, OR 97333
Proprietary and Confidential