Tango Maintenance - Business Structures

Modified on Tue, 3 Mar at 1:03 AM

Overview

The April and May Sprints have introduced a new feature in the Maintenance application that Tango is calling Business Structures. With this new functionality, clients can now assign different Problem Code Matrices to different Buildings/Stores.

Clients can create additional Problem Code Matrices as per their business requirements. Business Structures are created for each Matrix, and Locations are assigned to the Business Structures (1 Business Structure per Location). When the Locations are selected on a Service Request, the application can determine which Matrix values are used based on the Location > Business Structure > Matrix relationship.

The Maintenance product has also been updated to support Business Structures on Scheduled Maintenance but in this case the Business Structure is selected directly on Tab 1 before the Matrix values are populated. Locations added to the Scheduled Maintenance must also be associated to the selected Business Structure.

Even though existing end user Roles for Facilities Admin and Facility Matrix Admin do provide access to set up Business Structure data, Client configuration is still needed to enabled Business Structure functionality which requires Services involvement.

This article provides details on the various updates now available, focusing on the setup aspect of the new functionality.

Business Structure Functionality

Business Structure functionality setup requires 2 existing Roles:

  1. Facilities Admin
    • User Guide: Please click here.
  2. Facility Matrix Admin
    • User Guide: Please click here.

Note: It is entirely acceptable for a single user to have both of these roles assigned.

Business Structure Example

The content below is also provided in the Facility Matrix Admin User Guide:

As mentioned above, Business Structure in Edge is a way to categorize and group locations. The intent is that those Locations all use the same Matrix, and different Business Structures can use different matrices. The level of granularity is up to the client and is not directly tied to any specific Location related data or geography, although a client could create the Business Structures to mirror geographic regions and/or for just a single specific Location, if desired.

Note: Business Structure/Matrix override is not enabled in Tango by default and requires configuration by the Tango team.

This concept allows the use of different Matrix values per Location (or set of Locations) when creating Requests and Scheduled Maintenance in Edge. The different Business Structure matrices could be configured to have different NTEs and SLAs, and possibly other downstream fields, but the Issue Type, Impacted Area and Problem Code options would remain the same as a best practice.

Note: At this time there is no support for a Business Structure matrix/ dynamic matrix values on the Core and Mobile Service Request, which is why the Level 1-3 values should remain the same across all Business Structure Matrix Items and the Core Matrix values.

First, the Facility Matrix Admin user creates a new Facility Matrix record for each Business Structure required by the client.

In this example the Facility Matrix is named TX_HQ_Facility_Matrix:


Note: There is no Matrix data loaded here, but there would be a Datasource file created per Facility Matrix and Items generated through the Register button process, with Item Lookups added per Vendor Acceptance Window and SLA value.

Next, the Facilities Admin user (this could be the same user as above if given both Roles), creates a Business Structure that will use the new Facility Matrix.

In this example the Business Structure is named Texas Headquarters Business Structure:

Find the new TX_HQ_Facility_Matrix record in the Default Matrix lookup field:


Note: This is where the Name and Description are used and why it might be important to follow a meaningful naming convention if the list of available Matrix records will be long.

Finally, the Facilities Admin user can add the Headquarters location(s) into the Assigned Locations for this Business Structure.

Once the data is set up (assuming Business Structure functionality has been enabled for the client), every time a Service Request is created for those Locations, the Matrix values will pull from TX_HQ_Facility_Matrix instead of from the default Facility_Matrix.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article