top of page

Zefcot Task

​

In Zefcot, a work instruction is a true first-class citizen called a Task. A Zefcot Task defines one discrete step in your process. Tasks are the nucleus of the Zefcot system in which everything revolves.

Zefcot Overview

How it works

Task

Seven Task Types

​

There are seven Task types in Zefcot to drive process. The Task type indicates the nature of the action to be performed.

Route

@

Send Somewhere

Process

+

Do

Something

Data

>

Collect

Something

Join

*

Hold

!

Info

&

Meta

#

Connect

Sub-Assembly

Stop

Work

Special

Note

Group/

Categorize

Types

You Define Them

​

Identify each discrete step in your process you want to control and define a Task for it. The below is an example of a Data Acquisition Task.

ID/Mnemonic

Description

>MB0750  Measure Bore Inside Diameter .750

​

Using a digital air gauge measure the inside diameter of the main 

bore and record the value.

Notes

Documentation

​

Documentation such as PDFs or Images can be attached to a Task. The documents are delivered to the operator when the Task is being performed.

Define
Documentation

Configuration

​

Configuration data needed to setup a workstation can be attached to a Task. The configuration 

is delivered to the workstation with the Task to configure local hardware.

Configuration

Triggers

​

Custom triggers can be plugged into a Task to perform special functions when the task is processed. Triggers are one way of introducing custom behavior and can be used for any purpose. e.g. communicate with enterprise systems.

Triggers

Data Validator

​

For Data Acquisition Tasks, a custom Validator can be attached to the Task that will examine the incoming data to determine if the data is within tolerance.

0 1 2 3 4 5 6 7 8 9 0

Validator

Data Renderers

​

For Data Acquisition Tasks, a custom Renderer can be attached to the Task that will control how collected data will be displayed to users.

0 1 1 0 1 0 0 1

1 1 0 1 0 0 1 1

0 1 0 0 1 1 0 0

0 0 1 1 0 1 0 1

Renderer

Replication/Spawning

​

Tasks may replicate themselves if they are not completed successfully or may add another Task to the assembly being processed conditionally based on the outcome of the Task. 

Replication

Task Assignments

​

Once Tasks have been defined, they are assigned to part numbers (and optionally customers, and orders). Zefcot will use these assignments to apply Tasks to a new unit when it's serial number is initialized in the system.

Part

Customer

Order

Unit

Assignments

Task Permissions

​

Tasks permissions control who can perform what Task and at what location. This can be setup as strict or loose as you want. In order for a user to perform a Task on a unit, the user and the location must have permission to perform the Task. 

Permissions

Task State

​

Tasks that are applied to a unit have state indicating its current disposition. Pending, In Process, Passed, or Failed.

State

Production Processing

​

When an unit is scanned on the shop floor 

Zefcot supplies the next Task to be worked.

Production

Capture

​

Tasks collect information as they are closed including who, what, where, and when. 

Capture
Complete

Compete

​

Zefcot considers a unit complete when all of it's Tasks have been closed.

bottom of page