Crash Magic Online
  Intersection Magic
  Map Magic
  Knowledge Base
  Contact Us

Technical Specifications 

Product information Support Downloads (& demos)

System requirements


Crash Magic is the newest generation of crash records analysis tools from Pd' Programming, Inc.

It follows the successful Intersection Magic crash records analysis software created in 1987, and used by thousands of engineers in city, county and state DOT offices across the country.
This new tool is server based. It runs as a service, connected to an SQL database. Users connect via a web browser on a local intranet or across the Internet.
Note: The system may also be installed as an ISAPI plug in Microsoft IIS.

Server Operating Systems

As a server-based product, Crash Magic has different requirements than our desktop 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 are accessed in read-only mode. Therefore, all that is needed is SELECT 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 occuring. 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.

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

  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • 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 recommended for multi-user environment)

GIS components

Crash Magic has several optional pieces of functionality that utilize ESRI components:

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 available on 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.1 or newer and a suitable base map. In addition, a crash layer is helpful

GIS-based collision diagrams (coming Jan, 2018)

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

Geocoding service (coming Jan 2018)

  • 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 server hosted on ArcGIS Server.


  • Intel-based Server or Virtual Machine with at least 1 Xeon class server processor, 2 preferred.
  • 200 Megabytes available RAM required, 400 Megabytes 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.


  • Application Server to Client Bandwidth - minimum recommended 2Mbs. (i.e. DSL, Cable, 10/100/1G)
  • Application Server to Database Server Bandwidth - minimum recommended 100mb/s. 1Gb/s 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

Client software

Crash Magic currently utilizes HTML 4 for rendering. (requires that it be added to "compatibility mode" sites in IE.
Support for HTML 5 will begin January 2018. At that time, this list will change and is expected to cease support for earlier versions of MS Internet Explorer and simultaneously include support for IE 11, Firefox, Chrome, Safari and Edge.
  • Microsoft Internet Explorer 8, 9, 10, 11
  • Firefox -latest version
  • Unsupported browsers:
    • Chrome
    • Safari
    • MS Edge
  • Acrobat Reader - Required for print output of reports
  • Current Microsoft Silverlight browser plugin - Required of collision diagrams and some charts (not required for HTML5 version)


Software provided for installation

  • Product installer
  • Crash Magic executables (Desktop, Service and ISAPI provided)
  • Crash Magic post-install utility (Windows desktop application)
  • Crash Magic IIS Prep utility (Windows desktop application)
  • Windows-based application utilities for configuration changes, SQL database access, etc. (not required for program use)
  • 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

February 19, 2019 12:08PM

© 1999-2019 Pd' Programming, Inc - Lafayette, CO USA