1 / 11

T4.2 Negotiation support functions

T4.2 Negotiation support functions. Marco Barbi KELYAN. Functional requirements recap. Enable the collaboration among user companies Understand the supply conditions and the customer needs Exchange of formalised documents Provide formalised specification for company offer

tanek-ramsey
Download Presentation

T4.2 Negotiation support functions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T4.2Negotiation support functions Marco Barbi KELYAN

  2. Functional requirements recap • Enable the collaboration among user companies • Understand the supply conditions and the customer needs • Exchange of formalised documents • Provide formalised specification for company offer • Suppliers can specify their offers by means of their local language and classification scheme • Suppliers declare offer features via parameters • Offer classification based on taxonomies • Support for defining company demand in respect of the company offer • Customers can specify their needs by means of their local language and classification scheme • Customer demand follows the parametrical structure provided by the supplier (misunderstanding prevention)

  3. Use cases (1) • UC1: Offer definition • Actor: Company A, German manufacturer of cylinders • Defines a new family of cylinders (“zylinder – standard mechanisch”) • The family is parameterised via 4 features: motion (linear, telescopic); power [0/50]; powered (hydraulic, pneumatic); size [0.0/20.0] • The Eclass taxonomy is used for the family classification • UC2: Product configuration (video) • Actor: Company B, English engine manufacturer • Prerequisites: Company A has been chosen as potential supplier (partner search) • Chose a family among the ones offered by Company A • Set the parameters’ values according to their needs • The configuration is stored

  4. Use cases (2) • UC3: RFQ preparation (video) • Actor: Company B • Prerequisites: the product configuration has been already defined • Fills the data in for preparing a new Request For Quotation document addressed to Company A • The RFQ is linked to the configuration. Additional info: quantity • The document is stored • UC4: RFQ dispatch and notification (video) • Actor: Company A, Company B • Prerequisites: Company B has prepared a new RFQ • Company B sends Company A the RFQ • Company A is notified of the incoming RFQ (e-mail) • Company A views the RFQ and configuration details

  5. UC2: Form rendering

  6. UC2: Check configuration

  7. UC4: RFQ dispatch

  8. Advanced configuration • KET-PC (Kelyan) • Rule-bases product configurator software • Product modeller module (Eclipse RCP) • Data repository (Server repository via HTTP protocol) • Pluggable run-time engine

  9. Use cases (3) • UC5: Offer definition - advanced support (video) • Actor: Company A • Prerequisites: KET-PC module enabled for Company A • The standard product definition is imported by the KET-PC modeller application • KET-PC modeller manages the standard product definition parameters as native parameters • KET-PC modeller: definition of constraints limiting the valid configurations, e.g. power > 30 -> powered in [pneumatic] and size > 8.0 • UC6: Product configuration - advanced support (video) • Actor: Company B • The same as UC2 + parameters’ values selection constrained to rules

  10. UC5: KET-PC modeller import

  11. UC6: Check configuration (KET-PC)

More Related