Skip to main content

DaaS Reference

Introduction

The BigChange Data as a Service (DaaS) leverages Snowflake's cutting-edge technology to securely put analytics-focused data in our customers' hands. The aim of this service is to enable our customers to generate impactful data-driven insights, thereby enhancing their capacity to make informed decisions based on data.

Something missing?

Our documentation is a priority to us and we strive to constantly improve it. Please reach out if you find an inaccuracy or have a suggestion on how we might make things better.


Setup procedure

Step 1 - Review our documentation

DaaS is a premium service that is not included in the standard JobWatch licensing agreement. Be sure to review the pricing information, data dictionary and FAQs to determine if the service is a good fit for your needs.

Step 2 - Create a Snowflake account

Snowflake is a market-leading cloud data warehouse provider that BigChange uses to provide DaaS. After you have signed up for a BigChange DaaS license, you will need to create a Snowflake account for your organisation, if you don't already have one.

After entering your name and company details, click continue and provide the following:

  • Choose Standard for your Snowflake Edition
  • Choose Amazon Web Services for your cloud provider
  • Choose EU (Ireland) for your region
Cross cloud fulfillment

If your organisation requires use of a different region or cloud provider, we are able to support Snowflake accounts outside of AWS / EU (Ireland) for an additional cost. Let us know your requriement when signing up to DaaS.

Step 3 - Sign up to our service

You can sign up to BigChange DaaS by contacting your customer success manager or alternatively, by sending an enquiry from right here in the Developer Portal. Be sure to include the required information, including the identifier of your Snowflake account.

Step 4 - Accept the data share

We use Snowflake's data marketplace to securely share data with your own Snowflake account. We'll publish a private data listing that you need to accept and import to be able to access the data we provide.

DaaS Image #1

  • We recommend leaving the database name and role as the form suggests. You can always change these later if you aren't sure. Click 'Get' to proceed.

DaaS Image #2

  • The share will be established and data will be made available immediately. Click the 'Query Data' button to examine it.

DaaS Image #3

  • The data marts will be presented in the database that you just created as a set of secure views. Expand the panel on the left hand side to locate and start interacting with them.

DaaS Image #4


Available data

Schema

The BigChange DaaS license grants access to our collection of purpose-built data marts, geared for analytics purposes and aligned to key business entities and functions.

Our versioned marts adopt a wide table structure to ensure high performance querying and developer ease-of-use. Data heavy lifting has been eliminated by building complex calculations directly into the marts and minimising the the need for table joins.

Each data mart is fully documented, containing an easy to understand naming convention and human readable data values. Data professionals do not need to be familiar with any other BigChange database or product when working with DaaS.

Freshness

DaaS is primarily geared to provide retrospective analytical insight, rather than to drive real-time data use cases. At present, the data marts we surface are refreshed every 3 hours from Monday to Saturday during UK working hours (8:00-17:00).

Read only

DaaS provides data that is read-only and does not provide the ability to write data back into our platform.

Data coverage

We are continually building out the quantity and quality of the marts we provide, and we encourage you to regularly review the change log for updates. If your use case needs additional data, feel free to make a request via the developer community.


Using your data

BI Applications

The Snowflake technology that our DaaS is built upon is widely supported by most business intelligence applications. Below you'll find documentation from popular suppliers on how to connect Snowflake to their product:

ApplicationSupplier HomepageDocumentation
Power BIhttps://powerbi.microsoft.com/Snowflake Connectivity
Tableauhttps://www.tableau.com/Snowflake Connectivity
Lookerhttps://lookerstudio.google.com/Snowflake Connectivity
QuickSighthttps://aws.amazon.com/pm/quicksight/Snowflake Connectivity
Metabasehttps://www.metabase.com/Snowflake Connectivity
Qlik Sensehttps://www.qlik.com/us/products/qlik-senseSnowflake Connectivity
ThoughtSpothttps://www.thoughtspot.comSnowflake Connectivity
Usage of BI applications

Please note that while we encourage the use of BI applications, we are unable to provide support for these third party tools.


Programmatic access

If your requirements cannot be fulfilled by off-the-shelf business intelligence tooling, it is possible to build your own applications to interact with the BigChange DaaS. We have compiled the list below to provide a steer on how to get started with Snowflake programmatic interfaces for most common languages:

LanguageInterface
C#Snowflake Connector for .NET
PHPPHP PDO driver for Snowflake
PythonSnowflake Connector for Python
GoGo Snowflake Driver
Node.jsNode.js Snowflake Driver
JavaJDBC driver for Snowflake
ODBCODBC driver for Snowflake
Writing your own code

Before building an application, please review our FAQs to understand the suitability of DaaS for your use case. Note that we are unable to provide support for any bespoke applications you build.


Data replication

Pulling data out

If your requirements mean that you have to merge data from DaaS with your existing data sources, you should consider establishing a synchronisation process.

Although you could create a custom application to transfer data from Snowflake into your intended database, we suggest leveraging an off-the-shelf SaaS solution for this task. FiveTran offers a cost-effective solution for this purpose, but there are several other platforms that offer similar services.

Pushing data in

Your Snowflake account is not BigChange specific and can be used to fulfill other data warehousing requirements for your organisation. In this regard, it might be more beneficial to explore the option of replicating additional data into your Snowflake account.

The same data transfer techniques outlined for moving data can also be employed with Snowflake as the destination rather than the source. Replicating data into Snowflake could be a preferable approach for blended insights, especially if your organisation lacks an established data warehousing capability.

Usage of data pipelines

Whilst your Snowflake account can serve as the source or target for data replication, such replication processes fall outside of the core service we offer. Please note that we are unable to provide support for the operation of third-party or bespoke applications for data replication.


Account management

You have complete control of how your organisation interacts with DaaS - BigChange applies no user or usage limits. You can manage your own Snowflake account to administrate user access, as well as scaling your warehouse to support your cost and performance targets. For more information how you can manage your account, please consult the Snowflake technical documentation.


Versioning

Latest data marts

Each of our data marts are versioned to provide a stable data contract for systems to be built upon. Details of our current versions are described below:

NameLatest versionPublished on
Contact custom fieldscontact_custom_fields_v12023-10-03
Contact notes custom fieldscontact_notes_custom_fields_v12023-10-03
Contact notescontact_notes_v12023-10-03
Contactscontacts_v12023-10-03
Contract custom fieldscontract_custom_fields_v12024-03-11
Contract financial linescontract_financial_lines_v12024-07-02
Contract notescontract_notes_v12024-03-21
Contractscontracts_v12024-03-04
Invoice custom fieldsinvoice_custom_fields_v12023-10-03
Invoice linesinvoice_lines_v12023-10-03
Invoicesinvoices_v12023-10-03
Job constraintsjob_constraints_v12024-11-13
Job custom fieldsjob_custom_fields_v12023-10-03
Job groupsjob_groups_v12023-10-03
Job linesjob_lines_v12023-10-03
Job notesjob_notes_v12024-04-18
Job worksheet answersjob_worksheet_answers_v12024-04-09
Jobsjobs_v12023-10-03
Person custom fieldsperson_custom_fields_v12024-07-24
Personspersons_v12024-07-11
Purchase order linespurchase_order_lines_v12024-09-18
Purchase orderspurchase_orders_v12024-09-18
Quote custom fieldsquote_custom_fields_v12023-10-03
Quote linesquote_lines_v12023-10-03
Quotesquotes_v12023-10-03
Resource absencesresource_absences_v12024-07-11
Resource activitiesresource_activities_v12023-10-03
Resource custom fieldsresource_custom_fields_v12023-10-03
Resource day summariesresource_day_summaries_v12023-10-03
Resource journeysresource_journeys_v12024-07-02
Resource notesresource_notes_v12024-03-12
Resource skillsresource_skills_v12024-11-18
Resource working hoursresource_working_hours_v12024-08-12
Resourcesresources_v12023-10-03
Sales opportunitiessales_opportunities_v12023-10-03
Sales opportunity custom fieldssales_opportunity_custom_fields_v12024-01-09
Sales opportunity notessales_opportunity_notes_v12024-10-30
Stock item custom fieldsstock_item_custom_fields_v12024-03-21
Stock item notesstock_item_notes_v12024-04-18
Stock items to contractsstock_items_to_contracts_v12024-10-17
Stock itemsstock_items_v12024-03-11
Stock movementsstock_movements_v12024-04-08
Stock planned usagestock_planned_usage_v12024-04-08
Stock reorder levelsstock_reorder_levels_v12024-04-23
Stock suppliersstock_suppliers_v12024-03-21
Stock worksheet answersstock_worksheet_answers_v12024-05-06
Stockstock_v12024-04-23
Timesheet worksheet answerstimesheet_worksheet_answers_v12024-06-17
Vehicle attributesvehicle_attributes_v12024-03-27
Vehicle checks and defectsvehicle_checks_and_defects_v12024-04-23
Vehicle custom fieldsvehicle_custom_fields_v12024-02-26
Vehicle notesvehicle_notes_v12024-03-12
Vehiclesvehicles_v12024-02-26

Breaking changes

DaaS will evolve over time and whilst every effort is made to develop in an unimpactful way, there may be situations where we need to make breaking changes. We consider breaking changes to be:

  • Renaming or removing an existing column
  • Changing the data type of an existing column
  • Changing the name or purpose of a mart

Where a breaking change is necessary a new version of data mart will be published and made available to you automatically. Older data mart versions will remain functional for a determined amount of time to ensure that existing systems can continue to operate uninterrupted.