Sam Higgins is an IBRS Advisor over 20 years of both tactical and strategic experience in the application of information and communications technology (ICT) to achieve business outcomes from large complex organisations. Through previous roles as a leading ICT executive, strategist, architect, industry analyst, program consultant and advisor, Sam has developed an extensive knowledge of key markets including as-a-Service (Cloud) computing, enterprise architecture (including service-orientation and information management), enterprise applications and development, business intelligence; along with ICT management and governance practices such as ICT planning, strategic sourcing, portfolio and project management. Sam’s knowledge of service-oriented architecture and associated business models is widely recognised, and he was a contributing author on the Paul Allen book Service-orientation: Winning Strategies and Best Practices, released in 2006 by Cambridge University Press. As the former Research Director for Longhaus he undertook the first in depth research into the implications of cloud computing and other “as-a-Service” ICT offerings on the Australian and near shore markets. The 2010 report entitled, Defining cloud computing highlights provider gaps in the Australian ICT market, was widely reported in both the online ICT industry press and mainstream media.
Conclusion: The development of AI-based solutions is heavily dependent on various types of data input in the form of either:
- Large data sets used to conduct experiments to develop models and algorithms for predictive analytics, optimisation and decision recommendations; or
- Enriched and tagged corpuses of images, audio, video and unstructured text used to train neural networks using deep learning techniques.
While at first the data management needs of AI-based solution development might leverage both data scientists and their existing business intelligence platforms to exploit these types of data, the actual lifecycle management needs of AI developers will expand quickly beyond the boundary of the traditional enterprise data warehouse.
Therefore, like the source code and configuration data underpinning transactional business applications, the raw data and algorithms of AI solutions must be managed by evolving DevOps practices towards a comprehensive “DataOps” model.
01 April 2018
Conclusion: Although online digital platforms are in ready supply, organisations remain unable to avoid the receipt of critical information in the form of paper documents or scanned images. Whether from government, suppliers or clients, organisations are faced with written correspondence, typed material, completed forms or signed documents that must be consumed. For a variety of reasons, it may be unreasonable or impractical to expect this information to be sent in machine-readable form.
However, machine-readable content from incoming information, both past and future, is emerging as a prerequisite to exploit artificial intelligence and machine learning as part of digital transformation. Therefore, organisations need to re-examine their data ingestion strategies and move proactively to the use of optical character recognition on incoming paper- and scanned image-based information.
06 March 2018
Conclusion: Organisations continue to emphasise their competitive differentiation based on the data they hold, and the insights gained from analysing this valuable resource. The rate at which organisations are shifting from traditional process-based to insight-oriented differentiation is being further accelerated by the adoption of Cloud-based data analytics services.
The combined result is an increasing portion of enterprise project activity that can be classified as extract, transform and load (ETL).
Despite ETL being the mainstay of data integration for decades, the cost of specialised skills and significant manual effort expended on integrating disparate data sources is now coming into sharp focus. In response, organisations are rightly seeking lower-cost solutions for data integration.
Although ETL exists in the form of at least one tool in almost every enterprise, the cost of ETL as a proportion of data analytics projects means organisations must decrease reliance on traditional ETL tools in favour of automated solutions that exploit machine learning techniques to reduce the need for ETL developers.
02 February 2018
- IBRS iQ
01 February 2018
Conclusion: The release of Amazon’s Echo in 2014 heralded the first of a series of “ambient” technologies1. These new devices are unobtrusive, multiple purpose and capable of responding to conversational input through integration with virtual digital assistants (VDAs) such as Amazon’s Alexa.
A key enabler of these platforms is the ability to implement “skills” or expand the platform’s capability to interpret and respond with appropriate conversational content beyond the basic function of the device itself.
The consistency of information required by organisations under omni-channel delivery models, combined with under-resourced editorial teams, mean organisations must prepare for conversational channels by transforming existing content sooner rather than later.
Failure to do so will see history repeat itself through short-term replication of content to support new channels only to have that content and channel functionality merged back into increasingly sophisticated content management platforms at significant cost.
04 January 2018
Conclusion: Technologists consistently under-estimate the growth of data volumes. The result is tactical actions aimed at increasing capacity achieved by adding storage on-premise using traditional bulk storage solutions or moving technical workloads, such as back-up or disaster recovery, to Cloud-based Storage-as-a-Service offerings. This reflects a decades-old mantra of “disk is cheap, buy more disk”.
When the lack of predictability of data volume growth is combined with the need to capture then distribute data from new sources as well as control the hidden cost of data movement across networks, these tactical responses fail to deliver transformational value to end users.
To deliver effective and efficient data storage solutions, IT infrastructure architects must collaborate with their information and data management colleagues to identify the demographics of data being managed1; they must then select storage solutions that optimise data capture, storage, distribution and access based on these characteristics, not simply by volume.
03 December 2017
Conclusion: Despite repeated audits pointing to failures by IT to deliver expected outcomes, organisations continue to publish IT plans that do not adequately address the fundamental dimensions of IT planning, being the IT Business Plan, IT Strategies and IT Program of Work.
These elements are often developed as a single composite document, but this approach fails to recognise that each dimension:
- requires a different method of creation
- is owned by different stakeholder groups
- has a different purpose and audience
- requires renewal on different cycles.
Failure to ensure that all dimensions are addressed presents risks to implementation both in terms of effective up-front investment selection as well as ongoing IT governance arising from gaps in critical decision-making information.
To avoid these risks, organisations should maintain the content of each IT planning element as a separate deliverable even if the desire, or requirement, is to regularly produce an “annually” updated composite document.
- Governance & Planning
03 November 2017
Conclusion: The current wave of digital transformation will see the retirement of large numbers of legacy systems. Although the cost of operations, including storage of data, in newer Cloud-based solutions is often cheaper, the cost of migration of historical data to new platforms can be significant. IBRS has observed increasing numbers of digital transformation projects where the decision is being made to preserve legacy systems using back-up infrastructure techniques at the application and/or database level without any reference to regulatory records management requirements.
Many legacy systems were not designed with a long-term view of key business records and information they capture and generate, nor are back-up technologies designed for long-term archival and retrieval of individual records. The result of these strategies is the potential for access to official records and chains of evidence to be interrupted – a situation likely to be viewed by regulators and stakeholders as a failure of the organisation’s record-keeping obligations.
03 October 2017
Conclusion: When undertaking business-oriented transformation programs, such as the current wave of digital transformation, it is important for Enterprise Architects to develop an EA for IT in parallel – not as a separate or independent IT transformation effort.
Establishing the EA for IT requires that the IT organisation itself becomes the “enterprise” in context, ensuring that IT has a true business blueprint that reflects the needs of its wider organisational context. This will require that Enterprise Architects identify an effective set of contemporary reference models for what it means to deliver IT in an As-a-Service world.
- Operations & Service Delivery
03 September 2017
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.
- IBRS iQ
10 August 2017