CrewSense

            Emergency Reporting Integration

            Video Tutorial available here, click here

            CrewSense directly integrates via an API (application programming interface) with Emergency Reporting. The integration will allow you to perform scheduling within CrewSense, and have that data reflect automatically within the Emergency Reporting 'Rosters'. This is useful for report writing, as you will only need to perform data entry in one location (CrewSense).

            How to Sync:

            To sync the CrewSense platform with Emergency Reporting Systems, simply click System Settings -> API / Integrations and click on the Emergency Reporting logo. From there, you will need to provide an administrator level login to securely grant CrewSense access to your Emergency Reporting system.


            Once you've done that, you have successfully linked your CrewSense platform to the Emergency Reporting system! Now, you need to set up the field Mapping, so we know exactly what to update in the daily ERS rosters:



            Step 1:


            Pair Users


            We'll need to know who is who in each system, so we must map the users. You can click the 'Try Guessing' button to have the system algorithm best guess the matches. Then, if you need to change them, simply manually change them.


            Pair Stations


            The next step is to pair the 'Stations' from Emergency Reporting to the CrewSense Scheduler Groups. If you do not have Scheduler Groups already built in the CrewSense system, please follow the steps here to do that first before proceeding. The Station field in ERS should match the CrewSense Assignment Groupings. Once done, Pair the Stations in ERS to Assignment Groups in CrewSense.


            Pair Apparatus


            The final step is to pair the ERS apparatus with the correct Crew Scheduler assignment. The ERS apparatus field should match the CrewScheduler assignment(s) name. In other words, if you have Engine 1 in ERS that is populated with employee names in the daily roster; but have the same assignment called 'Station 1' in CS populated with employee names...you'll need to make sure and map them correctly. It is easiest if the names match, but so long as you map them appropriately, it will be okay.


            Pair Roster Positions


            If you want Roster Positions to carry over to ERS, you will need to setup CrewSense Qualifiers. Once you have set those up, you can pair them to Roster Positions in ERS.


            Activity Codes


            You can send activity code data to ERS by setting up Work Codes for each Work Type in CrewSense. To setup a work code, go to System Settings - > Work Types. Add a work code for each work type. That field will carry over as the activity code in ERS.


            Important notes:

            CrewSense Assignments should equate to ER Apparatus 

            CrewSense Assignment Groups should equate to ER Stations

            The sync is 'one way' only. Only data can be pushed to ERS. Data cannot be retrieved from ERS

            The CrewSense -> ERS sync occurs automatically every 15 minutes. The update is not real-time, rather on the quarter hour.

            CrewSense will generate a new Daily Roster in ERS if one cannot be found already, and it will simply update today's and tomorrow's (2 days worth) ERS Rosters with your CrewScheduler updates. Only ERS rosters created / modified within the last 10 days can be 'seen' by CrewSense. For the sync to work, the current day/tomorrow's roster should have been created in the last 10 days.


            Once you've made a change in the CrewScheduler, those changes will be reflected in your ERS roster(s).


            Daily Notes / Activities will sync to the ERS roster; as will CrewScheduler Work Types / Codes.


            You do not need to add the employees in, but rather just make sure the Stations and Apparatus are setup correctly. The CrewSense sync will do the rest.


            Updated: 02 Aug 2019 05:54 AM
            Helpful?  
            Help us to make this article better
            0 3