Project Scope and Implementation Information
In this article, you find a description and comments around a suggested timeline, as well as documentation to miscellaneous articles and documentation.
Project
In the below articles you find a description of the Adonis Project Delivery Methodology and other useful information
https://adonishr.atlassian.net/l/cp/0pmZpgsz
https://adonishr.atlassian.net/l/cp/8VNXG4pv
https://adonishr.atlassian.net/l/cp/DTnoX0u1
Scope
In Scope
API
Inserting data
Adonis will copy and make the necessary API methods to insert the below data available in dedicated customer APIs. The cost is part of the quotation
Personal Data limited to
PIN
Full Name
Assigned Vessel
Rank/Position
Passport or Driver’s License
Employment Start/End and Termination reason
Trips as
Voyages (see below)
Port dates/Itinerary
Extracting Data
The customer will use the existing method for extracting data from the system as described in the following document and chapter:
Database views will be scoped and created together with Adonis technical consultants during the project phase
Planning Module
The customer will create a Trip as a Voyage via existing API calls. A Voyage is similar to a Project but has more functionality around it. By moving a Voyage start date, one can also move the Onboard activity start date for all linked persons accordingly.
Inside a Voyage (Trip) there can be several port calls, as needed for Crew Changes
Adonis suggests that a plan is created manually by the users. By using the Voyage a user can not assign persons to shifts outside the Voyage dates. There is easy functionality to copy previous plans.
The planning is linked to the Crew Change module that will be used onboard.
There are existing API calls for creating Voyages, however, a new API for creating the ports is needed.
It is still possible for the customer to create one plan per trip as wanted.
Crew Change
The system will be made available for onboard users.
An onboard role will be responsible for confirming the Onboard activities at the date the person sign on, and the same upon sign off
Out of Scope
Customs Reporting that potentially requires more personal details and crew effects in the system
Integrations built by Adonis to third parties
Competences & Requirements, Next of Kin or similar personal Information
Employee Portal
Onboard modules besides Planning and Crew Change
Sample Timeline
The sample timeline is based on the scope discussed in our meeting on the 14th of July 2022.
Assumptions
The below timeline indicates that the full specification of the needed API functionality is started upon contract signature
The kick-off, 3-5 days, will be performed onsite with dedicated customer resources made available
A second onsite visit, most often needed when we get to the User Acceptance Testing can be planned for
The Customer will prepare the environments and have the installations along with user access to the application in place by kick-off
There is no need for standard data migration, as all persons will come in via the API
Vessel Installations can be performed at the same time as the configuration.
Adonis can perform installations as long as the environment is prepared and proper remote connections and access are provided
A staged roll-out for the vessels is not planned for but can be done, together with the customer
The customer is responsible for their own Documentation, User Acceptance Testing, and End User Training
Adonis is willing to do End User training, however, this is not included in the cost or time estimates.
A delay in the contract signature can result in a delay in the Project mobilization and the Go live. December is a month where resources often take vacations, and can by such prolong the implementation phase.
Getting started with your Adonis Products
In the following article, you find full information and instructions on how to get started with your Adonis Products.
The following chapters and information will be relevant for the Customer.
Technical Requirements and Installations
Preparation of data
Defining General Codes
General Codes is used as a term for pre-defined codes that will be used throughout the system in various drop-down tables and similar.
General Code Table | Used for/Purpose | Related Manuals |
Departments | Used to identify the departments you have on a vessel. It is also used for being able to open a Rotation plan by department, between vessels. E.g. a user wants to look at the schedule for the Deck department across all vessels. | |
Embark_Disembark | These are the reasons for why a persons signs on or off a vessel. It can be a normal end of contract, or it can be due to medical or other ad hoc reasons. | |
Rank | Used for assigning a person to a Rank, as well as for creating the organization structure onboard a vessel. In order to create a position onboard, the rank must exist in General Codes table. | |
Termination Reason | Reasons for why a person is no longer active within the company. It should not be confused with Disembarkation reasons. Termination reasons might be that a person is deceased, has started working for another company or similar. | |
Travel Documents | These are the codes used when the user wants to register e.g. a passport information on a person. | |
Colors | Colors are used for registering eye and haircolors which some Ports requires when going through customs. |
|
Activity Codes | Used to track the movement of a person. E.g. when was a person onboard, when was he at home, is he sick, travelling, visiting office, etc. An activity is always registered with a Date From and Date To, and a person can only have one activity for a day. | |
Crew Effect Codes | Used for registering Crew Effects which is needed in some Ports and customs reports. E.g. Liquor, sigarettes, etc. | |
Rotation Plan Codes | Used for identifying the Rotation plans. Example is Deck, Engine, Factory codes. | |
Rotation Plan Views | Used for grouping the Rotation Plan Codes. Can be set with security so that a person e.g. is only given access to Deck plans. |