MetaField Process Overviews

Purpose

MetaField supports a huge range of processes, from logging field and lab activities to creating client reports. Each process follows a set path, with required and optional steps along the way.

This page explores some of the major workflows in MetaField. It'll help you understand how different types of data move through the app, step by step.

MetaField Software Process

The general idea behind MetaField is this: Get field and lab data you create into your clients' hands quickly and accurately. It's designed to make collaboration and communication between your team easy, so you can deliver your expertise to clients in hours instead of days and months.

See More

Below is a visual showing how data moves across MetaField, from when it first enters the app all the way to data delivery. For a more detailed breakdown of each step, click here.

Work Order & Dispatch Process (Scheduling)

MetaField allows your schedulers to assign work orders to field technicians. Schedulers may create and submit these orders to field techs in the Scheduling module. Once submitted, field staff can view, accept and complete, or decline assigned work orders in the Field module (Field > My Assignments).

See More

Below is a visual of the required and optional steps a work order can follow, from creation to completion. For more info on how work orders are scheduled and managed in MetaField, click here.

Lifecycle of a Density Test

Field techs can create and manage density tests in the Field module (Field > Density Testing). Field users input data and save the test, which then moves to Quality Control for review and report creation by the project manager. Project managers can also view saved density tests and their current status (pending, analyzed, etc.) from the Dashboard module.

See More

Below is a diagram showing how a density test moves across the Field and Quality Control areas of MetaField, along with optional steps. For more details on the lifecycle of density tests in MetaField, click here.

Lifecycle of a Lab Specimen (Concrete/Grout/Mortar or Generic Sample)

Your team can manage specimens across the entire lab testing process. Field techs start by creating a sample (comprised of one or more related specimens) in the Field module, then check it into a lab. Your lab techs receive the specimens in the LIMS module, moving them through the work queues for testing and reporting.

Project managers can track every step of this process in Quality Control, and even create a report for the tested specimen from there, if required.

See More

The visual below shows how samples/specimens are logged in Field and managed in LIMS. The Concrete/Grout/Mortar queues are used to test those types of materials. Other specimen types are tested using the Other Materials work queues. For more info on the lifecycle of specimens in MetaField, click here.

Lifecycle of an Activity Record

Activity records are forms that capture the details of a specific work event. These are highly flexible and allow your team to report on almost any type of activity done in the field. Activity records can be created in the Field or Quality Control modules by a field tech or project manager, respectively.

See More

The visual below shows the different paths an activity record can follow across Field and Quality Control. Project managers can also view and track open discrepancies and activities requiring review from the Dashboard module. For more info on activity records, click here.

Lifecycle of a Report

Reports are PDF outputs of the data you collect in MetaField, such as lab tests, field reports, and other activities. These reports make it easy to send relevant project data and updates to your clients. Reports can be built in many areas of MetaField, including Field, LIMS/Lab, and Quality Control (QC).

Once created, all reports end up in the Delivery module, where they can be finalized and emailed to clients, or made public using AgilePort.

See More

This diagram shows the different ways a report can be created, and how they flow from initial draft to final delivery. For more info on reports in MetaField, click here.

Lifecycle of a Safety Record

Safety records are PDF reports of safety data captured in MetaField, such as audits, incident reports, or safety observations. These records are a useful way to gather safety data across your projects. Safety records can be filled out in the Field module by your field staff, or in Quality Control (QC) by project managers. All safety records are visible in QC once saved.

If required, your administrators can create customized safety record forms. This allows you to control exactly what data your staff should collect when filling out a safety record. Custom forms are built in the Administration module. Once completed, these forms an be selected and filled out in Field or QC as safety records.

See More

This diagram shows how safety records can be drafted in Field or QC. The final output is a PDF safety report (or safety field report when drafted in Field). For more details on safety records, click here.