1. PCB Co. ERP Implementation Brian Ahearne Fergus Callinan Sean Hadden Ger Hallissey Pierce Kent Anthony OSullivan

2. Establish the Process Flow Aim : Understand the process flow through PCB Set the goals of the project Interview the departments : Jim Flaherty and Sales reps Bill Quinn and Sales and Support team Order Administration Shipping Department Pauline Sanders and accounts receivable. Document the procedure and work out flow on paper Once documented, communicated back to the stakeholders Determine who will get involved and how long the project will take

3. Process flow Leads Sales reps Leads Name Address Product Quote Sales & Support Quote No. Links lead with product Assigned to Product Order Admin. Order No. Could be converted to barcode on floor Invoice Shipping Invoice No. Corresponds to order Order Order Admin Order No. Convertes lead to order Receipt A/Cs Receivable Receipt No. Correspond s to Invoice

4. ERP – relational database Data Entry Customer details Product details Database Maintenance Transactions Documents Quotes Orders Invoices Packing slips Receipts Reports Sales Product volume / high runners Leadtime (order to invoice) Rep activity Deptors payment (invoice to receipt) ETC

5. Buy versus Build Quite a simple model so this could be programmed via MS Access or Bought off the shelf. ConcernBuy (std. Business package) Programmed Comments TimeShortLong Programming will take longer time to understand, get familiar with, plan and program SupportGood Pre-sales and post sales support good from vendor and internally unless programmer leaves. CustomizationGood Better initial customization with build ExpansionGoodLimited Greater expanision possibility with standard model

6. Action Plan Analysis – Roll it out with no disruptions Risk – contingency plan Feedback before GO LIVE and after Company communications Data clean up Data conversion Spec Vendor Selection Test Procurement H/W & S/W Training Time Line GO LIVE Business Simulation