What never got written down — will now be known.
What fixed it, and what did not, for your make and model — cited to the source.
Collective is built around the sources engineers actually use: manufacturer manuals and service bulletins, engineering forums, Q&A sites, and engineers' own accounts of a fault and how it was fixed. A source is added only where its owner's terms allow it, and every line links to it. Any summary shown is machine-generated and unverified.
Fleets that opt in will be able to share structured fault-and-fix fields from closed faults and work orders; their company identity is replaced with a coded reference, and vessel names, IMO/MMSI numbers, crew names, serials and locations are removed — no scrubbing is perfect, so free-text notes are excluded by default. Fleet-contributed findings will appear only once at least five separate fleets have independently logged the same failure and fix.
Nothing here is engineering advice: always follow your OEM manual and your SMS.
The fix that worked was traded on a dock, in a group chat, between two engineers who never wrote it down anywhere searchable. A search engine indexes what became public — manuals, the fraction anyone bothered to publish. Collective gathers it per make and model — manufacturer files, engineering forums, Q&A sites and engineers' own fault-to-fix accounts, each cited to its source — and adds structured fault-and-fix fields from closed faults and work orders as fleets opt in. Most of what a good engineer knows sits below where search stops.
A query is matched to the equipment make and model, then returns the symptom, the cause and what was done for that make and model, each with a citation to its source. Any summary shown is machine-generated and unverified. Fleet-contributed findings will be kept as a separate answer and will appear only once at least five separate fleets have independently logged the same failure and fix.
A fault your crew fixes once will become an answer another fleet never has to rediscover. Once at least five separate fleets have independently logged the same failure and fix, it will be searchable for every fleet on the network, at no extra cost to any of them. Facts grouped by equipment model are held to a stricter rule, described below.
None of this changes what your crew already does, and sharing is opt-in per fleet. Structured fault-and-fix fields from closed faults and work orders are read in the background, not through a tool anyone has to open. Your company identity is replaced with a coded reference, and vessel names, IMO/MMSI numbers, crew names, serials and locations are removed. No scrubbing is perfect, so free-text notes are excluded by default. What crosses is a fault and a fix. Counts are shown in bands. Every fact publishes only once at least five fleets have contributed; a fact grouped by equipment model additionally needs a minimum population of fleets running that model and a spread of different faults and outcomes, so rare configurations are held.
MTU, Caterpillar, and a handful of others power most of the fleet. A fault on one of those engines is a fault every other yacht running the same one will eventually see. Collective doesn't need to know which yacht reported it — only that it happened — and, as fleets opt in, what fixed it.
Plausibility checks against engineering limits are being built: the aim is that a reading which breaks a real thermal or pressure limit is flagged before fleet agreement is ever counted, because five fleets agreeing isn't proof if it isn't physically possible. These checks are not live yet — one more reason any label here is unverified and nothing here replaces your OEM manual or your SMS.