General Reference
ASO Site Filtering
In Asset Strategy Optimization, users will only see global data and strategy data related to their assigned sites.
When asset and unit strategies are optimized in ASO, the ASO analyses are locked with the site they inherit from the strategy. So, once the ASO analysis inherits a strategy, subsequent strategies added to that analysis must be of the same site.
If you have optimized a global strategy, you cannot add an asset with a site if the strategy has already been optimized.
Example
Consider an organization that has three sites, Site X, Site Y, and Site Z. The following strategies receive the specified site assignments:
- Strategy 1: Assigned to Site X
- Strategy 2: Assigned to Site Y
- Strategy 3: Assigned to Site Z
Scenario 1: User assigned to only Site X
When creating an ASO analysis, the user will only be able to assign the ASO analysis to Site X and will only be able to add strategies of the same site if it is a system or unit strategy being optimized.
Scenario 2: User assigned to both Site X and Site Y
When creating an ASO analysis, the user will be able to assign the ASO analysis to Site X or Y and will only be able to add strategies of the same site to that ASO analysis.
Scenario 3: User with access to all sites
When creating an ASO analysis, the user will be able to assign the ASO analysis to Site X, Y, or Z, and will only be able to add strategies of the same site to that ASO analysis.
ASO URLs
There is one URL route associated with Asset Strategy Optimization: /strategy/aso. The following table describes the various paths that build on the route, and the elements that you can specify for each.
ASM URLs
| Element | Description | Accepted Value(s) | Notes |
|---|---|---|---|
| <AnalysisKey> | Specifies which ASO Analysis that you want to view. | The Entity Key of the selected System Analysis Record. | |
| <Summary> | Identifies the page that you want to display. | Analysis | When the analysis appears, the Analysis workspace page is displayed by default. |
Example URLs
| Example URL | Destination |
|---|---|
| /strategy/asm/aso/analysis/64253128637/summary | Opens the ASO Analysis containing the System Analysis record with the Entity Key 64253128637. |
ASO Data Model
The following diagram illustrates how the families are related to one another within the ASO data model. Boxes and arrows represent entity families, relationship families, and associated relationship definitions. Note that in the following image:
- Gray arrows and boxes represent families that exist in the ASO data model but are not currently used in any ASO workflows. These may require customization.
- Black arrows and boxes families that are configured in the baseline database. These do not require customization for baseline usability.
While interpreting the image, note that:
- While only one System Scenario box appears in the image, each ASO Analysis will contain multiple System Scenario records.
- The image contains two System SubSystem boxes because in an ASO Analysis, System SubSystem records serve two purposes:
- They identify the Diagram. Each ASO Analysis contains only one Diagram, but per Scenario, the database contains two separate System SubSystem records to represent this Diagram. In other words, for each Scenario that exists in the analysis, the set of System SubSystem records that represent the Diagram is duplicated. So, for an analysis that contains only an Active Scenario and Proposed Scenario, four identical System Subsystem records will exist. Two of the records will be linked to the Active Scenario record, and two of them will be linked to the Proposed Scenario record. Whenever a change is made to the properties of the Diagram itself, the APM system updates all System SubSystem records that represent the Diagram so that they are always identical.Note: The APM system creates two identical System subsystem records to represent the Diagram because the ASO and Reliability Analysis modules share code and in Reliability Analysis, each analysis can have multiple Diagrams.
- They identify subsystems within the Diagram. In an ASO Analysis, the Diagram can contain multiple subsystems. Per Scenario, the database contains two separate System SubSystem records to represent a single subsystem in the Diagram. In other words, for each Scenario that exists in the analysis, the set of System SubSystem records that represent a subsystem within the Diagram is duplicated. So, for an analysis that contains only an Active Scenario and a Proposed Scenario, if the Diagram contains only one subsystem, four identical System SubSystem records will exist to represent this subsystem. Two of the records will be linked to the Active Scenario record, and two of them will be linked to the Proposed Scenario record. Whenever a change is made to the properties of the subsystem element via the Diagram, the APM system updates all System SubSystem records that represent that subsystem so that they are always identical.
In other words, because each ASO Analysis must have an Active Scenario and a Proposed Scenario at all times, each ASO Analysis will contain at least four System SubSystem records, where these System SubSystem records represent the Diagram. Two of these records will be linked to the Active Scenario record, and two of them will be linked to the Proposed Scenario record. As additional Scenarios are created, other identical sets of System SubSystem records are created and linked to those Scenario records to represent the Diagram. In addition, if the Diagram includes subsystems, per Scenario, the ASO Analysis will contain two additional System SubSystem records to represent those subsystems.
- They identify the Diagram. Each ASO Analysis contains only one Diagram, but per Scenario, the database contains two separate System SubSystem records to represent this Diagram. In other words, for each Scenario that exists in the analysis, the set of System SubSystem records that represent the Diagram is duplicated. So, for an analysis that contains only an Active Scenario and Proposed Scenario, four identical System Subsystem records will exist. Two of the records will be linked to the Active Scenario record, and two of them will be linked to the Proposed Scenario record. Whenever a change is made to the properties of the Diagram itself, the APM system updates all System SubSystem records that represent the Diagram so that they are always identical.
- The System SubSystem family is related to the System SubSystem family through the Has System Elements relationship. In the image, the System SubSystem box that contains the text Diagram in parentheses represents the Diagram. The System SubSystem box that contains the text Subsystem in parentheses represents subsystems within the Diagram. This distinction is made so that you can see that the System Global Event record is linked to the System SubSystem records that represents the Diagram.Note: In ASO Analyses, all System SubSystem records are linked to the successor System Element records. The boxes are separated in the image only to clarify the Has Global Events relationship.