2. Overview
1. ROMAN II Background
2. Development Phase
3. Systems Implementation
4. Documentation of Standards
5. Establishment of User Group
6. What is next?
3. 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
4. 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.
5. 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
6. 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
7. 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
8. What is Next?
Better communication with RSL
Bug resolution
Future improvements
Link to New Zealand
RIMS?
Link to Australian Eastern States
IPWEA, NAMS