ERP and More!

Many times companies try to select and implement ERP software on their own. Sometimes this works and sometimes it doesn’t. So the question is, when should a company use an ERP Software Consultant to guide them in their ERP Selection or ERP Implementation?

The answer is not so simple. If a company is mature and has the resources that can look independently at the business processes, then it may make sense to embark on a selection on their own. Most of the time in mid-market sized or even smaller clients, then it is difficult for them to 1. Spare the resources and 2. Look at the business processes objectively.

Any good ERP Selection begins with a company evaluating their business processes. Borrowing from the Toyota Production system (aka Lean Manufacturing), a company should first eliminate waste and then consider automating. Automating bad processes will only make things worse faster. However, automating good processes will help grow the business and promote better communication.

The real question becomes how much is the company willing to flex their processes to adapt to “best practices” that are usually built into a commercial software system. If the company is flexible (and this takes a lot of leadership to make happen), they can select a system and model their business around that system. The larger commercial systems, such as those from Microsoft, Infor, SAP, Oracle, and others have all grown up from thousands of implementations from all sorts of companies. They have developed efficiencies that many companies who adopt the software’s methodology can benefit from.

The real key is understanding the fit of a software package to the business. If the company does some niche processing, then a mainstream commercial package may not fit. However it the company is a Read the rest of this entry »

• del.icio.us
• digg this
• Recommend on Facebook
• Buzz it up
• Buzz it up
• Share on Linkedin
• Mixx it up
• rddit this
• Stumble Upon
• Tumblr it
• Tweet This
• Subscribe to the comments on this post
• Tell a friend
• Print for later

1. One central database
Anything to do with the matter is held on a database accessible to all the team. View all the documents related to a matter based on a certain standard; all the documents associated with a particular contact. Incoming letters can be scanned into the matter management system..

2. Email integration
Stay on top of your inbox and ensuring that the matter information is also complete through email integration (packages support generally include Outlook, Lotus Notes etc).

3. Time saving
Reduce time spent on document management with the use of precedents and workflows. Documents are created, stored and managed in real-time. Avoid the unnecessary overheads of typing details in every time through pre-populated templates.

4. Consistency of work
Working practice consistency can be created through templates and workflows. {Appropriate automation to free professionals from background tasks – three different levels of workflow provide the opportunity for work to be heavily controlled or largely free-flowing|Fee-earning professionals don’t need to spend time on background tasks. Workflow automation is a key step to driving up team efficiencies. Do you prefer working in a controlled environment or more loose procedures. Matter managment software systems offer these choices.

5. Keep on top of key dates and events
Matter management software can be combined with your calandar system. Supporting:

• Resources scheduling
• Automatic scheduling of required team members
• Reminders for bring forward dates

6. Team effectiveness
Legal teams benefit from access to shared libraries of best practices, procedures and resources..

7. Information Management
Automated user-defined reporting. In addition to a set of standard reports. Allow user-configurable reporting to suit different organisational needs. Most matter management software allows reports to be programed to run automatically and output in the chosen format..

8. Easier client care.
Deliver an organisation-wide, shared contact database to aid collaboration and ensure that team members have access to the very latest information. Contact details can be automatically inserted as required into precedents. Conflicts and risk areas can be more easily accessed because all the files and cases associated with any contact are tagged..

9. Compliance and Records Management
Maintaining records of dates, instructions, correspondence and outcomes is increasingly important in today’s legislative environment, requiring retention or information for discovery and disclosure purposes. Implement an audit trail of the management of all records of every kind, from cases, matters and projects through to individual documents and emails.

10. Data security
Today’s professional teams are dispersed georgraphically, so an online system meaning secure access from anywhere is not only important but vital

• del.icio.us
• digg this
• Recommend on Facebook
• Buzz it up
• Buzz it up
• Share on Linkedin
• Mixx it up
• rddit this
• Stumble Upon
• Tumblr it
• Tweet This
• Subscribe to the comments on this post
• Tell a friend
• Print for later

Chris Shaul

Today, many ERP vendors are offering Lean Manufacturing modules in their solutions. These modules propose to assist companies in their lean effort. The real question is to what degree will these modules be used. Can a traditional manufacturer going to a lean model utilize a lean software tool immediately? When implementing an ERP system, process redesign is a must. The change that must occur in order to support an ERP system can be tremendous. But can a company bite off and digest all of the changes? Which should be done first, lean or ERP? These are all some of the questions that a typical manufacturing manager who is about to embark on an ERP implementation might ask.

First, lets define a few things. Lean is the removal of waste within a process and the concept of pulling items to a demand. It is also known as the Toyota Production system as it was developed and refined by Toyota in Japan. ERP is a business process enabled by software tools. It is not a software project! ERP streamlines your information flow such that it parallels your process flow. ERP works to build product to a forecast and then execute a production plan and inventory purchases synchronized to meet the predicted and actual demand. Lean, on the other hand, uses a pull system to meet an actual customer requirement. Lean uses the philosophy of smaller batches and reduction in non-value-added activities to create a much shorter lead time, thus delivering faster to a customer. ERP does not by its’ nature drive efficiencies in the production process. It only provides planners with information on what is going on and allows them to plan faster. If the process is broken, then automating it with the use of ERP will only highlight the problems.

What is the answer? The answer for many is to implement lean as part of an ERP intiative. Some would say that it should be a predecessor to an ERP initiative. Lean purists will argue that you do not need MRP and MPS to drive the production. ERP folks will argue that MRP and MPS are essential to having parts in-house and suppliers coordinated with the production. The answer for most companies is a hybrid solution, where lean is driving waste from the production and supply chain process (although also in the above-the-shop-floor activities too), while ERP is being implemented, such that you are automating value added processes and not trying to replicated waste processes in your new system. MRP can be used to plan longer lead time items, or items with higher value, whereas a Kanban can be setup for the faster turning and less expensive items.

Working from the perspective of a hybrid model, lean principles and practices can be implemented just prior to the ERP initiative. Then during the ERP implementation, the lean concepts must be considered and utilized in the setup of the new system. Tools such as Value Stream Mapping can define areas for quick improvements. Then once those improvements are made, a process flow based on the future state model can be applied to the ERP system. For example, a production cell might be setup for a particular product line with kanban inventory control. This would change how you would define your production process in the ERP system. Better ERP systems can run in this hybrid mode of traditional MRP and modern Lean concepts. Some product lines might be more suited to the MRP/MPS method because of supply chain issues or because of the long lead times that are associated with the products. Other product lines might be easy to immediately switch to flow manufacturing. Because of this, you want a system that can handle both methods.

Using a hybrid model, you select and position the ERP system to work alongside your lean initiatives. By leaning out processes (above and below the shop floor), you are avoiding “automating the mess.” Doing so will shorten lead times, reduce inventory, reduce production costs, improve employee moral and streamline your ERP implementation. Be sure to choose an implementation partner that is familiar with lean and is able to work in a hybrid manner. What order should these two tranforming intiatives occur? It might be best to have the lean initiative lead the ERP intiative by a few months. Then begin to implement the system. But do not stop the lean transformation. That should now be an ongoing philosophy of continual improvement. Use it to your advantage during the ERP implementation. Doing so will only help you on go-live day.

References:

http://www.advancedmanufacturing.com/September00/informationtech.htm

http://www.lean-manufacturing-info.com

http://www.qad.com/company/newsroom/lean_value.html

http://www.mapics.com/software/EE/SyteLine/sl7-aps.asp

http://www.cmtc.com/

http://www.inventoryinc.com/complimentary.html

Chris Shaul is a Sr. IT Consultant and specializes about ERP selections and implementations.

• del.icio.us
• digg this
• Recommend on Facebook
• Buzz it up
• Buzz it up
• Share on Linkedin
• Mixx it up
• rddit this
• Stumble Upon
• Tumblr it
• Tweet This
• Subscribe to the comments on this post
• Tell a friend
• Print for later