ICT Modernisation

Conclusion: One strategy to implement IT-as-a-Service models is to build an in-house capability whereby the IT organisation is accountable for the full service delivery according to commercial practices. This requires the IT organisation to play the role of an internal service broker, expected to acquire external services and coordinate internal and external services delivery to meet the business needs. The service broker should at least be flexible, reliable and cost effective.

IBRS iQ is a database of Client inquiries and is designed to get you talking to our Advisors about these topics in the context of your organisation in order to provide tailored advice for your needs.

Conclusion: IBRS’ finding is that prominent Cloud marketplaces (CMPs) such as AWS Marketplace1, Microsoft Azure2, Google Cloud Platform3 and IBM Bluemix4 are gaining traction as alternatives to conventional enterprise ICT infrastructure and services sourcing.

Given the state of maturity of these marketplaces, they are currently only useful for quickly and conveniently locating and obtaining ICT infrastructure and microservices for use in low-risk small scale pilots or trials.

As wider take-up is underway with larger applications being adopted through AWS and Azure organisations should begin to prepare for a shift in the viability of enterprise-level solutions.

Our caution is that CMPs will not have profound impacts on enterprise ICT provision until both the IT and Procurement organisations within a business become satisfied that this approach has validity, value and is auditable5 and manageable.

Conclusion: Employ a bottom-up technology-based approach and a top-down business approach when developing the business and IT transformation program. Additionally, the program must take a pragmatic approach to reflect workplace changes that are feasible to meet the expectations of clients, staff, suppliers and the community.

Unless the program is continually revised to reflect the changing business and technology environment, it runs the risk of addressing yesterday’s problems. When benefits expected are not being realised, as indicated immediately below, it is important to implement turnaround strategies.

 IBRS iQ is a database of Client inquiries and is designed to get you talking to our Advisors about these topics in the context of your organisation in order to provide tailored advice for your needs.
 

Conclusion: Transitioning to hybrid Cloud might include migration from the current outsourcing contracts and some in-sourced activities to IT-as-a-Service models. The rationale is to accelerate efficiency gains realisation in a timely manner. One of the Procurement Manager’s options is to seek a service broker (e. g. prime contractor) to efficiently undertake the migration without disrupting the current business operations.

IT Procurement Managers should:

  • Establish governance arrangements underpinned by an effective organisational structure, tools and processes to select the service broker
  • Request the acceptance of the transition plan to become a prerequisite to contract signature
  • Manage the new contract until the business objectives are met

One of the migration critical success factors is a detailed transition plan covering the service provider selection and setting the foundation of a healthy relationship between both parties throughout the contract duration.

Conclusion: Executives trying to put ambitious and commendable goals in place may not appreciate the clarification that they may see as downgrading their original goal. When IT is asked to provide systems to support ambitious goals, the executive team needs to make sure the costs are understood and any ramifications that may result in significant changes or investment in IT solutions to support the goals are clearly identified and costed.

Having corporate goals or strategies as a focus to help employees know what is to be achieved is commendable and a proven approach to getting individuals and teams to focus on specific targets or outcomes. But setting the targets too high can come at a cost that is not justified or that may result in a continual investment in trying to achieve something that is beyond the organisation. It can also be unnecessary when the goal only requires the organisation to be delivering better than the nearest competitor, or be providing a unique offering or service that defines the organisation and sets it apart from others in the market.

Conclusion: Although automation is actively being introduced through digital transformation projects, it may still be a minor part of the technological mix for a few years. The main reason for the potentially slower progress with automation is the relatively mixed economic background. In some specific instances, it is an obvious option but otherwise its benefits will be ambiguous for some time.

In these foreseeable circumstances it may be that business as usual (BAU) is the overriding strategic principle.

Limited resources and a lack of skilled staff are holding back councils' IT plans. Australia's local councils are under increasing pressure to modernise their operations and improve on-line service delivery for residents, but many are starved of the funds and skills to achieve those goals. These are the key findings of a report from IBRS into local government IT management. The report - Winds of Change also Sweeping Local Government - found that local government IT leaders are grappling with demands to simultaneously improve online customer-centric service delivery while reducing operating expenses.

Full Story

Conclusion: IT organisations initiating efficiency improvement programs should automate inter-process interaction, focus on measurement and refine inter-group communication. This will enhance service availability, reduce delivery cost and enrich end user experience.

Conclusion: IT organisations wishing to maximise the ROI of as-a-Service contracts must transform the relationship management role from contract focus (i. e. whereby the mindset is to create a win/lose scenario) to a value focus whereby business benefits are realised. This demands building advanced skills in negotiation, communication and consulting. It is also necessary to extend the Relationship Manager’s role to one which ensures as-a-Service policies are developed, security policies are adhered to and external providers’ deliverables are synchronised with those of internal service providers.

Conclusion: With the migration to complex hybrid sourcing strategies, traditional IT organisations based on ‘plan/build/run’ models will not be suitable for acquiring Cloud services in an increasingly changing market. This is due to a vague understanding of service total cost of ownership and limited contract negotiation and management skills. IT organisations wishing to rely on external services must evolve to ‘plan/procure/govern’ structure to emphasise strategic service planning and hire specialised service providers’ governance skills. This shift should ensure mutual trust and respect between parties, well-defined service levels and clear roles and responsibilities. IBRS estimates the cost of the governance structure and services to be 3 %-7 % of the annual contract value. This must be considered during the business case preparation.

Conclusion: IT-as-a-Service is an initiative launched by IT organisations to fix an IT problem, whilst digital transformation is another initiative launched by business lines to fix a business problem. However, fixing both problems remains an enterprise’s critical issue. Hence, organisations wishing to remove the duplication between the two programs should unify both programs and ensure sufficient funds are available to implement the unified program in a timely and cost effective manner.

Conclusion: The enterprise architect (EA) role is one of the most intellectually challenging in an organisation. This is because it involves developing a systems roadmap to migrate from the current to a desired future state that is compatible with the business strategy.

Assign the wrong person to the EA role and the future systems will probably be unattainable and realising the business strategy problematic.

In this interview, Dr Wissam Raffoul outlines a practical and effective approach to migrating to an As-a-Service model. 

Sydney-based IT analysis firm IBRS has launched maturity assessment and methodology tools to assist organisations with the task of SaaS migration.

In order to improve business performance, or reduce the cost of doing business, forward-thinking IT organisations are trying to run IT as a service (ITaaS), said Dr Wissam Raffoul from IBRS.

“There are many challenges; for example, long software implementation time lines, fragmented delivery processes, as well as insufficient skilled resources to meet business demands,” said Dr Raffoul.

Full Story

Conclusion: While IaaS and PaaS adoption has been increasing, most IT organisations are hesitant to migrate their legacy systems to public SaaS. This is primarily due to the applications being highly customised resulting in a significant effort being required to retrofit existing systems to migrate them to public SaaS architecture in the Cloud.

Conclusion: Opposition to workplace change stemming from the organisation’s digital strategy agenda1 is inevitable. Astute IT managers expect it and identify initiatives to minimise opposition.

Digital strategy (or transformation) initiatives typically generate both overt and covert workplace resistance. Its sources may vary from situations such as:

  • Senior managers who fear that failure could adversely impact their career
  • Overworked middle managers claiming they cannot cope with more workplace change
  • IT professionals maintaining legacy systems not prepared to learn new skills.

Managers responsible for driving digital strategy agenda must identify where resistance is likely and determine how to minimise it. Assuming no resistance to it is unwise. Alternately, continually questioning the agenda may not reflect opposition but an indication staff are determining how to best implement it.

Conclusion: There are distinct differences between traditional outsourcing, managed services and as-a-service contracts. Traditional outsourcing and managed services are input-based contracts with a fixed price based on the number of the supplier team members delivering the service, service levels that do not reflect business operations and significant financial penalties when exiting for convenience.

As-a-service contracts are outcome-based contracts, priced on a consumption basis, measured by service levels that reflect end-user experience and no exit fees.

IT organisations should analyse the advantages and disadvantages of each alternative whilst formulating their sourcing and Cloud migration strategies.

Conclusion: Serverless programming is a new paradigm for developing and running Cloud-native solutions. It holds the promise of creating far more scalable solutions that ‘stitch together’ other Cloud services, making it the much-needed ‘programmatic underpinning’ for the Cloud. It is as significant a shift in software development as object orientation was from procedural programming in the 1980s.

However, serverless programming is immature, and its use cases not well understood. The timing for development teams to engage with serverless programming is largely dependent upon an organisation’s appetite for adopting bleeding-edge, Cloud-based services. The more services being adopted, the sooner the team should begin to learn this new programming paradigm. Even when used, care should be taken to limit the scope of deployment of serverless programs.

Conclusion: One of IT organisations’ objectives must be to reduce the total service cost of legacy applications by migrating them to a Cloud environment. However, achievement of the desired success largely lies in limiting the scope variations of Application-as-a-Service contracts and controlling the hidden cost drivers. This requires leveraging the lessons learnt in containing outsourcing cost and establishing flexible contracts in the legacy environment. Failure to do so may extend the legacy system lifetime and leave IT organisations with no alternative but to absorb the increased cost of application management on an ongoing basis.

Conclusion: The Total Cost of Ownership (TCO) was created two decades ago to provide visibility of the total cost of IT assets. It was targeted at IT organisations running an in-house mode of operations. While TCO can provide a good understanding of the internal IT asset cost, it could not estimate the cost per service because the IT budget was never based on service delivery. As a result, it was neither adequate to buy external services nor sufficient to assess the value that an IT organisation can bring to the business lines. IT organisations should adopt the Total Cost of Service (TCS) model to accurately estimate services’ internal costs, benchmark the external services cost and justify the services costs in terms of business imperatives.

Workforce transformation embraces far more than just mobility: it embraces not only where work gets done, but how, when and by whom. Much has been written about the fact that many jobs will cease to exist, while many others will transform beyond all recognition. And the impact these workforce changes will have on hiring practices and the structure of business is significant.

Conclusion: Business prefers certainty to doubt and some issues now appear to be clear:

  • Full deployment of Australia’s National Broadband Network now seems likely within about 5 years.
  • Its funding method and construction costs will create broadband access with higher prices than current ISP charges and those of Australia’s trading partners.
  • Enterprises now need to act in self-interest to review and plan their access networks for branch offices and customer service.

Conclusion: The drive for digital disruption has forced many organisations to implement contact centres’ online chat facilities (or equivalent). The rationale is to instantly connect customers with service experts and to resolve inquiries at the first contact whenever possible. While customers enjoy the ability to initiate a chat anytime and from any device, the ability of service providers to resolve inquiries to customers’ satisfaction remains unfulfilled in many cases, especially in the telecommunication carriers industry. Organisations should realise that a digital transformation is not only about implementing online facilities; it requires significant business process re-engineering to improve end-user experience across all types of inquiries.

Conclusion: Even though stakeholders may support ‘Digital’ initiatives – due in no small part to the all-encompassing nature of the term ‘Digital’ in today’s market – many of these initiatives will fail to deliver on the original intent. This is because the term ‘Digital’ enables stakeholders to reinterpret the intent of an initiative in a number of different ways. This can cause stakeholders – both within ICT groups and within the organisation more broadly – to take actions that deviate from the original intent, or that resist attempts to change. Even when organisations have put in place governance and processes to reconfirm stakeholders’ understanding of the initiative’s intentions, reinterpretations and misaligned actions can still occur.

By understanding the types of ‘mutation’ that stem from the use of ‘Digital’, and by appreciating the limitations of traditional methods of checking stakeholder alignment, policy and program leads can minimise the risk of projects being implemented in unexpected ways.

IBRS iQ is a database of Client inquiries and is designed to get you talking to our Advisors about these topics in the context of your organisation in order to provide tailored advice for your needs.

Conclusion: IT organisations driving their business transformation should mature their as-a-Service capability to deliver IT services at commercial standards in a timely and cost-effective manner. This should lead to effective delivery through the integration of business and IT processes.

Conclusion: The Australian Bureau of Statistics’ annual innovation survey quantifies the efforts of businesses in all industries. The status of innovation is quite mixed, between small businesses which tinker at the edges and larger enterprises which are more thorough.

Innovation is not one thing – it is a variety of actions which can be implemented. Improving technological capability is not a high priority and that could be a concern for CIOs, CTOs, CDOs and vendors because the purpose and value of technology, and related investments, appear less directly important to business.

IBRS iQ is a database of Client inquiries and is designed to get you talking to our Advisors about these topics in the context of your organisation in order to provide tailored advice for your needs.

Conclusion: Traditional disaster recovery plans do not mitigate risks against frequent software and hardware malfunction, nor do they integrate with business continuity plans. As a result, a production service may become unavailable for up to two days in certain cases (e. g. recovery from a database outage or data corruption). In the digital world, the business impact of such a failure will be significant as clients may place their orders with a competitor when they face an unavailable service for a prolonged period of time. IT organisations should deliver recovery-as-a-service that provides non-stop business operations.

Conclusion: Just as every marketable motor vehicle needs skilful designers and a proficient driver to reach its destination, an organisation needs visionary leaders and skilled staff to digitally transform its business model.

Technology, whilst important, represents just one wheel of the motor vehicle. Overstating technology’s value is simplistic. Vendors who promote technology, and their solution, as the cornerstone of the digital transformation strategy do themselves a disservice.

IBRS iQ is a database of Client inquiries and is designed to get you talking to our Advisors about these topics in the context of your organisation in order to provide tailored advice for your needs.

Conclusion: Organisations typically discuss the selection of enterprise mobility development in terms of web-based applications versus native applications, which quickly leads to debates regarding cross-platform tools versus standardising on one platform, such as iOS or Windows10. This is entirely the wrong way to think about enterprise mobile application development, resulting in unsustainable portfolios of fragmented and increasingly difficult to maintain applications. Instead, organisations should first identify the generalised use cases (i.e. common patterns of work) and seek to select mobile solution architectures (as opposed development tools) that meet each use case.

Conclusion: There is debate within the IT industry whether or not DevOps can replace ITIL1. From ITIL perspective, many IT organisations, especially in Australia, have been implementing ITIL processes since 1994 with significant investment in technology and professional services. Hence, it is impractical to just drop ITIL and adopt DevOps. This is because firstly, DevOps covers only Release Management which is only one process of the 26 processes of ITIL v3 and secondly, DevOps in not different from mature2 ITIL Release Management. In this light, existing ITIL organisations embarking on digital transformation should plan to mature Release Management to match DevOps principles. DevOps3 sites need to leverage the lessons learnt from ITIL implementation to enjoy a smooth business transformation as fixing only the software release process without integrating this with the remaining 25 ITIL processes is insufficient to raise the overall IT performance to the level needed by the digital world. This research outlines that ITIL and DevOps can co-exist in the same organisation once brought to the right maturity level.

This Compass is a companion document to IBRS’ Master Advisory Presentation (MAP) “Delivering Digital Business Transformation” which outlines business and management issues and provides guidance on delivering an effective digital business transformation.

Conclusion: IT organisations driving their business transformation should mature their internal consulting function to connect with business units’ service quality expectations. This should lead to consistent delivery, facilitate knowledge sharing and realise business benefits.

Conclusion: While the increased adoption of public IaaS1 can reduce cost and simplify technology procurement challenges, IaaS does not meet all IT organisations’ sourcing requirements such as legacy applications maintenance and IT service management. Hence, IT organisations are left with no alternative but to use multiple service providers to satisfy all their needs. This will increase clients’ governance cost of service providers and extend the duration of external services acquisition. As a result, a service broker model has emerged to provide one single point of accountability to all sourcing deliverables, simplify go-to-market strategies and fulfil the Cloud migration requirements in a cost-effective manner. IT organisations should assess the applicability of this model to their environment.

Conclusion: To facilitate business and IT transformation PMOs must be given a role that puts them at the forefront of advising management where best to invest scarce resources in business and IT-related projects whilst ensuring business systems are successfully implemented.

To be successful PMO staff need:

  • People management skills to help project managers reach their potential
  • Business acumen to assess competing claims for funds for business systems projects
  • To be able to shape management’s expectations of what IT can and cannot deliver.

Conclusion: Forward thinking IT organisations wishing to create a service differentiation should analyse their value activities to construct a “uniqueness capability”. The outcome should convince business lines that IT services can generate business value at a competitive price. The value chain firstly requires to address service delivery processes by constructing the IT value chain1 , secondly to realise cost advantage2 and thirdly to create service differentiation (this note).

Conclusion: IT organisations establishing business relationship management to excel at coordinating business and IT strategic matters should assess the current maturity of this role. The rationale is to allow IT to deliver solutions that improve business performance, reduce the cost of doing business and mitigate business risks.

Conclusion: IT organisations should not be treating software releases to support the digital transformation as “business as usual”, because they may overlook the demand for extra-company IT management process integration, rapid application deployment, and speedy problem resolution. IT organisations should recreate their “release to production” processes to address the new applications’ unique requirements for appropriate security, resilient architecture, and elevated service level standards.

Conclusion: Deployment of Office 365 as a pure Cloud solution has lagged the sales of Office 365 licences. This is partly due to lack of formal migration strategies, confusion over the licensing and user options1, although non-technical issues play a bigger role. To assist in the move to Office 365, IBRS has identified a framework that will assist organisations in their journey.

Conclusion: Cost advantage can be achieved by firstly, estimating the existing services costs. Secondly, use cost effective external services. Thirdly, integrate services. Fourthly, retain cost advantage. This can be achieved by removing duplicated activities and influencing cost drivers.

Conclusion: Traditional on-premises approaches to infrastructure can create unnecessary costs, risks and bottlenecks. This is particularly a problem for projects delivering new systems that have a high-risk (i. e., uncertain benefits, functionality, capacity) which are often associated with innovation and digital strategies.

IT organisations should look at alternative methods for delivering IT infrastructure to ensure it is not a barrier to business innovation.

Conclusion: Although virtualisation is widespread in computing and storage, software-defined everything (SDE) is 3–5 years away from broad adoption by enterprises. Early adopters are major ICT Service Providers and enterprises with specific opportunities.

Enterprise architects need to understand the implications of SDE now as Cloud and managed services projects using software-defined technologies ramp up, or risk becoming irrelevant and wedded to displaced traditional sourcing and delivery concepts.

Failure to appreciate the impacts of software-defined ICT will mean that businesses will be making planning and budget decisions today for ICT futures based only on current practices that are becoming superceded. 

When the leadership of IT and business management work well as a team there are few limits to what they can achieve in delivering services to clients. However for the teamwork to become a reality line management and IT professionals must put aside special interests and focus on implementing initiatives that deliver outcomes that meet the objectives of the organisation.

Agility is achieved when the team is able to quickly identify the source of a problem or business opportunity, corral their resources and expertise and respond with alacrity.

One area where teams struggle is identifying and putting into practice the guiding principles under which they will pool their resources.

This MAP is designed to guide and stimulate discussion between business and technology groups, and point the way for more detailed activity. It also provides links to further reading to support these follow-up activities.

Conclusion: Many IT organisations are perceived by their business units as high cost/low quality service providers. Much of this perception is due to the IT group’s inability to successfully articulate service value, demonstrate cost competitiveness, and create internal service differentiation. IT organisations should construct service value chain models to diagnose the IT organisation’s deficiencies, improve image, and link to vendors’ value chains. This can be achieved by disaggregating the business of IT into its strategic activities (e. g. service definition and communication, customer service). This will result in understanding the cost behaviour and identifying existing and potential differentiation sources such as accelerating the release of business products to market and improving IT and business lines interaction.

Conclusion: While technology is becoming increasingly critical to business transformation, IT organisations are becoming less important to business stakeholders. This is because enterprise architecture practice’s main focus remains on back-office systems and on initiatives that do not necessarily contribute to business performance improvement and business cost reduction initiatives. IT organisations should revive the enterprise architecture practice by delivering IT-as-a-Service with an outward focus targeting business, information, applications, and infrastructure domains. This will increase IT organisations’ credibility to become key players in business transformation projects.

Conclusion:Within the ICT industry new technology is deferred to as the catalyst of innovation. While this is partially true at the current time and over the next 3-5 years, the shifting structure of the wider economy is the more likely agent of transformation, and even perhaps of disruption, which will be seen through the adoption of various technologies.

Conclusion: The term ‘digital disruption’ exerts a powerful cocktail of possibilities. While the term has limited application in specific cases, its general use has diluted its meaning. Whether this is significant may be judged individually but the general use of digital disruption to any and all events coinciding with the introduction of new technologies is misleading.

For the most part executives and strategists can understand technologies and their implementation as progressive evolution. This is especially true for buyers of technology. For some technology vendors and industries the effect of digital technologies may be disruptive, even destructive, insofar as markets, capital and stock value are lost.

Conclusion: The Service Catalogue required by the ITIL framework has undergone several variations during the last 20 years. The rationale was to address the emerging service trends in in-house and outsourced modes of operations. However, while the original service catalogues’ objectives were achieved, they are inadequate in acquiring hybrid Cloud core services (e. g. storage) that should be delivered under outcome-based service contracts.

Conclusion: Since 1994 many Australian IT organisations have been implementing Configuration Management practices. However, it has been done with limited success when assessed against the key objectives of Configuration Management process and its associated database (CMDB) in terms of service availability and configuration items interdependencies. IT organisations should review their Configuration Management plans in view of the latest public Cloud offerings and adopt a phased implementation approach.

Conclusion: Microsoft’s consumer-led strategy for Windows 10 will create ‘pester power’ for the new OS within the enterprise. However, simply upgrading to Windows 10 will re-entrench old assumptions, and continue an out-dated SOE model, yet with no additional business value. An alternative approach is to delay the introduction of Window 10 while a new digital workspaces strategy is developed to transform the business environment. A digital workspace strategy will take time to define and execute, so the CIO must prepare activities to avoid the negative impact of pester-power, while engaging the business in a re-envisioning of the work environment.

Conclusion: One IT-as-a-Service strategy remains to migrate legacy systems to SaaS to reduce cost, improve service level and achieve excellence in end user experience. However, large-scale ERP SaaS migrations are still not imminent, primarily due to the significant ERP customisation made by Australian organisations during the last twenty years, which prevent the use of standard SaaS architecture without re-engineering the business processes. However, it is worth noting that there are third party ERP maintenance and support services, which used in the short term may result in up-to 50 % reduction in the current yearly maintenance and support cost.

Conclusion: Based on usage patterns and personalisation MCPs (Smartphones and Tablets) offer an opportunity to build a more intimate relationship with customers. While there is great opportunity there are some technology and cultural challenges that need to be addressed.

Conclusion: Digital disruption is now a given in every industry vertical, although each is impacted in its own distinctive ways.

The drivers for connecting everything and transforming business are the desires for improving corporate agility and personal productivity. The use of utility information and communications technologies (ICT) such as Cloud and Mobility is proving to be a key enabler of Digital Transformation for any size of private or public sector business in any sector.

Transformation, agility and productivity are coming from hyper-connected people and processes.

Conclusion: IT organisations adopting IT-as-a-Service strategies tend to acquire the best of breed services from the market instead of building them in-house. This leads to increased adoption of multi-sourced services, whereby reliable governance processes are critical success factors to realise the desired business benefits in a timely and cost-effective manner.

Conclusion: in the publication ‘Running-IT-as-a-Service part 4’, IBRS defined how Service Value Agreements can be constructed by correlating business performance metrics with IT service levels. This note describes how Service Value Agreements can be constructed by aligning IT service levels with business service levels and processes. As a result, meeting or exceeding SLA targets will demonstrate the IT organisation’s contribution to business performance improvement and cost reduction undertakings.

Conclusion: organisations planning to move to Microsoft Cloud-based Office 365 should first examine and segment their workforce to identify the most appropriate mix of Office 365 editions (which Microsoft calls SKUs) for staff, and then examine Microsoft’s various licensing options. Organisations with existing enterprise agreements need to be particularly careful with the latter, not so much to avoid compliance issues, but rather to minimise spend.

Conclusion: the adoption of Cloud-based applications and data, the proliferation of mobile devices (i.e. Smartphones and Tablets) and the increased interest in BYOD is driving a radical change in end user computing. The old device-centric model, based on a stateful Windows desktop, is being replaced by an application-centric model where device state is transient. While this is not yet the end of the Windows desktop, the beginning of the end has arrived.

Conclusion: when managing both client server (legacy) and Anything-as-a-Service (XaaS) environment it is important the legacy environment does not constrain the potentially superior XaaS environment.

Conclusion: IT organisations adopting IT-as-a-Service practices are often challenged by limited resources to meet service demands, especially in the IT Operations space. IT operations groups should develop supply/demand models that link to business priorities and ensure funds allocation. These models will enable IT organisations to meet client necessities, clear workload backlogs, and set the foundation for effective resource management methods.

Conclusion: softening business conditions in Australia demand that IT operations executives find current cost (cash) savings, optimise the cost of existing operations and/or make valuable new contributions to the enterprise by leveraging networking technologies and practices throughout IT.

IBRS has identified ten practical ways to cut enterprise networking costs while preparing to execute a business’s digital strategy.

Expect to obtain a mix of cost savings, cost optimisation and revenue contributions from networking. Aim to create business insights into making savings from using communications creatively rather than just connecting data, processes, devices and people.

Conclusion: with the increased adoption of SaaS for business systems (e. g. ERP), new SaaS providers continue to appear in the market. While those providers are offering easy-to-use products and low start-up costs compared to running in-house business systems services, there is a risk that some service providers might cease to do business. As a result, SaaS clients will be at risk recovering services on time and without data loss. To address this issue, several escrow services have been evolving. IT organisations wishing to migrate critical services to public SaaS should explore escrow1 services. Unfortunately, escrow service costs have to-date been fully absorbed by the buyer. In this light, IT organisations should incorporate the escrow services cost into the SaaS migration business case.

Conclusion: To meet the demand for more online services, IT and business management must identify and filter the opportunities and vigorously pursue those with high client visibility, ensure adherence to legislation and reduce the cost of doing business.

Conclusion: When moving from traditional on-premises IT to Cloud it is important to update the Business Leaders and Executive on the risks. Rather than try to quantify the absolute risks, as the first step in gaining acceptance, explain how the risks of Cloud compare with the current on-premises, or MSP, solution. Offer ideas on risk mitigation that might be necessary and liberally apply simple examples and analogies to aid comprehension.

Conclusion: Running IT-as-a-Service requires offering broad IT services tied to external-value that goes beyond meeting or exceeding SLA targets. This is because the majority of existing SLAs are IT centric and vaguely relate to business value. Much of this issue is related to IT Groups’ lack of business analysis skills and IT ad hoc methods to comprehend business strategic requirements. As a result, business lines perceive IT as a support function instead of being a strategic business partner.

Conclusion: The first generation of the Internet of Things (IoT) is now reliably internetworking uniquely identifiable embedded computer devices.

However, the emerging Internet of Everything (IoE) will go beyond the IoT and its machine-to-machine (M2M) communications between devices, systems and services. The demands from popular consumer IT will lead to a broad adoption of IoE in enterprises although corporations will focus on the IoE for its business process improvement.

Use of common collaboration tools will become the most prevalent and valuable way to extend isolated low level IoT interactions into sophisticated orchestrated IoE apps that deliver valuable experiences and tangible benefits to both consumers and corporate users.

Many Australian IT organisations have been implementing Configuration Management practices since 1994. However, with limited success when assessed against the key objectives of Configuration Management process and its associated database (CMDB).

Conclusion: Cloud migration should not be a quick and dirty job just to upload the current business systems with their inefficiencies, only to get rid of the in-house hardware ownership. It should be considered as an opportunity to clean IT and business inefficiencies at the same time. IT organisations wishing to migrate to public Cloud require a new methodology to avoid incurring unforeseen consumption cost and to address business processes overheads. Strategies are needed to measure code inefficiencies and develop a remedy roadmap whilst building the case for public Cloud. Only efficient code should be released to public Cloud unless there are other benefits which make the overall migration cost-effective. This will ensure IaaS usage remains within IT budget.

Conclusion: To reduce Service Desk costs and improve resources scheduling, some IT organisations are exploring the potential of Virtual Service Desk Agents to either improve self-service and/or reach to the right subject matter expert at the right time. However self-service success depends on the quality of information available to the virtual agents. It is critical for the virtual agent tool to be enabled by a mature service management engine that describes the service’s known errors and their resolution alternatives. Failure to do so will leave the virtual agent with no alternative but to call the live agents, thereby making the investment in virtual agent technology questionable.

Conclusion: The popularity and growth of online social media platforms has pushed social data into the spotlight. Humans using the Web mainly interact with human-produced data. Yet the floods of machine-generated data that flow through the Internet remain invisible to humans. For a number of reasons attempts by organisations to mine big social data to improve marketing and to increase sales will fall significantly short of expectations. Data from digital devices and sensor networks that are part of the Internet of Things is eclipsing human produced data. Machines have replaced humans as the most social species on the planet, and this must inform the approach to data science and the development of healthy economic ecosystems.

Conclusion: IT organisations developing IT policies in isolation from business units1 will face challenges to tie policies to business drivers and limit policies acceptance rate. IT organisations should formulate policies by involving business units at an early stage in policy scope discussion. IT best practices2 should be leveraged to develop reliable and practical policies. The resources needed to develop the new policies should come from both sides and a business benefits realisation plan should jointly be developed and tracked.

Conclusion: The development of new digital services often entails not only changes to workflows but also changes to the business rules that must be enforced by software. Whilst vendors of business rule engine technology often market their products as powerful and highly generic tools, the best results are achieved when restricting the use of the different approaches to specific use cases.

Conclusion: Business-centric IT strategies are critical to run IT-as-a-Service1 because they attempt to integrate IT with business strategies. The rationale is to support business operations by implementing new technologies that reduce business risks, create business opportunities and achieve high levels of customer satisfaction.

Business-centric IT strategies focus on addressing the business critical issues by implementing new IT solutions in a timely and cost-effective manner. The proposed IT solutions should provide capabilities that address the current and emerging market forces such as consumerisation, mobility, social media and Cloud. This will signal to business lines that IT is being modernised to meet consumers’ exigent needs.

It is critical for business-centric IT strategies to be developed within two months to accelerate IT-as-a-Service transitioning.

Conclusion: Vendor offerings for end-to-end solutions for ‘self-service desktops’ are both limited and immature. Furthermore, organisations are likely to have many of the individual components that comprise a self-service desktop solution. For the next 4-6 years end-user computing cycle, organisations should look to construct self-service portals from existing point solutions, rather than looking for a pre-integrated stack.

Conclusion: To improve business performance and/or reduce the cost of doing business, forward-thinking IT organisations are trying to run IT as a Service. However, they are challenged by long software implementation timescales, fragmented delivery processes and insufficient skilled resources to meet business demands.

To address these challenges, IT organisations should emulate the commercial practices related to delivering quality IT solutions at reasonable costs.

Conclusion: There are many different Hybrid Cloud approaches, each with different costs, risks and benefits. Organisations should evaluate the alternatives to find which is best aligned to their business requirements, then update IT governance processes to guide the organisation towards the chosen Hybrid Cloud strategy. Failure to align to the right Hybrid Cloud strategy will either result in the creation of new IT silos, which becomes a barrier to the business strategy, or will adopt an approach that stifles business innovation and agility.

Conclusion: While many IT organisations believe that using public IaaS (e.g. AWS, Microsoft Azure, Google) to host business applications is a cost-effective strategy, the lack of IaaS usage planning will most likely increase consumption cost. IBRS recommends that IT organisations undertake a self-assessment of their usage management practices prior to migration to public IaaS1.

Conclusion: The Standard Operating Environment (SOE) desktop has long been considered a best practice and is widely used. However, in recent years consumer IT has dramatically changed users’ expectations resulting in frequent complaints that the SOE desktop is inflexible and a hindrance to doing business.

With corporate supplied desktop continuing to be a key application access platform for the foreseeable future, IT organisations need to find an approach that meet the user’s expectations while controlling complexity, manageability, security and cost. One solution is a Dynamic Desktop1 extended with a self-service portal that emulates an ‘app store’ experience.

Conclusion: IT organisations' lack of IaaS usage planning will most likely increase consumption cost. As a result, IT organisations should work closely with business units to understand usage patterns and track monthly usage against forecasts. This will more likely ensure that IaaS usage levels remain within budget. This note provides the usage management framework. Part 2 planned for release in August 2014 will provide User Management maturity self-assessment approach.

Conclusion: WhileI SaaS and PaaS adoption has been increasing during the last two years, most IT organisations are hesitant to migrate their legacy systems to public SaaS. This is primarily due to the applications being highly customised to support the current business mode of operations. As a result, migration to cloud requires significant effort to retrofit the existing systems in public SaaS architecture. One of the options to address the customisation obstacle is to adopt a rapid business process redesign approach.

Conclusions: Based on cost modelling, organisations looking to provide a ‘Windows virtual desktop’ experience should consider centralised, Windows Server OS based computing as opposed to Windows Desktop OS based computing. In addition to lower costs for hardware and simpler management and deployment, Windows Server OS based computing has a licensing model that can be just 25% of the cost of Windows Desktop OS based computing. Furthermore, Windows Server OS based computing licensing provides for greater freedom of where and on what devices the end-user desktop experience may be deployed.

While IBM is planning to invest A$1.4 million to grow its global datacentre facilities, its focus remains on private cloud with no serious public cloud offerings, As a result, IT organisations under traditional outsourcing contracts with IBM should examine the feasibility and cost-effectiveness of third party public cloud alternatives prior to renewing the existing outsourcing contracts.1

Conclusion: Organisations that need to run legacy applications under Windows XP will no longer have access to economically sustainable options. In short, there is no way to maintain an XP environment without Software Assurance, and thus there is no practical way for an organisation to continue to run legacy applications without investing in Software Assurance or Enterprise Agreements for the desktop. Organisations should factor in the significant licensing costs when considering the business case for continued support of ‘XP only’ to legacy applications.

Conclusion: With the migration to complex hybrid sourcing strategies, traditional IT organisations based on ‘plan/build/run’ models won’t be suitable for acquiring public cloud services in an increasingly changing market. This is due to vague understanding of service total cost of ownership and limited contract negotiation skills. IT organisations wishing to rely on external services must evolve to ‘plan/procure/govern’ structure to emphasise strategic service planning and hire specialised service procurement skills. This paradigm shift requires CIOs to restructure IT procurement with a view to run it as-a-service to other IT groups and business lines.

Conclusion: Organisations that do not upgrade their major assets to reflect new technologies and practices quickly fall by the wayside. Similarly, organisations that do not critically review the effectiveness of their ERP solution, and either replace it or reinvigorate it, are failing their stakeholders.

Conclusion: IT organisations wishing to maximise Public Cloud return on investment should adopt a Cloud Governance Maturity Model that ensures consistent delivery, builds trust and leverages new technology. This will enable IT organisations to effectively manage their sourcing portfolio by balancing cost and risks, creating value and realising the desired benefits.

Conclusion: In-house IT Service Management (ITSM) initiatives require considerable time and investment (up-to three years, up-to $1.5 million approximately). This has resulted in limited senior management continuous buy-in and reduced ITSM benefits realisation. Therefore, IT organisations wishing to implement ITSM should evaluate a public cloud alternative versus the cost and merits of establishing in-house service management capability.

Conclusion: Some SaaS service providers can exercise ‘exit for convenience’ contractual terms by giving no more than thirty days termination notice. As a result, SaaS users will be at a high risk to recover services on time and without data loss. Therefore, IT organisations wishing to migrate critical services to public SaaS should develop a Contingency Plan and test it regularly. The Contingency Plan establishment cost should be incorporated into the business case for public SaaS migration.

Conclusion: Mobile devices have fundamentally different patching and upgrade cycles compared to the desktop models of which IT services staff are familiar. The key differences are: more frequent refresh cycles, cloud-based updates that generally are not manageable by the organisation, Internet-based rather than intranet-based delivery of upgrades. Managing mobile patches and upgrades will more about end-user communication, training, and change management than technology.

Conclusion: IT organisations wishing to migrate in-house services to public cloud should ensure that service providers understand the complexity of the in-house architecture candidate for cloud migration. This can be achieved by identifying the in-house service failure points within the legacy applications and their associated infrastructure. The service providers’ lack of understanding of the existing operational weaknesses will most likely extend the transition period and delay achieving the expected service levels in a gradual and cost-effective manner.

Conclusion: IT organisations managing a multi-sourced environment and wishing to reduce unscheduled service downtime, should establish end-to-end Change Management Frameworks. This will ensure that business operations remain unaffected by service providers’ system changes.

Conclusion: Given previous uncertainties regarding the future of TRIM, and dissatisfaction with what is perceived to be onerous knowledge management, IBRS has noted that many organisations are considering replacing TRIM with SharePoint. Simply migrating to SharePoint will not alleviate the perceived problems associated with TRIM, nor indeed traditional EDRMS in general. Organisations should recognise that while knowledge management is more important than ever, it will not be met with a single solution. Instead, multiple repositories for different types of knowledge, at different stages of the knowledge lifecycle will be required.

Conclusion: Given that the public cloud value is maximised when end-to-end SaaS is reached, IT organisations’ misunderstanding of SaaS building blocks, business applications architecture integration and lack of mature multi-sourced environment governance will limit SaaS public cloud adoption. CIOs should establish a cloud sourcing strategy to assess the feasibility and cost effectiveness to gradually migrate business applications to public cloud. Failure to do so might minimise public cloud opportunity to improve enterprises’ performance and/or reduce the cost of doing business.

Conclusion: Microsoft’s licensing for its end user products (Windows, Office) attempts to straddle the old desktop-bound paradigm and the new user-centric paradigm brought to the fore by mobility, cloud services and consumerisation of end points. This has resulted in a fragmented and complex set of intertwined usage rights that can confound even the most astute procurement specialist. The only workable approach is to prepare long-term scenarios that deal with specific end-user situations and have Microsoft develop and confirm the licensing requirement in writing prior to deployment: plan for more dynamic application deployment, but externalise the effort, time, costs and risk of the licensing decision back to Microsoft.

Conclusion: The challenge for all organisations is to understand the technology options and work practices that will ensure the durability of the organisation. The rise and acceptance of social media tools is one example of this challenge. Those organisations that have adopted activity based working offer one possible path. For others there may be a combination of work designs and solutions that serve them best.

IT executives should play a role in the decisions that are made on how work is conducted in the future and the technologies to enable the new processes.

Conclusion: Deciding to transition the organisation to activity based working (ABW) will be complicated by meeting various stakeholder interests and aligning the organisation’s culture. In this sense it may involve several iterations. Each one refined from lessons of the previous one.To reduce risk it is essential that the ABW checklist be precise about the objectives and the organisation’s capacity to transition to a new working model.

Conclusion: Organisations looking at building enterprise mobile applications too often put the device selection and coding tools selection as their primary concerns. Instead, organisations should be focusing on identifying the mobility architectures need to support business strategy. Technological priorities then become identification of broad mobile service platforms, integration infrastructure and abstraction of the client.