Laserfiche WebLink
0 The color of all animations and values on displays shall indicate if the <br /> status of the object attribute. <br /> d. Operation from graphics — It shall be possible to change values (setpoints) <br /> and states in system controlled equipment by using drop -down windows <br /> accessible via the pointing device <br /> e. Graphic editing tool — A graphic editing tool shall be provided that allows for <br /> the creation and editing of graphic files. The graphic editor shall be capable <br /> of performing/defining all animations, and defining all runtime binding. <br /> 0 The graphic editing tool shall in general provide for the creation and <br /> positioning of point objects by dragging from tool bars or drop -downs <br /> and positioning where required. <br /> 0 In addition, the graphic editing tool shall be able to add additional <br /> content to any graphic by importing backgrounds in the SVG, BMP or JPG <br /> file formats. <br /> f. Aliasing — Many graphic displays representing part of a building and various <br /> building components are exact duplicates, with the exception that the <br /> various variables are bound to different field values. Consequently, it shall be <br /> possible to bind the value of a graphic display to aliases, as opposed to the <br /> physical field tags. <br /> 9. Historical trending and data collection <br /> a. Each Automation Engine shall store trend and point history data for all analog <br /> and digital inputs and outputs, as follows: <br /> 0 Any point, physical or calculated, may be designated for trending. Two <br /> methods of collection shall be allowed: <br /> - Defined time interval <br /> - Upon a change of value <br /> 0 Each Automation Engine shall have the capability to store multiple <br /> samples for each physical point and software variable based upon <br /> available memory, including an individual sample time /date stamp. <br /> Points may be assigned to multiple history trends with different <br /> collection parameters. <br /> 2.4 Network Control Engine (NCE 25XX) <br /> 1. The Network Control Engine (NCE) shall be a fully user - programmable, supervisory <br /> controller. The NCE shall monitor the network of distributed application- specific <br /> controllers, provide global strategy and direction, and communicate on a peer -to- <br /> peer basis with other Network Automation Engines. <br /> 2. The Network Control Engine (NCE) shall be a fully user - programmable, digital <br /> controller that includes a minimum of 33 I/O points. <br /> 3. Automation Network — The NCE shall reside on the automation network and shall <br /> support a subnet of 32 Field controllers. <br /> Non - Professional Services Agreement between November 1, 2010 <br /> City of San Leandro and Martin Industries, Inc., DBA Climatech Page 18 of 28 <br />