The vendor lifecycle in one place: Requirement Definition (BOQ/BOM) β RFI β RFP β RFQ β Contract Signing β Closure & Renewal β the same pipeline pattern used by SAP Ariba, Coupa, and Zycus, built offline and zero-server like every other GVS tool.
LiveOffline Β· your Anthropic key only
What this build covers: vendor master data, the full 6-stage sourcing pipeline with RFP scoring and RFQ quote comparison, contracts, a KPI dashboard, and closure reports β all with Add/Modify/Delete and CSV/XLSX/JSON import-export, the same benchmark standard as. It does not include live ERP or IoT integration β those need a real backend and OAuth applications, same reason IAS Office is architecture-only. See the Parameters panel for the fields that stand in for those live feeds today.
// Vendor Master
The vendor directory every Sourcing record and Contract draws from. Add, edit, and retire vendors at any time β deleting a vendor doesn't touch Sourcing/Contract records that already reference it.
0
Open sourcing events
0
In RFP/RFQ
0
Contracts awarded
β
Avg cycle time (days)
// Sourcing Pipeline
One record per procurement need, moving through Requirement Definition β RFI β RFP β RFQ β Contract Signing β Closure & Renewal. Each stage is a checkpoint, not a rubber stamp β vendor responses, RFP scores, and RFQ quotes live inside the record.
// Contracts
Signed and active vendor contracts β created automatically when a Sourcing event reaches Contract Signing, or added directly. Renewal dates feed the closure/renewal step and the KPI dashboard.
// KPI Dashboard β monitoring & controlling
Five standard vendor-management KPIs, computed on-device from Sourcing and Contract data β glass-box, no model judgement in the number. Targets are yours to set.
// Spend by Vendor Category
Where contract value actually concentrates β informational, not target-banded.
Anthropic API key
Stored only in this browser's local storage, on this device. Never sent to GVS or any server other than Anthropic's API, which you call directly. Get a key at console.anthropic.com.
Closure reports
One report per sourcing event that reaches Closure & Renewal β awarded, cancelled, or lapsed. View, add, edit, or delete any report at any time.
Stored locally on this device only. Use Export JSON or Backup data (top right) to keep a copy or carry data between browsers.
Parameters
Option lists, KPI targets, and operational defaults. Built-in values marked core are protected because KPI math and the sourcing pipeline key off them by name β add as many extra values as you like around them.
KPI targets
Operational defaults
Live-integration stand-ins
Real ERP sync and IoT device monitoring aren't built β see the architecture note for why. Until then, these are manual fields: Requirement records carry a "PO/ERP reference" text field, and Contracts carry a manual "SLA/device status" note instead of a live feed.
