One report, three apps.
Reports draw on files you keep, figures people hand in each period, and answers from people without an account. ovidens has an app for each, and an analytic app brings them into one published version.
An example
An emissions report, from three sources.
The names and figures are samples. Every part is one the product has.
An employee commuting survey, an emission factors file and an indicator app with each country's energy use each feed one analytic app. Its pipeline works out commuting emissions and energy emissions and puts them in one table. It is published as one version, shown open in the Visualisation editor.
Survey app
Survey app
Employee commuting
Asked through one link. Nobody signs in.
A file you keep
A file you keep
emission-factors.csv
The factors you use, uploaded as they are.
Indicator app
Indicator app
Energy per country
Each country enters its own. Checked, then locked.
Analytic app
Emissions report
All three arrive as nodes on the pipeline. SQL turns them into the figures.
Published
Published as one version.
Every run is kept with the version it ran against. The Visualisation is part of the version.
Side by side
Which one you need depends on where the data comes from.
Start with the first row. Versions, publishing and the audit log work the same in all three.
| Analytic app | Indicator app | Survey app | |
|---|---|---|---|
| Where the data comes from | Files you upload (CSV, XLSX, XLS), the Automation API, and other apps | Figures entered per reporting unit and period | Answers to a form you publish |
| Who enters it | Your team | Workspace members, each assigned to a unit | Anyone with the link. No account needed |
| How often | Whenever the data changes: run the pipeline again | Reporting periods, daily to yearly | Until you close it, on a date or after a number of responses |
| What checks it | Validation rules, on every run | Validation on every value, and consistency checks that block sign-off | Each question's type: a number, a date, an email, a choice |
| What is kept | Each published version: pipeline, knowledge base, skills and Visualisation. Every run is filed under one. | Approve & lock freezes a period and publishes a version | Each published version of the form, and every response |
| Vera | Builds the pipeline from a description | Sets up indicators from a description | Not in survey apps |
| What you get | Charts, pivots and tables your team edits; ad-hoc SQL | Checked, approved figures per unit and period | One row per answer, and a summary |
| Feeds an analytic app | Its published result, into another analytic app | Its published figures, through a bridge | Its responses, as an import |
| Explore the Analytic app | Explore the Indicator app | Explore the Survey app |
- Where the data comes from
- Files you upload (CSV, XLSX, XLS), the Automation API, and other apps
- Who enters it
- Your team
- How often
- Whenever the data changes: run the pipeline again
- What checks it
- Validation rules, on every run
- What is kept
- Each published version: pipeline, knowledge base, skills and Visualisation. Every run is filed under one.
- Vera
- Builds the pipeline from a description
- What you get
- Charts, pivots and tables your team edits; ad-hoc SQL
- Feeds an analytic app
- Its published result, into another analytic app
- Where the data comes from
- Figures entered per reporting unit and period
- Who enters it
- Workspace members, each assigned to a unit
- How often
- Reporting periods, daily to yearly
- What checks it
- Validation on every value, and consistency checks that block sign-off
- What is kept
- Approve & lock freezes a period and publishes a version
- Vera
- Sets up indicators from a description
- What you get
- Checked, approved figures per unit and period
- Feeds an analytic app
- Its published figures, through a bridge
- Where the data comes from
- Answers to a form you publish
- Who enters it
- Anyone with the link. No account needed
- How often
- Until you close it, on a date or after a number of responses
- What checks it
- Each question's type: a number, a date, an email, a choice
- What is kept
- Each published version of the form, and every response
- Vera
- Not in survey apps
- What you get
- One row per answer, and a summary
- Feeds an analytic app
- Its responses, as an import
Start with the part you have.
Most reports start with a file in an analytic app. Add the other two when the report needs figures or answers from other people.