In the face of rising data volume and complexity and increased need for self-service, enterprises need an effective business intelligence (BI) reference architecture to utilize BI as a key corporate asset for competitive differentiation. BI stakeholders — such as project managers, developers, data architects, enterprise architects, database administrators, and data quality specialists — may find the myriad choices and constant influx of new business requirements overwhelming. Forrester's BI reference architecture provides a framework with architectural patterns and building blocks to guide these BI stakeholders in managing BI strategy and architecture.
Enterprise information management (EIM) is complex — from a technical, organizational, and operational standpoint. But to business users, all that complexity is behind the scenes. What they need is BI, an interface to enterprise data — whether it's structured, semistructured, or unstructured. Our June 2011 Global Technology Trends Online Survey showed that BI topped even mobility — the frontrunner in recent years — as the technology most likely to provide business value over the next three years.
Like many others in the New York region, I am writing this in a cold, mostly power-less house, without landline telephone or Internet connections. Thanks to the foresight and generosity of a neighbor with a generator, we have an extension cord that is powering the refrigerator and one light, plus charging of various iPhones, iPads, and PCs. With a gas range for cooking and intact house, we are basically engaged in high-class camping, with both the pleasures and discomforts that entails.
Right now, my only electronic connection to the outside world is through my iPhone, which did provide email through the storm, though cell voice service went missing for 36 hours after Sandy hit. I am writing this on my laptop, which doesn’t have Internet access, because I refuse to write an article like this on the keypad of an iPhone. (Yes, I know, I should have bought the iPad with 3G, but do I really need to spend $600 just for that?) Once I get this written, I will head to the nearby Starbucks and use their Wi-Fi to post this blog.
What this experience has reinforced for me are four lessons:
Earlier this week, in conjunction with ARM Holdings plc’s announcement of the upcoming Cortex A53 and A57, full 64-bit CPU implementations based on the ARM V8 specification, AMD also announced that it would be designing and selling SOC (System On a Chip) products based on this technology in 2014, roughly coinciding with availability of 64-bit parts from ARM and other partners.
This is a major event in the ARM ecosystem. AMD, while much smaller than Intel, is still a multi-billion-dollar enterprise, and for the second largest vendor of x86 chips to also throw its hat into the ARM ecosystem and potentially compete with its own mainstream server and desktop CPU business is an aggressive move on the part of AMD management that carries some risk and much potential advantage.
Reduced to its essentials, what AMD announced (and in some cases hinted at):
Intention to produce A53/A57 SOC modules for multiple server segments. There was no formal statement of intentions regarding tablet/mobile devices, but it doesn’t take a rocket scientist to figure out that AMD wants a piece of this market, and ARM is a way to participate.
The announcement is wider that just the SOC silicon. AMD also hinted at making a range of IP, including its fabric architecture from the SeaMicro architecture, available in the form of “reusable IP blocks.” My interpretation is that it intends to make the fabric, reference architectures, and various SOCs available to its hardware system partners.
For some reason public safety has been a hot topic for me of late. I recently presented at ZTE’s Public Safety Summit in Dubai, where there was an audience of public safety officials and telecommunications ministry representatives from the Middle East and Africa. One element of the presentation that sparked interest and audience questions was citizen engagement.
We often think of public safety in terms of emergency services – police, fire, and ambulance; and, for many people, public safety first conjures up images of the police chasing bad guys – likely the effect of too many TV shows like Cops or Southland. But as I defined it in a previous blog, public safety covers a broad range of issues that touch a city’s inhabitants: crime prevention, traffic control, health services, public infrastructure management, and any of a list of emergency services including those for natural disasters such as earthquakes and flooding or incidents like urban wildlife sightings as well as fire or riots.
In order to better act as the eyes and ears of the city – particularly given the mandate of doing more with less – many public safety organizations are returning to a kind of community policing – through better engagement with citizens. This isn’t a new concept.