EAM Selection

1. Enterprise Resource Planning(ERP) SelectionPresented by:Masoud Shams Ahmadimasoudsa@hotmail.comFebruary 2007

2. EAM Selection ERP Selection

3. ERP Selection • Establish Team: • Scope of team(s) should include all work streams and IT • Deliverables: • Project charter • Milestone based schedule • Responsibility matrix

4. ERP Selection • Define Requirements: • Guidelines: • Process maps • Requirement templates • other? • Deliverables: • Requirements docs. • RFI (optional)

5. ERP Selection • Vendor Search: • User Groups • Use consultant knowledge • Internet • Others

6. ERP Selection • Ranking Criteria: • Quantitative • Covers EACH requirement as well as “soft” issues: • Vendor financial health • Stability • Longevity • Referencability

7. ERP Selection • Prepare / Issue RFP: • Technical and Functional Requirements • Client responsibility to get legal input

8. ERP Selection • 1st Cut Assessment: • Produce initial scores from RFP results • Overall Review of Responses • Demonstration Scripts • Reduce vendor list to 3

9. ERP Selection • Detailed Assessment: • Includes • Vendor references (business) • Site references (application focus) • Site visits • Vendor presentations • Additional Vendor demonstrations • Scope to be tailored to Clients budget/Requirements • Deliverables: • Annotations to proposal submissions • Reference feedback / revised scoring

10. ERP Selection • DECISION: • Process: • Review latest scoring • Proceed to negotiations with winner but keep runner-up in picture • Conclude negotiations and advise all vendors

11. Factors to Consider in Selecting an ERP System

12. Request For Proposal(RFP)

13. What is an RFP? An RFP is a standard tool used to purchase equipment and services by promoting competitive proposals among suppliers. The RFP becomes a vehicle that allows both the buyer and the supplier to establish a dialogue and to work from the same set of rules, requirements, schedules, and information. The opportunity to have this dialogue is an important element in the process, because RFP requirements are often not clear and the supplier is allowed to question and interpret what is being requested. Note: Proposals are a supplier’s interpretation of an RFP’s requirements.

14. What is a successful RFP: • A successful RFP process requires us to do the following: • Formally recognize a deficiency or need in current operations that could be resolved through the purchase of systems, equipment or services • Identify appropriate potential suppliers and solutions • Gain visibility for internal acceptance of the identified need and potential solutions • Establish the project budget • Develop a project schedule • Organize project personnel • Identify real requirements • Develop evaluation criteria (Objective)

15. What is a less successful RFP: • A less successful process may include the following issues: • Not enough time has been allocated for the RFP process • Requirements unfairly limit the range of suppliers who may participate • Requirements are not clearly defined • Project deadlines are too short to allow suppliers to prepare proposals • The project team has not been fully educated about available technologies • A budget has not been established, or has been based on unverified data and is not sufficient for the project Note: Strong leadership, dedicated resources, and management commitment are critical to a successful RFP and a successful relationship with the chosen supplier.

16. What are the different types of RFPs: • There are two different types of RFPs: • Request for Information (RFI) • Request for Proposal (RFP)

17. Request for Information (RFI): An RFI is a way for buyers to determine what is available from suppliers who respond to its requirements. It is also a way for the buyer to determine whether the requested requirements are reasonable and whether appropriate technology is available. The information from suppliers may help guide the subsequent RFP or cause it to be cancelled if suppliers do not respond. Note: An RFI is not a mandatory prerequisite to writing an RFP.

18. When do you consider writing RFIs: • RFIs may be considered when: • The technology for the project is new to the industry or your company • You would like to explore a variety of potential solutions

19. What are the different sections of an RFP: • Project overview and administrative information • Functional and technical requirements • Management requirements • Supplier qualifications and references • Pricing • Contracts and licenses • Appendices

20. Administrative Section The first section of the RFP is the administrative section. The purpose of this section is to provide suppliers with a framework for their responses so that all proposals received, present the same information and follow the same structure.

21. Contents: • The administrative section contains the following section: • Introduction and statement of the problem • RFP Schedule • Time and place to submit the proposal • Date of a bidders’ conference, if one is being held • Relevant dates for the procurement process • Requirements for preparing proposals • RFP contact names and addresses • Any other information suppliers may need in order to respond adequately

22. Requirements Section The requirements section contains the requirements for what you are buying, The requirement section is the heart of the RFP and is where suppliers should spend the most time initially.

23. Requirement Section • Vendors will “interpret” requirements if they are not clear. • Use an RFI if you can not determine whether products or services exist for your project. • Note: The proposals received in response to an RFI should help you to focus on: • The correct technology • The appropriate set of suppliers

24. Writing Requirements There are always two parts to every requirement: 1. The requirement itself 2. The evaluation or measurement criteria We may also argue for a third criteria, which may seem obvious but is commonly overlooked. A product or service must exist in order to satisfy the requirement. 3. The requirement must be feasible

25. Management Section A supplier’s response to the RFP’s management section will clearly indicate whether the supplier’s company has the requisite project management skills, resources, and experience to be considered for the project. A supplier may have developed the proposed functional and technical product but lack the ability to develop and implement an effective management program.

26. Sections of a project management plan • The project management section typically requires, but it is not limited to development of the following: • Project Plan • Site preparation plan and responsibilities • Staffing requirements • Design, development, and implementation • Delivery and installation • System acceptance test • System Maintenance • Training • Documentation

27. Pricing Section A successful RFP meets two basic requirements: 1 – Products or Services meet the requirements 2 - Product or Services fall within the projected budget Notes: It is critical to the evaluation of proposals to have pricing presented in a consistent format.

28. Management Section • Project implementation and management services (include supplier personnel who are on site) • Integration of unique hardware or software • Development or customization of the application • Installation • Acceptance testing • Maintenance • Training • Documentation • Project staffing • Facilities upgrades

29. Contract and License Agreements Section • Most RFPs request that suppliers include a copy of the following document: • Purchase agreement • Maintenance contract • Warrant period • Software license agreement • Payment method • Nondisclosure agreement