Business Objects
Built around a semantic metadata model, trac can accommodate any type of model or analytic workflow. Platform users primarily create and interact with four object types:
Data object: Refers to and describes a collection of data records held in trac's primary storage, which can be uses for running calculations
Model object: Refers to and describes a discrete unit of code in a repository that trac can acccess and use in calculations
Flow object: The blueprint for a complex calculation composed of multiple models arranged into a single execution graph
Job object: An instruction for a calculation which trac orchestrates via the exectuion service — such as running a specific Model or Flow
System Resources
Integrating with existing tools and technologies, trac creates a unified environment in which to curate models and data, orchestrate processes and run calculations. A typical deployment will make use of five resource types:
Internal storage: Storage location(s) which hold the platform’s primary data. These must be locations to which trac alone has write access
External storage: Storage location(s) which trac does not control, but can access for importing and exporting data
Model repository: One or more locations within a version control system (e.g. Git) where models are stored
Execution service: The compute capabilities of your underlying infrastructure, which trac uses to execute calculations.
Runtime environment: The set of internal and external libraries and dependencies that are made available to models at runtime
Jobs and Actions
Unopinionated by design, trac can support any process or workflow via the following actions:
1. Import model: Bring in a new model or model version from a repository
2. Upload/import data: Bring in data via the UI or a batch process
3. Build flow: Combine multiple models into a single execution graph
4. Run job: Execute a model or flow with a set of data inputs
5. Download/export data: Extract data via the UI or a batch process
