Automatic digital as-built database populator and construction material delivery location estimator

An automatic digital as-built database populator, comprising:

• a first server configured to receive, via a computer network, electronic load tickets, wherein each electronic load ticket:
• (a) represents a respective load of construction material hauled to or from a construction site by a respective vehicle;
• (b) lacks data indicating a construction site location to or from which the load was hauled;
• and (c) comprises:
• (1) an identification of a kind of construction material in the load;
• (2) a time associated to the electronic load ticket;
• and (3) chain of custody data about the construction material in the load;
• a first electronic database coupled to the first server and configured to automatically store at least a subset of the electronic load tickets received by the first server;
• a second server configured to receive, via the computer network, construction equipment sensor data comprising electronic operational data from sensors of a plurality of pavers, wherein each operational datum comprises:
• (a) data identifying a then-current operational mode of the respective paver;
• (b) data identifying a location of the paver when the paver operated in the operational mode;
• and (c) data identifying an operational time at which the paver construction equipment operated in the operational mode at the location;
• wherein the second server is further configured to receive, via the computer network, electronic operational data from a plurality of rollers, wherein each operational datum comprises:
• (a) data identifying a then-current operational mode of the respective roller;
• (b) data identifying a location of the roller when the roller operated in the operational mode;
• and (c) data identifying an operational time at which the roller operated in the operational mode at the location;
• a second electronic database in communication with the second server and configured to automatically store at least a subset of the operational data received by the second server;
• a filter configured to automatically select, based on contents thereof, a subset of the electronic load tickets stored in the first electronic database, such that the subset includes only load tickets associated to a preselected construction project;
• and
• a third server configured to, for each electronic load ticket in the subset:
• automatically select a selected operational data in the second database, each of the automatically selected operational data respectively comprising:
• (a) data identifying the operational mode as indicating operation by the respective paver at the preselected construction project;
• and (b) data indicating the operational time is within a tolerance of the time associated to the electronic load ticket;
• automatically determine, from the data identifying the location of the respective paver comprised in at least a portion of the automatically selected operational data, an estimated location where the construction material represented by the electronic load ticket was operated on by the respective paver, wherein the estimated location is based on the location of the respective paver comprised in an automatically selected operational datum;
• automatically smooth one or more of (a) the data identifying the location of the paver or (b) the estimated location where the construction material represented by the electronic load ticket was operated on by the paver based on the data identifying the location of the roller of the second server;
• and
• store the estimated location in the first database in association with the electronic load ticket to thereby generate a respective digital as-built on demand record for the preselected construction project;
• wherein the digital as-built on demand record is concurrently accessible by a plurality of users to visually render a representation corresponding to the electronic load ticket and the respective estimated location.