Administration Manual 3.6

 

 enVision 3.6 Admin Manual rev 1.21 (3).pdf

 

 

 



enVision Administration Manual V 3.6











< Click the image to the left to open a PDF on a web page.

 To go to the enVision Administration Manual V3.6 in Sectional Form CLICK HERE

 


Table of Contents



 


Sectional Quick Jump

 

    


What’s New

New link to the Admin Menu Overview video.

 

 

 


More Information

 Administration Documents

 


Introduction

Overview

This document is intended to provide basic guidelines when it comes to entering descriptions and expressions for an Envision project. This applies whether the project is initially entered in an Excel spreadsheet that is later used to copy and paste the descriptors/expressions to Envision or typing the information into the Envision application directly.

Under a typical FIS, you would be limited to see when a cycle has started and stopped through the cycle time.  In between the start and stop of a station, maybe many functions and process that are happening during the cycle.  They have a routine rhythm that can be tracked, but they are not. The FIS monitors the time from start to stop.  It does not monitor the actual processes going on in between.

With ENVISION, it is possible to monitor the actual processes within a cycle.  Cycle time is measured along with all the processes and operations in the cycle.

Each process within a station can be closely monitored to see if it is taking longer or shorter to complete. A single process within a cycle has a baseline that is set initially. If the operation takes longer than expected, it is recorded and shown visually to show you where, when, and how long it took to complete. With the ability to set tolerances on a specific operation, the operation would be labeled Good, Watch, Warning, or even Faulted.

The Operation within the cycle can be displayed in many forms. A column graph that shows the actual cycle time. When a cycle takes longer than the tolerance allows, it will turn from Green (Good) to Yellow (Watch), Orange (Warning), or possibly Red (Fault).

A Bar chart would show the cycle length as well as the time between cycles (Dark area between).  It can also be shown in a Sequence view. This would display the operations of the cycle in a sequence of when they happened.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Admin Module

Click on the Admin button on the top right-hand side of the menu bar.

Slide the cursor over to the left-hand edge of the window until the side menu appears.

This action will open a side display menu.

   

 

 

See Admin Menu Overview video for a brief description of the uses and functions of the Admin Browsers Administrators Side Menu.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 




Factory Tree

Overview

This document is intended to provide basic guidelines when it comes to entering descriptions and expressions for an Envision project. This applies whether the project is initially entered in an Excel spreadsheet that is later used to copy and paste the descriptors/expressions to Envision or typing the information into the Envision application directly.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Factory window

The basic structure of an Envision application and their suggested descriptor lengths.

Object tree -

  1. Highest level referred to as the "

Plant" - try to keep between 5 and 15 characters - no more than 20.

  1. Next level (or 'Child') under Plant is the "

Area" – it can be more than 1 - same punctuation rules as Plant

  1. Next level under Area is the "

Line" - it can be more than 1 - no more than 20 characters.

  1. Next level under Line is the "

Station" - it can be more than 1 - try to keep around 10 characters

  1. Next level under Station is the "

Asset" - it can be more than 1 - same punctuation rules as plant

  1. Next level under Asset is the "

Group" - it can be more than 1 - no more than 20 characters

  1. Next level, (the last one) under Group is the "

OP" - at least 1 but no more than 16 for any one Group - no more than 29 characters

Use a mixture of upper and lower case letters. This will help in interpreting abbreviations. Lower case letters also seem to use less screen area than upper case letters. Try to use logical abbreviations as much as possible.

Obviously, there will sometimes be exceptions to these guidelines. Also, some customers use different terminologies for their processes such as using "OP ##" instead of "STA ##", etc. These need to be treated in a case by case scenario.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Object Naming

Factory (PLANT) 

The Factory/Plant Object can be named after the Customer Name (Or Accepted Abbreviation) or Plant Name (Or Accepted Abbreviation). It is the highest-level object. 

When naming, keep it between 5 and 15 characters - no more than 20.

Area

The Area Object is a Customer Designated Area, such as a Bodyside, Door, Transmission, or other large parts of a whole product. The Area Object is the “Child' under the Plant object.

When naming the Area Object, there can be more than one Area Object per Plant, follow the same character limits as the Plant. Example Bodyshop and Closures.

Line

The Line Object is a Customer Designated Line Segment and Style of Station range, such as a 6X S010 or 6X S010-S050 (if there are multiple stations in one or more of the Line Objects). The Line Object is the “Child' under the Area object.

When naming the Line Object, it can be more than 1 - no more than 20 characters, stating a segment and a range of station (element) in the Line.

Station

The Station Objects are Customer Designated Station number, usually about the 2nd part of the Line Objects name (aka S020 which is part of the 6X S010-S050 Line Object or S010, S020, S030, S040, and S050). The Station Object is the “Child” under the Line object.

When naming the Station Object, there can be more than 1, to try to keep it around 10 characters.

Asset

The Asset Objects are Customer Designated Asset Name and a description of the type. It consists of Main Stations, Robot Stations, and Fixture Stations. Main Stations, are Customer Designated Station Number. Robots are Numbers, Robot numbers, and descriptions. A Fixture is a station number. The Asset Object is the “Child” under the Station object.

When naming the Asset Objects, there can be more than one Asset Object per Plant, try to keep it under 10 characters.

Group

The Group Objects are Tooling Group – [Unit Type] [Unit Type Number# ][Unit Type Motion] Model Abbreviation. The Group Object is the “Child' under the Asset object. There can be several Group objects, so use no more than 20 characters.

 

OPS

The OPS or Operations objects are the “Child” objects of the Group Object. There may be at least 1 but no more than 16 for any one Group – use no more than 29 characters when naming the OPS. The naming of a Tooling Group OP typically consists of a Unit Type Abbreviation, a Unit Number, and a Unit Type Position Abbreviation.

 

 

 


Object Overview

Factory

WTM A / BODYSHOP/ 6X_S010_050 / S020/ S020FX1 / ADV PIN 1 / PIN 1 ADVD

The FACTORY for this example is the fictional Willison Truck Manufacturing (WT Mfg.). They make several versions of trucks. In this example, there are two factory locations, Arizona and Utah.

Selecting a Factory name could use the initials of the company name and the location if there are multiple sites.

WTM A (Willison Truck Manufacturing) + A (Arizona). WTM A.

WTM U for the Utah Factory.

Area

WTM A / BODYSHOP/ 6X_S010_050 / S020/ S020FX1 / ADV PIN 1 / PIN 1 ADVD

In this factory, the manufacturer will have several areas that could be monitored. The Areas would be separated by the types or parts of a product they produce, such as Bodysides, Framing, Painting, Bodyshop, etc. For this, we would specify a particular AREA.

Bodyshop

Bodyside

Framing

Line

WTM A /BODYSHOP/ 6X_S010_050 / S020 / S020FX1 / ADV PIN 1 / PIN 1 ADVD

In the Bodyshop AREA, they may have multiple LINES. Each LINE has an abbreviated designation for them and the STATION or STATIONS in the LINE Name. If a line has two or more STATIONS within the LINE, you would want to use the LINE Number (6X) + the STATIONS (S010_050) included in that LINE. Note the examples below.

BA010_050

6X_S010_050  (this line has multiple stations)

UBODY_C01 (this LINE has only one station)

Station

WTM A / BODYSHOP/ 6X_S010_050 / S020 / S020FX1 / ADV PIN 1 / PIN 1 ADVD

The STATIONS are the Child objects located in each LINE Object. Within the 6X S010-S050, there would typically be 5 (S010, S020, S030, etc.) stations in each LINE Object:

S010, S020, S030, S040, S050

Asset

WTM A / BODYSHOP/ 6X_S010_050 / S020 / S020FX1 / ADV PIN 1 / PIN 1 ADVD

The ASSET Object naming is a combination of the Station Name + Type of station it is (Main, Fixture, or Robot). You would name as follows:

S020FX1 (Station Name (S020)+ Fixture(FX) + Number(1)

Group

WTM A / BODYSHOP/ 6X_S010_050 / S020 / S020FX1 / ADV PIN 1 / PIN 1 ADVD

Group Object naming is typically made up of 2 group types (Tooling and Robot Motions) and 3 descriptors (Unit Type Motion, Unit Type, and Unit Type Number).

Tooling Group

(Example - ADV PIN 1 [Unit Type Motion] + [Unit Type] + [Unit Type Number#]



Unit Type Motions: 

ADVANCE       RETRACT           EXTEND

RETURN          ENGAGE            RAISE

CLOSE            DISENGAGE      RETRACT

OPEN               LOWER

Unit Types:

PIN              BACKUP

CLAMP        VACUUM

DUMP         PIVOT

SLIDE

Unit Type Numbers: 

1, 2, 3, etc., dependent on how many of the type that is present in the group.

 



Robot Motion Group:



GO TO” Work Type Position:

POUNCE

PICK

DROP

1ST RIVET/FDS 2ND, LAST

PEDESTAL

MOVE” Work Type Position

CLEAR OF PICK

CLEAR OF DROP

CLEAR OF PED

CLEAR OF FIXTURE

HOME



OPS

WTM A / Bodyshop / 6X_S010_050 / S020/ S020FX1 / ADV PIN 1 / PIN 1 ADVD

Tooling Group OP

The naming of a Tooling Group OP typically consists of a Unit Type Abbreviation, a Unit Number, and a Unit Type Position Abbreviation. The full spelling can be used, however, if the OP has a long descriptor, it may be advisable, to use an abbreviation.



Unit Type Abbreviation:

PIN (Pin)

CLP (Clamp)

DMP (Dump)

SLD (Slide)

BKUP (Back-Up)

VAC (Vacuum)

PVT (Pivot)



Unit Type Number:

1, 2, 3, etc. Depending on the amount of the same Ops that a present.



PIN 1 ADVANCED

PIN 1 ADVD





Unit Type Position Abbreviation:

Advanced = ADVD

Returned = RETD

Closed = CLSD

Opened = OPND

Extended = EXTD

Retracted = RTCD

Engaged = ENGD

Disengage = DSNG

Lowered = LWRD

Raised = RSD





 

Robot Motion OP

The OP also uses Robot Motions stated as Work Type Position in the naming. These are “AT” and “CLEAR OF”.





AT consists of:

POUNCE

PICK

DROP

1ST RIVET/FDS 2nd LAST

PEDESTAL

HOME

AT POUNCE

CLEAR OF consists of:

PICK

DROP

PED

FIXTURE

 

 

CLEAR OF FXT















WTM A / Bodyshop / 6X_S010_050 / S020/ S020FX1 / ADV PIN 1 / PIN 1 ADVD



 

 

 


Objects and Relationships

Factory Window | Building a Factory Tree | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

Overview

From the Object and Relationships menu, you can view or create a Factory tree, as well as define the Op Tags. It is where you can create the structure that represents the plant of the manufacturing process. From there you can lay out how you want to collect the data as well as where you can set up all the information for collecting data.



 

Move the cursor to the left-hand side of the screen to open the Admin Menu Tab. From there, select Objects and Relationships to open the Factory window.

 

Once the Factory window is open, select the Plant Object and another window will reveal to the right. From that window, you have access to the Edit Select-Object and Add New Child Tabs. The Edit Select Tab is for Adding, Delete, or Editing the object selected. The Add New Child tab, adds a new object below the current object selected. If you selected a Plant level object, clicking the Add New Child Object will add an Area level object.

 

The PLC and System tabs can expand to show other sub-tabs to choose from.  The PLC tab has Channels and Devices. The System tab contains the sub-tabs for System Configuration, Audit, and Application Logs.

 

 

 

 

 

 

 

 


Building a Factory Tree

Factory Window | Objects and Relationships | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

From the Envision Admin Browser, you can select a recent project if it is listed below.

To start a new Factory Tree project, select the Factory button above the selection window. This will open an Add Plant Window. From there, input the name that you would like to represent your company or plant.  After the name is inputted, click the  Save button to create your new Factory.

After the Plant Object is saved, this next screen will appear. The Plant object is in the Factory window. To the right of the Factory Window is the Editing window. Here you can use the Edit Select-Object tab to edit the Name, Description, and control where it is displayed (such as Visibility).













There is also a tab fo­r   Add New Child Object.  This will add the levels below the Plant, down to the Group objects.  In this tab, you name the (Area) Object and its description.  You can use the Description area to add pertinent information about the object if needed.













When the Name and Description are filled out, you now can save by clicking the  Save button. This will add the (Area) object under the (Plant) Object.

 

 After clicking  Save, this window will appears showing the new AREA Forward at the next level below the Plant Object (AMTTest1). This step can be repeated to all levels down to the Asset and Group Level objects.

In the Asset level, the editing window, with the "Edit Selected Object" tab to the right now reveals the PLC Device edit box.  At the Asset level, you are required to assign a PLC Device to that Object. Click on the pull-down to reveal the choices of PLC Devices available to use.

 

Definition of Asset, Group, and OP objects

 

Assets

Assets are used to define a repeatable set of motions/activities (Groups) that have defined Start and End signals. Each occurrence is referred to as a "cycle" and is represented by a bar in the Cycle View history window. The number of Assets for a specific Station is completely dependent on the process and how the product transfers in and out of the station. For analysis and report features the following objects should be defined as unique Assets:

Overall Station Asset

This shows how the individual sub-Assets contained in the Station performed in relation to each other. This Asset can also have other Groups for individual motions that are independent of the sub-Assets such as the transfer of parts into and out of the station and tooling motions that are part of the overall Station sequence. In addition, this Asset might also have groups that represent an overview of other sub-assets that perform work during this Assets cycle. Examples include an operator group, robot groups, and a summary sub-asset.

Operator Asset

Each Station that requires a physical operator to enter a light screen protected area to perform some activity for every cycle is considered a unique Asset. If 2 operators share the same light screen area they will share the Asset. They can have separate groups for their Operator PB (Push Button) if they each have their own PB. If there is no light screen for each cycle an operator must acknowledge that they have performed some prescribed activity by pressing a PB for a cycle to continue, then a separate Asset will be required for that operator ONLY if there is a clearly defined signal that can be used to Start the Asset (example: Part in Pos - Rdy For Oper).

Robot Asset

Each robot will be a separate Asset. This is recommended not only because robots have considerable detail themselves and could cause an Overall Station Asset to become cluttered, but Robots may have processes that run outside of the Overall Station Asset’s cycle. (e.g. Tip Dress, Cap Change, Magazine Fill)

Summary Asset

A summary asset can be used in situations where there is a high-density Overall Station Asset or when there is a tool change that can have considerable sequence changes. This asset is generally used to combine large tooling fixtures into smaller summary groups in the overall asset but maintains the level of detail desired in a separate sub-asset. Some examples could include changeable framing gates, fixtures mounted on tool-trays, or even high unit count fixtures mounted on pallet transfer systems.



 

Asset States

Asset States are used to flag important periods in a cycle and can also be used for reporting purposes.

Auto – Used to indicate when the machine is currently in automatic production mode. This state can be concurrently active with other machine states.

Faulted - Used to denote there is an active machine fault, and the cycle will not be used to calculate averages for reporting purposes. This state can be concurrently active with other machine states.

Blocked – Used to indicate when an Asset has reached a point of work complete, but cannot progress further due to a downstream blockage. This state can be concurrently active with other machine states.

Starved – Used to indicate when an Asset is ready to receive and start the next cycle, but an upstream condition is preventing advancement. This state can be concurrently active with other machine states.

Non-Production – Used to indicate Planned Downtime. While this state can be active concurrently with other states, it is recommended to the sole active state for reporting and tracking purposes.

Additional notes

All Part Present sensors should be monitored. Quite often it is a part present that causes a cycle to go over. We need to show this situation as clearly as possible. The Envision PLC drivers have the ability to track the pattern of a part present going on and off during a cycle if it is desired to monitor this activity. This may come in very handy when trying to monitor operator part-load efficiency.

All operator light screens need to be monitored. The Envision PLC software driver has the ability to capture the on and off status of light screen interruption as long as the appropriate signal from the light screen is wired to an input.

Special Case Cycles

There are situations when a cycle can have an abnormal process; this can be in the form of an alternate path—when the Asset uses a limited number of different groups or Ops while retaining the original CycleTime—or an outside influence that causes an expected change in performance. For the cases involving an alternate path, it is suggested to distinguish these cycles by using a different Model.  If the alternate path is minor, or the use of a distinct MODEL is not preferred, it is also possible to have a GROUP with two Ops to denote the path options; to do this correctly, when one path is taken, the OP designating the unused path must be recorded with a zero-duration timestamp otherwise a purple, missing data record will be generated.  When there is the possibility for an outside influence, the usage of STATE identifiers is suggested to be used flagging the cycles to be ignored, or processed separately, for average cycle time calculations.

              Possible Special Cases:

  • Model Changeover with Tool Change—STATE FLAG

  • Runout—STATE FLAG

  • Processes with possible alternate paths

    • Pull-off & Swap—MODEL

    • MH Robot with an alternate Pick/Drop Locations—MODEL/2 OP w/ zero duration

    • MH Robot with an alternate Work Pedestal—MODEL/2 OP w/ zero duration

 



 

Groups

Assets are a collection of Groups that describe a sequence of events that comprise one complete cycle for the Asset. The first Group for every Asset is called the CYCLE TIME Group and is created automatically when the Asset is created. This Group is used to control the overall Start and Stop of the Asset. All other Groups that are added to describe the sequence for the Asset should have their Start and Stop signals occur between the Start and Stop of the CYCLE TIME Group. In most situations, the CYCLE TIME Group Start signal is the same signal used for the Group Start signal that describes the first step of the sequence. A Group is comprised of a START signal, a STOP signal, and 1 to 16 OP signals. There are also placeholders for a Fault signal and a Blocked signal for each Group which is used in special cases that we will not discuss here.



START signal

 

The START signal is used to indicate that the step has been initiated. Solenoid valves, robot initiate, operator clear to enter, etc. are examples of common Start signals. The START signal is a retentive signal and goes true upon the first OFF à ON transition. It is not reset until the Group STOP signal goes true. The Envision PLC driver stores the current Timestamp during the scan that the transition is detected.



STOP signal

 

The STOP signal is used to reset the Group and clear all retentive signals and memory bits in the PLC driver that are associated with that Group. The only Group that MUST have an expression entered for its STOP signal is the CYCLE TIME Group. This STOP signal has special meaning to the Envision application. It turns on the Asset Stop signal inside the PLC driver that indicates to Envision that an Asset has completed a cycle and that all the data captured by the application since the Start of the Asset can be processed and stored as historical data. All Groups other than the CYCLE TIME Group have the option of leaving the STOP signal blank. The Deploy function that generates the PLC driver logic is designed to automatically use the Asset Stop signal to fill in any Group STOP signal that is left blank. It is strongly recommended to leave Group STOP signals blank IF the Group is expected to occur only once per cycle. This ensures that all Groups get reset at the end of a cycle.

There are a couple of exceptions touched upon earlier where it may be desirable to capture multiple occurrences of a Group during one cycle of an Asset such as monitoring how many times an operator moves in and out of a light screen and the gaps between each occurrence. For this scenario, it is necessary to enter an expression for the STOP signal to reset the Group before the cycle ends.



OP signals

 

The OP signals are the expected results (inputs) for the Group. They should be edited to describe the specific input they represent. There can be 1 OP signal or up to as many as 16 OP signals for anyone Group. The START signal is used to represent the beginning of a sequence step. When all the OP signals for a Group have activated, this indicates that the sequence step is complete. Like the START signal, OP signals are retentive and go true upon the first OFF à ON transition for each OP independently AFTER the START signal has gone true. OP signals are ignored until the Group has been Started. They are not reset until the Group STOP signal goes true. A Group is considered as Running once the START signal goes true up until all the OP signals for the Group have gone true. The Group will not be able to START again until the Group STOP signal has gone true.

 



 

Examples:

  • Overall Station Asset

    • Pallet Transfer Stations

      • CycleTime

      • Transfer In

      • Tooling to Clear to Lower Position (One group per pneumatic valve/Summary sub-asset Group)

      • Read RFID

      • Lifter Lower

      • Part Presents

      • Tooling to Work Position (One group per pneumatic valve/Summary sub-asset Group)

      • Robots Work

      • Tooling to Clear to Raise Position (One group per pneumatic valve/Summary sub-asset Group)

      • Lifter Raise

      • Transfer Out

    • Tooling Fixture Stations

      • CycleTime

      • Tooling Reset to Clear to Load (One group per pneumatic valve/Summary sub-asset Group)

      • Operator/Robot Load Parts

      • Tooling to Work Position (One group per pneumatic valve/Summary sub-asset Group)

      • Robots Work

      • Tooling to Clear to Unload Position (One group per pneumatic valve/Summary sub-asset Group)

      • Operator/Robot Unload Parts

      • Operator Asset

        • CycleTime

        • Break LightScreen

        • Load Parts (An OP for each Part Present)

        • Press PB

      • Robot Asset

        • Carried Application

          • CycleTime

          • Go to Pounce

          • Individual work completes (e.g. 1st, 2nd, 3rd weld complete)

          • Move Clear of Fixture

          • Move Home

          • Tip Dress/Cap Change/Magazine Fill

 

  • Material Handling Application

    • CycleTime

    • Go to Pounce

    • Go to Pick

    • Part Presents

    • EOAT (One group per pneumatic valve)

    • Move clear of Pick

    • Individual work completes (e.g. 1st, 2nd, 3rd weld complete)

    • Go to Drop

    • EOAT (One group per pneumatic valve)

    • Move Clear of Drop

    • Move Home

 

Adding a Group and OPs

Below the Asset is the Group levels objects. Under the groups are the OPS, also referred to as Operations. To add another Group object:

Click on the Asset and the Editing window will open.

Click on the Add New Child Object (Group) A20.

Input “Move to Pounce” in the name field.

Click the  Save button when finished.

The A20 Asset should update to know to have the Move to Pounce Group object. The OP “OP1” needs to be renamed to reflect the process properly.







 

 

 

Select the OP1 OP, then select the “Edit Selected Object” tab located on the right side of the page. Delete OP1 from the name field and replace it with “At Pounce”. Click  Save.

REMEMBER to Double-check to be sure that you now have a properly labeled project from the Asset to the OP.

 

 

 

 

START signal

START is used to indicate that the step has been initiated. Solenoid valves, robot initiate, operator clear to enter, etc. are examples of common Start signals. The START signal is a retentive signal and goes true upon the first OFF à ON transition. It is not reset until the Group STOP signal goes true. The Envision PLC driver stores the current Timestamp during the scan that the transition is detected.

STOP signal

STOP is used to reset the Group and clear all retentive signals and memory bits in the PLC driver that are associated with that Group. The only Group that MUST have an expression entered for its STOP signal is the CYCLE TIME Group. This STOP signal has special meaning to the Envision application. It turns on the Asset Stop signal inside the PLC driver that indicates to Envision that an Asset has completed a cycle and that all the data captured by the application since the Start of the Asset can be processed and stored as historical data. All Groups other than the CYCLE TIME Group have the option of leaving the STOP signal blank. The Deploy function that generates the PLC driver logic is designed to automatically use the Asset Stop signal to fill in any Group STOP signal that is left blank. It is strongly recommended to leave Group STOP signals blank IF the Group is expected to occur only once per cycle. This ensures that all Groups get reset at the end of a cycle.

There are a few exceptions discussed earlier where it may be desirable to capture multiple occurrences of a Group during one cycle of an Asset such as monitoring how many times an operator moves in and out of a light screen and the gaps between each occurrence. For this scenario, it is necessary to enter an expression for the STOP signal in order for the Group to reset before the cycle ends.



 

 

 

 







OP signals

OP signals are the expected results (inputs) for the Group. They should be edited to describe the specific input they represent. There can be 1 OP signal or up to as many as 16 OP signals for a single Group. The START signal is used to represent the beginning of a sequence step. When all the OP signals for a Group have gone true this indicates that the sequence step is complete. Similar to the START signal, OP signals are retentive and go true upon the first OFF à ON transition for each OP independently AFTER the START signal has gone true. OP signals are ignored until the Group has been Started. They are not reset until the Group STOP signal goes true. A Group is considered as Running once the START signal goes true up until all the OP signals for the Group have gone true. The Group will not be able to START again until the Group STOP signal has gone true.

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Importing

Factory Window | Building a Factory Tree | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

The Import button is used to install an.enx file or Import SeqOfOp.json file. 

 

Importing.enx file

Click on the object you would like to import to.  Click the Import button and the Import window will open.

Select the “Choose file” button to open and search for the folder that contains the.enx file. 

 

 

 

 





 

Select the Import as Library option. Click the  Upload_    button to start the download.

NOTE: There is no progress bar.  The upload should take about 30 seconds.

 

 

 

 

 

 

 

 

 

 

 

 

 

Importing SeqOfOp.json file

Factory Window | Building a Factory Tree | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

This process is done starting at the LINE level. At that level, is the only time that will allow you to import a.json file.

Before you select the  Import button, it may be necessary to create a.json file.  Navigate to the SeqOfOp.xls file that contains the data needed to build the Factory Tree.

Open this configuration file. To the far right is the Create File button. Select it to start the building of the Factory Tree.

Select the LINE level object. Click the   Import button and the Import window will open. Select the Choose File button to find and select the.json file.

Navigate to find the.json file that was created from the.xls file with all the information for ASSET level objects and below. Select Open, and this will fill in the Select.json file edit box in the Import window.











Click the Upload button to the build Import relationship tree.

A “ Building import relationship tree…” screen will appear. When it is finished, it will open a preview window.

After the Factory Tree preview is ready, an   Import – Configuration tree window will open. Review the projected Factory Tree. Check that all the ASSETS and GROUPS are there. Click the   Accept button if you would like to proceed.









After the Factory Tree structure is created, it is necessary to select the PLC for the Objects selected.  Use the pull-down menu to select the correct PLC Device.

 

 

 

 

 

 

 

 

 

 


Deploy

The Deploy button is used when everything is set up completely or a change has been made and is ready to be installed into Envision.

NOTE: BEFORE you Deploy make sure you have done all of the following:

Assigned each Asset a PLC

Inputted baseline values

Inputted values for TAGS (Blocked, Starved, Manual, etc.)





The deployment may take some time to complete. You will be prompted when it's finished.

When the Deploy finishes successfully, you will see a zip file created in your computer's Downloads folder. It will have the name of EnvisionDeployResult (##).zip where ## is a number to distinguish between multiple Deploy files. Unzip the folder to view the contents.

Inside each folder, you will find an L5X file that will need to be imported to the associated PLC along with a text file that contains the instructions for this task. If there is a ConfigTree.CSV file that is in the folder, it can be ignored. 

 












Exporting

Factory Window | Building a Factory Tree | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

The Export button is a feature that allows you to export an object from a Plant level to a Group level. First, select the object you would like to Export (e.g.  1AREA Forward ). Now select the Export button. A green Notice window will open, showing that the Export has been initiated. A few moments later, a download dialog window will open on the lower left-hand side of the browser window. Select open to view the.enx file or view it in the Downloads folder.

 

 

 

 

Configurations

Factory Window | Building a Factory Tree | Adding a Group or OPs | Start/Stop Signals | OPS Signals | Importing | Exporting | Configuration

In the event of new installations, it may be needed that the Parameters used in the PLC may require a modification or a change to make it function correctly. For that, there is the blue  @ Config button. The Config button is used to add Parameters for the Device section of the PLC. First, select the  @ Config button on the upper right side of the browser window. An Object Configuration window will appear. Input the Parameter (name) and the Value for the created parameter. Then click the Add button.

Go to the side menu and select Devices under the PLC tab. This will open the PLC Device page, which will list all the PLC Devices that are in the system currently. To view the created parameter, click on the   Config button to open a window of the parameter for the selected PLC Device.

Sometimes an installed PLC device needs to have modified parameters to work correctly or to be tuned to the PLC. To make changes or modify a parameter you can use the! Edit button.











Click the Edit button to open the Device Config. Window.

That will open an editing box for the parameter that has been selected. You can now make a change to the parameter to fine-tune the parameter for a specific PLC Device.

 *

 

 

 


I/O Expressions

 Code Explanation

 

AssetStart

This bit is handled by the Cycle Time Group AOI (Add-On Instructions) and acts as an echo of the Cycle Time Group Start.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetStart bit in the same PLC scan (only in the cases where AssetStart is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the transitions of the AssetStart bit.     

AssetStarted                     

This bit is handled by the Cycle Time Group AOI, and it is turned on when an idle (stopped) group is started by the Cycle Time Group Start and turned off on the Cycle Time Group Stop.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetStarted bit in the same PLC scan (only in the cases where AssetStarted is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the transitions of the AssetStarted bit                

AssetStartOS                     

This bit is handled by the Cycle Time Group AOI, it is turned on when the Cycle Time Group goes from not started to Started, stays on for one PLC scan, and then turned off.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetStartOS bit in the same PLC scan (only in the cases where AssetStartOS is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the state of the AssetStartOS bit

AssetRunning                   

This bit is handled by the Cycle Time Group AOI, and it is turned on together with the Cycle Time Group Started bit and turned off when the Cycle Time Group Op0 is triggered.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetRunning bit in the same PLC scan (only in the cases where AssetRunning is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the transitions of the AssetRunning bit"                           

AssetDone          

This bit is handled by the Cycle Time Group AOI, and it is turned when the Cycle Time Group Op0 is triggered and turned off on the Cycle Time Group Stop.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetDone bit in the same PLC scan (only in the cases where AssetDone is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the transitions of the AssetDone bit.    

AssetStop                          

This bit is handled by the Cycle Time Group AOI and acts as an echo of the Cycle Time Group Stop.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetStop bit in the same PLC scan (only in the cases where AssetStop is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the transitions of the AssetStop bit.

 

 

AssetStopOS                     

This bit is handled by the Cycle Time Group AOI, and it is turned on when a STARTED Cycle Time Group is stopped, stays on for one PLC scan, and then turned off.

The Groups after the Cycle Time Group belonging to the same Asset will see the actual state of the AssetStopOS bit in the same PLC scan (only in the cases where AssetStopOS is used in any Group IO Expression), however, since the Asset is scanned before the Cycle Time Group, it will take one more scan for the Asset to see the state of the AssetStopOS bit                    

AssetMem                        

This bit is handled by the Asset AOI, it is turned on by the Asset SetUserMem Entry and turned off on either the AssetStop or the Asset ResetUserMem Entry.

All Groups after the Asset AOI belonging to the same Asset will see the actual state of the AssetMem bit in the same PLC scan (only in the cases where AssetMem is used in any Group IO Expression), however, if the AssetMem is used in any IO Expression of the same Asset, it will take one more scan for the AssetMem to show transitions                                                         

GroupStarted                   

This bit is handled by the Group AOI, it is turned on when an idle (stopped) group is started by the Group Start and turned off on the Group Stop.

If the GroupStarted bit is used in any IO Expression of the same Group, it will take one more scan for the GroupStarted to show transitions for those IO Expressions.                 

GroupStartOS                   

This bit is handled by the Group AOI, it is turned on when the Group goes from not started to Started, stays on for one PLC scan, and then turned off.

If the GroupStartOS bit is used in any IO Expression of the same Group, it will take one more scan for the GroupStartOS to show transitions for those IO Expressions.                

GroupRunning                  

This bit is handled by the Group AOI, it is turned on together with the Group Started bit and turned off when all the configured Ops in the Group are triggered.

If the group running bit is used in any IO Expression of the same Group, it will take one more scan for the GroupRunning to show transitions for those IO Expressions.               

GroupDone                       

This bit is handled by the Group AOI, it is turned when all the configured Ops in the Group are triggered and turned off on the Group Stop.

If the GroupDone bit is used in any IO Expression of the same Group, it will take one more scan for the GroupDone to show transitions for those IO Expressions.                    

GroupOccurCount                          

This byte is handled by the Group AOI, it counts up when on the GroupDone and reset on the AssetStopOS.

If the GroupOccurCount bit is used in any IO Expression of the same Group, it will take one more scan for the GroupOccurCount to show changes for those IO Expressions.                            

GroupStopOS                   

This bit is handled by the Group AOI, it is turned on when a STARTED Group is stopped, stays on for one PLC scan, and then turned off.

If the GroupStopOS bit is used in any IO Expression of the same Group, it will take one more scan for the GroupStopOS to show transitions for those IO Expressions."               

GroupMem                       

This bit is handled by the Group AOI, it is turned on by the Group UserMem Entry and turned off on either the GroupStop.

If the GroupMem bit is used in any IO Expression of the same Group, it will take one more scan for the GroupMem to show transitions for those IO Expressions.

Envision IO Expression Shortcuts

Asset Status bits

Shortcut (Not Case Sensitive)

Description

ASSETMEMORY   or   ASSETMEM

This is turned on by the Asset SetUserMem Entry and turned off by either the AssetStop or the Asset ResetUserMem Entry. All Groups that belong to the same Asset use the same AssetMem.

ASSETSTART

This is an echo of the CycleTime group’s START conditions. All Groups that belong to the same Asset use the same AssetStart.

ASSETSTARTOS

This is a one-time trigger set on the first OFFàON transition of the CycleTime group START following a STOP. All Groups that belong to the same Asset use the same AssetStartOS.

ASSETSTOP

This is an echo of the CycleTime group’s STOP conditions. All Groups that belong to the same Asset use the same AssetStop.

ASSETSTOPOS

This is a one-time trigger set on the first OFFàON transition of the CycleTime group STOP following a START. All Groups that belong to the same Asset use the same AssetStopOS.

ASSETSTARTED

This is turned on when an idle (stopped) Asset is started by the Cycle Time Group Start and turned off on the Cycle Time Group Stop. All Groups that belong to the same Asset use the same AssetStarted.

ASSETRUNNING

This is turned on together with AssetStarted and turned off when the Cycle Time Group Op0 is triggered. All Groups that belong to the same Asset use the same AssetRunning.

ASSETDONE

This is turned on when a STARTED Cycle Time Group Op0 is triggered and turned off on the Cycle Time Group Stop. All Groups that belong to the same Asset use the same AssetDone.

 

Group Status bits

Shortcut (Not Case Sensitive)

Description

GROUPMEMORY or GROUPMEM

This is turned on by the Group SetUserMem Entry and turned off by the GroupStop Entry

GROUPSTARTOS

This is a one-time trigger set on the first OFFàON transition of the Group START following a STOP.

GROUPSTARTED

This is turned on when an idle (stopped) group is started by the Group Start and turned off on the Group Stop.

GROUPRUNNING

This is turned on together with GroupStarted and turned off when all configured Group OPs are triggered.

GROUPDONE

This is turned on when all configured OPs of a STARTED Group are triggered and are turned off by the Group Stop.

GROUPSTOPOS

This is a one-time trigger set on the first OFFàON transition of the Group STOP following a START.

 



 

Group Tag Explanation

At the Group level, every object has a tag that can be configured to what you need it to achieve. To view and configure these Group Tags, you need to select the group object you wish to view. In the upper right-hand corner is the   Tags   Button.

The Tags: (CYCLE TIME) window will open and display the default parameters associated with that object selected. Whenever a Group object is created, these Standard Tags are automatically attached to the Group objects created.

There are more Tags available for you to utilize. Simply click on the  Show All Tags-  button, located on the lower left side of the Tags Window.















The Tags window will now update with all the available tags to be utilized as needed. The tags provided, are additional labeled Spare 4-15 and OPTRIGGER SPARES 1-16. You can also add a new Tag by selecting the + Add new record button. Fill out the parameter fields and click the update button.















The Column headers can be dragged and dropped to sort the tags by the header selected. Simply click and hold the column header, then drag it up to the column field above the headers and then release. It will now sort the tags by the selected header field. They also can be sorted by ascending or descending, by simply clicking on the Column Header icon.

 

 

 

 

 

 

 

 

 

Add New Record

If another tag needs to be created or needs to be edited, you can select a tag from the list (SPARES or OPTRIGGERS SPARES), then click the  + Add new record. The selected window will expand into an editing field to make you changes. Under the Description, input a name to represent the tag. Input the I/O expression, Tag type, and Tag Mode. If everything is set and ready, click the Update button, to save changes or  Cancel to discard changes and go back to the list. If you want to change the I/O Expression only, you can select the Edit button and the selected tag will open an editing box to make your changes. When finished, click update to Save or Cancel to discard changes.

Group Tag Definitions

START

START is used to indicate that the step has been initiated. Solenoid valves, robot initiate, operator clear to enter, etc. are examples of common Start signals. The START signal is a retentive signal and goes true upon the first OFF / ON transition. It is not reset until the Group STOP signal goes true. The Envision PLC driver stores the current Timestamp during the scan that the transition is detected.

STOP

STOP is used to reset the Group and clear all retentive signals and memory bits in the PLC driver that are associated with that Group. The only Group that MUST have an expression entered for its STOP signal is the CYCLE TIME Group. This STOP signal has special meaning to the Envision application. It turns on the Asset Stop signal inside the PLC driver that indicates to Envision that an Asset has completed a cycle and that all the data captured by the application since the Start of the Asset can be processed and stored as historical data. All Groups other than the CYCLE TIME Group have the option of leaving the STOP signal blank. The Deploy function that generates the PLC driver logic is designed to automatically use the Asset Stop signal to fill in any Group STOP signal that is left blank. It is strongly recommended to leave Group STOP signals blank IF the Group is expected to occur only once per cycle. This ensures that all Groups get reset at the end of a cycle.

 

There are a couple of exceptions touched upon earlier where it may be desirable to capture multiple occurrences of a Group during one cycle of an Asset such as monitoring how many times an operator moves in and out of a light screen and the gaps between each occurrence. For this scenario, it is necessary to enter an expression for the STOP signal in order for the Group to reset before the cycle ends.

FAULTED

The object is faulted and stops working.

BLOCKED

The object completes its work and is waiting for downstream objects to finish so the finished part can move out of the object.

CYCLETIME

Amount of time between the start and stop of an object.

SPARES (4-15)

The Spares are used to create custom Group Tags when you are required to have more than the default tags.

OPTRIGGER SPARE (1-16)

The OPTRIGGER SPARE is used to create a custom Op Trigger

 

Asset Tag Explanation   s

AUTO

The object is in a full auto or normal operation mode.

MANUAL

The Asset is running manually or being engaged for a maintenance or troubleshooting mode.

FAULTED

Tooling or Automation failure, that may require manual intervention.

BLOCKED

The Asset has finished its work and cycle, but cannot transfer its finished product to the next position.

PRIMARY STARVED

The overall time the object is in a Starved state. The object completed its job and the produced part has exited the object. The object is waiting for the next part to start working.

RUNNING

The Asset is performing its designed functionality

IDLE

The asset has done its function.

SECONDARY STARVED

The system is waiting for parts that are loaded at this asset.

INTERRUPTED

An asset cycle is interrupted due to violation of safety setup or other non-tooling and automation related stoppage.

NON-PRODUCTION

The system is not engaged or not in production. During this time, no records will be kept.

USER 01-04

SPARE 11-27

The Spares are used to create custom Asset Tags.

 

 

 

 

 


Envision Application Server (EAS)

EAS receives the data and information to display the complete data taken. It receives data from the EDC which is in contact with the PLCs.

Components of EDC

OPC Server (OLE Process Control)

Object linking and embedding (OLE) is a Microsoft technology that facilitates the sharing of application data and objects written in different formats from multiple sources. Linking establishes a connection between two objects, and embedding facilitates application data insertion.

Object Linking and Embedding (OLE) for process control (OPC) is a set of standards developed by a joint collaboration of leading automation industry suppliers. OPC's primary mission is to define a uniform interface for use with any organization or custom software package.

Makes it possible to understand and unify the communications between machines.

Agent

The Agent is a service program, that allows the EDC to talk to EAS. The EAS cannot talk to EDC directly. The agents initiate communication through the web API’s (application programming interface) to the EAS to find out what it has to do.  The Agent asks the EAS if it needs anything. If the EAS has a job to do, it tells the EDC, and the EDC will start to perform the job. If it needs more information on the job, it will ask the EAS for the necessary information (such as deployment). When asked by the EDC, the EAS will say it needs to deploy, so the agent executes the Deployment instructions.

Data logger

Data Logger is an application of the EDC that logs data from an OPC server to any ODBC-compliant database.

Data logger monitors for any data changes in the PLC. It will log the changes through the database and staging the data in a temporary storage area. The data will be accessed and processed by the Data Processor when ready.

Data processor

The Data Processor performs the real work and performed the complicated functions needed to complete the process.  The Data Processor looks at the data that comes in through the system and the Data logger. It takes the data, organizes it, makes sense of it, and identifies the cycle data. It then analyzes the data, Envisionizes it (structures it) and sends it to the Envision Application Server. From there the data can be accessed through the Envision Browser.

 

 

 

 

 

 

  

 


 Collector Engine

Overview

The Collector Engine, in Envision, is a representation of an EDC (Envision Data Collector). Every collector engine is a representative of an EDC.

Before you can Deploy your Envision project, you need to configure how Envision will communicate with the PLC device that controls the machine/process that your project is monitoring.

The first step is to create a Collector Engine. This defines the actual piece of hardware that will connect to the PLC network and gather data via an OPC (Kepware in this case) from the PLC.



Click on the Admin button on the top right-hand side of the menu bar.

 

 

 

 

 







Slide the cursor over to the left-hand edge of the window until the side menu appears. This action will open the Admin menu tab.



Click the Collector Engine_   tab to open the Collector Engine Display Table.

 

 

 

 







 

Adding a New Record

In the window that pops up, you can create a new Collector Engine by clicking on the + Add new record button, enter a name for the new engine, and then click the update button. From there, are the Agent Version, Address, and Last connect columns as well. Only the name needs to be added, no other data other than the name needs to be entered.

 

After clicking the update, the Collector Engine Table now displays the newly created Collector engine for “AMT CE 001”. Use the  Edit button to make any changes to the name field.  Use the  Delete button to Remove the Collector Engine from the table. Clicking the  Status button will display the current status of the Collector Engine. The  ID  button will open a small window with the ID displayed. Click  OK  to close the window.

 

 

 

 


PLC

PLC | Overview | PLC Function | PLC Devices

Overview

The next step after creating the Collector Engine is to create and configure the PLC device itself. Based on the type of PLC (Rockwell ControlLogix, Siemens, Mitsubishi, etc.), you are dealing with for your Envision project, you will need to enter certain information to tell the Envision application where inside the PLC memory it needs to read data from.

When you slide the cursor to the left-hand edge of the window, the Admin menu appears. Under the heading, PLC is two (2) selections that can be clicked on, Channels and Devices.



 

PLC Function


The Channel information is used by the EDC server to setup how data is transferred between the different PLC devices and the EDC. Each channel is like a separate connection as far as the EDC is concerned. This means it can be communicating simultaneously with each PLC. This can be considered the recommended default setting. The trade-off with having independent channels for each processor is that it adds more traffic to the network at any given point in time. When there are many PLC processors connected to an EDC it may become necessary to have PLCs share channels to reduce the amount of traffic on the network. When PLCs share a channel, the EDC will read data from them in a sequential fashion rather than simultaneously. The Channel selection is used to set up the sharing of channels between PLCs. The trade-off with PLCs sharing a channel is it takes longer for the EDC to read data from the PLCs since it is reading data from one PLC, then the next PLC, and so on, until it reads the last PLC on the channel and then repeats the sequence. The potential is that data may change in the PLC before the EDC was able to read it. There are options available to help reduce the risk of missing data. The Channels selection is usually only important when an EDC is going to be talking with many PLCs, say more than 4 or 5. The amount of data being read from a particular PLC could also play a role. These situations need to be addressed on a case by case basis.



One Channel setup with Multiple PLCs (2 or More)

If a cycle time would take several seconds to minutes, one channel can be used for multiple PLCs. Each PLC will send off a data package into the channel. The Channel will read each PLC one at a time in order. When the last PLC is read, it goes back to the 1st PLC.Because the typical channel can only perform one action at a time. If there were 2 or more PLCs, then it would create a bottleneck at the channel input. It would only be able to process one action at a time. 1 action from PLC 1, then 1 (2) action from PLC 2, and so on. This setup is typically s l o w e r through the channel, but also creates less demand or traffic, on the network. If the cycle time is high and data requirements are low, then this would be a good setup to use. This system configuration is slower but has less demand on the network if used.

Two Channels Setup with 1 PLC Each


In the event of a very low cycle time, where the cycle time would be millisecond to a few seconds, it would be better to use multiple channels with a single PLC. With 2 channels with a PLC for each, it would be able to process the data faster. The bottleneck would be eliminated. However, using this setup would create greater demand or traffic, on the network.
This would also be the case if you have different models of PLCs. Two different PLCs cannot run on the same channel. Therefore, it would be necessary to have a separate channel for each PLC. You have to take caution that too much demand on a Network connection can cause a series of issues such as flooding the network, saturation, and cause backlogging resulting in packet losses as well as other problems.













PLC Devices

Click on Devices under PLC heading inside the menu.

The following window appears. The data currently shown in the screenshot is data that was created in a test environment. It gives an idea of what a system with many PLC devices would look like. In the Admin menu, click the + Add new record button.



Click the + Add new record button and a series of options will appear, text boxes to name the Device and Network ID. Dropdown menus for Plc Device Type, Channel, and Collector Engine. And a selector for PLC ID and Job ID as well. Enter the information for the PLC device you are adding, then click the update button.

 



 

The Name(*)   field is where you enter a name for the PLC. For this example, Test is the processor name.

The  Plc Device Type(*) field utilizes a pulldown menu from which you select the type of PLC that you are connecting. For this example, Rockwell ControlLogix was selected from the menu.

The  Channel field can be left blank. A Channel with the same name as the Collector Engine will automatically be created and inserted into the field when the Update button is selected.

The  Collector Engine field is where you enter the Collector Engine name that was created previously. The Test, is the Collector Engine name that was created for this example. The Collector Engine named “Test” communicates with the named PLC Device “Test”.

The Network ID (*)  field is where the Ethernet I.P. address for the PLC device is entered. For Rockwell, this typically would be the I.P. address of one of the Ethernet modules in the chassis where the PLC resides. This would be based on how the EDC is networked into the PLC network. For this example, 136.129.6.4 was used.

The  PLC ID  is an Integer reference number for the PLC device.

The  Job ID  is the number of the job agent that will process the collected data.  For advanced users only, a performance increase may be possible by distributing the processing load among multiple job agents.

Once all of the parameters are set and you approve, click the Update, to save.

PLC Channel s



Overview

  • Array.ANALOG.ArrayCount

    • Array.IO.ArrayCount

    • Array.OP.ArrayCount

    • Array.USER.ArrayCount

    • PATH

    • Program.Name

    • SLOT

 





The PLC Device, named Test, is created and added to the list of available PLC Devices. Note that the Channel field has an entry of (AUTO) Test shown. This indicates that a Channel named Test was automatically created when you created the PLC Device since the Channel field was left blank.

Click on the Channels button on the LH side menu and see that the channel (AUTO) Test was created.





















The next step is to configure the PLC Device. Go back to the Admin Display Menu, and select Devices under the PLC Tab.  The configuration selections are based on the PLC type (Rockwell, Siemens, etc.). For this example, we’ll be dealing with configuring a Rockwell ControlLogix PLC Device. Click on the  Config button for the PLC Device named (Test) that you would like to configure.

The following window pops up. Not all of the selections can be seen at one time in the window. There is a scroll bar to allow navigation to the remaining selections. Multiple screenshots will be utilized to show all the different available selections. There are actually only 6 or so selections that should ever be modified and so those will be focused on. The remainder should use the Default Value unless there is a sound reason to change them.







In the Device Config. 1st screenshot all the Parameters shown should be left with their Default Value. They are shown in the Device Config. list for informational purposes.

In the Device Config. 2nd the screenshot 3 Parameters can be modified based on the specific application that is being monitored. If the Envision application is designed to store analog data or if the PLC has fast-changing data then either of these can impact what values are entered for these specific parameters.















Array.ANALOG.ArrayCount  

Array.USER.ArrayCount       |   1    |    1    |    !Edit.    

This value (Array.ANALOG.ArrayCount) can range from 1 to 5. If the specific Envision application is not designed to capture any analog data then this Value should be left at its Default Value of 1. If the Envision application is designed to capture analog data then it is recommended that the Value be changed to 5. The PLC driver will use 5 identical arrays that will store Change Of State (COS) data for all analog signals in a cyclical manner. 1st COS will be stored in array 1, 2nd COS in array 2, 3rd COS in array 3, 4th COS in array 4, 5th COS in array 5, 6th COS in array 1, 7th COS in array 2, etc. This allows the EDC to capture fast-changing data even if the OPC (Kepware) is not as fast as the PLC scan time. The OPC will read all 5 arrays every time it accesses the PLC database.

 

Array.IO.ArrayCount  

Array.IO.ArrayCount       |   3    |    3    |    !Edit.    


This value (Array.IO.ArrayCount) can range from 1 to 5. The Default Value of 3 is recommended to be left unchanged. Data in the IO array can sometimes have COS in consecutive scans of the PLC. This usually occurs near the end of a cycle and the beginning of the next one. Since the COS of data in the IO array is “fast” only at certain points and only for 2 or 3 PLC scans having the number of arrays used set to 3 is usually sufficient. The PLC driver will use 3 identical arrays that will store Change Of State (COS) data cyclically. 1st COS will be stored in array 1, 2nd COS in array 2, 3rd COS in array 3, 4th COS in array 1, 5th COS in array 2, etc. This allows the EDC to capture data that may have changed in back to back scans of the PLC even if the OPC (Kepware) is not as fast as the PLC scan time. The OPC will read all 3 arrays every time it accesses the PLC database.

Array.OP.ArrayCount  

Array.OP.ArrayCount       |   3    |    3    |    !Edit.       

Array.OP.ArrayCount – This Value can range from 1 to 5. The Default Value of 3 is recommended to be left unchanged. The same explanation used above for Array.IO.ArrayCount holds true for Array.OP.ArrayCount.

In the  Device Config. 3 screenshots there is 1 Parameter that can be modified based on the specific application that is being monitored. If the Envision application is designed to store User data and the data is fast-changing then that will impact what value is entered for this specific parameter.

Array.USER.ArrayCount

Array.USER.ArrayCount       |   1    |    1    |    !Edit.    

Array.USER.ArrayCount – This Value can range from 1 to 5. If the specific Envision application is not designed to capture any User data, then this value should be left at its Default Value of 1. If the Envision application is designed to capture User data, then this value can be modified if the data is fast changing using the same explanation given for Array.ANALOG.ArrayCount. (Note: USER Array is currently unavailable. Future releases of Envision will incorporate this feature).

 

 

 

 

 

 

 

 

 

 

 

In Device Config.4 screenshots 3 Parameters can be modified based on the specific configuration of the PLC hardware and how the connection is made between the EDC and the PLC.

PATH 

PATH             | 1   | 1  |  !Edit.    

This Value helps describe how the EDC (specifically the Kepware OPC) will connect to the PLC database after it has established communications to the Network ID entered for the PLC Device (136.129.6.4 for this example). For Rockwell, a Value of 1 indicates that the PLC processor is accessed via the chassis backplane where the processor is installed. This is the most common method of connecting to a Rockwell PLC. This means the EDC is connected directly to an Ethernet communication module that is mounted in the same chassis as the PLC. There are other scenarios where the network between the EDC and the PLC is more complex and subsequently causes the PATH parameter to be more complex. You will need to refer to the Kepware manual that specifically addresses the different communication network setups that it supports for Rockwell processors to determine what the PATH value should be for these situations.

https://www.kepware.com/products/kepserverex/drivers/allen-bradley-controllogix/documents/allen-bradley-controllogix-ethernet-manual.pdf

 

Program.Name  

Program.Name          |   ENVISION  |   ENVISION   |    !Edit. .    

This parameter (Program.Name) defines the program name that the Envision PLC software driver will be called when it is imported into the ControlLogix project file. The Import file (*.L5X) is created when a Deploy is performed. It is recommended that the Default Value of ENVISION is used unless it is absolutely necessary to change it. One situation where the Program.Name parameter would need to change is if there is more than one (1) Envision PLC driver program imported into a PLC. The Envision PLC program names will need to be unique in this scenario. One Program.Name could be ENVISION and the other ENVISION_A for example. The Program.Name is used by EDC to find the program scoped tags that it needs to access.

 

SLOT

SLOT              |   0     |  0     |    !Edit..   .    

This parameter (SLOT) is used to define the slot within the PLC chassis that the PLC processor is installed. This value is used by the EDC in helping define the communication path between the EDC and PLC. Typically PLC processors are mounted in slot 0 although they can be mounted in any slot. Modify this parameter as needed.

 



 


Editing Asset Tags

Editing Asset Tags | PLC Tags | PLC Setup and Configurations

Asset Tags are used to convey additional information to the Envision application for display purposes and also for reporting calculations. To access the tags in Admin mode, highlight an object at the Asset level in the Factory tree window and then click on the Tags button.



The following window appears:  Here is a zoom-in of the most frequent tags used for cycle recording.





 

 

 

 

 

PLC Tags

PLC tags have already been assigned in this example for the I/O Expressions. The Asset Tags themselves are pretty self-explanatory. AUTO, MANUAL, FAULTED, BLOCKED, PRIMARY STARVED (and also SECONDARY STARVED which isn’t used in this example) are used to draw lines when looking at cycle history with Sequence View enabled to indicate when any of these signals changes state.

Below is an example of how Asset Tags are displayed in the Cycle view screen. Note: Must be selected for sequence view.

There are other Asset Tags that can be edited. To see these, click the Show All Tags button located at the lower LH corner of the window.

PLC Setup and Configuration

Editing Asset Tags | PLC Tags | PLC Setup and Configurations

One Channel setup with Multiple PLCs.

In the event, that a cycle time would take several seconds to minutes, one channel can be used for multiple PLCs. However, the typical channel can only perform one action at a time. If there were 2 or more PLCs, then it would create a bottleneck at the channel input. It would only be able to process one action at a time. 1 action from PLC 1, then 1 (2) action from PLC 2, and so on.  This setup is typically slower but has less demand on the network. If the cycle time is high and data requirements are low, then this would be a good setup to use. This system configuration is slower but has less demand on the network if used.

Two Channels Setup with 1 PLC

In the event of a very low cycle time, where the cycle time would be millisecond to multiple seconds, it would be better to use multiple channels with a single PLC.  With 2 channels with one PLC a piece, it would be able to process the data faster. The bottleneck would be eliminated. However, by using this setup, the demand on the network would be greater.

This would also be the case if you have different models of PLCs. Two different PLCs cannot run on the same channel. Therefore, it would be necessary to have a separate channel for each different PLC. You have to take caution that too much demand on a Network connection can cause a series of issues such as flooding the network, saturation, and cause backlogging resulting in packet losses and other problems.

 

 

 

 

 


Models

Models | Overview | Adding, Editing, and Deleting

Overview

In ENVISION Models have significant importance. Models are used to signify a major motion path that needs independent baselines assigned to these motions. It must have a valid IoExpression entered for Asset cycles to be captured. The Envision application uses the MODEL tag as a pointer to the appropriate baseline cycle time values entered for each group of the Asset. Options are used to signify part type differences where the major motion remains the same and existing baselines and tolerances can be used. Options are generally used for reporting purposes.

At the top of the Cycle View window, you will see the following tags now visible: CYCLENUMBER, PARTNUMBER, MODEL, OPTION, and PALLET. These tags are 32-bit values. The MODEL tag has significant importance. NOTE: It must have a valid IO Expression entered, for Asset cycles to be captured. The Envision application uses the MODEL tag as a pointer to the appropriate baseline cycle time values entered for each group of the Asset. You define the models and their values in a different area of the Admin environment. This is shown in detail elsewhere but a short example of what the MODEL tag is used for and its significance is shown below.





Slide the cursor to the left side of the screen to open the Admin Display menu. From the side menu, select the    Model (Tab)   from the side Admin Display Menu.



A list of the PLC devices that have been defined appears. You select the PLC that was entered for the PLC Device for the Asset. For this example, the PLC Device is TRAINING_SIM_STA. Click on it.

The following window appears. In this example, 3 models have been created. The Part Code values are the numbers that the Envision application expects to see returned by the tag name entered in the MODEL Asset Tag. S130VRoll_SR.Model is the tag name that was entered for this example.

 













Adding, Editing, and Deleting

From this Model screen, several types will be listed in a table. These are the types that were previously inputted earlier from when the test was set up. They can be.!. edited or.3. deleted. You may also add to the list by simply filling out the fields above the list.  Enter the name that you would like to call it, the Part Code, Type, and Priority. Then click the. +. button to add it to the list.

Name

Enter a name that is unique to the object you are using. For example, above, there are 3 different Cab configurations, Crew, Regular, and Super Cab. To add the Extended Cab (Ext), we would enter Ext under the name dialog box.

Part Code

A part code can be an actual part number or merely a designation number to show a difference between parts or similar parts. In the example above, the different types have a simple number to designate their Part Codes.

Type

In this part of the Table, there is a pull-down tab to which will give you a selection of choices to choose from. They are GOOD, DMGD (Damaged), EMPTY, NULL, and TEST. These labels or strings are configurable to make it whatever you deem as needed. They are common types in manufacturing. The label can be tagged so the PLC can know what is in the system at that time.

In the case of manufacturing, the choice of GOOD would be picked in the production of parts. DMGD selection would represent a part or process that could not be completed due to an incomplete process or stoppage.

  • GOOD

  • DMGD

  • EMPTY

  • NULL

  • TEST





Priority

An integer value is used to select which model to use when multiple models code are collected during a cycle. It is based on the fact that a lower number is a higher priority. As in the number 1 priority would be higher than 2 or 3.

 

Once the Model data has been created, baseline values can be entered for the Groups that comprise the Asset. This is shown in the following screenshots. Drag the cursor to the left-hand edge of the screen for the Admin menu to appear. Click on Objects & Relationships to go back to the Factory Window.

Expand the tree in the Factory window as shown. Then highlight the CYCLE TIME (GROUP level)  and click on the  Baseline  Values button. A window will pop up with a table for entering Baseline data parameters.

The Baseline (Design) Values window will reveal. From here, the values of the Group Ops are inputted. In this example, all the values are inputted in for At Pounce.













There are 3 other objects, Move In, Align Pos, and Move Out, that will need to have the values inputted as well. Click on the object tabs to input your values.



 

 

 

 

 

 


Baselines and Tolerances

Baselines and Tolerances | Baseline Values | Tolerances

Baselines are used to signify the expected or designed duration each motion will experience.  Tolerances are used to denote how much variation from these baselines there can be before the motion is flagged. Motions will be flagged as “Watch” – the cycle duration exceeds the “NTol” value – or they will be flagged as “Warning” – the cycle exceeds the “Tol” value – which will display these motions on the “Hotspots” screen and is also used for reporting purposes.

There are 3 generally recommended – but not fully inclusive – methods of baseline and tolerance selection:

Choose a baseline value slightly above the normally expected cycle duration with tighter tolerance values.

Useful for setting standard tolerance values for common pieces of tooling.

Generally, tight variance cycles where a small overage denotes an immediate issue.

Choose a baseline value of an average expected cycle duration with wider tolerance values.

A more variable normal cycle duration useful for tracking cycles that exceed normally expected variance.

Generally, tight variance cycle where a larger overage is allowed.

Choose a baseline value as a hard limit with zero values for tolerances.

CycleTime group where an overage constitutes a machine over cycle condition.

Operator motions where a maximum time is given and any overage is considered an over cycle condition.

An agreed-upon maximum limit for a common piece of tooling is used to track tooling degradation for predictive maintenance purposes.

Object Classifications

Object Classifications are used to label common types of objects for easier usage for reporting purposes. By creating and assigning classifications to individual Group motions for each Asset, these objects can quickly be sorted and combined for reporting and data analysis.  Commonly used classifications are Operator, Tooling, Robot, and Joining. These classifications are fully user-definable, and any group may be assigned multiple classifications.

Smart notes

Notes are used to add descriptions to a given cycle. Note categories and subcategories can be created or modified in the admin area of ENVISION. When a note is created on a given cycle, any previously created note category can be assigned to this note, and these notes can then be sorted and summarized based on their category. Notes are very useful for describing reasons and conditions for abnormal cycles; these notes remain persistent and are available to all users. See Note Categories.

 

 

Baseline Values

When the Baseline Values button is selected, the following window pops up.  It is here where the data is entered for baseline (Cycle Time) and tolerances for the models that were created previously. This is the data that the Envision application uses to create the graphical representation of the cycles. For this reason, the MODEL Asset tag is of critical importance. Envision needs a value for the MODEL Asset tag or it will not know how to “draw” the cycle.

Every Group of the Asset will have a similar window that pops up when the Group object is highlighted and the Baseline Values button is clicked. For Group objects with 2 or more OP’s, each OP will need values entered individually as required.

There were additional Asset Tags that appeared when the Show All Tags button was clicked. These tags can be used to display additional information for each cycle.

The CYCLENUMBER tag does not need an IoExpression and will be ignored if one is entered. This tag is automatically updated by the Envision PLC driver logic. The tag is displayed for informational purposes only.

The PARTNUMBER tag can be used to store a part tracking value such as a sequence number or rotation number if the process utilizes some sort of part monitoring. This is optional. If no IoExpression is entered, then Envision will display a zero.

The OPTION tag is currently not used by the Envision application for any display or calculation purposes. It is for future use. A value can be entered for the IoExpression but it will be ignored by the application.

The PALLET tag is fairly self-explanatory. It can be used to store part conveyance data such as a conveyor carrier I.D. number or a roller bed pallet I.D. This is optional. If no IoExpression is entered, then Envision will display a zero.

To edit model baselines and tolerances, go to any group object, then click the baseline tab at the top of the window. CycleTime baseline values will determine when the Asset starts and stops all other baselines will only affect Groups.

Baseline tables will differ from one another in terms of how many models each asset has, and how many OPs each group has.  The values inputted in each cell will depend on how each model tied to the asset is intended to function. ­­­



 

 

 

 

 

 

 

Tolerances

Baselines and Tolerances | Baseline Values | Tolerances

Overview

The Tolerances are preset in Envision to give a visual representation of the health of the cycle with a glance. In sequence, the base of the cycle is the Cycle Length. Cycle Length is represented by a Blue bracket on the graph. In a recorded cycle, it will show the length as compared to the Baseline tolerance. It will show a color based upon the performance of that cycle. Green for Good Cycle Length,  Yellow to Watch, and  Orange to give the operator a  Warning. Below are the definitions of each in the Sequence and Heartbeat Views.

Cycle Length

Cycle Length baselines are represented by a |--- blue- --|bracket in Envision. Ideally, group length will match this bar exactly.

 Minimum Tolerance

Minimum Tolerance is the amount a group or cycle can deviate below the cycle time before becoming an Orange (Warning) record.

 Minimum Normal Tolerance

Minimum Normal Tolerance is the amount a group or cycle can deviate below the cycle time before becoming a Yellow (Watch) record. The NTol number should always be smaller than the regular Minimum Tolerance (Min Tol).

 Good Cycle Time

A Good Cycle Time record will be Green (Good) if the amount of deviation above or below ideal cycle time is smaller than any tolerances.

 Maximum Normal Tolerance

Maximum Normal Tolerance (Max NTol) is the amount a group or cycle can deviate above ideal cycle time before turning Yellow (Watch). The MaxNTol number should always be smaller than the Maximum Tolerance (Max Tol) number.

 Maximum Tolerance

Maximum Tolerance (Max Tol) is the amount a group or cycle can deviate above the cycle time before becoming an Orange (Warning) record.



All in Heartbeat View

Tolerance Reference sheet

This example is shown in Sequence mode also shows the actual details if you hover the cursor over the cycle bar.

 

Tolerances in Heartbeat View

 

 

 

 

 

 


User Maintenance

User Maintenance | Overview | Create New User  | Changes and Editing Profile

Overview

This section of the Admin module contains the data table of all the created user accounts. To use or make changes to the administration module you will need to be registered in this database.



Create New User

To add a new user, click the Create New User button on the upper right side of the User Maintenance Table window. Once selected, a Create User window will appear. Input a Username, Full name, and Email address in the required fields. Below the edit boxes, is the Roles list. Check off the roles you will be performing. These roles will add permissions and allowances for using the Admin Module. After you are finished, click the save button.

 

 











The User Maintenance List will now have the new user in the database.

To make any changes, use the buttons to the right side of the User Maintenance window.



 

 

 

 

 

 

Changes and Editing Profile

User Maintenance | Overview | Create New User  | Changes and Editing Profile

On occasion, changes to a profile may be required or a profile may need to be removed. The User Management window has the options to make changes by using three different buttons, Edit, Reset Password, and the Deactivate buttons. All buttons are located on the right side of the User Management table. 

Click the Edit button and an Update User window will open. Make the changes to Full name, Email address, and check or uncheck additional Roles.

When your changes are completed, click the Save button.



In the event you lose or forget your password, you can have it automatically reset if needed.

Clicking the  Reset Password button will send you an email with a new password. Ensure that your email is correct. If you don’t see it in your inbox, check the spam or junk folder.



Clicking the  Deactivate button will disable and remove the selected profile from the database.

 

 

 

 

 

 

 

 


System

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

System Configuration

The System section tab has many different sections that have the setting and configurations for the Admin Module. Clicking on the System Configuration tab will reveal the subsection to the right.



Warnings

If this message appears anywhere on a window you are viewing, take caution. Any changes made will change all global settings immediately on the network. Be very cautious when performing any actions or changes on any window with this warning.

 

 

 

 

 

 

State Display Settings

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

The State Display Names Tab is used to edit the default names, colors, and appearance of the objects and display names. NOTE: These changes made are global and immediate!!!

The names of the States all have a default name. If you wanted to use another name other than the default, simply use the edit box under the Override column, to the right of the State (default) name, to change it to what you desire.

The states have a default color code for each state, but they can be modified as well. Simply click on the colored box and a color pallet will appear. Choose the color, tone, and hue you desire.

At the far right side is a column labeled “Show in Live View”. Check and uncheck the boxes to show this state in the Live View Module. When everything is set, click the Save button.







 

 

 

 

 

 

Object Classifications

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

The Object Classification tab controls the Classifications on the Edit Select object window, under the Objects and Relationships window. Any changes that you make here in this window will display when viewing Group level objects in the Objects and Relationship window.

These Classifications created here, are used for Grouping, Sorting, and other purposes used in the reports.

Simply double-click an Object Classification and then edit it to read what you desire.

If a field has a Lock icon, then this Object Classification cannot be changed in this window.

There is an open field to enter a new Object Classification if needed. Simply click on it and enter the Classification.













When you are finished, these Classifications will appear on the Objects and Relationships window, when you have a Group level object selected. The Edit Selected Object tab is selected, as seen here.







Note Categories

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

The Notes Categories tab holds the key to configuring the Notes Category list in the Cycle View Browser. From here, you can add, remove, or edit the categories that will appear in the Cycle View Notes. To add a new Category or Subcategory, click on the editing box with the labels starting with “Add New”. Input your new Category or Subcategory. For an already existing Category or Subcategory, you can double click on it to edit the field.



In the Cycle View browser, when viewing an Asset or Group level object you can click on the  Notes.     button to create a note. Shown here is a screenshot from the   Notes browser section. When the Category pulldown is selected, it shows the selections you made in the Note Category List editor.



 



Date and Time

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

This section controls the Date and Time formats that appear in the Envision, Tables, and Data.

Date Format

To change the date format, click in the Date Format editing box and delete the previous format if there was one present before. Input a different format style in its place. If it is recognized by the program, then it will show an Example below the Edit box.

Date formats examples:

American MM/DD/YYYY

European-DD.MM.YYYY

Japanese-YYYY-MM-DD

Time Format

To change the time format is very similar to changing the date format. Click in the Time Format editing box and delete the previous format, if there was one present before. Input a different format style in its place. If it is recognized by the program, then it will show an Example below the Edit box.

Common Time Formats:

h:mm:ss a  / 1:30:00 p.m.

hh:mm / 13:30

h:mm / 1:30

 

When your changes are complete, click the   Save button and the changes will update in the program.

NOTE: These changes made are global and immediate!!!

 

 

 

 

 

 

 

 

Nomenclature

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

Because of different industry standards, some companies have different definitions and keywords for certain parts of their company. Based upon company needs, it may be necessary to rename one or more of the Default Objects, Part-type, Parts, and Pallets. The Default Object names are common and/or typical names in manufacturing.

NOTE: These changes made are global and immediate!!!

In this case, we would like to change the name for the Line (default) object from Line to Segment. Click on the Editing box for Line. Delete the previous name (Line). Then input the name (Segment) you desire.

After your changes, review your changes and click   Save to complete the process.

 

 

 

 

 

 

 

 

 

 

 

EDC Agent Settings

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

The EDC Agent Configuration screen is used to set the Heartbeat Update Delay. Since the Agent is continually trying to contact the EAS, constant contact would cause a strain on the EAS. Therefore, this configuration setup feature will allow the EDC Agent to connect to the EAS and update at a specified interval (120 seconds in this example). The inputted number must be greater than 59 seconds.



Input the number of seconds you desire, then click the  Save button.  NOTE:  These changes made are global and immediate!!!

 

 

 

 

 

 

 

 

 



 

SMTP Settings

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (email) transmission. SMTP by default uses TCP port 25. For a more secure port, it will allow you to change to a more secure port (e.g. 465 or equivalent).

This page allows you to input the Host Server Name (the computer representing the SMTP server), your choice of the port to use, the email of the originating message, login information, and the option to use SSL (Secure Socket Layer) encryption.

NOTE: These changes made are global and immediate!!!

 

 

 

 

 

 

 

Others – Subscriptions and Default Dashboard

System Configuration | Warnings | State Display Names | Object Classification | Note Categories | Date and Time | Nomenclature | EDC Agent Settings | SMTP Settings | Subscriptions

In the ENVISION system, an email is automatically sent in the instances of certain events such as a fault, stoppage, or whatever is set in the configuration. For this reason, there is a configurable option to delay the automatic email. The Email Delay setting box is set to delay the email is automatically sent (in Minutes). This must be set for greater than 5 minutes. This would give you a preset time period that would allow you to verify an issue and make sure it is not a false positive or a false alarm before an email is sent. The level is set based upon the time needed to verify the issue.

NOTE: These changes made are global and immediate!!!

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 AUDIT

Overview

The Audit Log contains all the changes made from the actual user that is logged in. This log will show the date of the action performed, User, Method, Entity ID, Field, Comments, and the actual Data changed.

To use this feature, simply click on the Audit Date Range Icon to open a date range selection window. Choose from Today all the way to a custom range. In custom range, you select the start date and the end date, then click on Submit.

Audit Date

When an action is performed in the Admin Module, that requires a Save or a change on a screen that makes instant changes, Envision records the event Date and actual time the action was taken.

User

The user who logs into the Envision program will have their User ID added to the record. For example, Thomas Katt (username TomKat) will show up as TomKat under user.

Method

The Method is the way that the action was performed. By use of an action button (Save), command, process, update, or removal.

Entity ID

The entity ID is a label assigned to the action that was performed?

Comments

Comments are inputted by the User when the action was taken.

 

Data Changed 

The data changed section shows what the original data (Original Data in Pink with STRIKETHROUGH) was before it was changed, then shows the new data (New Data Highlighted in Yellow)as well using a color code and format to show the changes. If the result of the changes was wrong, it preserves that original data to revert to if needed. Click on any of the highlighted data in the Data Changed column and a window of the original and modified data will appear, as seen below.

In this example, you can click any of the highlighted area in the Data Changed column to open an Audit Data Details window - null {“_id”:”bdb595cb-0689-491c-a016-221a8d8bba52”,”PerentId”:”f4270b7

The Audit Data Details window contains all the data from the previous setting. When new data is entered, it highlights the previous data in pink with a strikethrough highlights and also shows the new data in yellow highlight. If a situation occurs where you need to revert to the original configuration, this data would be available.

 


APPLICATION LOGS   s

Application Logs | Overview | Log History Selector | Descriptions

Overview

In the Application Logs section, it keeps a record of certain actions that are happening to Envision. It records a time and date stamp for when certain actions happen in Envision. It also records when a user logs into Envision. As well if Envision is experiencing an error, fault, or something did not work correctly as designed, it will create a record of what happened. 

Log History Selector

When the Application Log is selected, it defaulted to the last (1) day. To view back several days, simply click in the Log History edit box and enter the number of days you would like to look back to.

Note:  A single day may have a large number of logs. Selecting multiple days may take a longer time period to load and display.

 

 

 

Descriptions

The records it creates contains the current date, time, level (information, error, etc.), User, Method, Message, and Exception.

The Level column shows the kind of record it is representing. Info would show that there was a log on, deploy, or similar actions performed. The error would show that an action took place or an incorrect result occurred.

The Method column displays ( Envision2.Models.EDCAgent.EDCAgentRepository.LogEdcError )what part of Envision experienced the condition, and the action or inaction that was taking place. In the case of an inaction, or something that was supposed to happen that didn’t, it would seem that an error occurred and will be listed as such. When logging onto or to different parts of Envision, it will show it as an action in the program and leave a record of an application engaging.

The Message column contains the message recorded by the part of Envision that the Info or Error had occurred in. (CE: 393a5b41-b928-43c3-ac2b-f8ef465365b3 – ErrorMessage : EnvisionLiveData is not found). The CE (Collector Engine and Address) could not connect or get access to the Envision Live Data.

 

 

 

 

 

 


 Subscriptions and Notifications

The Subscriptions and Notifications sections is an area of the Admin module where the Subscriptions and Notifications and be monitored and maintained. From here you can Edit or Delete them. Selecting the tab will open the Subscriptions screen (default).

Subscriptions

In the Subscriptions window, the subscription button will be highlighted in blue. You can easily go to Notifications by selecting the button to the right of it. Below the button is a table of previously configured subscriptions.

Filter Bar

You can filter each column by selecting the filter icon, atop of each column. This action will open a window that will show a check-off list that will include the items of each column and a Select All box. Either select check all or select the individual items you desire. When finished, select the OK button to close and update the table list.





You can also sort by using the search dialog. Simply start typing the name of the item you seek and a list with a similar item name will appear below. From there, the items of the list can be Edited or Deleted.

 

 

 

Notifications

The functions of the Notifications Table are the same as the Subscriptions table.

 

 

 

 

 

 

 

 

 

 

Edit

Selecting the Edit button will open the Configure Subscription window. From here, changes can be made to the selected subscription. Once everything is edited, select the Save button to save the newly edited subscription or select Close to go back to the table list.

 

See Subscriptions and Notifications at the End User manuals or the Beet Knowledge Base.

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Glossary

AOI

Add On Instructions

CE

Collector Engine

COS

Change of State

EAS

Envision Application Server

EDC

Envision Data Collector

xls

Excel spreadsheet

FIS

Factory Information System

OP

Operation

OPC

OLE Process Control

OEE

Overall Equipment Efficiency

PB

Push Button

PLC

Programmable Logic Controller

SSL

Secure Socket Layer

SMTP

Simple Mail Transfer Protocol

UID

Unique Identifier

VPS

Virtual Private Server

 

 

 



 

 

 









 

 

 

3.6 enVision Administration Manual (PDF)