I have worked at sites with generic overlays & custom (individual) overlays. I believe the benefits of using custom overlays exceeds the info you can present using generic overlays. The custom overlays are bulk generated (or created as needed using d_edit scripts/templates) but are then individually modified as necessary to show detailed info that is unique to the mtr/loop. Examples of customised info - motor auto start/stop logic, start only permits, interlocks. If a mtr auto starts on low pressure then the mtr overlay would have a live connection to the block low alarm limit to show the actual value. Custom overlays do require a bit more effort but the Operators are more informed & it helps Maint staff. Fox View needs an improved display optimisation process. Barry -----Original Message----- From: Ashley Davey [mailto:Ashley.Davey@xxxxxxxxxxxx]=20 Sent: Tuesday, 30 May 2006 5:40 p.m. To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Resetting graphics optimization for FoxView? Kevin =20 Is there a reason why you are not using generic overlays with either the "ov_conn" command or substitution scripts? =20 This would require reconfiguring the primary graphics but would eliminate all but one generic and few non-standard overlays per overlay type (i.e motor, control.etc.). Does not solve the problem of optimizing the displays, however it will reduce the overall number of graphics. =20 On two of our three sites we have implemented the "ov_conn" command to call generic overlays. On the third site we use scripts which will be replaced with the "ov_conn" command when we move from Display Manager to FoxView. =20 Regards =20 =20 =20 Ashley Davey Systems Engineer African Products (Pty) Ltd Gauteng Republic of South Africa -------------------- >>> fitzgerrell@xxxxxxxxxxxxxxx 00:21 30/05/06 >>> Terry, > The concept of 4000 graphics and overlays is a little difficult to =3D > grasp. Welcome to our paper machine! <grin> I just checked one of the FoxView workstations and it has 4818 .fdf files under the operator graphic directory. The breakdown is something like this: ~400 primary graphics ~1000 motor overlays ~1800 control overlays ~600 hand controls overlays ~300 misc overlays ~700 graphics and overlays that are obsolete, redundant, work in progress, backup or have no readily obvious purpose to me. > Is there a mechanism within the OS to know how many times a specific > display has been called by the Operator?=20 <snip> > Howmany different graphics (and overlays) does one operator call in > a one week period? <snip> > Can Op. Action Journal data be manipulated to get you useful information? I could get this information through OAJ. Many of the graphics are not needed or used on a day-to-day basis, however that doesn't make them any less important when they need to be used. =20 > Perhaps you can optimize the addresses on the 200 most-often-called=20 > graphics right away and more slowly optimize the remaining graphics=20 > over a few weeks. Unfortunately not practical. When an operator needs to take rapid action, the 30 second delay only to call up a smurfed out graphic is unacceptable. Regards, Kevin FitzGerrell Carter Holt Harvey, Ltd +64 27 460 9994 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: =20 http://www.freelists.org/list/foxboro to subscribe: =20 mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: =20 mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin= to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave= =20 DISCLAIMER: This electronic message together with any attachments is=20 confidential. If you are not the intended recipient, do not copy, disclos= e or=20 use the contents in any way. Please also advise us by return e-mail that = you=20 have received the message and then please destroy. Carter Holt Harvey is = not=20 responsible for any changes made to this message and / or any attachments= =20after=20 sending by Carter Holt Harvey. We use virus scanning software but exclude= =20all=20 liability for viruses or anything similar in this email or any attachment= . _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave