Subject Name:

Number:

Student :Name

Number:
Table of Contents
Introduction......................................................................................................................................3

SQL Code Name..............................................................................................................................4

SQL Query.......................................................................................................................................5

Global Waste Management Security and Privacy Policy..............................................................11

Query View....................................................................................................................................13

Poster.............................................................................................................................................19

Conclusion.....................................................................................................................................20

References......................................................................................................................................22
Introduction
It is a well-known fact that the world is changing at an incredibly fast pace and it becomes more
and more important to minimize the amount and impact of the wastes produced in the
environment, it is also an important factor that with the tendency of population growth the
question of city sanitation becomes very important as well. Global Waste Management (GWM)
is one of the promising organizations to supply waste collection services in NSW, Australia, but
the increasing crow of customers, types of wastes, types of vehicle, and human resources when
the organization operates at the national level become an important challenge (Shittu et al.,
2021). Traditional, primitive ways such as the use of paperwork to keep records of orders, the
different types of waste, vehicles and manpower, as well as financial transactions had been
embraced at GWM (Hossain et al., 2024). Although for the initial years of growth in the
organization’s structure this system may have been effective, it has proven to be largely
ineffective as the organization’s operations expanded. The manual system made response time
very slow, data was often incorrect and not reliable, resources were wasted and managing
customers’ requests was a problem which hindered the company’s growth due to increased
demand.
SQL Code Name
Here is all the SQL Code Name given below:

 Create Table for Customer Entity

 Create Table for Personnel Entity

 Create Table for Vehicle Entity

 Create Table for Rubbish Categories Entity

 Create Table for Smart Tins Entity

 Create Table for Ordering System Entity

 Create Table for Financial Management Entity

 Create Table for Council Administration Entity

 Create Table for Council Dump Management Entity

 Create Table for Council Recycling Facilities Entity

 Create Table for Outsource Management Entity

 Create Table for Business Intelligence Entity

 Create Relationships between Entities

DROP DATABASE IF EXISTS TheWasteManagement;

CREATE DATABASE TheWasteManagement;

USE TheWasteManagement;

Customer Table

CREATE TABLE Customer (

customer_id INT PRIMARY KEY,

name VARCHAR(100) NOT NULL,

address VARCHAR(255),

phone_number VARCHAR(15),

email VARCHAR(100),

created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP

);

Personnel Table

CREATE TABLE Personnel (

personnel_id INT PRIMARY KEY,

first_name VARCHAR(50),

last_name VARCHAR(50),

role VARCHAR(50),
 hire_date DATE,

salary DECIMAL(10, 2),

department VARCHAR(100)

);

Vehicle Table

CREATE TABLE Vehicle (

vehicle_id INT PRIMARY KEY,

vehicle_type VARCHAR(50),

license_plate VARCHAR(15) UNIQUE,

capacity DECIMAL(10, 2),

assigned_personnel_id INT,

FOREIGN KEY (assigned_personnel_id) REFERENCES Personnel(personnel_id)

);

Rubbish Category Table

CREATE TABLE RubbishCategory (

category_id INT PRIMARY KEY,

category_name VARCHAR(50) NOT NULL,

description VARCHAR(255)

);

-- Inserting categories

INSERT INTO RubbishCategory (category_id, category_name, description)

(1, 'Mixed Rubbish (Light)', 'Gardening materials, household items...'),

(2, 'Building Materials (Heavy)', 'Soil, bricks...'),

(3, 'Concrete', 'Only concrete removal'),

(4, 'Dirt', 'Only soil');

Smart Tins Table

CREATE TABLE SmartTins (

tin_id INT PRIMARY KEY,

tin_size VARCHAR(50),

location VARCHAR(255),

category_id INT,

FOREIGN KEY (category_id) REFERENCES RubbishCategory(category_id)

);

Orders Table

CREATE TABLE Orders (

order_id INT PRIMARY KEY,

customer_id INT,

tin_size VARCHAR(50),

assigned_vehicle_id INT,

assigned_personnel_id INT,

order_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP,

FOREIGN KEY (assigned_vehicle_id) REFERENCES Vehicle(vehicle_id),

FOREIGN KEY (assigned_personnel_id) REFERENCES Personnel(personnel_id)

);
Financial management Table

CREATE TABLE FinancialManagement (

transaction_id INT PRIMARY KEY,

order_id INT,

amount DECIMAL(10, 2),

transaction_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP,

FOREIGN KEY (order_id) REFERENCES Orders(order_id)

);

Council Administration Table

CREATE TABLE CouncilAdministration (

council_id INT PRIMARY KEY,

locality VARCHAR(100),

contact_info VARCHAR(255)

);

Council Dump Management Table

CREATE TABLE CouncilDumpManagement (

dump_id INT PRIMARY KEY,

council_id INT,

location VARCHAR(255),

capacity DECIMAL(10, 2),

FOREIGN KEY (council_id) REFERENCES CouncilAdministration(council_id)

Council Recycling Facilities Table

CREATE TABLE CouncilRecyclingFacilities (

facility_id INT PRIMARY KEY,

council_id INT,

facility_location VARCHAR(255),

capacity DECIMAL(10, 2),

FOREIGN KEY (council_id) REFERENCES CouncilAdministration(council_id)

);

Outsource Management Table

CREATE TABLE OutsourceManagement (

outsource_id INT PRIMARY KEY,

company_name VARCHAR(100),

vehicle_id INT,

personnel_id INT,

contract_start_date DATE,

contract_end_date DATE,

FOREIGN KEY (vehicle_id) REFERENCES Vehicle(vehicle_id),

FOREIGN KEY (personnel_id) REFERENCES Personnel(personnel_id)

);

Business Intelligence Table

report_id INT PRIMARY KEY,

report_name VARCHAR(100),

report_data TEXT,

generated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP

);

Relationship Between Entities

All relationships are already created in the previous queries using `FOREIGN KEY` constraints.
Global Waste Management Security and Privacy Policy
This paper explores the significance of efficient waste management which in current dynamic
world is essential for the environmental sanity as well as sanitization of developing cities. GWM
a well-established waste collector firm in NSW, Australia currently in the process of growing
nationwide to meet the needs of its expanding clientele base faces the rising duality of the
number of customers, types of wastes, the number of vehicles and workers within the firm. For
example, previous to integrated system implementation at GWM, orders were documented using
paper-based files, categories of wastes recorded on paper and so on, vehicles and workforce to be
deployed and financial transactions documented all on paper (Ribeiro-Navarrete et al., 2021).
Although this was healthy in embryonic development, this system has emerged as a problem
with growth in the organizational structure. The manual system wrongly depicted the company’s
response time, frequently contained erroneous data, wasted valuable resources and failed
miserably when it came to managing the voluminous number of customer requests that flooded
the company due to escalating demand.

The objective of this venture was to develop and integrate an online backup solution that would
otherwise decrease GWM’s waste management cycle. When moving from using files to using
files using manual and a paper-based system converting to a centralized relational data base
GWM intended to et better accuracy ,more efficient and scalable. The new system would
comprise customer order management, vehicle and personnel scheduling, waste type and
financial transaction processing which would ease out management challenges that are
associated with the current manual system (Ismagilova et al., 2022). By doing so GWM expected
to enhance custoIn this way at Global Waste Management (GWM) we take a lot of care in
protecting the identity and other details of the customers as well as operational details. This
policy explains how we manage personal information collected from you through use of our
services. Access and usage of our services are governed by the policy represented here.
To optimise the provision of the waste management services, GWM receives and stores various
types of data including; identity data (name, address, phone number, email), payment data,
operational data, vehicle and personnel, and other data that depicts how users interface with the
services. This information is used for the following uses: to collect waste, collect payment for
waste, to develop our services, to meet regulatory requirements, and sending out service updates
and promotions.

For increased security of the information, GWM has enforced data encryption, restricted access
to specific personnel in acquisition of the information, constant security assessment, and backing
up of the data in case it is tampered with or lost. We also respect the privacy of data collected
from our customers and we never share their information with any third party unless legally
compelled to do so, necessary to provide services to the client or where the client has provided
express consent.

Customers guarantee their rights regarding their data and have the right to access, correct, erase
or refuse to share their data for commercial purposes. We also collect cookies and tracking
technologies on the website to improve the usage of services and manage cookies from users.

At GWM, many pieces of personal information are only kept for the time needed to perform its
functions or stay compliant with legal requirements, and the corporation follows rules like GDPR
and CCPA. Any changes to this privacy policy will be made through posting on the website or
through customer personalized announcements.

This paper describes the main decisions that were made before designing the automated system,
the problems which the authors encountered during the process of creating this system, and the
indispensable assumptions adopted while transferring to this system. It also details the ideal
strategies for GWM’s present and future business environment and offers an introduction to the
flexibility of the system in response to a fast-growing enterprise.
Query View
All the screen shorts of the query have been taken within the “Action Output” and “schemas”
table viewers.

Customer

Personnel
Vehicle

Rubbish Categories
Smart Tins

Orders
Financial management

Council Administrations
Council Dump Management

Council Recycling Facilities

Business Intelligence
Completed ERD
Conclusion
Global Waste Management (GWM) operates across New South Wales (NSW) and is rapidly
expanding its services throughout Australia. With this expansion, GWM is seeking to transition
from a paper-based waste management system to a fully automated database solution. The new
system aims to solve inefficiencies in tracking customer orders, waste types, vehicle
assignments, financial transactions, and personnel management. By automating these processes,
GWM hopes to increase operational efficiency, reduce errors, and improve scalability. The
design, implementation, and challenges faced in creating this automated solution were pivotal in
transforming GWM’s operations. The first major design decision was adopting a centralized
relational database system. As GWM’s operations grow, managing vast amounts of data through
a single, unified system becomes crucial. The relational database model allows for easy access to
information through structured queries and enforces data consistency using relationships between
tables. For example, customer orders were tied directly to customer details via foreign keys,
ensuring that all relevant data was linked and easily accessible. The decision to use a relational
model allowed for flexibility in scaling, as more data and tables could be added as needed. The
database design also prioritized data normalization, a process of structuring data to minimize
redundancy. By normalizing data, the system ensures that GWM’s data is organized efficiently,
and updates or deletions can be performed without inconsistencies. For example, employee
details such as roles, salary, and department were stored in separate tables rather than repeating
this information for each personnel record. This not only saves storage space but also enhances
the accuracy of updates across the system. Another key design decision was ensuring the
database’s security. With sensitive customer information and financial data stored in the system,
encryption and secure access controls were prioritized. The implementation of role-based access
control (RBAC) ensures that only authorized personnel can access certain sensitive data. For
example, financial records and customer payment information are protected through strict user
access permissions. Additionally, sensitive data is encrypted both in storage and during
transmission, ensuring compliance with privacy laws. Lastly, ensuring the database integrates
smoothly with GWM’s existing systems was a critical design consideration. The new system had
to interface with third-party financial processors and vehicle tracking software. The design took
into account the need for seamless integration between the database and these external services,
ensuring that data could flow without interruption between systems. This integration allows for
real-time updates on orders, financial transactions, and vehicle assignments, which is essential
for managing field operations effectively. One of the most significant challenges faced was the
transition from paper-based to digital systems. GWM had relied on manual, paper-based records
for years, and the shift to a fully automated system required careful planning. Employees who
had become accustomed to the old paper processes had to be trained on the new system.
Additionally, legacy data from paper records needed to be cleaned and accurately migrated into
the new database. This process of data migration was complicated by discrepancies in the
existing records, which had to be addressed before the data could be imported. The scalability of
the system was another major challenge. As GWM expanded its service area, the system needed
to be capable of handling an increasing amount of data. The design included cloud-based data
storage and optimized indexing to ensure the system could manage large volumes of information
efficiently. While GWM was initially operating in NSW, the system needed to be designed with
the ability to scale to accommodate other states and eventually national expansion.

Integrating the new system with external services was another challenge. GWM needed to ensure
that the system could communicate effectively with third-party financial systems, vehicle
tracking solutions, and other operational tools. This required developing APIs and ensuring that
data could be exchanged securely and efficiently across multiple platforms. Testing and
troubleshooting integration points were critical to ensuring that no data would be lost or
incorrectly transferred during the integration process. Another significant challenge was user
adoption. Employees had been used to a paper-based system, and transitioning to a digital system
required retraining and time for adjustment. Staff had to become familiar with the new interface,
understand how to input and retrieve data, and adapt to a new workflow. Resistance to change
was anticipated, but thorough training sessions, along with user-friendly interface design, helped
mitigate this challenge. Feedback from early users was incorporated into the design to ensure
that the system was intuitive and easy to navigate.

Finally, ensuring the security of customer data posed a significant challenge. With the shift to a
digital system, sensitive customer and financial data was now stored electronically. GWM
needed to ensure compliance with privacy regulations, including the Australian Privacy
Principles (APPs) under the Privacy Act 1988. This required implementing robust security
measures, such as encryption and secure access controls, to safeguard the data from unauthorized
access and potential breaches. Several assumptions were made to complete the desired solution.
First, it was assumed that GWM would undergo a gradual transition from paper-based operations
to a fully digital system. This assumption was made to ensure that the company could maintain
business continuity while employees adapted to the new system. The gradual transition also
allowed for better data migration and training for employees, reducing the risk of operational
disruptions. Another assumption was that the new system would be able to scale as GWM
expanded its operations beyond NSW. The solution was designed with the future growth of the
company in mind, including the ability to handle increased volumes of customer orders, financial
transactions, and waste category data. This scalability was ensured by using cloud-based storage,
indexed queries for faster data retrieval, and a flexible database schema that could easily
accommodate new tables and data fields as needed. It was also assumed that external integrations
with financial systems, vehicle management software, and other tools would be successful.
While third-party systems could introduce potential compatibility issues, it was assumed that
APIs would allow for smooth integration, ensuring that data could flow seamlessly between
systems. To mitigate the risk of integration issues, extensive testing was conducted to ensure
compatibility. The solution assumed that ongoing support and training would be necessary for
GWM employees. As the system evolved, regular updates and training sessions would be
required to ensure that staff remained proficient in using the new system. This assumption was
made to ensure that GWM could continue to leverage the benefits of the system as its operations
grew and its technology evolved.
References

Hossain, M. A., Ferdous, N., & Ferdous, E. (2024). Crisis-driven disruptions in global waste
management: Impacts, challenges and policy responses amid COVID-19, Russia-Ukraine war,
climate change, and colossal food waste. Environmental Challenges, 14, 100807.

Ismagilova, E., Hughes, L., Rana, N. P., & Dwivedi, Y. K. (2022). Security, privacy and risks
within smart cities: Literature review and development of a smart city interaction
framework. Information Systems Frontiers, 1-22.

Ribeiro-Navarrete, S., Saura, J. R., & Palacios-Marqués, D. (2021). Towards a new era of mass
data collection: Assessing pandemic surveillance technologies to preserve user
privacy. Technological Forecasting and Social Change, 167, 120681.

Shittu, O. S., Williams, I. D., & Shaw, P. J. (2021). Global E-waste management: Can WEEE
make a difference? A review of e-waste trends, legislation, contemporary issues and future
challenges. Waste Management, 120, 549-563.