[0:00] Mr. Jotham Kildea ICONICS Solution Supervisor
I think Megan's going to join us. And we're going to answer some of the questions that came in. Again, that's on the app in Attendee Hub. Thank you.
[0:15] Ms. Megan Courtney ICONIS Marketing Coordinator and Social Media Specialist
Hello, everybody. Jotham. Josh, fantastic presentation, as usual. So, we did receive a few questions. The first one: “Is remote acknowledgement of notifications always tied to a mobile device or can it be handled independently?”
[0:33] Jotham Kildea
Oh, sure. So, for remote notification, anybody not in a traditional SCADA screen environment absolutely can be handled through other things for example as I mentioned, SMS. There's acknowledge code that as a user, you can plug it in and just respond to an alarm. And that handles an acknowledgement. Same thing effectively for voice and email. Even you can do the same thing as far as emailing responses. So that frequently can be a quick thing. It doesn't always involve the mobile interface. A lot of times, applications just go the route of “Hey, I got a text message. I can respond in just quick few seconds”.
[1:07] Megan Courtney
Right. Our second question that we received is “What do we have to be concerned about if we have to comply with GDPR?”
[1:15] Jotham Kildea
Yeah, so I mentioned this a little bit in the session, but GDPR is very concerned with making sure that personally identifiable information is that they've opted in or authorized the use of that information, and it can be removed from the system at will. So, a lot of what CFS WorX is doing is a kind of an anonymized actor ID that says, “Here's a generic user”. It doesn't actually personally identify people. We use that for a lot of transactional information of “who do we contact and how”. So that is separable from the personal information because a lot of times when you're deploying a system, if you're configuring it, you want to know, “Okay, I'm sending a message to Josh, not user 1278”. But under the hood, those things are entirely separable. And that's a good way to make sure that if you decide to remove, for example Josh, you remove his system, it's going to be decoupled from any personally identifiable information.
[2:10] Megan Courtney
All right, our next question, “Does CFS WorX require that there's some dispatcher making the decisions about who to notify?”
[2:20] Jotham Kildea
No, no. So, in the demo that we showed you that Josh was running, we used the example of a dispatcher dashboard. That's absolutely one way we see some applications go where they have somebody that's actually making the decisions of, “Hey, this notification is going out to this person.” You can go that route. You can also very commonly go with the automated dispatch with no humans in the middle; it just sends notices out to a predefined queue of workflow of users. For example, Lake Cities does that since they don't have a lot of in-person staff that are onsite all the time. They mostly have remote workers, so they just automatically dispatched to who needs to be informed.
[3:01] Megan Courtney
Awesome. Next one, “Can we get worker location data from other sources if there are privacy limitations to getting it directly from an app?”
[3:12] Jotham Kildea
So, privacy, do you want to feel that, Josh?
[3:19] Mr. Josh Opal ICONICS Senior Software Engineering Supervisor
What I mentioned in the demo was that you can get the “Locate Worker Location” from the ICONICS MobileHMI app. There are also third-party apps. But typically, we're going to be getting the worker location from their cell phones which might be running the ICONICS MobileHMI app or a Dynamics or Salesforce app that's communicating back to their server. So there has to be something collecting information about where the worker is located, transmitting it back to some server so that our server can make the determination of who's closest and who needs to receive the notifications.
[4:06] Jotham Kildea
And to be clear: That the MobileHMI is an opted-in type of deployment for that. It’s not secretly tracking where you are. It's something you've configured and enabled to expose that information for the system.
[4:17] Megan Courtney
So, looks like we have one more question, “You mentioned Managing Schedules - is that something that's done on a per user or group basis?”
[4:27] Jotham Kildea
It depends. So, Josh showed a little bit of the dashboard where you can configure the schedule environment from that space, and it really depends on the application. For some folks if it's a smaller system, they might just say, “Hey I've got eight workers. I can configure everybody's schedule. I know when they go on holidays.” It's individualized. Or you might have a broader model where it's kind of like a first shift, second shift or who's on call at certain times. You can go either way. Obviously, a group schedule is going to be easier to shift and adjust at scale, but the personalized approach of individualized schedules really gives you that free control. As I said, I typically see that with smaller applications where it’s much more of a personal interaction where they're going to say, “Yeah, I can cover that shift, or I can do these different times or someone's on vacation”. And you can adjust it very finitely.
[5:18] Megan Courtney
That was it for questions. Thank you.