1. Successful Development of CGIS's System Functionalities (Year 1 and Year 2) Through Comprehensive Requirement Gathering Program Mulia Senayan, Jakarta 17th October 2011

2. Introduction to CGIS
CGIS 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 divisions
GE Smallworld was chosen as CGIS platform.

3. Where are CGIS now Year 3 2009 2010 2011 2012 2013 Customer Management
Operation &
Maintenance
Asset
Management
Asset Planning &
Construction
Current ly in year 3
More than 10 functions have been rolled out to users
Currently in the stage requirement gathering for year 3 functions.
So what do TNB do during this requirement
Asset Register
Project
Kick-off
2009
2010
2011
2012
2013

4. Phases of Requirement Gathering
Business Requirement
Functional Requirement
Review As Is Process
Identify gaps
Identify pain points
Capture Management’s Visions
Review To Be Process
Propose User Interface
Propose Report, Application

5. Business Requirement

6. Define “To-Be” Processes Develop Blueprint Design
Business Requirement
Scoping and Planning
Review “As-Is”
Processes
Define “To-Be” Processes
Develop Blueprint Design
Phases
Schedule for workshops
Inform users of workshops
Collect relevant documents
Analyze information prior to workshops
Conduct “As-Is” workshops with all 6 Divisions
Conduct “As-Is” validation workshops
Sign-off of “As-Is” processes by users
Conduct Visioning and Focus Group Meetings
Identify gaps and improvement opportunities
Conduct “To-Be” validation workshops
Sign-off of “To-Be” processes by users
Develop Process Blueprint Document
Review and Signoff Process Blueprint
Key Activities

7. Functional Requirement
TNB CGIS
Master Plan
Functional Requirement Report 50
Functions
Functional Requirement Workshops
Discuss and Gather Functional Requirements
Feasibility study with System Owners
To Be Process Blueprint
Best Practices
Phases
Scoping & Planning
Review “To Be” processes
Functional Requirement Gathering
Develop Functional Requirement Report Design

8. Functional Requirement
Scoping and Planning
Review “To-Be”
Processes
Functional Requirement Gathering
Develop Functional Requirement Report Design
Phases
Schedule for workshops
Appoint Functional Implementation Taskforce
Inform users of workshops
Analyze information prior to workshops
Internal discussion to propose application and interface
Review To-Be Process
Conduct Functional Requirement workshops
Conduct system study
Develop Functional Requirement Report
Review and Signoff Functional Requirement Report
Key Activities

9. Challenges 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.

10. THANK YOU