House of Fraser Real World Experience Using Microsoft Technology 3/25/2017 11:28 AM House of Fraser Real World Experience Using Microsoft Technology Andrew Bond Development Services Manager House of Fraser © 2003-2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
Agenda Background B2b integration Web services for CRM Conclusions and the future Questions
House of Fraser - background Britain's leading designer brands retailer 53 Stores across the UK 1300 Suppliers 120,000 documents per year
IT infrastructure Traditionally Oracle based Increasingly heterogeneous environment Increasing Microsoft technology
Point to point internal integration ASB BLT HDL AFT COPOS QOSY DRW SWG EDI BST XOI CUI RMO DLY KYF KFC JIA FQA VUH HCO WKD ECP SKD MFP WCP DKE AJT
B2b 2003 strategic review – situation analysis 50% of orders (350 suppliers) sent over EDI 50 suppliers providing EDI invoices 50 suppliers receiving EDI sales 60 suppliers providing EDI advance shipping notices for X-docking in Distribution Centre
B2b Existing architecture Suppliers Purchase Order Cycle Systems Catalogue 3rd parties 3rd parties NonEDI EDI Recruit Recruit P a p e r Extranet Proprietary EDI software HOF Systems Merchandising Financials Customer ordering Merchandising Range planning Customer ordering
*VAN – Value Added Network – 3rd party provider EDI services House of Fraser aims No paper based communication Lower cost barriers by reducing dependence on EDI VANs* Increased supplier communication Vendor managed inventory Reduce maintenance overheads for B2B systems by 50% *VAN – Value Added Network – 3rd party provider EDI services
*VAN – Value Added Network – 3rd party provider EDI services House of Fraser aims Integrating a supplier should be equivalent to adding a user to a system and not like integrating a new system! *VAN – Value Added Network – 3rd party provider EDI services
Problems Number of adhoc pilots Proprietary, specialist skills, difficult to configure Lack of buy in to 3rd party service providers 3rd party’s interests not HoFs interests Expensive and difficult to add new trading partners Cost of EDI VANs Expensive and difficult to configure for new file types (e.g. XML)
Why choose BizTalk 2004 ? A platform that provides everything Best strategic fit with IT strategy Ability to generate a revenue stream Simple to administer No change for existing suppliers
Partners are important Covast Microsoft’s recommended partner Embedded within BizTalk 2004 History of EDI connectivity experience AS2 knowledge and experience Includes UK-specific EDI translation capabilities
Partners are important Solidsoft Strategic integration advisors of choice The UK’s premier BizTalk specialists Collaborative and results orientated project implementation approach Applied industry understanding to make a resilient operational system Understood and delivered upon our ambitious and complex business goals
Project Proof of concept Gradual replacement of services and existing EDI software Supplier recruitment Drive to IP based supplier communication
Issues Moving suppliers seamlessly Exceptions and “bending” of the standards Different VAN providers and formats Range of supplier abilities
HoF Supplier Community B2b architecture HoF Enterprise HoF Supplier Community Web Integration INTERNET Supplier HoF Systems HoF Extranet Finance 3rd Party UNIX COPOS BizTalk for B2B WMS AS2 Electronic Data Interchange Value Added Network Mercatus
BizTalk 2004 based solution Suppliers Purchase Order Cycle Systems Catalogue 3rd parties 3rd parties NonEDI EDI Recruit Recruit P a p e r Extranet COVAST CPFR BizTalk Server 2004 Catalogue Management HOF Systems Merchandising Financials Customer ordering Merchandising Range planning Customer ordering
Extranet solution Smaller suppliers ASP.Net Classic n-tier deployment Component-based Scalable Logical Architecture (CSLA) Write direct to Merchandising system
Concessions information Double recording of sales Partner “catalogue provider” charged both suppliers and HOF Encouragement of heterogeneous formats Replaced with BizTalk Suppliers now charged directly by HOF
Results of project All suppliers now send ASNs Previous supplier subscriptions now paid to House of Fraser New recruitment for all processes over internet protocols XML standard messages Lower costs and revenue generation
BizTalk for internal projects Customer Ordering Long running orchestrations
CRM - Recognition Card Loyalty card based scheme Joint venture between House of Fraser and 3rd party Transactions and points owned by HOF Customer support, statements, fulfilment provided by 3rd party
Recognition Card House of Fraser CRM Engine Data Warehouse 3/25/2017 11:28 AM Recognition Card Data Warehouse CRM Engine House of Fraser Call Centre CRM Engine HTML reports © 2003-2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
CRM – Recognition Card House of Fraser CRM Engine Data Warehouse Call Centre Web Services
CRM Web Services Moving from Oracle stored procedure / Java approach to .Net Business logic moved towards middle tier Built around HOF specific CLSA Security
Future Supplier Partner COPOS WMS Information Platform Financials Customer Partner COPOS WMS Financials Information Platform
Conclusions BizTalk and Web Services enable easier heterogeneous environment Focus is increasingly on SOA Web services which are object oriented enable greater reuse Integration still requires management and documentation – BizTalk Integration projects can bring tangible benefits