1 / 14

RDF/RMS Implementation - DRAFT Deliverable

RDF/RMS Implementation - DRAFT Deliverable. Application Architecture. Introduction. Assumptions The Vision Application Architecture Key Standard RMS & RDF Interfaces WHSmith High Street “As-Is” Application Architecture Interface Framework Concept Interface Framework Benefits

jenna-holloway
Télécharger la présentation

RDF/RMS Implementation - DRAFT Deliverable

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. RDF/RMS Implementation - DRAFT Deliverable Application Architecture

  2. Introduction • Assumptions • The Vision • Application Architecture Key • Standard RMS & RDF Interfaces • WHSmith High Street “As-Is” Application Architecture • Interface Framework Concept • Interface Framework Benefits • WHSmith High Street RDF Transitional Application Architecture • WHSmith High Street RDF & RMS Transitional Application Architecture • WHSmith High Street “To-Be” Application Architecture • Interface Framework Options • Implementation Risks

  3. Assumptions • RDF to be implemented before RMS • RDF, RMS and Interface Framework to be implemented in parallel workstreams • RMS to be rolled out by SBU or Department and not “Big-bang” • During the rollout period, a user will exclusively use RMS or Minerva • “Live” pertains to an application becoming operational for any part of the business • WHS Travel applications have not been considered and any Travel application integration effort would be carried out post High Street RMS/RDF Go-Live • WHS High Street and WHS Travel will exist within the same RMS and RDF instances • The Interface Framework will be completed before RMS is Live • All external or periphery application interface feeds will remain unchanged for the duration of the project • The MicroStrategy reporting framework has been included to “complete the Vision” but is not considered here in any detail

  4. The Vision

  5. Application Architecture Key Minerva Legacy Application Number of interfaces 18 Interface flow directions RDF New Application EDI External Interface Feeds Interface Framework MicroStrategy Reporting Framework

  6. Standard RMS and RDF Interfaces RDF RDW POS data Inventory Adjustments PO data RTV’s Promotions & pricing Etc……. 15 10+ Sales /sales forecasts EPOS 7 Pricing Item data 6+ RMS Oracle Financials Stock ledger data POS data Vendor data PO and receipt data POs EDI 9 Items Suppliers PO’s ASN’s Pricing Ticketing ASNs, Item info, Order Confirmations Receipts RTV’s Inventory Adjustments 18 RDM

  7. WHSmith High Street “As-Is” Application Architecture

  8. Interface Framework Concept • The Interface Framework will be a medium for interface exchange and will act as a “bridge” between the central merchandising systems – RMS and Minerva – and all peripheral applications. The IF will perform the following: • Receive and send interface data (flat files or “messages”) • Reformat interface feeds from RMS into the required target application format • During the transition period, intelligently merge Minerva and RMS download interface feeds and output a single interface feed to the target application • During the transition period, intelligently divide source application upload feeds and output an interface feed to Minerva and RMS • The IF could be used to protect RMS from the development or implementation of future applications e.g. if a new EPOS system were to be rolled out on a store by store basis, the IF could support 2 EPOS systems operating side-by-side with no impact to RMS. Consequently, the IF could remain in place indefinitely.

  9. Interface Framework Benefits • Enables transition from Minerva to RMS whilst ensuring that the transition process is transparent to periphery applications • Allows for phased rollout of RMS • Protects central merchandising system from periphery application replacement, introduction or removal, in effect “future-proofing” RMS from interfaced application development • The IF allows for periphery applications to be “bolted” on thus allowing new applications to be introduced to the Application Architecture through a company merger or acquisition • Rationalisation of existing Legacy interfaces

  10. WHSmith High Street RDF Transitional Application Architecture - December 2001 Note: It is only necessary to complete the RDF-Minerva portion of the Interface Framework at this stage.

  11. WHSmith High Street RDF & RMS Transitional Application Architecture – August 2002

  12. WHSmith High Street “To-Be” Application Architecture - January 2003

  13. Mainframe: Pro*C on UNIX: Package Solution: Interface Framework Options

  14. Implementation Risks • Development of the Interface Framework not being complete before RMS goes “Live” will require a significant re-think of the interfacing strategy to enable RMS and Minerva to operate in tandem, each supporting different SBUs • System performance impact of introducing the Interface Framework • Successful segregation of Minerva data by SBU such that RMS and Minerva can operate reciprocally in the delivery of the Merchandising function

More Related