Integrating PrintReleaf with ECI FMAudit®
PrintReleaf offers a software integration with FMAudit to automatically and securely synchronize customer paper consumption data from your FMAudit server to PrintReleaf. FMAudit provides PrintReleaf with a custom, read-only, secure web API designed specifically for this integration.
On a nightly basis, PrintReleaf performs a data collection process that connects to your FMAudit server, retrieves and processes aggregate paper consumption metrics for each of your customers, and deposits the data into the customer’s PrintReleaf account.
At the end of each month, PrintReleaf totals each customer’s paper consumption for that month, equates it to forest impact measured in trees, and issues a Certificate of Reforestation to the customer certifying that their paper consumption has been reforested.
Configuring the Integration
At a high-level, setup of the PrintReleaf/FMAudit integration involves two parts:
- Registering your FMAudit server and customer feeds in your PrintReleaf account
- Enabling the PrintReleaf integration on your FMAudit server
You will need the following FMAudit credentials to register your server:
- URL: The web URL of your FMAudit server.
- Username & Password: Login credentials for a user on your FMAudit server. The minimum necessary permissions for the FMAudit user is Dealer Admin. As a best practice, it is highly recommended you create a new user on your FMAudit server specifically for the PrintReleaf integration.
To register your FMAudit server in PrintReleaf, you provide the URL of your server and Username & Password credentials that PrintReleaf will use to connect to your FMAudit server.
Once your FMAudit server is registered in PrintReleaf, you can begin registering individual customer feeds that should be synchronized with your FMAudit server. To register a customer feed, you supply the customer’s FMAudit Account ID and Activation Date. The FMAudit Account ID is used by PrintReleaf to identify the matching customer in FMAudit. The Activation Date is the date PrintReleaf should begin synchronizing data for this customer; if it is set to a date in the past, PrintReleaf will automatically sync historical data back to that date.
The PrintReleaf integration must also be enabled on your FMAudit server to give PrintReleaf access to retrieve customer paper consumption data. This is located in the Admin > Syncs > Public API Security section of your FMAudit server panel.
You have the option to grant PrintReleaf access to each customer individually, or you may enable it for all customers at once. FMAudit offers two reports with different levels of access for each customer: “PrintReleaf Report” (all devices) or “PrintReleaf Managed Only Report” (only devices marked as ‘managed’). When both reports are enabled, PrintReleaf uses the all devices report.
For complete step-by-step configuration instructions, please view the FMAudit Integration Setup Guide.
Data Collection & Flow
PrintReleaf’s data collectors will attempt to connect to your FMAudit server on a nightly basis to retrieve and process customer paper consumption data. Individual customers are batched and synchronized one after another in a serial fashion.
The duration of a data collection is dependent on a number of factors, including current load on your FMAudit server, the number of customers to be synchronized, and network latency due to geographic distance to your server. Most individual customer data collections finish in between 1 and 2 seconds.
PrintReleaf has read-only access to your FMAudit server, meaning customer data only flows from FMAudit to PrintReleaf and PrintReleaf never writes new data to your server.
FMAudit Customer Data provided to PrintReleaf
FMAudit provides PrintReleaf with a custom, read-only, secure web API designed specifically for this integration. The FMAudit API provides PrintReleaf with aggregate paper consumption data for each customer that can be queried between startDate/endDate time boundaries.
Data fields provided by FMAudit:
- Customer name
- Customer ID
- Number of devices
- Small page count
- Large page count
- Duplex page count
- Last audit date
PrintReleaf normalizes the small page count, large page count, and duplex page count to determine the number of “standard pages” (8.5”x11” 20lb bond). The number of standard pages is then deposited into the customer’s PrintReleaf account.
PrintReleaf does not have access or visibility to any other customer data on your FMAudit server.
Integration Health Checks
PrintReleaf actively monitors the health of your FMAudit integration on two levels: the server level and the feed level.
The server health check is performed by attempting to connect to your FMAudit server using the credentials provided during registration. Failed attempts to connect will immediately mark the server as unhealthy and will pause customer data collection until the health check passes again.
At the individual feed level, PrintReleaf monitors the flow of inbound paper consumption data. If the feed has not received new data from FMAudit in 3 business days, the feed is marked as unhealthy. This often indicates the DCA is stale. When a feed becomes healthy again, PrintReleaf automatically synchronizes data back in time to when the feed became unhealthy, ensuring paper consumption data is never missed.
In transit, all network traffic to and from PrintReleaf’s web servers, data collectors, and APIs is transmitted via HTTPS. HTTP requests are not permitted. At rest, sensitive data (e.g. server credentials) are encrypted using industry standard hashing functions and ciphers.
Personal Data Security & PII
Still have questions?
Can't find the answer you're looking for? Get in touch with us.
Ready To Make A Difference?
As a Managed Print Services provider, you understand the significance of paper usage, and embracing more sustainable printing practices is becoming a vital part to doing business. Your customers rely on you to ensure smooth operations. Let's explore how PrintReleaf can support your business, deliver added value to your customers, and help you contribute to a greener planet.Start the conversation