Performance and Data Limits
A recurring question is how much data can MyPM take and what impacts on the performance. The answer is complicated by the following variables:
- Not all devices are created equal – The device operating system (type and release); processing speed and memory mean that one device may accept a great deal more data than another. Device capabilities are regularly improving in terms of hardware and software.
- Not all master data records are the same – Equipment and Functional location records can vary considerably in terms of their data volume – for example whether they are a shell record or fully maintained; their classification data; associated measurement points; long texts; etc.
- Not all SAP systems, networks, WiFi and cellular systems are the same – All these things contribute to how fast synchronisation events occur.
- Not all user expectations are the same – People have different expectations on how fast the application should perform. The data size is not just about the total number of records but also the frequency of change.
- Not all users use their device the same way – Depending on the device, other concurrent use can impact on the application performance.
Because of the variables the answer as to ‘how much data can MyPM take’ is not definitive. In general terms you should send the least amount of data that is needed to perform the business function. After all we are trying to mobilise some aspects of SAP operations and not all of Plant Maintenance. The following are some generalised targets, not hard limits, MyPM may continue to perform well above these limits or may strike issues earlier with smaller data sets.
- Work Orders – 200 Orders
- Operation – Work Order should have no more than 100 Operations as a guideline
- Objects – Work Orders should have no more than 100 Objects. More than this can cause performance issues as each Object is evaluated in real time for Inspections every time the Order is opened
- Equipment and Functional Locations – 75,000 full records with associated measurement points and a moderate number of classification values.
Data should be limited by using the MyPM User Profiles and with the following in mind:
- Are all the object types required on the device? For example you might have 10 of thousands of Equipment records for inconsequential assets which are not actively worked on and have infrequently requirements for Notifications. Rather than sending to the device consider if Notifications could be raised against the parent Equipment or FL.
- Are all the classification values required? For example you might have administrations details maintained in the classification values that are never referred to in the field.
- Is the window for Orders too far back/ too far forwards? How much backward visibility is required if the planner are keeping on top of overdue work; how much forward visibility is required to accommodate the ‘self planning’ nature of your workforce.
- If workers are transient between areas then can multiple profiles be used to more precisely define those areas rather than a ‘take everything’ approach. MyPM also allows you to start and end profiles at specific dates through MyPM config or through SAP User Roles (SAP Security)