The only agentic integration layer for Decision Intelligence

Triage captures decision intent, VMSagent creates a portable record, and publishes it into multiple systems of record.

Triage
Decision Intelligence
Direct API
Programmatic Access
VMSagent
Record Publish Correlate
Permanent hiringWdSFOrUKHRIS
Contingent labourFGBeVMS
Outsourced / Work ordersArOrCoPO / S2P
Short-term services / SoWFGBeIcGlVMS + CLM + Sourcing
AI agents?On roadmap

Triage decides. VMSagent publishes. The VMS executes.

01

Triage

Decision Intelligence

Diagnoses the request, classifies work, identifies constraints, and recommends the best fulfilment path — based on the enterprise's own supply chains and systems.

02

VMSagent

Publishing Layer

Creates a portable record of the decision and publishes it into the right system(s) in a program-compliant way. The decision becomes a durable asset that survives system changes.

03

Systems of Record

Execution Layer

Manages the transactional objects: requisitions, work orders, timesheets, invoices, compliance checks, approvals, and supplier interactions.

The Channel Map turns policy into action

Each intent record carries the full context of the decision. The Channel Map routes it to the right destination based on region, category, and business rules.

Channel Map — Intent Record
intent_id
intent_3kF9xQm2
work_type
Contingent Labour
region
EU · United Kingdom
channel
SAP Fieldglass (EU tenant)
route_type
Single-step publish
status
✓ Routed

What happens when Triage completes a decision.

Magically link the decision intent from triage into a requisition, like this example in Fieldglass.

VMSagent — Intent Record
intent_3kF9xQm2 Draft
work_typerole
channelcontingent
confidence0.92
titleData Engineer
locationLondon, GB · hybrid
start_date2026-04-01
duration6 months
cost_center_idCC-4401
risk_posturemedium
defence_filedf_8nWqL2v1.json
intent_3kF9xQm2 Planned
Channel Map resolved this intent to a single-step publish:
target_systemSAP Fieldglass (EU)
object_typeJob Posting / Requisition
mapping_profilefg_eu_contingent_v3
required_fieldstitle, start_date, cost_center_id, location, duration ✓
preconditionsBudget approval ✓ · HR classification ✓
idempotency_keyintent_3kF9xQm2-v1-fieldglass_eu
update_policyrates, dates mutable · title immutable
intent_3kF9xQm2 Publishing
FG
SAP Fieldglass adapter
14:32:01 Authenticating via OAuth 2.0 (client credentials)…
14:32:01 Token acquired. Tenant: fg-eu-prod
14:32:02 Mapping canonical → Fieldglass dialect…
14:32:02   start_date → WorkStartDate
14:32:02   cost_center_id → CostObjectID
14:32:02   title → JobPostingTitle
14:32:02 Payload validated. 12 fields mapped.
14:32:03 POST /api/v1/job_postings
14:32:03   Idempotency-Key: intent_3kF9xQm2-v1-fieldglass_eu
14:32:04 201 Created → REQ-40281
14:32:04 Defence File URL written to CustomField_12
14:32:04 Publish log entry recorded.
intent_3kF9xQm2 Published
Both systems now reference each other. Pull the thread from either side.
VMSagent
intent_3kF9xQm2
external_id: REQ-40281
target: SAP Fieldglass (EU)
defence_file: df_8nWqL2v1
SAP Fieldglass
REQ-40281
CustomField_11: intent_3kF9xQm2
CustomField_12: defence file URL
Status: Open
intent_3kF9xQm2 ✓ Synced
14:30:12
Intent created
Triage completed. Defence file attached.
14:31:05
Plan generated
Channel Map → Fieldglass EU, requisition.
14:32:04
Published
REQ-40281 created. Idempotency key logged.
14:32:05
Correlated
Intent ID → REQ-40281 linked. Defence file URL stored.
15:12:33
Approved
Webhook from Fieldglass. Hiring manager approved.
15:12:34
Timeline synced
All events traceable by intent_3kF9xQm2.

One Intent ID ties everything together.

One Intent ID ties together the decision, the evidence, the execution, and the audit trail across every system it touches.

VMSagent — Intent Lineage
intent_3kF9xQm2 Origin
Triage
Decision made
Contingent, Data Engineer, London, 6 months
Evidence
Defence File
df_8nWqL2v1.json
intent_3kF9xQm2
Execution
VMS objects
Requisitions, work orders, assignments
Audit
Events & approvals
Every transition traced
Financials
Costs & invoicing
Linked to original decision
Pull the thread on any object in any system, and you trace back to the original decision. No more orphaned transactions. Every VMS object carries its lineage.
intent_3kF9xQm2 Execution
Three objects across two systems — all carrying the same Intent ID.
FG
SAP Fieldglass · Requisition
Data Engineer — London
REQ-40281
FG
SAP Fieldglass · Work Order
J. Martinez — Data Engineer
WO-90114
ERP
SAP S/4HANA · Purchase Order
Staffing Services — CC-4401
PO-772891
Every object carries its lineage. Search intent_3kF9xQm2 in any system and see the full chain: decision → requisition → work order → purchase order.
intent_3kF9xQm2 Events
Complete governance trail — who did what, when, and under what authority.
14:30:12
Intent created
Triage completed classification. Defence file attached.
⚙ Triage · automated
14:45:33
Budget approved
Cost center CC-4401 confirmed within Q3 envelope.
👤 Sarah Chen · Finance BP
15:12:07
Hiring manager approved
REQ-40281 approved in SAP Fieldglass. Webhook received.
👤 Tom Richards · Engineering Dir
Apr 3
Worker assigned
J. Martinez accepted. Work order WO-90114 created.
⚙ Fieldglass · webhook
Apr 3
Rate drift detected
Recruiter edited bill rate in Fieldglass: £650 → £680/day. Reconciliation flagged.
⚠ VMSagent · reconciliation
Apr 4
Drift accepted
Procurement approved rate change. Intent Record updated to v2.
👤 Lisa Park · Procurement Lead
intent_3kF9xQm2 Cross-reference
The same decision exists in three systems. Every ID is cross-referenced.
VMSagent
intent_3kF9xQm2
Canonical record · v2
SAP Fieldglass
REQ-40281 / WO-90114
CustomField_11: intent_3kF9xQm2
VMSagent
intent_3kF9xQm2
Canonical record · v2
SAP S/4HANA
PO-772891
Reference field: intent_3kF9xQm2
Correlation register
Intent IDintent_3kF9xQm2
Fieldglass REQREQ-40281
Fieldglass WOWO-90114
S/4HANA POPO-772891
Defence filedf_8nWqL2v1
intent_3kF9xQm2 Financials
From decision to invoice — cost is traceable to the original intent.
Total spend to date
£78,880
16 weeks · £680/day · 4.6 days avg/wk
Budget remaining
£9,520
Original estimate: £88,400
Invoices raised
4
3 paid · 1 pending approval
Rate variance
+4.6%
£650 planned → £680 actual
Period
Amount
Source
Apr 1–30
£14,960
INV-8812
May 1–31
£15,640
INV-9103
Jun 1–30
£14,280
INV-9441
Jul 1–present
£34,000
Pending
Total
£78,880
Every pound traces back to intent_3kF9xQm2. The original decision, the evidence, the rate change, and every invoice — one thread.
Pull the thread on any object in any system, and you trace back to the original decision. No more orphaned transactions. Every VMS object carries its lineage.

Same intent, different destinations.

Enterprises have multiple processes by region, BU, category, and channel. The Channel Map defines how intent becomes action — without hardcoding.

Channel Map — EU program
intent_3kF9xQm2 Config A
Channel Map resolves this intent to a single-step publish to the EU Fieldglass tenant.
work_typerole
channelcontingent
regionEU — United Kingdom
mapping_profilefg_eu_contingent_v3
target_systemSAP Fieldglass (EU)
object_typeJob Posting / Requisition
publish_steps1
Intent Record
intent_3kF9xQm2
Channel Map
fg_eu_contingent_v3
Destination
SAP Fieldglass (EU)
intent_3kF9xQm2 Config B
Same intent format. Different MappingProfile routes to the US VMS tenant instead.
work_typerole
channelcontingent
regionUS — New York
mapping_profilebl_us_contingent_v2
target_systemBeeline (US)
object_typeWork Request
publish_steps1
Intent Record
intent_3kF9xQm2
Channel Map
bl_us_contingent_v2
Destination
Beeline (US)
The intent record is identical. Only the MappingProfile changed — fg_eu_contingent_v3bl_us_contingent_v2. Field names transform automatically.
intent_3kF9xQm2 Config C
Services intent triggers a multi-step chain — the Channel Map sequences four destinations.
work_typeservice
channelstatement_of_work
mapping_profilesow_multi_v1
publish_steps4
sequencingserial — each step gates the next
Intent Record
intent_3kF9xQm2
1
Sourcing
Globality
2
CLM
Icertis
3
S2P
Coupa
4
VMS tracking
Fieldglass
Four destinations, one intent. The Channel Map sequences them — sourcing first, then contract, then purchase order, then VMS tracking. Each step gates the next. The intent_3kF9xQm2 thread runs through all four.

Every transaction carries its justification.

The Defence File is an evidence bundle that travels with the decision. When an auditor asks "why did we engage this supplier through this channel?" — the answer is attached to the object.

01 — Triage

Defence File created

Triage builds the evidence: classification rationale, confidence score, constraints, recommended channel, alternatives considered, required approvals, supporting documents.

02 — VMSagent

Linked and published

Defence File URL written into the VMS object's custom field or notes on publish. Where supported, the PDF is attached directly to the VMS object.

Always

Canonical copy preserved

VMSagent keeps the canonical Defence File in its own store. Portability remains even if the organisation changes VMS vendor or tenant configuration.

What the Defence File contains

Request summary & justifications
Classification rationale & confidence
Constraints & assumptions
Recommended channel + alternates
Required approvals & compliance
Links to supporting documents

VMSagent handles 29 question and data types.

Triage captures decision intent through structured, scorable, and integration-ready question types — from simple choices to AI-prompted inputs and real-time scenario simulators.

Showing 29 of 29 question types
Launch Screen
Informational · Metadata
Entry point for context and user instructions.
Not scorable Integration
Integration examplePulling user data from Workday to personalise the greeting.
Statement
Informational · Metadata
Non-interactive block for providing specific context.
Not scorable Integration
Integration exampleDisplaying a live Budget Balance retrieved from a VMS.
End Screen
Informational · Metadata
Confirmation block and trigger for downstream events.
Not scorable Integration
Integration exampleTriggering an automated Slack or Teams notification.
Outcome Screen
Informational · Logic Object
Conditional final screen displaying path-based results.
Not scorable Integration
Integration exampleShowing a “Risk Rating” based on a Calculated Score.
Multiple Choice
Choices · Enum
Selection of one or more options from a fixed list.
Scorable Integration
Integration examplePulling active Cost Centres from SAP S/4HANA.
Dropdown
Choices · List
Scrollable menu used to save space for long lists.
Scorable Integration
Integration examplePopulating Job Titles from a global VMS library.
Yes/No
Choices · Boolean
Binary choice for simple qualification or logic.
Scorable No integration
NoteStatic logic gate used for qualifying branching paths.
Ranking
Choices · Array
Arranging items into a preferred sequence.
Partial score No integration
ExampleOrdering internal priorities (e.g., Speed vs. Quality).
Drill Down
Choices · Hierarchical
Menu where the first choice filters subsequent levels.
Scorable Integration
Integration exampleSelecting Vendor › Service Category › Job Role.
Scenario Simulator
Choices · JSON / Map
Toggling variables to see projected real-time outcomes.
Scorable Integration
Integration exampleTesting budget impact against IBM Decision Manager.
T
Short Text
Text · String
Single-line box for brief answers or labels.
Not scorable Integration
Integration exampleValidating a Tax ID against a corporate database.
Long Text
Text · Text
Large text area for qualitative project descriptions.
Not scorable Integration
Integration exampleSending feedback to a Sentiment Analysis engine.
AI-Prompted Box
Text · Object / JSON
AI-enabled open field for natural language prompts.
Not scorable Integration
Integration exampleDirect LLM connection to generate SOW text.
@
Email
Contact · Email
Verified field for email addresses with format validation.
Not scorable Integration
Integration exampleZeroBounce to verify address deliverability.
Phone Number
Contact · Tel
Formatted field for international or local digits.
Not scorable Integration
Integration exampleTwilio Lookup to verify carrier and line type data.
🔗
Website
Contact · URL
Field validated for standard URL structures.
Not scorable Integration
Integration exampleSimilarWeb to categorise a vendor’s business sector.
Address
Contact · Geo
Integrated field for verified geographical locations.
Not scorable Integration
Integration exampleGoogle Maps API for address autocompletion.
#
Number
Numbers · Float
Restricts input to ensure only numerical data.
Scorable No integration
ExampleValidating simple headcount or quantity requirements.
📊
Likert Scale
Numbers · Scale
Psychometric scale used to assess levels of agreement.
Scorable No integration
ExampleMeasuring manager satisfaction on a scale of 1–5.
Opinion Scale
Numbers · Scale
Numbered scale used for general sentiment.
Scorable No integration
ExampleCapturing a 0–10 score for an NPS calculation.
£
Benchmark Rate
Numbers · Currency
Market data: compares rates vs. external averages.
Scorable Integration
Integration examplePulling live Market Pay Data from Lightcast.
%
Prediction Rating
Numbers · Probability
User-rated accuracy of a suggested AI prediction.
Scorable Integration
Integration exampleAssessing Confidence in an AI completion forecast.
Attestation
Operations · Boolean
Checkbox for verifying truth or compliance terms.
Scorable No integration
NoteLegal verification recorded as a local timestamp.
📎
File Upload
Operations · Binary / File
Allows users to attach documents, PDFs, or images.
Not scorable Integration
Integration examplePushing an uploaded resume to a Beeline Profile.
📅
Date
Operations · ISO Date
Interface for selecting specific days and years.
Partial score Integration
Integration exampleSyncing an interview with an Outlook Calendar.
De-duplication
Operations · Lookup / ID
Reference class: checks to prevent redundant work.
Scorable Integration
Integration exampleQuerying a CMS for an existing, similar SOW.
Policy Check
Operations · Boolean / ID
Background check against enterprise governance rules.
Scorable Integration
Integration exampleVerifying vendor ISO 27001 compliance in a Master File.
🛡
Captcha
Security · Boolean
Challenge to ensure the respondent is a human.
Not scorable Integration
Integration exampleGoogle reCAPTCHA to block automated entries.
Timing (Hidden)
Security · Time
Records time spent on a page or individual question.
Scorable No integration
ExampleFlagging “speeders” who bypass engagement logic.

Platform coverage.

We show exactly what's connected and what requires official documentation or sandbox access.

PlatformCategoryAPI DocsStatus
SAP FieldglassVMSREST API + OData. 227+ resources.✓ Docs available
BeelineVMS300+ RESTful APIs. Auth0 / OAuth 2.0.✓ Docs available
MagnitVMSREST API. PDF reference available.✓ Docs available

Coming soon — Contract Management (Icertis, Ironclad), Source to Pay (Coupa, SAP Ariba), Document Signature (DocuSign), Procurement Orchestration (Zip), Autonomous Sourcing (Globality, Keelvar), HRIS (Workday, SuccessFactors).

Turn decisions into portable assets.