Allow Fire MPS client application to 'Relocate' unit to another station
Name/Agency Point of Contact
Brien Foss - South Sound 911
Version of EdgeFrontier
The attached system's intent is to allow the Fire MPS client to relocate the currently logged in unit, to another 'station'.
The 'Home' button will relocate the unit back to their defined home/base station.
The 'Relocate To:' button will allow the user to select a station from a customizable list (options file). This options file is hardcoded and created with the same structure as any other pre-existing options file.
The data we chose to put into our options file came from the table LIVE_930.dbo.def_station (columns 's_name' and 'station').
The act of choosing a station to relocate to, in MPS, will send a CAD 'message' to the CAD Comm Server. The message is picked up by the EdgeFrontier RelocateUnit system attached to this forum post. The EdgeFrontier system will then request a more detailed 'message report' using the IFCAD Command - IFCADRequestMessageReport. The system will then listen for, and capture the results of that IFCADRequestMessageReport, and parse the parameters needed to then perform the IFCAD Command - IFCADUnitRelocate. Utilizing this command will cause the CAD system to perform the relocation of the unit.
[ ] - As a first step, please view the pages in the attached PDF for an overview of the structure of the process, and the order of operations.
[ ] - To install this system, login to the server hosting your EdgeFrontier Engine. Copy the included RelocateUnit.EFE file to the desktop. Double-click the EFE file, and it will load the new system into the EdgeFrontier Engine.
[optional] - I've also included the XML file in case you want to manually add it to your list of systems, typically located @ c:\ProgramData\Intergraph\EdgeFrontier\Engine\Systems.
If you do this however, you'll also need to add XML to your Systems.xml file, typically located @: c:\ProgramData\Intergraph\EdgeFrontier\Engine.
List of items that were needed to be changed/added to complete this functionality:
[ ] - Modify forms\HomeStatus.html, to add buttons for relocation, using and adding new UseCases (PublicSafetySendMessageRelocate, PublicSafetyRelocateTo)
[ ] - Modify oneshots\RelocateMsg.htm, to only serve the purpose of calling the SendMsgRelocate() with the parameter "HOME"
[ ] - Create a new form (forms\RelocateTo.htm) to use a dropdown list, form validation, a newly created Options file with station listings, and call function SendMsgRelocate() with the chosen dropdown value.
[ ] - Modify function SendMsgRelocate() to build the expected string that the EdgeFrontier system is expecting to parse.
[ ] - Move function SendMsgRelocate() to a common location of scripts\publicSafety.js
[ ] - Create EdgeFrontier user in CADDBM
[ ] - Associate message group to EdgeFrontier user
[ ] - Create EdgeFrontier system (RelocateUnit)
[ ] - Modify ListenerNotificationsService.exe.config file, to include CadChangeNotifications of MessageData, MessageReceiveData
Please reply back to this forum if you have any questions, we will be happy to help!
If I'm understanding this correctly, the system you posted really could be used for several purposes where you want to send a message from MPS or I/Dispatcher and have the EF System react. Is that a fair statement?
As you can see in the structure of the message sent through the system, we are actually passing delimited strings that our EdgeFrontier system is expecting to parse and 'do something' with.
This granularity allows for very powerful possibilities as EdgeFrontier is also capable of working with assemblies, web services, databases, etc.. Once you have a handle on an assembly, the opportunities for additional functionality elsewhere is essentially endless.
Add a Comment
Please sign in on the right menu to comment.
If you do not have an account, please Join now.