Our production system runs on Actian Ingres 11.2 with a front-end written in OpenROAD 6.2. The codebase has begun to show its age, and I now need regular maintenance that focuses on two fronts: squashing existing bugs and delivering small, well-scoped feature updates that keep the application relevant for our users. Current pain points • Functional errors inside the data-processing routines occasionally crash long-running jobs. • Data-integrity problems in the reporting module create mismatched totals and duplicate rows. Scope of work 1. Investigate and resolve those functional and data-integrity issues. A short write-up explaining root cause, steps to reproduce, and the applied fix must accompany every patch. 2. Implement agreed-upon feature enhancements without disrupting existing workflows. Each new feature should follow our present OpenROAD 6.2 GUI conventions and leverage native Ingres capabilities whenever possible. 3. Provide clean, version-controlled source updates along with an incremental database script (DDL/DML) so I can promote the changes through staging to production. 4. Run basic performance and regression tests after each change to confirm that no new errors appear in data processing or reporting. Acceptance criteria • All critical jobs in the data-processing layer complete without runtime errors. • Report outputs match the underlying tables with zero duplicate or missing records. • New features compile and run on a vanilla Ingres 11.2/OpenROAD 6.2 setup. • A concise change log and rollback script are supplied for every delivery. I handle deployment myself, so the deliverable is limited to patched source, scripts, and documentation. If you have deep experience with Actian Ingres internals, Embedded SQL, and the OpenROAD 4GL, you will feel right at home on this project.