Attachment A Software Specifications Sheet.XLSX

XLSX spreadsheet 32 KB Posted

Attached to
Police Professional Standards Software
Solicitation number
RFP-RFP20260259-0-2026/BG
Issued by
James City County, Virginia

About this file

The document is a Software Specifications Sheet for Police Professional Standards Software, specifically for James City County, Virginia. The comprehensive software specification details requirements for a professional standards management system for law enforcement, covering multiple critical reporting and tracking functions across various incident types including complaints, use of force, internal affairs, K9 incidents, foot pursuits, vehicle pursuits, and animal euthanasia. The software must provide extensive capabilities such as spell checking, unlimited narrative entry, email/text notifications, comprehensive employee reporting, audit trails, data protection, mobile app functionality, statistical reporting, workflow customization, and integration with other data sources.

The specification includes over 200 specific technical and functional requirements, with a strong emphasis on data security, customizable workflows, comprehensive reporting capabilities, and detailed incident documentation. The system must support features like single sign-on, dual-factor authentication, API calls, data encryption in transit and at rest, and the ability to create custom reports. The software is expected to meet professional standards compliance requirements, including CALEA standards, and provide robust tracking and intervention capabilities for law enforcement administrative processes. The specification suggests the county is seeking a comprehensive, flexible, and secure software solution to manage professional standards and administrative reviews within their police department.

View the file

Other files

File Type Posted
Police Professional Standards Software.PDF PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Police Professional Stanards

Item #Department / County AreaSectionRequirementsHave it?Included in Base ProposalComments
1PoliceAll sectionsThe software will provide a spell checker as a standard feature in areas where a narrative may be entered
2PoliceAll sectionsThe software will provide the ability to enter unlimited narrative with text wrap-around feature in the narrative field.
3PoliceAll sectionsSoftware sends an email and/or text notification to next employee in the review chain the assignment is submitted to
4PoliceAll sectionsGenerate an overview report regarding an individual employee (Comprehensive history of all professional standards data/events/investigations involving the employee from the professional standards software
5PoliceAll sectionsTrack and audit all activity by users (what was accessed /viewed/amended, when and who did it)
6PoliceAll sectionsLinks, PDFs, etc be placed in each "task"/investigation, complaint, force report, etc. (able to click on a link, able to import or export data from other systems
7PoliceAll sectionsAdditional information fields available that are user definable
8PoliceAll sectionsHighly customizable statistical reports (annual, monthly, quarterly, on off, etc) displaying combinations and comparisons of entered data (1. How many uses of force involving a firearm pointed at a subject in last six months, 2. Over the past year how many foot pursuits involved a suspect who was a minor, etc.)
9PoliceAll sectionsMap plotting for incident location
10PoliceAll sectionsTrack the current stautus of all complaints, use of force investigations, internal affairs investigations, etc. by agency individuals given specific access (ie. Chief of Police, Internal Affiars Coordinator, etc.)
11PoliceAll sectionsPermanent audit trail for all information recorded related to an event, whether or not that information is later modified or deleted
12PoliceAll sectionsProtect data/info from viewing by employees not in the agencies' identified chain of review/approval.Examples, only direct supervisors of the officer in question should see the data, or only certain people can see information and only certain types of information.
13PoliceAll sectionsAble to upload/attach PDFs, videos, links, excel and other types of files to individual complaints, use of force incidents,etc. Ability to overwrite a file and track all files added no matter if they get "Deleted" or changed.
14PoliceAll sectionsAble to link with other data sorces (ex. event numbers in CAD, IBRs in RMS, TASER CEW use data)
15PoliceAll sectionsSoftware sends an email and text to the agency identified professional standards administrator(s) notifying that a report/action that was submitted to someone has not been looked at yet.
16PoliceAll sectionsStatistical data reports (annual, monthly, quarterly, on off, etc) displaying combinations and comparisons of entered data able to also show data in chart and graph formats.
17PoliceAll sectionsSoftware has mobile app in addition to the computer (PC) based interface
18PoliceAll sectionsVariety of built in data/statistical reports with easy report generation and ability to export to other products such as excel and PDF
19PoliceAll sectionsSoftware system is secure
20PoliceAll sectionsAll individual workflows (chain of review/approval) are set by agency and changeable by agency
21PoliceAll sectionsAll individual workflows (chain of review/approval) are changeable by position as well as employee
22PoliceAll sectionsAll correspondence from system s auditable, tracked, and saved in the system
23PoliceAll sectionsEmployee namebank must include county applied employee ID number and (if badge number is given to an employee) employee badge number
24PoliceAll sectionsDates are selected from calendar
25PoliceAll sectionsMaster search by name that lists al the differenttimes a particular name has been entered into the system (employees, witnesses, complainants, suspects, etc.)
26PoliceAnimal EuthanizationAnimal euthanasia incident report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
27PoliceAnimal EuthanizationAnimal euthanasia incident report records date (dated selected by calendar) the original incident report was filled out
28PoliceAnimal EuthanizationAnimal euthanasia incident report records the agency generated event number for the incident
29PoliceAnimal EuthanizationAnimal euthanasia incident report records the submitting officer name and badge number
30PoliceAnimal EuthanizationAnimal euthanasia incident report records incident date (dated selected by calendar) and time
31PoliceAnimal EuthanizationAnimal euthanasia incident report records the animal type by drop down (drop down menu additions made at agency level)
32PoliceAnimal EuthanizationAnimal euthanasia incident report records the type of weapon used
33PoliceAnimal EuthanizationIf a firearm was used, Animal euthanasia incident report records the type of firearm and how many rounds were fired
34PoliceAnimal EuthanizationAnimal euthanasia incident report records reason for the euthanization pursuit with free text narrative
35PoliceAnimal EuthanizationAnimal euthanasia incident report records the agency established chain of command review work flow
36PoliceAnimal EuthanizationAnimal euthanasia incident report records whether the pursuit was in compliance with agency policy
37PoliceAnimal EuthanizationAnimal euthanasia incident report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
38PoliceAnimal EuthanizationAnimal euthanasia incident report records whether or not the incident was recorded on video/audio
39PoliceComplaintsComplaint on agency employee report records whether the finished investigation determined each allegation was either sustained, not sustained, unfounded, exonerated, not involved, policy review/policy failure
40PoliceComplaintsComplaint on agency employee report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
41PoliceComplaintsComplaint on agency employee report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
42PoliceComplaintsComplaint on agency employee report records date the complaint report was filled out
43PoliceComplaintsComplaint on agency employee report records the agency generated event number or IBR number associated with the original incident regarding the complaint
44PoliceComplaintsComplaint on agency employee report records the name of the agency employee assigned to investigate the complaint
45PoliceComplaintsComplaint on agency employee report records the date and time of the original incident regarding the complaint
46PoliceComplaintsComplaint on agency employee report records a list of specific allegations and the employee(s) that each specific allegation is involving
47PoliceComplaintsComplaint on agency employee report records separate "final dispositions" for each allegation and each related employee
48PoliceComplaintsComplaint on agency employee report records any corrective actions taken as a result of the investigation findings
49PoliceComplaintsComplaint on agency employee report records any involved persons or witnesses to the original incident regarding the complaint
50PoliceComplaintsComplaint on agency employee report records any involved persons or witnesses names and contact information
51PoliceCompliantsComplaint on agency employee report records the date and time the complaint was received
52PoliceCompliantsComplaint on agency employee report records date the complaint report was filled out
53PoliceCompliantsComplaint on agency employee report records complainant name
54PoliceCompliantsComplaint on agency employee report records complainant age
55PoliceCompliantsComplaint on agency employee report records complainant sex
56PoliceCompliantsComplaint on agency employee report records complainant race
57PoliceCompliantsComplaint on agency employee report records complainant last four # of social security
58PoliceCompliantsComplaint on agency employee report records complainant date of birth
59PoliceCompliantsComplaint on agency employee report records Complainant residencial address
60PoliceCompliantsComplaint on agency employee report records Complainant contact phone number(s) and email
61PoliceCompliantsComplaint on agency employee report records Name and badge number of each officer complaint is being made on
62PoliceCompliantsComplaint on agency employee report records the details of the complaint as given by the complainant with free text narrative
63PoliceCompliantsComplaint on agency employee report records date of original incident regarding the complaint
64PoliceCompliantsComplaint on agency employee report records location of original incident regarding the complaint
65PoliceCompliantsComplaint on agency employee report records how compliant was received (by email, in person, social media, by mail, phone, other (with "other" able to type in free text field for better descripition) )
66PoliceCompliantsComplaint on agency employee report records location where complaint was received
67PoliceCompliantsComplaint on agency employee report records the date, time, and reason each contact is made with the complainant during the investigation
68PoliceCompliantsComplaint on agency employee report records the date, time, and method (ex. by phone, in person, email, letter mailed,etc) contact is made with the complainant notifying complainant of investigation final determiniation
69PoliceCompliantsComplaint on agency employee report records name and badge # of employee submitting the complaint report to the agency identified work flow (chain of commmand review) and the date of the submittal
70PoliceCompliantsComplaint on agency employee report follows an agency established chain of review
71PoliceCompliantsComplaint on agency employee report records the agency generated event number for the complaint
72PoliceEarly Intervention SystemSoftware must have an "early warning system" / "early intervention system" that satisfies CALEA related standard(s)
73PoliceEarly Warning SystemEarly warning/intervention system (EIS/EWS) must have the ability to cancel "alert" notification after the alert has been addressed
74PoliceFoot pursuitFoot pursuit incident report has field to record date of incident
75PoliceFoot pursuitFoot pursuit incident report records date the original incident report was filled out
76PoliceFoot pursuitFoot pursuit incident report records Suspect name
77PoliceFoot pursuitFoot pursuit incident report records Suspect age
78PoliceFoot pursuitFoot pursuit incident report records Suspect sex
79PoliceFoot pursuitFoot pursuit incident report records Suspect race
80PoliceFoot pursuitFoot pursuit incident report records Suspect last four # of social security
81PoliceFoot pursuitFoot pursuit incident report records Suspect date of birth
82PoliceFoot pursuitFoot pursuit incident report records Suspect height
83PoliceFoot pursuitFoot pursuit incident report records Suspect weight
84PoliceFoot pursuitFoot pursuit incident report records Name and badge number of each officer involved
85PoliceFoot pursuitFoot pursuit incident report records reason for the pursuit with free text narrative
86PoliceFoot pursuitFoot pursuit incident report records whether or not Suspect was apprehended
87PoliceFoot pursuitFoot pursuit incident report records location of foot pursuit
88PoliceFoot pursuitFoot pursuit incident report records additional charges resulting from incident
89PoliceFoot pursuitFoot pursuit incident report records whether or not any injuries were sustained as a result of the foot pursuit.
90PoliceFoot pursuitIf any injuries were sustained by any involved party (suspect, officers, others) of the foot pursuit, foot pursuit incident report records persons' names and injuries described for each person and what medical treatment was applied
91PoliceFoot pursuitFoot pursuit incident report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
92PoliceFoot pursuitFoot pursuit incident report follows an agency established chain of review
93PoliceFoot pursuitFoot pursuit incident report records the agency generated event number for the incident
94PoliceInternal AffairsInternal affairs investigation report records whether the finished investigation determined each allegation was either sustained, not sustained, unfounded, exonerated, not involved, policy review/policy failure
95PoliceInternal AffairsInternal affairs investigation report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
96PoliceInternal AffairsInternal affairs investigation report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
97PoliceInternal AffairsInternal affairs investigation report records date the interanl affairs case was begun
98PoliceInternal AffairsInternal affairs investigation report records the agency generated event number or IBR number associated with the original incident regarding the complaint
99PoliceInternal AffairsInternal affairs investigation report records the name of the agency employee assigned to investigate the complaint
100PoliceInternal AffairsInternal affairs investigation report records the date and time of the original incident regarding the complaint
101PoliceInternal AffairsInternal affairs investigation report records a list of specific allegations and the employee(s) that each specific allegation is involving
102PoliceInternal AffairsInternal affairs investigation report records separate "final dispositions" for each allegation and each related employee
103PoliceInternal AffairsInternal affairs investigation report records any corrective actions taken as a result of the investigation findings
104PoliceInternal AffairsInternal affairs investigation report records any involved persons or witnesses to the original incident regarding the IA investigation
105PoliceInternal AffairsInternal affairs investigation report records any involved persons or witnesses names and contact information
106PoliceInternal AffairsInternal affairs investigation report records the date and time the complaint was received
107PoliceInternal AffairsInternal affairs investigation report records complainant name
108PoliceInternal AffairsInternal affairs investigation report records complainant age
109PoliceInternal AffairsInternal affairs investigation report records complainant sex
110PoliceInternal AffairsInternal affairs investigation report records complainant race
111PoliceInternal AffairsInternal affairs investigation report records complainant last four # of social security
112PoliceInternal AffairsInternal affairs investigation report records complainant date of birth
113PoliceInternal AffairsInternal affairs investigation report records Complainant residencial address
114PoliceInternal AffairsInternal affairs investigation report records Complainant contact phone number(s) and email
115PoliceInternal AffairsInternal affairs investigation report records Name and badge number of each officer complaint is being made on
116PoliceInternal AffairsInternal affairs investigation report records the details of the complaint as given by the complainant with free text narrative
117PoliceInternal AffairsInternal affairs investigation report records date of original incident regarding the complaint
118PoliceInternal AffairsInternal affairs investigation report records location of original incident regarding the complaint
119PoliceInternal AffairsInternal affairs investigation report records how compliant was received (by email, in person, social media, by mail, phone, other (with "other" able to type in free text field for better descripition) )
120PoliceInternal AffairsInternal affairs investigation report records location where complaint was received
121PoliceInternal AffairsInternal affairs investigation report records the date, time, and reason each contact is made with the complainant during the investigation
122PoliceInternal AffairsInternal affairs investigation report records the date, time, and written method (ex.email, letter mailed,etc) contact is made with the complainant notifying complainant of investigation final determiniation
123PoliceInternal AffairsInternal affairs investigation report records name and badge # of employee submitting the complaint report to the agency identified work flow (chain of commmand review) and the date of the submittal
124PoliceInternal AffairsInternal affairs investigation report follows an agency established chain of review
125PoliceInternal AffairsInternal affairs investigation report records the agency generated event number for the complaint
126PoliceK9Incident report records date the original incident report was filled out
127PoliceK9Incident report records Suspect name
128PoliceK9Incident report records Suspect age
129PoliceK9Incident report records Suspect sex
130PoliceK9Incident report records Suspect race
131PoliceK9Incident report records Suspect last four # of social security
132PoliceK9Incident report records Suspect date of birth
133PoliceK9Incident report records Suspect height
134PoliceK9Incident report records Suspect weight
135PoliceK9Incident report records Name and badge number of each officer involved
136PoliceK9Incident report records primary officer narrative/statement describing the reason(s) for the use of K9 with free text narrative
137PoliceK9Incident report records location of incident
138PoliceK9If any injuries were sustained by any involved party (suspect, officers, others) of the use of K9, incident report records location(s) on the body fo each injury and type of injury to include a body diagram (front and rear view) for each person injured (suspect, officer(s), others)
139PoliceK9Incident report records whether or not any injuries were sustained as a result of the use of K9
140PoliceK9If any injuries were sustained by any involved party (suspect, officers, others) of the use of K9, incident report records persons' names and injuries described for each person and what medical treatment was applied
141PoliceK9Incident report records name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
142PoliceK9Incident report follows an agency established chain of review
143PoliceK9Incident report records the agency generated event number for the incident
144PoliceK9Incident report records whether the K9 use was in compliance with agency policy
145PoliceK9Incident report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
146PoliceK9Incident report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
147PoliceK9Incident report records date the original incident report was filled out
148PoliceK9Incident report records incident date and time
149PoliceK9Incident report records photos were taken related to the incident
150PoliceK9Incident report records type of suspect resistance (verbal reisitance, verbal threat to harm, passive resistance, defensive resistance, empty hand aggression towards officers/others, Officer(s) believed suspect was armed with a weapon, etc)
151PoliceK9Incident report records each involved officer's narrative/statement describing the reason(s) for the use of force with free text narrative
152PoliceK9Incident report records any other incident involved persons or witnesses to the force incident
153PoliceK9Incident report records name, date of birth, age, and contact information any other incident involved persons or witnesses to the force incident
154PoliceK9Incident report records what type of device(s) the video/audio was recorded on (in car camera, body worn camera, etc)
155PoliceK9Incident report records whether or not the incident was recorded on video/audio
156PoliceK9Incident report records name and badge number of canine(s) involved
157PoliceUse of ForceUse of force incident report records date the original incident report was filled out
158PoliceUse of ForceUse of force incident report records Suspect name
159PoliceUse of ForceUse of force incident report records Suspect age
160PoliceUse of ForceUse of force incident report records Suspect sex
161PoliceUse of ForceUse of force incident report records Suspect race
162PoliceUse of ForceUse of force incident report records Suspect last four # of social security
163PoliceUse of ForceUse of force incident report records Suspect date of birth
164PoliceUse of ForceUse of force incident report records Suspect height
165PoliceUse of ForceUse of force incident report records Suspect weight
166PoliceUse of ForceUse of force incident report records Name and badge number of each officer involved
167PoliceUse of ForceUse of force incident report records primary officer narrative/statement describing the reason(s) for the use of force with free text narrative
168PoliceUse of ForceUse of force incident report records location of incident
169PoliceUse of forceUse of force incident report records additional charges resulting from susbject resistance
170PoliceUse of forceIf any injuries were sustained by any involved party (suspect, officers, others) of the use of force, use of force incident report records location(s) on the body fo each injury and type of injury to include a body diagram (front and rear view) for each person injured (suspect, officer(s), others)
171PoliceUse of forceUse of force incident report records whether or not any injuries were sustained as a result of the use of force
172PoliceUse of forceIf any injuries were sustained by any involved party (suspect, officers, others) of the use of force, use of force incident report records persons' names and injuries described for each person and what medical treatment was applied
173PoliceUse of forceUse of force incident report records name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
174PoliceUse of forceUse of force incident report follows an agency established chain of review
175PoliceUse of forceUse of force incident report records the agency generated event number for the incident
176PoliceUse of ForceUse of force incident report records whether the force used was in compliance with agency policy
177PoliceUse of ForceUse of force incident report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
178PoliceUse of ForceUse of force incident report records Name and badge # of employee submitting the report to the agency identified work flow (chain of commmand review) and the date of the submittal
179PoliceUse of ForceUse of force incident report records date the original incident report was filled out
180PoliceUse of ForceUse of force incident report records whether the incident involved a show of force (such as officer(s) pointing a firearm or CEW at suspect) or a use of force (hands on, takedown, CEW shock administered, OC spray deployed, etc.) OR both
181PoliceUse of ForceUse of force incident report records incident date and time
182PoliceUse of ForceUse of force incident report records photos were taken related to the incident
183PoliceUse of ForceUse of force incident report records type of suspect resistance (verbal reisitance, verbal threat to harm, passive resistance, defensive resistance, empty hand aggressin towards officers/others, Officer(s) believed suspect was armed with a weapon, etc)
184PoliceUse of ForceUse of force incident report records whether or not suspect was belived to be under the influence of alcohol, drugs, cognitive condition, etc)
185PoliceUse of ForceUse of force incident report records the types of force applied and/or attempted by officers
186PoliceUse of ForceUse of force incident report records each involved officer's narrative/statement describing the reason(s) for the use of force with free text narrative
187PoliceUse of ForceUse of force incident report records any other incident involved persons or witnesses to the force incident
188PoliceUse of ForceUse of force incident report records name, date of birth, age, and contact information any other incident involved persons or witnesses to the force incident
189PoliceUse of ForceUse of force incident report records what type of device(s) the video/audio was recorded on (in car camera, body worn camera, etc)
190PoliceUse of ForceUse of force incident report records whether or not the incident was recorded on video/audio
191PoliceVehicle PursuitVehicle pursuit incident report records the agency generated
192PoliceVehicle PursuitVehicle pursuit incident report records the agency generated event/IBR report number for the incident
193PoliceVehicle PursuitVehicle pursuit incident report records the agency established chain of command review work flow
194PoliceVehicle PursuitVehicle pursuit incident report records whether the pursuit was in compliance with agency policy
195PoliceVehicle PursuitVehicle pursuit incident report records an "explaination" section for free text comment/analysis for each level of the agency established chain of command review
196ITGeneralDo you offer Single Sign On (Microsoft Tenant)
197ITGeneralDo you support Dual Factor Authentication (Preferable with DUO)
198ITGeneralDo you allow for API calls
199ITGeneralIs the data encrypted in rest
200ITGeneralIs the data encrypted in transit
201ITGeneralDoes the system allow for SSRS (Reporting Services reports) to be created by Users

Definitions

DEFINITIONS

Word / Phrase / AcroynmDefinition
RESOURCE / UNIT MANAGEMENTOne of the fundamental and critical components of a CAD system is the ability to assign and track resources. Resources include not only the traditional responders—law enforcement, fire, and EMS—but may also include units like animal control, tow trucks, and utility services. Tracking of these resources is critical for the dispatcher to know what units are available to send to a particular CFS and what their status is at any given time.
CAD SYSTEM ADMINISTRATIONSystem administration is a core function of a CAD system. The various administrative functions and capabilities described below are required to keep the CAD system current and operational. Some of these administrative functions and capabilities should be completed on a daily or weekly basis; others are completed according to a predefined schedule; while others are only completed on an as needed basis. Since these CAD administrative functions and capabilities are frequently used by non-technical personnel, they should be implemented in the CAD system with an ergonomically structured GUI14 so they can be easily accomplished.
CALL / INCIDENT / EVENT MANAGEMENTThe incident is managed by continually updating the CFS event with any additional information reported by callers or officers on scene. The resource recommendations may be revised based on additional information and may be added to or reassigned
CALL HANDLING / CAD EVENT CREATIONThe CAD handling and event creation process consists of the PSAP being notified through a variety of sources of the need for assistance: Receiving a telephone call, electronic notification, radio request;

Obtaining sufficient and accurate information from a reporting party or electronic device to determine the location and event classification;

Determining if the incident being reported is a duplicate of an incident in progress; and, Creating or updating the CFS in the CAD system.

DISPATCH SUPPORTThe dispatcher is responsible for using the CAD system in multiple ways to manage an incident. This section of the document will cover some of the most common and important features for a CAD system to assist the dispatcher in the dispatch decision and incident management process.
E9-1-1 INTERFACEAn interface that imports subscriber information (ANI and ALI) for each E9-1-1 caller, as provided by the telephone company, into CAD-compliant entry process, eliminating the need for redundant data entry. If GIS data (latitude/longitude) is provided by the telephone provider, then the E9-1-1 data can be simultaneously imported into the mapping system for immediate centering and display.
EMERGENCY SERVICES NUMBER (ESN)An ESN is a three to five digit number representing a unique combination of emergency service agencies (Law Enforcement, Fire, and Emergency Medical Service) designated to serve a specific range of addresses within a particular geographical area, or Emergency Service Zone (ESZ). The ESN facilitates selective routing and selective transfer, if required, to the appropriate PSAP and the dispatching of the proper service agency (ies).
EXTERNAL DATABASE INTERFACEQuery to state, local and national databases. Queries to the state, local, RMS, and national databases will automatically occur from selected CAD commands using the messaging system interface. In addition, the operator (i.e. dispatcher or officer) will have the ability to use stand-alone query windows, eliminating redundant data entry. Responses to such queries should be stored with the incident record
GUIGraphical User Interface
INCIDENT DISPOSITIONIncident disposition addresses those CAD system activities related to the closing of an incident including: assigning case numbers, entering an incident disposition, and transferring the call data to one or more RMS.
INTERFACESAn interface is the means by which the CAD system communicates information with other systems within the PSAP, such as E9-1-1 systems, or with external systems, such as federal databases, fire toning systems, or emergency operations centers (EOC). Typically, interfaces serve to provide CAD operators or first responders with a greater degree of information to increase situational awareness and officer safety through the addition of messaging or alerting capability that is not inherent to the CAD application itself.
MESSAGING SUBSYSTEM INTERFACEProvides the ability to communicate with external messaging subsystems. This is one of the most important interfaces in terms of situational awareness and officer safety. Common examples include SMTP (email protocol), SMS (paging and text), and other TCP/IP-enabled technologies. Also common are interfaces to alerting modules, such as systems utilizing the existing radio network or an IP- enabled network (WAN/LAN), and text-to-voice technology to read CAD incident data over open intercom systems in fire/EMS stations.
RECORDS MANAGEMENT SYSTEM (RMS) INTERFACEThe RMS will have a robust interface designed to work in conjunction with the CAD application to enable a higher level of information sharing and workflow capabilities. In the absence of such an integrated solution, incident and resource data should be able to be sent to the RMS at configurable points in the incident management process (e.g. initiation, on-scene, clear). Additionally, the interface should be a two-way interface that enables the queries of incident and resource data by operators working in both applications. In addition to incident and resource information, RMS interfaces could include information/data on persons, premise, hydrants, inspection, training, personnel, roster, and/or logistics
REPORTING & MONITORINGReporting and monitoring are important components of a CAD system. Reporting functions should include the ability for the command staff to generate statistical, detail event and log reports, and may include some form of snapshot/incident replay as well. CAD systems should also have the capability to manage the workflow of the call takers and dispatchers to include training and testing functions.
SMTPSimple Mail Transfer Protocol. This paging protocol sends your message as an email, and your cellphone service provider delivers it as a text message.
SNPPSimple Network Paging Protocol, and it is used for sending text messages over the internet to cellphones.
SUPPLEMENTAL RESOURCE REQUEST AND TRACKINGSupplemental resource request and tracking refers to the ability for PSAP personnel to assign external resources, such as a towing company, to an incident whether it is via a vehicle owner’s request for a specific towing company or a towing rotation list. In addition to tow companies, rotational lists have also been used for: utility companies, funeral homes, animal control companies, and persons willing to pick up fresh deer kills (hit by vehicles).
SYSTEM FUNCTIONSFor the purposes of this document, system functions refer to internal functionality. Some of these are seamless to the end user, while some are routine. Regardless, they are all integral parts to a CAD system and provide critical functions and/or capabilities.
TAPTelelocator Alphanumeric Protocol (TAP) is an industry-standard protocol for sending short messages via a land-line modem to a provider of pager and/or SMS services, for onward transmission to pagers and mobile phones
WCTPWireless Communications Transfer Protocol The method used to send messages to wireless devices such as pagers on NPCS (Narrowband PCS) networks.
MCTMobile Computer Terminal
MFRMobile Field Reporting
BWCBody worn camera
IBRIncident Based Reporting (IBR)
CEWConducted energy weapon (TASER) (CEW)
CADComputer aided dispatch
EIS/EWSEarly Intervention System/Early Warning System
IAInternal Affairs

File details come from the government source that posted it. Updated .