System requirements

Server Operating Systems

• MS Windows Server 2008 (all variants)
• MS Windows Server 2012 (all variants)
• MS Windows Server 2016 (all variants)

SQL Servers

Crash Magic requires two types of database connections:

1. System connection – For managing Crash Magic application state
   System tables are used by the program to store system state, user settings, configuration, etc.
   The program requires SELECT, UPDATE, DELETE access to these tables. If the program is to create the tables, it will also need CREATE TABLE access. (optionally the program can provide the SQL statements required to create the tables and a system administrator can execute the commands)
2. Crash Data connection – Access to crash data to be analyzed and reported on
   Crash, roadway and other safety releated data.
   These tables may be accessed in read-only mode, with only SELECT access.
   Or, these tables may be maintained by Crash Magic, allowing data entry and importing.  In this case, the program will require SELECT, UPDATE, DELETE access.

Logins, security and connection pooling:

• Crash Magic performs connection pooling for it’s system tables. In general, each user action utilizes a system connection for the moment the action is occurring. Users do not maintain system table connections across requests.
• Connections to crash data may be made on a per-user login basis, or with all users sharing the same login. In both cases a connection is created, used and destroyed during the processing of each report. When a per-user login is specified for the crash data connection, each user’s login and password is used by Crash Magic when connecting. When a single login is specified, that login and password is used for every user.
• Each user of the Crash Magic system must have an account in Crash Magic. That account specifies a login name and password.
  In order to avoid the task of maintaining passwords in multiple systems, Crash Magic can store only a login, and “pass-thru” the password from login to the SQL server. This login can also be used to validate users into Crash Magic.
  MS Active Directory Services may also be used to authenticate a user and provide access to their Crash Magic account.

This system has been developed and tested around the following systems, and all of them function properly:

• Microsoft SQL Server 2008R2
• Microsoft SQL Server 2012
• Microsoft SQL Server 2014
• Microsoft SQL Server 2016
• Oracle 9i (tested on Unix, Windows)
• Oracle 10g (tested on Linux, Unix, Windows)
• Oracle 11g (tested on Linux, Unix, Windows)
• Oracle 12c (tests pending)
• IBM DB2 10, 11 Linux, Windows
• MS Access – generally just used for testing (not supported for production environment)

GIS components

Crash Magic has several optional pieces of functionality that utilize ESRI components. At this time, ArcGIS Server with REST services exposed is required to be provided by the client.  ArcGIS Online is not yet supported:

Inline pin maps

• Crash Magic has built-in pin maps that utilize the public ArcGISOnline maps OR
• Clients may provide REST access to their ArcGIS server. This allows for use of custom layers such as construction, volume data, bicycle lanes, etc.
• This feature requires one or more Map Services exposed by the ArcGIS Server

Map Magic

• Map Magic is an ArcMap v10.x desktop add-in that provides access to Crash Magic
• REST is used to communicate with Crash Magic
• This feature requires ArcMap v10.3 or newer and a suitable base map. In addition, a crash layer is helpful

GIS-based collision diagrams

• In addition to the static collision diagrams that Crash Magic is known for, a new feature enables the program to produce “dynamic collision diagrams” based on the road alignments reported by ArcGIS Server
• REST is used to communicate with ArcGIS from the Crash Magic servers.
• This feature requires a Street Centerline Map Service and a Gecoding service exposed by an ArcGIS Server.

Geocoding service

• Pd’ Programming has a geocoding service that uses intersection street names plus distance and direction from the nearest intersection.
• This feature requires a Street Centerline Map Service and a Gecoding service exposed on an ArcGIS Server.

Hardware

• Intel-based Server or Virtual Machine with at least 1 server class processor, 2 preferred.
• 500 Megabytes available RAM required, 1 Gigabyte or more recommended.
• 5 Gigabytes of application hard disk space.
• 2 Gigabytes of hard disk space available for processing. This will vary depending on number of concurrent users and reports in use.

Networking

• Application Server to Client Bandwidth – minimum recommended 2Mbs. (i.e. DSL, Cable, 100Mb/1Gb/10Gb/100Gb)
• Application Server to Database Server Bandwidth – minimum recommended 100mb/s. 1Gb/s or faster preferred. This connection is critical and generally determines overall application performance
• HTTP/HTTPS protocol to browsers
• Single IP address – user defined
• Single port – user defined
• Connection to internet required for mapping and some diagramming functionality.  (esri.com / ArcMap.com and GovernmentTools.com)

Client software

Crash Magic generally supports the most current version of all modern browsers:
Note: Development and testing are performed on Firefox and Chrome.  Other browsers are tested prior to release.

• Microsoft Internet Explorer 11
• Firefox
• Chrome
• Safari
• MS Edge
• A PDF Reader is also required, but is built in to many browsers.

Deliverables

Software provided for installation

• Product installer
• Crash Magic executables (Service and ISAPI provided)
• Crash Magic IIS prep utility (Sets up users, groups, sites, virtual directories and permissions in IIS)
• Configuration – XML file for program import*

Items not provided except by contract

• Computer hardware
• Networking hardware or software
• Operating systems
• SQL server software (see above for options)
• Database Drivers

*Configuration files are generally purchased from Pd’ Programming, but may be prepared by client if desired