|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Complex Event Processing RSS News
Manual Event Processing: delivering the Tiffin Box
Post 302167348 by Linux Bot on Thursday 14th of February 2008 07:10:09 AM
02-14-2008
Manual Event Processing: delivering the Tiffin Box
vincent
Thu, 14 Feb 2008 04:13:59 +0000
Whilst on a customer visit [*1] in Mumbai, India, the topic of the Tiffin Box delivery industry was raised as an example of “manual CEP” [*2]. This is where office workers get their lunch (tiffin) box delivered from home to work at around midday by a delivery network of thousands of “dabbawalas“. So this is a process of multiple source addresses (imagine homes across Mumbai), multiple destinations (imagine office cubes across Mumbai), using no written instructions (dabbawalas were often illiterate), in “human” real-time, with a negligible error rate, in use since the 1880s …
This somewhat puts us in our place regarding our discussions on CEP for transport, logistics, baggage handling, RFID, the need for BAM and SLAs, etc etc!
Notes:
[1] This is a “customer master data management” application involving TIBCO CIM for the MDM part, augmented by TIBCO BusinessEvents for business rule processing against new master data events. This is an additional use case than those described* earlier on CEP and MDM.
[2] Apparently this a Harvard Business School business case study, and interestingly the dabbawallahs are not at all immune to change.
Source...
Thu, 14 Feb 2008 04:13:59 +0000
Whilst on a customer visit [*1] in Mumbai, India, the topic of the Tiffin Box delivery industry was raised as an example of “manual CEP” [*2]. This is where office workers get their lunch (tiffin) box delivered from home to work at around midday by a delivery network of thousands of “dabbawalas“. So this is a process of multiple source addresses (imagine homes across Mumbai), multiple destinations (imagine office cubes across Mumbai), using no written instructions (dabbawalas were often illiterate), in “human” real-time, with a negligible error rate, in use since the 1880s …
This somewhat puts us in our place regarding our discussions on CEP for transport, logistics, baggage handling, RFID, the need for BAM and SLAs, etc etc!
Notes:
[1] This is a “customer master data management” application involving TIBCO CIM for the MDM part, augmented by TIBCO BusinessEvents for business rule processing against new master data events. This is an additional use case than those described* earlier on CEP and MDM.
[2] Apparently this a Harvard Business School business case study, and interestingly the dabbawallahs are not at all immune to change.
Source...
|
|
LEARN ABOUT DEBIAN
raidfile.conf
RAIDFILE.CONF(5) Box Backup RAIDFILE.CONF(5) NAME
raidfile.conf - Userland RAID for Box Backup SYNOPSIS
/etc/box/raidfile.conf DESCRIPTION
The raidfile.conf is usually generated by raidfile-config(8) but may be manually edited if the store locations move or if more than one disc set is required. discX Specifies a set of discs. SetNumber The set number of the RAID disc, referenced by each account. BlockSize The block size of the file system (usually 2048). Under BSD with FFS, set this to your file system's fragment size (most likely an 8th of the block size). Dir0 The first directory in the RAID array. Dir1 The second directory in the RAID array. If you do not wish to use the built-in RAID functionality, this field should be set to the same as Dir0. You should not use the built-in RAID if you have a hardware RAID solution or if you're using another type of software RAID (like md on Linux). Dir2 The third directory in the RAID array. The same notes that apply to Dir2 also apply to Dir3. FILES
/etc/box/raidfile.conf SEE ALSO
raidfile-config(8), bbstored.conf(5) AUTHORS
Ben Summers Per Thomsen James O'Gorman Box Backup 0.11 10/28/2011 RAIDFILE.CONF(5)