Examples of architecture use: Cars

With the launch of their “Vision EfficientDynamics Concept”, BMW provides a good example to explain what architecture means for a company. While car itself will probably never be used as a production model, it does portray the vision that it carries in all its fibers will be embedded in BMW’s future models. Together with architected versions of the more production ready models, they make a pretty good picture of where this car manufacturer is headed. And this in turn makes them a perfect example to explain how architecture should work in the field of IT.

The car resembles the vision or, in IT-architect-speak, the reference architecture. To be absolutely clear: That DOESN’T mean that the concept will be built! However, the various subsystems and quality aspects of the reference car can be incorporated into the various models that the manufacturer does make in to production models.

On the performance part, a key quality aspect of BMW, this car sets the direction in which the powertrain will be developed. This means powerful engines, torque, rear-wheel drive and low fuel efficiency. Even the look of the engine has to abide by the guidelines set in the reference model. The technical subsystems in the car are also similar through the entire product line. They might use higher quality materials on the high-end cars, but the vision behind them is the same.

On the inside of the car, comfort is a more important quality aspect. While there are obvious references to the concept, like similar knobs and materials through the product line, there are also less obvious guidelines. These, for instance, dictate how the car should feel, sound or behave. The feel of the fabrics, the feel of a switch being flicked, the sound of the engine in- and outside the car. The sound of the door closing, et cetera. They all contribute to the image the of the manufacturer. Thus, they should all be the same or, in the worst case, pretty similar to achieve the same experience by the user.

Isn’t that true for all car manufacturers? Yes, Renault and Audi (to pick two) also do a good job of visually portraying their vision for the future and incorporating similar/the same car bits in various models. It’s the various details in looks, feels, sounds, smells and experiences that make a car undeniably BMW, Renault, Audi or any make whatsoever. And that is exactly what makes the reference architectures so important: It creates a family that share the same characteristics and that efficiently make use of the same resources from a vision for the future. And in case of cars and architecture we drive the fruits of that vision every day.

Semantic what? Lets call it Information Recycling

When talking with customers and colleagues, I'm often confronted with the question "What is semantic technology?". As a standard reaction I start explaining that semantic technology can enable businesses to consistently store and reuse its information, improving the quality of the information and increasing the speed of which the information can be found/obtained. By now the listener understands, but why didn't he beforehand?

When we're talking about "semantic technology" we're talking about something, uh, technological. We should be talking about something that has meaning to the people that are going to use and/or adopt it. So, while the technology might be called "semantic", we should use the term "Information Recycling".

Information recycling captures the essence of what semantic technology does and instantly explains it to non-technical listeners. Of course, there are still questions about what to recycle and how we are going to do that. What it does is keeping us talking about solving a business problem without using technological slang.

And I bet we can easily link it to saving the environment too. :-)