Archive for June, 2009

Attending the National Summit

Friday, June 26th, 2009

First, I want to thank my company DATAForge LLC for suggesting that I attend the National Summit. My leadership understands the importance of participating in the comprehensive dialog around the direction of the US strategies in the Technology, Energy, Environmental and Manufacturing industries.

The Detroit Economic Club put together a dynamic three days of thought starting and panel discussions with business leaders, state, federal and education representatives. I am looking forward to reading the report of the action items gleaned from the National Summit to be presented by Bill Ford and Andrew Liveris to Secretary Locke in Washington.

The dialog was refreshing and un-stereotypic as prominent business leaders discussed the “how to” and the “what is” for the future direction needed to support “clean energy” and “smart technology” for our environment. The discussions were the first steps to create a roadmap to set the long term policies and standards needed to allow our innovative research universities and businesses to work together to develop and manufacture the next generation of global environmental and manufacturing technologies. This is the old fashion “American” spirit and I am thrilled to be a part of the revolution.

So let’s get the plan in motion, communicate and discuss our action items, support the research institutions, businesses and the startup ventures to make America the next generation innovators and competitors in this global economy.

View Jackie Roberts's profile on LinkedIn

DATAForge LLC is now managing the AICSC Council through ECCMA

Wednesday, June 24th, 2009

We are pleased to announce that DATAForge LLC is now managing the Automotive Industry Content Standardization Council (AICSC) through ECCMA (www.eccma.org) with Chris Roberts as the chair of the council. The purpose is to standardize the naming conventions and descriptive attributes for spare parts and services.

Master Data Ownership

Friday, June 19th, 2009

Master Data ownership is a hot topic these days inside most organizations, large and small. Business or IT?  The correct answer is both! For your companies master data to be managed in a way that is best for the company, your customers, and suppliers it is imperative that both the business and IT units take shared responsibility for its maintenance. James MacLennan states it simply. Who owns master data in your company?

Getting smart about business intelligence in the downturn

Friday, June 12th, 2009

Economic adversity represents opportunity. Slowdowns can lead to new opportunities for companies to emerge smarter, leaner, and more competitive. Read More…

Cut Costs (And Save Your Job) Using Business Intelligence

Thursday, June 11th, 2009

Here’s a great way to guarantee your current employment for the next few years: offer to deploy some of your company’s Business Intelligence tools to improve operational efficiencies and cost reductions.  Read More…

Achieving buyer/supplier information synergy… eOTD, XML, People

Thursday, June 11th, 2009

What comes to mind when you read those words? Does your organization have issues attaining the product data you need to run your manufacturing operations?

Buyer/supplier information synergy to me means that at any given time, if a piece of data is needed to complete a product description or a piece of data is needed to place a product or service order that is not available in your ERP applications, your suppliers are willing and able to provide the piece of data automatically without human intervention.

That probably sounds ridiculous.

This situation probably sounds more familiar:

1.) New equipment is installed
2.) The recommended spares list is loaded directly into ERP
3.) The new equipment malfunctions, goes down
4.) Production stops
5.) The maintenance department attempts to replace failed component only to find there is no inventory
6.) Maintenance frantically calling machine builder/suppliers/plant engineering to identify the failed component

This may be an over simplification or might not be something your organization can relate to, but, there are several types of technology and business process that enable prevention of this scenario and other problems that plague the large manufacturers supply chain.
—a common unified schema or dictionary used by all commercial organizations to label product information (eOTD)
—a common method of transmitting this information directly into ERP prior to the need arising to replace a component (xml)
—develop a supporting business process to ensure the needed information is requested (people)

As manufacturers/suppliers/BPO providers we all need to work together to move to a common method of requesting, transmitting and receiving the information we need to keep our operations running.

Outsourcing. India is not always the answer

Wednesday, June 3rd, 2009

I have been struggling with this blog entry for the past week working against everything a blog is supposed to be. My struggle has been in keeping this short and sweet and not publishing an essay, or not going off on too much of a rant. We are a company that has operations around the globe. We have made strategic decisions to send some work to low cost countries such as India and China but have also decided to keep certain key functions here in the United States.

Two weeks ago we lost a bid for a large project for a Fortune 100 manufacturer because we were not willing to send all of the work to India. Sure, we could have cut our costs, significantly as a matter of fact. But in doing so we would have gone against what we believe as a company, and honestly what I believe in personally. Those beliefs are as follows:

 

*      My belief as a business owner. Our mission as a company revolves around providing the best BPO services possible. Any outsourcing initiative is made up of different processes, some complex, and some relatively simple. India is a place for those simpler processes. Not because workers in India do not have the skills to deal with complex processes, but because when you analyze the quality or work over time; the total cost of doing business in India; and factors related to flexibility and convenience, India’s value has consistently shown itself in less-complex, but time consuming tasks.

Processes that require intense analysis, or extensive decision making are better off staying here in the U.S. Long-term quality remains much higher and the overall cost of doing business is far less expensive.

*      My belief as a United States citizen. Sending work outside of our country, no matter the savings, can be a very short-sighted business solution to a long-term economic problem. I like to think about the subject this way, what is the value of our country to the rest of the world? In other words, why do other countries need the United States?

I have customers sending everything from new product engineering to the writing of commercial aircraft maintenance documentation to India. I start to ask myself, where is the line? What cannot be outsourced to India? The more we send, and the more complex the tasks, to me personally, the more our value as a country decreases to our own economy and to the rest of the world.

*      Finally, my belief as a parent of three children. My friends and I joke about what to tell our kids to be when they grow up. Someone always answers sharply ‘whatever cannot be outsourced to India’. It seems like all that will be left are civil servant jobs and positions in healthcare that will be deemed unable to be outsourced. Look at our current economy and the fact that its demise was based on the short-term gains by shareholders and corporate executives with no regard for the long-term impact. We are taking the same approach to outsourcing. Creating jobs in India as fast as we can to eliminate jobs in the U.S.

What is wrong with this picture? Should I move my family to India or to China to ensure my children will have jobs when they become adults?

Ok so I ranted a bit. All I’m saying and all that I ask is when outsourcing to us or anyone else, consider all of the factors, the complexity of the work to be done, and how it will affect our country and our children’s future opportunities.

Data Quality – What is a good description?

Monday, June 1st, 2009

A spare part record, sounds fairly simple? Yes, I used the same concept earlier. Ask the questions, what is the end use for this record? Is this information only to purchase the item? What if we broaden the scope of Data Quality to enterprise wide, say Engineering or Plant Maintenance, is this description enough to describe the part technically?

Table

A full technical description provides many benefits that support engineering and maintenance such as identifying functional equivalents or using another part in inventory if the requested item is out of stock. The description will provide enough information for purchasing to ensure that the correct item is being purchased and also provides ability to reconcile legacy data.  

What additional elements should be included in a description?

table1

I am not sure what the legacy system search capabilities are but if these descriptive element are included in a description, it only ensures the ability to find the part quickly (or a substitute part) and this will minimize equipment down time and employee sourcing time.

Question: What level of description is required enterprise wide to optimize employee performance and inventory optimization?

View Jackie Roberts's profile on LinkedIn