IT Vocabulary Builder

IT Vocabulary Builder: Microsoft Certified Professional

2

The 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.

image

Depending on what part of the Information Technology Professional field you are in and what you customer base looks like (federal, public, private, or small company) you either have tons of Microsoft Certified Professionals running all around you or you may have never met one.  What exactly does this term mean and is it a standard, a term or art, or one of science?

This is how Wikipedia defines it:

Microsoft Certified Professional (MCP) broadly refers to all Microsoft certifications. But it can also refer to an individual who completes any exam within the program (subject to some exclusions).

 

The MCP program offers multiple certifications, based on different areas of technical expertise. To attain these certifications, a candidate must pass a series of exams within the program. The current generation of certifications are Microsoft Certified Technology Specialist (MCTS), Microsoft Certified Professional Developer (MCPD), Microsoft Certified IT Professional (MCITP), the Microsoft Certified Architect (MCA), Microsoft Certified Systems Administrator (MCSA) and Microsoft Certified Systems Engineer (MCSE).

Basically, if you have ever earned a single Microsoft certificate for any product or service, then you are permitted to call yourself a Microsoft Certified Professional.  The Term itself does not tell you what the person is certified for or what their expertise is.  It also does not convey a level of expertise – journeyman or master.

Most of the entry level Microsoft Certifications are earned by successfully passing an examination.  Most people need to complete an associated training course in order to get enough level of knowledge to successfully pass the exam, though some can do it just by purchasing written or audio study manuals and using them.  In some cases, the higher level certs also have experience requirements and prerequisite certs.

New Horizons is one of the premier education centers providing full service training and examination for this program.  Here is how they define it:

Microsoft Certified Professional Description

Individuals with expertise in a particular Microsoft® product can pursue the Microsoft Certified Professional (MCP) credential. MCPs have demonstrated in-depth knowledge of at least one Microsoft product. The MCP credential provides a helpful first step on the way to other Microsoft technical certifications.

Microsoft itself has a wonderful site dedicated to the program.

Certifications are available for most Microsoft technologies and skill levels from business workers to IT professionals, developers, technology trainers, and system architects. Pursuing a certification, provides you with up-to-date, relevant skills that can not only lead to a more fulfilling career, but offer valuable Microsoft Certified Professional (MCP) benefits, including access to the MCP member site and a vast, global network of other certified professionals.

There is also a magazine dedicated to this group, The Microsoft Certified Professional Magazine.  They highlight the top reason to obtain the title: salary, in a recent article.

A looming recession should affect salaries. So should reports of IT budgets being slashed for the rest of 2008. And so should global economies going crazy with every dollar fluctuation, mortgage crisis or the closing down of another subprime-laden bank or brokerage.

 

But get this: Those events haven’t made any such visible impact on IT compensation — at least, so far — as this year’s joint Redmond/MCPmag.com 2008 Salary Survey indicates. For a fourth year in a row salaries have risen, as have raises, bonuses and job stability, sidestepping any rising recessionary tide.

There are many many more IT certifications than just Microsoft’s, but there are no more widely accepted or understood ones.  If you were not familiar with this program, hopefully I gave you enough to get started.  If you are one of the many IT Pros who have them swarming around you…. you already know all that you will ever need about their value.

That is my Information Technology Thought of the Day (ITTOD) for December 14, 2009 ©Scott Coughlin.

Image Credit: Microsoft

Information Technology Vocabulary Builder: Manufacturing Intelligence

2

The 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.

image

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

0

The 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.

image

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:

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

Go to Top