03_Planning, Design & Implementation

Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Enterprise Resource Planning, 1st Edition by Mary SumnerChapter 3: Planning, Design, and Implementation of Enterprise Resource Planning Systems

Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner

Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*ObjectiveUnderstand the information systems development process for enterprise systems, including planning, design, and implementation


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Traditional Systems Development Life CycleDetailed analysis of system using tools and techniques to determine problem areasProcess models Data modelsPhasesProblem definitionFeasibility studySystems analysisSystems designDetailed designImplementationMaintenance


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Traditional Systems Development Life Cycle, continuedAutomating current system is counter-productiveInherit old problems and flawsProvides opportunity to re-engineer current systemCreate logical database design before details are refinedTakes too much timeUses a great deal of resourcesExpensive


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*New ApproachesPrototypingSystem Designers could show Models of system documents to end-users for feedback, guidanceIt enabled End-users to specify their requirement, it did not necessarily speed up the processEnd-user developmentEnd-users create information systems using spreadsheets and databasesNot effective for large-scale developmentSoftware packagesEconomies of scale in development, enhancement, maintenance. ERP systems are large-scale, integrated commercial off-the-shelf software.


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*ERP Systems Design ProcessPhasesPlanningRequirements analysisDesignDetailed designImplementationMaintenance


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Planning and Requirements PhasesPlanningNeeds assessmentBusiness justificationTangible and intangible benefitsRequirements analysisIdentify business processes to be supportedBest practices offered by vendorsModels of supported functionsChecklist of activities and factors


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Design PhaseRe-engineering business processes to fit softwareTraditional SDLC defines new business requirements and implements conforming softwareRe-engineering versus customizationRe-engineering can disrupt organizationChanges in workflow, proceduresCustomizingUpgrading can be difficult


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Alternative DesignsVanillaEasy to implementFollow vendor prescribed methodologyEmploy consultants with specialized vendor expertiseUsually on time and on budget implementationsCustomizedTime and costs increaseNot easily integrated into new version


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Alternative Designs, continuedMaintain legacy systems and add ERP modulesSupport specific functionsCost-effectiveOrganization doesnt get full benefit of ERPLess disruptiveLacks integrationOutsourcingExternal vendor operatesASPs provide on time-sharing basisDepends on reliability and stability of vendor


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Detailed Design PhaseTeam selects the models, processes, and information to be supportedBest practices methodology provides modelsSelect applicable business processesDiscard inapplicable processesThose processes that do not match the system will serve as foundation for re-engineeringIdentify any areas not covered as candidates for customizationInteractive prototypingExtensive user involvement


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Implementation PhaseImplementationAddress configuration issuesData ownership and managementSecurity issuesMigrate dataEnsure accuracy Build interfacesDocumentation reviewUser trainingReportingTesting


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Implementation StrategiesBig bangCutover approachRapidRequires many resourcesSmall firms can employMini big bangPartial vendor implementationPhased by moduleModule-by-moduleGood for large projectsPhased by siteLocation-based implementation


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Case: Response to Request for Proposal for an ERP SystemWingate ElectricMid-sized manufacturer of electric motorsOwned by Dick, CEO, and Steve, COOMIS systemSupports major accounting and financial functionsSales order processing, inventory control, accounts payable, accounts receivable, general ledgerMultiple legacy systemsRedundant dataInconsistent dataQueries difficult


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*Case: Response to Request for Proposal for an ERP System, continuedCompetitors adopting ERP systemsIntegrating financial and manufacturingWeb-based front endsOrder processing, tracking, follow-upRFP for ERP systemInitially to support accounting, financialsAdditional support for production, manufacturingEventual support for sales and marketing, HR, CRM, eBusiness$1,000,000 budget for systemDetermination made by five executives, representing different user groups10 scored criteriaVendor presentations, supplemental materials


Prentice Hall, 2005: Enterprise Resource Planning, 1st Edition by Mary Sumner3-*SummaryTraditional SDLC has been modified by the use of prototyping, end-user developments, and software packagesERP systems design process consists of six phases: planning, requirements analysis, design, detailed design, implementation, and maintenanceThe design phase considers the use of traditional methods, re-engineering, and customization, as well as outsourcing


*

03_Planning, Design & Implementation

Documents

Transcript of 03_Planning, Design & Implementation