| Table of Contents | |
|---|---|
|
Subscription
...
Packages
Every MetaField user in your system will have a MetaField subscription package, There are three subscription packages available in MetaField that you may incur charges for. These packages are based on permissions given to users. The three subscription packages are described below along with what permissions are tied with each.
MetaField Standard
This package with different costs based on level of access. The subscription package a user has, and thus what you will be charged for, is based on the permissions they are assigned. The three packages are:
MetaField Standard
This package is the most common and the one the vast majority of your field, office and lab users will have. It applies to any user that uses MetaField for activities other than just viewing reports and/or entering safety data into the field.
If a user has a role with at least one permission in MetaField, other than Delivery Read-Only or Safety Field (see below for more information), they are counted in this package.
MetaField Report Access
...
Occasionally you may have users that only need access to MetaField to view reports
...
. They are not involved in the report creation or delivery process but simply need access to the report repository. This package is appropriate for those people. Users with this role may also optionally be entering in Safety data in the Field module. If they are able to do anything else, they would have a MetaField Standard package. Note: this subscription package replaces AgilePort Employee Access for customers who have upgraded from Agileport 2 to AgilePort 3.
If a user (role) has ONLY the Delivery Read-Only permission or ONLY the Delivery Read-Only permission and Safety Field permission, they are counted in this package.
MetaField Safety Program
...
Firms using MetaField as the core of their corporate safety program will have users who only need access to MetaField for logging safety records but are not using it for anything else. This package is for those users. If there is any additional functionality the user is given, they will have a Report Access or Standard package instead,
If a user (role) has the Safety Field permission only, they are counted in this package.
Supplemental
...
Modules
Some of your MetaField Standard users will have access to enhanced areas of MetaField and you may also incur supplemental charges for supplemental modules they have access to. Refer to your contract or contact your Solutions Consultant if you have questions on what you are being billed for. Like . Like the subscription packages, these supplemental modules are also based on permissions given to users. The four supplemental modules are described below along with what permissions are tied with each.:
MetaField LIMS
MetaField LIMS is used for any user utilizing LIMS for entering lab results, adding cast cylinder daily diameters, or managing lab documents. Supplemental fees may be applied to any user who has a role with at least one permission under the LIMS area. This does not include the LIMS related admin screens in administration. The following image shows the permissions that
...
will cause the user to be counted for this supplemental module:
MetaField Scheduler
MetaField Scheduler is used for any user that needs to add and edit work orders.
...
Note that being able to view the Scheduling module does not trigger this supplmental charge - only the ability to create/edit the scheduling data. The following image shows the permissions that
...
will cause the user to be counted for this supplemental module:
MetaField Field Dispatch
MetaField Field Dispatch is used for any user that need to receive work orders from the scheduler
...
and view their assignments in the field. The following image shows the permissions that
...
will cause the user to be counted for this supplemental module:
MetaField DIY Form/Report Designer
MetaField DIY Form/Report Designer is used for any user that is creating DIY Forms and/or Report Designs in Administration.
...
The following image shows the permissions that
...
will cause the user to be counted for this supplemental module:
