paledo - paperless documentation

The Software - Mobile maintenance has never been easier

The PALEDO software consists of 3 components:

PALEDO-Server

The PALEDO-Server serves as a central storage unit and provides all relevant data. Additionally, the server contains the interface module that connects to third party systems, e.g. ERP or IPS solutions.

PALEDO-Desktop Client

The PALEDO-Desktop Client serves to access data when working at the office. Here, documentation protocols are created and assigned to the maintained objects. Furthermore, acquired data, e.g. the maintenance history, can be analyzed. System administration is also performed using the Desktop-Client.

PALEDO-Mobile Client

The PALEDO-Mobile Client serves to provide technical information en route and, of course, to document maintenance relevant work, the core function of the PALEDO system.

Functional modules

Knowledge management-Module

All maintenance relevant data are saved and made available in the knowledge management module. This comprises the structure of attachments, for example. All objects that are subjected to maintenance work are managed in this module. Object structure and related master data can either be managed in PALEDO or can be synchronized from external systems, e.g. SAP PM. Maintenance history and technical documentation are available for every object. The maintenance history can be scanned through manually or can be analyzed automatically according to specific criteria.

Functional modules

Template-Module

A documentation template is necessary to document maintenance work in a systematic and structured way. In most companies these templates exist as photocopy templates or are created and managed using Office-Applications like Excel and Word.
These templates can be imported into PALEDO and subsequently provided for use no matter the kind of source they come from. After importing, the user defines where object and task master data are automatically provided in the protocol, e.g. object codes, manufacturer, serial number, task number, start date, etc. Only few clicks are necessary to define where the user has to fill in data in the protocol template.
It is furthermore possible to define tolerance checks, calculation formulas or executable macros for the entered data. All definitions take place in the intuitive, graphic protocol designer.

Once all protocol pages of a task are defined and approved via the functionalities of quality control, they can be assigned to a task (e.g. “Major Inspection”) and to a group of objects (e.g. “all underground trains of a defined manufacturer”). Data acquisition can directly start once this template is predefined and assigned.

Protokolldesigner

Acquisition-Module

Actual data acquisition takes place in the Acquisition-Module. Every documentation activity is based on a work order. The latter can either be created manually in PALEDO or be imported automatically from an external system. The work order defines which maintenance object (e.g. “pump with serial number LAB10-AP001”) has be worked on using which kind of activity (e.g. “complete revision”). On the basis of the documentation template that is deposited in the template module PALEDO provides automatically all necessary protocol templates and compiles them in a report. The documentation task which includes protocol templates, object master data and technical information (manufacturer instructions, schemes, internal work instructions…) is then automatically sent via the network to the assigned employees and provided on their Tablet-PC. The actual data acquisition takes then place on location using handwriting recognition, digital camera or connectable diagnosis systems. Data entry can be done offline meaning that no active WLAN or UMTS connection is needed. After completion of work or at the end of the work day the employee synchronizes the input device via WLAN or docking station with the main data base. All completed reports are archived as PDF in the data base and additionally on a network drive. Optionally work orders can be reported back in external systems or the documentation can be stored in a document management system (DMS) via interfaces.

Protokolldesigner

Interfaces

The provided interface modules constitute a particular strength of the PALEDO system. No programming is necessary to implement an interface to standard systems, since this is achieved by using configurable standard modules. To connect proprietary customer software a standard interface can be used or a customer specific solution can be developed and implemented. A possible integration strategy is shown using the example of SAP PM.

>> to integration example SAP interface

SAP interfaces