IDAT Consulting | Project Team Guidelines <META name="resource-type" contents="a-dodont.html">; <META name="description" content="Project Team Guidelines."> <META name="keywords" value="Consulting ADC AIDC Automatic ID"> <META name="distribution" content="global"> <META name="copyright" content="Copyright Bert Moore, contents may be used upon request and with appropriate reference(s).">

 
IDAT logo
Article Index
 

  Project Team Guidelines

Bert Moore

Below is a brief list of DOs and DON'Ts for your project team. Although it's geared towards bar code implementation, most of the items apply to any automation project.

DO

  • DO allow some "blue sky" thinking - it will help you plan for the future and may lead to some tangible benefits in the short term.
  • DO identify as many needs and opportunities as possible - prioritize them later.
  • DO identify both direct and indirect benefits from the project - it will help with cost justification.
  • DO encourage employee (not just management) involvement - they know the current situation as well as anyone and will be the ones using the system. Employee "ownership" of bar code systems has been a big plus in many implementations.
  • DO limit the time you will spend on brain-storming. Focus on the issue at hand once you understand how the current project might integrate with other projects.
  • DO identify your suppliers' capabilities to supply bar codes.
  • DO identify customer (and industry segment) requirement for bar codes.
  • DO investigate existing industry-wide and inter-industry standards - use whatever you can.
  • DO determine exactly what information you need, where you can get it and how it will be used.
  • DO examine all related existing systems to see if they can be improved at the same time.
  • DO consider the impact of automation on non-automated systems.
  • DO consider the impact of the system on employees.

DON'T

  • DON'T "come down to earth" too soon.
  • DON'T assume that automating existing systems will improve them (they may need to be eliminated or changed).
  • DON'T limit your thinking to the "obvious" problem.
  • DON'T assume the need that has been identified is the one that should be addressed.
  • DON'T stop thinking of additional benefits.
  • DON'T start off by defining a bar code symbology (or assuming a technology).
  • DON'T start off by defining a bar code reader or printer type (or other equipment).
  • DON'T reinvent the wheel
  • DON'T overlook your peers and industry associations as sources of information.
  • DON'T accept unrealistic expectations or timeframes.
  • DON'T be afraid to ask for help.

Always remember Bert Moore's First Law: "Without proper planning, a successful AIDC project can become your worst nightmare."