Get started with OS GIR
Process start in 1-2-3
In the implementation of OS GIR, a typical project contains three phases – Installation and cleansing, analysis and prioritization, and finally, automation. On this page we will illustrate the implementation process from start to finish.
OS GIR brings you complete control over the people connected to your organization whether they are employees, externals, volunteers, interns, etc. It also enables the possibility of planning organizational changes and maintaining numerous organizations within your organization – especially if you must handle a complex matrix or agile organization. Read more about the key benefits of OS GIR here.
Process start in 1-2-3
In the implementation of OS GIR, a typical project contains three phases – Installation and cleansing, analysis and prioritization, and finally, automation. On this page we will illustrate the implementation process from start to finish.
OS GIR brings you complete control over the people connected to your organization whether they are employees, externals, volunteers, interns, etc. It also enables the possibility of planning organizational changes and maintaining many organizations within your organization – especially if you must handle a complex matrix or agile organization. Read more about the key benefits of OS GIR here.
To get started with OS GIR and take advantage of the benefits of the system, the three phases need to be completed:
GET STARTED
To get started with OS GIR and take advantage of the benefits of the system, the three phases need to be completed:
1
Install and cleanse
Install and populate OS GIR to clean up data and consolidate identities
In this step OS GIR is installed, and data are consolidated from various identity sources.
The purpose is to establish a ‘well of truth’ and thus enabling the diffusion of identities into other it-systems, e.g. an IGA platform.
Different branches of the organization are also ingested to get the full overview and to enable management of the organizations.
2
Analyze and prioritize
Scrutinize the system landscape and the workflow processes
The system landscape is mapped and system integrations are identified.
A GAP analysis pertaining to workflow processes is established in order to define a to-be state.
The results of the analyses will define the next step, ‘Automate’.
3
Automate
Development of system integrations and automation of processes
This step depends on the analyses in the previous step.
Both system and workflow processes will be underpinned, and automation will occur.
The bullets below give examples of automated processes.
- Infrastructural setup and security
- Installation of OS GIR as-is
- Data clean-up and test
- Ingestion of cleansed identities and organizational units
- Enrichment of data from other sources
- Heightened data quality
- System landscape analysis
- Workflow process analysis
- Definition of data model and organizational principles
- Governance and policy creation
- Prioritized action plan
- Continuous ingest from HR/ERP
- Integration with IGA platform, cantine system, Active Directory(s)
- Identity attestations
- Organizational diagram on the intranet
- Automatic termination of licenses and system accesses
- Request management
1
Install and cleanse
Install and populate OS GIR to clean up data and consolidate identities
In this step OS GIR is installed, and data are consolidated from various identity sources.
The purpose is to establish a ‘well of truth’ and thus enabling the diffusion of identities into other it-systems, e.g. and IGA platform.
Different branches of the organization are also ingested to get the full overview and to enable management of the organizations.
- Infrastructural setup and security
- Installation of OS GIR as-is
- Data clean-up and test
- Ingest of cleansed identities and organizational units
- Enrichment of data from other sources
- Heighten data quality
2
Analyze and prioritize
Scrutinize the system landscape and the workflow processes
The system landscape is mapped and system intergrations are identified.
A GAP analysis pertaining to workflow processes is established in order to define a to-be state.
The results of the analyses will define the next step, ‘Automate’.
- System landscape analysis
- Workflow process analysis
- Define data model and organizational principles
- Governance and policy creation
- Prioritized action plan
3
Automate
Development of system integrations and automation of processes
This step depends on the analyses in the previous step.
Both system and workflow processes will be underpinned, and automation will occur.
The bullets below give examples of automated processes.
- Continuous ingest from HR/ERP
- Integration with IGA platform, cantine system, Active Directory(s)
- Identity attestations
- Organizational diagram on the intranet
- Automatic termination of licenses and system accesses
- Request processes
Our delivery model
Magenta presents a delivery model for agile development.
Pre-analysis
The first thing we do is to examine your business case. Preliminary analysis will often alert you to even more benefits that can be achieved. Have you considered what the actual time savings will be? Will an employee’s workflow become more intuitive or precise? Is there a focus on the core message? What are the specific success metrics? Are there specific KPIs that need to be improved?
The outcome of the pre-analysis is a basic understanding of your needs, a strengthened business case and an understanding of the scope of the project.
Business case-analysis
One of the first things we look at is where your new solution creates value: is it for a specific user group? Is it making work process more efficient?
User Surveys
We are conducting initial surveys of users. How high is the demand? Is there already a solution? If so, how does it work and how can it be improved?
Scope Analysis
The understanding of the scope of the solution is nuanced as the pre-analysis progresses, and at the end of the phase we qualify the estimate for the development of your solution.
Analysis
You rarely start building a house without consulting your plans with an architect, builders etc. The same concept applies when developing an IT-project. One of the most important aspects of IT-development is planning out the process. This is one of the safest ways to ensure budget and quality. To work in an agile environment with incremental processes is one of the ways to ensure a successful analysis. This creates a solid foundation for your further development – from backend architecture to specific userflows and visual expression.
When the analysis is complete you will have specific documentation that resonates our common understanding of the project and how we move further. It is a must to reconsolidate our expectations, to reach the goal of a succesful project.
IT-architecture
As part of this phase, we will develop documentation for architecture, API, which technologies that needs to be applied, and everything else relevant to the technical aspect of this project.
User-friendly design
Usability surveys will determine the user processes and the design of the interface.
Project plan
As part of the analysis, we create the overall project plan where we map all of the milestones and clarify the extent of the project.
Agile development
At Magenta we prefer to work in an agile manner with emphasis on incremental distribution. This means that we work intensely on delivering as fast as possible, all the while we invite our customers to contribute to the process. Any functionality will be tested thoroughly together with the customer. This creates transparency and leaves you with the opportunity to change whatever you want during the development. The ability to change is a core aspect of our distribution. If interested, you can even be a part of our SCRUM-meetings as a ‘product-owner’ and test it from the get go (MVP).
Development prints
We typically plan 2-4 weeks ahead and then intensely work on getting the functional aspects, so you will be able to test it right away.
User-tests
To ensure that every piece of functionality meets the quality standards of the customer, everything will be tested by a QA-team defined in the beginning of the project.
Ongoing prioritization
To work with incremental development means that you can prioritize our milestones. This ensures that what adds the most value is prioritized first.
Delivery
After the development is completed, the next step is to implement the project. We review the delivery and shake hands on a successful project. The delivery process may vary but the key focus is that both of us walk away happy!
As the last step of the process we will sit down together and evaluate the project: What went well, and what could have been done better? This way, our mutual learnings will help us improve any further projects.
Delivery test
Here we formally approve of the product. How this is done vary on the projects size. This is also the part where we shake hands and agree whether the project is done.
The implementation
The finished product will be implemented and the ownership will go to your organisation. If you want to run the solution, we will ensure that you have the necessary knowledge.
Operation maturation
When the product is implemented and running, we will make a test to ensure that everything is running smoothly. After this the operation is over.
Processes within os gir
All processes within the OS GIR system are described and divided into five categories:
| Processes pertaining to Organizations | Processes pertaining to Identities | Advanced processes in the UI |
| Advanced processes in the External UI | Advanced processes regarding data imports and exports |
