Once an Organisation has been created in Serendata, it is time to identify and stipulate the Core Data. It is this information that essentially allows you to manage and process Change. Depicted below are the elements within Core Data that must be gathered, validated and entered into Serendata.
It is essential to be aware that Sysdoc can set up all Core Data however the data will need to be supplied by the Client.
Core Data can be described the foundation on which all outputs will be driven from.
Creating Core Data
Step | Action |
1 | Click Note: The Cog displays all sections that need to be completed in order. |
2 | Select Core Data. |
in the bottom left-hand corner of the Home Screen.
Core Data is broken down into the following categories:
Business Areas
Locations
Roles
Processes
Action Types
Impact Types
Labels
People
Core Data | Description |
Business Areas | Business Areas are functional business areas within your Organisation. For Example: Finance and Administration, Marketing and Sales and Learning. There are pre-existing Business Areas that have been set up in Serendata but they can be fully edited to reflect your Organisation. Each Business Area can be expanded out to input Sub Business Areas. |
Locations | Locations refers to the Locations in which you operate. This could be an office, call centre, factory etc. For Example: United Kingdom, Australia and America. There are pre-existing Locations that have been set up in Serendata but they can be fully edited to reflect the Locations in which your Organisation operates. Each Business Area can be expanded out to input Sub Business Areas. For Example: United Kingdom – London and Newcastle. |
Roles | Roles refers to all Business Roles that exist within the Organisation that are applicable to the Change Project. For Example: Advertising Specialist and Brand Manager. There are pre-existing Roles that have been set up in Serendata but they can be fully edited to reflect the Roles that exist within your Organisation. |
Processes | Processes refer to the new or changing Business and Change Processes being impacted by the Project. Processes can be broken down into a maximum of 5 levels. For Example: Order to Cash >> Accounts Receivable >> AR Close. Once the Processes have been captured and inputted, this data can be copied across into the relevant Project(s). |
Action Types | Action Types refer to groupings of Action Types. For Example: Communications, Training and Development. There are pre-existing Action Types that have been set up in Serendata but they can be fully edited to reflect the Action Groupings that will come about as a result of the Project. |
Impact Types | Impact Types refer to groupings of Impact Types that the Project bring about. For Example: Behavioural, Data and Role. There are pre-existing Impact Types that have been set up in Serendata but they can be fully edited to reflect the Impact Types that will come about as a result of the Project. |
Labels | Labels are an organisational tool that allows you to attach additional notes to an element within Serendata. For Example: This could be to an Action or Impact. To provide extra information that might not be included elsewhere in Insight, can be attached to Actions, Impacts, processes etc. |
People | People refer to all individuals that are relevant and part of the Change Management Programme. From this stage their Business Roles can be added and imported into Projects as Stakeholders. |
There are also key icons that displayed and used throughout this action. Those icons are:
Core Data | Description |
| This icon represents Edit. This allows data that has already been entered into the system to be edited. |
 | This icon represents Create. This allows new data to be created in Serendata. |
| This icon represents Delete. This icon allows pre-existing data to be deleted from Serendata. |
 | This icon represents Expand All. |
 | This icon represents Collapse All. |
This completes the guide for Introduction to Core Data.
