Site icon Site Title

Key benefits

Key benefits

Obtain complete organizational control

With OS GIR, all of your organizational processes are simplified, optimized and streamlined. Read more about the key benefits that OS GIR can bring to you and your organization:

OS GIR - Key benefits

In many organizations today there are numerous manual steps that come with an organizational change, and these are often time-consuming with tight deadlines. With OS GIR, the entire process of performing organizational changes is underpinned from A to Z.

If the management want a visual overview of the organization, simply use the Orgviewer in OS GIR:

The Orgviewer brings insight into all the different sections and elements of an organization, and gives you a common ground for reflecting and discussing how the future organization will look.

With the OS GIR Datepicker, you can jump ahead in time, and present the future organization by sending it to all relevant parties. This way, you are making sure that everyone is in agreement before the change launches. This reduces backflow and increases the transparency throughout the entire process.

In OS GIR you can relate IT-systems to employees and units, and when a change is to be launched in OS GIR, you can ensure that the security is in order and all necessary accesses are secured. Thereby, any disruption in the operation will be diminished when the change is done.

With OS GIR by your side, your next organizational change is supported from start to finish – with less time-waste and complete control.

Organizations often need identity data for many different purposes and roles in the organization; employees, externals (contractors, suppliers, consultants etc.), as well as individuals who have access to IT systems that support business operations.  The identity data is used in many processes, such as digital and physical access management, compliance reviews, planning activities, and displaying the different organizational structures within the organization. Identity data is an intrinsic part of any matrix organizational structure and is maintained and displayed in various IT systems, spreadsheets, databases, etc., without any governance, policies or procedures.  OS GIR provides structure to the identity data, establishes processes that underpin governance and policies, and acts as the source of truth for identity data and organizational structures. OS GIR displays the various relations an identity has to the different organizational structures, support reporting, lifecycle management processes, and can integrate to the many IT systems that use identity data. OS GIR also includes the capability that vendors can push identities to the OS GIR for identity lifecycle management of identities related to activities at the organization. A Core Identity Model creates the foundation for the implementation of the OS GIR. The Core Identity Model is an information model for identities.  The process of creating the Core Identity Model is:
  • Define the entity term
  • Identify the objects (this could be employee, external, owner, account, role, resource etc.)
  • Define the objects.
  • Create relations between the objects.
  • Add attributes to the objects.
A crucial part of the Core Identity Model is to be able to define the terminology of an entity.  An entity is: “A natural person or legal entity who wants access to an online service through Authentication with Electronic Identification Means. Entities can have multiple Electronic Identities – for example, a natural person can have both a private identity and multiple business (employee) identities.” The entity terminology will be used when linking identities.  It is common that internals become externals and vice versa which will be shown in the current ERP data, as multiple identities for the same person. For externals that return to the organization and get new initials the same will occur.  The identities should be related to an entity using a unique personal identifier. The Core Identity Model will evolve over time as more business functions use the model and more applications are connected to the OS GIR. With the Core Identity Model, an organization will be able to:
  • Eliminate redundant processes for creating identity data: Business processes can be reduced or eliminated in the processes of creating and using identity data. OS GIR will eliminate the need for specific processes for individual application use by delivering data to all relevant applications in your organization. This way, you reduce double work by not having to create the users in all applications manually.
  • Enable interoperability and identity attribute sharing: The Core Identity Model enables a common understanding of the identity attributes, which enables the basis for sharing identity attributes. By using OS GIR, the company enables the capabilities of sharing identity attributes for specific business (application) uses. 
  • Enable cost savings for identity life cycle management: Processes associated with identity life cycle management could be reduced throughout the business.
  • Heightened data quality: The Core Identity Model should enable better data quality and accuracy improvements. The processes for identity life cycle management combined with the Core Identity Model should enable an increased data quality. The consistency in identities and the distribution of identity data through automated workflows should enable the improved reliability in identity data and data accuracy.
In the process of creating an identity, a set of attributes needs to be collected to uniquely identify the person. The processes for obtaining and handling identity data are essential for the data quality and must be analyzed and if necessary improved.  The identity of the person hired must be verified using a nationally recognized photo- or biometric evidence of the claimed identity such as a passport or a driving license. The activities in this step are:
  • Map identity lifecycle processes: Identify all processes for identity lifecycle events and related processes. This should be done with the business process owners. Ensure that the attribute collection is part of the process descriptions.
  • Identify inefficiencies: The described processes, data collection and identity attributes should be examined for improvements. All data entry points should be identified, and any manual processes marked as possible improvement opportunities.
  • Document data quality level: The data collection processes should be aligned with the new capabilities in the OS GIR, and the current data quality should be documented. Improvements to the data quality (accuracy and completeness of information) and data collection processes should be documented.
  • Create a plan for process improvement: With the current business process owners, a plan for process improvement should be created. The plan should focus on streamlining the processes with the OS GIR as a focus point for identity lifecycle management. The plan should contain an action plan for the OS GIR implementation project and the business process owners.
Payroll is often the primary source for maintaining identity data for employees and most externals. Payroll receives identity information as part of the hiring process. By targeting integration and streamlining of these HR processes, it should be possible to optimize identity lifecycle management. Activities in this step are:
  • Integrate ERP and OS GIR. 
The ERP system and OS GIR should be consolidated to ensure the data quality and the identity creation processes, as well as support identity lifecycle management.
  • Establish processes for organizational changes and other identity lifecycle events. 
Streamline the process for organizational changes and other lifecycle events for identities.
  • Develop identity proofing processes. 
Ensure that the integrated background investigation processing during the hiring processes contain the necessary validation to be able to reuse the identity in all business units.  Streamlining the HR processes will enable the company to enforce the benefit realization of the previous steps and the downstream processes. Depending on the target architecture the ERP system could be the authoritative source for internal identities and the OS GIR a customer application or vice versa. 
Exit mobile version