TrakSYS™ Training

D ay 3
Training Overview
 3

Training Agenda

Day 1 Day 2 Day 3 Day 4 Day 5

TrakSYS Overview Content Pages Performance M anagement API Introduction Production Scheduling

Setup and Installation Values Dictionary Content Page Functionality Logic Service Alerts and Notifications

Configuration Basics Visual Pages Batching and Storage Data M anagement Service Inventory M anagement
Systems
Navigation Introduction Content Parts and Features TrakSYS Extensibility Statistical Process Control
Template Systems
Functionality and Data Users and Permissions Sites, Translations, and Audit Support and Resources
Task Configuration

Introduction Training

Advanced Training

Comprehensive Training
Discrete Systems and Event Configuration
 5

Training Objectives

Explore in more detail the modeling and functional support for

tracking complex machine stoppage data.

Describe the advanced settings available in the System and Event

Definition entities that allow business rule definition for
monitoring multiple Tag inputs and discerning the more accurate
stoppage reasons.
 6

Discrete Systems

• Used to model Manufacturing

Equipment which produce / process
Discrete Items (Cans, Cases,
Widgets, etc…)
• May represent a Production Line
(S95), or Work Cell (S95) / Individual
Equipment (e.g. Packaging Line,
Labeler, Caser, Sealer, etc…)
• May include Sub-Systems (Work
Cells) to represent smaller
components within the main System
• Contain child configuration elements
to model Stoppages, Tasks, SPC
Sampling and KPI Calculations
 7

Discrete System Properties

• Event Split settings allow Events to be

automatically End and Restart Events when
specific transitions occur…
• Day Change
• Shift Change
• Job Change
• Specify how Events behave in Display and
Categorization User Interfaces
• Allow Interaction
• Display Delay
• Auto Acknowledge
• Settings effect all Event Definitions defined
within the System
 8

Sub-Systems

• Allows for organizing and

grouping Event Definitions by
smaller pieces of a larger System
(Equipment on a Line)
• Settings applied at the Sub-
System override similar settings
at the System Level
• Grouping Event Definitions in
Sub-Systems does NOT effect
Triggering or Priority Logic
 9

Event Definitions

Packaging Line 1 Configuration

• Represent configurable data entry fields to be collected during
Changeover execution of a specific Event
• An Event represents a span of time (typically downtime)
Filler Event Definition associated with a specific asset (System)

Jam • Configurable at the System OR Sub-System Level

• A Discrete Trigger Tag property indicates when an Event Starts
Tipped Bottle and Ends

Labeler
Execution
Jam
Event Records • Loaded and executed by the Logic Service
No Labels • Events contain reference to related information such as Job,
Batch, Product, Shift, OEE Type, Category, etc…
• Only one Event at a time can be active for a given System *
 10

Event Definition Properties

• By default, only one Event Definition is

allowed to be active on a System
• Subsequent triggered Events are recorded as
Sub-Events related to the primary active
Event
• Event Definitions settings control how the
active Event is determined when multiple
Triggers are active at the same time…
• Trigger Tag
• Priority
• Re-Evaluate System Event on Start/ End
• Isolation Type
 11

Event Definition Example

Event Definition Priority Re-Evaluate on Start Re-Evaluate on End Isolation Type

Changeover (C) 2 YES YES Single Active

M aintenance (M) 4 Independent

Filler Stop (F) 10 YES Single Active

Labeler Stop (L) 20 Single Active

Events

L 10:00 – 11:00

F 10:08 – 10:56

M 10:16 – 10:54

C 10:20 – 10:52
 12

Event Categories

• Hierarchical list (up to 10 levels) of reasons

or descriptions that may be manually
assigned to Events
• Provides details about Events that cannot be
automatically determined from the Process
Automation
• Categories can be defined to be used for
specific Event Definitions, or can be added
as Global (available to all Event Definitions)
• Optional Event Codes can be related to each
Event Category allowing Events to be
associated with higher level Business
Classifications
 13

Event Category Assignment

• Relate Event Category Groups (collections

of Categories) with a…
• System
• Sub-System
• Event Definition
• An Event will display Event Categories
from a combination of all assignments
from its related Entities
• Global type Event Category Groups will
be displayed for every Event
 14

Event Script Events

• The following transitions are monitored by the

Logic Service for Event records…
• On Start
• On End
• On OEE Type Changed
• TrakSYS allows for these transitions to be used to
trigger real-time functionality such as…
• Email Notifications
• Entity Script Class Events
 15

Event Data Structures

KPI Configuration
 17

Training Objectives

Explain the features and capabilities of the KPI tracking entities in

TrakSYS for recording real-time production counts and aggregating
related Event and stoppage data.

Understand Overall Equipment Effectiveness (OEE) and other key

performance indicators to better understand the productivity of
manufacturing processes.
 18

KPI Calculations

Configuration
Filler
• Allows the collection of real-time production counts and event
information to record Interval records in the TrakSYS Database
• An Interval contains raw data over a period of time (typically 30
to 60 minutes) that can be used to calculate Key Performance
Indicators (KPIs)
Production Flow

OEE : 50.9% • Configurable at the System Level

Labeler Availability : 87%
Common KPIs
Performance : 61%
• OEE : An industry standard calculation for measuring Asset
Quality : 96% Effectiveness [ OEE = A * P * Q ]
• Availability : % of time a process is available for
Caser
Production
• Performance : Ratio of Total Units vs. Theoretical over
Available Time
• Quality : Ratio of Good vs. Total Production
• TEEP : A variation of OEE that re-interprets un-scheduled time
as Availability Losses
 19

KPI Calculation Properties

• Interval Duration
A raw KPI data record is recorded every Interval
Duration (minutes).

• Theoretical Rate
Maximum Calculation Units per minute the
measured asset can be operated.

• Target Rate
Ideal Calculation Units per minute the measured
asset should be operated.

• Derived Input
One of the three Inputs that should be calculated
based on the other two.

• Calculation Units
Unit of measure for the smallest counted piece on
produced on the System
 20

KPI Counters

Total Units
Configuration
Filler
(Bottles) • Allows the real-time accumulation of automated counters (Tags)
to record Production Count data in the TrakSYS Database
• Counters are characterized as Total, Good, or Bad
Bad Units • Multipliers can be configured to allow conversion of Raw Units
(Bottles) to Calculation Units (Cases to Bottles)
Production Flow

Labeler

Execution
Bad Units
• Loaded and executed by the Logic Service
(Bottles)
Caser • Counters must move Forward Only with the exception of being
Reset to Zero
• Counter Tags are polled on every scan (~1 second) and the
Good Units
difference is Accumulated
(Cases)
 21

KPI Counter Properties

• Counter
The automation Tag to be monitored and
accumulated.

• Counter to Input Units M ultiplier

Multiplication factor to convert the raw Counter
Units to Input/ Calculation Units (Cases to Bottles).

• M aximum Increment per Scan

Counter Tag movement that exceeds this setting
(within 1 Logic Service Scan – typically 1 second)
will be ignored.

• Rollover
This setting indicates a fixed value where the
Counter Tag is expected to rollover back to zero (a
setting of 0 indicates that the rollover point is
unknown).
 22

KPI Counter Example

Bad Bottles - Filler Rollover 100 M aximum Increment per Scan 5

Time Stamp Tag Value Tag Increment Counter Value Reason

11:00:00 0 0 0 0

11:00:01 3 [ +3 ] 3 [ +3 ]

11:00:02 5 [ +2 ] 5 [ +2 ]

11:00:03 8 [ +3 ] 8 [ +3 ]

11:00:04 90 [ +82 ] 8 [ +0 ] Max increment value Exceeded

11:00:05 94 [ +4 ] 12 [ +4 ]

11:00:06 97 [ +3 ] 15 [ +3 ]

11:00:07 1 [ +1 ] 19 [ +4 ] Rollover value Exceeded

11:00:08 4 [ +3 ] 22 [ +3 ]

104 22
 23

OEE

Total Time

Not Holiday, Not Production

Net Operation Time
Scheduled Scheduled, etc…

Availability Changeover, Material Shortage, PM,

Production Time
Losses Breaks, Cleaning, Training, etc…

Performance
Run Time Short Stops, Reduced Speed, etc...
Losses

Quality Rejects and Rework

Productive Time
Losses

OEE (Productivity)

TEEP (Asset Utilization)

 24

OEE

Availability Production Time

Net Operation Time

Performance Total Units

Th. Rate * Production Time

Quality Good Units

Total Units

OEE
Availability * Performance * Quality
 25

KPI Data Structures

 26

Demonstration

• Show System Properties • Configure Event Categories

• Split • Assign Event Categories to System
• Event • Configure a KPI Calculation
• Show Sub-System Properties • Configure KPI Counters
• Event
• Show Event Definition Properties
• Trigger Tag
• Priority
• Re-Evaluate
• Event
Lab 9
Performance User Interfaces
 29

Training Objectives

Learn about the various standard Content Pages available within

TrakSYS to quickly configure and build a Performance
Management operator user interface.

Explore the techniques for integrating a custom Page to be called

from a link in a standard Content Page.
 30

Standard Content Pages Review

Content Page (out-of-the-box)

Content built into the TrakSYS product. These Pages cannot be altered (other
than what is exposed via Parameters and configuration settings).
 31

Performance Related Pages

Event Attention List Event Attention Event Categorization

Lists Events requiring Detailed Event Information Category Assignment
Attention and Options

Real-Time Overview Planned Jobs Create New Job

Current Job/ Shift Lists upcoming Jobs Manually create Job
Event Overview
KPI Overview

Completed Jobs End Job Start Job

Lists finished Jobs End Job Production Begin Job Production

Job Overview
Job Summary
KPIs for Job
Events for Job
 32

System Real-Time Overview Properties

• System and KPI Calculation IDs

are Required
 33

System Real-Time Overview

 34

Job List Pages

• Planned Jobs
Lists Jobs assigned to the
System that have yet to
begin.
• Completed Jobs
Lists Jobs assigned to the
System that have ended.
• Allow filtering by Date
Range and Product
• Support common Actions
 35

Job Action Pages

• Start Job
Confirmation and execution. Sets Job and
Product Tags based on System configuration.
• End Job
Confirmation and execution. Clears Job and
Product Tags based on System configuration.
• Redirects to System Overview
 36

Real-Time Event List

• Contains Events for the

System which have been
configured to display for
Categorization and/ or
Acknowledgement
• Displays Active and Ended
Events
• Can show Events for
multiple Systems
• Supports common Actions
 37

Event Attention

• Displays details for a selected Event

• Offers Options
• Change Event Definition
• Change Event Category
• Edit Notes
• Split
• Acknowledge clears Event from the
Attention List
 38

Event Categorization

• Displays Event Category

Hierarchy based on
Configuration
• Selecting a Category
with children drills
down to the next level
of Event Categories
• Saving applies the
Category to the Event
Content Page Navigation
 40

Training Objectives

Explore the mechanism used by standard Content Pages to

interconnect and navigate between each other.

Discover how solution-specific Visual Page Definitions or

specifically defined Content Pages can be inserted into the
navigation chain to allow standard and custom Content Pages to
be used in combinations.
 41

Related Content Pages

Event Attention List Event Attention Event Categorization

Lists Events requiring Detailed Event Information Category Assignment
Attention and Options

Real-Time Overview Planned Jobs Create New Job

Current Job/ Shift Lists upcoming Jobs Manually create Job
Event Overview
KPI Overview

Completed Jobs Start Job

Lists finished Jobs Begin Job Production

Job Overview
Job Summary
• How does this work?
KPIs for Job
Events for Job • Where is the Planned Job Page?
 42

“C Equals”

…/ ocv/ packaging/ linehub/

Real-Time Overview Planned Jobs

Current Job/ Shift Lists upcoming Jobs
Event Overview
KPI Overview

…/ ocv/ packaging/ linehub/ ?c=ETS.Application.Job.JobDiscreteListForSystemPlanned

( programmatic identifier for Content Page )
 43

Integrating a Custom Page

Event Attention List Event Attention Event Categorization

Lists Events requiring Detailed Event Information Category Assignment
Attention and Options

Real-Time Overview Planned Jobs Create New Job

Current Job/ Shift Lists upcoming Jobs Manually create Job
Event Overview
KPI Overview

Completed Jobs Start Job

Lists finished Jobs Begin Job Production

Job Overview
Job Summary
KPIs for Job Special page Functionality Needed
Events for Job
 44

Integrating a Custom Page

• Navigation in standard Content Pages may be

Overridden
• Provide a Relative URL
• Visual or standard Content Page
• Any other URL
• Parameters may be Passed (as available)
• Page Key on same Hierarchy Level
• JobListSpecial ? SystemID = {SystemID}
• Page Key back one Hierarchy Level
• ../ JobListSpecial ? SystemID = {SystemID}
Page Values and Instances
 46

Training Objectives

Understand how to programmatically set items to the Values

Dictionary for a single Page, or across an entire section of the
Page hierarchy.

Explore the capability to create a single Page Definition, that is

rendered multiple times in the navigation infrastructure based on
a configurable set of entities.
 47

Page Values

Site Sec H1 H2 Spokes

• Allows programmatic setting of items to the
Values Dictionary for a Page and all of its
Children (Hubs and/ or Spokes)
• Values set via .NET script Editor
• Retrieve data from TrakSYS
• API is Available
• Add to Values Dictionary
• Occurs before Page Class Script is
Executed
 48

Page Values Script

 49

Page Instances

• Allows a single Page Definition to be

Site Sec H1 H2 Spokes
rendered multiple times in the User Interface
• Instances based on one of three modes:
• Custom Script: Use API and SQL to
build a list of Instances
• Page Definition Instance: Configure
instances with IDs and Keys
• System by Area Key: Get one Instance
Inst. per System in an Area

L1
• Instances set via .NET script Editor
• Retrieve data from TrakSYS
L2
• API is Available
L3
• Add to Instances List
• Occurs before Values Script is Executed
 50

Page Instances Custom Script

 51

Page Instances | Values Script

 52

Page Instance URLs by Key

Base Pages URL

http:// servername/ ts/ pages/
http:/ / servername/ ts/ pages/ site
http:// servername/ ts/ pages/ ocv
http:/ / servername/ ts/ pages/ site/ section

http:// servername/ ts/ pages/ ocv/ packaging

http:/ / servername/ ts/ pages/ site/ section/ hub1$instancekey
http:// servername/ ts/ pages/ ocv/ packaging/ line$L1
http:/ / servername/ ts/ pages/ site/ section/ hub1$instancekey
http:// servername/ ts/ pages/ ocv/ packaging/ line$L2
 53

Demonstration

• Show a single Page Values Script • Walk through the Standard

Performance Content Pages
• Show an Instances Script
• System Real-Time
• List all Systems
• Job Pages
• Show an Instances Values Script
• Event Pages
• Based on Instance Data
• Create a custom End Job Page
• Visual Page Definition
• Link to System Real-Time
Lab 10
Batching Configuration
 56

Training Objectives

Explore in more detail the Batch System and Batch Recipe

Management features within TrakSYS.

Describe the settings available in the System, Function Definition,

Product and Recipe entities that allow the setup and systematic
execution of a Batch System and Batch Recipe respectively.
 57

Batch Systems

• Used to model Manufacturing

Equipment which produce / process
Batch or Volumes of Material
(Process Cells (S95) / Batching Lines)
• Contain one or more Sub-Systems or
Units (e.g. Blender, Mixer, Granulator,
and Dryer)
• Contain child configuration elements
to model Batch Steps, Events, Tasks,
and SPC Sampling
 58

Batch System Properties

• Similar to Discrete Systems

• Product Set
Identifies the set of Products that may be
stored within the System (if applicable)
• Event Split
Settings allow Events to be automatically End
and Restart Events when specific transitions
occur…
• Day Change
• Shift Change
• Batch Change
• Batch Size (Planned and Actual)
Can be defined dynamically for a Batch
System using Tags
 59

Batch Sub-Systems

• Allows for the creation of all Data

Definitions (Function, Event,
Task, Sample).
• All data definitions are executed
at the sub-system level, not at
the system level.
• Sub-systems model the actual
process options available for the
Batch system.
 60

Sub-System Properties

• Job and Batch Tags are configured at the Sub-

System level in Batch Systems
• A Batch System must have at least one Sub-
System
• The Job Tag should contain a unique identifier for
the current Job running on the Sub-System
• The Batch Tag should contain a unique identifier
for the current Batch running on the Sub-System
• TrakSYS creates new Job and Batch records for a
System when the Job and Batch Tags change
Values
 61

Batches

• Batches are smaller sub-sets of production within Scale

Job : ADRA-7655
a Job
Batch : 3
• Batches apply only to Batch type Systems

System : Batch Line 2

• A single Batch Job may contain one or more
Batches M ixer
Job : ADRA-7655
• A single Batch System (containing many Batch
Batch : 2
Sub-Systems) may be processing more than one
Batch Simultaneously
• Each Batch Sub-System may only be operating on
Dryer
one Batch Simultaneously Job : ADRA-7655
Batch : 1
 62

Function Definitions
Batch Systems Only

Batch Line 2 Configuration

• Allows the real-time examination of an input condition to
Scale record instances of Batch Step records in the TrakSYS Database
• A Batch Step represents a span of time that a Batch System is
Load engaged in a specific activity (Step)
Function Definition
Measure • Configurable at the Sub-System Level Only
• A Discrete Trigger Tag property indicates when a Batch Step
Clean Starts and Ends

Mixer
Execution
Load • Loaded and executed by the Logic Service
Batch Step Records
• Batch Steps contain reference to related information such as
Mix Job, Batch, Product, Shift, etc…
• It is possible for multiple Batch Steps in a single Sub-System to
Clean
be simultaneously active, with each Batch Step having a
corresponding Batch Step Record
 63

Function Definition Properties

• Batch-specific data definition used to

model potential operations or actions
that a Batch Sub-System (Unit) can
perform
• Trigger Tags are used to record
Function data in TrakSYS™
• Step Categories can be used to assign
reasons to functions the execute
longer than their planned duration
• The actual sequence and duration of
Function Definitions required to
complete a Batch is defined as a
Recipe in the Product configuration
 64

Product Materials

• Represent a physical material that is

consumed or produced by a
manufacturing process
 May be used for all System types
 Does not require the TrakSYS™
batching feature line
• May be simple ingredients or
compounds of other materials
defined in the configuration
• May be associated with a product in a
configured Product Set to define a Bill
of Material for a product
 65

Product Recipe

• A Recipe is a formula or a set of production

directions for a specific Product on a
specific Batch System
 Product and System must exist prior
to Recipe creation
 May be assigned to a System Template
• Defines the size and overall duration for a
single run of the Recipe
• Recipes may be versioned with their
associated Products
• A Recipe is made up of one or more Recipe
Step Definitions
 66

Recipe Properties

• A product Recipe is created and assigned to

the Line 1 Batch System
• Support for different planned durations
based on “multiples” of the Recipes
Planned Batch Size
• Recipes have versioning where the most
recent version (version X) is the active
Recipe for this combination of Product and
System
 67

Recipe Step Definitions

• Define the sequence and duration of steps

required for the completion of a batch
 Assigned to an existing Function
Definition from a subsystem
 Steps may be executed in parallel or
sequentially
 Does not support complex workflow
structures (repeat until, conditional
branching, etc.)
• A Recipe step is automatically started when
its associated Function Definition becomes
active based on its Trigger Tag logic
 68

Recipe Step Materials

• List of Materials can be added to

individual Recipe Steps in order to track
accurate batch records
• Materials are assigned quantities that
represent percentages of the entire Batch
size specified
• Materials are consumed by the Batch
process at each specific Recipe Step
Definition
Batching Data
 70

Training Objectives

Explore the data records associated with Batching processes.

Understand how Batch Step and Material Use Planned records are
created, and how Batch Step Overages and Material Use Actual
records are related.
 71

Batch Steps

Scale: Measure and Weigh

• Batch Steps are created when a Batch is started Start 1 | End 1

• Batch Steps have an expected Start and End Scale: Measure and Weigh M ixer: Load
Sequence, as well as an expected duration Start 2 | End 3 Start 2 | End 2

Recipe Definition
• The Start and End timestamp for each Batch Step M ixer: Mix
is based upon the associated Function Start 3 | End 3
Definition’s Trigger tag
Scale: Clean M ixer: Load
• Multiple Batch Steps can occur at the same time Start 4 | End 16 Start 4 | End 4

M ixer: Mix
Start 5 | End 5

M ixer: Clean
Start 6 | End 16
 72

Batch Step Overages

• When a Function Definition’s Trigger Tag is

active, a Batch Step will start for that
Function on that System
• Batch Steps have an expected duration and
sequence based upon the Recipe
configuration
• If step occurs out of sequence, it will be
marked as Unexpected and have a duration
of 0 seconds
• A Batch Step Overage is created any time a
Batch Step exceeds its expected duration
• Batch Step Overages can be assigned Step
Categories to assist with reporting
 73

Material Use Planned/Actual

• Material Use Planned Records are created when the

Batch first starts
• The expected quantity of materials is based off the
combination of Product and Recipe configuration, as well
as the planned Batch
• Actual material consumption can be recorded as Material
Use Actual records
• Planned and Actual records are related Job and
BatchStep records
 74

Batch Product Configuration Hierarchy

 75

Batching Data Structures

Storage Systems and Transfers
 77

Training Objectives

Explore in more detail the modeling and functional support for

tracking material and storage equipment status within TrakSYS.

Describe the settings available in the System and Transfer

Definition entities that allow the capture of material movements
to and from storage type equipment (Silos, Tanks, etc…)
 78

Storage Systems

• Used to model Manufacturing

Equipment which store a Quantity of
Material (Storage Zones (S95))
• Facilitate Inventory and Material
Management Solutions
• Contain child configuration elements
to model Material Transfers , Events,
Tasks, and SPC Sampling
 79

Storage System Properties

• Similar to Discrete Systems

• Product Set
Identifies the set of Products that may be
stored within the System (if applicable)
• Storage Units
String description for the unit of measure
stored within the System
• M aximum Capacity
Maximum quantity that may be stored within
the System
 80

Storage System Layers

Silo
• Storage System contents may be Salt
recorded in Layers
• Each Layer identifies… Lot C
4 KG
• Product, Material
• Lot, Sub-Lot
Lot B
• Quantity 9 KG
• Transfer Definitions enable to tracking
of content movement in and out of the
Storage System
• A transfer (out) may draw from multiple B (2)

Transfer 5 KG
Layers
A (3) Lot A
3 KG
 81

Transfer Definitions
Storage Systems Only

Storage Silo 3 Configuration

• Allows the real-time examination of an input condition to
In from WH record instances of Transfer records in the TrakSYS Database
Transfer Definition
• A Transfer represents a movement of a specific Material to or
Out to Mixer from a Storage System
• Configurable at the System Level Only
Clear
• A Discrete Trigger Tag property indicates when a Transfer
Starts and Ends

Transfer Records Execution

• Loaded and executed by the Logic Service
• Transfers contain reference to related information such as Job,
Batch, Product, Shift, etc…
• Data records include captured information such as the Material
Code and Quantity that is Transferred
 82

Transfer Definition Properties

• Trigger Tag
A Discrete Tag indicating when the Transfer starts and ends.
A value of 1 = transferring. Transfers have duration.

• Transfer Direction
Describes the type of Transfer…

• In : Adding material to the System

• Out : Removing material from the System

• Set : Adjusting/ correcting the quantity in the System

• End Point System

A reference to a System where the material being
transferred is coming from, or moving to.
 83

Transfer Definition Properties

• Quantity Tag
A Tag storing a quantity to be transferred in or out of the
System. The Tag value must be accurate at the moment the
Transfer starts or ends.

• Capture Quantity On
Indicates when the Quantity Tag should be captured and
recorded in the Transfer record (Start or End).

• Capture Tags
These Tags hold TrakSYS production entity Codes or Names
(Job, Batch, Product, Material, etc…). When a Transfer
begins, the associated entity ID is captured and stored with
the record.
 84

Transfers by User Interface

• Standard Content Parts

• Visual Page Definition Forms for solution-
specific User Interfaces
• Scripting / API
• Transfer / tTransfer
Historical record of material movement
in/ out of the Storage System
• SystemStorage / tSystemStorage
Real-time contents of the Storage
System with one record per Layer.
 85

Transfer and Storage Data Structures

 86

Demonstration

• Configure a Batch System • Configure a Storage System

• Configure a Batch Sub-System • Configure a Transfer Definition
• Configure a Function Definition
• Configure Material
• Configure Recipe
• Configure Recipe Step Definition
Lab 11
Template Systems
 89

Training Objectives

Understand how Template Systems are created and the

differences between them and their non-template counterparts.

Explore the Template Tag Mapping capabilities and common

patterns used with Template Systems.
 90

Template Systems

• Used to facilitate rapid modeling of

Manufacturing Equipment that
produce/ process similar products
and have similar data requirements
• Can be created for each type of
System (Batch, Discrete, and Storage)
• Contain child configuration elements
based upon the System type for the
template
• Provides a way to map configuration
from the Parent to the Children
Systems
 91

Template System Properties

• Can be created from an existing parent-less

system
• Available properties will be the same as a
normal system of the same type
• The same children elements will be available
• The same properties will be available on the
children elements
• All Tag properties will expect Template Tags
• Most properties on Children Systems are
disabled and must be configured through the
Parent System.
 92

Template Tag Mapping

• Template Parent Systems will use Template Tags for all tag-
based properties
• Template Children Systems can use any tag type for tag-based
properties
• Template Children cannot have tags directly assigned to them
through their configuration. They must use one of the Assign
Tags actions.
• Template tag prefix is required for the mapping to take place
• Tag Duplication can be utilized to quickly prepare tags for new
template children
 93

Mapping Example
 94

Template Tips

• Existing Systems can be turned into Template

Systems. The new Template Parent System will
have a set of Template Tags created and assigned
to it.
• Tag Duplication can be utilized to quickly prepare
tags for new template children. Tags can be
duplicated with new Prefixes through the Tag
Configuration options.
• A Template can be detached from a Parent, but
cannot be reattached.
• A Parent Template System does not need to have
any Children Template Systems
Task Configuration
 96

Training Objectives

Explore the capabilities of the TrakSYS Task Management entities

and functions to enable periodic quality checks and operator log
entries.

Understand the Task Definition and Task Form Item entities and
their key properties.
 97

Task Definitions

Packaging Line 1 Configuration

• Allows the real-time examination of an input condition to
Hourly Log Entry record instances of Task records in the TrakSYS Database
• A Task represents a request with pre-defined user inputs
Filler Task Definition required (a form) associated with a specific asset (System)

Safety Check • Task Definitions are configured to require 1 or more user input
fields (Task Form Items)
• Configurable at the System OR Sub-System Level
• A Discrete Trigger Tag property indicates when a Task is
Generated

Task Records Execution

• Loaded and executed by the Logic Service
• Tasks contain reference to related information such as Job,
Batch, Product, Shift, etc…
• Task Forms are implemented and completed in the TS Web
User Interface
 98

Task Definition Properties

• Trigger Tag
A discrete condition that determines when a
Task record is created. A Task is created
when the Trigger goes from 0 to 1.
• A Trigger Tag is NOT Required (manual or
script based Task creation)
• Task Completion Seconds
Drives logic that determines when a Task is
considered late (optional). This can drive
scripted business rules and Notifications.
 99

Task Form Items

Configuration
• Represents configurable data entry fields to be collected during
completion of a specific Task
• Task Form Items are organized into groups called Task Form
Item Groups
• One or more Task Form Item Groups are assigned to a Task
Definition defining the fields to be captured in the UI Form

Execution
• Task Forms in the TS Web UI render the defined Task Form
Items as form input fields…
• Text Boxes
• Dropdown Lists
• Check Boxes
• Support basic validation (min, max, required)

Task Form Item Task Form Item Group

 100

Task Form Item Groups

• Task Form Item Group Group

An organizational only level of
grouping to help manage large
numbers of Task Form Item
Groups
• Task Form Item Group
A collection of Task Form Items
that can be assigned to a Task
Definition. They can be
assigned to multiple Task
Definitions
 101

Task Form Item Properties

• Data Type
Drives the displayed form input type and validation in
standard Pages and Parts.

• Prompt
An alternate label displayed on standard Pages and Parts.

• Default Value
The value of the item when the Task is created and before it
is edited by a User.

• M inimum/ M aximum
Used for automatic validation in standard Pages and Parts.

• Require Change
If checked, a User must change the item’s value to
something different than the Default Value.
 102

Associating Task Form Item Groups

• Standard Task Pages and Parts display inputs

based on Task Form Item Groups assigned to
the Task Definition
• One or more Task Form Item Groups must be
Assigned (unless the Task is a simple Yes/ No
completion)
 103

Task Entities

Task Definition Task Form Item Task Form Item

Group

• Controls the creation and • A grouping mechanism • Individual inputs housed

processing of task that is referenced by Task in Task Form Item Groups
records Definitions.
• Represent the actual
• Tasks hold the required • When the task is created, fields found on any type
inputs from users and it references the Task of form.
required timestamps. Form Item Groups to
• Examples
render the inputs.
• Examples • Name
• Examples
• HACCP Check
• Number of tablets
• Common signatures
• Fill Weight
• Cleaning checks
 104

Task Configuration Hierarchy

…
…

Test M etal Detectors

Common Signature Task Form Item
Task Form Item Group
Hourly HACCP Check
Task Definition
Test Bottle Seal
HACCP Check Inputs Task Form Item
Task Form Item Group
Hourly Fill W eight Check
Task Definition
Test Label Placement
Fill W eight Inputs Task Form Item
Task Form Item Group
…

…
 105

Task Script Events

• The following transitions are monitored by the

Logic Service for Task records…
• On Create
• On Late
• On Complete
• On User State Change
• On Pass
• On Fail
• TrakSYS allows for these transitions to be used to
trigger real-time functionality such as…
• Email Notifications
• Entity Script Class Events
 106

Task Data Structures

Task User Interfaces
 108

Training Objectives

Describe the out-of-the-box capabilities of the Task Form Content

Page to quickly enable the creation of Task Management user
interfaces.

Explain how the Task Items Content Part and Task Form Visual
Page Definition Template can be used to create extensible,
solution specific data capture forms.
 109

Task Data Fields

• CreatedDateTime
Timestamp for the Task record creation. Populated by the Logic
Service or the UI (for manual Tasks).

• CompleteByDateTime
Calculated based on the Task Definition TaskCompletionSeconds.
• CompletedDateTime
Actual timestamp of User completion of the Task form (Pass or Fail).
• PassFail
Integer result for the Task.
• -1 = Unknown
• 0 = Fail
• 1 = Pass

• User State
A developer-use-only Integer for extensibility. Use this field to store
a custom Task status or result.
 110

Task New/Edit Content Page

• Automatic Task Form render based on

Task Definition and Task Form Item
Configuration
• Basic field Validation and Task
Business Rules
• Integrated Task Instruction Display
• Edit Mode driven by TaskID
• New Mode driven by TaskDefinitionID
• Zero Script for Database/ API
Interaction
 111

Task Items Content Part

• Allows a custom Task Form to be

created using a Visual Page Definition
• Handles the complexities of the
Dynamic Task Form Items
• Configuration Driven
• Renders
• Populates
• Validates
• Allows for custom Validation and
Insert/ Update Script using the
standard Visual Page Script Editor
 112

Task Form Visual Page Template

• Visual Page Templates provide pre-

configured Content Part and Script
combinations for common Patterns
• The Task Form Template contains the
Parts and Script to reproduce and
customize the standard Task Form
Content Page
• Adjust/ Add Parts to customize
Look and Feel
• Modify Validation and Update
Business Rules
 113

Demonstration

• Create a Parent Template System • Configure a Task Definition

from an existing System • Configure a Task Form Item Group
• Duplicate a Tag Group • Associate the Task Entities
• Create a New Child Template System • View the Task Form Content Page
• Map Tags to the New Child Template • Create a Custom Task Form Page
System
Lab 12