Scope

In Scope

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

The customer will use the existing method for extracting data from the system as described in the following document and chapter:
https://adonishr.atlassian.net/wiki/spaces/UD/pages/3645079565/AdonisWebServices+-+Consume+example#Example-consume-DB-views-via-API-(AdonisIntegrationWebService)
Database views will be scoped and created together with Adonis technical consultants during the project phase

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.

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

Customs Reporting like I-95, I-408 as it 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

The sample timeline is based on the scope discussed in our meeting on the 14th of July 2022.

...