Frequently Asked Questions

Chat with Your Vessel lets your team ask questions about the vessel information you provide through a chat interface. It can bring machinery manuals, maintenance records, sensor readings, and operational reports into the conversation. The product is available and already used by customers.

Yes. You can use Chat with Your Vessel with your machinery manuals and technical documents without installing sensors or using another Gelectric product. Maintenance history and other data sources can be added later when they are useful.

Sources can include machinery manuals, technical documents, maintenance logs, noon reports, operational records, and customer sensor data. We review the formats and access available, then configure the document preparation and data connections around your sources.

Yes. Chat with Your Vessel can use data supplied from your own systems; it does not require that the data comes from another Gelectric product. The connection depends on how the source makes information available and what access your team can provide.

You might ask what a compressor manual says to check, what work was recorded during the last maintenance visit, or how cooling-water temperatures changed over an operating period. You can ask follow-up questions to focus on a particular machine, record, or time period.

Users ask questions in everyday language through the chat interface. Gelectric prepares the relevant documents and data connections behind it, so your team can explore the available information without writing database queries.

Use the answers to help find information and investigate questions. Their usefulness depends on the supplied sources and the question asked. Check the relevant documentation, equipment context, and onboard observations before making a maintenance or operational decision.

Vessel Monitoring connects available onboard machinery and sensor data in a shared monitoring workspace. Crew and shore teams can follow trends, review configured limits, and explore equipment behavior and vessel performance.

The scope depends on the equipment and signals available onboard. Examples include engines, generators, pumps, and other connected machinery, with measurements such as temperatures, pressures, vibration, power, speed, or operating loads. We review the sources needed for your monitoring goals.

We start by reviewing your existing equipment, signals, and available interfaces. Where suitable data is accessible, it can form part of the monitoring setup. If additional instrumentation is needed, we discuss that as part of the proposed scope.

Vessel Monitoring is the product for connected onboard data and ship-to-shore visibility. Condition Monitoring describes the specialist use of equipment readings to understand machinery behavior. Energy Monitoring, Emission Monitoring, and Predictive Maintenance are also covered on separate specialist pages.

Equipment trends can help your team identify changes worth investigating. Reviewing those readings alongside operating conditions, manuals, and maintenance history gives engineers more context for planning checks and maintenance. It does not guarantee that every fault will be detected or predicted.

Update frequency depends on the connected equipment, collection intervals, onboard setup, and communications. We review your connectivity and information needs when planning the monitoring setup, including how interruptions affect ship-to-shore visibility.

Digital Noon Reports turns the reports your crew already sends into structured vessel information. It brings reported values and operational remarks into dashboards and reporting workflows, reducing repetitive collection and copying for shore teams.

The workflow starts with your crew’s existing emails and report formats. We review sample reports and configure the setup around the information you provide, so the crew can continue with familiar reporting practices.

Share examples of your current reports and explain how your team receives and uses them. We review the fields, formats, and reporting needs, then arrange the report delivery and processing setup with you.

The workflow can surface missing or inconsistent information for your team to review. Your team can check the original report and clarify the entry with the vessel before relying on it for further analysis.

Yes. When Digital Noon Reports is connected to Chat with Your Vessel, your team can ask questions and request summaries of the available records. For example, you could explore machinery issues mentioned in crew remarks during a particular week.

Structured fuel and voyage records can help your team prepare operational reporting inputs and identify information gaps. The required records, calculation methods, and verification steps depend on the reporting task. Your team still needs to review the information against the applicable requirements.

The EEXI Calculator helps calculate attained and required Energy Efficiency Existing Ship Index values from vessel particulars. Our team works with the relevant inputs and provides a calculation result with its supporting information.

Typical inputs include vessel type and capacity, main and auxiliary engine data, fuel consumption characteristics, and reference speed. The exact information depends on the vessel and applicable calculation method. Our team can guide you through the required documents and particulars.

EEXI is a technical efficiency index based on vessel and machinery particulars under a defined calculation method. Operational reports describe activity and consumption over time, while exhaust monitoring measures available parameters directly. These sources answer different questions and should be reviewed in the appropriate context.

Use the Request an EEXI Calculation button on the product page or contact our team with your vessel details. We’ll discuss the required inputs and the calculation scope with you.

A calculation result supports the technical assessment. Any required verification or approval follows the applicable process with the relevant verifier or classification society. Discuss the intended use of the calculation with our team when defining the scope.

Start with a list of the documents, reports, and systems relevant to your first workflow. Examples of their formats, the period covered, and how information can be accessed help us understand the connection requirements. There is no need to have every source connected before choosing a starting point.

Yes. A workflow can start with a limited set of useful sources, such as machinery documents or existing noon reports. Additional records or sensor connections can be scoped as your team’s questions and needs develop.

Include the people who use the information and those who manage access to it. Depending on the product, that may involve onboard engineers, technical superintendents, operations staff, and IT or system owners. Together, we can identify useful questions and the sources needed to answer them.

Share your organisation’s requirements with our team before providing access to operational data. Ask us to confirm the proposed hosting, user access, retention, and data-handling arrangements for your setup so your technical and IT teams can review them.

The needs depend on the product, the connected sources, and the people using the workflow. Tell us which teams and locations need assistance so we can discuss onboarding, training, and support arrangements as part of the proposed setup.