ASI Packages | On-Premises APM

What is an Implementation Package?

Details

An Implementation Package is a collection of actions that are to be implemented in an SAP system. The implementation package defines the structure that the SAP system will use and defines how the actions map into that structure. An Implementation Package consists of the following:

One Implementation Package that defines basic information about the purpose and content of the Implementation Package.
One or more Actions representing the original work requests.

There are multiple records in ASI that represent work that you want to perform. These records are linked directly or indirectly to the root Implementation Package and can belong to different families, such as the Maintenance Item family. Because they can belong to different families throughout the APM documentation, we refer to them generically as work items.

About State Configuration in ASI

ASI leverages State Configuration Roles, which you can assign to Security Users to manage who can transition strategies from one state to another.

Throughout ASI, some options will be disabled based on whether or not the current user is assigned to the State Configuration Role that is required to perform that action.

If no State Configuration Roles are specified for State Configuration, as in the baseline database, all options will be available to all users, and state changes will not be restricted. To take full advantage of the features in ASI, we recommend that you assign members of the ASI Security Groups to a corresponding State Configuration Role.

The following diagram shows the states and operations that exist in the baseline State Configuration for the Asset Strategy Implementation family. You can use this diagram to determine which operations will appear on the Operations menu when you are viewing an Implementation Package. The Operations menu will display any operation to which the current Asset Strategy Implementation record can be transitioned from its current state.

State Configuration

The Draft state is the initial state of all new Asset Strategy Implementation records.

Datasheet Configuration: By default, states and operations will appear on the datasheet when you are viewing an Asset Strategy Implementation record in the Record Manager.
Reserved States and Operations: Custom states and operations are only supported between the Draft and Packaged states. This means that you cannot remove or modify any of the other states or operations.
State Configuration Roles: By default, the MI ASI User State Configuration Role is assigned to all states in the Implementation Package State Configuration. However, you can assign other State Configuration Roles. In addition, for each state, the Require a specific user to be assigned to a state check box is selected.

Reserved States and Operations

The following table lists the baseline states and operations and indicates which of these states and operations are reserved. You cannot remove or modify reserved states or operation. You can, however, add your own states and operations to the State Configuration.

Note: Custom states and operations are only supported between the Draft and Packaged states. This means that you cannot remove or modify any of the other states or operations.


States	States
State	Is Reserved?
Draft	No
Implemented	Yes
Modified	Yes
Packaged	No
Partially Implemented	Yes
Pending Implementation	Yes
Operations
Operation	Is Reserved?
Complete Implementation	Yes
Implement	Yes
Package	No
Partially Implement	Yes
Revert	No
Revise	Yes
Update	Yes

About Site Filtering in ASI

While the families within ASI are not enabled for site filtering, many records within ASI use site assignments. A single implementation package can contain actions from multiple sites. If the package has actions from multiple sites and you as a user do not have permissions for all of the associated sites, the entire package will be view-only.

Tip: For more information, refer to the Site Filtering section of the documentation.

Example

Consider an organization that has three sites, Site X, Site Y, and Site Z. MPI Package is a global record and it contains the following action records:

Action 1: Assigned to Site X
Action 2: Assigned to Site Y
Action 3: Assigned to Site Z

Scenario 1: User assigned to only Site X

When this user views the Package Details page, the package will be view-only for the user, because there are actions (Action 2 and 3) with a site assignment for which the user does not have permissions (Site Y and Z). The user will not see the actions for Sites Y or Z.

Scenario 2: User assigned to both Site X and Site Y

When this user views the Package Details page, the package will be view-only for the user, because there is an action (Action 3) with a site assignment for which the user does not have permissions (Site Z). The user will not see the action for Site Z.

Scenario 3: User assigned to Sites X, Y, and Z or Super User

When this user views the Package Details page, the user has modify privileges for the package, having full access and permissions for all of the associated actions.

Access an Existing Implementation Package

Procedure

Access the ASI Overview page.
Select the Implementation Packages tab, or the tab for the section that contains the package that you want to manage.
The selected section appears, displaying a list of available packages.
Select the link for the package that you want to manage.
The page for the selected package appears, displaying the Manage Actions section.

Create an Implementation Package

Procedure

Access the ASI Overview page.
In the page, select New Package.
A page for the new ASI package appears.
As needed, enter values in the available fields.
Select .
A message appears, confirming that your ASI package has been created.

What To Do Next

Import SAP Objects into ASI

About This Task

You can import items from an external SAP system to become actions to build out an existing implementation package in ASI.

Note: To use the Import from SAP feature, you must have active ASI and ASM licenses.

Procedure

Access an existing ASI package.
In the page, select .

The Asset Strategy Builder (SAP Work Management) window appears, displaying the SAP Object(s) section, which contains a list of assets with related SAP objects.
Select the check box for each asset whose SAP objects you want to import into the package.

Note: If you want to search for a particular asset, select to access search boxes in the grid. If you want to exclude operations and only import the Maintenance Plan, Maintenance Item, Object List, and Task List, select the Exclude Operations check box.
Select Next.

The Action Creation screen appears.
Choose whether you want to Import Maintenance Items as Actions or Import Operations as Actions, and then select Next.

The SAP Item(s) screen appears, displaying a list of SAP objects available to import based on the assets you selected.
Select the check box for the SAP objects that you want to import, and then select Finish.

The Import Results section appears, and an import report runs, indicating the progress of importing the items. When finished, the status bar appears at 100%.

Note: The status bar is color-coded. If the report completes with no errors, the status bar is green. If some SAP objects have been skipped, the bar is orange. If the report has failed, the status bar is red.

Results

Existing SAP objects have been imported into ASI as WMIs in the implementation package and actions related to the strategy.
A strategy and associated actions are created in ASM in Active state, and the actions are linked to the WMIs in the implementation package.

Package Implementation Packages

Before You Begin

These steps assume that you have an implementation package that is in the Draft state.

Procedure

Access an existing ASI package.
In the page, select .
Select Package.
Select Done.

A message appears, asking you to confirm that you want to perform the package operation.
Select Yes.

The package is now in the Packaged state.

What To Do Next

Implement a package

Revert a Package

Before You Begin

These steps assume that you are using an ASI package that is in the Packaged state, but has not yet been implemented.

Procedure

Access an existing ASI package.
Select .
Select Revert, and then select Done.

A window appears, asking you to confirm that you want to perform the operation.
Select Yes.
A message appears, notifying you that the package was updated. The package is now in the Draft state.

Implement a Package

Before You Begin

These steps assume that you have an implementation package in the Packaged state.
There must be a user assigned for your package, so depending on state configuration settings, you may need to assign a user to perform the package operation.

Procedure

Access an existing ASI package.
Select .
Select Implement, and then select Done.
A window appears, asking you to confirm that you want to perform the implement operation.
Select Yes.
A window appears, displaying a summary of all that has been implemented.
Select Close.
The package has been implemented.

Revise a Package

Before You Begin

This documentation assumes that you have an ASI package in the Implemented state.
There must be a user assigned for your package, so depending on state configuration settings, you may need to assign a user to perform the package operation.

Note: Revising a package takes an ASI package from the Implemented state back into a Modified state.

Procedure

Access an existing ASI package.
Select .
Select Revise, and then select Done.
A window appears, asking you to confirm that you want to perform the operation.
Select Yes.
A notification appears, indicating that the operation was successful. The package is now in the Modified state.

What To Do Next

Update an ASI Package

Update an ASI Package

Before You Begin

This topic assumes that you have an ASI package in a Modified state.

Procedure

Access an existing ASI package.
Select Update, and then select Done.
A window appears, asking if you want to perform the operation.
Select Yes.
A window appears, confirming the implementation results.
Select Close.
The package is now in the Implemented state.

Export an ASI Package from the Package View

Before You Begin

As needed, configure the Export ASI Package feature.

About This Task

Exporting an ASI Package serves the following purposes:

Allows you to export an ASI Package, along with all the WMIs in the package.
Allows you to include a WMI added at the root level while exporting the package.

You can also use the package as a template for the ASI Data Loader.

This topic describes how to export an ASI Package.

Procedure

Access the ASI Overview page.
Select the ASI Package.
In the ASI Package view, select Actions > Export Package.
The Export Package - Select Work Management Item from Package Level window appears, displaying a list of WMIs at the root level.
Select the WMIs that you want to export.
Select Export, and provide the file name.
The Job Monitoring Dashboard page appears, displaying the progress of the export. After the job is completed, you can download the package. If, however, another job such as implementing or validating the package is running at the same time, you will be able to export the package only after the current job is completed.
Note: You can also export the history of an ASI Package by selecting Actions > Export History in the ASI Package view.

Delete ASI Packages

Procedure

Access the ASI Overview page.
Select the Implementation Packages tab, or the tab for the section that contains the package that you want to manage.
The Implementation Packages section appears, displaying a list of available packages.
Select the package that you would like to delete.
The package is highlighted.
Select .
A message appears, asking you to confirm that you want to delete the package.
Select Yes.
The package has been deleted.

Remove an Action from a Package

About This Task

If you need to remove an action from a package, that package cannot yet be implemented. If you want to remove an action that is implemented, you must first unlink the implementation from the action, and then you can remove the action from the package.

Procedure

Access an existing ASI package.
Select the check box for each action that you want to remove from the package, and then select .
The action is removed from the package.

Results

The action is removed from the implementation package, but not deleted from the APM database. If you want to add the action back to the package, you can do so from the Implement Actions workspace in ASM.

Build SAP Plan from Actions

About This Task

You can implement actions in ASM to manage their execution in APM. Or, if you want to manage the execution in SAP, you can implement them in the Manage Actions section of ASI, as described in the following steps. Alternatively, you could create WMIs and link actions to WMIs manually. Or, you could import SAP objects into ASI as WMIs.

Procedure

Access an existing ASI package.
Select the row containing the action to which you want to link an implementation method, and then select Build SAP Plan.
The Select Action Mapping window appears.
Select one of the following options:
- Actions are Items: This option creates a plan and an item for each asset and interval combination from the selected Actions.
- Actions are Operations: This option creates a plan, item, and task list for each asset's intervals, and it creates an operation for each action under the correct task list.
Select Build.
The actions are now associated with WMIs. Now, when this package is implemented, you can manage the actions in SAP.

Apply Updates to Implemented Actions

About This Task

If you modify actions after they have been implemented, you must apply those updates to the implemented actions, which can be done in ASI or in ASM.

Note: For actions that require updates to synchronize their implementations, the text Requires Update appears in the Implementation column for the actions in the Manage Actions section in ASI or in the Implementation column in the Implement Actions page in ASM.

Important: Depending on the Unit of Measure employed by your organization, customization of ASI may be required to support strategy plan interval updates.

Procedure

Access an existing implementation package.
In the Manage Actions section, select each row containing an action whose WMI you want to update, and then select .

Results

The updates are applied to the WMIs associated with the actions.

The corresponding SAP Maintenance Plans or Maintenance Packages are updated:


Plan type	Value update by Maintenance Plan interval
Single Cycle Plans	Cycle for the corresponding Maintenance Plan
Multiple Counter Plans	Cycle for the corresponding time-based Maintenance Plan
Strategy Plans	Cycle in the corresponding Maintenance Package

If any updates were unsuccessful, the Errors window appears, which contains a list of the unsuccessful updates.