New PLC EN

From PlcWiki

Revision as of 08:16, 14 April 2020 (view source) Jon (Talk | contribs) (Created page with '== Reasons to develop new version == # Optimized SQL database structure # better configuration management (centralized, versioned, ...) # User-friendly front-end for production …') ← Older edit		Revision as of 08:22, 14 April 2020 (view source) Jon (Talk | contribs) Newer edit →
Line 62:		Line 62:
	* Customer benefits		* Customer benefits
	* Customer training		* Customer training
-	* How do I fast	+	* How to proceed during implementation

---

Revision as of 08:22, 14 April 2020

Contents 1 Reasons to develop new version 2 PLC Areas 3 PLC data model 4 What you need to change 5 Define impact on customer and collaboration in implementation

Reasons to develop new version

1. Optimized SQL database structure
2. better configuration management (centralized, versioned, ...)
3. User-friendly front-end for production configuration
4. better web interface
5. new software modules
   1. monitoring station - Display the current status of products on the production line
6. Expand client options
   1. graphic front-end
   2. separation of PLC core and graphic input and output
   3. ssh connection for showscreen through kernel
   4. two-level configuration: declarative + imperative (scripts, external modules through hooks, DBUS?)
   5. API, hooks + modularity (modification without client kernel translation)
   6. QtScripting (AKA JavaScript), PythonQt
   7. Add-ins in C ++, Java, Perl, Bashi, ... (SWIG?)
   8. continuous state saving - possibility of reinterpretation for remote display / control purposes
   9. multilevel logging
   10. dynamic layout based on required operations (better use of screen area)
   11. rack partcheck defined by enumeration of positions
7. better performance
8. change logic of manufacturing operations
9. External access to current production and status data
10. robustness
11. possible kernel station independence
12. documentation !

PLC Areas

1. client
2. kernel
3. Data transfer between modules
4. Data transfer between PLC and external systems
5. web
6. SQL DB
7. utilities (auxiliary scripts, ...)
8. OS settings

module - separate functional component of PLC

PLC data model

1. production DB on the kernel
2. archive DB to SQL
3. Data is coming from the client:

* std. mechanism of communication with PLC kernel to production DB

* SQL protocol to archive DB

1. After the production is finished (or a certain period of time has elapsed), the product data is moved to the archive DB (if it was previously sent by the client, it is not overwritten)

What you need to change

• Web interface

* Listing of product details - problem if the VIN is in the database several times (eg current and same VIN two years ago)

• PLC client

* Dependencies - track the entire string of dependencies, not just one

• Configuration tool

* Define the roles in the PLC, who will configure what (System, operations, part numbers for part checks) ...

Define impact on customer and collaboration in implementation

• What the customer will need
• Interface for receiving and sending data - changes?
• Customer benefits
• Customer training
• How to proceed during implementation