Data exchange and API
What goes in, what comes out, where it is kept, and how other systems connect: files, autosave folders, cloud workspaces and the REST API.
XER with the enterprise scheduler
DeltaSys reads and writes the XER format used by the industry's leading enterprise scheduling software.
| Imported | Exported |
|---|---|
| Projects (several in one file, with cross-project relationships), calendars with exceptions, WBS, activities with types, durations, dates, status and constraints, relationships with lags, resources and assignments, expenses, activity code types and values, activity steps, OBS and project codes | The project's calendars, WBS, activities, relationships, resources and assignments, expenses, codes and steps, in a file the scheduler opens as a project |
The critical path results match the scheduler's on the same inputs: early, late and float dates across the reference projects. Scheduling options (retained logic or progress override, lag calendars, float type, critical threshold) are in the Project panel.
Planner and Estimator files
A project is a .planner.json: the model, the baselines, the resources, the updates, the risk and register, the codes, the changes and the log, all in one file. An estimate is an .estimate.json. Both are plain JSON and open in any text editor; keep them with the project records like any other document.
Autosave folder
Choose a folder (Projects view) and every project is written there as you work, with a backup a day. A OneDrive or SharePoint-synced folder is backed up by that service too. Reconnect the folder in another session and the projects come back. Folder access uses the browser's file system API, available in Chrome and Edge.
Cloud workspace
With an account, projects and the enterprise setup are kept on the DeltaSys server and shared with the workspace's members. Saves sync automatically; the app keeps working offline and syncs when back online. Every write carries a version: if someone else saved a newer version, yours is kept beside it as a conflict copy rather than overwriting theirs.
Excel and CSV
- In: timesheets and contractor costs (CSV or pasted), estimate sheets with column mapping, bills of material, benchmark data, reference catalogues, risk logs.
- Out: every table in the Planner to CSV (activities as laid out, forecast, cash flow, manpower, earned value by WBS, change requests, change log, risk results, the portfolio tables); the Estimator to an Excel workbook with summary, detail, WBS, rates, materials, cash flow and risks.
REST API
A cloud workspace is also reachable through the API that the apps use. Authentication is the session cookie set at sign-in; an API token for service accounts is on the roadmap for enterprise deployments.
| Method and path | What it does |
|---|---|
POST /api/auth/signup, /api/auth/login, /api/auth/logout, GET /api/auth/me | Accounts and the session |
GET /api/orgs/:org/projects | The workspace's projects with their summaries |
GET /api/orgs/:org/projects/:key | One project's document (the .planner.json content) and version |
PUT /api/orgs/:org/projects/:key | Save a project; send the version you read, and a stale save is refused with 409 and the newer version |
DELETE /api/orgs/:org/projects/:key | Remove a project from the workspace |
GET, PUT /api/orgs/:org/enterprise | The enterprise setup, versioned the same way |
POST /api/orgs/:org/invites, DELETE /api/orgs/:org/members/:email | Members (owners only) |
GET /api/health | Service status |
Bodies are JSON. A project document is the same JSON the Planner saves, so a connector can read the schedule, post actuals into a copy and save it back with the version it read.
ERP, finance and field systems
Cost codes, budgets, actuals, commitments and timesheets come in through the files every such system exports (CSV, Excel) with saved column mappings, or through the API for a scheduled connector. Forecasts, cash flow and earned value go back out as CSV, Excel or through the API. For enterprise deployments we build and run the connector to your finance system with reconciliation and an audit trail of every load.