Standardising Business Practices & Lookups The ROMAN II Experience Freddy Salvador ARRB Group Ltd 22 March 2012
Overview1. ROMAN II Background2. Development Phase3. Systems Implementation4. Documentation of Standards5. Establishment of User Group6. 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 PhaseMake most of existing, improve some, and add new tools andprocessesRAMM - Only ONE version of the software exists – RSL workedheavily on using the best of both worlds.
System Implementation Challenges Urban/Rural differences/resources Database Translations Template DB created to cater for default values Standard lookup tables and locking some Rollout Process DB Naming Convention (live vs. test) Training Basic Training Levels of understanding/education/background
Documentation of Standards ROMAN II Website (roman2.com.au) Central place (documentation, forums, ticketing system, support, etc.) Operational Rules Document Network setup guidelines Lookup table contents Guidelines documents Condition rating manual Training material
Establishment of User Group Who is in? Committee (LG Users, Consultants, RII and WALGA) All users get invited Tasks Agree recommended future improvements Manage asset lookups including processes Identify/Prioritise field trials New tools, processes, ideas. UDT standardization Identification and implementation
What is Next? Better communication with RSL Bug resolution Future improvements Link to New Zealand RIMS? Link to Australian Eastern States IPWEA, NAMS