Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

About the Project

TitleLink
Project DevOps Backloghttps://dev.azure.com/transport-canada/DSD-MARINE Vessel Registry/_backlogs/backlog/Team Kraken
Working Documents Repositoryhttps://034gc.sharepoint.com/sites/VesselRegistryCSPSPremiumLearner
Legacy Systems/wiki/spaces/MAR/pages/161677331 (Large)
/wiki/spaces/MAR/pages/158105635 (Small)

Overview

...

Project delivery

To facilitate the process of design and development for the Vessel Registry project, we are following the UK Government methodology for Agile service delivery laid out in their Service Manual.

The service manual recommends breaking down a service design project into phases:

Expected Business Outcomes

...

Product Vision Board

TBD

Product Roadmap

TBD


About Vessel Registry

About the service

...

Business Capabilities/Services provided

...


Canadian Register of Vessels (Large Vessel)

This register applies to vessels of all types and sizes including pleasure and commercial. This type of registration is required for:

  • vessels more than 15 gross tonnes used for commercial purposes, including government-owned vessels (if unsure of tonnage, check this explanation of tonnage measurements)
  • vessels that require marine mortgages
  • if you are planning to travel outside of Canada for extended periods of time

You may also choose to register your pleasure craft in the Canadian Register of Vessels if you wish to have an approved name and port of registry for your vessel or show proof of ownership.

This type of registration is not required if:

  • your vessel does not or will not have a mortgage
  • you do not wish to register an “official” name
  • you don’t intend to travel outside of Canada

Small Vessel Register

This registry only applies to commercial (non-pleasure) vessels that are 15 gross tons or less.

This type of registration is required for:

  • vessels less than or equal to 15 gross tonnes used for commercial purposes with propulsion motors of 10 horsepower (7.5kW) or more (if unsure of tonnage, check this explanation of tonnage measurements)
  • commercial river rafts
  • government-owned vessels with propulsion motors of 10 horsepower (7.5kW) or more

Identified Business Capability Services

These may are my not be identified as core services – further analysisrequired.

  • 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

These are the Core systems that maintain Vessel information and should be used as the system of record for feature sets/services.

All systems do not implement delete?

  • 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

It is believed that each system implements a search capability, but only a few do a search across the core systems. The majority are only searching within their own data repository, lots a places for error and duplication here.

  • 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??

  • No labels