IT Vocabulary Builder
Information Technology Vocabulary Builder: Manufacturing Intelligence
2The Information Technology (IT) Vocabulary Builder series aims to deliver a very concise summary of a currently relevant topic to Information Professionals. It is done mostly by collecting a small number of highly relevant web links to save you the time of combing through search results yourself. It differs from sites such as Wikipedia because it includes opinions, forecasts, and detractions in addition to just facts.
Today, I would like to discuss the term, Manufacturing Intelligence. It means different things to different professions, people, and parties. It is intertwined with Information Technology in such a way that I believe that all Information Technology professionals need to be familiar with the concept and ready for its explosion.
This is how Wikipedia defines it:
Enterprise Manufacturing Intelligence (EMI), or simply Manufacturing Intelligence (MI), is a term which applies to software used to bring a corporation’s manufacturing-related data together from many sources for the purposes of reporting, analysis, visual summaries, and passing data between enterprise-level and plant-floor systems. As data is combined from multiple sources, it can be given a new structure or context that will help users find what they need regardless of where it came from. The primary goal is to turn large amounts of manufacturing data into real knowledge and drive business results based on that knowledge.
Automation World has a great quote in their explanation that adds real insight into the concept.
There are two important things to note about implementing Manufacturing Intelligence: 1) It is not something you can “buy” in a software product; 2) It is not a standard or a defined technology. Manufacturing Intelligence is more a strategy or way of defining and approaching solutions to problems and opportunities. However, a well-designed strategy will use software products that can make the adherence to standards and application of specific technologies easier.
The critical idea is that with quicker, more accurate, more timely, more complete information about your manufacturing process, you can make decisions faster, in a more timely manner, and with significantly less risk. It is closely akin to other Enterprise Knowledge Management and Data Mining initiatives that we have discussed before.
Here are some recommended sites for further reading on this dynamic topic:
- Wikipedia – Enterprise manufacturing intelligence
- AutomationWorld – Manufacturing Intelligence Not a Buzzword in Manufacturing Software
- Managing Automation – Manufacturing Intelligence (MI) News, products, and resources
- SAP – Manufacturing Intelligence Using Intelligence Dashboards
Beyond dashboards, data storage, knowledge management, and databases information technology is an integral part of the burgeoning focus on manufacturing intelligence. Though many may try, I suggest that you cannot have world class manufacturing intelligence without ninja class information technology systems and people.
Do you have experience with implementing, market research, or product development in support of manufacturing intelligence? Is your enterprise using or thinking of installing a program to accomplish it? Do you know of any case studies associated with the IT portion of it? Please share with us.
That is my Information Technology Thought of the Day (ITTOD) for November 24, 2009 ©Scott Coughlin.
Image Credit: Link Notes
Information Technology Vocabulary Builder: Enterprise Architecture
0The Information Technology (IT) Vocabulary Builder series aims to deliver a very concise summary of a currently relevant topic to Information Professionals. It is done mostly by collecting a small number of highly relevant web links to save you the time of combing through search results yourself. It differs from sites such as Wikipedia because it includes opinions, forecasts, and detractions in addition to just facts.
Today, I would like to discuss the term, Enterprise Architecture. It means different things to different professions, people, and parties. In the Information Technology context, It is essentially the design for your highest echelon of networking. It includes functional, technological, systems based, and operational layouts for what your IT system is supposed to accomplish.
This is how Wikipedia defines it:
Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
They continue with this very informative discussion point:
Enterprise architecture has become a key component of the information technology governance process in many organizations. These companies have implemented a formal enterprise architecture process as part of their IT management strategy. While this may imply that enterprise architecture is closely tied to IT, it should be viewed in the broader context of business optimization in that it addresses business architecture, performance management and process architecture as well as more technical subjects. Depending on the organization, enterprise architecture teams may also be responsible for some aspects of performance engineering, IT portfolio management and metadata management.
While the people who create Enterprise Architectures are actually systems engineers, every Chief Information Officer (CIO) and Information Technology Professional needs to understand these concepts enough to lay the groundwork. In many smaller organizations, it will be the CIO who produces, maintains, and most importantly, justifies the Enterprise Architecture.
Here are some recommended sites for further reading on this dynamic topic:
- Wikipedia – Enterprise Architecture
- Gartner – Enterprise Architecture Topic Page
- The US Government Office of Management and Budget (OMB) – Federal Enterprise Architecture (FEA)
- CIO,com’s – Enterprise Architecture Topic Page
Like most design, architecture, coordination, and planning roles in the Information Technology profession, there are essentially two camps on this topic. There are organizations who swear by the idea and extol the competitive advantages that come with it. On the other hand, many question the return on investment (RIO) from these efforts and have a hard time quantifying its value. Regardless, all IT Pros need to be conversant on the topic. Hopefully, this primer helps you.
Please share examples, case studies, ideas, and lessons learned from your involvement with Enterprise Architecture initiatives.
That is my Information Technology Thought of the Day (ITTOD) for November 11, 2009 ©Scott Coughlin.
Image Credit: Van Ness Feldman