Final Project Milestone Three
.docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
510
Subject
Information Systems
Date
Jan 9, 2024
Type
docx
Pages
8
Uploaded by MinisterField10017
1
Final Project Milestone Three
Jerome Bowers
SNHU
IT 510
Dr. Boyett
May 27, 2023
2
Final Project Milestone Three
Flowserve’s current ERP, Oracle, is at the heart of the business. Therefore, its replacement must be as functional yet efficient and address the current shortfalls of Oracle. To recap, some of the main issues with Oracle are the repetition of work due to duplicate orders, inexplicably lost orders, and overly complicated tasks when completing user operations. Current System Analysis
Oracle is a cloud-based enterprise resource planning system that allows Flowserve to conduct financial management, procurement, supply chain management, and manufacturing (Oracle, n.d.). Oracle is used in our business worldwide by over 18,000 employees in over 55 countries. Oracle is designed to allow us to conduct business from procurement of materials to disposal of scrap. In between these two states are receipt of materials, movement of materials within the manufacturing process, inventory management, shipping, and receiving.
Inputs
Although Oracle has several inputs, such as customer data, parts data, order information, procurement data, and inventory data, we will focus on one aspect of the system, aftermarket order fulfillment. In aftermarket order fulfillment, the primary input is the order placed by a customer that the warehouse must fulfill. Output
The output is a pick ticket. The pick ticket contains information about the entity placing the order, its name, and its address. Additional data are items ordered, quantity ordered, due date,
part nomenclature, part location within the warehouse, and QR codes. All of this data is necessary for order fulfillment. Process
3
The order process is as follows: the customer orders parts for pumps needing replacement. Oracle searches the inventory to ascertain the availability of parts. If parts are available, a pick ticket is dropped so that material handlers can pick, pack and ship. Upon shipping verification, shipping data is sent to the customer with EDD, and an invoice is generated by accounting for payment by the customer. Current Issues
One of the most significant issues with Oracle is the loss of orders, specifically in the aftermarket division. Daily pick tickets are dropped for fulfillment. However, some orders fail to drop, leading to missed deadlines if not caught. There is a manual way to drop these tickets, which leads to duplicate orders. If the same orders are worked, there is a loss of productivity. Business Process Model
The business process for Flowserve is simple for the aftermarket team. Orders are processed electronically or via phone calls. All orders are processed using the Oracle ERP. In this model, we will assume that the warehouse stocks the material. A pick ticket will be generated in the warehouse. The material handlers will retrieve the parts. Once picked, the order will be packed, shipped, and received by the customer. The process model below illustrates this process.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help