Currently, there's critical and frustrating differences between the the Power Operations and PlantScada versions of the user editable DBF files. Power Operations has added additional columns to certain DBF's to support the Device Profile functionality critical to that product.
In addition, the lack of certain 'almost standard' fields makes it hard to write tooling and automation around the DBFs, and internal inconsistancies in the provided DBF files causes subtle and frustrating errors.
Specific requests:
Every DBF that takes user input should have a TAGGENLINK field, LINKED, and EDITCODE field, currently most do, but not scanner, almsrv, trnsrv, rptsrv, unit, computer, netaddr, and some others.
Power Operations specific modifications to DBF, which include units and param adding an equipment field, should be merged into the plantscada dbf files.
Dbf Column orders vary slightly between the applications, and within the application. For example, the System project files included in 8.2 have a different column order than the files created by 'Create New Project'
Guest
|
Idea business value
Consistancy between products and features, reduce errors when working in multiple environments |
|
| Idea priority | 3 – Some use to my company |
