Expertise in app solutions: the Ha-VIS Application-Suite
A work shift gets under way in the maintenance and service department of a factory. A technician performs maintenance on equipment within the company. This activity must be thoroughly documented and centrally recorded in an in-house database system.
But the technician doesn't grab a folder full of checklists from the shelf that details the work he needs to complete today. Instead, he picks up a mobile RFID reader with integrated touch panel. After logging on to the device, his work can begin.
Arriving at the first maintenance location, the machine scheduled for servicing is uniquely identified by UHF RFID with the aid of the mobile RFID reader. The maintenance checklist is automatically shown to the technician on the display, including the correct machine/object identification. Maintenance work is digitally documented directly on the mobile recording device. Thanks to RFID identification, any mix-up with the wrong checklist or an incorrect maintenance object is ruled out.
- But who ensures that the recorded data are stored in the correct database?
- How complex is the maintenance of such a system?
- What happens if different recording devices are used?
- Can an application potentially be adapted to new work processes in flexible manner?
- Does the mobile recording device need to be permanently connected to the server?
HARTING's Ha-VIS Application-Suite takes over and organizes these tasks. The client-server based architecture of this solution platform makes it possible to create hardware-independent and operating system-independent applications (apps). In concrete terms, this means that an app runs on a central server and can be updated and maintained there. The predominantly mobile client devices receive the necessary information and interfaces from this central location. But unlike a conventional client-server based mobile app, more than just a website is displayed on the client. Extensive job steps such as maintenance work can be performed offline. The mobile device loads necessary data once into memory and can then continue to work offline.
In addition, in contrast to pure Web-based applications, the hardware of the mobile end device can be accessed – for example, that of the RFID reading unit.
To accomplish this, HARTING makes device-specific connections available. As a result, during the actual app creation the device-dependent properties can be ignored. The advantage of this technique: an app that is created can run on different end devices supported by HARTING.