Maritime & ShippingEvery change traced to vessel, rule and approval.
The maritime pack sets agents up around vessel and equipment requirements, class and statutory rules, safety-management controls, certificates, configuration changes, tests, maintenance and defects. They keep that record linked inside your Azure DevOps project, show what a change touches across the fleet, and open the actions it needs. Rule interpretation, survey and certification stay with the people and bodies that own them.
No card required. Your data stays in your Azure DevOps tenant.
- IMO SOLAS
- MARPOL
- ISM Code
- IACS unified rules
- STCW
- MLC 2006
A change is only done when it is traced to the vessel that carries it.
Maritime engineering and operations combine vessel configuration, classification rules, statutory requirements, safety-management procedures, equipment software, maintenance, incidents, certificates, and crew and operational controls. Every change has to be traced to the vessels it applies to, the class notation, the rule, the test, the document and the approval. When that trace lives in inboxes and spreadsheets, a fleet-wide change becomes a fleet-wide search.
- 01
Fleet applicability is a guess.
An equipment software update applies to some vessels and not others. Without a maintained baseline, nobody is sure which are as-fitted with which version.
- 02
Surveys arrive before the evidence does.
Documents, test records, open findings and certificate prerequisites are gathered in the week before a survey, and the gaps show up on board.
- 03
SMS procedures lag behind approved changes.
A change is approved, but the safety-management procedure, emergency response and training records are updated weeks later, if at all.
- 04
Defects and certificates are disconnected.
An equipment defect carries an operational restriction or a certificate impact, but the link lives in someone's memory, not in the record.
Your fleet's controls, set up as configuration.
Four layers tell the agents how your organization classifies vessels and equipment, links the record, maps it to rules and gates it. You configure the applicable society, rule set, notation and version.
- 01 Classification
Every item knows its vessel and its risk.
Vessel, equipment and system, class and flag context, safety and environmental criticality, statutory certificate impact, operational and cyber risk, configuration applicability, and fleet scope.
- 02 Traceability model
From rule to operating evidence.
Operational, class or statutory requirement to system and equipment requirement, design, configuration or software, inspection and test, class or flag approval, certificate or SMS procedure, then operation and maintenance evidence.
- 03 Standards & frameworks
Mapped to the rules your fleet answers to.
IMO SOLAS, MARPOL, the ISM Code, IACS unified rules, classification-society requirements such as DNV, Lloyd's Register, Bureau Veritas or ABS as applicable, and STCW and MLC 2006 context. Mappings are reviewed by your subject-matter experts.
- 04 Lifecycle gates & evidence
Gates from design review to closeout.
Design and class review, equipment and software release, installation, commissioning, survey and inspection, certificate issue and renewal, SMS change, maintenance, and incident closeout.
The Maritime chain, kept intact.
An equipment software change breaks the link between a requirement and the approved configuration. The agent flags it, opens the actions, and verifies the link is restored.
- Class / statutory
- Equipment req
- Configuration
- Inspection/test
- Class approval
- SMS / certificate
- Operation
Six maritime workflows to hand over first.
Each one runs the same controlled sequence: trigger, context, decide, act, approve, verify, record. Output lands on the work item, test or wiki page your technical team already uses.
Rule and requirement mapping
Link vessel and equipment requirements to the applicable class, statutory, safety, environmental and operational evidence, and flag requirements with no evidence behind them.
Requirements Engineer Agent
Configuration and change control
Maintain vessel and fleet applicability, approved baselines, modifications, software versions, tests, approvals and as-fitted status.
DevOps Engineer Agent
Survey and inspection readiness
Check that required documents, tests, findings, certificates, approvals and configuration evidence are in place before a survey or inspection.
Release Manager Agent
Safety-management procedures
After an approved change, draft updates to SMS procedures, responsibilities, emergency response, training and evidence for review.
Compliance Officer Agent
Maintenance and defect follow-up
Connect equipment defects to maintenance actions, spares, tests, certificates and operational restrictions, and chase what stays open.
QA Engineer Agent
Certificate and evidence status
Track statutory and class certificate status, expiry, prerequisites, findings and source documents, and report what is due next.
Product Owner Agent
A shipping advisor, working with the role catalog.
The supplied catalog includes a Maritime Shipping Advisor configured for this pack. It works alongside the role agents in the catalog, with explicit handoffs and approval boundaries between them.
Requirements Engineer Agent
Maps vessel and equipment requirements to class and statutory rules, and flags suspect links when one changes.
ShipDevOps Engineer Agent
Keeps software versions, baselines and as-fitted status per vessel in step with approved changes.
GovernCompliance Officer Agent
Drafts SMS procedure updates after an approved change, linked to the change and its evidence.
ReleaseRelease Manager Agent
Builds the survey readiness pack: documents, tests, open findings and certificate prerequisites.
Maritime roles in the catalog
- Maritime Shipping Advisor
Equipment software changes. Here is what follows.
A new version of ballast control software is approved for release, and the advisor's trigger condition matches. It identifies which vessels the change applies to, the class and statutory requirements involved, the configuration baseline, cybersecurity and safety impact, the installation and test procedure, survey or approval needs, manuals, training, and certificate and SMS evidence. It creates the required actions for named owners, pauses for approval, then verifies each action closed with evidence and writes the run record to Job Explorer.
run started · CHG-412 ballast sw 3.2
applicability: 6 vessels · 2 as-fitted 3.0
class rule · SMS procedure · 2 certificates
install, test and training actions drafted
checkpoint · awaiting technical manager
record · run history in Job Explorer
- ✓ Vessel applicability set
- ✓ Class and statutory mapped
- ✓ Install and test procedure
- ! Survey or approval need
- ! SMS and training updated
The agent prepares the record. Your authorities decide.
Design, technical management, class, flag, safety, environmental, maintenance, vessel and operational authorities stay responsible for rule interpretation, survey, certification and safe operation. The agent prepares mappings, checks evidence and opens actions. With Required Approval on, any step with side effects pauses and opens a task for a named approver, who can answer, attach files, and approve, edit or reject it. Every decision is kept in the run record.
[ Trusted by Microsoft and industry leaders ]
Maritime and shipping questions.
No. It prepares rule mappings and evidence. The class society and authorized authorities perform review and certification.
Yes. It can maintain status, prerequisites, findings, evidence and expiry data, provided those records are represented and controlled in Azure DevOps.
We make no blanket claim. You configure the applicable society, rule set, vessel class notation and version, and your subject-matter experts review the mapping.
Yes. Schedule an agent once, daily, on weekdays, weekly, monthly or yearly, and it reports what is due. It can still be run on demand at any time.
Yes. With Bring Your Own Data, agents retrieve from your uploaded documents, Azure DevOps queries and wiki pages during the run, so drafts use your own procedures and terminology.
No. Agents run inside your Azure DevOps environment with no separate portal or login, and your project data is not used to train models.
Nothing extra. Every plan includes the full catalog and all 15 industry packs. Credits cost $0.01 each, pooled across your organization with no per-user fees. A rule-based Execution Agent run is a flat 4 credits.
Bring one fleet change to the demo.
Start a free trial with 2,000 credits, no card required. Or book a 30-minute demo with a real requirement, change, defect, certificate or survey gap, and watch the trace, approval point and run record live.
