case study: nettbuss
TRANSCRIPT
/
IRM Summit
Eventslides
1
/
Agenda
About NettBuss
High-level challenges
Specific challenges
The solution
Specifics
Delivery
2
/
About NettBuss
4
/
About NettBuss
4
/
About NettBuss
4
/
High-level challenges
Public transport operates on tendersThe tender process leads to acquisitions and on-/offboarding
4
New and existing processes must coexist or mergeThis repeats itself over time
/
High-level challenges cont’d
Only 20% of employees are office-workers
4
/
High-level challenges cont’d
Lack of integration and masterdata focus leads to data duplication with most known side effects
4
/
Specific challenges
Only 20% of employees are office-workers- Until recently communication with the majority was via phone and
mail (snail-)- Most employees have little or no IT experience- Fast-changing staffing situation causes further communication
issues
This needed to be addressed with a digital communications solution, which in turn required a solution for digital identities and lifecycle.
4
/
The solution
A key part of the solution was to introduce a new Intranet, which has the following benefits:- A central source of information to all- or company-specific
employees- Centralized access to process support tools- Browser-based
To enable this, it was necessary to implement a lifecycle for digital identities, with these additional benefits:- Single Sign-on- Password reset- Time-restricted ad-hoc access support- Tighter process integration- Standardizing on some masterdata structures and sources
4
/
The solution
4
- Full identity stack- AD/Exchange account
integration- DJ: Not everyone needs
AD accounts- Enonic intranet with
Tomcat AM agent- No custom connectors- Configuration mgmt
/
Solution delivery
Solution was delivered on estimate time & costApproximately 7 weeks duration3 resources from ConductProject manager from IT due to aspects of- Information security- Masterdata - Process- and therefore system integration
The solution is implemented under the HR department, which maps well with the organization processes and responsibilities.
Pending next step: transition to Conduct cloud operations
4
© 2001 - 2012 Conduct ASKongensgate 14, Postboks 805, Sentrum, 0104 OSLO
www.conduct.no