CPO Statement of [Company Name]

Following the prerequisites of ProSTEP iViP’s Code of PLM Openness (CPO) IT vendors shall determine and provide a list of their relevant products and the degree of fulfillment as a “CPO Statement” (cf. CPO Chapter 2.8).

This CPO Statement refers to:

Product Name	Name
Product Version	Version number, Release, SP etc.
Contact	Full name of the CPO-related contact e-mail@ad.dress

This CPO Statement was created and published by [Company Name] in form of a self-assessment with regard to the CPO.

Publication Date of this CPO Statement: DD Month 201x

Content

1 Executive Summary	2

2 Details of Self-Assessment	2

2.1 CPO Chapter 2.1: Interoperability	2

2.2 CPO Chapter 2.2: Infrastructure	2

2.3 CPO Chapter 2.5: Standards	2

2.4 CPO Chapter 2.6: Architecture	2

2.5 CPO Chapter 2.7: Partnership	2

2.5.1 Data Generated by Users	2

2.5.2 Partnership Models	2

2.5.3 Support of User and Innovation Groups	2

2.6 Additional Information	2

Executive Summary

max. 1.500 characters, including spaces

Company Name:	[Company Name]	Contact Person:	[Contact Name]
Product Name:	[Product Name]
CPO Term	Fulfilled (100%)	Comments because of deviations
2.1 Interoperability	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.2 Infrastructure	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.3 Extensibility	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.4 Interfaces	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.5 Standards	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.6 Architecture	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
2.7 Partnership	☐	Comments: Please provide your reasons for deviations Convergence Path: Please provide your plan for CPO convergence, if intended
List of inherent supported neutral standards	API: ☐C/C++ / ☐Java / ☐.NET / ☐Web Services / Others: Please provide, if desired 3D: ☐IGES / ☐JT / ☐STL / ☐STEP / ☐VRML / Others: Please provide, if desired DX: ☐eCl@ss / ☐FMI / ☐IDX / ☐PDF / ☐ReqIF / ☐STEP / ☐VEC Others: Please provide more or URL to product flyers, if desired Remarks: Please provide information, if e.g. certain standards are not supported throughout the whole software suite for which you want to provide this statement.

Details of Self-Assessment

The following chapters summarize the results of the CPO-related self-assessment of [Company Name] with regard to [Product Name].

CPO Chapter 2.1: Interoperability

APIs have the following standard language bindings:

Please provide relevant information or URL to product flyers providing relevant information

Remark: If detailed information with regard to bindings are not given (e.g. C++, instead of C++11 (ISO/IEC 14882:2011), maybe additional clarification efforts arise.

CPO Chapter 2.2: Infrastructure

Supported platforms (hardware and OS) are:

Please provide relevant information or URL to product flyers providing relevant information

Remark: If detailed information with regard to platforms are not given (e.g. OS Version and Service Pack), maybe additional clarification efforts arise.

CPO Chapter 2.5: Standards

Supported data exchange formats:

Please provide relevant information or URL to product flyers providing relevant information

Remark: If detailed information with regard to name and version (e.g. STEP AP 214 (ISO 10303-214:2010)), considered Implementation Guidelines (e.g. CAx-IF Recommended Practices) and potential participation in related Implementor Forums (e.g. CAx-IF) are not given, maybe additional clarification efforts arise.

CPO Chapter 2.6: Architecture

The IT system’s architecture is conforming CPO 2.6	Yes ☐ / No ☐
Please provide relevant information or URL to product flyers providing relevant information

CPO Chapter 2.7: Partnership

Data Generated by Users

Data generated by IT users with an IT system is and remains the intellectual property of these IT users, according CPO 2.7.4	Yes ☐ / No ☐

Partnership Models

Partnership models are offered according CPO 2.7.7	Yes ☐ / No ☐
Please provide relevant information or related URL to product flyers providing relevant information

Support of User and Innovation Groups

Supported groups are:

Please provide names and, if available, related URLs to the homepages of the groups

Additional Information

Statements concerning CPO Chapter 2.3 “Extensibility” and Chapter 2.4 “Interfaces” can be noted here. For example, statements concerning “Development Environments”, “Third-party Integration”, “Version and Release Compatibility”, possibilities for “Batch Processing” and “Cancellation”.

You can note related URLs where related information can be found.