The language of maritime contract governance, in plain terms. Every name here matches the platform exactly, so what you read is what you'll use.
In contracting, a tender is a formal, published request for a defined scope of work. A vessel publishes exactly what it needs done. Qualified service providers bid against that same scope. The vessel awards one of them under recorded authority.
It's the discipline of institutional and government procurement, brought to maritime contracting. Two things set it apart from a quote traded over email: the scope is written once and identical for every bidder, and every step (the bids, the clarifications, the award) stays on one record, attributable and dated.
One note for the yacht world: on MBN, a tender is the contract process, not the vessel's tender boat.
MBN governs three organization types, plus the people inside them and the officer who reviews them.
When a service provider registers, it declares how it will operate. The choice sets which roles it assigns and how tenders route to it.
A tender reaches a service provider only when two things line up: an engineering category the provider serves, and a service sub-region the provider covers.
MBN organizes coverage into 4 region groups and 14 sub-regions. A service provider serves multiple sub-regions within a single group (never across groups); a vessel operates at the region-group level. Matching is by engineering category and service sub-region together.
Active coverage today is the United States and the Caribbean, with the Mediterranean and Central America built into the platform for expansion.
Registering an organization is a guided, autosaving flow with a fixed set of stages.
Flat licenses, monthly or annual. No percentage of contract value, no per-deal fees. Prices include 7% tax.
Once tendering is grounded, MBN extends governance into the rest of the contract lifecycle. None of this is live yet.