Laserfiche WebLink
Mee <br />AUTOMATION <br />Nothing Leaves Enterprise Untested <br />Enterprise Automation <br />210 Goddard Irvine CA 92618 USA <br />Tel 949- 769 -6000 Fax 949 -769 -6005 <br />¢mow. eal ntonrator:00m <br />a. 1/0 naming conventions <br />b. Internal PLC variable naming conventions <br />2. User security standards <br />3. PLC code commenting standards <br />4. Software backup standards (possibly recommending a formal source control <br />system with check -In /check -out functionality) <br />4.9.2 PLC code modules and data structures <br />EA will also develop and document the following PLC code module standards and <br />associated data structures based on outcomes of the site operations workshops <br />performed early in the project: <br />1: Digital input <br />2. Analog input <br />3. Analog output <br />4. Pump (DOL) <br />5. Pump (RVSS) <br />6. Pump(VFD) <br />7. Valve (open /close) <br />8. Valve (modulating) <br />9. PID controller <br />10. Intrusion control <br />11. Electrical energy monitoring <br />12. Communications module <br />These code modules will be fully functional and compatible with the existing Dynac <br />SCADA system. <br />Following development, EA will develop test documentation and subsequently test each <br />code module to ensure they are ready for handover to the PCS Integrator. <br />It is likely, and more to the point beneficial that the PCS Integrator will need training on <br />the use of these standards, however EA has not provided for this scope. <br />Revision: <br />251 -75 <br />Page Number 9 of 11 <br />