Data library
Operations data for AI.
Quick answer
Operations data records how work gets done day to day: work orders, approvals, scheduling, dispatch and process logs. It shows sequences of actions and decisions that AI agents must learn.
Process
Operations data for AI
What's included
- Work orders
- Approval histories
- Scheduling records
- Process event logs
Where it typically lives
How AI developers use it
- Workflow agents
- Process mining
- Scheduling optimization
Preparation and privacy
- Remove employee and customer identifiers
- Generalize locations
How SourceX approaches it
Preparation requirements are agreed with you before any work begins, and no data is delivered to SourceX until you have approved the scope and terms and signed the agreement.
Industries with this data
Datasets built from this data
Dataset specs AI labs can request through SourceX, sourced to spec from businesses like yours.
- Operations and the physical worldField service and maintenance work ordersA maintenance work order dataset is a record of real repair and upkeep jobs on equipment: the reported symptom, the technician's diagnosis, the parts used,…Structured recordsTextImages
- Software and ITIT service management and incident historiesAn ITSM ticket dataset is the record of how an IT organization handled its incidents, service requests, problems and changes, exported from its service…TextStructured records
- Workflows and human feedbackEnterprise workflow and task execution historiesAn enterprise workflow dataset is a set of task execution histories: connected records that follow one business task from the incoming request through the…Structured recordsText
- Workflows and human feedbackHuman feedback and QA-scored workA human feedback dataset is a set of real work products paired with the judgments people made about them: QA scorecards, approvals and rejections, reviewer…Structured recordsText
- AI lab? Browse Field service and maintenance work orders
- AI lab? Browse IT service management and incident histories
Typical fields
- Record ID (pseudonymous)
- Created and closed timestamps
- Category or type
- Request or input text
- Ordered steps or actions
- Outcome or resolution
- Role of each actor (not identity)
Sample record
- record_id
- rec_8f21c0[masked]
- created / closed
- 2023-04-11 → 2023-04-12[masked]
- category
- Billing question[masked]
- request
- Customer [NAME] asks why invoice [ID] was charged twice.[masked]
- steps
- 1. Checked payment log 2. Found duplicate 3. Issued refund[masked]
- outcome
- Resolved · refund issued[masked]
- actors
- customer, agent_tier1[masked]
What Acquisition Partners look for
- Complete start-to-finish records
- Consistent fields over years
- Clear, labeled outcomes
- Low duplication
- Work done by skilled professionals
- Edge cases and failures, not only successes
Personal details removed
- Names
- Email addresses
- Phone numbers
- Postal addresses
- Account, customer and order numbers
- Government IDs
- Payment details
- Health information
- IP addresses and device IDs
- Credentials, keys and hostnames
How Acquisition Partners test it
- Sample review by Acquisition Partner researchers
- Residual personal-data scan
- Duplicate and leakage check against public data
- Label and outcome accuracy spot-check
- Rights and consent documentation review
Rules that may apply
Federal Wiretap Act 18 U.S.C. 2511
Applies to recorded calls and intercepted communications; some states require all-party consent. Assessed deal by deal.
California Consumer Privacy Act Cal. Civ. Code 1798.100 et seq.
May apply where records include personal information of California residents and the business meets the law's thresholds. Assessed deal by deal.
Reviewer note: applicability is confirmed with counsel for each deal. Not legal advice.
All data types · Call recordings · Project management data · Quality assurance data
See if your company qualifies
A short company assessment. No data uploads are needed.