Integrated Product Database for Food Industry [Mercrius] | FAQ

FAQ

1) What are the requirements for the operational environment?

The following environment is recommended (supported ranges vary depending on the Mercrius version. Please contact us for details.)

2 x CPU at 2 GHz or faster, RAM 2 GB or more, and a hard disk with plenty of available space.
Windows Server 2008 Standard or Enterprise (x64 only)
Windows Server 2003 Standard Edition or Enterprise Edition

Specifications which satisfy requirements of the operating systems in use (CPU at 1 GHz or faster, RAM 512 MB or more, a hard disk with plenty of available space)
Windows 7,Windows Vista, or Windows XP
IE8 or IE7 (some function do not work with the x64 edition of IE)
Excel 2007 or Excel 2003 (required if using the Excel report output function)

There are some cases where the server is running in a virtual environment. Please contact us for details.

2) What kind of data can we manage?

Many customers use Mercrius for managing product and ingredient information.
You can manage various types of data such as diagnostic information, packaging information, customer support information, etc., to suit your business operations.
You can place product information as the core and associate information in different fields.
In addition to text data in the database, you can associate images and electronic files.
You can declare tables in the database as subject to management by making Mercrius aware of them at the implementation. You can change the management scope even after commencing the operation as required.

3) What types of reports can it produce?

Mercrius can output Excel reports and PDF reports.
You can create report templates in advance and register them to Mercrius to output reports in various layouts (SVF designing department is required to create templates for PDF reports).

4) Can Mercrius link with other systems?

You can use the Mercrius batch function to import and export CSV files.
You can use the database function to transfer diagnostic information to FINET FDB and Arcanum.
Program development is not required to enable Mercrius to import and export CSV files (configuration only).

5) Can we reduce the burden of entering data?

You can use the Excel import function to transfer data in Excel files on the screen.(register the Excel file as a template in advance.)
This allows you to check the data integrity and automatically format values before registering the data on the screen into the database.

6) Can we define access levels to the data?

You can define access levels by assigning separate data entry screens to groups based on the user’s organization and authority, and specify the available screens for each process in the business operation flow.
You can configure data access in a way where a user is not even made aware of data outside of his/her operations.
You can log what the user did and to which data.
You can modify the list screen and entry screen using Designer (there is no need for programming either in the implementation or in the operation).

7) How is Mercrius implemented?

We will establish a project team which includes staff in charge of departments and business operations. The team will clarify the business flow and summarize formats of input and output reports. Then we will implement them on Mercrius.
We will create a prototype before the actual roll-out to make sure that the system will be introduced seamlessly.
Generally, the first two month are spent on designing (clarification of managed items and the business flow), the following two month on creating the prototype, another two month on implementing the system, and approximately a month on following up; however, the duration varies depending on the scale, the volume of information to be managed, and the complexity of the business operation flow.
The system implementation and operation can be achieved relatively in a short time compared to bespoke application development.

1) Is the generation management function of product information included?

Mercrius manages generations using a concept called "revisions"
If part of product information is modified, Mercrius would create a new "revision" and applies the change; therefore, information before the modification is preserved and used for searches on previous products.

2) Can we manage a combination of products as a set product?

Mercrius manages products using a concept called "assortment".
You can include a member product of a set in search results if part of the set is applicable to the given search condition.
You can also manage without using the "assortment" concept if preferred.

1) Can we manage procurement from multiple suppliers?

You can manage products with multiple suppliers by also using the "assortment" concept just as you do for set products in product information management.
You can also manage without using the "assortment" concept if preferred.

2) Can suppliers directly enter information?

We have implemented a configuration where specific Mercrius screen were made accessible on the Internet to allow information entry.
If you are using VPN, some functions may be restricted depending on the VPN devices deployed.
Please contact us for details.

1) What is the difference between the diagnostic information database and the Mercrius' normal information management?

Mercrius has a set of items which are the minimum requirements for diagnostic information sheets. You can generate the basic items of the diagnostic information database smoothly by assigning the corresponding items in the product database to them.
If you enter all items in the diagnostic information database, you can transmit them as they are to FINET FDB and Arcanum (all items are covered). You can also add any items required for your business operations.
You can recognize which items of diagnostic information may be affected by a certain modification in the product database. (Planned)

2) Can't we output diagnostic information sheets (Excel report) from anywhere else except from the diagnostic information database?

You can output either from the product database, or from the diagnostic information database depending on the configuration.
It is recommended to standardize the output from the diagnostic information database if it has been implemented; however, you can configure to output internal references, etc. from the product database to suit business operations.
However, if you have implemented the diagnostic information database, data transmission source to FINET FDB and Arcanum is fixed to the diagnostic information database (whereas data is transmitted from the product database if you have not implemented the diagnostic information database).

1) What business operations can Mercrius help?

In addition to the “product development process involving the company wide business operation flow”, Mercrius can be applied to some other operations for restricted purposes such as “search operations for customer support and query information management”,“submitted diagnostic information sheet management”, and “master data management which does not involve a complex business operation flow”.
You can introduce Mercrius in selected departments and gradually expand the application scope.
You can integrate high-level product development processes and the company-wide business operation flow by implementing Mercrius Quevel.