Hierarchy is a client's organizational structure, including levels, units, relationships, attributes, and configurations. SMG must maintain a list of all participating units and how those units are grouped (or 'roll up') at each upper level. To ensure that data rolls up appropriately, SMG requires details related to each level within the organizational Hierarchy.
Importance of Setting up a Hierarchy
The Hierarchy influences every component of the CX/EX program, from alerts to survey content to reporting and analysis.
Every SMG client must have a Hierarchy. Setting up a Hierarchy is one of the very first steps to launching a new project. Projects that have separate reporting websites must have separate Hierarchies - even if all the Hierarchy data is exactly the same.
Note: There are ways in the Hierarchy tool to have a single file import update Hierarchy for multiple projects. Talk with your SMG Account team to learn more.
A Hierarchy may maintain a one-to-one relationship (e.g., a grouping of units rolling up into the same upper Hierarchy levels) or multiple relationships (e.g., a subset of units in a grouping rolling in different Hierarchy levels).
Hierarchy Components
The 4 main components that make up the Hierarchy include:
- Units – A “unit” corresponds to an individual unit of the structure on each level (e.g., Restaurant, Area, Region, etc.) and contains all attributes for that individual unit.
- Attributes – Details for each unit. Attributes could include ID/Name, contact information, email, flags, text filters, etc.
- Level – Corresponds to the client’s corporate structure. The highest level is typically Company, and the lowest level is the Unit level.
- Relationships – Defines the rollup from Unit to Company. Outlining the relationship between each level in the organization is important to have a clear reporting structure.
Questions to Consider When Setting up Hierarchy
- What levels are included within your organization?
- What are the relationships among the levels (e.g., the lowest level, highest level)?
- What is the reporting structure (e.g., locations report to districts, districts report to regions)?
- What is used to identify each level? SMG recommends using a consistent (non-person specific) value as the ID for each level (e.g., Region 1 or West Region vs. John Doe’s Region).
- Do the levels and/or the level titles vary throughout the organization (e.g., corporate vs. franchise, domestic vs. international)?
- What information is available about each level (e.g., ID, name, email, attributes)?
- What should be displayed in reporting for units at each level (e.g., ID Only, ID + Name, Name Only)?
- Who will be the point of contact for the hierarchy and any hierarchy questions and updates?
- For EX Hierarchies:
- Do all employees have unique identifiers (e.g., employee ID, payroll ID) that remain consistent?
- What information is available at the employee level to segment data (e.g., hire date, job type)?
Hierarchy Checks for Accuracy
- For EX Hierarchies:
- Hierarchy reflects real reporting relationships (e.g., employees associated with actual non-training units, HR employees flowing into home office vs. stores, etc.).
- Hierarchy includes unique identifiers (e.g., one employee ID per employee, one district ID per district, etc.).
- The Hierarchy includes data in all fields to ensure the population of data across all levels and allow for reporting segmentation.
- Internal resources are allocated to generate hierarchy files and provide ongoing support (if necessary).
After Hierarchy has been set up, it must be maintained as changes occur within the client's organizational structure. Common updates include:
- Changes in organization structure
- Updating addresses
- Updating alerts
- Updating Callback cases
- Updating survey questions
- Adding Units
- Closing Units
Adding or Closing Units
Units at the lowest level can be made active or inactive. A unit must be active to receive surveys and be displayed on the smg360 Reporting Website. Units at each upper level are automatically made active or inactive based on whether any active units are assigned to them. To minimize file omission errors, SMG recommends your team notifies the SMG Support team when units are closed for the team to deactivate from the system. Allow 24 hours after the system processes the updates for changes to appear on the smg360 reporting website.
Updating Hierarchy guarantees the smg360 reporting platform reflects the most current information for alerts, survey content, reporting, and analysis. Hierarchy changes can be updated in the SMG system either automatically or manually.
Automated Hierarchy
Automated hierarchy allows clients to update the hierarchy as soon as changes occur by posting the updated file to an SMG-managed SFTP site. Auto Hierarchy is the preferred method to update Hierarchy because it minimizes errors and creates greater flexibility with hierarchy updates.
Automated Hierarchy File Requirements
- The file must be uploaded to SMG's secure FTP site
- File type and contents should be consistent
- File types supported: CSV, JSON, or Excel (one tab)
- Can have partial/multiple files (e.g., separate files provided by Corporate/Franchisee or countries)
- All files must be in the same format and have the same fields, mappings, and the same re-coding (i.e., one mapping per project).
- While having partial/multiple files is possible, it is not recommended. Please work with your SMG Account team to discuss the impact of this option.
How Does it Work?
- You will apply updates and/or add new units to the most recent hierarchy file. Each new file overrides the data included in the previous file.
- Verify that the new file aligns with the one used in the initial mapping (same columns and column names, all required data populated, etc.) and that the cells exclude formulas.
- Save the new file with the desired changes under a new name (e.g., Hierarchy_DDMMYYYY) (no restrictions exist for the naming convention in the SMG hierarchy system).
- Go to the SFTP site and enter the SFTP credentials provided by SMG.
- Navigate to My Folders > Incoming > Hierarchy and drag and drop your updated hierarchy file.
The SMG platform automatically detects and ingests the updated file. Survey updates controlled by the hierarchy (e.g., changes to flags that control survey metrics) go into effect in real time, and reporting updates appear on the reporting website the following day.
Note: Each time a new Hierarchy file is updated, the SMG Support team is notified when the changes are processed or if there are any errors that need to be resolved within the file.
Manual Hierarchy
As mentioned above, setting up Auto Hierarchy is the easiest and quickest way to make Hierarchy changes, especially to several units at the same. A manual import requires you to work with the SMG Account team to make Hierarchy changes.
Note: To avoid manual changes being overridden by a recurring import, you should upload an updated file instead of requesting manual changes to Hierarchy.
When a Manual Import is needed to make Hierarchy updates, reach out to your Account Team, and follow one of the below processes:
- SMG provides your team with the current Hierarchy information in an Excel file, and your team applies the updates directly in the Excel file and highlights the changes
- Your team provides SMG with a manually created file maintained by your team that conforms to automated file criteria (e.g., single flat file format, consistent column headers or column order, your generated IDs)
- Allow 3-4 business days for updates to be reflected in the system
Manual Hierarchy updates may occur up to two (2) times per month.
Hierarchy File Configurations
File integrity is crucial to maintaining your Hierarchy information. Here is a list of file configuration guidelines:
- Excel, CSV, or Text (with a defined delimiter and text qualifier, if applicable)
- Flat file format (e.g., one row for each unit at the lowest level, with all upper-level details included on the same row as unit-level details)
- All units and all data within a single file
- SMG may be able to accommodate multiple partial files pending the file format and the columns remaining consistent if limitations exist for a single file.
- Consistent labeling of column headers (if column headers are included in the file)
- A consistent order of columns (if column headers are excluded from the file)
- Unique IDs for each unit
- SMG recommends using a consistent (non-person specific) value as the ID for each level (e.g., Region 1 or West Region)
- When IDs do not exist, SMG may use the level name as the ID. However, this creates added reporting and user management complexity with leadership changes.
- Example file for initial setup required (must match the final file output)
Fixing Hierarchy issues
When a change to the file results in an error, the import process and hierarchy updates are paused. The system sends the SMG Support team an automated email notification with the failure reason details to help them determine the next steps. Upon review of the details, the SMG Support team may determine whether you need to make changes to the file. If this is the case, the SMG Support team will notify you about the changes and provide guidance on fixing the file. Larger issues may require the file to be remapped by the SMG Support team. Remapping can happen when there is a change in organizational structure or if a new attribute is added. Please work with your SMG Support team if you have questions about fixing the hierarchy.
Hierarchy is a powerful tool and can be complex. Please reach out to your SMG Account team if you have questions.
Comments
wendpark llc
need to add 2 stores to my smg
site 11133
site 71
add these 2 sites to my smg
and i need login credentials for site 11133
Please sign in to leave a comment.