Web-Platform to administrate Company Knowledge, Error Tickets (like osTicket) and Improvement proposals

Project aim: Delivering a web platform (multi language support: English and German) that allows users from different companies (after login verification) to address and administrate tickets in their company within these 3 main categories 1) Knowledge 2) Problems 3) Improvements. Attached you'll find a pdf file of the 1st draft to get an idea. (When being logged-in and pressing e.g. "Problems" a window opens where the issue can be entered) Note: A possible way could be to extend the free osTicket solution to manage multiple companies with specific company setups. Scope: Focus on technical functionality - very professional graphical design isn't scope at this stage to the project. Usage of a CMS is preferred but not mandatory. The developer may use the technologies he/she prefers get the work done. In case of usage commercial modules be aware that this may not result in recurring costs or in maintenance issues in the future. Requirements: User Logon/Registration to access the company's portal. A logged-on user is: 1) related to a company and a department 2) may be responsible in a specific department to release, edit o reject improvements and knowledge from that specific department 3) may be defined as responsible to access and handle addressed Problems from a specific sub-category 4) may be defined as the administrator within the specific company that is able to edit settings like users/roles/cagetories/company name and logo. The user may view 1) all the tickets he addressed with its status 2) new released knowledge and improvements related to his department 3) new released problems related to his department 4) tickets that are addressed to him (e.g. in case this user is defined as department/sub-category responsible) This information is displayed on the user's page after logon. The user may search the knowledge database and see the articles. Depending on category, sub-category and priority the company administrator can define if further an email notification will be submitted to the recipient when creating a ticket. All tickets have a title, a (sub-)category and a description (WYSIWYG editor to allow input pictures - see osTicket or [login to view URL]) "Problems" further have the field "Priority", "Quality cost" and the cost selection field with "once" or "per year" "Improvements" further have the field "Savings" and the savings selection field with "once" or "per year" Code/Project should be easily adaptable in case of provider/domain change. Nice to have: - When a unknown user tries to register from a unknown company: access to a test database with test data to check the features Deliverables: - Source code/ Brief documentation - Brief explanation how to set up different languages (so I can use it in German environments as well) - GoLive of a solution on [login to view URL] for acceptance test Please feel free to offer alternative solutions/examples that matches the main requirements. Don't hesitate to contact me in case of any questions to clarify the requirements for the project offer! Budget: Technical solution as described max USD 400