OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [ebxml-dev] End to End ebXML implementation....

Title: RE: [ebxml-dev] End to End ebXML implementation....

Yes... those are all developers ... who are you exchanging payloads with?  what are your business transactions...??

Have a great day ..
Gene Hockemeyer

-----Original Message-----
From: Andrzej Jan Taramina [mailto:andrzej@chaeron.com]
Sent: Wednesday, November 20, 2002 3:16 PM
To: ebxml-dev@lists.ebxml.org
Subject: RE: [ebxml-dev] End to End ebXML implementation....

Gene asks:

> It would be nice to hear .. how many partners you are working with ..

Partners included:

   Vision, Strategy & Architecture
   Partner/Product Selection
   Project Management & Team formation
   ebXML adoption/deployment strategy and recommendations
   Web Services adoption/deployment strategy and recommendations

New Era of Networks (Sybase) software:
   BPSS Visual Modelling Tool
   BPM Engine
   MSH Implementation

   Open Source Registry/Repository - ebxmlrr

   Web Services & J2EE Platform


> what
> modeling types your are building .. and what transactions.. if any ... you
> are executing to resolution.

The goals of this implementation included:

   - Prove feasibility of end to end ebXML Implementation
   - Clarify benefits from such an approach
   - Provide "go forward" strategy and reference implementation
   - Promote knowledge & adoption of ebXML

The business processes were modelled visually using a UML-derivative, and
then the executable BPSS definition was generated automatically. 

The scenario that we implemented was that of Used Vehicle Sales (eg. off-
lease, employee returns, etc.) for a large Auto OEM.  This scenario, and
related transactions (inventory availability search, quotes, purchases, credit
checks, confirmations, etc.) was selected since it would have the greated
"understandability" throughout the organization.  Supply Chain was
considered...but the terminology and problems in automating supply chain can
be rather specialized and not "ring" with the general user population.

Hope this helps.....

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions

The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC