Supplier & Vendor Data

Vendor drawings, tag lists, and ITR packs land in one completions model — linked to equipment, chased as work, exported cleanly.

Back to solutions

Supplier packs rarely fail because the file does not exist. They fail because the file is in email, a shared drive, or a DMS the person raising the ITR never opens. Doc-u-menT treats an incoming vendor pack as completions data: a register you import, drawings you pin to tags, and outstanding items you assign.

This is not a supplier portal and not a replacement document-management system. Vendors keep sending the pack they already send — CSV, Excel, or PDF. Your team loads it. The activity engine turns “still waiting on the vendor” into work with an owner, a due date, and a close.

Vendors do not need a Doc-u-menT login. Your team loads the pack. Transmittal wording is configured with labels and procedure steps — there is no separate supplier portal.

Load the pack you already received

Most vendor data arrives as a spreadsheet and a drawing set. Map the columns once — tag, description, hierarchy, ITR — and review new versus existing rows before anything is created. In the same Prep session you can scrape the PDFs so the register and the sheets meet before Confirm.

Prep Configure mapping a tags spreadsheet: Name to Tag Name, Detail to Description, plus hierarchy and discipline columns — Vendor CSV or Excel — header row mapped, then reviewed against the live register.

Vendor CSV or Excel — header row mapped, then reviewed against the live register.

Pin the revision to the equipment

A vendor P&ID that only lives in the DMS will not be opened on the ITR. Reference the issued revision on the tag and it is there when the assignee needs it. If the sheet was scraped, overlays sit on that same revision.

Tag Documents tab listing a pinned engineering drawing revision on the equipment record — The right vendor revision on the right tag — not a folder someone else owns.

The right vendor revision on the right tag — not a folder someone else owns.

Chase what is still missing as work

Outstanding vendor documents fail when they are a reminder in a register nobody owns. A Document Tracking activity has an assignee, a due date, and a close. Generate Activities can raise one item per matching file when the next pack lands.

Document Tracking Work Space list showing a completed activity against a document target — Still waiting on the vendor — as an activity, not an unread email.

Still waiting on the vendor — as an activity, not an unread email.

What it does

✓Import vendor tag lists, hierarchies, and ITR or procedure sheets from CSV or Excel
✓Scrape vendor drawing PDFs for tags, document numbers, and revisions in the same Prep session
✓Hold incoming files on the project document register with revision history
✓Pin a specific vendor revision to the tag, system, or subsystem it belongs to
✓Open the linked drawing from the equipment record instead of hunting the pack
✓Raise Document Tracking activities against files that have not come back yet
✓Bulk-generate tracking work when a new vendor pack lands
✓Assign chases into My Work with evidence on close
✓Label packs by supplier, discipline, or package for dashboard breakdowns
✓Export the cleaned register and tracking status through Data Hub

Highlights

• Same import and scrape path as the rest of Prep — no vendor-only tool
• Revision-pinning so an ITR points at the sheet the vendor actually issued
• Outstanding documents are activities, not highlighted rows in a mailbox
• Complements the project DMS; it does not replace transmittals or vendor logins

Demo

Demo video coming soon

See the rest of the platform, or talk to us about a demo.

All solutions Request a demo