leitsc law enforcement cad systems
DESCRIPTION
guideTRANSCRIPT
-
Law Enforcement Computer Aided Dispatch (CAD) Systems
Standard Functional Specifications for
Developed by the
Law Enforcement Information Technology Standards Council (LEITSC)
Bureau of Justice AssistanceOffice of Justice Programs U.S. Department of Justice
National Institute of JusticeThe Research, Development, and Evaluation Agency of the U.S. Department of JusticeNIJ
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
LawEnforcementComputerAidedDispatch(CAD)Systems
StandardFunctionalSpecificationsfor
Developedbythe
LawEnforcementInformationTechnologyStandardsCouncil(LEITSC)
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
This document was prepared with the guidance, leadership, and funding of the Bureau of Justice Assistance, Office of Justice Programs, U.S. Department of Justice, in collaboration with the Law Enforcement Information Technology Standards Council. This project was supported by Grant No. 2003-MU-BX-0068, awarded by the Bureau of Justice Assistance.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
LEITSCGovernanceLarry Boyd, ChairmanChiefofPoliceIrving(TX)PoliceDepartmentPoliceExecutiveResearchForum(PERF)
Joe AkersLEITSCStaffLiaisonNationalOrganizationofBlackLawEnforcementExecutives(NOBLE)
Terry ChowanecLEITSCStaffLiaisonPERF
Ted Kamatchus, Vice ChairSheriffMarshallCounty(IA)SheriffsOfficeNationalSheriffsAssociation(NSA)
Mark MarshallChiefofPoliceSmithfield(VA)PoliceDepartmentInternationalAssociationofChiefsofPolice(IACP)
Morris RobersonU.S.PostalService(Retired)NOBLE
Heather RuzbasanLEITSCProjectManager
G. Matthew SnyderLEITSCStaffLiaisonIACP
Fred WilsonLEITSCStaffLiaisonNSA
LEITSCFunctionalStandardsCommitteeJoe CassaBureauCommanderWheatRidge(CO)PoliceDepartment
Mitchell Ray Davis, IIIChiefofPoliceDixmoor(IL)PoliceDepartment
Debbie FoxInformationTechnologyAdministratorLouisville(KY)MetroPoliceDepartment
Michael HaslipChiefofPoliceCityofBlaine(WA)PoliceDepartment
Linda HillConsultantIJISInstitute
J. B. HopkinsDivisionCommander/JailAdministratorStoryCounty(IA)SheriffsOffice
Dina JonesCADManagerStoryCounty(IA)SheriffsOffice
Bruce KellingBaskEnterprises,LLCManagingPrincipal
Daniel MurrayITManagementSectionCommanderArlingtonCounty(VA)PoliceDepartment
Acknowledgements
-
v StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
Beverly MuseTechnologyManagerCityofChattanooga(TN)
Morris RobersonPostalInspector(Retired)U.S.PostalService
Jim SlaterChiefInformationOfficerMassachusettsExecutiveOfficeofPublicSafety
Mark SteigemeierVicePresidentMotorola
Darrell TrueITAdministratorWrentham(MA)PoliceDepartment
Gary VestChiefofPolicePowell(OH)PoliceDepartment
Paul WormeliExecutiveDirectorIJISInstitute
AdvisorsandOtherProgramContacts
William Cade, Jr.Director,911ServicesandCommunicationsOperationsCenter
AssociationofPublicSafetyCommunicationsOfficials
Joe EsteyChiefofPoliceHartford(VT)PoliceDepartmentFormerLEITSCGovernanceMemberIACP
Joe HeapsCommunicationsTechnologyPortfolioManagerNationalInstituteofJusticeOfficeofJusticeProgramsU.S.DepartmentofJustice
Dustin KooncePolicyAdvisorBureauofJusticeAssistanceOfficeofJusticeProgramsU.S.DepartmentofJustice
J. Patrick McCrearyAssociateDeputyDirectorBureauofJusticeAssistanceOfficeofJusticeProgramsU.S.DepartmentofJustice
Harlin McEwenChiefofPolice(Retired)Ithaca(NY)PoliceDepartment
David MulhollandLieutenantU.S.ParkPoliceIACP
Jennifer ZeunikFormerLEITSCProjectManager(20022005)IACP
ProjectManagerHeather RuzbasanLEITSCInternationalAssociationofChiefsofPolice515NorthWashingtonStreetAlexandria,VA22314(703)836-6767,[email protected]
SpecialThankstoOurPartners
www.ijis.org
Thisdocumentistheresultofanextraordinarycollaborationbetweenmanyjusticepractitionersandindustryexperts.Thankyouallforyourcommitment,time,energy,andpatience.
IJIS Institute
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems v
TableofContents
Acknowledgements ............................................................................................................................................................ iii
Table of Contents ................................................................................................................................................................ v
Executive Summary: CAD ............................................................................................................................................... vii
Business Function: Law Enforcement Dispatch ............................................................................................................. 11.1Description:.....................................................................................................................................................................11.2UseCaseDiagram..........................................................................................................................................................11.3UseCaseSpecification:CallTaking...............................................................................................................................11.4UseCaseSpecification:DispatchDecisionSupport......................................................................................................61.5UseCaseSpecification:BOLO......................................................................................................................................71.6UseCaseSpecification:DispatchUnits.........................................................................................................................71.7UseCaseSpecification:UnitStatusManagement.......................................................................................................101.8UseCaseSpecification:CallManagement..................................................................................................................121.9UseCaseSpecification:SupplementalResourcesTracking........................................................................................141.10UseCaseSpecification:CallDisposition....................................................................................................................15
Business Function: CAD System Administration ......................................................................................................... 172.1Description:...................................................................................................................................................................172.2UseCaseDiagram........................................................................................................................................................172.3UseCaseSpecification:GeofileMaintenance.............................................................................................................172.4UseCaseSpecification:Security.................................................................................................................................172.5UseCaseSpecification:Logging..................................................................................................................................182.6UseCaseSpecification:Configuration.........................................................................................................................182.7UseCaseSpecification:TableMaintenance................................................................................................................192.8UseCaseSpecification:CommunicationCenterRelocation........................................................................................192.9UseCaseSpecification:CADCatch-Up.......................................................................................................................19
Business Function: Support Services............................................................................................................................ 213.1Description:...................................................................................................................................................................213.2UseCaseDiagram........................................................................................................................................................213.3UseCaseSpecification:BOLO....................................................................................................................................213.4UseCaseSpecification:EmergencyOperationsCenter..............................................................................................22
Business Function: Call Management and Management Reporting ........................................................................... 234.1Description:...................................................................................................................................................................234.2UseCaseDiagram........................................................................................................................................................234.3UseCaseSpecification:DispatchSupervisorSupport.................................................................................................234.4UseCaseSpecification:CADManagementReporting................................................................................................234.5UseCaseSpecification:TrainingandTesting..............................................................................................................24
-
v StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
Business Function: Interfaces ........................................................................................................................................ 255.1Description:...................................................................................................................................................................255.2UseCaseDiagram........................................................................................................................................................255.3UseCaseSpecification:Primary..................................................................................................................................255.4UseCaseSpecification:AdditionalInterfaces..............................................................................................................255.5UseCaseSpecification:LocationalSystemsInterfaces..............................................................................................275.6UseCaseSpecification:AdministrationInterfaces.......................................................................................................275.7UseCaseSpecification:CommunicationsInterfaces...................................................................................................285.8UseCaseSpecification:PublicAwarenessMessaging................................................................................................285.9UseCaseSpecification:EmergencyOperationsInterface...........................................................................................285.10AdditionalBusinessFunctions.....................................................................................................................................29
Conclusion ......................................................................................................................................................................... 31
Properties: Activity ......................................................................................................................................................... A:1
Properties: Actor ............................................................................................................................................................ A:7
Properties: Business Function ....................................................................................................................................A:11
Properties: State ........................................................................................................................................................... A:13
Properties: Use Case ................................................................................................................................................... A:15
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems v
HistoryTheLawEnforcementInformationTechnologyStandardsCouncil(LEITSC)wascreatedin2002withfunding(GrantNumber2002-LD-BX-0002)fromtheU.S.DepartmentofJustice,BureauofJusticeAssistanceandcontinuedin2003withfunding(GrantNumber2003-MU-BX-0068)throughacollaborativeeffortbetweentheBureauofJusticeAssistanceandtheNationalInstituteofJustice.LEITSCiscurrentlyfundedundertheBureauofJusticeAssistance(GrantNumber2003-MU-BX-0068)andcontinuestoworkincooperationwiththeNationalInstituteofJustice.LEITSCbringstogetherrepresentativesfromtheInternationalAssociationofChiefsofPolice(IACP),NationalSheriffsAssociation(NSA),NationalOrganizationofBlackLawEnforcementExecutives(NOBLE),andPoliceExecutiveResearchForum(PERF)toaddresslawenforcementinformationtechnologystandardsissues.Themissionofthegroupistofosterthegrowthofstrategicplanningandimplementationofintegratedjusticesystemsthroughthedevelopmentandimplementationofinformationtechnologystandards.
PurposeIn2003,LEITSCidentifiedtheneedforanationalstandardforcomputeraideddispatch(CAD)functionalspecifications.Theybelievedthatthestandardwouldaccomplishthefollowinggoals:
ProvideastartingpointforlawenforcementagenciestousewhendevelopingCADrequestsforproposal(RFP);
Leveltheplayingfieldwhenworkingwithvendors;and
Promotesysteminteroperability(forexample,CADtoCAD).
Withthesegoalsinmind,theLEITSCFunctionalStandardsCommittee,composedoflawenforcementpractitionersandindustryexpertsfromaroundthecountry,wasappointedtodeveloptheStandardFunctionalSpecificationsforLawEnforcementCADSystems.Thebaselinedocumentwasdevelopedfromcommonelementsfoundinrequestsforproposals,technicaldocumentation,andotherCAD-relatedresearch.Thedocumentwasthenvalidatedbythegroupusingamodelingtool.Oncedevelopedandvalidated,thespecificationswerevettedthroughthelawenforcementcommunityviaeachoftheparticipatingassociations,aswellasthroughotherstakeholdercommunitiesinanefforttogaininputfromanumberofdifferentperspectives.
NationalInitiatives:LawEnforcementInformationSharingProgram(LEISP),LawEnforcementNationalDataExchange(N-DEx),andLawEnforcementRegionalDataExchange(R-DEx)Aslawenforcementagenciesmovetowardtheprocurementofcomputeraideddispatch(CAD)andlawenforcementrecordsmanagementsystems(RMS),itisvitaltorecognizeandconsidertheLawEnforcementInformationSharingProgram(LEISP)developedbytheU.S.DepartmentofJustice(DOJ).TheLEISPisdesignedtopromoteinformationsharingamongalllevelsofthelawenforcementcommunityandtoguidetheinvestmentofresourcesininformationsystemsthatwillfurtherthisgoal.ThegoalsofLEISParesupportedthroughtheproliferationoftheGlobalJusticeInformationSharingInitiative(Global)ExtensibleMarkupLanguage(XML)DataModel(GlobalJXDM).ForadditionalinformationontheGlobalJXDM,visitwww.it.ojp.gov.TheGlobalJXDMisanXMLstandard
ExecutiveSummary:CAD
-
v StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
designedspecificallyforjusticeinformationexchanges.Itprovideslawenforcement,publicsafetyagencies,prosecutors,publicdefenders,andthejudicialbranchwithatooltoeffectivelysharedataandinformationinatimelymanner.ThereareseveralongoingDOJinitiativesincorporatedintotheLEISP.
OneprogramcurrentlybeingdevelopedjointlybetweentheFederalBureauofInvestigation(FBI)andstateandlocallawenforcementistheLawEnforcementNationalDataExchange(N-DEx)1System.AsecondprogramtheLawEnforcementRegionalDataExchange(R-DEx)2SystemhasbeendevelopedandimplementedbytheFBI.Bothprogramsarenewlawenforcementinformationsharingsystemsbasedupontheabovecriticalstandards.
DocumentScopeThisdocumentpresentsstandardfunctionalspecificationsforlawenforcementCADsystems.Thespecificationsfoundinthisdocumentareintendedtobegenericinnatureratherthanfavoroneparticularsystemorapproachoveranother;theyareatthefunctionallevel,meaningthattheydefinewhatistobeaccomplishedversushowitshouldbeaccomplished.ThesespecificationsweredevelopedtodepicttheminimalamountoffunctionalitythatanewlawenforcementCADsystemshouldcontain.TheyarenotintendedtosimplybesubstitutedforanRFPbutshouldbetailoredtofitthespecificneedsofeachagencyorgroupofagencieslookingtopurchaseaneworupgradeanoldCADsystem.Thesespecificationsshouldbeusedasastartingpointtobuildafullyfunctional(basedonagencyneeds)CADsystemthatisbasedonopenstandardsinordertoefficientlyinterfaceandshareinformationwithothersystemsbothinternallyandexternally.
1 TheN-DExProgramisanincident-andcase-basedinformationsharingsystem(e.g.,RMS)forlocal,state,tribal,andfederallawenforcementagenciesthatsecurelycollectsandprocessescrimedatainsupportoftheinvestigativeandanalyticalprocessandwillprovidelawenforcementagencieswithstrategicandtacticalcapabilitiesthatdonotcurrentlyexistonanationalscale.AnN-DExconceptofoperations(ConOps)documentisbeingfinalizedtoaidinthedesignoftheN-DExsystemandtoensurethatstakeholdersunderstandandsharetheN-DExvision.
2 TheR-DExProjectseekstosecurelysharesensitivebutunclassifiedcrimeinformationbetweenfederalagencies,whileallowingforconnectionwithseveralexistingregionallybasedlocalandstateinformationsharingsystemstoimpedecriminalandterroristactivities.R-DExisnowoperationalinseveralmetropolitanareas.
ItisexpectedthattheprocessofdefiningdetailedinformationexchangesinaCADsystemwillbeaddressedinfuturephasesofthisproject.Inaddition,thesespecificationsareintendedtobeusedinconjunctionwithtechnicalstandards,includingtheGlobalJXDM,inordertostreamlinetheprocessofsharinginformation.
Itisintendedthatthesestandardswillbeupdatedandaugmentedonaregularbasis.
IntroductionCADsystemsallowpublicsafetyoperationsandcommunicationstobeaugmented,assisted,orpartiallycontrolledbyanautomatedsystem.Itcaninclude,amongothercapabilities,computer-controlledemergencyvehicledispatching,vehiclestatus,incidentreporting,andmanagementinformation.
AllaspectsofaCADsystemmustbeoptimizedforrapidresponsetimeandsystemreliability.Sincetimeisoftheessence,theCADsystemmustaccuratelyprovideadataandtimestampforeveryactivity.
CADsystemscollecttheinitialinformationforanincidentandthenprovidetheinformationtooneormoreRMSsystems.
TheCADsystemalsosupportsotheractivitiesthatassistintheeffectiveuseofpublicsafetyresources,includingshiftchangerollcall,Beonthelookout(BOLO)files,andtheabilitytoscheduleacallinthefuture.
Thisdocumentaddressesthefollowingbusinessfunctions:
LawEnforcementDispatch
CADSystemAdministrators
SupportServices
CallManagementandManagementReporting
Interfaces
EMSDispatch
FireDispatch
IntelligentTransportation
Properties
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 1
1.1Description:LawenforcementagenciesuseCADtofacilitateincidentresponseandcommunicationinthefield.CADsystems,inmanycases,arethefirstpointofentryforinformationcomingintothelawenforcementsystem.TypicalCADsystemfunctionsincluderesourcemanagement,calltaking,locationverification,dispatching,unitstatusmanagement,andcalldisposition.Additionally,mappingfunctionality,interfacewithmobiledatacomputers(MDC),andinterfaceswithotherexternallocal,state,andfederalinformationsystemsmaybeincluded.Calltakers,dispatchers,andtheirsupervisorsareprimaryusersofCAD.Unitsinthefieldmayinteractviamobiledatacomputers.
1.2UseCaseDiagram(seepage2)
1.UseCaseSpecification:CallTakingCallsforservice(CFS)initiatetheCADprocess.Callersarecitizensorotheragenciesrequestingservicesfromtheagencyorgivingnotificationofeventsoractivitiesofconcern.ACFSmaycomefrommanydifferentpointsoforigin,suchasalarmsystems,E911systems,directcalls(7-or10-digitnumbers),walk-ins,CAD-to-CADinterfaces,orWeb-basedsystems.
Theservicerequestedbycallerswillconsistofbothemergencyandnonemergencypriorities.Calltaking
3 URLIntegrationcollaboratedwithLEITSCtoassistinthedevelopmentofthefunctionalstandards.URLIntegrationusedanalternativemethodtorequirementsanalysiswiththeirRequirementsModelersoftware.RequirementsModelerisbasedonUnifiedModelingLanguage(UML),whichisthedefactostandardfordocumentingfunctionalrequirements.UMLwascreatedbytheObjectManagementGroup(OMG)in1997asastandardforvisualobject-orientedmodeling.RequirementsModeler,consistentwithUMLprinciples,automaticallygeneratesdiagramsandprocessflow(UseCaseandActivitydiagrams).URLIntegrationsUseCaseandActivitydiagramswerereproducedforuseinthisreport.
LawEnforcementDispatch1 BusinessFunction:consistsofreceivingthecall,obtainingsufficientandaccurateinformationfromthecaller,determiningwhetherthisisaduplicateofacallinprogress,andrecordingorupdatingtheCFSintheCADsystem.Thecalltakermayalsoapplyproceduresandguidelinestoverify,analyze,classify,andprioritizethecallpriortoroutingtheCFStothedispatcher.ACFSmayalsobegeneratedbyaunitinthefield.Theunitcancontactthedispatcherorthecalltaker,orhemayactuallycreatethecallelectronicallyusingtheoptionalmobiledataterminal(MDT)interface.ACFSmaybeforwardedtoatelephonereportingunitandbereceivedfromthetelephonereportingunit.ThismayincludetheabilitytocreateaCFSforfuturescheduledevents.
AssociatedActor
Relationship Description
Caller calls InjurisdictionswithanE911interface,thecalltakerstilltalkstothecaller,butthedatafromtheE911interfacereducescallentrytime.
Unt initiatesAlarm initiates Businessalarmor
otheroptionalinterfaceprovidesdataonly.
ExternalCAD calls AnexternalCADmaycommunicatewithacallcenterinanotherjurisdictionifthosejurisdictionsareunderanagreementtoworktogetherandhaveaCAD-to-CADinterface.
CallTaker receives Insmalleragencies,thecalltakermaybethedispatcher.
-
2 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
BOLO
Dispatch Units
Call Management
Call Disposition
Unit Status Management
Supplemental Resources Tracking
iniatiates alarm
records
transfers
calls
transfer
initiates
calls
maintains
performs
sends
receives
transfer
Call Taking*
records
performs
Dispatch Decision Support
records
dispatched
Telephone Reporting
Unit
AssociatedActor
Relationship Description
ExternalAgency
transfers Thismaybeacalltakerfromanotheragencytransferringtheoriginalcalltothereceivingagency.
TelephoneReportingUnit
transfer
FlowofEvents1..1UpdateCFSData[Ifduplicate]Informationrelatedtoanopencallwillbeupdatedasinformationbecomesavailable.Multiplecallersprovidepotentialwitnessestothecallandmayprovideadditionalorsupportiveinformation.Thismayresultinreclassificationandprioritizationofthecall.ThedispatcherwillneedtheabilitytoenternarrativedataatanytimepriortoclosingtheCFS.
1..1.1Notes
DetailCallmayhavealreadybeendispatched.
1.2UseCaseDiagram
Call Taker
Caller
External Agency
External CAD
Unit
Dispatcher
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 3
Retrieve Incoming Call
Take Caller Data
Capture Location
Retrieve Alarm Location
Verify Location
Assign Call Classification and Priority
Check for Duplicate Calls
Update CFS Data
Create Call for Service
Correlate to Sector
Retrieve Preraise Hazard
and History
Retrieve Person
Information
Retrieve Vehicle
Information
Determine Dispatch Need
Utilize Call Disposition
(person called)
(alarm)
(first call) (duplicate)
(if person information is available)
(if no person information is available)
(resource dispatch not warranted)
(appropriate to dispatch)Routed
CallTakingActivityDiagram
-
4 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
1..2DetermineDispatchNeedAdecisionismadetodispatchaunitordirecttheCFSfordisposition.
1..2.1Notes
DetailThisflowassumesthatthecalltakerisalsothedispatcher,whichiscommonpracticeinsmallandmedium-sizeagencies.Inlargeragencies,calltakersroutecallstodispatchers,whohandletheincidentmanagementfromthatpointforward.
1..UtilizeCallDisposition[Ifresourcedispatchnotwarranted]AcalltakermaycloseaCFSthatdoesnotrequirethedispatchofresources.
ACFSwillbeclosedwhentheunitsatthescenehavecompletedtheassignment.Dependingontheagencystandardoperatingprocedures(SOP),theprimaryunitmayclosethecallwithastatus.Thedispatcherisnotifiedbyassignedunitsoftheirstatuschangeusingvoiceormobiledatacomputer(MDC)transactions.MDCtransactionsmayupdateCADtorecordtheunitstatusandclosetheCFS,ifthedatareceivedindicatestheCFSiscomplete.TheCFSwillbeclassifiedwithaspecificdisposition,generallyprovidedbytheprimaryunit.
Whenacallisclosed,informationcollectedduringtheCFSmaybeautomaticallytransferredfromtheCADsystemtotherecordsmanagementsystem(RMS).AnyupdatesmadebytheCADoperatorsonreopenedcallswillbeautomaticallytransferredtotheRMS,subjecttoagencypolicies.
Ininstanceswhereaduplicatecallisidentified,onecallisdisposedwithacross-referencetotheoriginalCFS.Thecallswillbelinkedforfutureretrievability.
1..4AssignCallClassificationandPriorityAssignanaturecode,whichmayincludegeneralclassificationandsubtypesofthecall,baseduponagencypolicy.
Thecallwillbeprioritizedbasedupontype,applyingestablishedguidelinesandprocedures,todeterminetheappropriatedispatchandresponseneeds.
1..5CheckforDuplicateCallsThesystemautomaticallyevaluatestheCFSlocation(andpotentiallyothersiteparameters)todeterminewhetheracallisaduplicate.Thecalltakerevaluatestheinformationpresentedbythesystemwiththatobtainedfromthecallertomakethefinaldecisionregardingduplicatecalls.CallsforservicemaybereceivedbymanysourcesforthesameCFS,suchasatrafficaccidentwitnessedbytwoor
moremotoristsorafirealarmreportedfromanelectronicmonitoringsystemorawitnessreportingsmokecomingfromabusiness.Thecallmaybedeterminedtobeunique,butthereshouldbeacapabilityoflinkingthecalltoanotherexistingcall.
ThisanalysiswilldeterminewhetheranewCFSisrecordedinCADorwhetheranexistingCFSistobeupdatedwithinformationnotyetcaptured.
1..5.1Notes
Detail[Description]Thecalltakermayhavetheabilitytoreopenacallbutmaynotbeabletoclosethecallonceithasbeenreopened.
1..6TakeCallerData[Ifpersoncaller]Thecalltakerrequestsbasicinformationofthecaller.Many911systemsprovideinformationaboutthephoneaccount(ANI)originatingthecall,whichmayormaynotbeverifiedimmediately,dependingonthenatureandpriorityofthecall.
ThebasicinformationneededtoopenandinitiateaCFSisthetypeofcall(natureofthecomplaint),thepriority,andthelocationoftheCFS.Dependinguponthepriorityofthecall,whenbasicinformationhasbeenentered,theCFScanberoutedtotheappropriatedispatcherforhandling.
1..7CaptureLocationInmanyinstances,thecalltakerhasaccesstothecalloriginationlocation(ALI/ANI)datausingthe911system.Ifnot,theCFSlocationmustbeelicitedfromthecaller.Insomeincidents,thecallerslocationmaynotbethelocationofthecallforservice.
1..7.1AlternativeFlows
DetailIfthecallisgeneratedfromthe911system,thelocationmaybeavailablefromANI/ALI,ifsuchaninterfaceexists.PhaseIcellularcallsmaygivethelocationofthenearesttower.PhaseIIcellularmaygivethecoordinatesofthecaller.Beyondlatitudeandlongitude,thealtitudemaybecaptured.
1..8VerifyLocationThecallerlocationwillbecheckedagainstcurrentaddresslistingsinthesystem.Locationsthatarenotverifiedprovideanindicationtothecalltakerthatinformationreceivedmaybeinaccurate,providingadditionalinformationforthedispatchertorelaytotheresponder.
Thelocationformatcanbeastreetaddress(blockfaceaddress),intersection,orcommonplacename.Location
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 5
informationforacommonplace,suchastheCityHall,hasastreetaddresslistingcross-referencethatwillprovidethelegalstreetaddress.Informationwillbecontainedinageofile,whichmustincludelatitudeandlongitude.Altitudewouldbeoptional.
Thegeofilewill:
Validatethatthestreetnameisanactualstreetintheservicearea.
Resolveambiguitieswhileaccountingforspellingvariationsandduplications.
Validateintersections.
Validateaddressrange.
Relatecommonplacenamestoactualaddresses.
RelateX/Y/Zcoordinatestoanactualaddress.
Transformlatitudeandlongitudetomapcoordinatesfordisplay.
Translatecalllocationtoagencyreportingarea.
Translatealiasnamestoactualstreetnames.
1..9RetrieveIncomingCallsIncomingcallsbyphoneareansweredintheorderthattheycomein.Callsfromthe911systemaregivenapriorityovercallsfromdirectphonelines.Thecentersoperatingprocedureswilldeterminewhetheranycallisallowedtogotovoicemailorbeputonhold.
1..9.1AlternativeFlows
DetailThecalltakeranswerscallsfromthepublicfroma911line,a7-or10-digitphonenumber,oraTDD/TTYdeviceforthehearing-impaired.
1..10RetrievePersonInformation[Ifpersoninformationisavailable]Personinformationmayincludehistory,protectionorders,warrants,mentalorhealthissues,ganginformation,sexoffenderregistryinformation,etc.
Thiscouldbeautomaticallyqueriedbaseduponinformationenteredintofields,ifavailable.
1..11RetrieveVehicleInformationAnypertinentinformationofavehicle.Thiscouldbeautomaticallyqueriedbaseduponinformationenteredintofields,ifavailable.
1.
2.
.
4.
5.
6.
7.
8.
9.
1..11.1AlternativeFlows
DetailThisflowassumesthatthecalltakerisalsothedispatcher,whichiscommonpracticeinsmallandmedium-sizeagencies.Inlargeragencies,calltakersroutecallstodispatchers,whohandletheincidentmanagementfromthatpointforward.
1..12RetrievePremiseHazardandHistoryRelevanthistoricalandtacticalinformationaboutspecificandneighboringpremisesisobtainedfrominternaland/orexternalsourcesfordecisionsupport.Thisinformationmayincludeinformationaboutpreviouscallsforserviceatthepremise,whetherthepremisehasrecordsofregisteredfirearms,hazardousmaterialsstoredatthesite(usuallybusinesssites),seriousmedicalinformationconcerningindividualsresidingatthepremise,andotherrelevantinformation.
1..1CreateCallforService[Iffirstcall]AnewcallforserviceisrecordedintheCADusinginformationcompiledtodate.Auniquecallnumberisassigned.
1..14CorrelatetoSectorThelocationinformationobtainedfromthecallerandverifiedbythegeofilewillbecheckedtoidentifythepatrolareaassignmentinwhichthecallislocated.
1..14.1AlternativeFlows
DetailInlargeragencies,itisthecalltakersfunctiontosimplydeterminethenatureofthecallandthecalllocationandthenroutethecalltothedispatchersothatunitscanbeplacedenroute.
1..15RetrieveAlarmLocation[Ifalarm]Obtainthelocationofanelectronic-generatedcallfromthecallsourceinformation.LocationandcontactinformationfromelectronicsourcesmaybereceivedfromdataexchangestoCADormaybeobtainedfromadatabaseofcommonaddressesmaintainedbytheagency.
Postconditions PostconditionDescriptionsRouted Informationinvoice,paper,or
electronicformwasrecordedandsentordistributedtointendedrecipients.
-
6 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
1.4UseCaseSpecification:DispatchDecisionSupportThedispatcherispresentedwiththerecommendedresourcesfortheselectedCFS,baseduponpresetcriteriaforthetypeandpriorityofCFS.Furtherinformationwillbeconsidered,suchasthehistoryofthelocation,suspect,andthepossibilitythathazardousmaterialsmaybeinvolved.Therecommendedresourcesmaybeoverriddenbythedispatcherbasedontheadditionalinformationorrequestsbyofficersonthescene.Thesystemmayhavethecapabilitytoperformdispatchdecisionsupport,suchasassigninganincidentnumberwithouthumannterventon.
UnitsavailablewillbeconsideredaswellastheavailableunitproximitytotheCFS.Thefinaldecisioniswhichspecificunitstodispatch.
AssociatedActor
Relationship Description
CallTaker calls
Dispatcher performs
AssociatedActor
Relationship Description
TelephoneReportingUnit
transfer
FlowofEvents1.4.1ReviewCallBackgroundInformationTheinformationassociatedwiththelocationand/oraffiliatedpersonisconsideredtodeterminewhethertherecommendedresourcesareadequate.Thedecisiontooverridetheresourcerequirementshouldbemadeifitisdeterminedthattherecommendationisinadequate.
1.4.2DispatchResourceDecisionRecommendedresourcesareassignedbasedonSOPsthatfactorworkloadandunitcapabilitywithregardtoskillsandequipmentrequiredfortheCFS,unitavailability,andtheproximityofresources.
1.4.RetrieveCFSFromCallPendingQueueThenextCFSonthecallpendingqueueisretrieved.Thecallwillcontainallinformationcollectedduringthe
Retrieve CFS from Call
Pending Queue
Determine Resource
Availability
Review Call Background Information
Retrieve Resource
Recommendations
Determine Proximity of Resources
Dispatch Resource Decision
Override Resource
Requirement
CFS Resource Assigned
(recommended requirement appropriate)
(recommended requirement appropriate)
DispatchDecisionSupportActivityDiagram
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 7
calluptothepointitisretrieved.AdditionalinformationmaycontinuetobeaddedtothecallbycalltakersanddispatcherswhiletheCFSisopen.
Callsinthequeuearestackedbyagency-definedpriority,oftenbasedonSOP.TheCADsystemallowstheagencytodeterminethesortorderofthecallpendingqueue.
1.4..1AlternativeFlows
DetailIntheeventofanofficer-initiatedcall,theunitcaninitiateacallbyreportingtheeventtothedispatcher,whocreatesanewcallfordispatchandplacestheofficeron-sceneataninitiatedcall.BasedonSOP,theofficermaydirectlyinitiatethecallthroughamobiledevice,ifavailable.
1.4..2Notes
DetailEventsarestackedbyagency-definedpriority,oftenbasedonSOP.
1.4.4RetrieveResourceRecommendationsResourcerecommendationsareinitiallydeterminedbasedonthecalltype,priorityandlocationinformation,andothercharacteristicsofthespecificCFS.Thecalltypeandprioritylevelareusedbasedonagencypolicyandprocedure.Thedispatchermustreviewresourcesrecommendedbythesystem.Inselectingappropriateresources,thedispatchermayconsideranumberoffactors,suchasproximitytothecalllocation,numberofunitsavailable,specialskillsorequipment,andthenumberandtypeofotherCFStowhichofficersareresponding.Thesefactorsmayormaynothavebeenconsideredintheinitialsystemrecommendation.
1.4.5OverrideResourceRequirement[Ifrecommendedrequirementappropriate]Theinitialrecommendationbaseduponknowncriteriamaybeadjustedbaseduponadditionalinformationthatbecomesavailable,suchaslearningthatthesuspectisknowntobearmedanddangerous.Overridemustberecorded.
1.4.6DetermineResourceAvailabilityAvailableresourcesaredisplayedbaseduponunitstatus,whichwouldincludeunassignedaswellasassignedwithalowerprioritystatusofcalltowhichaunitisassigned.TheunitsmaybecurrentlyunassignedorassignedtoaCFSwithadesignatedtypeandprioritylevel.Unassignedunitsareavailabletobedispatched.
1.4.7DetermineProximityofResourcesResourceproximitycanbebasedonaclosenesscalculation,whichcanbedistanceordrivingtime.Anyunitsuggestionmustrespectdispatchcontrolareas
anddepartmentalSOP.ProximitydeterminationcanbesupportedbyanoptionalAVLinterface.
1.5UseCaseSpecification:BOLOBOLO(BeontheLookout)canbeanoptionalpartofaCADapplicationorapartofanRMSsystem.BOLOsinCADarecreatedandmaintainedinadatafileinCAD.Thesemaybeenteredbyadispatcherormaybecreatedbyanyonewhohasbeengiventherequiredsecurityclearancetocreateormaintainthefile.
BothanRMSinterfaceandthemobiledataterminalinterfaceshouldsupportthecreationandtransmissionofaBOLO.ABOLOshouldbeassignedanexpirationdate,eitherbythepersonwhocreatesitorbythesystem,basedondepartmentpolicyandavailablesystemresources.AtypicalBOLOfilewouldincludethenatureoftheBOLO,priority,date,rangeofeffectiveness,subjectpersonandsubjectvehicleinformation,andcontactinformation.ThereshouldbeamechanismtosearchtheBOLOandtoprintitinareportandtopurgetheBOLOsoutofthedaterange.
1.6UseCaseSpecification:DispatchUnitsTheunitsspecificallyrecommendedorselectedforaCFSwillbedispatchedandtheiracknowledgmentrecorded.OtherunitsnotdispatchedmaybenotifiedofaneventinprogressiftheCFSwarrants.Whenmultipleunitsaredispatched,oneunitwillbedesignatedastheprimaryresponderresponsiblefortheCFSuntilitiscompleted.
AssociatedActor
Relationship Description
Unt dispatched
Dispatcher performs
FlowofEvents1.6.1RecordUnitActivityTheunitstatuswillbeupdatedtoassociatethedispatchedunitorunitswiththeCFS,includinglocationandtime.
1.6.2PlaceCallonUnassignedStatus[Ifunitpulledoffofcall]Theunitisreassignedtoanewcallandautomaticallyunassignedfromthepreviouscall.
-
8 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
Recognize Acknowledgement
Utilize BOLO
Assign Units
Record Unit
Activity
Alert/Notify Units
Place Call on Unassigned
Status
RecordCFS Activity
Resources Dispatched
(dispatch) (alert or notify)
(no call affected)
(unit pulled off of call)
1.6.2.1Notes
DetailIfallunitsareremovedfromthecall,thentheCFSisplacedinthependingdispatchqueue.Thisisoftenreferredtoasapreemptedcall.
1.6.RecordCFSActivityTheCFSrecordwillbeupdatedtoassociatetheunitorunitsdispatchedasrespondingunitstothecall.
1.6.4RecognizeAcknowledgement[Ifdispatch]Theunitassignedtothecallwillrespondtothedispatchertoconfirmreceiptofthedispatch
information.Thismaybedonebyvoicecommunicationorthroughmobiledatacomputers.
1.6.5Alert/NotifyUnitsThedispatcherwillrelayinformationpertainingtocallsforservicetotheappropriateunits.Thisnotificationhasthepurposeofinformingandraisingtheawarenessofdesignatedteamsorallofficers.
1.6.5.1AlternativeFlows
DetailAlertingotherunitsorcommandmaynotoccurandislikelybasedonSOP.
DispatchUnitsActivityDiagram
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 9
1.6.6AssignUnitsThedispatcherwillassignaCFSandrelaypertinentinformationtotheappropriateunitsinthefieldforthepurposeofdispatchingaresponder.AnoptionalMDCinterfacesupportsthisactivity.
AssignedbutavailableunitsmaybepulledoffofcurrentassignedstatusbasedonprioritylevelsandtheresourceneedsoftheCFS.Ifalltheunitsarepulledoffofacall,thecallwillbeaddedbackintothedispatchqueue.
UnitStatusManagementActivityDiagram
1.6.6.1Notes
DetailDecisionpoint.Unitmaybedivertedenroutewhileencounteringincident.Thiswouldreturntoofficer-initiateddispatch.[Description]DecisiontoalertornotifyisbaseduponSOP.
1.6.7UtilizeBOLO[Ifalertornotify]BOLO(BeontheLookout)canbeanoptionalpartofaCADapplicationorapartofanRMS
RecordUnit Location
Status Recorded
Display Unit Dispatch Status
Record Arrival on Scene
Timed Alerts
Maintain Status
Reassign to Available
Update Unit Status
(en route)
(unassigned)
(unit cleared from call)
(unit remains on scene)
-
10 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
system.BOLOsinCADarecreatedandmaintainedinadatafileinCAD.Thesemaybeenteredbyadispatcherormaybecreatedbyanyonewhohasbeengiventherequiredsecurityclearancetocreateormaintainthefile.
BothanRMSinterfaceandthemobiledataterminalinterfaceshouldsupportthecreationandtransmissionofaBOLO.ABOLOshouldbeassignedanexpirationdate,eitherbythepersonwhocreatesitorbythesystem,basedondepartmentpolicyandavailablesystemresources.AtypicalBOLOfilewouldincludethenatureoftheBOLO,priority,date,rangeofeffectiveness,subjectpersonandsubjectvehicleinformation,andcontactinformation.ThereshouldbeamechanismtosearchtheBOLOandtoprintitinareportandtopurgetheBOLOsoutofthedaterange.
1.7UseCaseSpecification:UnitStatusManagementUnitstatusmustbecontinuallymonitored,updated,andrecordedbythedispatcher.Thisinformationmaybemadeavailablebyvoicecommunicationorthroughmobiledatacomputers.Inadditiontorecordingtheunitstatusanddestination,theCFSnumberandtimes(action)willalsoberecordedbythesystem.Therecordingofstatuschangesisrepresentativeofaunitsworkactivityduringatimeinterval.ThisinformationisessentialtorunningstandardCFSreports.
Thesystemshouldmaintaintheelapsedtimebetweenstatuschanges/checksandalertthedispatcherwhenagency-definedthresholdsaremet.
AssociatedActor
Relationship Description
Unt records
Dispatcher maintains
FlowofEvents1.7.1DisplayUnitDispatchStatusThecurrentstatusofunitswillbeavailableatalltimes.Thedisplaywillindicatetheunitsstatusandassignedcallsforservice(ifany).Thedisplaycanalsoshowthelocationorlastknownlocationoftheunit.IntheabsenceofAVL,thelocationmaybethecurrentcalllocation,thelastcalllocation,orthelocationenteredbythedispatcherorMDC.Inthecaseofassignedunits,thedisplaymayshowanyalerttimer,theCFStype,andpriority.
Examplesincludearrivedonscene,available,unavailable,andunavailablebutassignable.Morestatustypesshouldbeconfigurable.
1.7.1.1Notes
Detail[Description]Decisionpoint.Unitmaybedivertedenroutewhileencounteringanincident.Thiswouldreturntoofficer-initiateddispatch.
1.7.2RecordArrivalonScene[Ifenroute]Unitsrespondingtothescenecommunicatetodispatchthattheyhavearrivedatthelocation.ThiscommunicationmayoccurverballyorthroughanMDCtransmissionthatmayautomaticallyupdateCADtoreflectthecurrentstatusoftherespondingunit,includingtimeofarrivalonscene.
Theremaybeaneedtorecordmultiplearrivaltimes;anexamplewouldbethearrivalatthelocationandanotherarrivalatthescene.Forexample,aunitmayarriveatthelocationofahigh-risebuildingandatalatertimewillarriveatthescenelocatedwithinthebuilding.Thesystemshouldprovideforthesettingofdifferenttimersbasedupontime-of-arrivaltype.
1.7.2.1Notes
Detail[Description]Thesystemshouldmaintainadate-andtime-stampedunitlogthatincludesallchangesinunitstatus.
1.7.TimedAlertsThesystemmustbeabletoalertthedispatchertotheexpirationofthetimerassociatedwithanystatuschange.Thealerttothedispatchermaybeintheformofatoneand/oravisualprompt.ThisshouldbeconfigurablebaseduponthetypeofCFS.Thesystemshouldrecordtheacknowledgementoractionofthedispatcherinresponsetotheprompt,whichwillautomaticallyresetthetimer.
1.7.4RecordUnitLocationAnychangeinunitlocationiscapturedalongwithtimestamps,includingchangesoflocationassociatedwiththesameCFS.
1.7.5MaintainStatus[Ifunassigned]InformationiscontinuallydisplayedinCADtoreflectthecurrentstatusofunitsthataremonitoredbythedispatcher.
1.7.6ReassigntoAvailable[Ifunitclearedfromcall]WhenaunithasclearedfromasceneandisnolongerassignedtotheCFS,theunitwillbereassignedtoanavailablestatus.DatareceivedfromMDCtransmissionsmayupdateCADandreflectthenewstatusoftheunit.Theunitmayremainonsceneandhaveanavailableon-scenestatus.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 11
Call Monitored
Assign RMS Incident Number
(RMS requires incident data) Transfer Basic
Incident Data to RMS
Display Additional CFS Data
ReopenCFS
Dispatch Resource Decision
Assign Units
Utilize Supplemental
Resources Tracking
Display CFS Data
(no additional information)
(additional information available)
Update CFS Data
Update Assigned
Resources
Update Call Status
(less resources needed)
(additional resources needed)
(resource requirement changed)
(closed CFS identified)
(open call)
(supplemental resources not needed)
(resource requirement not changed)
(supplemental resources needed)
(additio
nal
info
rmat
ion)
CallManagementActivityDiagram
-
12 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
1.7.6.1Notes
DetailClearingthecallmayhavethecapabilityofclearingallunitsassignedtotheCFSwhenallunitssimultaneouslyarereassignedtoavailablestatus.
1.7.7UpdateUnitStatus[Ifunitremainsonscene]InformationiscontinuallyupdatedinCADtoreflectthecurrentstatusofunitsthataremonitoredbythedispatcher.
PostconditionsPostcondition Description
StatusRecorded ThestatusoftheunitisrecordedintheCADsystem.
1.8UseCaseSpecification:CallManagementThecallismanagedbycontinuallyupdatingtheCFSdatawithanyadditionalinformationreportedbycallersorofficersonscene.Theresourcerecommendationsmayberevisedbasedonadditionalinformationandmaybeaddedorreassigned.
Postcondition Relationship Description
Dispatcher records
FlowofEvents1.8.1DisplayCFSData[Ifnoadditionalinformation]TheCFSwillneedtobedisplayedandmonitoredthroughCAD.Thisincludesactivitiessuchasadditionalcallinformationandactivitiesreportedbytheofficers.Immediateaccesstoallopencalls(includingunassigned)shouldbeprovidedontheCFSstatusdisplay.Whenacallisclosed,itwillautomaticallyberemovedfromthecalldisplay.
1.8.2UpdateCallStatus[Ifnoadditionalinformation,resourcerequirementunchanged,supplementalresourcesnotneeded]Thestatusofthecallisupdatedasnewinformationisreceived.ThisshouldincludeupdatingthereportedCFStypetotheactualCFStype.Forexample,oncetheimmediateincidentisresolved,therespondingunitwillcommunicatetothedispatcherthatthesceneissecured.
1.8.2.1AlternativeFlows
DetailInsomejurisdictions,dispatchersmaynotalwaysmakethedecisionastowhethertheeventhasadequateresources.Inthoseinstances,itismostlikelyacommanderonscenethatmakesthisdeterminationandthedispatcherwillrespondbysendingmoreunitswhenrequestedbythoseonscene.
1.8.DispatchResourceDecision[Ifresourcerequirementchanged]RecommendedresourceswillbeassignedbasedonSOPthatfactorworkloadandunitcapabilitywithregardtoskillsandequipmentrequiredfortheCFS,unitavailability,andtheproximityofresources.
1.8.4UpdateAssignedResources[Iflessresourcesneeded]Whenrequiredresourcesforthecallhavechanged,thiswillbeadjustedandrecordedonpredeterminedcriteria.
1.8.5UtilizeSupplementalResourcesTracking[Ifsupplementalresourcesneeded]Forexample,incaseswhereavehiclehasbeenconfiscatedorfoundtobedisabled,thedispatcherneedstheabilitytorequesttheservicesofatowingcompany.Thisrequestmaybemadebycompanyname(ownerrequested)orbyrotation.Incaseswheretheownerdoesnothaveapreferredcompany,thesystemwillselectacompanyfromthetowingrotation.Atowingrotationpreventsanyonecompanyfrombeingfavoredoveranother.
Ifresourcesotherthanthoserecommendedbytherotationareselected,thesystemshouldcapturethereasonfortheexception.
1.8.6AssignUnits[Ifadditionalresourcesneeded]ThedispatcherwillassignaCFSandrelaypertinentinformationtotheappropriateunitsinthefieldforthepurposeofdispatchingaresponder.AnoptionalMDCinterfacesupportsthisactivity.
AssignedbutavailableunitsmaybepulledoffofcurrentassignedstatusbasedonprioritylevelsandtheresourceneedsoftheCFS.Ifalltheunitsarepulledoffofacall,thecallwillbeaddedbackintothedispatchqueue.
1.8.7UpdateCFSData[Ifopencall]Informationrelatedtoanopencallwillbeupdatedasinformationbecomesavailable.Multiplecallersprovidepotentialwitnessestothecallandmayprovideadditionalorsupportiveinformation.Thismayresultinreclassificationandprioritizationofthecall.ThedispatcherwillneedtheabilitytoenternarrativedataatanytimepriortoclosingtheCFS.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 13
1.8.8AssignRMSIncidentNumberInadditiontotheCADCFSnumber,anRMSincidentnumber(casenumber)maybeassignedbeforethecallistransferredtotheRMSsystem.Thismayhappenatanytimepriortosendingthereportbutmostlikelyafterthedeterminationthatitwillbesent.TheRMSnumbermaybeassignedfromadatafileofincidentnumbersmaintainedintheCADsystemincoordinationwiththeRMSsystem.DepartmentpoliciesinthisareamustbesupportedbytheCADsystem.
1.8.9TransferBasicIncidentDatatoRMS[IfRMSrequiresincidentdata]Basicincidentdatathatcanbemodifiedwillbetransferredtotheagencyrecordssectionforitsuse.Itwillbetransferredinaneditableformat.
ThisfunctionrelatestothetransferfromCADtoRMSoftheCFSdataelementsnormallycontainedinalawenforcementincidentreport.Infact,theJusticeXMLreferencedocumentforalawenforcementincidentreportshouldprovideanexcellentstandardforthetransfer.
Thefollowingareexamplesofthetypesofdatafoundinanincidentreport:reportnumber,CADcalltype,natureofcall,date/timeofcall,locationofincident,andpersonsandvehiclesinvolved.TheCADCFSnumbershouldbeincludedtoprovideacross-referencebetweentheCFSandthesubsequentincidentreport.
Incidenttransferisnormallytriggeredandtakesplaceautomatically.Withintheframeworkofthisstandard,itwouldhappen(optionally)asanincidentreportnumberisassignedandatthetimeoffinaldispositionoftheCFS.TheCADsystemsshouldincludeafeaturewherebyadministrativecommandscanbeexecutedtotransfereitheraspecificincidentoraseriesofincidentsbaseduponparameters.
1.8.10DisplayAdditionalCFSData[Ifadditionalinformationavailable]Asadditionalinformationismadeavailable,thedispatcherwillbealertedandhavetheabilitytoviewthenewinformation;forexample,anyinformationenteredbyacalltakeroranotherdispatcher.
1.8.10.1Notes
DetailThereneedstobeameanstoeasilydisplayrecentlyclosedcalls.
1.8.11ReopenCFS[IfclosedCFSidentified]AnexistingCFSisreopenedforupdate.Changesaretracedforauditpurposes.
Request Supplemental
Resource
(service unavailable)Retrieve
Supplemental Resource
Rotation List
Notify Supplemental
Resource Service
Enter Supplemental Service Record
Update Supplemental Service Record
Supplemental Resource
Dispatched
1.8.11.1Notes
Detail[Description]ACFSmaybereopenedbyadispatcherorcalltaker,butthecalltakermaynothavetheabilitytocloseareopenedcall.
SupplementalResourcesTrackingActivityDiagram
(supplemental service available)
-
14 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
1.9UseCaseSpecification:SupplementalResourcesTrackingForexample,incaseswhereavehiclehasbeenconfiscatedorfoundtobedisabled,thedispatcherneedstheabilitytorequesttheservicesofatowingcompany.Thisrequestmaybemadebycompanyname(owner-requested)orbyrotation.Incaseswheretheownerdoesnothaveapreferredcompany,thesystemwillselectacompanyfromthetowingrotation.Atowingrotationpreventsanyonecompanyfrombeingfavoredoveranother.
Ifresourcesotherthanthoserecommendedbytherotationareselected,thesystemshouldcapturethereasonfortheexception.
FlowofEvents1.9.1RequestSupplementalResourceAlawenforcementofficialrequeststhatasupplementalresourceservicebedispatchedtoaspecifiedlocation.
1.9.2RetrieveSupplementalResourceRotationList[Ifsupplementalserviceunavailable]Theagencywillobtainthecontactinformationfromthesysteminordertocontactandrequestservicefromthenexteligibleservice.
DetermineCall Status
Call Closed
CallDispositionActivityDiagram
Utilize Call Management
Determine Reportability
Record Disposition
Assign RMS Incident Number
Send Data to RMS
Active Call for Service
(services rendered)
(call in progress)
(nonreportable CFS)
(report required)
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 15
Thesystemmayprovidealistofoneormoreservices.Thiscouldbebasedongeographicalrequirements.
1.9.NotifySupplementalResourceServiceThesupplementalresourcewillbecontactedtoprovidedispatchinformationbythedispatcherandwillbeprovidedinformationabouttheincidenttowhichitisrequestedtorespond.Theavailabilityoftheservicetoprovideserviceswillberecorded.Asupplementalservicethatcannotbecontactedorinformstheagencyofitsinabilitytorespondwithinaprescribedtimeisconsideredunavailabletoprovidetheservice.Asupplementalresourcewillbeselectedfromthelistuntiloneisfoundthatisavailable.
1.9.4EnterSupplementalServiceRecordArecordofsupplementalservicerequestisestablishedtoreflecttheinstanceoftheselectionfromtheservicerotationlist.Thistriggerstherotationtothenextresourceintherotation.Therotationoccursregardlessoftheresourceabilitytorespondtotherequest.
1.9.5UpdateSupplementalServiceRecord[Ifsupplementalserviceavailable]Thesupplementalresourceresponsewillberecordedinthesystemtoreflecttheservicesprovided.
Postcondition Description
SupplementalResourceDispatched
Asupplementalresourcewascontactedwithdispatchinformationandconfirmeditsavailabilitytoprovidetheservice.
Postconditions
1.10UseCaseSpecification:CallDispositionAcalltakermaycloseaCFSthatdoesnotrequirethedispatchofresources.
ACFSwillbeclosedwhentheunitsatthescenehavecompletedtheassignment.DependingontheagencySOP,theprimaryunitmayclosethecallwithastatus.Thedispatcherisnotifiedbyassignedunitsoftheirstatuschangeusingvoiceormobiledatacomputer(MDC)transactions.MDCtransactionsmayupdateCADtorecordtheunitstatusandclosetheCFS,ifthedatareceivedindicatestheCFSiscomplete.TheCFSwillbeclassifiedwithaspecificdisposition,generallyprovidedbytheprimaryunit.
Whenacallisclosed,informationcollectedduringtheCFSmaybeautomaticallytransferredfromtheCADsystemtotherecordsmanagementsystem(RMS).Any
updatesmadebytheCADoperatorsonreopenedcallswillbeautomaticallytransferredtotheRMS,subjecttoagencypolicies.
Instanceswhereaduplicatecallisidentified,onecallisdisposedwithacross-referencetotheoriginalCFS.Thecallswillbelinkedforfutureretrievability.
AssociatedActor Relationship Description
Dispatcher records
FlowofEvents1.10.1DetermineCallStatusTheCFSwillremainopenandmonitored.ThestatusoftheCFSmaychangeasthesituationisresolved.TheoptionalMDTinterfacewouldallowtheofficetoenterCFSdisposition.
1.10.1.1AlternativeFlows
DetailTheoptionalMDTinterfacewouldallowtheofficetoenterCFSdisposition.
1.10.2UtilizeCallManagement[Ifcallinprogress]ThecallismanagedbycontinuallyupdatingtheCFSdatawithanyadditionalinformationreportedbycallersorofficersonscene.Theresourcerecommendationsmayberevisedbasedonadditionalinformationandmaybeaddedorreassigned.
1.10.DetermineReportability[Ifservicesrendered]CFSmayvaryintheneedtoreportbeyondtheCADsystem.Guidelinesaredefinedbytheagencypolicybaseduponacombinationofcalltypeandcalldisposition.
1.10..1AlternativeFlows
DetailIftheCFSisreportable,theassignmentofanincidentnumberfromtheRMSsystemmayoccurwhentheincidentnumberissentbackwithCADreportdatatotheRMS.Thismayhappenatanytimepriortosendingthereportbutmostlikelyafterthedeterminationthatitwillbesent.
1.10.4RecordDisposition[IfnonreportableCFS]Recordthedispositionofthecallforservice.Thismayincludeanarrativeinadditiontothetypeofdisposition.
1.10.5SendDatatoRMSCallhistory(completedetailsonclosedcalls)istypicallymaintainedinaCADsystemforarelativelyshorttime
-
16 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
frame.WhileinCAD,theCADsystemprovidesaccessbasedonaseriesofretrievalkeysand/orparameters,includingbutnotlimitedtocallnumber,location,date/timerange,etc.Callhistoryappliestothecompletecall,includinginitialcallinformation,unitassignments,statuschanges,imbeddedinquiriesandresponses,triagerequestsandresults,comments,cross-references,etc.Inotherwords,itcontainseverythingthatwasrecordedduringthetakingandhandlingoftheCFS.
Long-termstorageofcallhistoryrecordsisnormallyrelegatedtoeitheranRMSorastand-alonecalls-for-servicesystem.TheCFShistorysystemisusedfordatalook-upandinformationretrieval,plusitsupportsextendedstatisticalprocessesbasedontypesofevents,timestorespond,callsbyarea,date/time,andsoon.Becauseoftheneedforstatisticalanalysis,callhistorydataneedstobestructuredsoastofacilitateidentifyingspecifictypesofdata,suchaseventsandassociateddatesandtimes.
1.10.6AssignRMSIncidentNumber[Ifreportrequired]InadditiontotheCADCFSnumber,anRMSincidentnumber(casenumber)maybeassignedbeforethecallistransferredtotheRMSsystem.Thismayhappenatanytimepriortosendingthereportbutmostlikelyafterthedeterminationthatitwillbesent.TheRMSnumbermaybeassignedfromadatafileofincidentnumbersmaintainedintheCADsystemincoordinationwiththeRMSsystem.DepartmentpoliciesinthisareamustbesupportedbytheCADsystem.
1.10.6.1Notes
Detail[Description]AnRMSincidentnumberincludedindatasenttoanRMSwilltriggerthecreationofaninstanceofanincidentreporttorelevantinformationcapturedfromCAD.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 17
2 CADSystemAdministration2.1Description:SystemadministrationencompassesawidearrayofgeneralrequirementsthatlawenforcementagenciesneedfromCADsystemsinordertobeabletoqueryinformationeffectively;ensureappropriateaccesstoinformationandsystemssecurity;andensureeffectiveinformation,image,anddocumentmanagement.
Thereareseveraldistinctrequirementsassociatedwithsystemadministration:
Tablemaintenance
Securityanddatamanagement
Geofilemaintenance
Errorlogging
Customization
2.2UseCaseDiagram(seepage18)
2.UseCaseSpecification:GeofileMaintenanceThegeofileisusedtovalidateandstandardizelocationandaddressinformation.Itisalsousedtocross-referenceaddressesandlocationswithlawenforcement-definedreportingareas,X/Y/Zcoordinates,ZIPcodes,andotheridentifiers.Thegeofilecontainssufficientinformationtoensurethatanaddressisvalid.Furthermore,itprovidescross-referencestoaddressesandlocationsusingcommonplacenames(e.g.,businessnames,parks,hospitals,andschools)andstreetaliases.Itincludesinformationsuchasdirectionoftravelonparticularstreetsandcanidentifythesideofastreetforaspecificaddress.ItisassumedthatalladdressesintheRMSarevalidatedusingthesystemgeofile.
1.
2.
.
4.
5.
Thereportingareadefinedaboveshouldbeusedtodefinebeats,sectors,commandareas,neighborhoods,communities,etc.
Thegeofilecontainsthegeographicinformationthatisthebasisformanydecisionsinacommunicationscenter.Thesystemneedstoprovidetheabilityforanagencytoenterandupdateallgeofiledata,includingthephysicaladdressandtheX/Y/Zcoordinates.
Thecreationofacomprehensivegeofileisasignificantundertaking.Thesystemshouldsupportthecreationandmaintenanceofthegeofileusinganavailablemapping/GISdatabase.GeofileinformationinCADandRMSshouldbesynchronized,basedonestablishedparameters.
AssociatedActor Relationship Description
System provides
RMS supplies
2.4UseCaseSpecification:SecuritySystemsshouldallowtieredaccesstoinformationbasedonpasswordsandotherauthenticationandnonrepudiationpractices.Role-basedauthenticationandauthorizationmustbeapartoftheRMS.Otheridentificationtechnologiessuchasbiometrics,IDcard,securitytoken,etc.areemergingstandards.
Systemsshouldapplyappropriateeditstoallentereddatatoensuredataintegrityandmaintainactivitylogsandaudittrails.
BusinessFunction:
-
18 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
Security
Configuration
Communication Center Relocation
Systemprovides
supplies
provides
allows
provides
GeofileMaintenance
supports
Logging
Table Maintenance
CAD Catch-Up
initiates
provides
performs
AssociatedActor Relationship Description
SystemAdministrator
provides
2.5UseCaseSpecification:LoggingCADwilllogallactions,includingsecurityviolationsandattemptedbreeches,errors,changes,andupdates.Logsshouldbeviewableandsearchablebythesystemadministrator.
AssociatedActor Relationship Description
System provides
2.6UseCaseSpecification:ConfigurationTheCADshouldbeconfigurabletoallowfortheenforcementofagencySOPs.Exampleswouldincluderesourceallocationalgorithmsanddispatchpolicies.
2.2CADSystemAdministrationUseCaseDiagram
Call Taker
Dispatcher
System Administrator
RMS
performs
performs
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 19
Thesystemshouldbeconfigurabletodeterminescreenparameters,colorchoices,fontsize,screenlayout,anduserpreferences.
AssociatedActor Relationship Description
System allows
2.7UseCaseSpecification:TableMaintenanceTheflexibilityneededinaCADsystemrequiresthatthedatausedtosupportsystemrecommendationsordecisionsbemaintainedintablesthatcanbesupportedandchangedbytheagency.EachdepartmentwillhavetheirownsetofStandardOperatingProcedures(SOPs)thatmustbefollowedwithregardtotablemaintenance.
Inaddition,theCADsystemmustbeflexibleenoughtoallowthesystemsetuptoreflecttheSOPsatthetimethesystemisinitiallyinstalledandtobechangedwhenthedepartmentSOPschange.SOPsaretypicallydefinedandmaintainedinaseparatedocumentortheymaybeavailableforreferenceonlineasaCADhelpfile.
Examplesofcommontablesincludebutarenotlimitedto:
Units
Calltypesandpriorities
UnitStatusTypes,e.g.,assigned,unassigned,andassignedbutavailable
Personnel,includingemergencycontactinformationandcurrentassignment
ServiceProviders
Patrolandcommandareadefinitions
Timers
Commands
1.
2.
.
4.
5.
6.
7.
8.
AssociatedActor Relationship Description
Systems provides
SystemAdministrator
performs
2.8UseCaseSpecification:CommunicationCenterRelocationThesupportofanemergencythatrequiresthatthedispatchcenterbemovedtoanoff-sitesecurelocationmustincludeahardwaresystemandnetworkconnectivitythatwillsupportthecreationofanoff-site,real-timebackupserverattherelocatedcommunicationcenter.
AssociatedActor Relationship Description
System supports
2.9UseCaseSpecification:CADCatch-UpTheabilitytorecoverfromtheinterruptionofCADservices,allowingtheagencytoenteractivitydataperformedduringtheinterruptionofservice.
AssociatedActor Relationship Description
SystemAdministrator
initiates
CallTaker performs
Dispatcher performs
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 21
3 BusinessFunction:.1Description:Inadditiontothehandlingofcallsforservice,theCADsystemshouldsupporttheeffectivemanagementoftheavailableresources.Theneedfortheoptionalitemswillbebasedontheagencysize,thepopulationservedbythedepartment,andotheraspectsofthespecificdepartmentordepartmentsservedbytheCADsystem.
.2UseCaseDiagramSupportServicesUseCaseDiagram
.UseCaseSpecification:BOLOBOLO(BeontheLookout)canbeanoptionalpartofaCADapplicationorapartofanRMSsystem.BOLOsinCADarecreatedandmaintainedinadatafileinCAD.Thesemaybeenteredbyadispatcherormaybecreatedbyanyonewhohasbeengiventherequiredsecurityclearancetocreateormaintainthefile.
BothanRMSinterfaceandthemobiledataterminalinterfaceshouldsupportthecreationandtransmissionofaBOLO.ABOLOshouldbeassignedanexpirationdate,eitherbythepersonwhocreatesitorbythesystem,basedondepartmentpolicyandavailablesystemresources.AtypicalBOLOfilewouldincludethenatureoftheBOLO,priority,date,rangeofeffectiveness,subjectpersonandsubjectvehicleinformation,andcontactinformation.ThereshouldbeamechanismtosearchtheBOLOandtoprintitinareportandtopurgetheBOLOsoutofthedaterange.
SupportServices
.2SupportServicesUseCaseDiagram
provides
Emergency Operations
Center
BOLOprovides
System
-
22 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
AssociatedActor Relationship Description
System provides
.4UseCaseSpecification:EmergencyOperationsCenterThesupportofanemergencythatrequiresthatthedispatchcenterbemovedtoanoff-site,securelocationmustincludeahardwaresystemandnetworkconnectivitythatwillsupportthecreationofanoff-site,real-timebackupatserverslocatedattheEmergencyOperationsCenter(EOC).Otherfunctionalitythatcanbeprovided
bytheCADsysteminsupportofEOCoperationincludesremoteCADdispatchingcapabilityandsupportformultiagencyeventcoordination.
ThesetwooptionalfeaturesprovidebenefitstotheCADsystemevenifthedispatcherdoesnothavetobemoved.Multiagencyeventcoordinationusuallyrequiresthatsupportagreementsbenegotiatedandinplaceamongalloftheagencies.AnotherdesirablefeatureinsupportofanEOCwouldbetheabilitytoaddadditionalagenciesontheflyduringanemergencyoperation.
AssociatedActor Relationship Description
System provides
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 23
4 BusinessFunction:4.1Description:CommandmustbeabletogeneratereportsandmanagetheworkflowofthecalltakersanddispatchersintheDispatchCenter.
4.2UseCaseDiagramCallManagementandManagementReportingUseCaseDiagram
4.UseCaseSpecification:DispatchSupervisorSupportTheCADsystemshouldprovidethesupervisorwiththeabilitytomonitortheactivityonanydispatcherworkstation.Ifnecessary,asupervisorneedstohavetheabilitytotakedirectcontroloveradispatchpositionremotely,withoutleavingthesupervisorconsole.
AssociatedActor Relationship Description
System provides
4.4UseCaseSpecification:CADManagementReportingItisessentialthattheCADsystemincludestandardreportsthatcanberunusingflexibleparameters.NewreportsshouldbedefinedeitherthroughtheCADsystemorathird-partyreportingtoolandthenbestoredasastandardreportavailablethroughtheCADsystem.
Thefunctionalityneedstoincludetheabilitytoreportanydataelementbyanyotherdataelementinthesystem.Thismayincludetheabilitytoexportdataforuseinthird-partytools.Awizardmaybeprovidedthatallowsforuser-generatedreports.
CallManagementandManagementReporting
provides
Dispatch Supervisor
Support
Training and Testing
CAD Management
Reporting
provides
4.2CallManagementandManagementReportingUseCaseDiagram
System
-
24 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
ExamplesoftypicalCADreportsincludethefollowingreportsthatcanberunbyanyuser-defineddateandtimerange:
Dailylogshowingallcallsreceivedfortheprior24hoursfromtimeofprinting
ActivityAnalysisbyspecifiedgeographicalareaandbytimeperiod
CFSSummarybyspecifiedgeographicalareaandbytimeperiod
ActivityAnalysisbydayoftheweek
ActivityAnalysisbyhouroftheday
ActivityAnalysisbydayandhour
ResponseTimeAnalysisbyspecifiedgeographicalareaandbytimeperiod
ResponseTimeAnalysisbycalltype
TimeConsumedbycalltypebyhouroftheday
WorkloadActivitybyresource
WorkloadActivitybygroup
TimeConsumedbydayoftheweekandhouroftheday
TimeConsumedbyspecifiedgeographicalareaandbytimeperiod
Attemptedbreachesinsecurity
Errormessagesbytypeforidentifyingsystemproblems
Customizingreportstomeetdepartmentneedsshouldalsobeanoption.
AssociatedActor Relationship Description
System provides
4.5UseCaseSpecification:TrainingandTestingThisfunctionrelatestothenecessityofhavingaregionontheCADsystemthatisisolatedfromtheproductionenvironmentforthepurposesofprogramtestingandfile
1.
2.
.
4.
5.
6.
7.
8.
9.
10.
11.
12.
1.
14.
15.
maintenancetesting,aswellastrainingofnewpersonnel.ThisfunctionmaybereferredtoasaCADtrainingmode.
Tothegreatestextentpossible,thetrainingenvironmentshouldbeidenticaltotheproductionregion,thusallowingaccuratetestingandtrainingtooccurwithoutimpactingtheproductionenvironment.Thefollowingareexamplesofthetypesofitemstoincludeinthetrainingenvironment:
Definitionofthetypesofagenciesbeingutilized;i.e.,Law,Fire,EMS
Tablesdefinedtoincludeunitnames,recommendationpatterns,premiseinformation,personnelinformation,securitypermissions,etc.
SeparatetestE911connectionoracannedscriptofE911information
Separatetestmobileconnectionoracannedscriptofmobileinformation
Accesstoaudibleradiotransmissions
Thetrainingenvironmentshouldhaveitsownstart-and-stopsequencethatisindependentoftheproductionenvironment.Thetrainingenvironmentdoesnothavetobeactiveatalltimesandcanbestartedasneeded.
Byhavingthetrainingenvironmentestablishedanddefined,theagencycandeveloparobusttrainingprogramthatsimulatestheliveenvironmenttoincludetheassociatedinterfacesandradiotraffic.Thepersonnelcanenterincidentsandmockliveincidentsthatareoccurringontheradiowithouttheproductionenvironmentdatabeingaffected.
Additionally,anyprogrammaticchangeorchangestofilemaintenancerecordscanbethoroughlytestedandanyissuesresolvedpriortobeingimplementedintheproductionenvironment.
AssociatedActor Relationship Description
System
1.
2.
.
4.
5.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 25
5 BusinessFunction:5.1Description:CADsystemswillinterfacewithoneormoresystems,someofwhichareconsideredmoreessentialthanothers.Factorssuchasagencysize,numberofswornofficers,agencybudget,anduniquecommunityfactorswillaffectwhetheragencieswishtoadopttheseoptionalinterfaces.
5.2UseCaseDiagram(seepage26)
5.UseCaseSpecification:PrimaryTheseCADinterfacesareconsideredtobeessentialforconductingprimarylawenforcementbusinessfunctions.ThefourprimaryCADinterfacesarewiththemessagingsystem,thelocalRMS,Regional/State/NCICWarehouses,andE911.
E911.Thisinterfaceimportssubscriberinformation(ANIandALI)foreachE911caller,asprovidedbythetelephonecompany,intoCAD-compliantentryprocess,eliminatingtheneedforredundantdataentry.Asanoption,theE911datacanbesimultaneouslyimportedintothemappingsystemforimmediatecenteringanddisplay.
Regional/State/NCIC.Querytostate,local,andnationaldatabases.Queriestothestate,localRMS,andnationaldatabaseswilloccurautomaticallyfromselectedCADcommandsusingthemessagingsysteminterface.Inaddition,theoperator(e.g.,dispatcherorofficer)willhavetheabilitytousestand-alonequeryscreens,eliminatingredundantdataentry.Responsestosuchqueriesshouldbestoredwiththecallrecord.
RMS:SeeRMSInterfaces.
AssociatedActor Relationship Description
E911
MessagingSystem
RMS
5.4UseCaseSpecification:AdditionalInterfacesItisoftendesirabletohaveadirectinterfacebetweentheCADsystemandotherkeylawenforcementsystems,suchasotherCADsystemsinthearea,RMSsystems,alarmsystems,andmobiledataterminals.
CADtoCAD.TheCADwillactasapeerinamulti-CADenvironment.TheCADsystemwillacceptanewcallforservicefromaparticipatingCADsystem,inanagreed-uponstructure.TheCADsystemcangenerateandtransferarequestforservicetoapeerCADagency.TheCADsystemlogsallcommunicationbetweenpeeragencies.
MobileDataTerminal(MDT).MobileterminalsinlawenforcementvehiclesprovideanextensiontotheCADdispatchservices.TheCADsystemmustinterfacewithoneormoremobilecommunicationsinfrastructurestowhichthemobileunitsareattached.TheCADsystemcanprovidesilentdispatchorderstoamobileunit,inadditiontoprovidingtheunitwithdetailsofthecallandpremisehistoryinformation.Themobileunitcanchangeitsstatus,queryCADinformation,andquerylocalandnationaldatabases,suchaswanted-personchecks.ThequeriesmaynotgothroughCADbutmaybepartofaseparatemobilesystem.
Interfaces
-
26 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
Locational Systems
Interfaces
Primary
InterfacesUseCaseDiagram
GIS
Additional Interfaces
null
Administration Interfaces
Public Awareness Messaging
Communications Interfaces
Emergency Operations Interface
E911
Prearrival System
RMS
Messaging System
E-Mailing
PagingFaxing
Internet Call Generation
AVL
Real-Time Mapping
Mobile Mapping
Alarms
Push-to-Talk
Mobile Data
External CAD
Reverse 911
Media
Clock Synchronization
Resource Scheduling
System
Emergency Operations
Center
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 27
PrearrivalInstructionSystem.ThecalltakeranswerstothequestionsposedbyaprearrivalsystemarewrittentoCADrecordofthecall.Basedonthecapabilitiesoftheprearrivalsystem,thecalltakermaybepromptedbytheprearrivalsystembasedontheCADcalltype.
Alarm.TheCADsystemcanautomaticallyrecognizeandacceptnotificationofabusinessalarm.Thesystemcoordinatesthealarminputwithakey-holdertopresentinformationtoacalltaker.Baseduponbusinessrules,thecalltakercanacceptthealarmcallandgenerateacallforserviceormanuallyhandlethecall.
RMS.Wheneveracase(report)numberisgeneratedforaCADcallforservice,abasicsetofCADinformationisextractedandtransferredtotheRMSsystemtocreatetheRMSincidentshell.Inaddition,theCADsystemmayinquireintotheRMSdatafiles(e.g.,masternameindex,masterlocationindex,warrants,orprotectiveorders)forinformationthatrelatestothecall.
AdiscussionofthebusinessfunctionsandsituationsthatwarrantCAD-RMSinterfaceisexploredintheLEITSCRMSfunctionalspecification.
AssociatedActor Relationship Description
MobileData
PrearrivalSystem
Alarms
ExternalCAD
Push-to-Talk
5.5UseCaseSpecification:LocationalSystemsInterfacesLocationalsystemsprovideautomatedaccesstoaddress,geographic,andmappinginformationforlawenforcement.TheprimarylocationalsystemsincludeAVL,GIS,andMobileandReal-TimeMapping:
AVL.TheCADsystemwillacceptinputfromanAutomaticVehicleLocationsystem.CADconvertsthevehiclegeographicallocation(e.g.,X/Y/Zcoordinates)toastreetaddress,recordsthevehicleslocationintheunithistory,andautomaticallyperformsachangelocationforthevehicle,ifnecessary.
GIS.InterfacewiththejurisdictionGIStosupportmaintenanceoftheCADmap;thelawenforcementmaplayers,suchasreportingdistricts/areas;andthecreationoftheCADgeofile.
MobileMapping.Dispatchinformationsenttothemobilecanbemappedonthemobileitself.Themapmayprovidetheunitwithdrivinginstructionstothelocation.
Real-TimeMapping.UsingthejurisdictionalGISinformationandthelawenforcementmaplayers,thedispatcherhasatacticalviewofthecityand/ordispatcharea.ThemapcanbecontrolledbyspecificCADcommands,suchaszoom-and-pan,orpresetcommands,suchaszoomingtotheaddressofaselectedcallforservice.Thedispatchercanmap/viewallunitsandopencallsforserviceforanareaorthecity.Unitsandcallsarelabeledonthemap.
AssociatedActor Relationship Description
MobileMapping
AVL null
AVL
Real-TimeMapping
GIS
5.6UseCaseSpecification:AdministrationInterfacesTheAdministrationCADinterfacesassistthelawenforcementteamofunits,dispatchers,calltakers,andcommandinworkingtogether.ThekeyinterfacesincludePush-to-Talk,mastertimeinterface,andResourceSchedulingSystem:
Push-to-Talk.ImportanddisplayinamarqueefashiontheradioID(andoptionallytheOfficerID)informationtothedispatcherbythosekeyingmobileradios.
InterfaceandsynchronizeallserversandCADworkstationswiththeMasterTimeClock.Thisensuresthateachworkstationandserverprovidesanaccuratetimestamp.
ResourceSchedulingSystem.Aschedulingsystemprovidestheabilityfortheagencytoschedulepersonnel,includingcommunicationcenterpersonnelandofficers.ThissystemisoftenfoundintheagencyRMS.
Typically,thesystemhastheabilitytofactorinmanyofthedepartmentalrulesforschedulingpersonnelforregularassignmentsandforovertime.TheinterfacewiththeCADsystemmayincludetheabilitytohaveonepointofmaintenanceforthenamesandassignmentsofallpersonnel.Aninterfacemayalsoincludetheroll-calllistforeachshiftchangefordispatcherreviewandconfirmationasunitslogontotheshift.
-
28 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
AssociatedActor Relationship Description
ClockSynchronization
ResourceSchedulingSystem
5.7UseCaseSpecification:CommunicationsInterfacesThereareseveralcommunications-basedinterfacesthatallowCAD-generatedinformationtobetransmittedtoothersviae-mail,messaging,andtheInternet.
InternetCallGeneration.TheCADsystemwillacceptnondispatchablecallsacrosstheInternet.CallsacceptedacrosstheInternetwillbeofageneralnature,inwhichacase(report)numbermaybeneededforinsurancepurposes.Thecasenumberisgeneratedandrecorded.Thecallisrecordedinthecallsforserviceforstatisticalreportng.
MessagingSystem.ThemessagingsystemisoftenprovidedthroughamessagesswitchthatcanbeinterfacedtotheCADsystem.Themessagingsystemsupportsunit-to-unitmessagingandunit-to-dispatchermessagingviatheMDTsystem.Optionally,themessagingsystemmayalsosupportexternalmessagingtootheragencies.
Paging.TheCADsystemwillautomaticallyperformanalphanumericpageforselectedCADcallsanddispatches.Adispatchermayinitiateanalphanumericpageforanypaginggroup.Theinformationsentinthepageisconfigurablebytheagencybutgenerallycontainsthecallnumber,typeofcall,andlocationofthecall.Thereisanadministrativemechanismtodefinepaginggroups.
Faxing.TheCADsystemwillautomaticallyformatandsendaFAXforselectedCADcallsanddispatches.AdispatchermayinitiateaFAXforanycall/CFS.TheinformationsentinaFAXisconfigurablebytheagencybutgenerallycontainsthecallinformationoralistofopencallsmeetingcertainsearchcriteria.ThereisanadministrativemechanismtodefineFAXgroups.
E-mailing.TheCADsystemwillautomaticallyformatandsendane-mailforselectedCADcallsanddispatches.Adispatchermayinitiateane-mailforanycall/CFS.Theinformationsentinane-mailisconfigurablebytheagencybutgenerallycontainsthecallinformationoralistofopencallsmeetingcertainsearchcriteria.Thereisanadministrativemechanismtodefinee-mailgroups.
AssociatedActor Relationship Description
Paging
Faxing
E-Mailing
InternetCallGeneration
MessagingSystem
5.8UseCaseSpecification:PublicAwarenessMessagingPublicawarenessmessagingistheabilitytobroadcast,publish,andsendmessagestoindividualsoragenciesthatneedtobeawareofcriticalevents.ExamplesincludeAmberAlert,criticalincidentoccurrences,utilities,transportation,hospitals,orthepublicatlargeviatheInternet.
Reverse911.Thiscapabilityistypicallyapartofthetelephonesystemusedinthecommunicationcenter.Thesystemmaintainsalistofallcallerswhohaveelectedtobeapartofthiscommunityalertsystem.Aninformationmessagecanbecreated.Thesystemthencallseverypersononthelistandplaysthevoicemessage.ThereisusuallynotactuallyaninterfacebetweentheCADsystemandtheReverse911systemunlessthecalllistismaintainedintheCADdatabase.TheWebinterfaceisanoptiontoprovidecitizenswiththeabilitytoaddtheirnametothecalllistfornoncriticalincidents.
AssociatedActor Relationship Description
Reverse911
Meda
5.9UseCaseSpecification:EmergencyOperationsInterfaceTheoperationofanemergencycenterrequiresthemultidirectionalexchangeofinformationbetweenCADandEOC.UnitsmaybeassignedtotheEOC,atwhichpointtheEOCwilltakecontroloftheunituntilreleased.CADwillmaintaintheabilitytomonitortheunitavailabilitystatus.CADwillcontinuallyupdateEOCwithcallinformation.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 29
AssociatedActor Relationship Description
EmergencyOperationsCenter
5.10AdditionalBusinessFunctionsTheCADsystemshouldhavethecapabilitytocommunicatewithoneormoresubsystems(i.e.,EMSDispatch,FireDispatch,and/orIntelligentTransportation).Itiscommonforexternalagenciestobecomeinvolvedinalawenforcementcallforservice.Reasonssuchasagencysize,numberofswornofficers,agencybudget,anduniquecommunityfactorswillaffectwhetheragencieswishtocommunicatewithexternalsubsystems.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems 31
6LEITSChadamissiontocreateanationalstandardforlawenforcementCADsystemsandhassucceededincarryingoutthistask.
TheCADfunctionalstandardsaremeanttodescribetheminimalamountoffunctionalitythataCADsystemforlawenforcementshouldcontain.ThesestandardsshouldbeusedasastartingpointtobuildafullyfunctionalCADsystem,basedonagencyneedsandopenstandards,toefficientlyinterfaceandshareinformationwithothersystemsbothinternallyandexternally.TheyaredesignedtoserveasaguidingtoolforlawenforcementagenciesandshouldbetailoredtofitthespecificneedsofeachlawenforcementagencyorgroupofagencieslookingtoupgradeorpurchaseanewCADsystem.AlthoughtheCADfunctionalstandardswerenotdevelopedtosubstituteforanRFP,theycanbeusedtosupplementanRFP.
Conclusion
Thefunctionalstandardsfoundinthisdocumentareintendedtobegenericinnatureanddonotfavoroneparticularsystemorapproachoveranother;theyareatthefunctionallevel,meaningthattheydefinewhatistobeaccomplishedversushowitshouldbeaccomplished.
TheCADfunctionalstandardsweredevelopedbytheLEITSCFunctionalStandardsCommitteeandarenowavailabletoalllawenforcementagencies.
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems A:1
Alert/NotifyUnitsThedispatcherwillrelayinformationpertainingtocallsforservicetotheappropriateunits.Thisnotificationhasthepurposeofinformingandraisingtheawarenessofdesignatedteamsorallofficers.
AssignCallClassificationandPriorityAssignnaturecodethatmayincludegeneralclassificationandsubtypesofthecallbaseduponagencypolicy.
Thecallwillbeprioritizedbasedupontype,applyingestablishedguidelinesandprocedures,todeterminetheappropriatedispatchandresponseneeds.
AssignRMSIncidentNumberInadditiontotheCADCFSnumber,anRMSincidentnumber(casenumber)maybeassignedbeforethecallistransferredtotheRMSsystem.Thismayhappenatanytimepriortosendingthereportbutmostlikelyafterthedeterminationthatitwillbesent.TheRMSnumbermaybeassignedfromadatafileofincidentnumbersmaintainedintheCADsystemincoordinationwiththeRMSsystem.DepartmentpoliciesinthisareamustbesupportedbytheCADsystem.
AssignUnitsThedispatcherwillassignaCFSandrelaypertinentinformationtotheappropriateunitsinthefieldforthepurposeofdispatchingaresponder.AnoptionalMDCinterfacesupportsthisactivity.
AssignedbutavailableunitsmaybepulledoffofcurrentassignedstatusbasedonprioritylevelsandtheresourceneedsoftheCFS.Ifalltheunitsarepulledoffofacall,thecallwillbeaddedbackintothedispatchqueue.
CaptureLocationInmanyinstances,thecalltakerhasaccesstothecalloriginationlocation(ALI/ANI)datausingthe911system.
Ifnot,theCFSlocationmustbeelicitedfromthecaller.Insomeincidents,thecallerslocationmaynotbethelocationofthecallforservice.
CheckforDuplicateCallsThesystemautomaticallyevaluatestheCFSlocation(andpotentiallyothersiteparameters)todeterminewhetheracallisaduplicate.Thecalltakerevaluatestheinformationpresentedbythesystemwiththatobtainedfromthecallertomakethefinaldecisionregardingduplicatecalls.CallsforservicemaybereceivedbymanysourcesforthesameCFS,suchasatrafficaccidentwitnessedbytwoormoremotoristsorafirealarmreportedfromanelectronicmonitoringsystemandawitnessreportingsmokecomingfromabusiness.Thecallmaybedeterminedtobeunique,butthereshouldbeacapabilityoflinkingthecalltoanotherexistingcall.
ThisanalysiswilldeterminewhetheranewCFSisrecordedinCADoranexistingCFSistobeupdatedwithinformationnotyetcaptured.
CorrelatetoSectorThelocationinformationobtainedfromthecallerandverifiedbythegeofilewillbecheckedtoidentifythepatrolareaassignmentinwhichthecallislocated.
CreateCallforServiceAnewcallforserviceisrecordedinCADusinginformationcompiledtodate.Auniquecallnumberisassigned.
DetermineCallStatusTheCFSwillremainopenandmonitored.ThestatusoftheCFSmaychangeasthesituationisresolved.TheoptionalMDTinterfacewouldallowtheofficetoenterCFSdisposition.
AAppendix
Properties:Activity
-
A:2 StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems
DetermineDispatchNeedAdecisionismadetodispatchaunitordirecttheCFSfordisposition.
DetermineProximityofResourcesResourceproximitycanbebasedonaclosenesscalculation,whichcanbedistanceordrivingtime.AnyunitsuggestionmustrespectdispatchcontrolareasanddepartmentalSOP.ProximitydeterminationcanbesupportedbyanoptionalAVLinterface.
DetermineReportabilityCFSmayvaryintheneedtoreportbeyondtheCADsystem.Guidelinesaredefinedbytheagencypolicybaseduponacombinationofcalltypeandcalldisposition.
DetermineResourceAvailabilityAvailableresourcesaredisplayedbaseduponunitstatus,whichincludesunassignedaswellasassignedwithalowerprioritystatusofcalltowhichaunitisassigned.TheunitsmaybecurrentlyunassignedorassignedtoaCFSwithadesignatedtypeandprioritylevel.Unassignedunitsareavailabletobedispatched.
DispatchResourceDecisionRecommendedresourcestobeassignedbasedonSOP,whichfactorworkload,unitcapabilitywithregardtoskillsandequipmentrequiredfortheCFS,unitavailability,andtheproximityofresources.
DisplayAdditionalCFSDataAsadditionalinformationismadeavailable,thedispatcherwillbealertedandhavetheabilitytoviewthenewinformation;forexample,anyinformationenteredbyacalltakeroranotherdispatcher.
DisplayCFSDataTheCFSwillneedtobedisplayedandmonitoredthroughCAD.Thisincludesactivitiessuchasadditionalcallinformationandactivitiesreportedbytheofficers.Immediateaccesstoallopencalls(includingunassigned)shouldbeprovidedontheCFSstatusdisplay.Whenacallisclosed,itwillautomaticallyberemovedfromthecalldisplay.
DisplayUnitDispatchStatusThecurrentstatusofunitswillbeavailableatalltimes.Thedisplaywillindicatetheunitsstatusandassignedcallsforservice(ifany).Thedisplaycanalsoshowthelocationorlastknownlocationoftheunit.IntheabsenceofAVL,thelocationmaybethecurrentcalllocation,thelastcalllocation,orthelocationenteredbythedispatcherorMDC.Inthecaseofassignedunits,thedisplaymayshowanyalerttimer,theCFStype,andpriority.
Examplesincludearrivedonscene,available,unavailable,andunavailablebutassignable.Morestatustypesshouldbeconfigurable.
EnterSupplementalServiceRecordArecordofsupplementalservicerequestisestablishedtoreflecttheinstanceoftheselectionfromtheservicerotationlist.Thistriggerstherotationtothenextresourceintherotation.Therotationoccursregardlessoftheresourceabilitytorespondtotherequest.
MaintainStatusInformationiscontinuallydisplayedinCADtoreflectthecurrentstatusofunitsthataremonitoredbythedispatcher.
NotifySupplementalResourceServiceThesupplementalresourcewillbecontactedtoprovidedispatchinformationbythedispatcherandwillbeprovidedinformationabouttheincidenttowhichtheyarerequestedtorespond.Theavailabilityoftheservicetoprovideserviceswillberecorded.Asupplementalservicethatcannotbecontactedorinformstheagencyoftheirinabilitytorespondwithinaprescribedtimeisconsideredunavailabletoprovidetheservice.Asupplementalresourcewillbeselectedfromthelistuntiloneisfoundthatisavailable.
OverrideResourceRequirementTheinitialrecommendationbaseduponknowncriteriamaybeadjustedbaseduponadditionalinformationthatbecomesavailable,suchaslearningthatthesuspectisknowntobearmedanddangerous.Overridemustberecorded.
PlaceCallonUnassignedStatusTheunitisreassignedtoanewcallandautomaticallyunassignedfromthepreviouscall.
ReassigntoAvailableWhenaunithasclearedfromasceneandisnolongerassignedtotheCFS,theunitwillbereassignedtoanavailablestatus.DatareceivedfromMDCtransmissionsmayupdateCADandreflectthenewstatusoftheunit.Theunitmayremainonsceneandhaveanavailableon-scenestatus.
RecognizeAcknowledgementTheunitassignedtothecallwillrespondtothedispatchertoconfirmreceiptofthedispatchinformation.Thismaybedonebyvoicecommunicationorthroughmobiledatacomputers.
RecordArrivalonSceneUnitsrespondingtothescenecommunicatetodispatchthattheyhavearrivedatthelocation.ThiscommunicationmayoccurverballyorthroughanMDCtransmissionthat
-
StandardFunctionalSpecificationsforLawEnforcementComputerAidedDispatch(CAD)Systems A:3
mayautomaticallyupdateCADtoreflectthecurrentstatusoftherespondingunit,includingtimeofarrivalonscene.
Theremaybeaneedtorecordmultiplearrivaltimes;anexamplewouldbethearrivalatthelocationandanotherarrivalatthescene.Forexample,aunitmayarriveatthelocationofahigh-risebuildingandatalatertimewillarriveatthescenelocatedwithinthebuilding.Thesystemshouldprovideforthesettingofdifferenttimersbasedupontimeofarrivaltype.
RecordCFSActivityTheCFSrecordwillbeupdatedtoassociatetheunitorunitsdispatchedasrespondingunitstothecall.
RecordDispositionRecordthedispositionofthecallforservice.Thismayincludeanarrativeinadditiontothetypeofdisposition.
RecordUnitActivityTheunitstatuswillbeupdatedtoassociatethedispatchedunitorunitswiththeCFS,includinglocationandtime.
RecordUnitLocationAnychangeinunitlocationiscapturedalongwithtimestamps,includingchangesoflocationassociatedwiththesameCFS.
ReopenCFSAnexistingCFSisreopenedforupdate.Changesaretracedforauditpurposes.
RequestSupplementalResourceAlawenforcementofficialrequeststhatasupplementalresourceservicebedispatchedtoaspecifiedlocation.
RetrieveAlarmLocationObtainthelocationofanelectronic-generatedcallfromthecallsourceinformation.LocationandcontactinformationfromelectronicsourcesmaybereceivedfromdataexchangestoCADormaybeobtainedfromadatabaseofcommonaddressesmaintainedbytheagency.
RetrieveCFSFromCallPendingQueueThenextCFSonthec