About the Project

Quick Links

Overview (in progress, copied from Gate 1 Deck)

• The program is unable to meet its services standards given the burden created by the current paper-based process therefore; at high risk of remission with the introduction of the new remission policy.
• There is an opportunity for the Vessel Registry business line to undertake an end-to-end service design that is user-centered and driven by operational needs. This work is currently supported by an MOU signed with the CSPS.
• MSS business lines require information collected during the Vessel registration process to manage and deliver their programs to Canadians and the Canadian industry. The management of vessel registration program, its data and related information is fundamental to other business processes and programs within MSS (e.g. Marine Insurance Unit, Regional Inspection programs), and within other TC groups (e.g. Navigation Protection Program and Wrecked, Abandoned, and Hazardous Vessels Act-WAHVA). However, the current registry systems are not connected to other program applications and do not provide direct access to vessel tombstone data (lack of interoperability and data-sharing capacity for end-users).
• Vessel registration data also supports the information requirements of other government departments (i.e. DFO, CBSA and CRA) to allow them to fulfil their mandates. However, the current registry systems do not have reporting capabilities.

Project delivery

• Discovery phase
• Alpha phase
• Beta phase
• Live

Expected Business Outcomes (in progress)

1. Ability to manage all existing and new Service Fees and Service Standards as a result of Service Fee Act (SFA) requirements; including ability to measure (track and report on) program costs and revenue
2. Increased capacity to handle larger volumes of Vessel registrations (as a result of WAHVA)
3. Increased interoperability and accessibility of data to internal users (e.g. NPP inspectors, WAHVA registry) and external users such as CCG, CRA, CBSA, RCMP and the public (increased number of services accessible through digital channels)
4. Improved cost efficiency; Decreased number of hours spent on system maintenance
5. Decreased number of data errors (process prone to human error and lack of awareness)
6. Enable other MSS Business lines to leverage registration data collected for industry oversight and service delivery

Product Vision Board (in progress)

Product Roadmap

About Vessel Registry

About the service

Business Capabilities/Services provided

...

Identified Business Capability Services

• Ports?
• Vessel Management
• Owner
• Search
• Mortgage
• Fleet
• Charterer
• Point in Time (see MEMS, MSIS II)
  • we need to understand what this means for Point in time; we should be able to do this as a feature

System/Business Capability

• Ballast Water - full CRUD; own database
  • pulls from THETIS and APCIS
  • does an update on own data if required
• Port State is same as Ballast Water
  • Port State system of record for all foreign vessels
• SIRS - System of Record for Domestic
• SCVRS (Small Vessel) - System of Record
• SRCS (Ship Registry - Large Vessel) - System of Record
  • May duplicate Port State data

Systems that use core vessel data or replicated version of vessel data

• ACES - query/creat/update; has own database; MPDIS integrated with ACES
• CPSCS-DET - query of port state
• CPSCS-VTP - CRUD of Port State connects to Port State
• CPSCSWQS - read Port State
• CPSCS-INNAV - push an IMO to port database and creates a vessel traffic record (interim which eventually gets validated and links to existing - see Vessel Tracking Record
• EPAIRS - creates records that have IMO number; no links to Port State (data integrity)
• MEMS - read-only from Port State, SIRS, ACES, MTRB, SCVRS for vessel tombstone data and then keeps a read-only copy
• MIUS - stores its own vessels and owners
• MPDIS - maintains its own database
• MSDQT - read from all core systems
• MSIS II - read-only query for Point in Time; keeps data in own database
• NTARS-MSDTS - query of all four core systems and the duplicates the data
• PID - CRUD; maintains its own database

General Notes

• Regardless of what solution we come up with, we need to consider document storage for completed forms and all other required supporting documents e.g. photographs, ship plans, etc.
  • Azure Storage, RDIMS, GCDocs??