Attribution and confidentiality: This engagement was completed by Mossia team leadership in a prior software engineering role as part of a wider delivery context. The organization name, private screens, sensitive records, and unsupported metrics are withheld.
Context
The operating environment
An operations-heavy packaging environment required structured records and business controls across several related workflows. The system needed to support the day-to-day operation while remaining understandable enough for continued feature work and reporting changes.
Problem
What needed to change
Operational information and approvals needed a consistent shared system. Modules could not be designed as disconnected forms: assets, contracts, reimbursements, tax handling, reports, user roles, and other records had relationships and downstream effects that needed a coherent application and database model.
Role
Responsibility in the wider work
Application engineering and ERP workflow delivery in a prior role as part of a wider software team.
Constraints
What shaped the solution
- Multiple operational modules sharing users, records, approvals, and reports
- Business rules that had to be clarified with operational stakeholders
- Ongoing change after initial implementation
- A server-rendered Symfony application and PostgreSQL data model
- Confidential business information that cannot be shown publicly
Approach
How the work was handled
- Translated operating workflows into roles, records, states, validations, approvals, and report requirements.
- Kept shared business concepts consistent across modules instead of duplicating them in separate tools.
- Used Symfony and Doctrine patterns that allowed the application to evolve through maintainable modules.
- Implemented practical interfaces and reports around real staff tasks rather than generic ERP terminology.
- Supported continued delivery by keeping database, application, and deployment concerns visible.
Solution
What the delivery established
- A shared ERP application foundation for operational workflows
- Role-aware records and approval paths
- Modules spanning assets, contracts, reimbursements, tax and reporting contexts
- PostgreSQL-backed data relationships and Symfony application logic
- A maintainable base for subsequent changes and operational reporting
Outcome
What can be stated responsibly
- Related operational records became manageable through a common system rather than isolated tools.
- The shared application provided a foundation for continuing modules and reporting.
- The work demonstrated the importance of workflow and data relationships before interface polish.