Short Number: D3.6.1_2
Document identifier: VIVACE 3.6/1/VAC/T/06001-1.1
Abstract: This deliverable document describes the Virtual Enterprise Collaboration Hub operational environment in terms of how it is technically realised. The deliverable document also covers issues related to trust, security and the legal aspects in setting up a Virtual Enterprise and collaborating through a Virtual Enterprise Collaboration Hub (VEC-Hub).
Short Number: D3.6.2_2
Document identifier: VIVACE-3.6-2-ECS-T-06002
Abstract: This document specifies the Use case references, requirements and specifications of the services for the Virtual Enterprise Collaboration Hub defined by WP3.6. In Appendix I the PLCS PLM web services are defined.
Short Number: D3.6.2_3
Document identifier: VIVACE-3.6-2-ECS-T-06003
Abstract: This document is the technical specification of the web services being developed within ST 3.6.2.7. At this phase of the Vivace project, only PLCS PLM Web Services specifications are ready.
Short Number: D3.6.2_4
Document identifier: VIVACE-3.6-2-ECS-T-07005
Abstract: This document specifies the Use case references, requirements and specifications of the services for the Virtual Enterprise Collaboration Hub defined by WP3.6. It is an updated version of D3.6.2_2. The Reference Data Library services have been added and minor updates have been done on other parts. In the Deliverable D3.6.3_4, OASIS PLCS PLM Web Services Definitions, the PLCS PLM web services are defined more in detail. In the deliverable D3.6.2_5, WSDL of V3 services collection, the RDL web services are defined.
Short Number: D3.6.3_1
Document identifier: VIVACE 3.6/3/VAC/T/05008-1.1
Abstract: This document includes surveys of current state of the art models used for context and content management along with surveys of the state of the art in binary data representation. The context and content models are either standards based or provided by VIVACE member companies. The information models will allow the communication and exchange functionality within the collaboration hub and its peers. This version of the document includes suggested models for further development, initial model extensions and planned future work within VIVACE task 3.6.3.
Short Number: D3.6.3_2
Document identifier: VIVACE 3.6/3/VAC/T/06004-1.2
Abstract: The context and content models are either standard based or provided by VIVACE member companies. The information models will allow the communication and exchange functionality within the collaboration hub and its peers. This document describes the modelling work and the initial extensions made to the information models between months 18 – 30 of the VIVACE project.
Short Number: D3.6.3_4
Document identifier: VIVACE 3.6/3/ECS/T/07003-1.0
Abstract: This document describes the technical content of the PLCS PLM Services and serves as a reference usage guide. The Web Service specification is documented and explained in terms of use cases and diagrams. A separate document, “WSDL of V3 services collection”, describes the accompanying XML Schemas for all the types used in the WSDL specifications. All the specified Web Services in the WSDL specifications are not yet described in this definition document. They are marked
Short Number: D3.6.4_2
Document identifier: VIVACE 3.6.4/AVIO/T/06005/1.1
Abstract: After describing the requirement capturing methodology used for collecting the VIVACE requirements, the document provides a thorough description of the Use Cases and Scenarios used to identify the requirements that are subsequently harmonized and mapped towards actual service implementation. Particular emphasis is placed on the description of an integrated Use Case proposed with the objective of identifying a common Use Case, between WP3.6, WP3.2 and all WP2.3 tasks, which would be more appropriate for demonstration purposes.
Short Number: D3.6.4_4
Document identifier: VIVACE 3.6/4/AVIO/T/07008
Abstract: This document contains the VEC-Hub Usage Guidelines. It is not intended to be a detailed user’s manual, but rather a collection of general good practice aids on how to face the typical issues that may arise in a collaborative environment when using an advanced collaboration tool such as the VEC-Hub.