--- title: EM Implementation Overview slug: em-implementation-overview createdAt: 2024-10-15T14:46:32.766Z --- # Objective This document outlines the typical activities that occur during a new implementation of Entity Management (EM). It is meant to help you understand your level of involvement in the implementation so that you can plan appropriately, ensuring a smooth implementation experience.  # Onboarding Activities The list of activities and related information in the table below provides a summary of the typical activities that occur during a new implementation. The **Sequence** column shows the typical order of activities during a new implementation. | **Sequence** | **Component** | **Kingland Responsibility** | **Client Responsibility ** | | ------------ | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Application Data | - Setup Standard Legal Entity Data | * Review Legal Entity Data Fields | | 2 | Dashboard | - Setup standard dashboard configuration and standard dashboard widgets - Review standard dashboard and widgets with client - Implement any customized dashboard widgets or layouts as necessary | * Review standard dashboard configuration and standard dashboard widgets and document any changes needed * Review dashboard changes once development has been completed and provide sign-off | | 3 | Data Integration Framework | - Provide API Batch integration information - Provide client support when integrating with APIs to import or export data | * Review API documentation with IT teams and document any questions for Kingland * Execute integration and coordinate with Kingland for any needed support | | 4 | Data Model  | - Setup standard data fields, data displays, data privacy rules - Review standard data fields, data displays, data privacy rules with client - Implement any modifications to data fields, data displays, data privacy rules - Review client needs for any calculated fields - Implement required calculated fields | * Review standard data fields, display, privacy, and calculated fields, and document any changes that are needed * Review requested changes and provide sign-off | | 5 | Designation Inheritance  | | | | 6 | Entity Export  | | | | 7 | Entity Search | - Setup standard "stop words", "synonyms" and weightings - Implement any modifications to existing values or add new values as necessary | * Review standard "stop words", "synonyms" and weightings and document any changes needed * Review search customization changes and provide sign-off | | 8 | Group Management  | | | | 9 | Import Management | | | | 10 | Language Administration  | | | | 11 | Legal Entity | | - Display  | | 12 | My Tasks | | | | 13 | Natural Person | | | | 14 | Notifications  | * Setup standard notifications * Review standard notifications with client * Implement any modifications to existing notifications or create new notifications and necessary * Configure variable substitutions (e.g., replace $ASSIGNEE with assigned user's email address)  | - Review standard rules, workflows, and notifications and document any changes that are needed - Review rule, workflow, and notification changes once development has been completed and provide sign-off | | 15 | Operational Support | * Introduce to primary client contacts and Kingland client support lead to each other * Create the client users responsible for ticket handling and awareness in the Kingland service desk * Facilitate Kingland service desk training sessions * Identify and establish operational routines with client | - Identify which client users will be responsible for reporting and handling support tickets - Identify which client users need/want to be able to see tickets for informational purposes - Provide guidance to Kingland regarding designated support team members and contact information - Ensure appropriate support team members attend training and understand the support process and expectations | | 16 | Reference Data | * Setup standard reference data values * Review standard reference data with client * Implement any modifications or new reference data values as necessary  | - Review standard reference data values and document any changes needed - Review reference data changes and provide sign-off | | 17 | Rules Management  | * Setup standard rule definitions * Review standard rules with client * Implement any modifications or new rules as necessary | - Review standard rules, workflows, and notifications and document any changes that are needed - Review rule, workflow, and notification changes once development has been completed and provide sign-off | | 18 | Role Management | | | | 19 | Search Action Button Customization | * Review standard Action button functions with client (i.e., View Details, View Entity Restrictions) * Setup custom Action button link | - Review standard search Action button options and document any custom option that needs to be added - Review search Action changes and provide sign-off | | 20 | sFTP  Entity Import | * Set up a batch job to translate client entity data into predefined format and place on sFTP server for import | - Provide entity data in the required format and test file import and export - Verify that imported and exported entity data is correct and provide sign-off | | 21 | System Environment Setup | * Setup base environment * Create AWS Accounts (UAT and Production) * Define AWS network and access * Configure environment deployment infrastructure  | - Provide domain and URLs needed to set up the environment | | 22 | Third-Party Search Customization | * Provide API to call Search directly and return the results in a standard format | - Review standard "stop words", "synonyms" and weightings and document any changes needed - Review search customization changes and provide sign-off | | 23 | UI Content Customization | * Setup standard page content * Review standard page content with client * Implement any customizations to existing page content as necessary  | - Review default page & notification content and document any changes needed - Review changes once development has been completed and provide sign-off | | 24 | UI Branding | * Identify and document the client branding template for implementation throughout the system: - Brand colors - Brand logos and favicon - Brand typeface and styling - Backgrounds | - Provide corporate branding guidelines - Review branding changes once development has been completed and provide sign-off | | 25 | User Authentication: SAML SSO, API Integration, HR Import | * Review authentication methods with client * Setup the selected User Authentication method | - Provide decision on which User Authentication method should be used - Provide user import files, if applicable - Provide appropriate documentation and IT support to complete the integration or import | | 26 | User Permissions | | * Review out of box permissions  * Configure permissions to clients need | | 27 | Workflow Management | - Setup standard workflows - Review standard workflows with client - Implement any modifications or new workflows as necessary | * Review standard rules, workflows, and notifications and document any changes that are needed * Review rule, workflow, and notification changes once development has been completed and provide sign-off | | 28 | Workflow Process and Drawer | - Setup standard workflows - Review standard workflows with client - Implement any modifications or new workflows as necessary | * Review standard rules, workflows, and notifications and document any changes that are needed * Review rule, workflow, and notification changes once development has been completed and provide sign-off |