1 / 102

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS. Remote Managed Inventory – Soup to Nuts. Paul Stewart Chief Technology Officer/Export Compliance Officer Worthington Aviation Parts, Inc. Worthington Maintenance Repair and Overhaul Center. Who am I …

gilles
Télécharger la présentation

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

  2. Remote Managed Inventory – Soup to Nuts Paul StewartChief Technology Officer/Export Compliance OfficerWorthington Aviation Parts, Inc.Worthington Maintenance Repair and Overhaul Center

  3. Who am I … • Paul Stewart, Chief Technology Officer and Export Compliance Officer for Worthington Aviation since 2004. Former employee of Component Control from 1998 to 2004, leaving as the Vice President of Quantum Product. QUE Group Board Member since 2009 and former QUE Group Liaison at Component Control. • Worthington Aviation specializes in Regional Turboprop, Commercial and Corporate aircraft. Established in 1998, Worthington has locations in Eagan MN. USA, Pompano Beach FL. USA, Tulsa Ok. USA, Brisbane Australia and Prague Czech Republic. http://lnkd.in/9GYE8S

  4. In This Session … • We learn the basic elements of the RMI module. • Learn the business scenarios the RMI module is designed to handle. • Learn how to manage the inventory in a remote location. • Learn the process flow of each of the business models.

  5. What We’ll Cover … • We will cover the RMI header and detail screens and the elements of each. We will cover the web module as well as the transaction processing for remote inventory. • I will show you the business models this module is designed for, and how to process transactions for each of the models. • We will take an in-depth look at how automation can help you manage these business models.

  6. Types of business models for the RMI module • Fundamentals of the RMI module • The Web Portal • Tying it all together • Examples of automation • Other modules you will need for full effect

  7. Types of business models for the RMI module • Forward located inventory, also called exchange pools or rotable pools or consumable pools • Consigned inventory, where you are the consignor and the inventory is located at the consignee • Contract pricing, or pre-determined pricing • Flight hour billings, or Power by the Hour™

  8. Types of business models for the RMI module • Forward located inventory, also called exchange pools or rotable pools or consumable pools DEFINITION:Inventory that is placed or stored at the customer’s site. This could be rotables, expendables or consumables type parts. The customer is invoiced when the item is used. The keyword in RMI language is “Pool”, “Non-Program”– remember this.

  9. Types of business models for the RMI module • Forward located inventory, also called exchange pools or rotable pools or consumable pools • Consigned inventory, where you are the consignor and the inventory is located at the consignee DEFINITION:Inventory you have located at the consignee’s site, or at your site, for which you have a contract in place allowing them (the consignor) to sell your parts on behalf of you. This could be rotables, expendables or consumables type parts. The consignor is invoiced for your portion of the proceeds at the time the item is recorded as used (sold) The keywordsin the RMI language are “Pool”, “Non-Program” and “Consignment Code” – remember this.

  10. Types of business models for the RMI module • Forward located inventory, also called exchange pools or rotable pools or consumable pools • Consigned inventory, where you are the consignor and the inventory is located at the consignee • Contract pricing, or pre-determined pricing DEFINITION:A list of parts that you have agreed to make available and sell to a customer at an agreed upon price for exchange and outright. The inventory is NOT located at their facility, and they must submit a requisition or purchase order to initiate the shipment of the part. The customer is invoiced at the time the part is shipped. The keywordsin the RMI language are “Demand”, “Non-Program” – remember this.

  11. Types of business models for the RMI module • Forward located inventory, also called exchange pools or rotable pools or consumable pools • Consigned inventory, where you are the consignor and the inventory is located at the consignee • Contract pricing, or pre-determined pricing • Flight hour billings or Power by the Hour ™ DEFINITION:An arrangement with an aircraft fleet owner to manage a defined pool of parts at their facility, or your facility, for use in their aircraft fleet. Billing to the customer will be based on the hours flown by the aircraft for which you are supporting. The keywordsin the RMI language are “Pool”, “Demand”, “Program” – remember this.

  12. <- RI = System Assigned Transaction Number <- Doc ID = User Defined Identifier <- Date Open = Date RMI Header Created <- Sales Category = Default SO Category Code

  13. Station = The Remote WH Code -> Cons Code = Code Assigned To Package -> Currency = Default Currency Code For Billing -> Lease # = The Rental Lease Assigned -> Consignment codes would be used only if you are consigning your inventory out. A rental lease transaction is required to record flight hours for “power by the hour ™”. You must create a warehouse code for the customer or consignees location.

  14. <- Customer = The Customer or Consignee <- GL Dist = The GL Distribution for Inventory offset <- Res Geo Code = The Source WH Geo Code

  15. The GL Distribution Code defines the account number to be used when a part is Issued

  16. <- Shipping Priority = The default priority for shipments

  17. <- UDF Fields are used to identify the namesand email addresses of our internal contract administrators, and the corresponding contact information for the customer. This is used for automated notices and reports. We have modified the RMI header to accommodate our processes

  18. Let’s take a look now at the RMI detail screen..

  19. PN and Description are self explanatory Min QTY = This is the minimum QTY to be located at the remote location Cond = This is the condition of the unit to be located at the remote facility. Cons = The Consignment Code for consigned inventory where you are the consignor. Curr Price and Alt = This is the price to be billed based on the Exchange flag setting

  20. The exchange flag, and the curr price and alt price fields work together to determine the amount to be billed. When a unit is invoiced or issued, it will charge the Curr Price if the usage event matches the Item’s Exchange setting. If it does not, it will use the alternate price. Example: I have set up a unit where I want the primary transaction to be an exchange. So, I mark my item as an Exchange. When usage of this item is recorded, the user can remove the exchange flag indicating no core will be billed. This causes the Alt price to be used – the Outright price.

  21. WHEN USAGE IS RECORDED DOES THE EXCHANGE FLAG MATCH THE ITEM SETTINGS? If so, use the Curr Price If Not, use the Alt price

  22. The exchange flag will also determine if an awaiting core record is created. Additionally, it will initiate the exchange financial entries in the GL

  23. Stock Type determines if the part will be located at the remote location – or if the customer must request the part. Pool = indicates this part must be shipped to the customer’s location and be in their warehouse code before the unit can be invoiced or issued. It is stocked at the customer’s location. On Demand = indicates this part must be requested by the customer, and shipped/invoiced at that time. It is stocked at your location.

  24. The program flag determines how this item will be billed. Program flag checked means this item is part of a Flight Hours Billing (or Power By The Hour ™) type of contract. This means you do NOT invoice the part. You Issue the part in order to remove it from stock. When a part is issued, the GL Distribution code is referenced to determine where the cost of the unit should go within the GL accounts.

  25. The program flag determines how this item will be billed. Program flag UNCHECKED means this item is billed for each usage. This means you create an invoice for the part every time it is used. The standard GL defaults are used during the invoicing process.

  26. DEFINITIONS SUMMARY: POOL = THIS MEANS STOCK WILL BE LOCATED AT THE CUSTOMER’S WAREHOUSE DEMAND = THIS MEANS THE STOCK WILL BE LOCATED AT YOUR WAREHOUSE AND THE CUSTOMER MUST REQUEST THE STOCK TO BE SHIPPED. POOL AND DEMAND DRIVE STOCKING LOCATION PROGRAM = IF CHECKED, THIS MEANS FLIGHT HOURS WILL BE BILLED THROUGH THE RENTAL LEASE MODULE. IF UNCHECKED (NON-PROGRAM), THIS MEANS THE PART WILL BE INVOICED WHEN IT IS USED. PROGRAM DRIVES THE REVENUE MODEL EXCHANGE = IF CHECKED, AN AWIATING CORE RECORD IS CREATED, AND THE CORE COST CALCULATIONS ARE PERFORMED. IF UNCHECKED, IT IS TREATED AS AN OUTRIGHT SALE CURR PRICE = THE AMOUNT THAT WILL BE CHARGED IF THE USAGE EXCHANGE FLAG SETTING MATCHES THE RMI ITEM SETTING. ALT PRICE = THE AMOUNT THAT WILL BE CHARGED IF THE USAGE EXCHANGE FLAG SETTING DOES NOT MATCH THE RMI ITEM SETTING.

  27. For each item, activity grids are displayed at The bottom of the screen Stock Summary

  28. For each item, activity grids are displayed at The bottom of the screen Requisitions

  29. For each item, activity grids are displayed at The bottom of the screen Usage

  30. For each item, activity grids are displayed at The bottom of the screen Shipping Orders

  31. For each item, activity grids are displayed at The bottom of the screen Invoices

  32. For each item, activity grids are displayed at The bottom of the screen Purchase Orders

  33. For each item, activity grids are displayed at The bottom of the screen Exchanges

  34. For each item, activity grids are displayed at The bottom of the screen Repair Orders

  35. For each item, activity grids are displayed at The bottom of the screen Sales Orders

  36. Activity grids are available for the package As a whole too. Managed Items This is the list of items within your package.

  37. Activity grids are available for the package As a whole too. Invoiced Stock Invoices are applicable to NON PROGRAM part activity.

  38. Activity grids are available for the package As a whole too. Issued Stock Issued stock is applicable to PROGRAM type activity, or packages that are billed by the flight hour

  39. Activity grids are available for the package As a whole too. Low Stock Low stock shows what stock demands need fulfilling based on Minimum Qty and unfulfilled requisitions

  40. Activity grids are available for the package As a whole too. Open Cores Open Cores shows the cores due from the customer. NOTE: The Receiving Inspection Module is required in order to receive cores NOT processed through the Sales Order Module

  41. Activity grids are available for the package As a whole too. Offsite Stock Offsite stock shows inventory located at the remote warehouse

  42. Activity grids are available for the package As a whole too. Onsite Stock Onsite stock shows inventory located any warehouse NOT equal to the remote warehouse, which is reserved against the RMI

  43. Activity grids are available for the package As a whole too. Open PO Open PO’s shows any linked purchase order activity

  44. Activity grids are available for the package As a whole too. Exchanges Exchanges shows all exchange activity for the module, This includes both open, and closed core records.

  45. Linked Rental Lease Transaction Lease Time Log Lease Time Log shows flight hour entries made in the linked Rental Lease module. This is for “Program” parts (flight hour billings)

  46. Activity grids are available for the package As a whole too. Repair Orders RO Shows linked repair order activity

  47. Activity grids are available for the package As a whole too. Activity Log Activity Logs show all transactional activities for all events within the module.

  48. Activity grids are available for the package As a whole too. Activity Log ACTIVITY TRAN TYPE CODES: RCDP= Core Receipt Posted RCDA = Core Receipt Added RCDD = Core Receipt Deleted SMDP = Shipper Processed STII = Stock Issue processed CUTU = Usage record updated CUTA = Usage record added CRQA = Requisition added CRQU = Requisition updated INDA = Invoice added INDP = Invoice posted

More Related