Introduction
This sub tab is used to maintain configuration settings for BlueWorx Inspections. Documentation on actual Inspection configuration is detailed here Asset Inspections.
Important Information
- Inspection Authorisation Groups was delivered in Support Pack 11 which optionally provides additional control over who can maintain Inspection configuration settings. For comprehensive information on this topic see Inspection Authorisation Groups
- The Inspection Document Template configuration and Inspection Print Template was introduced in Support Pack 13
Inspections Sub Tab
The following is an illustration of this screen:
The following are the field settings for this sub tab:
| Field/ Function | Description/ Usage | Recommendation |
|---|---|---|
| Inspection Settings | ||
| Max Image size in HTML content | When you create Inspections and Inspection Questions you can, as of SP7, use HTML content including image files. This setting controls the allowed relative size of such images. | Such files should be used sparely as they, like all inspection details, are captured per inspection and if large numbers of images or large image files are used, then this can lead to poor sync performance. |
| Activate Inspection Authorisation Groups | Enable to turn on the user of Inspection Group Authorisations | This switch can only be enabled where Administration Authorisations are active and will be disabled where that switch is disabled. |
| Maintain Inspection Print Template button | See Maintain Print Inspection Template for details on use. | Only to be maintained by personnel experienced in the HTML. |
| Background Generation for Orders | ||
| Allow | Through this configuration, you can set SAP to generate the Inspections. Prior to this option being available, inspections could only be matched to work orders from within the running application. It happened on the front end. See important sub section below for more about this setting. | |
| Days before start date and days after the finish date | Used in conjunction with the above setting. This configuration time bounds the Inspections generated. The generation horizon is the greater of:
| |
| Inspection Document Template | ||
| Max Upload Size | Enter max file size (mb) | 20 |
| Document Repository | Select the document repository to use (SAP GOS, SAP DMS or Custom) | |
| Inspection Authorisation Groups | ||
| Description | A description for the Authorisation Group | |
| Authorisation Object | SAP Authorisation Object | Get your SAP user security people to make these and assign to personnel as required |
| Plants | SAP Plants | The SAP Plants that this authorisation group can maintain inspections for |
| Object Types | SAP Object Types | The SAP Object Types that this authorisation group can maintain inspections for |
Background Generation of Inspections
This option was introduced in SP7 and removes the load on the device for calculating large numbers of inspections for orders with many objects (for example power-pole inspections). A secondary benefit is that as the order-based inspections are generated without any user input, data becomes available in SAP which could be used to generate reporting on upcoming, or incomplete inspections. See also: Background generation of inspections
Dependent Steps for Use
- Administrators must also run and schedule a new SAP job to populate and update this information. Details are available in this article Master Data and Batch Jobs under Create Job to process Inspection Order Generation
- You must set up a new Event Linkage (ORDER_CHANGE event) as defined in the Installation Guide under BlueWorx Technical Configuration > Plant Maintenance Configuration > Events > SAP Standard Workflow Events.
- The only Inspections generated are those with a specified Work Order Type in the Inspection configuration.
- If there are User Profiles with a longer forward horizon for orders than the admin setting for background generation inspections, then the largest forward horizon from the User Profiles is used. This prevents orders from being synced to the application without their associated inspection relationships.
- If activated, only fieldwork order inspections, inspections from adding technical objects to the order object list, or those from add operations will be matched by the application.
- Ad-hoc inspections on Equipment and Functional Locations will continue to be matched by the application, regardless of the setting.