Integrating PrintReleaf with OneStop MPS Portal

PrintReleaf has partnered with BITS to offer a software integration with OneStop MPS Portal that automatically, securely, and reliably synchronizes your customers' paper consumption data from your OneStop MPS Portal into PrintReleaf.

Integration Overview

On a nightly basis, PrintReleaf performs a data collection process that connects to the API of your OneStop MPS Portal 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 OneStop MPS Portal integration involves two parts:

1. Registering your OneStop MPS Portal server in your PrintReleaf dashboard
2. Connecting customer feeds to map your OneStop MPS Portal customers to their respective accounts in PrintReleaf

To register your OneStop MPS Portal server in PrintReleaf, you provide the API URL of your server and Username & Password login credentials that PrintReleaf will use to connect to your OneStop MPS Portal server.

Once your OneStop MPS Portal server is registered in PrintReleaf, you can begin registering individual customer feeds that should be synchronized with your OneStop MPS Portal server. To register a customer feed, you select the Customer Name from a dropdown list and configure Activation Date. The Customer Name is used by PrintReleaf to identify the matching customer in OneStop MPS Portal. 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.

---

Data Collection & Flow

PrintReleaf’s data collectors will attempt to connect to your OneStop MPS Portal 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 OneStop MPS Portal 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 OneStop MPS Portal server, meaning customer data only flows from OneStop MPS Portal to PrintReleaf and PrintReleaf never writes new data to your server.

OneStop MPS Portal Customer Data provided to PrintReleaf

The OneStopAPI provides PrintReleaf with aggregate paper consumption data for each customer that can be queried by date.

For a complete data specification, please visit the OneStopAPI documentation.

Data fields provided by OneStop MPS Portal:

CustomerSummary

• id
• name

MeterReadingSummary

• deviceTotal
• colourTotal
• monoTotal
• scanTotal
• largeTotal
• duplexTotal
• smallTotal

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 OneStop MPS Portal server.

---

Integration Health Checks

PrintReleaf actively monitors the health of your OneStop MPS Portal integration on two levels: the server level and the feed level.

The server health check is performed by attempting to connect to your OneStop MPS Portal 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 OneStop MPS Portal 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.

---

Data Security

Encryption

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

PrintReleaf does not collect, store, or have access to any sensitive or private information about PrintReleaf users or their print activity. For users, PrintReleaf does not collect any Personally Identifiable Information (PII) – only the user’s full name and email as provided during registration. For more information, please visit PrintReleaf’s privacy policy which outlines this in more detail: https://printreleaf.com/privacy