What issues of existing products does SCADA-Aware Mobile solve?
- Unreliable message delivery
- No location awareness of support personnel
- No support for peer collaboration
- No support for automatic, intelligent escalations
- Minimal security
- Limited event auditing
Without getting into technical details, tell me why I need SCADA-Aware Mobile
- It saves you time, labor, and money
- It makes life easier for you and your personnel
- It fosters collaboration, and at the same time eliminates unnecessary actions
- It mitigates risks to your company’s profitability, reputation, and personnel’s safety
How is SCADA-Aware Mobile more reliable?
SCADA-Aware Mobile is more reliable than other alarm delivery products and methods for the following reasons:
- Unlike SMS or e-mail alarm delivery, SCADA-Aware Mobile does not depend on third party services for which performance guarantees are not available.
- Unlike SMS or e-mail alarm delivery, a SCADA-Aware Mobile client positively and promptly confirms to the server than an alarm update has been successfully received.
- Unlike voice, e-mail, or SMS-based alarm delivery, a SCADA-Aware Mobile client application lets the user know when alarm updates won’t be received as expected, enabling the user to take action to resolve the problem.
- The SCADA-Aware Mobile server application will raise and deliver an alarm when a user is unable to receive alarm updates, something SMS and email delivery systems cannot do. The server processes and delivers such an alarm exactly like one received from the SCADA system.
- The SCADA-Aware Mobile server will raise and deliver an alarm when a problem occurs that negatively impacts alarm processing and delivery. Examples of such problems include loss of connectivity to the SCADA system, loss of connectivity to the historian, or an alarm that could not be delivered to any user.
How will SCADA-Aware Mobile save me money?
- By making sure the right person gets the alarm at the right time, thereby minimizing the number of trips to the site
- By eliminating duplicate responses using GPS-based message delivery and peer visibility of alarm acknowledgment. Your personnel won’t get distracted unnecessarily, and it will save on overtime and vehicle gasoline cost
- By enabling the engineers and technicians to access – through their mobile device – current, historical, and related SCADA data, and thus helping them make better and faster decisions
- Through management visibility. Managers can also get the alarm and see operational status, and coordinate the resolution efforts if needed
- By using less equipment – your field or technical personnel will not have to carry a laptop to access data
- By better utilizing your personnel – no need to keep someone in front of the central monitor all the time
- By saving on repair and clean-up costs
- By avoiding lost production or sales
- By ensuring regulatory and procedural compliance through complete alarm life-cycle audit
Why can’t we just use SMS and pagers?
SMS and pagers have the following problems:
- Lack positive message acknowledgement/accountability
- Delivery success and time can be inconsistent
- Limited content (message size and unstructured text)
- Must acknowledge using a different device and/or application, thus hindering collaboration
- Must use another device or application to research the alarm. No easy way to interact with the SCADA system and no real-time query
- Does not use GPS to determine notification recipients
- Understanding the overall situation requires reviewing multiple messages to construct a mental model
How is SCADA-Aware Mobile better than browsers?
- Browsers require you to be connected to the Web to see the SCADA data. With SCADA-Aware Mobile, you get historical and related data on the phone, and it stays on the phone even if you get disconnected. Unreliable network becomes less of an issue.
- Browsers can’t use GPS to check your location. SCADA-Aware Mobile can.
How does SAM provide more “actionable awareness” on alarms?
- The Client receiving an alarm will ALWAYS generate an automatic positive acknowledgement to the server, an event recorded in the audit log.
- The Event Server records in the audit log each time an alarm update cannot be promptly delivered to a Client.
- If the Event Server detected that an alarm cannot be delivered to any Client, the server generates a system alarm that is normally configured for delivery to supervisory team members. The audit log contains a record of each of these system alarm events.
- Default reports provide detailed information on each alarm’s lifecycle. For example, if an alarm arrives from the event source at 1:20 p.m. and is acknowledged by someone at escalation level 3 (the highest level) at 3:47 p.m., a customized report can be generated showing for that tag that contains the following information.
– When the alarm arrived at the Event Server from the underlying event source
– When the Event Server delivered the alarm to escalation level 0 recipients
– What time the Event Server escalated the alarm from level 0 to 1, 1 to 2, and 2 to 3
– Which users were supposed to receive the alarm at each level of escalation
– Who actually received the alarm at what time
– Who acknowledged the alarm and when
– Which users were supposed to receive the acknowledgement update
– Which users actually received the acknowledgement update
– When the underlying event source informed the Event Server that the alarm returned to a non-alarm state
This level of detailed reporting enables managers to examine the effectiveness of his or her team in responding to alarms. Overall, the detailed alarm history created by the SCADA-Aware Mobile server contributes to the reliability of the entire solution, and gives relevant personnel important control over, and awareness of, system performance.
Give me a real-life example of how SCADA-Aware Mobile could help me
An alarm goes off! John Smith, the on call field service engineer, gets the message, “Tank 2 at critical level”! “Why did that happen?” He wonders. “What’s wrong? Now I have to drive all the way over there and it’ll take me 30 minutes! I wonder if I need Jerry to fix the problem? What is the problem?”
SCADA-Aware Mobile helps solve his problems. When he gets the alarm notification, he can query related tag values as well as historical information right from his smartphone. Related tags indicate the skillset required to address the alarm. Historical data will provide a level of urgency depending on how quickly the threshold values are changing. With this additional information, the alarm can be acknowledged and informed next steps can be determined (including who else to contact, if needed). Other individuals who received the alarm notification will get an update of who has taken ownership of the event.
Sending a field service engineer on site is costly to the organization. SCADA-Aware Mobile helps minimize the number of trips to the site, improves on the accuracy of the skillsets needed to resolve the issue, and reduces the organization’s overall cost. Reducing these risks also improves the safety for the impacted employees.
How does the ownership visibility help?
How will SCADA-Aware Mobile help me with unreliable network connection?
- With SCADA-Aware Mobile, you get historical and related data on the phone, and it stays on the phone even if you get disconnected. Unreliable network becomes less of an issue
- If you get disconnected from the network when your mobile device should be available to receive alarms, SCADA-Aware Mobile sends out an alarm so that your peers and manager become aware of the situation. Also, your own device notifies you that you’re not in a position to receive alarms
How does the push-pull technology work?
If the server cannot “push” the notification alarm to the right person’s mobile device, then the device will “pull” it from the server. The mobile device checks with the server for alarms in defined time intervals. This technology is based on the patented capabilities of Voyager, our middleware software.
How does the GPS-based alarm delivery work?
For each possible tag group or user group, a geo-fence can be defined (for example, a 5-mile radius around the event location). When that alarm goes off, designated personnel within that geo-fence get the alarm. If none of them acknowledges the alarm, then, after a defined time-period, the alarm escalates and goes beyond the geo-fence. This ensures faster response and eliminates duplicate action. However, if the manager of the designated personnel (for that alarm) wants to see the alarm even if (s)he is outside the geo-fence, that can be configured into the system.
The GPS-based message delivery and peer visibility of alarm acknowledgment ensures that your personnel won’t get distracted unnecessarily, and it will save on overtime and vehicle gasoline cost.
SMS, Pagers, laptops, and browsers don’t use GPS (location awareness) to determine notification recipients.
What happens when the intended person does not respond to the alarm?
What data can the alarm recipient view through his mobile device?
How are things actually automated through SCADA-Aware Mobile?
- When an alarm goes off, someone in the control room doesn’t have to make any calls. In fact, no one has to man the control room all the time to check if there’s any alarm, or anything that requires the generation of an alarm.
- When someone acknowledges the alarm, his peers and manager can see it automatically and thus know who “owns” the alarm now
- The system does automated monitoring of devices that should be available at a given time to receive alarms. If such a device that should be available is not, then, after a configured time, the system sends out an alarm, and the device also notifies the user
- If no one acknowledges the alarm, it automatically escalates to the next level. There are three levels of escalation after the initial alarm
What happens if I don’t log out?
Once logged-in, you can stay so indefinitely. Even if your device is turned off, you’ll be considered logged-in. However, if your device is not available to receive alarm when it should be available (for example, it’s turned off or you’re outside the geo-fence or network), an automated alarm is sent out.
What information is recorded following the alarm for audit purposes?
SCADA-Aware Mobile provides complete alarm life-cycle audit. The following are recorded in the database, and could be seen from both desktop editor and smartphone:
- Tag entering an alarm state
- Time the alarm was sent to a device
- Time when the alarm was received by the device
- Who acknowledged the alarm and when
- Time an alarm escalated
How are redundant servers handled?
We utilize Microsoft’s Windows Server Failover Clustering (WSFC) functionality. This provides local high availability through redundancy at the server-instance level—a failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
How is unreliable network coverage handled?
We review the coverage by different carriers in a given area. If we find significant coverage differences between carriers, we suggest remedial actions, such as power/carrier boosters for vehicles. Small pockets with no coverage is not a big issue for SCADA-Aware Mobile. Usually it only needs edge network capabilities to connect. Since the amount of data transmitted for SCADA-Aware Mobile is usually small, the connectivity window does not need to be long. It’s different from e-mail/web browsing, which often does not work reliably and transmits much more data.
How is the mobile device and user authenticated?
When the user launches the client, they are prompted for a username and password. This can be authenticated against an OpenLDAP / Active Directory server. The username and password can alternately be locally authenticated in the application and stored in the event server’s database. If this method is chosen, the password is stored in encrypted form. Transmission of password information does not occur in clear text.
While the device id is transmitted, it is not used for authentication purposes. The device id is used to distinguish devices when the user is concurrently logged in.
Will I have to change my existing SCADA system to implement SCADA-Aware Mobile?
No. Existing SCADA systems don’t need to be changed.
Recursion will, however, need to update the SCADA database to incorporate our one-button acknowledgment.
How is tag info transferred to the SCADA-Aware Mobile system?
Bulk import done during commissioning and startup.
How does SCADA-Aware Mobile handle long tagnames?
By grouping or aliasing the tagnames.
What OS/platforms does SCADA-Aware Mobile run on?
For smartphones – Blackberry (OS5 and OS6), iPhone (iOS 5) and Android (OS2.2 or greater). For PCs, any PC with Windows XP SP3 or newer operating system.
What smartphones does SCADA-Aware Mobile cover?
Blackberry, iPhone and Android
How do you sell SCADA-Aware Mobile?
We sell licenses for Event Servers, Secure Proxy Servers and Client Access Licenses (CAL). The Client Software is free and can be installed on ANY number of mobile devices or Windows desktop devices. One Client Access License (CAL) allows ONE user to log in to the SCADA-Aware Mobile system on ANY two devices at the same time (For example, a user’s mobile device AND his/her Windows desktop device).
For more on pricing options or to ask for a quote, please call or write to us.
What type of customer support does Recursion provide?
At Recursion Software, our goal is to deliver software that meets or exceeds established standards of performance and quality to help our customers achieve their business objectives. Our customer support program is designed and implemented with this goal in mind.
Hotline: M-F, 8:30am-5:30pm CST. (972-731-8800, firstname.lastname@example.org)
Incident Reporting: When a customer reports an incident it is logged into the Recursion Software Incident Tracking system and an incident number is generated. Based on the incident type and severity, the customer can expect regular status reports for the duration of the resolution process.
Incident Handling: Depending on the assigned severity level, the incidents will be handled through immediate or same day action, short term resolution, resolution in the next Minor Release, or resolution in a Major Release.
Incident Escalation: When escalation of the incident is required, the customer can contact the Customer Support Engineer assigned to the problem and request escalation. Afterwards, if required, the customer can request to speak with the Director of Customer Support Engineering.
Product Enhancement: If the customer requests an enhancement to a Recursion Software product, Recursion Software Customer Support Engineering will work with the customer to clearly define the proposed enhancement and prepare a development plan. Each enhancement will receive a priority of 1, 2, 3, or 4. Enhancement requests are reviewed internally for possible inclusion in the next release of the software.