Professional Documents
Culture Documents
ITCMSY2 - Milestone 2
ITCMSY2 - Milestone 2
Milestone 2
Streamlining Inventory Management:
A Case Study on Cloud Integration for Enhanced POS and
Inventory Tracking at Kwik-E-Mart
Additionally, the group also researched optional, but useful tools and services that
may be implemented into the cloud system integration if the budget permits it. The group
found options for an extra NoSQL database that may be used for faster and more efficient
report generations, as well as a AI/Machine learning forecasting service that can be fed
info in order to generate more and more accurate
INNOVATION
Category AWS Google Cloud Microsoft Azure Description
Amazon Fully managed Google Cloud Fully managed Azure Cosmos Globally These are
DynamoDB NoSQL Bigtable NoSQL DB distributed NoSQL
database for fast database for NoSQL database
and scalable large-scale database for services that
storage and storage and storing and offer highly
retrieval of real-time access retrieving scalable,
unstructured to structured structured and low-latency, and
data. data. unstructured globally
data. distributed
Database storage for
unstructured or
semi-structured
data. They are
designed for
applications that
require high
throughput and
low latency data
access.
Amazon Machine Google Cloud Machine Azure Machine These services
Forecast learning-based AI Platform learning Forecasting learning-based provide machine
service for platform for service for learning-based
accurate and training, accurate and forecasting
automated deploying, and automated capabilities to
forecasting. managing forecasting. predict future
models on trends or
Analytics & Google Cloud. patterns in your
Machine data. They offer
Learning automated
model training,
evaluation, and
deployment,
making it easier
to build accurate
forecasting
models.
Figure 1.1 - Optional Public Cloud Products and Services Comparison for Innovation and Redundancy
Figure 2.0 - Business Process Modeling Notation for Kwik-E-Mart’s Old Inventory Management System
The proposed solution for this case study is on the enhancement of the POS and
inventory management system by shifting it into the cloud. This could provide
automation and optimization in stock tracking which could greatly improve the store’s
inventory management practices that would tackle the case study’s main problem
statement. Furthermore, the proposed solution would solve the inefficiencies and
inaccuracies of the manual stock checking practices that the company employs by
directly tackling the root cause of the problem.
III. Proposed Solutions
A. Chosen Cloud Computing Tools and Services
The proposed system will provide realistic changes to enhance the store’s
inventory process for managing. Subsequently, it would also improve customer
satisfaction and stock inventory reliability. Higher management will also be aided
because a centralized and monitored inventory management system will allow them
real-time visibility into stock levels, make informed decisions, and properly assess and
communicate with lower management.
Figure 3.0 - AWS Service Architecture
The system will consist of multiple AWS products and services in order to ensure
the consistency and seamless functionality of the system, which will be integrated into an
app to be used as both a POS system and inventory management system. The following
are the selected AWS products and services:
● Amazon Elastic Beanstalk: To be used in the application layer for the deployment
and management of applications, its auto scaling feature allows the application to
handle varying levels of traffic efficiently across the different branches.
● Amazon RDS: To be used to provide a managed relational database, with features
like data redundancy, backups, and scalability, to ensure the safe keeping of stock
data.
● Amazon S3: S3 provides object storage for storing static files, such as order
reports and product documentations, which will be used for the graphical user
interface of the application for higher management.
● Amazon SQS: To be used for message queuing, in order to send alerts to higher
management about any alerts regarding each branch. It can help higher
management perform inventory-related tasks asynchronously, by allowing them to
have an easier way to manage lower management, ensuring smooth operations.
● Amazon API Gateway: Will act as an entry point for external applications, APIs,
and services to interact with the inventory management system. Additionally, it
will serve as a centralized hub for request routing, authentication, and
authorization, which ensures secure and controlled access to the inventory
management system.
● Amazon Lambda: To be used to execute business logic and processing tasks, and
will be integrated with other services, such as RDS and SQS, to perform
inventory-related operations and handle data processing efficiently.
● Amazon CloudFront: To be the content delivery network (CDN) provider used to
improve the performance and availability of the application, as well as cache
static assets, reduce latency, and enhance overall user experience.
● Amazon CloudWatch: Will be used to collect and track various metrics, logs, and
events from different components of the system, which enables proactive
monitoring, alerting, and troubleshooting, ensuring the inventory management
system's stability and performance.
● Amazon IAM: To enforce secure access control, adhere to the principle of least
privilege, and ensure the overall permission security with the application and
database layers of the system.
● Amazon DynamoDB: a NoSQL database service that can be used for fast and
scalable storage of non-relational data, specifically for report generation and
redundancy. While optional it can complement the relational database (RDS) and
provide additional flexibility in the case that Kwik-E-Mart needs it for future
proofing purposes.
B. Pricing Estimate
To compute the pricing estimate, the group utilized the AWS Pricing Calculator,
which can be found in this link. The group inputted their assumptions for the percentage
of system use based on the utilization and size of Kwik-E-mart for the application, and
came up with this estimate summary:
Some of the services, such as Amazon CloudWatch, AWS Identity and Access
Management (IAM), and Amazon Simple Queue Service were free of charge, while most
had on-demand pricing. Additionally, AWS Elastic Beanstalk was also for free or charge
because its fees are already included in the Amazon S3 bucket instance that we chose.
For Amazon CloudFront, we assumed that there would be around 90GB per
month of data transfer and outflow, which would amount the total cost to around USD
9.45 monthly. AWS Step Functions brought only around USD 0.10 of cost monthly. For
Amazon Redshift. We chose a single dc2.large instance with 2 vCPU’s and 15 GB of
memory, which amounts to around USD 120.45 monthly. For Amazon S3, we assumed
the use of around 1TB which costs around USD 25.00 per month. For Amazon API
Gateway, we assumed an average of 4.5 million requests per month, which amounts to a
cost of USD 5.63 monthly. For Amazon RDS, we chose one db.m3.medium instance,
which has 1 vCPU, 3.75GB of Memory, and an average of 25% resource utilization,
which brings its monthly total to USD 78.36. For the other optional services, such as
Amazon DynamoDB and Amazon Forecast, we assumed approximately 100GB of usage
for DynamoDB and 100 hours of training per month for Forecast. The total cost for
DynamoDB would amount to USD 28.50, while the cost for Forecast would be USD
32.80.
In summary, the total cost of ownership (TCO) for one month of our proposed
cloud system integration including the optional services for AI forecasting and
DynamoDB for faster report generation would amount to around USD 300.20 monthly
and USD 3,602.40 annually. Without it, it would only cost around USD 238.9 monthly
and USD 2,866.8 annually.