DHTMLX Allocation & Incident Tracking

Hello All, I am looking for a small piece of development work using packages from [login to view URL] You will need to become familiar with all the features that this package has to offer as well as their other components. This is a test project and based on the results of this test I will have more work to be done. [login to view URL] [login to view URL] [login to view URL] [login to view URL] You will need to check out this website and look through all the features and components that are supported. I have the full version of this package and will provide a copy to the successful bidder. The application is going to be used to log and display incidents in a GPS vehicle allocation system. The data should be presented in a grid (this component already exists). The vehicle allocations are stored in a mysql database and it needs to use the dhtmlxconnector component in retrieving the data from the database. The user needs to be able to modify the vehicle allocation through a searchable dropdown list. The second grid will display the vehicle incidents. The user needs to be able to create, modify and delete incidents. An incident can only be created by right-clicking on the vehicle allocations grid and this creates a new row in the incidents grid. The “ref” field is used as the link between the allocations grid and the incidents grid. This value is not editable. The 2 grids are contained within a dhtmlx tabbed pane. This component exists with dhtmlx. Functionality • Display both grids in a tabbed pane (dhtml component). • Load data from database and present in grid. • Use dhtmlConnector for both grids (allocation and incidents). • The grid needs to be searchable using search filters • Need to be able to export to PDF and Excel (this feature is supported by dhtmlx) • Need to be able to search by date and this displays all allocations and incidents for this date • The incidents need to be grouped by service • Need to be able to filter by incident type • Vehicle Registration needs to be to be overridden by selecting a new vehicle in a dropdown. This vehicle list is grouped by Operator Name. • Vehicle Registration needs to be overridden on a per row basis or all matching vehicle registrations. • If a vehicle allocation is changed this will automatically create an incident to reflect this change. • The incidents needs to be stored in a separate table called incidents. The parent “ref” value will need to be stored in the incidents table as well. • Incidents can only be added for current and future dates. • The grid needs to display total number of incidents recorded and total number of unassigned allocations. These needs to be added as rows at the bottom of the grid. Sample Suggested Layout 1. Grid 1 (allocations): Ref, Operator, Date, Service, Route Type, Start Time, Start Location, End Time, End Location, Dir, Vehicle Reg, Driver Name, Incidents, Last Updated 2. Grid 2 (incident): Ref, Operator, Date, Incident Type, Comments, Vehicle Reg, Reported By, Modified Timestamp Mysql Data: I will supply some sample allocations and vehicle data for testing. Types of Incidents • Driver Issues • Incorrectly Allocated • Safety Issues • Breakdown En Route • Complete Journey Failure • Partial Journey Failure • Complete Dupe Failure • Vehicle Accident I am attaching a sample of the type of data you will be dealing with. I will be providing sample data to the successful bidder. Regards Conor.