Standardising Business Practices & Lookups

The ROMAN II Experience

Freddy SalvadorARRB Group Ltd

22 March 2012

Overview

1. ROMAN II Background

2. Development Phase

3. Systems Implementation

4. Documentation of Standards

5. Establishment of User Group

6. What is next?

ROMAN II Project Background

WA Roman System - Access DB- 20yrs old- Unmaintained in last 5 years- no real ownership, hence lack of use- lack of support material

WALGA - Identified needs- Managed tender process

Tender process identified RAMM as best replacement tool

It includes Software and Processes

Development Phase

Make most of existing, improve some, and add new tools and processes

RAMM - Only ONE version of the software exists – RSL worked heavily on using the best of both worlds.

System Implementation

ChallengesUrban/Rural differences/resources

Database TranslationsTemplate DB created to cater for default valuesStandard lookup tables and locking some

Rollout ProcessDB Naming Convention (live vs. test)

TrainingBasic TrainingLevels of understanding/education/background

Documentation of Standards

ROMAN II Website (roman2.com.au)Central place (documentation, forums, ticketing system, support, etc.)

Operational Rules DocumentNetwork setup guidelinesLookup table contents

Guidelines documentsCondition rating manualTraining material

Establishment of User Group

Who is in?Committee (LG Users, Consultants, RII and WALGA)All users get invited

TasksAgree recommended future improvementsManage asset lookups including processes

Identify/Prioritise field trialsNew tools, processes, ideas.

UDT standardizationIdentification and implementation

What is Next?

Better communication with RSLBug resolutionFuture improvements

Link to New ZealandRIMS?

Link to Australian Eastern StatesIPWEA, NAMS

Questions?