http://docs.optrix.com.au/ Wed, 27 May 2026 01:27:59 +0000 FeedCreator 1.8 http://docs.optrix.com.au/_media/wiki:dokuwiki.svg http://docs.optrix.com.au/ http://docs.optrix.com.au/visan:adding_a_new_machine_condition Adding a New Machine Condition Both the OEE and Outage Reporting analytics classify your machine state. By default, the include four main states - Stopped, Running, Idle and Blocking. However, you can add more to your logic whenever you wish. In this case, we're going to add the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:advantages Why Use Visual Analytics Insight without Code Visual Analytics allow you to get insight from your data without having to write your own analytic code. This means you're able to get robust, tested analytics working quickly with a minimum amount of effort. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:analytic_modules Analytic Modules The Visual Analytic addon includes a series of different analytic modules that you can use. These vary from simply providing a calculation, to performing complex line synchronisation or utilisation analysis on equipment. Other analytic modules may also be available from your system integrators, or customised to your needs. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_eventname ARDI Event Name This node outputs the name of the most recently begun event that crosses the current time. This node is used in all modules and is one of the ARDI nodes. Outputs Output #1 is the name of the most recently-started current event from ARDI that comes from the source specified in the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_pastpoint ARDI Past Point Node This node outputs a property value from an ARDI asset in some point in the past. This node is used in all modules and is one of the ARDI nodes. Inputs Default (Input #1) is the default value to output if the property is null or bad. Delay (Input #2) anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_point ARDI Point Node This node outputs the current value of an single ARDI property on a specific ARDI asset. This node is used in all modules and is one of the ARDI nodes. Inputs Input #1 is a number or a string and is used when there's no valid value for the property in ARDI. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_ppoint ARDI Previous Point Node This node outputs the previous value of an single ARDI property on a specific ARDI asset. This node is used in all modules and is one of the ARDI nodes. Inputs Input #1 is a number or a string and is used when there's no valid value for the property in ARDI. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_spoint ARDI Status Node This node outputs the current value of an single ARDI property on a specific ARDI asset, specifically when that status is a digital value - it can only be true or false. This node is used in all modules and is one of the ARDI nodes. Outputs Output #1 anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_status ARDI Status Node This node outputs the current digital/boolean value of an single ARDI property on a specific ARDI asset. This node is used in all modules and is one of the ARDI nodes. This node mainly exists for convenience - you can use a normal ARDI Point node and some logic to do the same thing, but using this node keeps your graph looking cleaner and neater. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:ardi_valuetotext ARDI Value to Text This node converts an input number to the text representation of that number. This node is used in all modules and is one of the ARDI nodes. Inputs Input #1 is a number that represents the value of an enumeration or digital property from ARDI. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:background_caching_system Background Caching System Most of the Visual Analytics work at high data resolutions - to make sure nothing is missed, most analytics use data points that are no more than 1 second apart. While data at this scale works well when you're looking at 10, 20 or 30 minutes of information, you can notice that performance quickly drops when you try to look at longer time-frames. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:basic_const_boolean Boolean (Constant) Node This node is used to add a simple, unchanging true or false status to your graph. This node is available in all modules. This is part of the Basic nodes, common nodes used across several different types of graph. Outputs Output #1 is a boolean anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:basic_const_string String (Constant) Node This node is used to add simple, unchanging text to your graph. This node is available in all modules. This is part of the Basic nodes, common nodes used across several different types of graph. Outputs Output #1 is a string and is equal to the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:basic_const Number (Constant) Node This node is used to add simple, unchanging numbers to your graph. This node is available in all modules. This is part of the Basic nodes, common nodes used across several different types of graph. Outputs Output #1 is a number and is equal to the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:calc_output Calculation Output Node This node is used in the Calculation Module. It's the final output node of any calculation - the number that is sent to this node is delivered to the user. Inputs Input #1 is a number and is the final value of the calculation. Title The title of this node is also the title of the value in the final calculation. If you call this node anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:control_control Control Node This node is used in Control and Detailed Control modules. It takes three inputs - an actual and a target value, and a tolerance - and outputs if the actual value is within an acceptable range of the target. Inputs Actual (Input #1) is a number, that should be the actual, measured value from sensors in the field. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:control_output Control Output Node This node is used in Control and Detailed Control modules. It's the final output node for Control analytics - it chooses what state your machine is currently in. Inputs Active (Input #1) is a boolean (true or false) value - if true, the machine is in this state. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_change Change Node This is a counter node. It adds 1 to the count every time the input value changes. This is often used when you want to count the number of times a specific, relatively slow (ie. lasts for more than 1s) event has happened. Note that this node will count anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_ignore Ignore Node This is a counter node. It's used to ignore periods of time - any changes (depending on the different Output Node you use) they won't be counted when this node is active. This node only prevents counting. Internally, the system still recognises that the value has changed. For other behaviours, you can use the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_output Counter Output This node is a final outout node that chooses what values you're counting in a counter analytic. For example, if you'd like to see your power usage per day, your 'day' value would connect to your Pivot node, and the power usage would connect to this node. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_pause Pause Node This is a counter node. It's used to pause the counter. Unlike the Ignore node (which simply stops the count from increasing), the pause node completely stops the processing of the analytic. You can use the node to stop the counter and the pivot, which might be useful when you have shutdowns, power interruptions, maintenance or communication issues. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_pivot Pivot Node This node is a final outout node that chooses how you'd like to pivot/split your data in a counter analytic. This node is used in only in Counter analytics. Inputs Input #1 is a number or string that will be used to pivot your analytic. For example, if the input is fed a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_rate Rate Node This is a counter node. It takes a rate of change or consumption, and produces a total for the given time-frame. This is often used when you want to count how much of something is being produced or consumed per day, shift or other time window. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:counter_totaliser Total Node This is a counter node. It adds the total amount that a value has increased by between one sample and the next to the count. This is usually used when you already have an existing counter, but it doesn't reset when you'd like it to. For example, in some machines the total counter will reset every time the machine is turned off. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:deployment Analytic Deployment When you create a new Visual Analytic, you don't only create a simple graph. There are also a variety of methods you can use to deploy your analytic - to use it in other ways, across a variety of tools. API Function At the most basic, every analytic can be used as an anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:event_metadata Event Metadata Node This node is used in the Event Detection Module. It is an optional final output node for an event. When an event is captured by the Event Output node, you can also record additional information (for instance, how severe the event was, or what batch it's part of). You add these points of data as Metadata nodes. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:event_output Event Output Node This node is used in the Event Detection Module. It's the final output node of any event. If the input into this node is true, the system marks the event as happening. Inputs Input #1 is a true or false value. True indicates that the event has been seen. Title The title of this node is also the title of the event. If you call this node anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_calc_basic Calculation Example: Area, Volume & Weight In this example, we will take the details of the product we're producing and calculate the area, volume and weight of the product. Available Information AssetPropertyDescPaint LineThicknessThe thickness of the product we're making (m) anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_control_basic Control Example: Time Spent Out Of Control In this example, we see if our machine is maintaining the oven temperatures we are targeting. Available Information AssetPropertyDescFinish Oven Zone 1Temperature - OvenThe actual temperature of our ovenFinish Oven Zone 1 anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_counter_changes Count Example: Number of State Changes Per Day In this example, we want to know how many times our machine stopped and started every day. Our machine has a simple 'running' signal that is 0 when the system is off, and 1 when it's on. Available Information anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_counter_daily Count Example: Daily Total from Totaliser In this example, we want to know how much our machine has produced per day. While our machine gives us a 'total production' value, it resets back to zero every time someone interrupts the power - which happens several times a day. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_counter_rate Count Example: Calculate Per-Shift Energy Use In this example, we want to know how much power our different shifts and crews are using. Our power meters have a simple 'kWh' output that we can use. Available Information AssetPropertyDescIncomer Meter anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_event_advanced Advanced Event Detection This is a more advanced example of Event Detection. It continues on from the Basic Event Detection Tutorial. By the end of the first example, we've got the following graph. Note - for clarity, we'll remove the 'Spike' metadata in the following examples. Step 1: Ignoring Inrushes with a Custom Timer anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_event_basic Event Detection Example: Energy Spikes In this example, we'd like to point out when any of our machines are running at more than 100% of their rated power. Available Information AssetPropertyDescMotorCurrent - PercentageThe amount of current, relative to nameplate maximum anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_limits_basic Limit Example: Time Spent Outside Limits The process of making a Limit Analytic is almost identical to making a control analytic. The only real difference is that the control analytic takes slightly different parameters. A control analytic takes the actual measurement, the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_oee_basic OEE Example: Simple OEE Calculation In this example, we will calculate a rough Overall Equipment Effectiveness for one of our machines - Bridle #1. This will help point out where machines are either being under-utilised or failures are impacting on production and/or quality. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_outage_basic Outage Report Example: Simple In this example, we'll look at the outages we've experienced on our Paint Line, and try to classify why some outages happened. Complexity Because this is more complex than some other metrics, this tutorial isn't quite as step-by-step as the previous examples. It's assumed that you know how to add a node and are familiar with some of the basic node types. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_pivot_analogue Pivot Example: By Product Characteristic Choosing Pivot Data Because pivoting makes new entries for every unique pivot value, we suggest that you only pivot on properties that step rapidly between values, or you take advantage of functions such as anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_pivot_assetmovement Pivot Example: Movement Across Assets There are a number of different applications where machines move between assets - filling, loading, extracting or simply moving past other pieces of equipment. It's not unusual to know what values are as you pass anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_pivot_event Pivot Example: By Events In this example, we're going to use a pivot analytic to see how our different shifts and crews are performing. This will help point out any shifts that are struggling to meet targets. Available Information AssetPropertyDescFacilityProduction Rate anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:example_pivot_mode Pivot Example: By Machine Mode In this example, we will take the power usage on one of our machines and compare the usage when we are producing product to when we are not producing product. This will let us know if we are potentially wasting power by running machines when they aren't needed. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:final_output Output Nodes Every different analytic module will have it's own unique nodes. Some of these nodes are output nodes - they have inputs but may not have any outputs. They are the destination for your analytic data. After the data reaches an output node, it's then processed by ARDI. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_ardi ARDI Nodes The ARDI Nodes are a collection of graph nodes used to retrieve events and property data from your ARDI server. Point - The most recent value for an asset property Prev. Point - The second-most recent value for an asset property Past Point - The value from a specific number of seconds in the past anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_basic Basic Nodes These nodes are in the Basic category and are some of the simplest. They allow you to add fixed values to your graph and do some basic data manipulation. Const Boolean - Constant Boolean Value Const Number - Constant Numeric Value Const String - Constant String Value anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_logic Logic Nodes These nodes are in the Logic category and are used to make logical decisions about how your data flows through the graph. AND - AND (All Inputs are True) NOT - NOT (Inverts an Input) OR - OR (Any Inputs are True) Hold - Holds a numeric value Change - Detects if a numeric value changes anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_math Math Nodes There are a range of different nodes in the Math category, each of which performs a mathematical function or comparison on numbers. Abs - The Absolute/Positive Value of a Number Add - Add Two Numbers Ceil - Ceiling (Round Up) Clamp - Limit a number to a range anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_timing Timing Nodes There are a range of different nodes in the Timing category. These nodes are using to monitor and support changes over time. Clock - Clock data in UTC Timer - A flexible timer Elapsed - The amount of time between samples Time Difference - The amount of time since a fixed date anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:folder_variable Variable Nodes Variable nodes are a category of graph nodes used to store values between individual samples when performing analytics. These can be used to create counters and totals. You can also make custom timers when combined with timing nodes. Set - Set a Variable Value anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:graph Node Graphs Graph is the correct name for a single node programming diagram. It will consist of two or more nodes, connected together. Usually, data will flow through your graph from one or more input nodes to one or more output nodes. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:hysteresis Hysteresis In control systems, hysteresis is used to prevent digital signals (such as alarms, alerts and relays) from rapidly flicking between their on/off or true/false states. In these cases, you'll usually have a switch point and a certain amount of anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:input_nodes Input Nodes Every node programming graph will have one or more input nodes. This is where new data comes in to your graph. Input nodes will often have outputs (connections on the right-hand side of the node), but no inputs (connections on the left). The most common input nodes are anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:linetrack_merge Merge Node The Visual Analytic system allows you to connect an output to multiple inputs, but you can't bring several different outputs to a single input. The Merge node provides this ability - it lets you move your product from several different sources to a single destination. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:linetrack_point Tracking Point Node The Tracking Point node creates a point along the path that your tracking hotspots can flow down in a line tracking analytic. Inputs Input (Input #1) is linked to a destination node from another Tracking Point node. Speed (Input #2) a number that describes the speed of the line at the point. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:linetracking_options Options Node The Options node is used to specify two key options when it comes to line tracking. Inputs Drop (Input #1) is a true or false value. When it changes to true, a new tracking hotspot is 'dropped' into the start of the line. Trigger (Input #2) is a number or string anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_and And Node This is one of the most common logic nodes, along with NOT and OR. It outputs true only if all of the inputs are true. If any or all of them are false, the node will output false. This node is used in all modules. Inputs Input #1 is a boolean value - a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_change Change Node The Change node is a Logic node that is used to detect if a value has changed. This is a slightly simpler method than using a comparison between Point and Previous Point nodes. This node is used in all modules. Inputs Value (Input #1) is a number value. Outputs anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_edge Edge Node The Edge node is a Logic node that is used to detect the rising, falling or both edges of a boolean (ie. true or false) value. It effectively converts a long-lasting value to a momentary value. A rising edge is a change from false to true. A anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_greaterthanh Greater Than Node The Greater Than node is a Logic node that is used to determine if a value is greater than another. This can also be done using the Condition node. However, this version has hysteresis. This node is used in all modules. Inputs A (Input #1) is a number that you want to compare. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_hold Hold Node The Hold node is a Logic node used to keep fix a numeric value so that it doesn't change. It's often used along-side Timer nodes to add a small time-window before events are raised, to avoid overly 'noisy' events and alerts. This node is used in all modules. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_lessthanh Less Than Node The Less Than node is a Logic node that is used to determine if a value is less than another. This can also be done using the Condition node. However, this version has hysteresis. This node is used in all modules. Inputs A (Input #1) is a number that you want to compare. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_not Not Node This is one of the most common logic nodes, along with AND and OR. It inverts a boolean value - turning a true into a false and vice-versa. This node is used in all modules. Inputs Run (Input #1) is a boolean value - a true or a false. Outputs Output #1 anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_or Or Node This is one of the most common logic nodes, along with NOT and AND. It outputs true if any of the inputs are true. If all of them are false, the node will output false. This node is used in all modules. Inputs Input #1 is a boolean value - a true or a false anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:logic_toggle Toggle Node The Toggle node is a Logic node works like a switch. When the input of the node becomes true, the output changes state (from true to false, or vice-versa). Toggles can be used if you want to alternate between different states or conditions, or if you'd like to record a previous action without using anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_abs Abs Node This node outputs the absolute value of an input number - turning negative values into positive values. This node is available in all modules. This is part of the Math nodes, designed to perform mathematical functions and comparisons on values. Inputs anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_add Add Node This node adds the two input values together. This node is available in all modules. This is part of the Math nodes, designed to perform mathematical functions and comparisons on values. Inputs Input #1 is a number and is the first value to be added. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_ceil Ceiling Node This node rounds-up any numeric value to the next highest integer. Unlike Round (which rounds to the nearest integer), this node always goes to the next highest. This node is used in all modules and is one of the math nodes. Inputs Input #1 is a number anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_condition Condition Node This node checks to see if a mathematical condition has been met when comparing two inputs. It performs simple tests, such as... * Equal To * Not Equal To * Greater Than * Less Than, etc. This node is used in all modules and is one of the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_div Division Node This node divides the first input by the second input. This node is available in all modules. This is part of the Math nodes, designed to perform mathematical functions and comparisons on values. Inputs Input #1 is a number and is the numerator - the number at the top of the expression. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_floor Floor Node This node rounds-down any numeric value to the previous/lowest integer. Unlike Round (which rounds to the nearest integer), this node always goes to the previous/lower integer. This node is used in all modules and is one of the math nodes. Inputs Input #1 anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_mult Multiplication Node This node multiplies the two input values by each-other. This node is available in all modules. This is part of the Math nodes, designed to perform mathematical functions and comparisons on values. Inputs Input #1 is a number and is the first value to be multiplied. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_round Round Node This node outputs the current value of an single ARDI property on a specific ARDI asset. This node is used in all modules and is one of the math nodes. Inputs Input #1 is a number that will be rounded. Outputs Output #1 is the rounded, integer version of the number. Note that the 'Round' function will round up any value equal to 0.5 or higher. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:math_sub Sub Node This node subtracts the two input values from one-another. This node is available in all modules. This is part of the Math nodes, designed to perform mathematical functions and comparisons on values. Inputs Input #1 is a number and is the value you want to start with. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_calculation Calculation Module The Calculation analytic module is one of the simplest modules in the ARDI Visual Analytics system. It simply returns a value (or values) calculated over time. ---------- Note: This module is generally used for practise using the ARDI visual analytic system, rather than for genuine production results. It isn't as efficient as performing the calculation live in your system, in your historian, or in tools like anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_control Control Module The Control module is used to perform simple tests to see if an asset is either In Control (near the expected values) or Out Of Control (outside the expected values). It is very similar to the Limit module, except for the fact that the Control module takes a single anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_controldetail Detailed Control Module The Detailed Control module is a more complex version of the basic control module. Where the basic module is simply used to determine if the system is out of control, this version provides detailed analytics of every control event, including anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_count Count Module The Count analytic module is used to totalise a value or count events, resetting the counter based on a specific 'pivot'. For example, you might want to calculate the total amount of product made per day. They're often used for analysing production based on periods of time, such as anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_event Event Detection Module The Event Detection analytic module is used to spot time-windows where specific conditions are met. It returns a list of events, including the time it started and ended. Starting Out When you first create a new event detector, you'll see the graph below anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_limits Limit Module The Limit module is used to perform simple tests to see if an asset is either Inside or Outside the expected operating limits of the machine. It is very similar to the Control module, except for the fact that the Control module takes a single target anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_linetracking Line Tracking Module The Line Tracking analytic module is used to track the progress of a product, batch start, fault or other point of interest along a moving path through your system. It has significant benefits in applications such as production lines and conveyors anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_oee OEE Module The OEE module is part of the ARDI Visual Analytics system, and is used to determine how a particular machine, subsystem or section has been utilised. As well as providing a breakdown of performance, it calculates a single number for Overall Equipment Effectiveness anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_outage Outage Reporting Module The Outage Reporting module is part of the ARDI Visual Analytics system, and is used to determine how a particular machine, subsystem or section has been utilised and why outages might have happened.. It's very similar in design to the OEE module. However, the outage reporting module doesn't provide an OEE figure, but it instead offers the ability to do some simple analysis of anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_pivot Pivot Module The Pivot analytic module is used to view one or more properties based on a specific 'pivot' - such as a different property or events. They're often used for analysing production based on a systems mode, product, batch, shift/crew, position, or a range of other criteria. They can also be helpful when analysing loading, filling or other product transfer operations. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_python Python Module The Python module is used to call a Python script to process the results of your logic. The analytic performs the following steps... * The analytic is run over the requested time range, writing data to one or more Python Output nodes. * The python script is called, with a JSON-encoded list of values that contain the time of each sample and a value for each of the Python Output nodes in the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:module_sheartracking Shear Tracking Module The Shear Tracking module is targeted specifically at longwall mining applications, where it is used to monitor the movement of the shearer and convert that into a list of cutting passes, known as shears. Starting Out When you first create a new Shear Tracking analytic, you'll see the graph below anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:node_programming Node Programming Node or Flow-based programming is a way to create simple expressions and logic by connecting individual instructions (called nodes) together in what is called a node graph. The name 'flow' programming comes from the fact that values travel between the nodes through connections that can be thought of as if they were pipes - carrying data from the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:node_tree Node Categories The different types of node are broken up into categories, helping to organise them into a structure so that the node you want is easier to find. Certain modules also have their own nodes - these are covered in the module documentation. The common nodes categories include anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:oee_classify Classify Node This node is used in OEE and Outage modules. It's used to mark the current machine condition. Inputs Active (Input #1) is a true or false value. When true, the machine is in the given state. Outputs Outage (Output #1) is only available on OEE analytics. The output allows you to connect this node to a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:oee_runtime Runtime Node This node is used in only in the OEE module. It's used to indicate if the current machine state should add to the OEE percentage. Inputs Active (Input #1) is a true or false value. When true, any time spent in this state is considered 'acceptable' and is added to OEE. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:pivot_diff Difference Node This node is a final outout of a pivot analytic. It selects a value that you want to use in your pivot. A key distinction is that it's used when you want to measure the difference in a value between when the pivot began and when the pivot finished. This is very useful if you're trying to capture how much of the value was transferred between A and B. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:pivot_ignore Pivot Ignore This node is a final outout node that chooses what values to ignore when creating a pivot analytic.. For example, if you'd like to not include any times where your system was powered down, you could collect a power-meter value to the Ignore node, that is anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:pivot_output Pivot Output This node is a final outout node that chooses what values you're looking at in a pivot analytic. For example, if you'd like to see your power usage based on the day of the week, your 'day of the week' value would connect to your Pivot node, and the power usage would connect to anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:pivot_pivot Pivot Node This node is a final outout node that chooses how you'd like to pivot/split your data in a pivot analytic. This node is used in only in Pivot analytics. Inputs Input #1 is a number or string that will be used to pivot your analytic. For example, if the input is fed a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:pivot_timers Using Timers To Allow Values to Stabilise In some cases, values can take a while to stabilise after an abrupt change. A quick and easy way to ignore some of these instabilities is to use a timer to create a window of time where your analytic will ignore issues. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:python_output Python Output Node This node is a final output node that is used only in Python analytics. It delivers the incoming value to your Python script. Inputs Input #1 is a number or a string and is the value you want to write to Python. Title The title of the node is the name of the property that will be written. For example, if the Python script has an input named anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:python_settings Python Script Node This node is a node that is used only in Python analytics. It's used to specify the file name of your Python script. Options The node has a filename option - this should be the servers path to the Python script you want to run. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:python_special_comments Python Analytic Special Comments There are a few special comments you can add to your Python file that tell the Python analytic module about the script. Choosing Inputs The analytic looks for a '#' followed by a '+' to indicate some analytic information. For example, if your script wants a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:python_writing_the_script Writing the Python Script The script you can uses with the Python module converts an incoming JSON file that is created from your graph, to an outgoing JSON file that is delivered to the user. This 'transformation' can be anything - from a simple calculation to a complete Machine Learning analysis. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:sample Samples The graph you make in a Visual Analytic is rarely only run once. When being used on live or historical data, it will be run many times - each time with different data and a different timestamp. This means that there will be small spaces in time between each time your graph is 'run'. This is called the anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:sheartrack_tracking Tracking Node This node is exclusive to the Shear Tracking module. It's the final output module for shear tracking - it takes your current shearer position, cutting details and key properties of your wall to make a shear tracking table and event source. Inputs Value (Input #1) anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:start ARDI Visual Analytics The Visual Analytics addon to ARDI has been built to give you the power to create analytics powered by your data and your logic, without writing any code. It uses Node Programming to let you define your own control, process and business logic in a range of pre-made anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:synchronised_reporting Synchronised Reporting Synchronised Reporting is largely used when wanting to look into quality. In process lines and conveyor systems, things don't all happen at once. If you're making snacks on a production line, the cookie you put on the line at 9:00 takes its time to work through the ovens and doesn't reach the packaging machine until 10:22. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:timing_clock Clock Node This is a timing node. It outputs a single piece of information about the current time. This node is available in all modules. Outputs Output #1 is a number. This will be a single piece of information about the current time, such as the hour or minute anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:timing_diff Time Difference Node This is a timing node. It outputs the total amount of time since a specified date and time. It's most often used in Pivot and Counter analytics, although it can also be used in others. This node is available in all modules. Outputs Output #1 is a anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:timing_elapsed Elapsed Node This is a timing node. It outputs the total amount of time in seconds since the last sample. While the Analytic Engine usually works at one-second resolution, your data might not be available at that resolution, or someone may choose to manually run the analytic at a different resolution. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:timing_timer Timer Node This node acts as a timer. It's often used to give your measurements time to stabilise after a change in how your machinery is operating. This node is used in all modules and is one of the timing nodes. The way this node operates has a lot to do with its options - a more detailed explaination of how you can use Timer nodes is shown further below. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:tracking_hotspot Tracking Hotspots The Line Tracking analytic uses hotspots. A hotspot is a single point on your line that is then tracked along the path of your graph. For each hotspot, you get a list of the assets in the line, and the time that the hotspot passes by each one. Adding a new hotspot to your line is called anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:tutorials Visual Analytic Tutorials These tutorials are sorted by module. Calculations Calculating Area, Weight & Tonnage-Per-Hour Counters Daily totals from a machine counter Count the number of times a machine changed state Calculate the energy used for each shift Events Simple Event Detection Advanced Detection with Variables and Timing Pivots Pivoting on a Mode, Status or Other Discrete Values Pivoting on a Size, Style or Other Analogue Value Pivoting on Shifts, Crews or Events … anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:variable_dec Decrement Variable Node This is a variable node, used to decrease the value of a numeric variable. These are usually used to count changes, totalise values, or along with the Elapsed timing node to create a custom timer. This node is used in all modules. Inputs Value (Input #1) anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:variable_get Get Variable Node This is a variable node, used to retrieve the value of a variable. If the value hasn't been previously written to by any of the other variable nodes, the resulting output will be 0. This node is used in all modules. Outputs Output #1 is a number anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:variable_inc Increment Variable Node This is a variable node, used to increase the value of a numeric variable. These are usually used to count changes, totalise values, or along with the Elapsed timing node to create a custom timer. This node is used in all modules. Inputs Value (Input #1) anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000 http://docs.optrix.com.au/visan:variables_set Set Variable Node This is a variable node, used to set the value of the variable to a specific number. This is most often used when you want compare the value later, or you want to reset a counter you've created using the Increment node. This node is used in all modules. anonymous@undisclosed.example.com (Anonymous) Thu, 18 Dec 2025 22:50:17 +0000