Overview

 The existing sales and inventory management systems were enhanced to provide a proactive comparative price reporting system (CPRS) in order to reduce supplier claims.  Comparative price quote data can now be entered into the system and analyzed.  The company can use the new pricing data for its competitive value and track the information for planning purposes. 

The company was provided with several new reports available to users on an ad hoc basis.  The easy access to comparative pricing data has enhanced the company’s ability to analyze regional sales performance and improve price and revenue forecasting as well as simplify the liquidation process. 

Business Benefits 

·      Streamline the process for the tracking and reporting of comparative prices.

·      Improve the accuracy and timeliness of comparative and sales price reporting.

·      Use comparative prices to improve the companies average retail price (ARP).

·      Provide accurate and timely Price Analysis using comparative prices and average retail price.

·      Compile comparative prices, purchase and other price data by product and ship date.

·      Provide timely ad-hoc reports for claims, producers, forecasting, liquidation and sales.

·      Better analyze the performance of the company sales.

·      Improve the company’s ability to forecast sales prices and revenues

·      Reduce supplier claims by tracking comparative prices and providing proactive reports. 

Architecture 

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 issues and assumptions lists.

·         Built the business case and business benefits list.

·         Built consensus among the users and management about what needed to be done.

·         Reconfirmed requirements with Client.

·         Published the Conceptual Design document.

 Detail Design - 2 weeks

·         Detailed specific data attributes and entities.

·         Finalized data model.

·         Prepared detail screen designs and finalized design with user.

·         Worked with the user to finalize report specifications and ad-hoc query needs.

 Build - 4 weeks

·         Created the tables, procedures, functions, etc. necessary.

·         Created the user interfaces.

·         Built the necessary reports.

·         Set up security requirements.

·         Tested usability, functionality, and accuracy.

·         Created testing scripts to be delivered with the project to the client.

Rollout - 1 week

·         Established guidelines and business rules for comparative price mapping.

·         Trained business users and client technical staff.

·         Supported the rollout of the new functionality and enhancements