To create an online information system that allows the DPWH Region VIII Leyte 2nd Engineering District to effectively monitor the contractors' payments for their bond. The system does not handle the payment only the registration of the payment used in the monitoring. Users of the system cannot create their own username and password, but this must be requested from the system administrator.
The assistant district engineer is given responsibility by the chairman of the inspectorate team. The Highway Performance Monitoring System (HPMS) is a national (US) level highway information system that includes data on the extent, condition, performance, use, and operational characteristics of the nation's highways. The main purpose of HPMS is to support a data-driven decision-making process within FHWA (Federal Highway Administration), DOT (US Department of Transportation) and Congress.
The Insurance Information System (INSIS) is extremely flexible and highly configurable to meet specific product and administration rules of the insurance company. This information is analyzed in a central computer that helps the airport in managing.
Theoretical Framework
A Monitoring Engineer will be responsible for monitoring the acceptance/guarantee payments for the projects. One year after the completion of the project, the bond previously provided expires and the project will be inspected for deficiencies. If a project is damaged, the department finds out from reports from citizens who use the projects.
Once a report is filed, the Assistant District Engineer, acting as the Chairman of the Inspectorate Team, sends a team to investigate. Contract sureties include: bid bonds, which provide financial assurance that the bid has been submitted in good faith and that the contractor intends to enter into the contract at the bid price and provide the necessary performance and payment guarantees; performance bonds, which protect the owner against financial loss if the contractor fails to perform the contract in accordance with its terms and conditions; payment bonds, which guarantee that the contractor will pay certain subcontractors, laborers and material suppliers in connection with the project; maintenance bonds, which usually guarantee against defective workmanship or materials for a specified period; subdivision bonds, which guarantee to a city, county, or state that the principal will finance and construct certain improvements such as street, sidewalks, curbs, gutters, sewers, and drainage systems. Commercial surety bonds guarantee fulfillment of the principal amount of the obligation or liability described in the bond.
Commercial surety bonds include: License and permit bonds, which are required by state law or local regulations to obtain a license or permit to engage in a particular business, e.g. Litigation court bonds include injunction, appeal, indemnity to sheriff, mechanic's lien, attachment, replevin and admiralty; Public official bonds, which guarantee a public official's performance of duty, e.g.
Design and Implementation
LicenseNo Char(20) Contractor's License Contractor Name Char(50) Contractor/Firm Name Address Char(100) Contractor's Official Address Email Char(50) Contractor's Email Address. PrevLicenseNo Char(20) Previous Contractor ID LicenseNo Char(20) Contractor's License ContractorName Char(50) Contractor/Firm Name Address Char(100) Contractor's Official Address Email Char(50) Contractor's Email Address. EditedBy Char(20) Username of the issuer of the order Comment Char(100) Comment made by clerk to the officer LastEdit DateTime Date and time of last modification.
Warranty Period Integer Project Warranty Period NextPayment Date Next Payment Date Payments Made Full Number of Payments Made Annual PayableAmt Actual Annual Payable Amount. Approved Number ('Yes', 'No') Char Approved Official Approval Indicator (30) User who approved the payment.
WARRANTY MONITORING
SYSTEM
Result
As with most websites, the left part of the screen is the navigation buttons (in the case of Figures 19-24 for the monitoring engineer) and the right part is the interface section. The screen mainly consists of a list of artists that the system has, a search button, and due to the small size and simplicity of the data, an entry for adding new data is also included. As in the previous screen, the content of the navigation buttons is the same because the user is still the supervising engineer.
Additionally, when the user clicks on one of the projects listed in Figure 22, the project details such as Project ID, Contractor Name, Grant Amount, Structure Type, Warranty Period are displayed (as shown in Figure 21). The screen has two columns, the left side shows the original data in the user guidance system, and the right side is the new data input. The screen shows two things, projects that have a payment due and projects that will be paid in a month.
It also gives the user the option to create an auto-generated letter to print or send an auto-generated email (if available) to the contractor. As expected, the set of buttons on the navigation system differs from those of the control engineers, as each button corresponds to different functions for the users. The top screen shows the project's details and the bottom shows its previous payment records (this is hidden by default, but can be shown by clicking Past Payments), while the central part of the screen shows payments that have yet to be approved and registered.
The screen lists projects that have been completed for at least a year and are ready for on-site review. If the project passes the inspection, the user only needs to click the button to the right of the entry to accept the project to be monitored by the system. A Photo Manager button is also displayed on the screen, when the user clicks on it, he is redirected to the photo management section of the system.
The upper part allows the system administrator to upload and write descriptions of photos of the project, while the lower section displays the photos and their descriptions. The first allows the user to change the description of the photograph, and the second deletes the image completely. This shows the username, the data associated with it (except the password) and the options to enable/disable users and/or reset their passwords to be the same as their usernames.
It works the same way as adding entry for project, contractor and payment information.
Discussion
This transparency and its structure that reduces the chance of data tampering protects the integrity of the warranty monitoring procedure. The system is only a prototype, so only the basic functions are included and there is a lot of room for improvement and possible integration on other DPWH systems. Being able to handle the payments with a barcode scanner or another method will greatly increase the use of the system.
Conclusion
Recommendation
Bibliography
I am grateful to all the teachers who have taught me, but I am most grateful to the most helpful teachers I have had - Dr.
