| |
Product
Allocation and Shipping Substitution System
Overview
In order to improve sales efficiency and shorten (from receipt to sale) the inventory lifecycle for perishable product, new functionality was built into the existing sales and inventory management system. The ability to control overselling, to allow for speedy product substitution when necessary, to maintain product quality records, and enhancements to effectively manage product pricing were all integrated into the existing system. The new functionality strengthens management’s ability to manage and improves the efficiency and effectiveness of the sales and warehouse
staffs.
Business Benefits
-
Increase profits through enhanced price and inventory management.
-
Reduce customer claims by improving quality tracking and control.
-
Reduce time and resources needed to handle product shipping.
-
Provide timely price comparison information to suppliers.
-
Improve operational controls at the warehouse and distribution centers.
Architecture
|
Application Development/Design Component |
Development Tool |
|
Data Model Design/Generation |
ERwin |
|
Graphical User Interface |
PowerBuilder |
|
Component (Business Objects) Development |
PL/SQL Packages |
|
Database |
Oracle 8 |
|
Hardware |
HP Unix server |
|
Networking |
Microsoft Windows NT, Access to Oracle over a wide area network |
Process Flow Diagram
Methodology and Approach
The Artech project methodology consists of six areas – MIS Strategy, Foundation, Conceptual Design, Detail Design, Build, and Rollout. Based on the client/project needs the methodology is customized to both maintain Artech’s standard of excellence and meet the specific requirements of the particular project.
This project included the following steps:
Foundation / Conceptual Design – 3 weeks
- Facilitated cross functional group meetings to discuss needs.
- Built the business case and business benefits list.
- Built the issues and assumptions lists.
- Built consensus among the users and management about what needed to be done.
- Organized and prioritized the raw requirements gathered and translated them into application processes.
- Published the Conceptual Design document.
Detail Design – 2 weeks
- Detailed the specific data attributes and entities needed.
- Resolved issues brought forward during the foundation and conceptual design process.
- Finalized the data model.
- Finalized the screen designs.
- Resolved issues and noted assumptions as they came up during the detail design process.
Build – 8 weeks
- Created the tables, procedures, functions, etc. necessary.
- Created the user interfaces.
- Built the necessary reports.
- Set up security requirements.
- Tested usability, functionality, accuracy.
- Created testing scripts to be delivered with the project to the client.
Rollout – 2 weeks
- Trained business users and client technical staff.
- Supported the rollout of the new functionality and enhancements.
|