Conclusion: There are many links between the story of data warehousing and the story of SAP adoption, going all the way back to 1997, when SAP started developing a “Reporting Server”. Over the following decade SAP firmed up its dominant position as a provider of Enterprise Resource Planning functionality, creating countless business intelligence initiatives in the wake of SAP ERP implementation projects. Up to 80% of data warehouses have become white elephants, some completely abandoned, and others have been subjected to one or more resuscitation attempts. Big data can either be the last nail in the coffin, or it can be the vaccine that turns the colour of the data warehousing elephant into a healthy grey.
Conclusion: Einstein said that “everything should be made as simple as possible, but not simpler.” This is true in enterprise architecture and project management. CIOs know that simple solutions have many benefits over complex ones. Highly complex projects have high failure rates, like highly complex architectures. However, many CIOs unwittingly encourage and reward complexity. Complexity must be viewed as a primary focus for reducing cost and risk associated with large projects. CIOs should understand some of the key steps that can lead to reduced complexity in projects and systems.
Conclusion: Unless you have a definition of the key data items for your enterprise, you will not be able to manage your data effectively. Astute CIOs have an understanding of the key data items that their organisation relies on for effective decision-making.
An enterprise data model documents the data in your organisation. It is a key enterprise architecture asset that enables more effective data management as well as offering the CIO the ability to reduce duplication and provide a higher level of service to the organisation.
Conclusion: As the market for Board Portals rapidly matures, IT organisations are being asked to assist in selecting and implementing a solution. This is a golden opportunity to raise the IT Organisation’s profile with some of the most influential people in the company.
The CIO must ensure that technical staff do not overcomplicate the project and must find an Executive sponsor who can manage the Board members’ requirements and expectations.
Conclusion: Organisations looking to develop and deploy mobile applications must realise that the mobile device market will undergo significant change over the next five years. This creates serious challenges for developers within enterprises, who must either create applications for specific devices and different form factors, or attempt to develop cross-platform applications that will still meet end-user expectations. IBRS has identified four high-level architectures for developing mobile applications, each of which has specific strengths and weaknesses. This research provides an overview of these architectures.
Conclusion: Pattern-based and repeatable processes, such as gathering operational data, validating data, and assessing data quality, offer potential for automation. The Web and software-as-a-service technologies offer powerful tools that facilitate automation beyond the simple mechanical pumping of data from one system to the next. Operational management tasks that focus on administration and control can and should be automated, so that managers have time to think about the organisation as a system, and can focus on continuous improvement.
Conclusion: The implementation of Business Intelligence is critical to the optimised operation of even the most basic business functions. When executed well it provides quantifiable competitive advantage for private sector organisations, and improved service delivery outcomes for the public sector.
IT has a significant opportunity to enhance its business relevance by ensuring that Business Intelligence best practice is active and transparent across the organisation. Organisations without a comprehensive investment and capability in Business Intelligence will struggle to complete and will operate below their potential.
Conclusion: Does every organisation need a dedicated ECM system? Not necessarily. Given the breadth of the topic, it is common to use a combination of different systems to adequately address enterprise wide management of content. When embarking on an ECM initiative, it is important to set clear priorities, and to explicitly define the limits of scope, otherwise the solution that is developed may primarily be a costly distraction.
Conclusion: SharePoint is well known as a platform for small-scale knowledge management, team collaboration, and Web applications. However, some organisations have begun experimenting with SharePoint as an alternative to large-scale Enterprise Content Management (ECM) solutions, handling more than 100 million documents. The lessons learned from these initiatives indicate that while SharePoint can deliver ECM, such projects require a great many technical and planning skills that are foreign to most SharePoint implementation teams in Australia. It is almost certain you will need to hire short-term project specialists to be successful.
Conclusion: CIOs today are often faced with deciding whether to buy integrated systems solutions and services from major vendors or buy best of breed solutions from multiple vendors and manage the integration project in-house.
Organisations that have engaged external services providers on a major scale and eroded their IT skills base typically find they have no option but to buy the integrated solution. Conversely those with specialist skills in-house and the need to develop their people, often find in-house systems integration solutions more attractive.