Crew and common data
Use a shared crew/vessel context across the workspace and connect jobs to the people involved.
Shipboard operations & safety preparation
Chief Assistant
Connect daily jobs, crew coordination, safety preparation and operational documents in a single shipboard workspace.
What it is for
Help the Chief Officer and other responsible staff organise routine work, reduce repeated entry and find the relevant job, record or document more easily. Support preparation while keeping approvals and operational decisions with authorised people.
Main capabilities
Jobs and safety
Prepare daily and weekly work plans, toolbox material and job safety packages. Review the relationship between a job, its RA/JHA, permits and checklists.
Availability and actual work
Review crew availability and overtime previews, distinguish plans from actual participation and post confirmed actual work through the supported workflow.
Documents and records
Organise certificates, operational records, document templates and report archives. Form support depends on the templates and mappings included in the release; not every company form is automatically filled.
A practical workflow
Select the correct vessel, crew and working date.
Prepare the work plan and review the crew, hazards and required documents.
Complete the actual toolbox discussion, checks, permits and approvals through the vessel’s procedures.- Record actual participation and review the resulting work/rest entries and document package.
Standards and professional responsibility
The workspace supports company-defined operational and safety procedures. Applicable SMS requirements, permits, flag-state rules and document formats must be configured and checked for the vessel. Work/rest support uses the separate MLC module; the workspace does not certify compliance with the entire MLC, STCW or ISM framework.
Generated text and prepared packages are drafts until reviewed by the responsible people. The application does not conduct a risk assessment on their behalf, verify safe conditions in the workplace, issue a permit or sign a document automatically. The Master, Chief Officer and designated permit issuers retain their duties and approval responsibilities.
Official references
References describe the regulatory framework; they are not endorsements or approvals of this software.
Data, access and confidentiality
Autonomous and server-based working modes use different storage environments. Server access is tied to the configured organisation/vessel; autonomous use depends on local folder permissions and backups. Actual retention, recovery, access logging and hosting arrangements must be established for each customer. Do not place working crew records in the public website or public sample.
Keep a recoverable copy of important records. Restrict access to authorised personnel and review exported files before sharing. See the privacy notice and browser storage information for the website’s current draft disclosures.
Development, updates and validation
These products are under active development. Changes are reviewed and tested before release within the scenarios covered by the relevant checks. Calculation and document workflows require regression checks; release-specific validation must identify the tested scope and remaining limitations.
Testing reduces the risk of errors but does not establish that every vessel, cargo combination, rule exception or document is covered. No approval by a flag administration, classification society, IMO or ILO is claimed unless separately documented for a specific release. No guarantee of uninterrupted operation, error-free results or zero data loss is made; mandatory legal rights remain unaffected.
Maritime AI assistant
In development · Not included in the current public demo
A maritime-focused AI assistant is being developed for the product suite. It is intended to help users navigate the software, search a maintained maritime reference library, understand procedures and investigate operational questions.
Customer-controlled, local deployment
The planned architecture runs the AI model and its knowledge base on the customer’s equipment or within the customer’s approved server environment, without external AI services. Documents, drawings, diagrams, questions, prompts and conversations are intended to remain inside that environment rather than being sent to an outside model provider.
This is a development commitment, not a description of a released feature. Before delivery, deployment-specific network isolation, logs, backups, access controls and the offline update process must be verified. A model running on a customer server is local to that controlled environment; it is not necessarily running on the user’s individual computer.
The reference library and regulatory material are intended to be maintained through reviewed updates. AI answers must be checked against current authoritative sources and vessel procedures; they do not constitute operational approval or legal advice.
Try it or discuss a deployment
Contact us to discuss the working version, deployment mode and a suitable evaluation. This product page is public; the working application and customer records are not made public by this page.
Please do not send crew records, private drawings or sensitive cargo files with an initial request.
Software licence terms remain in draft. Licence options · Full safety notice