Release Notes Ver 2.0 Dec 2018

AssetOptics for Salesforce Lightning Version 2.0 Release Notes

Release Date – Dec 2018

How to use these Release Notes

The release notes are organized by solution area.  The UC identifier refers to a specific Use Case within the AssetOptics software development lifecycle (SDLC).  An explanation of the Use Case and delivered functionality follow.  If there are any configuration requirements, they will be listed in the Setup Requirements following the use case explanation.  The setup requirements should be used by your system administrator to plan and execute the AssetOptics managed package upgrade.

Asset Management

UC-0222        Building/Floor/Space Facilities Hierarchy.

A new facilities data model has been incorporated into asset management, preventive maintenance scheduling, and work order management.  The data model includes Buildings, Floors, and Spaces.  Lookup references have been added from the Equipment/Asset, PM Schedule, PM Group Schedule, and Work Order objects to the Space object.

A space hierarchy tree has been added to the page layouts for Buildings, Floors, and Spaces.  The space hierarchy displays the Floors within a Building, the Spaces on a Floor, and the Assets within a Space.

PM Schedules and PM Group Schedules can be created directly against a Space without entering an Asset.  Preventive and Corrective Work Orders can be created directly against a Space without entering an Asset.  Since Assets can now be contained in Spaces, the Work Order application logic (APEX code) has been updated such that when Work Orders are created against an Asset within a Space, the Space reference is also copied to the Work Order (this is in addition to the Location and Account references on the Asset).

The net result of the new data facilities data model is that you can now manage Assets within a facilities-oriented Space both independent of and interdependent with Locations and the location hierarchy.

Setup Requirement:   If you are utilizing the standard AssetOptics profiles and permission sets, field level security will be updated upon upgrade.  If you are using org-specific profiles and/or permission sets, then field level security needs to be added to the Building, Floor and Space objects.  There are now Lookup relationships on the Work Order, PM Schedule and PM Group Detail objects to the Space objects.  Field level for this field on these objects should be set consistent with your setting of the Asset on these objects, respectively.

Work Management

UC-0219        Location object reference on Work Orders

A lookup reference has been added from the Work Order object to the Location object.  The application logic (APEX code) has been updated such that when you create a Work Order against an Equipment/Asset that has a Location reference, the Location is automatically populated to the Work Order.  If the Location on the Asset is later changed, the existing Work Orders will retain their references to the original Locations.  Thus, as Assets are moved from one Location to another, Work Order history will be accurately represented at both the Asset and the Location.

Setup Requirement:  If you are utilizing the standard AssetOptics profiles and permission sets, field level security will be updated upon upgrade.  If you are using org-specific profiles and/or permission sets, then field level security needs to be added to the Location field (Location__c) on the Work Order object (sm1a__WorkOrder__c).  The Work Order page layouts require updating to display the new Location field.  The Location page layout should be updated to display the Work Order related list.

Preventive Maintenance

UC-0410        Update Work Order trigger handler class for PMSchedule.LastWorkOrder completed reference

The Work Order trigger handler class was updated so that when the Status of a Work Order is updated to Completed and the PM Schedule is not blank, then that specific Work Order is set to the Last Work Order Completed on the PM Schedule.  Prior to this change, the PM Schedule was only getting updated if the Work Order was also the Current Work Order noted on the PM Schedule.  While this did not result in any PM Due Date calculation errors, there are fixed-interval calendar-based PM scheduling scenarios in which the Last Work Order Completed would not be accurately represented; i.e. if on a fixed-interval calendar-based PM Schedule, the Release Window (measured in Days) was greater than the Calendar Interval, then the PM Schedule Last Work Order Completed would not be correct.

FAQ – Why would one create a fixed-interval PM Schedule where the Release Window is greater than the Calendar Interval?  If you wanted to create a daily work order; i.e. a daily pre-op or checklist, and you wanted to plan and schedule all of your work orders one week in advance, then you would need to create a fixed-interval calendar-based PM Schedule with a Calendar Interval = 1 Day and a Release Window of 7 Days.  This would ensure that the daily checklist work order is created 7 days before the due date.  You would always have 7 open checklist work orders. 

Setup Requirement:  None

Inventory Management

UC-0009        Noun-Modifier Attributes on the Item Master

Noun-Modifiers are used to define MRO Inventory Attributes.  The Noun-Modifier dictionary is a two-tiered classification schema with general attributes defined within a Noun-Modifier pair.  The use of a Noun-Modifier classification schema facilitates the standardization of inventory/parts descriptions which can lead to easier parts identification, less duplicate parts, less false stock-outs, and a greater ability to source across multiple vendors.

An example of a Noun-Modifier and its associated attributes can be as follows:

Noun:               Bearings
Modifier:         Radial Ball Bearings
Attribute 1:     Flange Type
Attribute 2:     # of Rows
Attribute 3:     Seal/Shield Type
Attribute 4:     Bore Diameter
Attribute 5:     Outside Diameter
Attribute 6:     Width
Attribute 7:     Cage Material

Thus, an industry standard 6202 bearing might be represented as:

Noun:              Bearing
Modifier:         Radial Ball Bearing
Attribute 1:     Flange Type: Unmounted
Attribute 2:     # of Rows: Single
Attribute 3:     Seal/Shield: Double Seal
Attribute 4:     Bore Diameter: 15 mm
Attribute 5:     Outside Diameter: 35 mm
Attribute 6:     Width: 11 mm
Attribute 7:     Cage Material: Pressed Steel

The Description of the Item Master would then be represented as:

Bearing, Radial Ball Bearing, Flange Type: Unmounted, # of Rows: Single, Seal/Shield: Double Seal, Bore Diameter: 15 mm, Outside Diameter: 35 mm, Width: 11 mm, Cage Material: Pressed Steel

A short Description can leave out the Attribute definition and thus would be represented as:

Bearing, Radial Ball Bearing, Unmounted, Single, Double Seal, 15 mm, 35 mm, 11 mm, Pressed Steel

Setup Requirement:  If you are utilizing the standard AssetOptics profiles and permission sets, field level security will be updated upon upgrade.  If you are using org-specific profiles and/or permission sets, then security needs to be configured for the following:

1. Objects and associated fields
   1. Noun (sm1a__Noun__c)
   2. Modifier (sm1a__Modifier__c)
   3. Attribute (sm1a__Attribute__c)
   4. Item Attribute (sm1a__ItemAttribute__c)
2. New Custom fields on existing Objects
   1. Item Master (sm1a__ItemMaster__c)
      1. Noun (Noun__c)
      2. Modifier (Modifier__c)
   2. Page Layouts
      1. Item Master page layout
         1. Display Noun and Modifier fields
         2. Item Attributes related list

Installation URL

Please submit a case via the AssetOptics customer community to request the managed package installation URL.