About the Project
Quick Links
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 (in progress)
- 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
- Increased capacity to handle larger volumes of Vessel registrations (as a result of WAHVA)
- 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)
- Improved cost efficiency; Decreased number of hours spent on system maintenance
- Decreased number of data errors (process prone to human error and lack of awareness)
- Enable other MSS Business lines to leverage registration data collected for industry oversight and service delivery
Product Vision Board (in progress)
| View file |
|---|
| name | Product Vision Board.pdf |
|---|
| height | 250 |
|---|
|
Product Roadmap
TBD
About Vessel Registry
About the service
...
Business Capabilities/Services provided
...
Identified Business Capability Services
These may are my not be identified as core services – further analysis required.- 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??