Decision-making and authority placed nearest the real-time data, circa 1854.
"Daniel McCallum created the first organization chart in response to the information problem hobbling one of the longest railroads in the world. In surprising contrast to today's top-down organization pyramids, in McCallum's chart the hierarchy was reversed: authority over day-to-day scheduling and operations went to the divisional superintendents down the line, who oversaw the five branch lines of the railroad. The reasoning: they possessed the best operating data, were closer to the action, and thus were best placed to manage the line's persistent inefficiencies."
Plus, cool 1854 org charts... flow with data.
My latest on Active Information:
"About a decade ago, I was working with my favorite co-conspirator on a universal task viewer service, which was an adjunct to our event-driven architecture. In order for something to appear in the task viewer, it had to be "trackable" (include the proper interface).
Over the course of our design sessions, and throughout the next few months, we kept identifying business and system actions that should be trackable. It became apparent to us that nearly every business and system action could be trackable, following an interface pattern similar to making document objects printable.
I hadn't thought of "trackable" -- and the running "hey that's trackable" joke -- in years. However, reading Counting Every Moment on self-tracking in the recent Economist Technology Quarterly bounced trackable up my memory stack."
This week's Active Information post:
"...And sure, we've heard all of this before. All those data management activities that get head nods, lumped into architecture and COEs (read: overhead) and then get resource gutted as soon the economy gets challenging, or a "business critical" project comes along.
But, here's the thing. According to the EIU research, the organizations that have actively, consistently invested in data management fundamentals are reaping more than business benefits..."
"Much has been written about SAP HANA. The technology has been variously described as “transformative” and “wacko.” Well, which is it?"
"In-memory databases take advantage of two hardware trends: a significant reduction in the cost of RAM, and a significant increase in the amount of addressable memory in today’s computers. It is possible, and economically feasible, to put an entire database in memory, for fast data management and query. Using columnar or other compression approaches, even larger data sets can be loaded entirely into main memory. With high-speed access to memory-resident data, more users can be supported on a single machine. Also, with an in-memory database, both transactional and decision-support queries can be supported on a single machine, meaning that there can be zero latency between data appearing in the system, and that data being available to decision-support applications; in a traditional set-up where data resides in the operational store, and then is extracted into a data warehouse for reporting and analysis, there is always a lag between data capture and its availability for data analysis."
”Sensors will be everywhere in the next few years and will be able to help people become more conscious of the environment and our own health,” explained Mr. Vigna. “Your socks, shoes, glasses and even your garbage can will have sensors inside designed to help you manage everything from your effects on the environment to your health.”