Your technology should adapt to future demands and work with existing technologies, processes and infrastructure in your organisation.
To meet point 9 of the Technology Code of Practice your plan or design must show how your technology project or programme integrates into your organisation.
You’ll have to explain how you’re doing this as part of the spend control process.
How integration helps your programme
Good integration means making sure your new technology works with legacy solutions without limiting your ability to adapt to future demands or upgrade systems.
Your programme will benefit from:
- less risk to your infrastructure as integration planning will discover compatibility gaps in the new technology
- less downtime on your regular processes when you upgrade or amend them
- systems which enforce built-in redundancy of services, minimising single points of failure
- lower long-term support costs
Fitting new technology into your organisation
Each organisation’s technology and infrastructure will have services and issues that are unique. There are some common elements to consider when fitting new technology into your current or legacy system, including:
- how different aspects of your organisation’s IT operating model come together, including business areas such as processes, governance, service support and service delivery
- how the new technology will work with your service management
- what skills and capabilities your organisation needs to deliver, support and continuously improve the new technology you’ll purchase
To optimise systems integration consider:
- adopting a continuous integration model so you can solve smaller issues iteratively (this is generally easier and cheaper than waiting to test everything at the end of a programme)
- designing your system using independently developed components that can easily work together
- building a system architecture early in the program to describe your current or future system and mapping hardware and software components
- defining a configuration management process
- doing component-level testing to make sure integration is possible
- doing regular integration and stress testing in your development environment to track progress and make sure the system remains robust
If you have chosen to use a systems integrator you should make sure they meet all of your requirements.
When managing system processes and service management integration aim to:
- define the governance, processes, tools and information required to meet business needs and user needs
- map and track the interdependencies between the infrastructure and the services running on it
- provide support to the infrastructure and make sure you have the flexibility to add hardware and software
- be flexible so that processes can incorporate legacy and new infrastructure, including the use of cloud services
- understand the probable lifespan of your technologies (being aware of expiry and renewal timings) and create a roadmap showing your plan for retiring legacy systems
System integration is important for the overall network performance and for considering your organisation’s service management.
Service management depends on how your current infrastructure is managed, what new technology is being integrated and what the longer-term business objectives are for IT in the organisation.