The m3i platform is a collection of components that "talk" to each other across a network. Usually these components are in physical proximity and are often installed in the same physical machine.

Some are User Interfaces, some are applications contributing external functionality but at least one must be a provider to make them work together, such that they are greater than the sum of their parts. This cluster of components can be thought of collectively as distributed application that communicates via m3i.

m3iR is such a provider working as a hub for communications for these loosely coupled components. m3iR runs inside a Ricoh MFD and exposes its functionality via attributes such that the other components (and people using them) can interact with the MFD in innovative ways.

So m3iR is the 'brains' of m3i but there is not a great deal that can be said about it in a non-technical sense. Its primary function is to get images from a source and send it to a destination. In the current version there is a single source, the MFD's scanner. The destinations are print, email, network folder and internet fax. Just remember that if you want to use any m3i component you will need m3iR to talk to the MFD.

For the techies amongst you...

Key Features

• m3iR is a layer on top of Ricoh's embedded environment (SDK/J) that abstracts and extends the functionality of the Ricoh MFD enabling it to be part of m3i. 
• Get from scan. Send to print, email, network folder, internet fax.
• m3iR has a customisable Machine Definition that can be used to redefine, restrict or extend the attributes of the MFD.
• m3i components monitor and utilise the functionality via these attributes over HTTP or securely over HTTPS.
• The nature of m3i is such that all connected components are advised of the same information simultaneously and alter attributes collaboratively. m3iR and m3i make developing customised solutions or integrating business processes very much easier than using SDK/J directly.
• m3iR provides a foundation upon which other m3i components can store their resources in order for them to fucntion. For example, web browser based UIs can be installed and served-up from m3iR.