Strong Integration: A Necessity in Today's Market - Jim Sawyers, Bounce10

822 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
822
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Strong Integration: A Necessity in Today's Market - Jim Sawyers, Bounce10

  1. 1. Strong Integration: <br />A Necessity in Today’s Market<br />As applied to version ML v8<br />Presented by: <br />Jim Sawyers<br />President, Bounce10<br />Knoxville, TN<br />www.bounce10.com<br />
  2. 2. Who is Bounce10?<br />We provide creative and comprehensive solutions that allow business owners to run their business and be assured their site is bringing in orders and producing revenue. <br />We build long term relationships with clients to ensure success.<br />Our goal is to be the best online partner to our clients.<br />
  3. 3. Who is Bounce10? (Cont’d)<br />We Offer Full Service Ecommerce<br /><ul><li>10+ years Ecommerce Development Experience
  4. 4. Working with ASPDNSF since 2008.
  5. 5. Wordpress development and integration experience
  6. 6. Specializing in Complex Integrations and Customizations
  7. 7. Business Process Consulting
  8. 8. Online Marketing Support (SEO/SEM/Affiliate/Email/Social)
  9. 9. and more… </li></li></ul><li>What this Session Covers<br /><ul><li>A Prelude to Integration – Know what you’re building
  10. 10. The Why’s, What’s and How’s of Integration
  11. 11. Integrating with WSI – Benefits, risks and case study
  12. 12. Integrating within SQL – Benefits, risks and case study
  13. 13. Integrating with Customizations – Benefits, risks and case study
  14. 14. How does mobile fit in?</li></li></ul><li>A Prelude to Integration<br />Know what you’re building<br /><ul><li> Know your company’s business needs
  15. 15. Choose tools which will scale with your growth
  16. 16. Define the business rules for integration
  17. 17. Ensure all systems enable the integration goals
  18. 18. Why one size doesn’t fit all</li></li></ul><li>Why Strong Integration?<br /><ul><li>Strong Integration is a cornerstone of good eCommerce
  19. 19. Today’s market presents Rapid Growth Opportunities
  20. 20. Strong Integration saves time & money
  21. 21. Strong Integration improves customer experience
  22. 22. Poor Integration impacts your customers</li></ul>Bottom line.. Strong integration aids in the creation and retention of good customers<br />
  23. 23. What do we Integrate?<br />Which processes need integration?… and when?<br /><ul><li> Order data (to fulfillment / accounting)
  24. 24. Tracking information (to the web)
  25. 25. Product data (to the web)
  26. 26. Product inventory (to the web)
  27. 27. And more... </li></li></ul><li>How do we Integrate? <br />Which Integration method fits best?<br /><ul><li> ASPDNSF WSI
  28. 28. Integrating within SQL
  29. 29. Customizing the Codebase</li></li></ul><li>Integrating with WSI<br />Benefits of using WSI<br /><ul><li> Built in to ASPDNSF
  30. 30. Industry Standard (XML)</li></ul>Risks of customizations<br /><ul><li> Poor development practices can lead to problems
  31. 31. Knowledge transfer / loss</li></li></ul><li>Integrating with WSI<br />A Case Study – Retail POS Products and Inventory<br />The Problem:<br />The client has a retail store and a web store. They do not have different inventories for each location. Their website is hosted remotely. Their POS database is local and allows for ODBC connectivity.<br />The Solution: <br />Bounce10 developed a middleware application which runs locally at their retail store as a windows desktop application and a windows service. The application uses ODBC to connect to the POS system and ASPDNSF web services to update product data. The service runs every hour updating products and inventory as it changes. <br />
  32. 32. Integrating within SQL<br />Benefits of using SQL<br /><ul><li> Data resides in a single environment
  33. 33. Risk of data theft is reduced
  34. 34. Smooth and fast integration </li></ul>Risks of using SQL<br /><ul><li> Only compatible systems / databases will work
  35. 35. Data schema changes will require updates
  36. 36. Incorrect data mapping could result in storefront errors</li></li></ul><li>Integrating within SQL<br />A Case Study – Large ERP Real-time Order Processing<br />The Problem:<br />The client has a large volume of web orders and needs to get orders into their ERP system so they can quickly be put into the pipeline for fulfillment. Their ERP database is SQL based and on the same network as their ASPDNSF database. <br />The Solution: <br />Bounce10 created a stored procedure which picks up the orders and moves them into the ERP. This stored procedure is scheduled through SQL Agent to run automatically every 5 minutes.<br />
  37. 37. Integrating with Customizations<br />Benefits of customizations<br /><ul><li> Almost anything is possible </li></ul>Risks of customizations<br /><ul><li> Poor development practices can lead to problems
  38. 38. Knowledge transfer / loss
  39. 39. Upgradability</li></li></ul><li>Integrating with Customizations<br />A Case Study – Delivering ERP Pricing to the Web<br />The Problem:<br />The client has over 50 different pricing tiers for their customers. In the past they have used the extended pricing features built into ASPDNSF to allow for a few of these tiers to be on the web. But they want to have them all.<br />The Solution: <br />Bounce10 first created a new set of db tables to hold the pricing data from the ERP and developed integrations with the ERP to populate the tables nightly. There already existed a tie between a web customer and an ERP customer in the database. We separated out ASPDNSF methods which retrieved pricing for customer levels and added new logic to get pricing from the new tables if it was available, defaulting to the retail price.<br />
  40. 40. New Mobile Platform<br />How do these integrations work with mobile?<br /><ul><li>Re-implement for mobile? Maybe for custom solutions
  41. 41. Mobile uses same dlls as full site
  42. 42. New .aspx and .cs files for mobile</li></li></ul><li>In Summary<br /><ul><li> Know what you’re building before you begin
  43. 43. Strong integration should be among the 1st priorities
  44. 44. Every integration is different and must be planned
  45. 45. Different processes may require different integration styles</li></li></ul><li>Thank You…Questions are welcomed<br />Jim Sawyers is the President of Bounce10, a full service Web and eCommerce company located in Knoxville TN. Jim has over 10 years of experience developing, integrating and managing eCommerce systems for clients such as DirecTV, TiVo and Sirius XM Radio. Jim has been developing solutions with ASPDotNetStoreFront since 2008.<br />Jim may be reached via email at jim@bounce10.com<br />

×