From an equipment fault to a port call. Explore practical guidance, see the source and turn what you learn into a service brief.
PELASTRIONKnowledge assistantBrowse by system, task or stage of the job.
A useful first message is not necessarily a long one. Start with the vessel, location, departure window, affected system, observed fault, and a reachable contact. Add documents only after the desk confirms an appropriate channel.
Read the guideUse the critical-priority inquiry route for a time-sensitive service issue. This website is not an emergency communications channel and cannot decide whether a vessel is safe to sail.
Read the guideCorrect equipment identification makes an inquiry easier to scope. Read information already visible on the display, exterior label, or existing equipment register; do not remove covers or enter service menus.
Read the guideRemote support begins with an agreed scope and a responsible person onboard. It is not unattended permission to change vessel systems.
Read the guideA recorder alarm should be described precisely. Record the displayed message, the affected input if named, and the time the symptom was observed. This guide helps prepare a service inquiry, not perform a repair.
Read the guideAn annual-test inquiry should establish the equipment, vessel requirements, available port window, and document issuer before attendance is promised.
Read the guideDescribe whether you need fault diagnosis, equipment work, survey coordination, or clarification of documentation. These are different scopes even when they concern the same radio installation.
Read the guideProgramming, battery replacement, routine checks, shore-based maintenance, and replacement supply are not interchangeable. State the actual task and the document you need.
Read the guideAn intermittent symptom is easier to investigate when the inquiry records when it occurs and what else was happening. Observation is useful; deliberately provoking a failure is not.
Read the guideIdentify the display, processor, and scanner from existing records where possible. A useful brief distinguishes a missing picture from a missing overlay, heading input, or display alarm.
Read the guideA heading mismatch should be escalated to the responsible onboard team. The website can help prepare the fault information but cannot provide a safe-to-sail or calibration decision.
Read the guideDescribe what the onboard equipment shows and how the issue came to your attention. A third-party vessel-tracking website is not a substitute for an authorized equipment assessment.
Read the guideStart by identifying which layer of the system appears to be affected. A chart entitlement issue, a hardware fault, and a missing sensor input need different review paths.
Read the guideReport the alarm text, system identity, and the functions affected. Do not bypass, suppress, or change watch-alarm settings to make an issue disappear.
Read the guideA connection complaint can involve the terminal, service account, onboard network, individual device, or shore-side provider. Describe the affected layer without changing configurations.
Read the guideThe initial public inquiry is for the minimum facts needed to route work. Supporting evidence often needs a different, access-controlled channel.
Read the guidePrepare a parts quotation request with equipment details, quantities and delivery requirements. Availability, compatibility and pricing are confirmed in your PELASTRION quotation.
Read the guideA useful comparison covers equipment compatibility, downtime, remaining support, installation effort, and the documents needed to close the work. This website does not produce a reliable repair estimate without technical review.
Read the guideA warranty or return inquiry starts a review. It does not establish coverage, fault attribution, return authorization, or reimbursement.
Read the guideThe delivery address needs to describe the receiving arrangement, not just the port. Confirm the handoff with the agent and supplier before a shipment is released.
Read the guideA clear service scope identifies the technical task and each responsible party. A logo or training certificate should not be treated as universal authority for a company to issue regulated documents.
Read the guideKnow what document you are purchasing. Attendance notes, a repair report, commissioning records, and a regulated certificate serve different purposes.
Read the guideCombining planned tasks can simplify coordination, but it does not make all tasks interchangeable or give one supplier authority to issue every document.
Read the guidePELASTRION’s corporate certification program is underway. Confirm the applicable qualification, service scope, performing organization and document issuer for your vessel and task.
Read the guideUse the service assistant to organize what needs confirmation before an attendance. Preparing a brief does not book a visit or certify readiness.
Read the guideA schedule change should refer to the existing inquiry or job and make the old and new arrangements easy to compare. Avoid creating duplicate instructions.
Read the guideSouth Florida based, PELASTRION supports vessels worldwide. Start with the exact location, equipment and work window so we can define the service plan.
Read the guideUse the quote inquiry to explain the result you need, not only the device name. The service assistant prepares a brief; it does not calculate a binding price.
Read the guideA useful update tells you the current stage, the unresolved dependency, the responsible person, and the next agreed update. A generic “in progress” is not enough.
Read the guideThe closeout package should make the work understandable to someone who was not onboard. Use this guide as a review checklist, not a substitute for the responsible technical review.
Read the guideAn equipment baseline helps turn repeated inquiries into a clearer service history. The fleet assistant helps prepare that baseline in a conversation you can save or download.
Read the guideCompare an individual service inquiry, planned maintenance, and an ongoing fleet-support discussion. The appropriate model depends on scope, frequency, information quality, and confirmed coverage.
Read the guideEngine service starts with the symptom, equipment identity, operating context, and the work window. The website helps organize that information; it does not provide remote repair instructions or authorize sea trials.
Read the guideMarine cranes, davits, hydraulic systems, and launch equipment can involve mechanical, electrical, hydraulic, structural, and regulatory responsibilities. A service inquiry should distinguish ordinary troubleshooting from inspection, proof-load, or certification work.
Read the guideDC power issues are easier to scope when the inquiry identifies the affected circuit, voltage, equipment, recent work, and observed behavior. The site does not instruct visitors to bypass protection, work live, or alter battery systems.
Read the guideTry a system name or simpler words. You can also search the FAQ or prepare a technical question.
Browse common questionsAsk a question