TeleCont

1. TeleCont A short description of the application

2. Presentation topics • TeleCont features • Users and permission levels • Sending commands to field devices • Receiving alarms from field devices • Transferring alarms to end users • Field device settings (maintenance) • Customization and various logs • Information security • Starting using TeleCont

3. What Can I Do with TeleCont? • Management of remote control and monitoring units operating in GSM network • Solves many problems related to the maintenance of field devices • You can easily manage complex systems with large number or field devices (traffic signs, holiday homes, etc...) • You can have many users operating the same device with differing access rights • Provides a graphical view of your field devices • Alarm transfer • Offers an alternative route for transferring alarms to users (phone call and GSM Short Message) • Confirms the alarm message coming directly from the field device to the end user • Sending commands • Provides a graphical user interface for controlling and commanding your devices • Other field devices • The system works with other devices besides TeleControl • The system is extensible • History is preserved • Received measurements and alarms are logged • Sent commands and field device setup changes are logged • Problem situations can be analyzed afterwards • Works on the Internet • Serves a geographically distributed group of people • One field device can answer to the varying needs of different people • ASP or local deployment • You can start using TeleCont easily without installing software • You can add capacity (new devices, new users, etc…) to TeleCont incrementally depending on your needs

4. TeleCont Features • Management of remote control and monitoring units operating in GSM network • Alarm transfer to end users • Sending commands to field devices • Not limited to TeleControl devices • History is preserved • Web browser based • Telemic can host the application (ASP)

5. Users and Permission Levels • To sign in to the system you must provide • a customer name, • your user name, and • your password • A user always belongs to a customer • Permission levels • Operator • Management of customers • Management of device templates • Administrator • Main user for a group of users • Devices, alarms, and reports are customer specific • Each customer must have at least one user with administrator rights • User • Normal user with limited permissions • Cannot change field device settings • Permissions are user specific • You can see if other users from your group are currently using TeleCont

6. Browsing and Sending Commands • The devices and IO-points are listed in a hierarchical tree structure • Points are always of a certain type • You can create your own point types • Point type determines the icon, time-outs, maximum measurement values, and the behaviour of a particular IO-point (BinIn, BinOut, AnaIn, AnaOut) • Sending commands • View of the received measurements • Command and alarm log • Timed commands • Lists and reports • Integrated help (Demo: general look of the application)

7. Alarm message is received. Message saying that alarm state has gone off is received. User acknowledges the alarm. User sets the alarm off. InputAlarmHi, InputAlarmLo AlarmIsNew Alarm Receiving Alarms • A TeleCont’s IO-point triggers off an alarm by • Measurement threshold values • Lack of command acknowledgement • Alarm state is displayed in the top portion of your web browser window and highlighted in red in point lists and alarm log • Alarm transfer option • Two-phase set off

8. Alarm Transfer • List of people • Groups • A person can belong to many groups simultaneously • Tasks • The alarm message can be formed from the information available in TeleCont (point and device names and alarm description) • People required, acknowledgement required, etc... • Activation of groups with calendar • Report page displays the progress of the task

9. Field Device Settings • TeleCont keeps track of your field devices • The device list is always available and the installation setup is documented • Initial testing before starting using the device • Setup changes and their testing • Setup history • An integrated user interface for maintenance of your devices (Device setup) • The setup changes are stored in the setup log • Changing field device settings directly (past TeleCont) is not recommended

10. Customization and Logs • New devices are based on templates • Devices, points, and groups of points are named according to their usage • You can define your own message patterns • History is preserved • in the point’s history page • in the web server’s log • in the traffic report page • Billing is based on the account’s traffic report

11. Customization and Logs 2 • Limiting user’s access rights • Normal user’s desktop can be customized (fewer pages, fewer options) • Field device setup changes are allowed only to selected users • The images on the “Send Command” page can be customized (defined in the point type) • The buttons on the “Send Command” page can be customized by assigning them to the point type and the point’s message patterns • Customer specific extensions are possible (for example, a graphical map of your field devices)

12. Information Security • Information is exchanged over secured connection (SSL) • Passwords • Must be strong enough (eight characters is recommended) • Intra-, Extra-, Internet • You can restrict the access to the system by adjusting your web server and network settings • Field device security • GSM subscription in TeleCont is unique • GSM subscriptions are easy to get

13. Starting Using TeleCont • Telemic as an Application Service Provider (ASP) • Web browser is all you need (MS-IE) • Own web server • MySQL Database (included) • MS Server 2003, IIS6 • GSM modems • Renting of the application (ASP) is priced according to the reserved resources (number of users, number or devices, etc…) • ASP is an easy and cheap way to start using TeleCont quickly