Presentation on theme: "Successful Development of CGIS's System Functionalities (Year 1 and Year 2) Through Comprehensive Requirement Gathering Program Mulia Senayan, Jakarta."— Presentation transcript:
1Successful Development of CGIS's System Functionalities (Year 1 and Year 2) Through Comprehensive Requirement Gathering Program Mulia Senayan, Jakarta 17th October 2011
2Introduction to CGISCGIS stands for Corporate Geospatial Information System.Implemented in Tenaga Nasional Berhad for 6 divisions covering electricity and telecommunication network as well as landed properties.50 functions were identified and chosen to be GISed from the existing business functions within the 6 divisionsGE Smallworld was chosen as CGIS platform.
3Where are CGIS now Year 3 2009 2010 2011 2012 2013 Customer Management Operation &MaintenanceAssetManagementAsset Planning &ConstructionCurrent ly in year 3More than 10 functions have been rolled out to usersCurrently in the stage requirement gathering for year 3 functions.So what do TNB do during this requirementAsset RegisterProjectKick-off20092010201120122013
4Phases of Requirement Gathering Business RequirementFunctional RequirementReview As Is ProcessIdentify gapsIdentify pain pointsCapture Management’s VisionsReview To Be ProcessPropose User InterfacePropose Report, Application
6Define “To-Be” Processes Develop Blueprint Design Business RequirementScoping and PlanningReview “As-Is”ProcessesDefine “To-Be” ProcessesDevelop Blueprint DesignPhasesSchedule for workshopsInform users of workshopsCollect relevant documentsAnalyze information prior to workshopsConduct “As-Is” workshops with all 6 DivisionsConduct “As-Is” validation workshopsSign-off of “As-Is” processes by usersConduct Visioning and Focus Group MeetingsIdentify gaps and improvement opportunitiesConduct “To-Be” validation workshopsSign-off of “To-Be” processes by usersDevelop Process Blueprint DocumentReview and Signoff Process BlueprintKey Activities
7Functional Requirement TNB CGISMaster PlanFunctional Requirement Report50FunctionsFunctional Requirement WorkshopsDiscuss and Gather Functional RequirementsFeasibility study with System OwnersTo Be Process BlueprintBest PracticesPhasesScoping & PlanningReview “To Be” processesFunctional Requirement GatheringDevelop Functional Requirement Report Design
8Functional Requirement Scoping and PlanningReview “To-Be”ProcessesFunctional Requirement GatheringDevelop Functional Requirement Report DesignPhasesSchedule for workshopsAppoint Functional Implementation TaskforceInform users of workshopsAnalyze information prior to workshopsInternal discussion to propose application and interfaceReview To-Be ProcessConduct Functional Requirement workshopsConduct system studyDevelop Functional Requirement ReportReview and Signoff Functional Requirement ReportKey Activities
9Challenges Users having minimal understanding of GIS Demonstration on the system has been incorporated in the functional requirement gathering workshops."Look and Feel” sessions are conducted to ensure that all requirements are built to users’ expectation.Different technical background between users and system developers.More visualization on functions proposed.the incompleteness of Functional Requirement Report which causes major enhancements during User Acceptance Tests.Most of the users are from engineering background and have minimal exposure on IT related projects.