sql database
Budget: £750 – £1,500 GBP
The project is to convert an existing Excel spreadsheet into a searchable PreSQL database allowing simle searches.
There are 8 principal asset subject record areas. The number of sub-sections vary within each principal subject area.
A visual representation of the top-down system architecture is attached.
The input GUI is also proposed to act as both an input and a search screen.
Data is to be recorded on a linear mileage basis based on a physical location along a defined distance. The input/output should allow for miles and yards as well as km and metres.
Every input/output will therefore show a start and a finish point, eg. 1m 200 yards to 2m 768 yards. Input/output would be recorded as 001-0200 to 002-0768. Mileage will run from 000 to 999 miles. Yardage will run 0001 to 1759 (There are 1760 yards in a mile so converts to the next mile, e.g. 124m 1760 yds becomes 12mm 0000yds).
The data must allow for the start and finish data to be the same to allow a small length record to be created, (e.g for a weld or a bolt).
Assett data will be coded using a simple numbering system where there are variables, e.g. there are two distinct rail prolfiles each one ith a different descriptor. This coding will be supplied. The code will be either a three figure format or a 3 plus 3 figure format with e.g. 057/317
Assett descriptors to be obtained from separate secure look-up pre-populated read only database with drop down menu.
NO requirement to enter data just set up the database.
Database should be capable of being replicated so that it can be used by a series of different non-related users. Database security to be simple username and password with read/write and read only authorities.
There are 8 principal asset subject record areas. The number of sub-sections vary within each principal subject area.
A visual representation of the top-down system architecture is attached.
The input GUI is also proposed to act as both an input and a search screen.
Data is to be recorded on a linear mileage basis based on a physical location along a defined distance. The input/output should allow for miles and yards as well as km and metres.
Every input/output will therefore show a start and a finish point, eg. 1m 200 yards to 2m 768 yards. Input/output would be recorded as 001-0200 to 002-0768. Mileage will run from 000 to 999 miles. Yardage will run 0001 to 1759 (There are 1760 yards in a mile so converts to the next mile, e.g. 124m 1760 yds becomes 12mm 0000yds).
The data must allow for the start and finish data to be the same to allow a small length record to be created, (e.g for a weld or a bolt).
Assett data will be coded using a simple numbering system where there are variables, e.g. there are two distinct rail prolfiles each one ith a different descriptor. This coding will be supplied. The code will be either a three figure format or a 3 plus 3 figure format with e.g. 057/317
Assett descriptors to be obtained from separate secure look-up pre-populated read only database with drop down menu.
NO requirement to enter data just set up the database.
Database should be capable of being replicated so that it can be used by a series of different non-related users. Database security to be simple username and password with read/write and read only authorities.