RMS Integration
TraCS does not charge for any interface between you and a third party. TraCS is completely FREE and paid for with a grant thanks to the FDOT using federal flow through money from NHTSA.
TraCS does not share your data with third party vendors such as LexisNexis, Carfax, or private RMS vendors. If you would like a third party to ingest TraCS data please use the following steps:
Sample Files and Documentation to RMS Vendor
You can download and provide your RMS vendor with these sample files and documentation. We do not have a schema to provide. The XML files contain:
1. All data elements, blank or not.
2. Images as embedded JPEGs (such as officer signatures)
3. An embedded Base64 PDF of what the report looks like in TraCS
It is between you and the vendor to decide which of this data gets imported.
TraCS dumps the raw data; the parsing is handled by the vendor.
There is a PDF which contains the groups and fields names. The support.mdb can be opened in Microsoft access which contains a pick list for any fields containing a list (table names in the support.mdb are specified on the PDF).
RMS Sample Files and Documentation
Carfax and LexisNexis
We do not have any agreement with these vendors. We will dump the full raw XML data to your agency and it is up to your agency to comply with public records laws. You can do what you wish with your XML data.
Server At Your Agency
1. Identify a server at your agency where we can install a program that can run on a schedule to pull the files down from our SFTP site.
2. Put a ticket in our TraCS Florida Issue Tracker requesting the external IP for that server be white listed on our firewall.
3. After the external IP is whitelisted by TraCS (i.e., the ticket you put in step 2 is closed as resolved), put a ticket in our TraCS Florida Issue Tracker requesting we install SFTPit.exe on that server. In this ticket you will need to specify:
- Which forms you want exported - Do you want the forms exported as XML, PDF, or TIFF - Do you care about the file name or can we use our standard naming convention (example: Crash_25-123456_uniquekey.xml)
RMS Vendor Formats
Axon
Forms
Axon imports the following forms:
- UTC Citations
- Warnings
- Boat Citations
- Boat Warnings
- Parking Citations
- DUI Citations
- Crash
XML file name format:
citation_Form#_FormKey.xml
- CreateBase64
crash_Form#_FormKey.xml
- CreateBase64
- CreateBase64NonMotorist
- CreateBase64Sig4
- CreateBase64Sig4NonMotorist
warning_warningtimelocation.warningformnumber_yyyyMMddhhmmss.xml
- CreateBase64
DUI_Form#_yyyyMMdd.xml
- CreateBase64
BoatingViolation_Form#_FormKey.xml
- CreateBase64Citation
BoatingWarning_Form#_FormKey.xml
- CreateBase64Warning
ParkingCitation_Form#_FormKey.xml CreateBase64Citation
ParkingWarning_Form#_FormKey.xml CreateBase64Warning
- Options: For all forms check:
- Active
- Run Search
- Include CodeText
- IncludeFolderFields
- Images & Report/Attachments: Form all forms:
- Export Images as JPEGS
- Export Reports and PDF
Export Path
All files go to the same export path
Example on a hosted server: C:\ProgramData\TraCS\Communications\Outbox\RMS\RMSXXX
Search Criteria
All forms above should be in Accepted, Submitted, or Mailed status to be exported to RMS.