It's almost like you were on the project. ;-)
Because the space (grid) holds all the OMS information, whether from
telesales, the website, or high street shops, it provides all the
information necessary to implement BAM. In order to take the load off
the OMS space, we created a statistics space. Events are logged in
the OMS space, to keep latency low, but are aggregated by separate
agents and the results written to the statistics space. From there,
information about potential problems is routed to operations and
realtime sales data is sent to the sales execs.
An interesting technique developed by a third party consultancy is
the hospital space. Initially, all problem orders were routed to this
space for manual intervention. As common types of errors have been
identified, new agents have been developed to programmatically repair
the broken orders and send them back to the OMS space. Over time the
amount of manual intervention required is steadily decreasing.
Regards,
Patrick
On 28 Jun 2008, at 18:39, htshozawa wrote:
> Is it possible to add or is there a BAM in a grid to alert when there
> is a problem with a process?
>
> H.Ozawa
>
> --- In [email protected], Patrick May
> <[EMAIL PROTECTED]> wrote:
>>
>> One day a few weeks after the new system was in place, the
> head of
>> Web sales came running down to complain that "The OMS is broken! We
>> haven't received any orders from the Web in 18 hours!" I looked in
>> the grid and found a large number of orders waiting to be processed
> by
>> the, you guessed it, ERP system. Once quick phone call to ask ops
> to
>> reboot the ERP app and we were back in business without losing a
>> single order.
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
----
[EMAIL PROTECTED]
S P Engineering, Inc.
Large scale, mission-critical, distributed OO systems design and
implementation.
(C++, Java, Common Lisp, Jini, middleware, SOA)
