Typically in most of the SME-based industrial sectors, such as the furniture industry, the e-Business offer is seller-driven due to the fact that the product distribution sector is even more fragmented than the production. In this environment, manufacturers offer their products and services through ad-hoc proprietary solutions, either on-line, CD-ROM or paper based, using proprietary corporate web sites and non normalized order forms. Even when joining either vertical or general-purpose e-marketplaces, most of the integration frameworks are open. Thus, apart from the technical considerations or appropriateness in the market of a particular approach, different users from different e-marketplaces cannot interoperate, and customers are wondering how they could make e-business with most of the providers using a common manner. For instance, in a typical e-procurement scenario, product suppliers sell goods over the Internet through sell-side e-Commerce applications and the buying companies purchase goods over the Internet through buy-side e-Procurement applications. In such a scenario, members of a buying company purchase goods from multiple suppliers, using asynchronous interactions between stakeholders and components.
The approach to the integration is based on a model for one or more purchasing components integrating with another purchasing or sales order management component. Main instances consider that all data is contained in the exchanged documents, but the existence of other instances where additional binary information accompanies the RFQ (Request for Quotation) and Quote documents (feedback from suppliers, product information, 3D drawing etc.) should not be excluded. E-procurement focuses also on the Order management and the creation of the forthcoming documents, i.e. invoices and delivery notes among others. Many other situations can be found for product transaction and management.
Summarizing, the scope of the business documents for product transaction and management is to enable the integration of business documents for product transaction and management (e.g., RFQ, Quotation, Order, Order Confirmation, Delivery Note, Invoice) with STEP product model data, and product catalogues. The tutorial deals with the implementation details of the of e-Business funStep Open Architecture (ebfSOA) inside an organization. As in the AP236 tutorial, the this tutorial can be also delivered depending of the different profiles of the students. For those groups belonging to managers and business related people, the tutorial will be more oriented to the potential benefits of adopting the business documents for product transaction and management while the groups belonging to the ICT Technicians will learn how to implement the documents inside their ERP to seemly generate the commercial documents in electronic format.
Tutorial Programme:Tutorial BTM is the second standards tutorial in the funStep training, and as FSS it is classified as "funStep core" level.
NOTE: The BTM tutorial is based on the funStep ebfSOA documents (a de-facto standard) for e-business data. However, has reported in previous INNOVAFUN deliverables, the funStep initiative has recently agreed to shift the rationale that lies beneath the ebfSOA XML schemas, towards the ISO standard approach.Currently the documents and the ISO funStep standard are not fully integrated due to modelling differences that come from the ISO methodology used in AP236. The funStep team is working on a new approach to the ebfSOA documents that would take profit of the packages developed for the ISO standard in order to avoid overspending of time and money. Therefore, because the structure of these documents is changing, the tutorial BTM will not be available during the INNOVAFUN project time.
Powered by:
