Parking Notifications and Orders 

In BlueWorx, when enabled for a User by an Administrator, a User you can Park a Notification or and Order for subsequent change and release. This section describes in detail how the Parking process works. 

Characteristics of Parked Notifications and Orders

Some key characteristics of Parked Notifications and Orders are:

  1. You can optionally Park a Notification or an Order when it's in a temporary state and prior to first Sync to SAP
  2. Checks that normally occur on Save of Notifications and Orders are not carried out when Parking
  3. An Order created from a Park Notification with be created as Parked
  4. You can release a Parked Notification associated with a Parked Order, unless it is a Notification triggered from an Order Notification
  5. A Parked Order on release will check for completeness itself and associated Notifications, and if ok, it will automatically release any associated Parked Notification. If the Order or Notification checks fail the checks then the Order Park release will fail. The associated Notifications includes:
    1. Order Header level Notification
    2. Order Object List Notifications
    3. Order Inspection triggered Notifications
  6. Parked Notifications and Orders are retained on device on sync. They are not transferred to SAP and via it to other devices for access by the User. i.e. you can’t Park on a mobile device and complete on a desktop browser

  7. All objects related to the Parked Notification and Order are suspended from going to SAP until the Park is released. This includes: Notification Items, Causes, Activities and Tasks; Order Operations, Time Confirmations, Objects, Inspections (Including Inspection Notifications), Issues, Reservations, Requisitions and Objects (FL, Equipment and Notifications). The exemption is on browser documents, which are transferred to SAP for future linkage on release of the Parked document (or clean-up removal if parent is not released within a given period of days)

Workflow Examples

Here's some workflow examples:

ScenarioWorkflow
Created a Notification but have not completed all the details.
You've found the asset record and created a Notification but there's some additional details you want to check prior to submitting.
  1. Create the Notification for the asset
  2. Park the Notification
  3. Follow-up and correctly maintain the Notification
  4. Release the Notification
  5. Sync with SAP

Can't find asset record when offline for a fault.

You're offline and find an asset that needs a Notification but it's asset record is not on your phone.

  1. Create the Notification without an asset (FL or Equipment or FL but no Equipment) and maintain it as per normal. To aid in its later identification take note of any identifiers (i.e. asset tag) or spatial location as may be appropriate
  2. Park the Notification
  3. When you're back online, search SAP for the correct asset record and apply to the Notification
  4. Release the Notification
  5. Sync with SAP
Can't locate asset record when offline for a fault where work is undertaken.
You're offline and find an asset that needs a Work Order maintenance but it's asset record is not on your phone. In addition you need to undertake an Inspection for the asset as part of the maintenance process.
  1. Create the Notification selecting a similar asset and maintain it as per normal. To aid in its later identification take note of any identifiers (i.e. asset tag) or spatial location as may be appropriate
  2. Park the Notification
  3. Create an Order from the Notification, it will automatically be Parked
  4. Undertake an Inspection for the Order/ Asset
  5. When you're back online, search SAP for the correct asset record and apply to the Order. This will automatically change the object in the Notification
  6. Release the Order. This will automatically release the Notification and ask the user if they want to update the asset record for the Inspection. If they do then they will have to re-complete the Inspection (where it has been completed). The action will also automatically update any Inspection derived on device Inspections.
  7. Sync with SAP