The life blood of DemandCaster is data. To that end, DemandCaster is built with an integrated data management service that securely extracts, transforms, and loads data from virtually any ERP system or data source to the DemandCaster application.
There are three primary components to DemandCaster’s automated data management process:
- Data Connector: Connects to any application or data source.
- Data Hub: Transforms and loads data into DemandCaster and when applicable loads data back to the source on-premise or cloud application.
- API: Allows connection, retrieval, and posting of data to and from a multitude of sources.
Most on-premise applications are typically kept behind a firewall, with no direct access via the Internet. To handle this requirement, the DemandCaster Data Connector is a lightweight 75 MB package which consists of a Java Virtual Machine, various JDBC drivers, a JDBC-ODBC bridge driver, and the actual Java based Data Connector application. It runs as a Windows service on a workstation or a server and serves as the communication link between the on-premise application and DemandCaster. No changes to the firewall are required. The Data Connector supports a full bi-directional movement of data in a normalized XML format between data sources and DemandCaster.
Prior to installing the Data Connector, your IT personal or our support staff enters the integration related information into the DemandCaster Data Hub. Once entered, your passwords are invisible and encrypted to everyone including our authorized support staff. The Data Connector is then downloaded to the location where it will reside, installed, and started.
Upon completion of the Data Connector installation, our support staff is only able to work through the data connector via SQL queries that are written and stored in the Data Hub. We will not be able to log into your server or gain access to your network without the assistance from your personnel.
As a further security measure, you can limit the Data Connector to read only and provide it access to only certain data tables. This can be controlled via the database login credentials you provide. Blackout periods may also be included to prevent the Data Connector from communicating with the Data Hub during certain times when maintenance processes are running for example.
Finally, multiple data connectors may be installed across your extended supply chain to promote end to end supply chain planning and collaboration.