ERP Roll out Implementation
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

ERP Roll out Implementation

on

  • 1,170 views

Presentation to Megalaya Crime Servents on ERP - Rollout & Implementation in Government

Presentation to Megalaya Crime Servents on ERP - Rollout & Implementation in Government
IIAM, Bangalore May 2012

Statistics

Views

Total Views
1,170
Views on SlideShare
846
Embed Views
324

Actions

Likes
0
Downloads
18
Comments
0

1 Embed 324

http://sanjay-sahay.com 324

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

ERP Roll out Implementation Presentation Transcript

  • 1. ONE ERP ONE INDIAONE ERP ONE INDIAERP: enterprise resource planning creation, rolloutERP: enterprise resource planning creation, rolloutand implementation in GovernmentSanjay Sahay
  • 2. Would the world have been different if there was noWould the world have been different if there was noMS Office?What do you understand by pervasiveness ofsoftware
  • 3. Softwarehistoryhistorywhat is an erpwhy requiredcharacteristicscreation/developmentroll outimplementation
  • 4. Have you heard of an ERP?Have you heard of an ERP?Name a few?
  • 5. InIn thethe yearyear 19001900 thethe GartnerGartner GroupGroupfirstfirst employedemployed thethe acronymacronym ERPERPfirstfirst employedemployed thethe acronymacronym ERPERPYY22KK problemproblemERPERP IIII inin earlyearly 20002000
  • 6. ERPERP IIII inin earlyearly 20002000WebWeb basedbasedRealReal timetimeCollaborativeCollaborative
  • 7. Why an ERP?Why this metamorphosis?
  • 8. WhatWhat isis anan ERP?ERP?
  • 9. The ERP
  • 10. Typical architectural componentsWebInternetMobileWirelesse-MailCall CenterICM/TelephonyInteractionChannelsMarketingIntelligenceSalesIntelligenceCustomerIntelligenceCall CenterIntelligenceAnalyticalApplicationsE-business PlatformTech StackCRMFoundationCommon Data and Object Models, Security, Interfaces,Common Data and Object Models, Security, Interfaces, GlobalisationGlobalisationE-BusinessFoundationMarketingMarketing SalesSales eCommerceBusinessApplicationsInteraction History Universal Work Q1-to-1 FulfillmentAssignment EngineEscalationsTCAInstalled BaseTasks NotesResourcesCalendarTerritoriesFinance HR
  • 11. ERP CharacteristicsAn integrated system that operates in realtime (or next to real time), without relying ontime (or next to real time), without relying onperiodic updates.
  • 12. ERP Characteristics• A common database, which supports allapplications• A consistent look and feel throughout eachmodule• Installation of the system without elaborateapplication/data integration by the InformationTechnology (IT) department
  • 13. Govt ERP! How do we create?• No history of software• No history of erp• Lack of managerial human resource• Lack of managerial human resource• Technical manpower• Humongous effort• Collaboration
  • 14. Police ITComprehensive ERP system providingseamless integration of the day to dayoperations of the Police Department
  • 15. Police ITIn its conceptualization, creation androll out, it would have a pioneeringroll out, it would have a pioneeringimpact in the way Police in India wouldgo digital in the days to come
  • 16. Police IT- Features• Centralized Architecture• Bilingual• Bilingual• Workflow design• Role based access• 522 screens and 417 reports
  • 17. FIRGCR (CO)FIR AssignmentFIR AssignmentCrime ClassificationCrime ClassificationIf Heinous CaseIF Case TransferredProperty SeizureProperty MovementCrime DetailsArrest/SurrenderWitness DetailsProceedings-174/176 CRPCExhumation DetailsIf Victim=DeadIf Dead body “Buried”I.M (CO)I.M(SDPO)I.M (DPO)Property SeizureProperty MovementCrime DetailsArrest/SurrenderWitness DetailsCase Transfer GCR (SDPO)GCR (DPO)COD, DCRE,..ExternalTransferCrime- Investigation WorkflowFinal Report/Charge SheetFinal Report/Charge SheetCourt Progress DiaryCourt DisposalCase DiaryFinal Report B,C and UDRExhumation DetailsPost Mortem RequestIf Final Report B,C or UDRRejectedForwardForwardAcceptedCPR (DPO)CPR (SDPO)CPR (CO)FR B,C & U (CO)FR B,C & U (SDPO)FR B,C & U (DPO)Witness DetailsCase DiaryBail BondResult of AppealIf Final Report AUDR DisposalIf UDR caseIf B or C case
  • 18. KSP Wide Area Network39 locations 2 Mbpsleased line10 Mbps aggregationbandwidth1400 remotelocations, 512 Kbps,VPNoBB4 Mbps internetleased lineSPDC
  • 19. PolicePolice ITIT SoftwareSoftware DevelopmentDevelopmentFRS/SRS/HRSFRS/SRS/HRSDevelopmentDevelopmentChangeChange RequestRequestTesting/UAT/Testing/UAT/ Feedback/RollFeedback/Roll Out/Bugs/Corrections/HHOut/Bugs/Corrections/HH
  • 20. Police IT-Modules• Crime• Law & Order• Traffic• Finance• Administration• Stores• Armed Reserve• Motor Transport• Training• Wireless• Forensic Science Laboratory• Executive Information System
  • 21. WhatWhat isis ERPERP RollRoll Out?Out?thethe complexity!!!!!complexity!!!!!
  • 22. WhatWhat areare thethe challenges?challenges?
  • 23. InsurmountableInsurmountable
  • 24. Police IT Roll Out• User Acceptance Test• Mandatory Change Requests over 400• Last phase of development• Last phase of development• Pilots for different modules• Capacity Building is most critical• 11 Training Centers established
  • 25. Police IT Roll Out• Near perfect synchronization of moduledevelopment, end user training and thecompletion of all precursor activities wouldensure a smooth roll outensure a smooth roll out• 12 modules in 1439 locations• Wipro would do the handholding in 50 locationsfor 48 months
  • 26. Implementationa long drawn out process
  • 27. Complimentary to the Roll Out Process
  • 28. Implementation based onBest PracticesCase Studies
  • 29. Test Bed to ProductionTest Bed to ProductionHelp Desk to Warranty Support
  • 30. HandholdingHandholdingFunctionalities
  • 31. Conclusion- One ERP One IndiaThe successful completion of this project would take thepolice to much higher level of efficiency, near totaltransparency, all mechanical work would becomeredundant, more human resources would be availablefor core tasks, better investigation, qualitative change infor core tasks, better investigation, qualitative change inplanning, split second communication, perfectdocumentation/ retrieval, no alibi as the application isrole based, need based passage of information on thewebsite/ press/individuals, tracking of incidents/facts/details would be flawless etc.
  • 32. Presentation Structure•What is a Best practice?•What is an ERP•ERP in Govt. Depts•Organisational Culture of ERP Org•ERPs- are they home grown•Do we have Best Practices?
  • 33. •What the IT industry has to offer• Best Practices for Creation, Deployment,Consolidation and MaintenancePresentation StructureConsolidation and Maintenance•We are in the beginning of the journey, the seedswhich sow today, hopefully would deliver one day•AVLS•Conclusion
  • 34. Personal Reflection• Is your organization using best practice method?• Are you using a variety of methods to improveyour systems?your systems?• Are you innovative?
  • 35. ERP ImplementationFundamentals
  • 36. Agenda• What is an ERP System?• Why implement an ERP system?• How should ERP systems be implemented?• How should ERP systems be implemented?
  • 37. What is an ERP System – definitionERP - Enterprise Resource Planning“ERP software is a multi-module application softwarethat integrates activities across functionalthat integrates activities across functionaldepartments, from product planning, partspurchasing, inventory control, product distribution, toorder tracking. ERP software may include applicationmodules for the finance, accounting and humanresources aspects of a business. ”
  • 38. Historical system architecturesHistorically, companies created “islands ofautomation”. A hodge-podge of various systemsthat operated or managed various divergentthat operated or managed various divergentbusiness processes. Sometimes these systemswere integrated with each other and sometimesthey weren’t. Sometimes they were looselyinterfaced and sometimes they were more tightlyinterfaced.
  • 39. What is an ERP – Key CharacteristicsIntegrationSeamless integration of all the information flowingthrough a company – financial and accounting,human resource information, supply chaininformation, and customer information.
  • 40. PackagesEnterprise systems are not developed in-house• Information System life cycle is differentWhat is an ERP – Key Characteristics• Information System life cycle is different1. Mapping organizational requirements to the processes andterminology employed by the vendor and2. Making informed choices about the parameter setting• Organizations that purchase enterprise systems enterinto long-term relationships with vendors.• Organizations no longer control their own destiny.
  • 41. Best PracticesERP vendors talk to many different businesses within agiven industry as well as academics to determine theWhat is an ERP – Key Characteristicsgiven industry as well as academics to determine thebest and most efficient way of accounting for varioustransactions and managing different processes. Theresult is claimed to be “industry best practices”.
  • 42. Some Assembly RequiredOnly the software is integrated, not the computingplatform on which it runs. Most companies have greatdifficulty integrating their enterprise software with aWhat is an ERP – Key Characteristicsdifficulty integrating their enterprise software with apackage of hardware, operating systems, databasemanagement systems software, and telecommunicationssuited to their specific needs.
  • 43. EvolvingEnterprise Systems are changing rapidlyArchitecturally: Mainframe, Client/Server, Web-What is an ERP – Key CharacteristicsArchitecturally: Mainframe, Client/Server, Web-enabled, Object-oriented, ComponentizationFunctionally: front-office (i.e. sales management),supply chain (advanced planning andscheduling), data warehousing, specializedvertical industry solutions, etc.
  • 44. Why implement an ERP System?To support business goalsIntegrated, on-line, secure, self-serviceprocesses for businessEliminate costly mainframe/fragmentedEliminate costly mainframe/fragmentedtechnologiesImproved Integration of Systems and ProcessesLower CostsEmpower EmployeesEnable Partners, Customers and Suppliers
  • 45. How should we implement ERPsystemsObtain the right mix of people, processes andtechnology!!
  • 46. How should we implement ERP Systems?PeopleProject StructureShould be aligned to processesProcessImplementation Process (outlined in detail)Implementation Process (outlined in detail)Adapt your processes to those of the ERP.TechnologyHardwareSoftwareIntegrated Systems
  • 47. ProcessDefinition and AnalysisHold discussions with various functional personnelto establish the actual number of systemsoperating at client site, what they are used for, whyoperating at client site, what they are used for, whyand how oftenProduce the Project Scoping Document outliningcurrent situation, proposed solution and budgetedtimeChallenge : REQUISITE EXPERTISE - No twoclients are the same
  • 48. Process2. Design• Prepare various functional reports - specifiescurrent scenario and wish list• Prepare Design document which specifies howthe system is going to workthe system is going to work• Prepare test scripts to be followed on systemtesting• Map out the interface paths to various modulesChallenge : INFORMATION SHARING -Availability of staff
  • 49. Process3. Build• Configure system as per set up documentspecifications i.e. transfer conceptual model intoreality• Test system to verify accuracy (preliminary tests)• Test system to verify accuracy (preliminary tests)Challenge : TECHNICAL ENVIRONMENT -System functionality
  • 50. Process4. Transition• Train users on their specific areas• Assist in test data compilation and system testingby users• Finalise the Live system and capture opening• Finalise the Live system and capture openingbalancesChallenge : USER RESISTANCE -Understanding and acceptanceData preparation
  • 51. Process5. Production• Official hand holding• Effectiveness assessment• Business and Technical Direction recommendations
  • 52. Best Practices
  • 53. What is Best Practice?A best practice is a technique or methodologythat, through experience and research, hasproven to reliably lead to a desired resultproven to reliably lead to a desired resultA commitment to using the best practices in anyfield is a commitment to using all the knowledgeand technology at ones disposal to ensuresuccess.
  • 54. Role of Best Practices
  • 55. Best Practice and BenchmarkingBest Practice is a term often used in the literaturein ways that treat it as identical to benchmarking.Others connect benchmarking with quantitativeindicators and leaves best practice in the realm ofindicators and leaves best practice in the realm ofmore qualitative, extended descriptions ofsuccessful firms and their processes.Benchmarking is one aspect of ‘best practice’.
  • 56. Best Practice DefinedA holistic, comprehensive, integrated and cooperativeapproach to the continuous improvement of all aspects ofan organisation’s operations.It includes leadership, planning, people, customers,It includes leadership, planning, people, customers,suppliers, the production and supply of products andservices, and the use of benchmarking as a learning tool.These practices, when effectively linked together, canbe expected, to lead to sustainable world class outcomesin productivity, quality, customer service, flexibility,timeliness, innovation, cost and competitiveness.
  • 57. BenchmarkingBenchmarking is the process of comparing onesbusiness processes and performance metrics toindustry bests and/or best practices from otherindustry bests and/or best practices from otherindustries. Dimensions typically measured arequality, time, and cost. Improvements fromlearning mean doing things better, faster, andcheaper.
  • 58. BenchmarkingBenchmarking involves management identifyingthe best firms in their industry, or any other industrywhere similar processes exist, and comparing thewhere similar processes exist, and comparing theresults and processes of those studied (the"targets") to ones own results and processes tolearn how well the targets perform and, moreimportantly, how they do it.
  • 59. Best Practice RequiresCommunication: Frequent and detailed exchangeenhanced by communicationContinuous improvement: Ongoing goal formation,preparation of action plans and evaluationpreparation of action plans and evaluationCulture consciousness: Constant formal and informalstudy aimed at a desirable organisational cultureIn summary Best Practice is a comprehensive, integratedand co-operative approach to the continuousimprovement of all areas of the business/service
  • 60. Why Adopt Best Practice?Proven quality approach to service deliveryIncreased productivityIncreased customer satisfactionMinimised riskMinimised riskReduced costsImproved communication between IT and thebusiness and your organisation
  • 61. Choosing Best PracticeHow many of us can decide on the BestPractices for the organisation? And that to ERPSome ParametersSome ParametersDoes the practice actually mitigate risk or satisfya security requirement?Can practice be implemented as planned?Does the benefit from a practice outweigh itscost?
  • 62. Technology• Technology is an enabler, not the driver (it is thereto assist the organisation to achieve businessgoals)• It is a means to an end, not the end• It is a means to an end, not the end
  • 63. Conclusion• ERP systems provide a mechanism forimplementing systems where a high degree ofintegration between applications is required• The Business Case or Value Proposition for• The Business Case or Value Proposition forimplementation must be outlined• To successfully implement - a proper mix ofpeople, processes and technology should bemaintained
  • 64. Automatic VehicleLocation System
  • 65. Vehicle Location System• What is AVLS / APRS?- Automatic Vehicle Location System- Automatic Position Reporting System- Automatic Position Reporting System
  • 66. Vehicle Location System• Vehicles Equipped with GPS Receiver• Mobile Sends GPS Location Data over RF Path• Mobile Sends GPS Location Data over RF Path• Fixed End Receives Location Data and Displayson Computer
  • 67. How does GPS work?Satellite SatelliteSatelliteSatelliteSatelliteSatelliteSatellite
  • 68. GPS Receivers• Handheld– Garmin– Magellan• Dedicated• Dedicated– Oncore• Receiver / Antenna Combos– Tripmate (Delorme)– Pharos– Tripnav
  • 69. Goals and Objectives• Evaluate the effectiveness of the AVLS system• Demonstrate capability of AVLS technology to:- Improve dispatch process- Optimize Police Patrol timing- Collect engineering data- Collect engineering data
  • 70. Quantity Over Quality• Better to get a bad position than no position?• Settings are dynamic—adjust them according toconditions• Use an external antenna whenever possible• Use an external antenna whenever possible• Different grades of antenna: multi-path rejection,receptivity• Antenna is the GPS position, not the unit• Multiple antennae will interfere with each other—maintain at least a foot of spacing
  • 71. Conclusion• Field work with GPS units is a dynamicundertaking…• Not just a walk in the woods with the GPS• Never trust your life to a GPS unit• Never trust your life to a GPS unit• Look up– pay attention to conditions that affectyour GPS reception and your safety (cliff edges,snags, traffic!)• Look down– don’t ignore your unit, it may betelling you something important• Never trust your life to a GPS unit!
  • 72. THANK YOUfor your TIME and PATIENCE