oxando Asset Management – Mobile Solution for SAP PM/CS/MRS

11
Page 1 Scope of functions „oxando Asset Management“

Transcript of oxando Asset Management – Mobile Solution for SAP PM/CS/MRS

Page 1

Scope of functions

„oxando Asset Management“

Page 2

Table of contents

1 Initial situation / objective 3

1.1 Architecture of oxando Mobile Connector / oxando Asset Management...................... 3

1.1.1 oxando Mobile Connector 5

1.1.2 oxando Mobile Client 7

1.1.3 RFID integration 8

1.1.4 Barcode integration 8

1.1.5 System integration and communication between client and SAP system 8

1.1.6 Range of function in the field of maintenance and service 9

Page 3

1 Initial situation / objective

oxando is convinced that the mobile infrastructure offered and the mobile application together with the

good process and solution knowledge of the oxando consultants will excellently contribute to achieving

the project targets of the customer mentioned. The solution offered has been employed by various

customers for years.

Among other things, the solution is successfully used at the reference customer Fraport at Frankfurt

Airport as a central solution for maintenance processes (planned and unplanned). By using the solution,

various other solutions could be replaced and various interface components were saved. Thus, the use

of the oxando solution has successfully replaced a complete SAP server landscape or a cloud-based

incident management solution.

On the part of the processes to be implemented, oxando offers profound experience of the project

members based on the customer projects realised since 2010, and will be pleased to include this know-

how into the customer project. This experience covers fundamental SAP processes starting with

maintenance planning and its strategy, including the definition of master data, checklists, test

characteristics right to the ideal control of technicians and an effective connection of mobile applications

without having to build up additional infrastructure for the purpose.

Below please find the description of the architecture, the product specifics and the general functions of

oxando standard solutions of “oxando Mobile Connector” and “oxando Asset Management”.

1.1 Architecture of oxando Mobile Connector / oxando Asset Management

oxando offers the implementation of mobile scenarios on the basis of is mobile infrastructure of oxando

Mobile Connector. This mobile infrastructure can be used on the SAP ERP system (as from ERP 6.0

release) of the customer in order to support different SAP ERP processes.

The solution oxando Mobile Connector (hereinafter referred to oxmc) is a plugin for the SAP ERP

system. It serves as an interface between the SAP processes and the mobile applications.

For the field of mobile maintenance and service management, the solution oxando Asset Management

is used as HTML5 version on this framework. As application on the various devices and platforms,

oxando Asset Management covers all standard processes in the field of maintenance and service

management. This includes the implementation of planned and unplanned maintenance and service

processes, mobile checklist processing, the acquisition of master data and plants, the structuring of

master data and plants already existing, the maintenance of master data and classification data and

many other processes within the framework of SAP maintenance and service activities.

Basically, the mobile solutions of oxando described here are directed to the following objectives:

Safeguard of a deep integration into the existing SAP ERP processes (PM, CS, MM, QM), and

into the existing system architecture.

Page 4

Ideal process design for the staff at the mobile device (for example, by RFID functionality,

ergonomic application setup, assistance by intuitive touch units, such as iPad and Android).

Creation of uniform, open mobile platform by using standard software for all mobile processes

with the option of assisting future processes mobile.

The reduction of costs for mobile solutions by simple administration by staff of the department.

Reduction of the system environment; the SAP ERP system and the mobile device are required

only. No separate middleware or cloud systems are required.

Fast implementation times.

Simple administration directly in SAP ERP without additional infrastructure.

The following presentation renders the architecture by using oxando Mobile Connector for the

implementation of mobile processes.

The mobile processes are linked to the SAP system by the oxando Mobile Connector in combination

with the mobile client. When free from modifications, the oxando Mobile Connector is installed directly

to the SAP backend system and is developed in ABAP/4.

Page 5

The oxando Mobile Connector provides the central software layer for the setup of mobile scenarios

(customising), the data distribution for the mobile users, the communication via web service with the

mobile client as well as a central administration overview for monitoring the mobile processes.

1.1.1 oxando Mobile Connector

By customising the oxmc, the application scenarios can be defined; the different mobile applications

(such as maintenance management, inventory, warehouse management) or different specifications of

a solution (such as inventory taking, master data maintenance, service staff, installation technician) can

be presented. In this way, it can be controlled in detail which functions with which data and which

processes and/or authorisations shall be available in mobile state.

In general, the architecture renders available the following functions:

Permanent synchronisation processes:

o Slim middleware functions:

The oxando Mobile Connector offers the functions of a middleware, however no additional

middleware system is required. This is helpful with regard to the request for low operating

costs of the mobile infrastructure.

o Indexed data accesses - targeted accesses to the data needed:

The data which are relevant for the mobile users are kept on stock within the data

retention of oxando Mobile Connector (“indexing”). Thus, no complex selection and search

variants are required for data gathering in the SAP system during synchronization. By

using the qualified SAP object key, the detailed data only are read during synchronization

in order to ensure a high topicality of the data.

o Prevention of long data preparation times during synchronization:

By the indexed access, the (detailed) data are read performance ideally from SAP for

synchronization. For master or customizing data, the data can be prepared by batch jog in

regular intervals or manually - as requested - by means of the administration surface, and

can be saved for synchronization directly as data packet. In this case no data selections

are available in the SAP system for synchronization - data transmission only occurs.

o Push and caching functions:

The mobile client receives the relevant data prefab. If the synchronization is aborted, the

data packet is retained and can be transmitted again without any data selection during the

next dial-up.

o Selective synchronization of master and transaction data as well as customizing:

In order to be able to avoid extensive synchronization processes for master data and

customizing during the daily routine and to be able to reduce the synchronization to the

most important transaction data (such as new orders as well as feedbacks), the function

of selective synchronization is available for the mobile client. The mobile user himself /

herself can control whether he or she wants to synchronize customizing, master data or

Page 6

transaction data. Thus, flexible reaction is possible to the respective circumstances, such

as type and quality of the network connection.

Flexible integrated data model:

o Generic data structures for field changes:

Depending on the business object and its data, there are configurable data structures

between the SAP system (or the oxando Mobile Connector) and mobile client. If additional

fields shall be transferred to the client, the field needs to be included in the corresponding

structure only - the data transmission to mobile must not be adapted for the purpose.

o Consistent data structures between ERP system and mobile client:

The experience has revealed that consistent data structures and field names for the data

exchange reduce effort and complexity of the mobile infrastructure. For this reason,

oxando uses consistent technical data wherever possible to avoid field mapping and data

convergence.

User administration:

o Use of named users:

The mobile infrastructure of oxando operates with name users (not with technical

composite users or RFC users). The user is used to login to the mobile client as well as in

SAP system in the background during synchronization. Data retention at the client as well

as mobile connector is user and client specific.

Note: For this reason, the client requires an additional SAP licence for the mobile users

(not part of the offer submitted by oxando).

Data security and persistence:

o Strict separation of the architecture levels in the mobile devices (data, persistence,

layout): In programming, oxando Mobile Client divides strictly between data, persistence

and layout. Thus, layout changes can be carried out easily, for example, without affecting

the other software layers.

o Use of the data storage on an external data storage device is possible at any time: By

separating the data retention from layout and the application layer, the data retention can

be moved to an external storage unit (such as memory card), for example.

o Encoded data storage:

The data on the mobile terminal unit can be saved encrypted in the local database.

Comprehensible simple administration:

o Central administration overview:

Oxando Mobile Connector includes a central administration overview. Depending on the

application scenario this central transaction can be used to view and check the user, the

data transaction from and to mobile as well as the faults occurred. Thus, a central

monitoring function is available directly in the SAP system. A complex analysis of the

Page 7

mobile process by SAP system and middleware system is not required, but is centrally

integrated and simplified.

o Simplified user-related view to synchronized data including error messages:

Depending on the mobile user, the administration layer indicates the data objects which

are transferred to its mobile device.

Data, which are supplied by the mobile device, can be displayed. If faults occurred in the

SAP application whilst processing data, the error messages are displayed directly for the

respective object. The data can be changed and updates easily in the administration

overview.

By grouping the data according to user and type of data object, the presentation is clearly

designed and can be operated intuitively.

o Date verification prior to updating:

Depending on the object, the mobile data can be updated separately. Thus, feedback, for

example, can be automatically entered; however master data changes are not entered.

Thus, by means of the administration overview, these data can be checked, but can be

entered or discarded only after release.

o Connection status and news to the mobile user:

The central administration overview can indicate the current connection status of the

mobile user. In addition, it is apparent when the last link existed.

Given an existing connection, a direct message can be sent from the overview to the

mobile user which appears directly on the mobile device as alert message.

Open and extensible infrastructure

o The mobile connection and synchronization in the Mobile Connector is generic and can be

used for all business objects of the SAP application. Thus, other mobile scenarios are free

to be implemented on the oxando infrastructure.

o The indexing of an object for a mobile user is carried out event-driven, and can be

adapted specifically to the customer and process. The control is based on customizing

and thus can be carried out flexibly when an object is transferred to the mobile device,

and when it is removed from the mobile device (such as PM order with status release to

mobile with technical completion of mobile).

1.1.2 oxando Mobile Client

The oxando Mobile Client as an HTML5 version is suitable for use on all standard operating systems

(Windows, iOS, and Android).

A uniform SQLite database is used for all client platform which can be optionally encrypted by means of

Microsoft Crypto API and RC4 algorithm.

In addition, oxando offers the solution as HTML5 variant and thus as a cross-platform solution. This

version is as offline capable as the native applications, which is of advantage, when the solution is used

on different or non-self-governed terminal devices.

Page 8

1.1.3 RFID integration

The RFID integration in the mobile client application is ensured by the integration of the manufacturer-

specific driver. Here, as a standard, oxando supports the RFID tags and interfaces of the Microsensys

components on the Windows / Android platform. Other RFID manufacturers and specifications can, of

course, be addressed as far as possible.

1.1.4 Barcode integration

The barcode can be integrated in the mobile client application at all points, in which manual inputs into

search / sorting or input fields can be carried out. This can be ensured without additional outlay, if the

mobile device permits the link to a barcode scanner.

1.1.5 System integration and communication between client and SAP system

The communication between mobile client and SAP backend system (with the oxando Mobile Connector

installed there) is ensured by a web service using http/https. For system integration, no additional

software shall be required in addition.

The oxando Mobile Client is basically online or offline capable.

By means of LAN / WLAN, GPRS or UMTS and, if possible, VPAN or alternatively by a tunnelling

solution, a network connection to the internal network can be setup on the mobile client, by which the

SAP system can be reached. Subsequently, the data are synchronised with the SAP system by

http/https. The duration of synchronization depends here significantly on the speed of the network

connection.

At present, the oxando Mobile Client recognises whether there is a link to the SAP system (“Live

Status”). Based thereupon, it is indicated before synchronization already whether data are available to

be synchronized for the user.

Based on the Live Status, the oxando Mobile Client can be used also to replace the online functions

and alternative synchronisation scenarios against the SAP backend system.

In case of an existing connection, push alerts and messages can be transmitted from the administration

overview using the SAP system.

Page 9

1.1.6 Range of function in the field of maintenance and service

As a standard, the following functions are supported by the oxando Asset Management.

General functions and master data maintenance

RFID support for identification of master data (equipment / technical workplace).

o Including write-back to RFID tag for data updates on site.

Master data change of equipment, technical workplaces.

Creation and inclusion of equipment on the mobile device.

Installation and removal of equipment in the master data structure of technical workplaces and

equipment.

Change of classification data for equipment / technical workplace.

Registration of measuring documents for measuring points.

Inspection checklists based on QM test plants, test lots and test characteristics with integration

to respective PM object (order / message), integration of fault messages and PM follow-up

processes in case of faulty test results.

Display / download of documents for equipment / technical workplace.

Support of flexible checklists on technical object (checklists of suppliers / manufacturers).

Central, transparent administration surface in SAP system.

No other interfaces between SAP system and mobile device.

Clearly arranged and simple visualisation of fault messages.

Low support outlay during ongoing operation.

Integrated software distribution management for administration of applications installed on the

mobile device.

Assistance of various scenarios, user groups and company organisations.

Support of further applications on the same architecture (such as mobile inventory, mobile

warehouse management, etc.).

Order processing

Download of PM / CS orders.

Download as well as mobile acquisition of long texts for order header and order processing.

Download as well as mobile acquisition of long texts for order header and order processing.

Page 10

Flexible distribution criteria in keeping with customizing (such as workplace, planning board

allocation, etcetera).

Download of detailed information on the order as well as of the referenced objects.

o Processes related to order.

o Messages related to order.

o Equipment related to order.

o Technical workplace related to order.

o Planned components related to order.

o Long texts related to order / process.

Order setup and processing of orders which have been created on the mobile device.

RFID assistance for the identification of orders / of technical objects.

Feedback of times (working and travelling times) as well as statistic index figures for service

lump-sums.

Feedback of materials.

o From the pool or technician or warehouse stock.

o From the components of the order.

o From the parts list for the technical object.

Registration of documents for the order,

o such as damage photograph with link to order.

o Generation of an order report (summary of all recorded data including the signature of the

technician and customer) as PDF and synchronization with SAP system (link to SAP

document and deposit in document system).

Use of a calendar surface instead of order list.

Planning of components related to order (order functionality).

Message processing

Download of PM / CS messages.

Download as well as mobile acquisition of long texts for order header / action / measure /

position.

Download as well as mobile acquisition of long texts for order header and order processing.

Flexible distribution criteria in keeping with customizing (such as workplace, planning board,

etcetera).

Page 11

Download of detailed information on the order as well as of the referenced objects.

o Positions, measures, causes, actions for message.

o Order related to message.

o Equipment related to message.

o Technical place related to message.

o Check lot / check-list related to message.

o Long text related to message and their measures, positions, causes, actions.

Message setup and processing of message which have been created on the mobile device.

RFID assistance for the identification of message / of technical objects.

Registration and change of measures, positions, actions, causes of a message.

o Complete integration of the report structure of SAP system (report structure related to

message, to technical object).

o Flexible customizing setting in order to limit data volumes of the catalogue at mobile client.

Registration of documents for the message.

o Generation and link of checklist results as PDF document.

o Registration of documents for the message (such as damage photography) and

synchronization to SAP system.

o Link to SAP document and filing in the document system. For any further information, a presentation in your company or online, reference-visits and test-installations of our mobile solutions please get in contact with:

Frank Ostwald Head of Sales & Marketing

oxando GmbH

Konrad-Zuse-Ring 12 D-68163 Mannheim Germany Tel.: +49-203-75 69 794 Fax: +49-203-75 69 792 Mobil: +49-160-95 90 04 80 Email: [email protected] <http://www.oxando.com>

Follow us on Facebook, Twitter & Co