Laserfiche WebLink
ENTERPRISE <br />TERPRISE <br />Automation <br />1 <br />210 Goddard <br />210 Goddertl Irmne CA 82048 USA <br />+01-ItUTOM4TION <br />Te1949-789 6000 Faz 948.789.8005 <br />vmw.paiakgatorcom <br />Nothing Leaves Enterprise Untested <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 />B. 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 PGS 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 />hna bNeCdve Data: T7 AMl <br />Pape Number: 9 of 1 q <br />