Document Actions
Managing the Risk of Lock-in
Managing the risk of lock-in. Open Standards; Open Competition; No Constraints.
In defining your IT infrastructure – hardware, software and applications – one of your key objectives is to create the maximum amount of agility in terms of future procurement decisions.
The problem is, the use of proprietary (as opposed to open) standards compromises this objective. This is the main factor, far more than any other, that creates risk – and the exposure to lock-in.
Transformational Government, and the creation of a citizen-focused, shared services environment, implies change in the IT infrastructure. And the fact that lock-in may already exist will inhibit the effectiveness and the benefits to be gained from transformation.
The problem has been that there is no way to assess the exposure to the risk of lock-in – until now.
Certified Open supports an organisation to develop all aspects of an open environment.
Both by encouraging a mix and match of proprietary and Open Source Software, and by ensuring both internal and supplier staff have the level of skills necessary.
Certified Open creates the framework that allows your suppliers to identify the level of openness of their products, services and staff. And by insisting that your solution suppliers assess against this framework, you will be able to identify the risk of lock-in before you undertake the key tasks of rearchitecting your infrastructure to the demands of transformational government.
Certified Open provides a fully graded “kitemark” of openness; and that, in turn, allows you to identify current exposure as well as minimising the risk of exposure in the future. And that, after all, is the hallmark of risk management – to identify the risk before it occurs!
Managing the Risks of Lock-in
1. Portfolio Analysis – ensure you have a comprehensive register of all of the elements within your environment which constitute risk of lock-in.
2. Assess Openness – challenge the suppliers of each element to provide you with a statement of openness based on Certified Open’s Products & Services framework.
3. Validate Responses – review the suppliers against the Open Source Academy’s validation program on the OSA web site.
4. Identify Problem Areas – identify those areas that constitute risk within the Certified Open Framework.
5. Risk Mitigation – press the suppliers that constitute risk to provide evidence of their proposals to mitigate the risk they represent.
In defining your IT infrastructure – hardware, software and applications – one of your key objectives is to create the maximum amount of agility in terms of future procurement decisions.
The problem is, the use of proprietary (as opposed to open) standards compromises this objective. This is the main factor, far more than any other, that creates risk – and the exposure to lock-in.
Transformational Government, and the creation of a citizen-focused, shared services environment, implies change in the IT infrastructure. And the fact that lock-in may already exist will inhibit the effectiveness and the benefits to be gained from transformation.
The problem has been that there is no way to assess the exposure to the risk of lock-in – until now.
Certified Open supports an organisation to develop all aspects of an open environment.
Both by encouraging a mix and match of proprietary and Open Source Software, and by ensuring both internal and supplier staff have the level of skills necessary.
Certified Open creates the framework that allows your suppliers to identify the level of openness of their products, services and staff. And by insisting that your solution suppliers assess against this framework, you will be able to identify the risk of lock-in before you undertake the key tasks of rearchitecting your infrastructure to the demands of transformational government.
Certified Open provides a fully graded “kitemark” of openness; and that, in turn, allows you to identify current exposure as well as minimising the risk of exposure in the future. And that, after all, is the hallmark of risk management – to identify the risk before it occurs!
Managing the Risks of Lock-in
1. Portfolio Analysis – ensure you have a comprehensive register of all of the elements within your environment which constitute risk of lock-in.
2. Assess Openness – challenge the suppliers of each element to provide you with a statement of openness based on Certified Open’s Products & Services framework.
3. Validate Responses – review the suppliers against the Open Source Academy’s validation program on the OSA web site.
4. Identify Problem Areas – identify those areas that constitute risk within the Certified Open Framework.
5. Risk Mitigation – press the suppliers that constitute risk to provide evidence of their proposals to mitigate the risk they represent.
UK
Forgot your password?