For years, multi-function print devices (MFP/MFD) have posed a problem for Managed Print Service (MPS) Providers: how to monetize non-copying and non-printing functions. Copying and printing are easily monetized by charging per physical page, but scanning is harder because there is no physical product to generate a charge; users simply place items on the glass and scan. Additionally, the functions are limited to scan-to-email functionality and fax. Now, however, there are more possibilities for you and your clients: In Time Tec’s series of HP Workpath connector applications give MFPs more functionality, and you get new ways to monetize the glass.
Do you remember all the hundreds of tests you took on preprinted forms while you were in school? And how there was always a moment of panic followed by dread when you realized you skipped a row and all of your answers were on the wrong row? Imagine how educators must feel managing all that mess.
In 2008, Apple changed the cell phone game when it introduced the first iPhone. It was similar to previous smartphones in that it had a camera and music player, but what catapulted it to the top of people’s wish lists was the ability to host applications. Users, competitors, and developers all took notice. It wasn’t long before almost every smart device manufacturer had its own app store with thousands of apps being developed every day.
We know you game the system when it comes to your MPS tools. We know you buy one license and share it with multiple people. And we know why — to save money. But there is a clear disadvantage to the seat-based pricing system — you must sub-optimize. When everyone’s work must go through the person currently in possession of the license, it turns into a bottleneck. With seat-based pricing, you also often find yourself playing rotating license key — chasing down the license key and coordinating login times. Questions frequently arising from people using seat-based are, “Who is using the license key now?” or “Who is logged into the account?”
I used to think that using classes in my code meant that I was using an Object-Oriented approach. After some time, I realized I was mistaken.
While I was reading the book "Clean Code" by Robert C. Martin, some examples took me by surprise. There were some examples used for demonstrating the procedural coding style and OO coding style that were using classes and methods. This article will share the insights that I have learned since then.