The Machine Analytics Module works by communicating with printers on the local network and querying them for information about their current status and historical job log. This data is then sent to the cloud for analysis and report generation. The Machine Analytics Module is therefore composed of two parts: the local aggregator, called Authentise Echo and the cloud analytics engine. The following diagram shows how this works
The Authentise Echo acts as the local data aggregator. It should be installed on a computer system that is on the same local area network (LAN) as the printers it will extracting data from (Installation). The same client can be used to extract data from many types of printers simultaneously when configured correctly. The client requires the ability to send outgoing HTTP connections over TLS (HTTPS) to perform its work - you’ll need to be sure your network firewall does not prevent these connections. Only job metadata - name of the job, duration, material consumed - is sent to Authentise servers. No intellectual property, such as actual model data, is ever sent outside of your network.
An organization with multiple networks or subnets can install Authentise Echo in each subnet. The cloud analytics engine will injest reports from all of the locations and aggregate the data into a single organizational report. Reports are available as interactive graphs via a web browser that can be accessed from anywhere with Internet connectivity.
Reports can also be downloaded as CSV files so that customers can perform their own analytics or import into an ERP system.
Machine Analytics can also provide insight into how jobs are scheduled to machines. This includes information on warmup and cooldown times, delays unloading a successful build and time spent switching materials.
All of the data is accessible over a publicly available API.
To get started with Machine Analytics see our guide on Installation