Backup and Restore at process control networks
Backup is a process of creating a copy of your data to be able to restore it during failure or disaster.
Backups can be a file backup, configuration backup, database export or a whole system backup for PLC, SCADA, network devices and windows machines.
Smaller is backup faster is recovery.
Thus, if you work with files, it is rational to make a backup of just a file, rather than recovering the whole system in hours with a system backup.
Most PCN uses Acronis backup and restore for system backups.
It is must to have a written procedures for sites for backup and restore with details on criticality of systems, backups schedules, validation, storage locations etc.
By SystemsConsult👍7
Which protocol is better to use for remote cisco switch configuration?
Anonymous Quiz
13%
rdp
19%
telnet
42%
SSH
13%
snmp
13%
secure telnet
👍1
List of Automation documents. There are many sources in internet explaining majors of them.
• Process and Instrumentation Diagrams (P&IDs)
• Loop drawings
• Instrument Index
• IO list
• IO (Tag) assignment
• Logic Print-outs
• Cause and Effect Matrixes (C&Es)
• Control Narratives
• Functional Design Specifications
• ICSS Design Specifications
• System Block Diagrams
• Control Room Layouts
• ICSS Design Specifications
• Fire & Gas I/O Database
• System Block Diagrams
• Control Room Layouts
• Instrument Building(s) Layouts
• Termination database
• Site Plot plan
• Instrument data sheets
• Cable routing drawings
• Database formats
• Database update for I/O Schedules.
• ICSS system architecture
• Power consumption
• Heat dissipation
• Panel layouts
• Graphics
• Group displays
• DDS
• Functional Logic Diagrams
• Logs and reports (Type and Format)
• Configuration Manuals
• FAT Procedure
• SAT Procedure
• Functional Test Procedures (FTP)
• Site Installation schedules
• System installation
• Loop check schedules
• Loop checks procedure
• ICSS Startup/ commissioning schedule
• Startup/commissioning support
• Process and Instrumentation Diagrams (P&IDs)
• Loop drawings
• Instrument Index
• IO list
• IO (Tag) assignment
• Logic Print-outs
• Cause and Effect Matrixes (C&Es)
• Control Narratives
• Functional Design Specifications
• ICSS Design Specifications
• System Block Diagrams
• Control Room Layouts
• ICSS Design Specifications
• Fire & Gas I/O Database
• System Block Diagrams
• Control Room Layouts
• Instrument Building(s) Layouts
• Termination database
• Site Plot plan
• Instrument data sheets
• Cable routing drawings
• Database formats
• Database update for I/O Schedules.
• ICSS system architecture
• Power consumption
• Heat dissipation
• Panel layouts
• Graphics
• Group displays
• DDS
• Functional Logic Diagrams
• Logs and reports (Type and Format)
• Configuration Manuals
• FAT Procedure
• SAT Procedure
• Functional Test Procedures (FTP)
• Site Installation schedules
• System installation
• Loop check schedules
• Loop checks procedure
• ICSS Startup/ commissioning schedule
• Startup/commissioning support
👍7⚡5
Deloitte-asset-performance-management.pdf
1.8 MB
Asset Performance Management white paper
Automation books to read
Recently reviewed several books on Automation and IT topic. Strongly recommend for read.
Control Systems Engineering Exam Reference Manual:
A Practical Study Guide
Third Edition
For the NCEES Professional Engineering (PE) Licensing Examination
Bryon Lewis, PE, CMfgE, CCNA
A Guide to Automation Body of Knowledge. Nicholas P. Sands
CompTIA Network+. Guide to Networks
Jill West
Complete A+ Guide to IT. Hardware and Software
A CompTIA A+ Core 1 (220-1001) & CompTIA A+ Core 2 (220-1002) Textbook
By SystemsConsult👍10
Projects, commissioning and operations.
One might have a question - where is better to start from: projects or operations?
I would say, for learning it is better to start in projects, then make commissioning of the same project.
In projects stage you learn how to design and there is a room for experiments and creativity.
In commissioning you learn a lot by fixing things to make them work.
However, it is true if you was involved from the project phase, otherwise you may lose hours investigating why someone wrote the code/design in particular way and not in the other way.
Also in commissioning you will find that many of design which was made during projects phase works different in reality (or even does not work).
In operations safety is a priority and every online change is a stress.
Much of time goes with collection of signatures and approvals for the change.
But operations show how things work together in reality, which you can simulate in no other environment.
Operations require different mindset.
By SystemsConsult
Zhanibek Yeskendir👍9
Sharing thoughts...
Complex projects - require deep work and focus.
Being online throughout the day hurts for such works, managers should understand this fact if pursuing outstanding results with their teams.
Innovation - requires free time and financial resources for small, fast and cheap experiments.
And it is not about a rocket science.
Complex projects - require deep work and focus.
Being online throughout the day hurts for such works, managers should understand this fact if pursuing outstanding results with their teams.
Innovation - requires free time and financial resources for small, fast and cheap experiments.
And it is not about a rocket science.
👍4
Two techniques you should look for a better alarms management
Imagine a situation when compressor, pump or well shuts down. Most of systems generate dozens of low flow, low pressure and so on alarms.
Do they really matter? No. Then, consider using alarms suppression technique to suppress related alarms when equipment is stopped.
You startup equipment and again system generates low pressure, low flow and other alarms as it ramps up.
Use alarm on-delay technique to enable alarms only after equipment is properly started up.
By SystemsConsult👍7
