Since the warehouse manager is now hosted (the database is in a data center), extensive changes had to be made in the database.
Because a local network installation can largely ignore performance issues, it's very different when the SQL Server is installed in a remote data center.
In particular, I worked extensively on the following points:
The client rated the work as very good. He is satisfied with the performance and stopped looking for a new system.
2023 was focused on the pharmaceutical industry. Our last client had special documentation requirements that needed to be added to the software.
Extended the ILSE Warehouse Manager with ERP functionality (quotes, orders, purchase orders, incoming/outgoing invoices, dunning letters) for an organic food manufacturer.
Extended the software to meet the requirements of the food industry (best-before dates, batch tracking, supplier control, returnable packaging management, etc.) for an organic food manufacturer.
Development, database extensions, project management (2 other developers were involved).
Implemented extensive extensions to the ILSE Warehouse Manager to create export documents and support multiple currencies (euro, dollar).
Created detailed documents, carried out very detailed imports, and implemented various commission payment calculations. The ILSE Warehouse Manager is still used as the base.
Implemented extensive extensions in our standard software without losing the ability to update. This is done through comprehensive configuration.
Extended the ILSE Warehouse Manager with inventory management functionality (quotes, orders, purchase orders, incoming/outgoing invoices, dunning).
The second part was extending the software to meet the requirements of the food industry (best-before dates; batches, supplier control, empty container management, etc.).
Development, database extensions, project management (two other developers were involved).
Development of a production control system.
We developed a system to manage goods receipts, goods issues, stock levels, and recipes. The special feature was creating production orders. Individual components were selected and sent to a central controller (S7). Mixing speed and temperature could also be sent to production. Production results were sent back (quantity, various measurements).
The tasks covered the full spectrum: effort estimation, requirements specification, implementation, coordination with the customer and other involved companies, on-site testing (4 weeks in Switzerland), acceptance, and ongoing support.
MS Access was used as the initial database, later replaced by MS SQL Server. The central controller was an S7 (Siemens), and communication was handled with WinCC (reading and writing variables).
This software formed the basis for the ILSE Warehouse Manager that we developed from it and that is still in use.
In April 2006, Mr. Popp approached me to see if I was interested in buying his company. He developed software for industrial scale integration and tire storage software.
After a long evaluation phase, I decided, through my then-company (implements GmbH), to take over the business.
Since then, we have been on the market with the following products (my main focus is on the ILSE Warehouse Manager):
My general tasks are:
Customer contact and software development are equally important tasks. Depending on requirements, I also create concepts. Meanwhile, I have started creating concepts even for internal extensions.
In software development, besides a self-explanatory user interface, database structure is crucial. The ILSE Warehouse Manager uses about 50 tables, all built on the same principle. The record ID is a GUID that identifies each record. Naming, internal management fields (when the record was created, by whom, and when the last change was made) also follow a naming syntax.
Another very important point is SQL queries: complex queries are offloaded to stored procedures or functions. These can become very extensive. The advantage is that these database-side logics can also be used by mobile devices (scanners), for example.
Project performance depends on a well-structured and designed database (e.g., don't forget indexes).
The ILSE Warehouse Manager is mainly used by small and medium-sized companies. Notably, Framatome uses the Warehouse Manager at two sites.
On the other hand, two food manufacturers use our software. All customizations are integrated so that updateability is maintained.
A planning tool was created for the Lidl Foundation to enable consolidation of the individual business units.
Great emphasis is placed on the GUI. All procedures that read from the database are implemented as packages.
My tasks:
Software: VB.net 2003, VB.net 2005, Oracle 10, PL/SQL, Oracle Raptor, SQL Plus
Completing software for an ERP system.
An ERP provider went bankrupt. Our task was to finish the software, fix bugs, and then expand the software with new modules.
Project size:
The activities only partly covered programming. Another focus was creating the functional specification and documentation.
Software: VB 6.0, VB.net, ADO, ADO.net, MS SQL Server 7/2000, caseStudio (Charonware), Document!X (innovasis)
Project Textile Database (since 09/2003):
The goal of the CRM project is to provide textile retailers with aggregated data that allows them to compare themselves with other retailers.
The buying behavior of customers is also analyzed to make better forecasts.
This project is a strategic project where I am responsible for the architecture and implementation. Team size: 3-5 people.
The data comes from different sources and is merged in the "Textile Database".
Database scope: approx. 500,000 customers, approx. 3,000,000 line items.
Another task was creating reports with Crystal Reports (8.5).
Automated Customer Import Project (Duration: 07-09/2003):
At the moment the data is imported from external systems "by hand". This was automated (with output of faulty records, import logs, etc.).
Software: VB.net, MS SQL 2000, CaseStudio 2.0 (case tool), Visio (class modeling), Crystal Reports.
Note: The software I developed uses a class model based on a 3-tier architecture. This means that the GUI only knows the business objects, the BOs know the database, etc. This approach makes it possible to use the same business objects for different applications. For example, you can create a VB application and reuse the business objects in ASP.net. Another big advantage is in maintaining the applications. The underlying classes are identical, so handing over to external/internal developers goes smoothly.
Development of a time tracking software.
The product now runs successfully in several companies. Project management and coordination, partly self-developed, UI and database design (05/2002 - 06/2003 full-time).
Great care was taken to create a "clean" class design that allows the application to run as a 3-tier application.
Software: Delphi 6.0, Interbase 6.0.1, Star Designer, IB Expert
BUS 2.0 (Advisor Support System) for Dresdner Bank AG.
Software: Siebel 6.3, Siebel Tools, MS Access 97
Software: Siebel 99.5 Server, Siebel Tools, VB 6.0
Visualization of insurance data.
Activities:
Software: VB 6.0 Enterprise, Oracle 8.0, Rational Rose 98, Windows NT 4.0, Farpoint Spread 3.0
Fund management system.
Tasks:
Software: Clipper 5.2e, Novell/ WinNT 4.0
Automatic bidding system.
Tasks:
Software: Clients: WinNT 4.0 WS, Server: WinNT Server, Oracle 8.05, Rational Rose 97, Star-Designer 5.1, VB 5.0 Enterprise, Farpoint Spread 3.0
Class modeling and tool development.
Tasks:
Software: Siebel Automation Marketing (SAM), Oracle, MS-Access97, VB 5.0, PL/SQL, Excel VBA
Discover other experts with similar qualifications and experience
2025 © FRATCH.IO GmbH. All rights reserved.