Data Management Application

This application is part of my current project developing control software and designing water purification products.   It was developed using my AppBuilder applications framework, and is in operation at the clients site.   It is executed as a normal compiled Windows 64bit application (.exe) and loads the main AppBuilder run-time class library (.dll) which executes in-process with the application.   This application was developed by me in under 2 days using Visual Studio 2019 and c#/.Net 4.8.   It contains no code other than the application entry point function which instantiates the AppBuilder object.

This is the main browse screen of the Customer database table.
The user can perform searches, filter the dataset, sorting and can modify the format of the grid.   The navigation bar on the left allows the user to change to another module which displays related screens.   Relationships between the data items is represented visually in this control with indentation, and are maintained automatically by AppBuilder.   Every browse screen looks and works exactly the same, regardless of what database table it uses and even across all applications.   The following screenshots show this consistency, and it was one of the first class directives when developing AppBuilder.

This is a browse+input screen of a child table, which lists each product of the selected customer location.
[Note: I will be adding more detailed information for these screenshots during 09/2020. Please contact me if you have any questions about my software.]

These are tasks the user has scheduled for the above selected product/unit.
The user performs scheduling of tasks and all other management tasks by using the web-application (customer portal) which they access from the web-browser on any laptop or cell phone.

The product manager maintains the company inventory of products exactly the same way as managing customers.   The consistency in the UI provided by AppBuilder means less work for the developers and much quicker learning for the end-users.   It also means that implementing changes to the UI or adding new features requires a fraction of the time it would normally take.

This screen allows the product manager to configure each product by declaring every component here.   The reason this is such a powerful feature is because the universal software platform I have developed must know the specifics of each product.   That includes firstly what GPIO pin number it is connected to, and whether the software should read or write to the component and if so is it a digital device or analog?   Every detail about each component is stored in the database, which means that when the client creates new products in the future (after the development project has been completed) no changes to the control software will be required.

This screen shows an audit table which is used to log every command passed between the product controller and the server software along with the results returned by the command processor software.   Very detailed information is logged about the product, customer, software versions etc. and any errors handled.   The product manager can use this to monitor the specific activity of a customer or specific unit in the field.

This screen displays all the details for the command transaction selected on the previous screen.

Copyright © 1999-2021 by David A Invenio - All Rights Reserved - Unauthorized Use or Duplication Prohibited