Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1521
| Newsgroups | comp.databases.ms-sqlserver |
|---|---|
| Date | 2013-07-01 04:03 -0700 |
| Message-ID | <464ca9b1-26d5-43bc-8ccb-30968b218639@googlegroups.com> (permalink) |
| Subject | Architecture: POSLog, One data container to rule them all |
| From | janette.pelletier@yahoo.com.au |
Full Link http://www.yellowfinbi.com/YFCommunityNews-POSLog-One-data-container-to-rule-them-all-well-at-least-for-Retail-141038 Brief The topic for today is "big retail" and how an industry standard data container (the ARTS POSLog) can tackle common integration issues with different retail systems and abstract the "Point of Sale" data collection layer from the backend processing layers. Usually we blog about using data once you have aggregated it; but today lets go back a step and talk about the data collection/transmission management and setting up the plumbing that will ultimately make data aggregation much easier, which in turn will makes your retail BI data collection easier and faster to gain insights from. POSLog (the data container) is an industry open standard retail schema developed by ARTS, a subgroup of the National Retailer Federation. It has been around a while and is quite mature as a standard; but still not too many people have heard of it. The primary goal of an industry defined schema like the ARTS POSLog, is to reduce costs through standards. That is, by setting a standard for data transmission and interchange that all POS vendors adhere too, you ensure consistency across platforms and this gives retailers more flexibility with their selection of software and hardware for the ‘point of sale’
Back to comp.databases.ms-sqlserver | Previous | Next | Find similar
Architecture: POSLog, One data container to rule them all janette.pelletier@yahoo.com.au - 2013-07-01 04:03 -0700
csiph-web