Transportation & LogisticsRule changes checked before they reach a shipment.
The transportation pack sets agents up around shipment and dangerous-goods classification, modal rules, fleet and driver controls, customs and security status, system changes, tests, approvals and incidents. They keep that record linked inside your Azure DevOps project, show which modes, jurisdictions and documents a change touches, and open the verification work before release. Classification and shipment decisions stay with trained, authorized people.
No card required. Your data stays in your Azure DevOps tenant.
- DOT/FMCSA
- ADR/RID
- IATA Dangerous Goods Regulations
- IMDG Code
- ISO 28000
- C-TPAT/AEO
Every system change needs modal and jurisdictional context.
Logistics technology decides real things: how a shipment is classified, packaged and labelled, how it is routed, which carrier takes it, which drivers and vehicles are eligible, what gets filed with customs, what the dangerous-goods paperwork says, how the warehouse handles it, its security status and how incidents are reported. A small rule change in one system can be correct for one mode and wrong for another. Teams need to know exactly what a change touches before it goes live.
- 01
One rule, many modes.
A classification or routing rule changes for road, but the same code path serves rail, air and sea. Nobody lists every mode and jurisdiction it touches.
- 02
Documents and labels fall behind the logic.
The system now classifies a product differently, but the label template, shipping document and training material still reflect the old rule.
- 03
Eligibility checks live outside the release.
Fleet and driver qualification, inspection and hours conditions are checked by people after a release, not as part of it.
- 04
Incidents don't trace back to changes.
When a noncompliance happens, linking it to the shipment, the system change and the process that allowed it takes a manual investigation.
Your modal rules, set up as configuration.
Four layers tell the agents how your operation classifies shipments, links the record, maps it to rules and gates it. You configure the exact modes, jurisdictions, rule editions, routes, products and company procedures.
- 01 Classification
Every item knows its mode and its risk.
Mode, route and jurisdiction, UN number and dangerous-goods class, quantity and package, carrier, fleet and driver applicability, customs and security status, operational criticality, and change risk.
- 02 Traceability model
From requirement to audit evidence.
Shipment, customer or regulatory requirement to classification and control, system or process implementation, validation and test, approval, operational transaction or document, then incident and audit evidence.
- 03 Standards & frameworks
Mapped to the rules each mode runs under.
DOT/FMCSA where applicable, ADR/RID, the IATA Dangerous Goods Regulations, the IMDG Code, ISO 28000 supply-chain security, and C-TPAT/AEO and customs-security context. Mappings are reviewed by your subject-matter experts.
- 04 Lifecycle gates & evidence
Gates from rule review to closeout.
Classification and rule review, system and configuration change, carrier and fleet eligibility, document and label validation, security and customs approval, release, operational readiness, and incident closeout.
The Transportation chain, kept intact.
A routing rule change breaks the link between a classification control and its implementation. The agent flags it, opens retest, and verifies the link before release.
- Regulatory req
- Classification
- Implementation
- Validation
- Approval
- Shipment record
- Audit evidence
Six logistics 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 pipeline your team already uses.
Dangerous-goods requirement mapping
Link classification, packaging, documentation, labelling, routing, carrier and training requirements to their implementation and tests.
Requirements Engineer Agent
System change impact
Identify the modes, jurisdictions, customers, carriers, documents, labels, integrations, tests, procedures and approvals a change affects.
Business Analyst Agent
Fleet and driver control
Check the configured eligibility, inspection, qualification, hours and safety, maintenance and evidence conditions, and flag anything unmet.
Compliance Officer Agent
Customs and supply-chain security
Maintain control, status, partner, audit, exception and evidence workflows, and keep each exception linked to its owner and resolution.
Product Owner Agent
Incident and noncompliance follow-up
Classify the event, link it to the shipment, system and process changes, create actions, verify the correction and keep the evidence.
QA Engineer Agent
Release and operational readiness
Verify rules, configurations, test cases, integrations, documents, training, approvals, rollback and monitoring before a release goes live.
Release Manager Agent
A logistics advisor, working with the role catalog.
The supplied catalog includes a Transportation Logistics 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
Links dangerous-goods requirements to the code, labels and tests that implement them, and flags suspect links on change.
PlanBusiness Analyst Agent
Lists every mode, jurisdiction, carrier and document a rule change touches, on the change itself.
TestQA Engineer Agent
Generates and links retests for affected rules, and records per-step results on the test runs.
ReleaseRelease Manager Agent
Checks release readiness: rules, documents, training, approvals, rollback and monitoring, before go-live.
Transportation roles in the catalog
- Transportation Logistics Advisor
A routing rule changes. Here is what follows.
A pull request changes how lithium battery shipments are routed, and the advisor's trigger matches. It identifies the affected modes, jurisdictions, UN numbers and classes, packaging, labels, carriers, documents, integrations, tests, training, approvals and live operational records. It creates the change and verification actions for named owners and links them to the PR. Release waits at a checkpoint until the actions close with evidence, and the run record is written to Job Explorer.
run started · PR !412 routing rule change
scope: road, air · UN3480 · 3 carriers
2 label templates · 1 customs integration
retest and training actions drafted
checkpoint · awaiting DG specialist
record · run history in Job Explorer
- ✓ Modes and jurisdictions set
- ! Labels and documents updated
- ✓ Affected tests passed
- ! Training and procedures
- ✓ Rollback and monitoring
The agent checks the change. Authorized people decide.
Dangerous-goods, fleet, customs, security, operations, legal and compliance, technology and carrier authorities stay responsible for classification, shipment acceptance, filing, safe operation and regulatory conclusions. The agent maps, checks 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 ]
Transportation and logistics questions.
It can apply your configured rules and prepare a classification. Trained and authorized personnel review and approve the shipment decision.
No. You configure the exact modes, jurisdictions, rule editions, routes, products and company procedures, and your experts review the mapping.
Agents read and write Azure DevOps artifacts: work items, repos, pipelines, Test Plans and wiki. Any other system is reached only through verified integrations and permissions you approve.
Yes. Event-based triggers start a run on PR creation or update, on pipeline stages, or on work item changes, and conditions narrow it to the rules and areas you choose.
Yes. With Bring Your Own Data, agents retrieve from your uploaded documents, Azure DevOps queries and wiki pages during the run, so checks follow your company procedures.
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 rule change to the demo.
Start a free trial with 2,000 credits, no card required. Or book a 30-minute demo with a real classification rule, routing change, incident or release gate, and watch the trace, approval point and run record live.
