View source

== Reasons to develop new version ==

# Optimized SQL database structure
# Better configuration management (centralized, versioned, ...)
# User-friendly front-end for production configuration
# Better web interface
# New software modules
## Monitoring station - Display the current status of products on the production line
# Expand client options
## Graphic front-end
## Separation of PLC core and graphic input and output
## ssh connection for showscreen through kernel
## Two-level configuration: declarative + imperative (scripts, external modules through hooks, DBUS?)
## API, hooks + modularity (modification without client kernel translation)
## QtScripting (AKA JavaScript), PythonQt
## Add-ins in C ++, Java, Perl, Bashi, ... (SWIG?)
## Continuous state saving - possibility of reinterpretation for remote display / control purposes
## Multilevel logging
## Dynamic layout based on required operations (better use of screen area)
## Rack partcheck defined by enumeration of positions
# Better performance
# Change logic of manufacturing operations
# External access to current production and status data
# Robustness
# Possible kernel station independence
# Documentation !

== PLC Areas ==

# client
# kernel
# Data transfer between modules
# Data transfer between PLC and external systems
# web
# SQL DB
# utilities (auxiliary scripts, ...)
# OS settings


module - separate functional component of PLC

== PLC data model ==

# Production DB on the kernel
# Archive DB to SQL
# Data is coming from the client:
:: * std. mechanism of communication with PLC kernel to production DB
:: * SQL protocol to archive DB
# 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