Specifications

Print Controller Design Guide for Information Security:
Page 63 of 92
Forwarding Image Data with Capture
• With the Capture feature, the primary machine function temporarily stores the image data to the
HDD in tandem with the MCS and IMH. A request is then made to the GWWS via the SCS to
capture the image. In tandem with the MCS and IMH, the GWWS in turn loads the image data out
of HDD storage, converts the image to a file type for Capturing. If the file was created using the
Copier or Printer function, the GWWS requests the IMH (via the MCS) to convert the file into a
commonly-used format using the File Format Converter. Finally, the GWWS temporarily stores the
new file in the HDD.
• Following this, the GWWS requests the DCS to forward the new file it just saved to the HDD. The
DCS in turn loads the file out of HDD memory and forwards it to ScanRouter. Three transfer
protocols are available for sending captured documents to ScanRouter: FTP, HTTP and HTTPS.
• For details on the data flow that is followed when images created with each primary machine
function are stored to the HDD, please refer to the “Data Flow” explanations in each section of this
document.
Restoring Images Back to the MFP (MFP models only)
• When Copier or Printer files which were originally downloaded from the MFP to Desk Top Editor for
Production in TIFF or JPEG format are then restored to the MFP, the GWWS sends the data to the
NCS, which then sends it to the HDD for storage via the MCS. This pathway is the reverse of that
used to send stored images to the PC. Before storage, the IMH uses its modules and the File
Format Converter to convert the file format from TIFF/JPEG2000 to a Ricoh-original format. These
“restored” files are actually separate files than their originals, and are stored in the HDD in a
separate location.