cnam.ca

Infrastructure Registry for Municipal Assets (IRMA)Presented by: Nova Scotia Department of Municipal Affairs

Keeping the Pace

Asset Management: The Nova Scotia Approach

2

Identify FundingWorking

Group

*Strategy

Development*

▪ Tools

▪ Projects

▪ Resources

Provide

▪ Leadership

▪ Direction

▪ Support

Implementation

Keeping the Pace

Overall Program Framework

3

NSGI Platform

The Pilot Projects

Data Collection (Excel Based)Future Data Collection (GIS)

Infrastructure Registry for Municipal Assets

(IRMA)

Keeping the Pace4

• “One Stop Shop”

• Storage and mapping for municipal infrastructure assets

• Provincially funded

• Leverages the use of existing Provincial IT/geomatics resources

Introducing IRMA

Keeping the Pace

Technical Processes and Considerations: Requirements

5

Business Analysis Support

• Preparation of preliminary system

business and usability

requirements

• Investigation of existing solutions

and industry best practices

• Preliminary project road mapping

Keeping the Pace

Technical Processes and Considerations: Requirements

6

Confirmation of Contractor’s Scope *Early and Often*

• Requirements (e.g. business, data,

functional, non-functional, reporting,

architecture, and transferable*)

• System development lifecycle

activities and tasks to support

implementation (e.g. analysis,

design, build, test, and deployment)

• Application training requirements

• Future requirements gathering needs

(e.g. future phases of work etc.)

Keeping the Pace

Technical Processes and Considerations: Requirements

7

Validation of Business

Requirements

• Conducting “in-person” business

requirements sessions with key

project stakeholders

• Producing requirements and

estimation documentation

Understanding the Architecture

• Important to determine how to

approach overall architecture and

database design

Keeping the Pace

• Mapping Requirements to User

Stories (Traceability)

• Provides a transition from

requirements to application

development

• Consolidates requirements into

specific categories (“stories”)

Technical Processes and Considerations:Requirements

8

Keeping the Pace9

Technical Processes and Considerations:

Database Design and Map Layer Properties

Documenting Specifications

Outline properties of the geodatabase:

• Schema was based on macro-enabled MS excel spreadsheet created for field collection

• IRMA (Phase1): Supports retrieval (read-only) asset data via web application

• IRMA (Future Phases): Further exploration to support editing of asset data via web application

Keeping the Pace10

Technical Processes and Considerations:

Database Design and Map Layer Properties

Documenting Specifications

Examples of information included:

• How feature classes (i.e. asset classes) are displayed as map layers in the application

• Coordinate system requirements

• Map document design and symbology

• Geodatabase fields

• Condition symbology

• Domains

Keeping the Pace

Technical Processes and Considerations:Deployment

Deployment and Configuration Manual

• Provides instructions on how to deploy and configure the application solution

• Covers the deployment and configuration of the following system components:

• Map Services

• Geoprocessing Service

• Map Viewer Application

11

Keeping the Pace

12

IRMA at a Glance:

The Dashboard

Keeping the Pace13

IRMA at a Glance:

The Dashboard

Keeping the Pace14

IRMA at a Glance:

The Dashboard

Keeping the Pace

15

IRMA at a Glance:

The Data Viewer

Keeping the Pace

IRMA at a Glance:

Layer Pop-ups

Keeping the Pace

IRMA at a Glance: Map Widgets

17

LESSONS LEARNED

18

Stakeholder Engagement

• Up-to-date Stakeholder Registry

• Commence support planning as early as possible

LESSONS LEARNED

19

Non-Functional Requirements

• Important to clients but are often overlooked

Examples:

• Compatibility

• Deployability

• Extensibility

• Maintainability

• Security

• Usability

LESSONS LEARNED

20

Reduce Technical Jargon

• Take the time to understand the business

• Account for subject matter experts / clients with different professional backgrounds

Keeping the Pace

Lessons Learned

Conducting Parallel Projects

What should come first?

The data or the solution?

Photo Source: Canadian Hatching Egg Producers (http://chep-poic.ca/) 21

Keeping the Pace22

Keeping the Pace23

Questions?