Produkte mit Kategorie, Projektgruppe, Datum und Textinhalt

691 start en de prostep ivip 10 4 2025 standards alle driving the software-defined vehicle transformation - prostep ivip's dna in the software-defined age

this report examines the shift to software-defined vehicles (sdvs) in the automotive industry, highlighting challenges and potential solutions to accelerate the transformation. an sdv is a new generation vehicle that manages most of its operations and adds functionality primarily through software, in contrast to traditional vehicles where hardware controls most functions. sdv allows for real-time adaptability, continuous updates, and enhanced features throughout the vehicle's lifecycle.

 

driving the software-defined vehicle transformation

pdf 37 pages prostep ivip's dna

---

Driving the Software-Defined Vehicle Transformation - prostep ivip's DNA in the Software-Defined Age

691 start en de prostep ivip 10 4 2025 standards alle driving the software-defined vehicle transformation - prostep ivip's dna in the software-defined age

this report examines the shift to software-defined vehicles (sdvs) in the automotive industry, highlighting challenges and potential solutions to accelerate the transformation. an sdv is a new generation vehicle that manages most of its operations and adds functionality primarily through software, in contrast to traditional vehicles where hardware controls most functions. sdv allows for real-time adaptability, continuous updates, and enhanced features throughout the vehicle's lifecycle.

 

driving the software-defined vehicle transformation pdf 37 seiten driving the software-defined vehicle transformation - prostep ivip's dna in the software-defined age

7. Benchmark (CAD) 2001

158 start benchmark stepbenchmark mitglied 11 2001 step en 7. benchmark (cad) 2001 benchmark - ausführlicher bericht zum 7. benchmark

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the compatibility and scope of the implementation of the available step products. the increasing number of new participants is the result of the intensive activities in the cax implementor forum. the 7th benchmark, particularly evaluated capabilities for product data exchange with respect to geometry and more detail processor handling. the new topics validation properties and 3d-text annotation tested for the first time in the last stability benchmark were updated. because of the participation of two new step translators the exchange of assemblies were tested again.

the 7th benchmark was performed using the step translators that were available by the end of june 2001. the translators were used once more in their dis (draft international standard) versions. next year the translators will become is (international standard).

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

sprache: en format: pdf (62 seiten)

---

7. Benchmark (CAD) 2001

158 start benchmark stepbenchmark mitglied 11 2001 step en 7. benchmark (cad) 2001 benchmark - detailed report to the 7th benchmark

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the compatibility and scope of the implementation of the available step products. the increasing number of new participants is the result of the intensive activities in the cax implementor forum. the 7th benchmark, particularly evaluated capabilities for product data exchange with respect to geometry and more detail processor handling. the new topics validation properties and 3d-text annotation tested for the first time in the last stability benchmark were updated. because of the participation of two new step translators the exchange of assemblies were tested again.

the 7th benchmark was performed using the step translators that were available by the end of june 2001. the translators were used once more in their dis (draft international standard) versions. next year the translators will become is (international standard).

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

language: en format: pdf (62 pages)

7. Benchmark (CAD) 2001 - Short Report

157 benchmark stepbenchmark alle 11 2001 step en 7. benchmark (cad) 2001 - short report step, benchmark - comparative test of stepprocessors language: en format: pdf (9 pages)

---

7. Benchmark (CAD) 2001 - Short Report

157 benchmark stepbenchmark alle 11 2001 step en 7. benchmark (cad) 2001 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (9 seiten)

CC8 Recommended Practices - Specification and Cofiguration / Product Coding / Documents and Transformation Matrices

125 start guideline recommendations&standards mitglied 12 2002 step en cc8 recommended practices - specification and cofiguration / product coding / documents and transformation matrices iso 10303, step, ap214, conformance class 8 - recommended practices for the usage of step ap214 cc8 language: en format: pdf (75 pages)

---

CC8 Recommended Practices - Specification and Cofiguration / Product Coding / Documents and Transformation Matrices

125 start guideline recommendations&standards mitglied 12 2002 step en cc8 recommended practices - specification and cofiguration / product coding / documents and transformation matrices iso 10303, step, ap214, conformance class 8 - recommended practices for the usage of step ap214 cc8 sprache: en format: pdf (75 seiten)

prostep ivip White Paper 
Collaborative Digital Twin

690 start cdt alle 20 12 2024 en de white-paper prostep ivip white paper 
collaborative digital twin (cdt)

the collaborative digital twin (cdt) initiative, which was launched by the prostep ivip association and

the german association of the automotive industry (vda), aims to explore a new way to collaborate

among development partners taking the digital twin concept into account. central to this is work package

2 (wp2), which focuses on enabling seamless cross-enterprise engineering collaboration by addressing

challenges such as data fidelity, global workflows, and supply chain digitalization.

the collaborative digital twin (cdt) initiative, which was launched by the prostep ivip association and

the german association of the automotive industry (vda), aims to explore a new way to collaborate

among development partners taking the digital twin concept into account. central to this is work package

2 (wp2), which focuses on enabling seamless cross-enterprise engineering collaboration by addressing

challenges such as data fidelity, global workflows, and supply chain digitalization.

this white paper highlights the cdt’s vision to transition from asynchronous file exchanges to

synchronous, semantically aligned linked data. key features include precise data exchange, automated

synchronization, robust

pdf 24 seiten prostep ivip white paper 
collaborative digital twin

---

prostep ivip White Paper 
Collaborative Digital Twin

690 start cdt alle 20 12 2024 en de white-paper prostep ivip white paper 
collaborative digital twin prostep ivip white paper 
collaborative digital twin (cdt) the collaborative digital twin (cdt) initiative, which was launched by the prostep ivip association and the german association of the automotive industry (vda), aims to explore a new way to collaborate

the collaborative digital twin (cdt) initiative, which was launched by the prostep ivip association and the german association of the automotive industry (vda), aims to explore a new way to collaborate

pdf 24 pages

CPM Implementation Guideline

118 start guideline implementationguidelines mitglied 21 12 2007 en cpm implementation guideline implementation guideline for psi 1-2 "collaborative project management - data exchange model"

this implementation guideline was created to facilitate implementation of the cpm data exchange model for use in cross-enterprise or cross-departmental projects.

this document will help you interpret the standard – collaborative project management” data exchange model (psi 1-2) – and also provides more detailed information about special requirements in certain application scenarios and the use of objects and their lifecycle during data exchange.

the aim of the cpm recommendations is to allow you to handle the work performed in the type of projects mentioned above in a more goal-oriented manner and thus improve efficiency.

the following basic assumptions are made:

every company uses some kind of project management software independently. this software has been extended to include a cpm component which allows data objects to be created and sent according to the cpm data exchange model.

a standard is required for collaboration which defines the objects to be exchanged and describes how this exchange takes place. this standard is extended so that the handling of the prescribed data objects is clearly described and to ensure that the project management software implementations provided by various system vendors remain compatible.

this document is intended for system vendors of project management software and it and/or method labs that provide their departments with the appropriate project engineering/implementations.

language: en format: pdf (96 pages)

---

CPM Implementation Guideline

118 start guideline implementationguidelines mitglied 21 12 2007 en cpm implementation guideline implementation guideline for psi 1-2 "collaborative project management - data exchange model"

this implementation guideline was created to facilitate implementation of the cpm data exchange model for use in cross-enterprise or cross-departmental projects.

this document will help you interpret the standard – collaborative project management” data exchange model (psi 1-2) – and also provides more detailed information about special requirements in certain application scenarios and the use of objects and their lifecycle during data exchange.

the aim of the cpm recommendations is to allow you to handle the work performed in the type of projects mentioned above in a more goal-oriented manner and thus improve efficiency.

the following basic assumptions are made:

every company uses some kind of project management software independently. this software has been extended to include a cpm component which allows data objects to be created and sent according to the cpm data exchange model.

a standard is required for collaboration which defines the objects to be exchanged and describes how this exchange takes place. this standard is extended so that the handling of the prescribed data objects is clearly described and to ensure that the project management software implementations provided by various system vendors remain compatible.

this document is intended for system vendors of project management software and it and/or method labs that provide their departments with the appropriate project engineering/implementations.

sprache: en format: pdf (96 seiten)

CATIA V5 STEP AP 214 Mapping

122 start guideline implementationguidelines mitglied 6 2006 step en catia v5 step ap 214 mapping problems and analyses problems, definition of a step ap 214 mapping for catia

the pdm user group is a forum for companies, which use pdm systems and exchange pdm data. in 2005 the main focus of the group was the catia v5 data exchange, because the switch from catia v4 to v5 has caused basic data exchange problems.

the results of the pdm user group’s work in 2005 is this “best practice”. it describes the problems, analyses the causes of the problems and defines a step ap 214 mapping for catia v5 related pdm data.

this document is addressed to all pdm related engineers and computer scientists, like pdm architects and pdm implementers.

taking a shallow look at the increasing catia v5 functionality, some people may think, that they don’t need step ap 214 based data exchange any more, because catia v5 stores the assembly structure, part ids, customer attributes and many other properties.

this simple approach doesn’t consider, that catia v5 is not used stand alone, but within pdmintegrations. the main problem is the usage of inter-document links in catia v5. the catia v5 links can build a network-like document structure. the pdm systems handle these links differently and there are company-specific construction guidelines, which define restrictions to the link usage.

therefore the goal of this “best practice” is to find a cata v5 - step ap 214 mapping to enable step based catia v5 data exchange with

1. no impacts from partner specific catia v5 methodology
2. no limitation of used catia v5 functionality
3. all used pdm systems (with catia v5 integration)

in other words: each data exchange partner should be able to exchange his cad and meta data with each other with only one step processor.

language: en format: pdf (41 pages)

---

CATIA V5 STEP AP 214 Mapping

122 start guideline implementationguidelines mitglied 6 2006 step en catia v5 step ap 214 mapping problems and analyses problems, definition of a step ap 214 mapping for catia

the pdm user group is a forum for companies, which use pdm systems and exchange pdm data. in 2005 the main focus of the group was the catia v5 data exchange, because the switch from catia v4 to v5 has caused basic data exchange problems.

the results of the pdm user group’s work in 2005 is this “best practice”. it describes the problems, analyses the causes of the problems and defines a step ap 214 mapping for catia v5 related pdm data.

this document is addressed to all pdm related engineers and computer scientists, like pdm architects and pdm implementers.

taking a shallow look at the increasing catia v5 functionality, some people may think, that they don’t need step ap 214 based data exchange any more, because catia v5 stores the assembly structure, part ids, customer attributes and many other properties.

this simple approach doesn’t consider, that catia v5 is not used stand alone, but within pdmintegrations. the main problem is the usage of inter-document links in catia v5. the catia v5 links can build a network-like document structure. the pdm systems handle these links differently and there are company-specific construction guidelines, which define restrictions to the link usage.

therefore the goal of this “best practice” is to find a cata v5 - step ap 214 mapping to enable step based catia v5 data exchange with

1. no impacts from partner specific catia v5 methodology
2. no limitation of used catia v5 functionality
3. all used pdm systems (with catia v5 integration)

in other words: each data exchange partner should be able to exchange his cad and meta data with each other with only one step processor.

sprache: en format: pdf (41 seiten)

Digital Data Package (DDP) Recommendation

180 standards prostepivip alle 4 2023 en digital data package (ddp) recommendation this prostep ivip / vda recommendation has been published by the digital data package (ddp) working group.

this prostep ivip / vda recommendation has been published by the digital data package (ddp) working group.

the ddp defines a standardized container format for the exchange of machine-readable and human-readable product data. it allows the exchange of, as well as the collaboration on semantic product data that is linked across different standard formats and domains across the entire product lifecycle. ddps can be used within an organization, as well as for data exchange and collaboration with partners, customers, and suppliers.

the digital data package is based on standardized neutral formats such as reqif, sysml xmi, step ap242, vec, etc. rather than a multitude of proprietary data formats. this ensures that the ddp is closely linked to the results from standardization committees and the projects in the prostep ivip association. in addition to format-specific working groups such as the jt wf and sysml wf, these include in particular the standardization strategy board (ssb) as the governing body for defining relevant standards and formats, and the integration collaboration framework (icf) as a cross-domain integration project.

the data model defined for and used in the ddp, has been aligned with the icf working group and will also be used and extended in the collaborative systems engineering (cse) working group.

language: en format: zip file

---

Digital Data Package (DDP) Recommendation

180 standards prostepivip alle 4 2023 en digital data package (ddp) recommendation this prostep ivip / vda recommendation has been published by the digital data package (ddp) working group.

this prostep ivip / vda recommendation has been published by the digital data package (ddp) working group.

the ddp defines a standardized container format for the exchange of machine-readable and human-readable product data. it allows the exchange of, as well as the collaboration on semantic product data that is linked across different standard formats and domains across the entire product lifecycle. ddps can be used within an organization, as well as for data exchange and collaboration with partners, customers, and suppliers.

the digital data package is based on standardized neutral formats such as reqif, sysml xmi, step ap242, vec, etc. rather than a multitude of proprietary data formats. this ensures that the ddp is closely linked to the results from standardization committees and the projects in the prostep ivip association. in addition to format-specific working groups such as the jt wf and sysml wf, these include in particular the standardization strategy board (ssb) as the governing body for defining relevant standards and formats, and the integration collaboration framework (icf) as a cross-domain integration project.

the data model defined for and used in the ddp, has been aligned with the icf working group and will also be used and extended in the collaborative systems engineering (cse) working group.

sprache: en format: zip-datei

ECR Implementation Guide V1-1

120 start guideline implementationguidelines mitglied 30 11 2007 en ecr implementation guide v1-1 implementation guideline for "engineering change requests" version 1.1

this document is a concretion of the vda recommendation 4965, v 2.0. its purpose is to describe additional aspects which are not covered by the vda recommendation due to various reasons, but which seems to be necessary in order to implement the vda recommendation or parts of it with the necessary quality. the guideline is a result of the prostep ivip project group engineering change management – implementor forum (ecm-if) and the prostep ivip / vda project group engineering change management (ecm), which specified the vda 4965, v2.0.

this document covers the scope defined by the interaction scenarios 1 and 2 of the vda recommendation 4965-1 on the ecm sub-process engineering change request (ecr). thus, it is also called ecr implementation guide.

language: en format: pdf (51 pages)

---

ECR Implementation Guide V1-1

120 start guideline implementationguidelines mitglied 30 11 2007 en ecr implementation guide v1-1 implementation guideline for "engineering change requests" version 1.1

this document is a concretion of the vda recommendation 4965, v 2.0. its purpose is to describe additional aspects which are not covered by the vda recommendation due to various reasons, but which seems to be necessary in order to implement the vda recommendation or parts of it with the necessary quality. the guideline is a result of the prostep ivip project group engineering change management – implementor forum (ecm-if) and the prostep ivip / vda project group engineering change management (ecm), which specified the vda 4965, v2.0.

this document covers the scope defined by the interaction scenarios 1 and 2 of the vda recommendation 4965-1 on the ecm sub-process engineering change request (ecr). thus, it is also called ecr implementation guide.

sprache: en format: pdf (51 seiten)

ECAD/MCAD Collaboration Implementation Guidelines

112 start guideline implementationguidelines mitglied 01 7 2018 ecad-mcad en ecad/mcad collaboration implementation guidelines implementation guidelines for psi 5 v3.5 "ecad/mcad collaboration"

this implementation guideline accompanies the prostep ivip psi5 recommendation for ecad/mcad-collaboration.

language: en format: pdf (83 pages)

---

ECAD/MCAD Collaboration Implementation Guidelines

112 start guideline implementationguidelines mitglied 01 7 2018 ecad-mcad en ecad/mcad collaboration implementation guidelines implementation guidelines for psi 5 v3.5 "ecad/mcad collaboration"

this implementation guideline accompanies the prostep ivip psi5 recommendation for ecad/mcad-collaboration.

sprache: en format: pdf (83 seiten)

Executive Summary - Collaborative Product Visualization

64 start executive-summaries alle 4 2007 en de executive summary - collaborative product visualization closing process gaps with visualization

increasing national and international competition is forcing companies to introduce new products at an ever faster rate, shorten the product development times, lower costs, improve product quality, and improve innovative capabilities. to master these challenges, companies are pressing ahead with distributed development and collaboration with suppliers and service providers. against this background, the realization of simple, streamline data exchange processes is becoming increasingly important.

language: en & de format: pdf (4 pages)

---

Executive Summary - Collaborative Product Visualization

64 start executive-summaries alle 4 2007 en de executive summary - collaborative product visualization mit visualisierung prozesslücken schließen

der wachsende nationale wie internationale wettbewerb zwingt unternehmen zur schnelleren markteinführung von produkten, kürzeren produktentwicklungszeiten, sinkenden kosten, verbesserter produktqualität und wachsender innovationsfähigkeit. um diesen forderungen gerecht zu werden, forcieren unternehmen die zusammenarbeit mit zulieferern und entwicklungsdienstleistern. der realisierung von einfachen, schlanken datenaustauschprozessen kommt in diesem zusammenhang eine immer größere bedeutung zu.

sprache: de & en format: pdf (4 seiten)

Executive Summary "Engineering 2010 - Setting the Course for Innovative Engineering

65 executive-summaries alle 4 2005 ssb en executive summary "engineering 2010 - setting the course for innovative engineering

the realization of efficient product development and production processes forms the basis for economic success. it is of vital importance to keep up with the technological development in order to be able to react to new developments in time and furthermore to actively participate in the future evolution of development related technologies. in this context, the domains of functional mock-up, collaborative requirements management, collaborative project engineering, vr-engineering, it-security in virtual product creation, and knowledge based engineering are of particular importance and require detailed attention.

the study “setting the course for innovative engineering” has been conducted with the major objective of identifying it-potentials in product creation and possible realization strategies up to the year 2010. this study pays special attention to the domains mentioned above and describes comprehensively the respective states of the art, deficits and requirements, trends and visions, realization subjects and strategies, as well as benefits and success criteria. the present article summarizes the results of the study which was conducted by fraunhofer ipk in cooperation with tu münchen (iwb), tu darmstadt (dik), tu chemnitz (ftu), computer graphics center (zgdv e.v.), and universidade metodista de piracicaba, brasil (unimep). it was kindly financed by prostep ivip association.

language: en format: pdf (8 pages)

---

Executive Summary "Engineering 2010 - Setting the Course for Innovative Engineering

65 executive-summaries alle 4 2005 ssb en executive summary "engineering 2010 - setting the course for innovative engineering produktentwicklung in der zukunft, funktional mock-up, requirements management, project engineering, vr, it-sicherheit, kbe - zusammenfassung der gleichnamigen studie

the realization of efficient product development and production processes forms the basis for economic success. it is of vital importance to keep up with the technological development in order to be able to react to new developments in time and furthermore to actively participate in the future evolution of development related technologies. in this context, the domains of functional mock-up, collaborative requirements management, collaborative project engineering, vr-engineering, it-security in virtual product creation, and knowledge based engineering are of particular importance and require detailed attention.

the study “setting the course for innovative engineering” has been conducted with the major objective of identifying it-potentials in product creation and possible realization strategies up to the year 2010. this study pays special attention to the domains mentioned above and describes comprehensively the respective states of the art, deficits and requirements, trends and visions, realization subjects and strategies, as well as benefits and success criteria. the present article summarizes the results of the study which was conducted by fraunhofer ipk in cooperation with tu münchen (iwb), tu darmstadt (dik), tu chemnitz (ftu), computer graphics center (zgdv e.v.), and universidade metodista de piracicaba, brasil (unimep). it was kindly financed by prostep ivip association.

sprache: en format: pdf (8 seiten)

Executive Summary - Visualisierungsformate und Strukturdatenaustausch

66 executive-summaries alle 4 2005 en de executive summary - visualisierungsformate und strukturdatenaustausch projektstudie zur bewertung des datenformats jt und einordnung der jt open aktivität

aufgrund gestiegener produktkomplexität sowie gleichzeitig kürzerer entwicklungs- und herstellungszyklen ist eine enge zusammenarbeit zwischen produktentwicklungspartnern notwendig. engineering collaboration findet heute verstärkt in entwicklungsnetzwerken über unternehmensgrenzen hinweg statt.

dies führt nicht nur zu immer größer werdenden datenaustauschvolumina, sondern vor allem zu einem vielschichtigen komplexitätsanstieg. in diesem kontext gewinnt der austausch von visualisierungsdaten zunehmend an bedeutung. auch die forderungen nach adäquaten möglichkeiten zum strukturdatenaustausch nehmen stetig zu. gegenüber herkömmlichen cad-anwendungen bestechen etwaige anwendungen durch geringere lizenzkosten und ein breiteres anwendungsspektrum.

um seinen mitgliedern in diesem spannungsfeld umfassendere informationen zu verschaffen, hat der prostep ivip verein 2004 zwei, aufeinander aufbauende studien in auftrag gegeben. der schwerpunkt der ersten studie lag dabei auf der bewertung des datenformats jt und der einordnung der jt open aktivität. die zweite studie umfasste eine analyse des unternehmensübergreifenden visualisierungsdaten- und strukturdatenaustauschs. mit der durchführung beider studien wurde das fachgebiet datenverarbeitung in der konstruktion (dik), tu darmstadt, beauftragt. die patenschaft übernahmen die firmen bosch und siemens. das vorliegende dokument gibt die wesentlichen ergebnisse der studien wieder.

sprache: de & en format: pdf (4 seiten)

---

Executive Summary - Visualization Formats and Assembly Data Exchange

66 executive-summaries alle 4 2005 en de executive summary - visualization formats and assembly data exchange project study involving the evaluation of the jt data format and an appraisal of the jt open activity

increasing product complexity in conjunction with ever shorter development and manufacturing cycles means that close cooperation between product development partners is a necessity. today's engineering collaboration takes place to an increasing extent in development networks that span corporate borders.

this not only results in an ever-growing volume of data being exchanged but, above all, in an increase of complexity on many levels. within this context, the exchange of visualization data is becoming more and more important, and the demand for appropriate means of exchanging structure data is growing. compared with conventional cad applications, possible applications provide a persuasive argument in their favor in the form of lower licensing costs and a broader range of application.

in order to provide its members with more comprehensive information relating to this energized area, the prostep ivip association commissioned two studies that are based on each other in 2004. the main focus of the first study was an evaluation of the jt data format and an appraisal of the jt open activity. the second study comprised an analysis of the cross-enterprise exchange of visualization and assembly data. the department for computer integrated design (dik) at the technical university of darmstadt was commissioned to carry out both studies. the studies were advised by bosch and siemens. this document provides an overview of the most important results of the studies.

language: en & de format: pdf (4 pages)

Recommendation - Automated Functional Data Exchange in the Automobile Industry - Part 3.3 Wheel Brake

176 start standards prostepivip alle 7 2023 fdx en recommendation - automated functional data exchange in the automobile industry - part 3.3 wheel brake this prostep ivip (psi) / vda recommendation was drawn up by the functional data exchange (fdx) working group and defines a standard format and a machine-readable specification of a data model/data format for the transfer of functional data between customers and their suppliers.

this prostep ivip (psi) / vda recommendation was drawn up by the functional data exchange (fdx) working group and defines a standard format and a machine-readable specification of a data model/data format for the transfer of functional data (e.g., characteristic diagrams, characteristic curves, characteristic values) between customers and their suppliers.

it enables the exchange of highly structured data. this recommendation aims at facilitating consistent and efficient implementation of these processes in the automotive industry.

objectives:

• harmonization of the exchange of functional data between oems and suppliers
• improved quality and availability of functional data for cae/simulation purposes
• elimination of discrepancies in functional data between ordered and delivered data
• higher level of automation for data generation, data exchange and data use

language: en format: pdf (22 pages)

---

Recommendation - Automated Functional Data Exchange in the Automobile Industry - Part 3.3 Wheel Brake

176 start standards prostepivip alle 7 2023 fdx en recommendation - automated functional data exchange in the automobile industry - part 3.3 wheel brake this prostep ivip (psi) / vda recommendation was drawn up by the functional data exchange (fdx) working group and defines a standard format and a machine-readable specification of a data model/data format for the transfer of functional data between customers and their suppliers.

this prostep ivip (psi) / vda recommendation was drawn up by the functional data exchange (fdx) working group and defines a standard format and a machine-readable specification of a data model/data format for the transfer of functional data (e.g., characteristic diagrams, characteristic curves, characteristic values) between customers and their suppliers.

it enables the exchange of highly structured data. this recommendation aims at facilitating consistent and efficient implementation of these processes in the automotive industry.

objectives:

• harmonization of the exchange of functional data between oems and suppliers
• improved quality and availability of functional data for cae/simulation purposes
• elimination of discrepancies in functional data between ordered and delivered data
• higher level of automation for data generation, data exchange and data use

sprache: en format: pdf (22 seiten)

Does PLM have a Future in the Age of Digitalization?

79 white-paper alle 25 7 2016 ssb en de does plm have a future in the age of digitalization? position paper: future plm

introducing and operating a plm system is a cost-intensive undertaking. according to plm expert john stark, half of all plm projects end in failure. the networking of products and services via the internet of things (iot) raises the question of whether plm is now no longer up to the demands placed on it. is plm, as we know it today, on its way out, rendered obsolete by linked data, big data and self-learning systems? or, to put the question differently, how will plm have to change in order to provide companies with optimum support during their digital transformation?

plm experts from user firms, software vendors, consulting companies and universities addressed these questions in a workshop and raised a variety of issues concerning "future plm" in order to prompt a discussion of requirements and possible solutions. the authors of this position paper are sylke rosenplänter (opel), bodo machner (formerly bmw), thomas kamps (conweaver), karsten theis (prostep), martin eigner (kaiserslautern technical university) and trade journalist michael wendenburg. all of them agree that we need a new type of plm.

this position paper comprises the 22 work out theses and invites all reader, to provide comments and discuss it in public.

language: en & de format: zip file

---

Hat PLM im Zeitalter der Digitalisierung eine Zukunft?

79 white-paper alle 25 7 2016 ssb en de hat plm im zeitalter der digitalisierung eine zukunft? freies thesenpapier future plm

systemeinführung und betrieb eines plm-systems sind kostenintensiv. nach einschätzung des plmexperten john stark scheitert jedes zweite plm-projekt. die vernetzung von produkten und services über das internet of things (iot) wirft die frage auf, ob plm damit nicht vollends überfordert ist? ist plm – so wie wir es heute kennen – ein auslaufmodell, das durch linked data, big data oder selbstlernende systeme obsolet wird? oder anders gefragt, wie muss sich plm verändern, um die unternehmen bei ihrer digitalen transformation optimal unterstützen zu können?

plm-experten von anwendungsunternehmen, softwareherstellern, beratungshäusern und hochschulen haben diese fragen in einem workshop diskutiert und dazu eine reihe von thesen zu future plm aufgestellt, um damit die diskussion zu anforderungen und lösungsansätzen anzustoßen. autoren dieses thesenpapiers sind sylke rosenplänter (opel), bodo machner (ehemals bmw), thomas kamps (conweaver), karsten theis (prostep), martin eigner (tu kaiserslautern) und fachjournalist michael wendenburg. sie sind sich einig, dass es eine andere art von plm braucht.

dieses papier fasst 22 herausgearbeitete thesen zusammen und fordert die leser auf, es zu kommentieren und öffentlich zu diskutieren.

sprache: de & en format: zip-datei

CPM-Expertenbefragung

88 start white-paper alle 12 2009 psms de cpm-expertenbefragung zusammenfassung der ergebnisse der cpm-expertenbefragung 2009

der prostep ivip verein ist in kooperation mit dem fachbereich wirtschaft der hochschule darmstadt sowie mit der deutschen gesellschaft für projektmanagement (gpm) der frage nachgegangen, welche speziellen projektmanagementmethoden und -prozesse einen nachhaltigen und positiven einfluss auf den erfolg unternehmensübergreifender projekte im aktuellen wandel der projektmanagementlandschaft besitzen.

im mittelpunkt der im sommer 2009 durchgeführten studie standen die kritischen erfolgsfaktoren für eine zusammenarbeit über die unternehmensgrenzen hinweg. darüber hinaus wurden rationalisierungspotenziale aufgedeckt, in denen notwendige veränderungen durchgeführt werden müssen, um eine effektive und effiziente projektarbeit gewährleisten zu können.

damit die vielzahl verschiedener methoden und prozesse erfasst werden konnte, wurde eine qualitative befragung mit insgesamt 26 antworten aus der industrie- und dienstleistungsunternehmen durchgeführt.

gemeinsam ist, dass alle untersuchungsteilnehmer projekte über die grenzen ihrer unternehmen hinaus in einem kooperativen vertragsverhältnis mit anderen projektpartnern durchführen.

mit der vorliegenden studie soll die diskussion über möglichkeiten neuer projektmanagementansätze zur förderung unternehmensübergreifender projektarbeit weiter vertieft werden.

die angesprochenen empfehlungen wenden sich gleichermaßen an projektmitarbeiter, projektmanager, schnittstelleninhaber wie manager und controller sowie projektportfoliomanager aus verschiedenen bereichen der wirtschaft und industrie.

die ergebnisse der durchgeführten befragung können als trend in der wirtschaftlichen und industriellen praxis gewertet werden, die sich zum einen gezielt mit vorhandenen problemfeldern auseinandersetzen und zum anderen lösungsansätze aus der unternehmensübergreifenden projektarbeit bieten.

language: de format: pdf (13 pages)

---

CPM-Expertenbefragung

88 start white-paper alle 12 2009 psms de cpm-expertenbefragung zusammenfassung der ergebnisse der cpm-expertenbefragung 2009

der prostep ivip verein ist in kooperation mit dem fachbereich wirtschaft der hochschule darmstadt sowie mit der deutschen gesellschaft für projektmanagement (gpm) der frage nachgegangen, welche speziellen projektmanagementmethoden und -prozesse einen nachhaltigen und positiven einfluss auf den erfolg unternehmensübergreifender projekte im aktuellen wandel der projektmanagementlandschaft besitzen.

im mittelpunkt der im sommer 2009 durchgeführten studie standen die kritischen erfolgsfaktoren für eine zusammenarbeit über die unternehmensgrenzen hinweg. darüber hinaus wurden rationalisierungspotenziale aufgedeckt, in denen notwendige veränderungen durchgeführt werden müssen, um eine effektive und effiziente projektarbeit gewährleisten zu können.

damit die vielzahl verschiedener methoden und prozesse erfasst werden konnte, wurde eine qualitative befragung mit insgesamt 26 antworten aus der industrie- und dienstleistungsunternehmen durchgeführt.

gemeinsam ist, dass alle untersuchungsteilnehmer projekte über die grenzen ihrer unternehmen hinaus in einem kooperativen vertragsverhältnis mit anderen projektpartnern durchführen.

mit der vorliegenden studie soll die diskussion über möglichkeiten neuer projektmanagementansätze zur förderung unternehmensübergreifender projektarbeit weiter vertieft werden.

die angesprochenen empfehlungen wenden sich gleichermaßen an projektmitarbeiter, projektmanager, schnittstelleninhaber wie manager und controller sowie projektportfoliomanager aus verschiedenen bereichen der wirtschaft und industrie.

die ergebnisse der durchgeführten befragung können als trend in der wirtschaftlichen und industriellen praxis gewertet werden, die sich zum einen gezielt mit vorhandenen problemfeldern auseinandersetzen und zum anderen lösungsansätze aus der unternehmensübergreifenden projektarbeit bieten.

sprache: de format: pdf (13 seiten)

ISO 10303 Part 11

19 start standards iso mitglied 01 11 2004 step en iso 10303 part 11 iso standard - description methods: the express language refernce manual language: en format: pdf (270 pages)

---

ISO 10303 Part 11

19 start standards iso mitglied 01 11 2004 step en iso 10303 part 11 iso standard - description methods: the express language refernce manual sprache: en format: pdf (270 seiten)

ISO 10303 Part 203

16 start standards iso mitglied 11 2011 step en iso 10303 part 203 iso standard, step ap203 - application protocol: configuration controlled design

iso 10303-203:2010 specifies the application protocol for configuration control 3d design ed2.

the following are within the scope of iso 10303-203:2010:

• products that are mechanical parts and assemblies;
• product definition data and configuration control data pertaining to the design phase of a product's development;
• representation of an instance of a part in an assembly through its usage in a sub-assembly;
• three dimensional shape representations of a part that includes:
  • geometrically and topologically bounded wireframe models;
  • geometrically bounded surface models;
  • topologically bounded solid models with facetted, elementary and advanced faces;
  • non surface bounded solid models including constructive solid geometry, curve swept and other swept solids, thickened face solid;
  • solids with construction history;
  • topologically bounded manifold surface and subsurface and non manifold surface models;
  • topologically bounded compound models;
• geometric validation properties to allow the translation of geometric shape representations (advanced boundary representation and faceted boundary representation solids) to be checked for quality;
• geometric and dimensional tolerances applied to geometric shape representations;
• materials and their composition of chemical substance;
• composite material structure and shape;
• catalogue data characterized by property value pairs;
• three dimensional presentation of product data:
  • arranging geometric elements in layers and groups and assigning colours;
  • presentation styles for points, curves, surfaces and sections, including hatching and tiling;
  • saved views of particular camera positions and sections;
  • textual annotation and notes applied to geometric elements;
  • presentation of geometric and dimensional tolerances;
• technical drawings as two dimensional presentation of product data.

language: en format: zip file

---

ISO 10303 Part 203

16 start standards iso mitglied 11 2011 step en iso 10303 part 203 iso standard, step ap203 - application protocol: configuration controlled design

iso 10303-203:2010 specifies the application protocol for configuration control 3d design ed2.

the following are within the scope of iso 10303-203:2010:

• products that are mechanical parts and assemblies;
• product definition data and configuration control data pertaining to the design phase of a product's development;
• representation of an instance of a part in an assembly through its usage in a sub-assembly;
• three dimensional shape representations of a part that includes:
  • geometrically and topologically bounded wireframe models;
  • geometrically bounded surface models;
  • topologically bounded solid models with facetted, elementary and advanced faces;
  • non surface bounded solid models including constructive solid geometry, curve swept and other swept solids, thickened face solid;
  • solids with construction history;
  • topologically bounded manifold surface and subsurface and non manifold surface models;
  • topologically bounded compound models;
• geometric validation properties to allow the translation of geometric shape representations (advanced boundary representation and faceted boundary representation solids) to be checked for quality;
• geometric and dimensional tolerances applied to geometric shape representations;
• materials and their composition of chemical substance;
• composite material structure and shape;
• catalogue data characterized by property value pairs;
• three dimensional presentation of product data:
  • arranging geometric elements in layers and groups and assigning colours;
  • presentation styles for points, curves, surfaces and sections, including hatching and tiling;
  • saved views of particular camera positions and sections;
  • textual annotation and notes applied to geometric elements;
  • presentation of geometric and dimensional tolerances;
• technical drawings as two dimensional presentation of product data.

sprache: en format: zip-datei

ISO 10303 Part 209

21 start standards iso mitglied 01 10 2001 step en iso 10303 part 209 iso standard, step ap209 - application protocol: composite and metallic structural analysis and related design language: en format: pdf (982 pages)

---

ISO 10303 Part 209

21 start standards iso mitglied 01 10 2001 step en iso 10303 part 209 iso standard, step ap209 - application protocol: composite and metallic structural analysis and related design sprache: en format: pdf (982 seiten)

ISO 10303 Part 21

20 start standards iso mitglied 15 1 2002 step en iso 10303 part 21 iso standard - implementation methods: clear text encoding of the exchange structure language: en format: pdf (82 pages)

---

ISO 10303 Part 21

20 start standards iso mitglied 15 1 2002 step en iso 10303 part 21 iso standard - implementation methods: clear text encoding of the exchange structure sprache: en format: pdf (82 seiten)

ISO 10303 Part 212

22 start standards iso mitglied 3 2001 step en iso 10303 part 212 iso standard, step ap212 - application protocol: electrotechnical design and installation language: en format: zip file

---

ISO 10303 Part 212

22 start standards iso mitglied 3 2001 step en iso 10303 part 212 iso standard, step ap212 - application protocol: electrotechnical design and installation sprache: en format: zip-datei

ISO 10303 Part 214

17 start standards iso mitglied 01 12 2003 step en iso 10303 part 214 iso standard, step ap214 - application protocol: core data for automotive mechanical design processes language: en format: pdf (3550 pages)

---

ISO 10303 Part 214

17 start standards iso mitglied 01 12 2003 step en iso 10303 part 214 iso standard, step ap214 - application protocol: core data for automotive mechanical design processes sprache: en format: pdf (3550 seiten)

ISO 10303 Part 22

23 start standards iso mitglied 15 12 1998 step en iso 10303 part 22 iso standard - implementation methods: standard data access via interface language: en format: pdf (220 pages)

---

ISO 10303 Part 22

23 start standards iso mitglied 15 12 1998 step en iso 10303 part 22 iso standard - implementation methods: standard data access via interface sprache: en format: pdf (220 seiten)

ISO 10303 Part 239

15 start standards iso mitglied 11 2012 step en iso 10303 part 239 iso standard, step ap239 - application protocol: product life cycle support

iso 10303-239:2012 specifies the application protocol for product life cycle support.

the following are within the scope of iso 10303-239:2012:

• information for defining a complex product and its support solution;
• information required to maintain a complex product;
• information required for through life configuration change management of a product and its support solution; 
• the representation of product structures, assemblies and breakdowns including:
  • the identification and representation of parts, their versions, definitions, and documentation and management information, such as dates and approvals assigned to parts; 
  • the representation of multiple product structure views;
  • the representation of functional, physical, system and zonal breakdown of the product structure, from system via subsystems or components to end items;
  • the representation of the shape of an assembly as the composition of the shape representation of its components; 
  • the identification of positions within an assembly of parts to which component parts may be attached; 
  • the association of valued properties to a part or to an assembly; 
  • the representation of interfaces between products;
  • the classification of parts, documents and assemblies.
• the representation of a product through life including:
  • the representation of product requirements and their fulfilment;
  • the representation of existing or potential future products; 
  • the identification of the configuration of a product for a given role;
  • the specification of effectivity constraints applied to configuration of a product; 
  • the representation of predicted and observed states of products.
• the specification and planning of activities for a product including:
  • the specification of tasks to be performed on a product;
  • the representation of conditions for performing the tasks, including the resources required and the location of the resources and product;
  • the representation of the type of person and skills required for performing a task;
  • the representation of planning and scheduling of the tasks and the management and authorization of the subsequent work. 
• the representation of the activity history of a product including:
  • the recording of the usage of a product and the resource usage; 
  • the recording of the activities performed on a product and the resource usage.
• the representation of the product history including:
  • a historical record of the states of a product;
  • a historical record of the configuration status of the product;
  • the location of product data; 
  • the observation of product data.

language: en format: zip file

---

ISO 10303 Part 239

15 start standards iso mitglied 11 2012 step en iso 10303 part 239 iso standard, step ap239 - application protocol: product life cycle support

iso 10303-239:2012 specifies the application protocol for product life cycle support.

the following are within the scope of iso 10303-239:2012:

• information for defining a complex product and its support solution;
• information required to maintain a complex product;
• information required for through life configuration change management of a product and its support solution; 
• the representation of product structures, assemblies and breakdowns including:
  • the identification and representation of parts, their versions, definitions, and documentation and management information, such as dates and approvals assigned to parts; 
  • the representation of multiple product structure views;
  • the representation of functional, physical, system and zonal breakdown of the product structure, from system via subsystems or components to end items;
  • the representation of the shape of an assembly as the composition of the shape representation of its components; 
  • the identification of positions within an assembly of parts to which component parts may be attached; 
  • the association of valued properties to a part or to an assembly; 
  • the representation of interfaces between products;
  • the classification of parts, documents and assemblies.
• the representation of a product through life including:
  • the representation of product requirements and their fulfilment;
  • the representation of existing or potential future products; 
  • the identification of the configuration of a product for a given role;
  • the specification of effectivity constraints applied to configuration of a product; 
  • the representation of predicted and observed states of products.
• the specification and planning of activities for a product including:
  • the specification of tasks to be performed on a product;
  • the representation of conditions for performing the tasks, including the resources required and the location of the resources and product;
  • the representation of the type of person and skills required for performing a task;
  • the representation of planning and scheduling of the tasks and the management and authorization of the subsequent work. 
• the representation of the activity history of a product including:
  • the recording of the usage of a product and the resource usage; 
  • the recording of the activities performed on a product and the resource usage.
• the representation of the product history including:
  • a historical record of the states of a product;
  • a historical record of the configuration status of the product;
  • the location of product data; 
  • the observation of product data.

sprache: en format: zip-datei

ISO 10303 Part 28

18 start standards iso mitglied 01 8 2003 step en iso 10303 part 28 iso standard - implementation methods: xml representations of express schemas and data, using xml schemas language: en format: pdf (366 pages)

---

ISO 10303 Part 28

18 start standards iso mitglied 01 8 2003 step en iso 10303 part 28 iso standard - implementation methods: xml representations of express schemas and data, using xml schemas sprache: en format: pdf (366 seiten)

ISO 14306

14 start standards iso mitglied 15 12 2012 jt en iso 14306 industrial automation systems and integration - jt file format specification for 3d visualization language: en format: pdf (578 pages)

---

ISO 14306

14 start standards iso mitglied 15 12 2012 jt en iso 14306 industrial automation systems and integration - jt file format specification for 3d visualization sprache: en format: pdf (578 seiten)

PSI 14, Part 1, V 3.1

31 start prostep ivip alle jt en 3 4 2024 psi 14, part 1, v 3.1 jt industrial application package
edition 3.1
jt file format specification

the jt format is an industry focused, high-performance, lightweight, flexible file format for capturing and repurposing 3d product definition data for visualization to enable collaboration and validation throughout the extended enterprise. the jt format is streamable and contains compression for compact and efficient representation.

some of the highlights of the jt format include:

built-in support for assemblies, sub-assemblies and part constructs;

a flexible partitioning scheme, supporting single or multiple files;

b-rep solid shape representations to provide precision to the light-weight viewing processes;

product manufacturing information in support of paperless manufacturing initiatives;

precise and imprecise wireframe shape representations;

discrete purpose-built levels of detail;

triangle sets, polygon sets, point sets, line sets and implicit primitive sets (such as cylinder, cone and sphere);

a full array of visual attributes such as for materials, textures, lights;

hierarchical bounding box and bounding spheres;

data compression that allows producers of jt files to fine tune the trade-off between compression ratio and fidelity of the data.

beyond the data contents description of the jt format, the overall physical structure/organization of the format is also designed to support operations such as:

offline optimizations of the data contents, i.e. file granularity and flexibility optimized to meet the needs of enterprise data translation solutions;

asynchronous streaming of content, i.e. viewing optimizations such as view frustum and

occlusion culling and fixed-framerate display modes;

layers, and layer filters.

note this document is based on the jt open version 10.5 specification.

language: en format: pdf (2008 pages)

---

PSI 14, Part 1, V 3.1

31 start prostep ivip alle jt en 3 4 2024 psi 14, part 1, v 3.1 jt industrial application package
edition 3.1
jt file format specification

the jt format is an industry focused, high-performance, lightweight, flexible file format for capturing and repurposing 3d product definition data for visualization to enable collaboration and validation throughout the extended enterprise. the jt format is streamable and contains compression for compact and efficient representation.

some of the highlights of the jt format include:

built-in support for assemblies, sub-assemblies and part constructs;

a flexible partitioning scheme, supporting single or multiple files;

b-rep solid shape representations to provide precision to the light-weight viewing processes;

product manufacturing information in support of paperless manufacturing initiatives;

precise and imprecise wireframe shape representations;

discrete purpose-built levels of detail;

triangle sets, polygon sets, point sets, line sets and implicit primitive sets (such as cylinder, cone and sphere);

a full array of visual attributes such as for materials, textures, lights;

hierarchical bounding box and bounding spheres;

data compression that allows producers of jt files to fine tune the trade-off between compression ratio and fidelity of the data.

beyond the data contents description of the jt format, the overall physical structure/organization of the format is also designed to support operations such as:

offline optimizations of the data contents, i.e. file granularity and flexibility optimized to meet the needs of enterprise data translation solutions;

asynchronous streaming of content, i.e. viewing optimizations such as view frustum and

occlusion culling and fixed-framerate display modes;

layers, and layer filters.

note this document is based on the jt open version 10.5 specification.

sprache: en format: pdf (2008 seiten)

1. JT Benchmark - Long Report

144 start benchmark jtbenchmark mitglied 13 1 2010 jt en 1. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the publication of the jt specification as an iso publicly available specification (pas 14306) has laid the foundation for taking the jt format into consideration when designing efficient plm processes.

the test criteria for the benchmark were derived from use cases defined by representative of leading oems and suppliers from the automotive and aerospace industries in the prostep ivip / vda jt workflow forum. only test criteria that can be satisfied in accordance with iso pas 14306 were considered. in addition to the core topics related to the application of jt – visualization and the use of jt in downstream processes – data exchange processes, were, of course also described.

since those involved saw the greatest need for clarification in classic data exchange scenarios and wanted to test the extent to which they could rely on the systems and converters already in use at their companies to implement the defined use cases, a pragmatic approach was selected for the first benchmark.

this document provides you with the results of the first prostep ivip/vda jt translator benchmark.

sprache: en format: pdf (98 seiten)

---

1. JT Benchmark - Long Report

144 start benchmark jtbenchmark mitglied 13 1 2010 jt en 1. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the publication of the jt specification as an iso publicly available specification (pas 14306) has laid the foundation for taking the jt format into consideration when designing efficient plm processes.

the test criteria for the benchmark were derived from use cases defined by representative of leading oems and suppliers from the automotive and aerospace industries in the prostep ivip / vda jt workflow forum. only test criteria that can be satisfied in accordance with iso pas 14306 were considered. in addition to the core topics related to the application of jt – visualization and the use of jt in downstream processes – data exchange processes, were, of course also described.

since those involved saw the greatest need for clarification in classic data exchange scenarios and wanted to test the extent to which they could rely on the systems and converters already in use at their companies to implement the defined use cases, a pragmatic approach was selected for the first benchmark.

this document provides you with the results of the first prostep ivip/vda jt translator benchmark.

language: en format: pdf (98 pages)

2. JT Benchmark - Long Report

142 start benchmark jtbenchmark mitglied 21 12 2010 jt en 2. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

in order to achieve an independent evaluation of the progress being made with regard to the development of jt translators, a jt translator benchmark was carried out for the second time in 2010. the benchmark was managed by the jt workflow forum and jt implementor forum. the aim was to create a neutral comparison of currently available jt translators with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also improvement to the interoperability of the translators.

the quality of jt export and import were tested. different combinations of translators and cad systems were used by way of example. the information to be transferred and the requirements were defined by users in the prostep ivip / vda jt workflow forum. the vendors participating in the benchmark verified the test cases proposed by the users. they were also responsible for making available the translator settings to be used for their respective tools. in 2010, focus was placed on benchmarking the ability to transfer the following elements:

geometry (solids)

product structure

pmi annotations

material data (the cad systems’ material feature)

tessellation (predefined lods)

user-defined attributes

jt translators from ct coretechnologie, siemens plm, t-systems and theorem solutions were tested. catia v5 r19 from dassault systèmes, nx 6 from siemens plm and pro/e wildfire 4 from parametric technology were used as the sending and receiving systems.

the results of this second prostep ivip / vda jt translator benchmark are presented in this document.

sprache: en format: pdf (43 seiten)

---

2. JT Benchmark - Long Report

142 start benchmark jtbenchmark mitglied 21 12 2010 jt en 2. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

in order to achieve an independent evaluation of the progress being made with regard to the development of jt translators, a jt translator benchmark was carried out for the second time in 2010. the benchmark was managed by the jt workflow forum and jt implementor forum. the aim was to create a neutral comparison of currently available jt translators with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also improvement to the interoperability of the translators.

the quality of jt export and import were tested. different combinations of translators and cad systems were used by way of example. the information to be transferred and the requirements were defined by users in the prostep ivip / vda jt workflow forum. the vendors participating in the benchmark verified the test cases proposed by the users. they were also responsible for making available the translator settings to be used for their respective tools. in 2010, focus was placed on benchmarking the ability to transfer the following elements:

geometry (solids)

product structure

pmi annotations

material data (the cad systems’ material feature)

tessellation (predefined lods)

user-defined attributes

jt translators from ct coretechnologie, siemens plm, t-systems and theorem solutions were tested. catia v5 r19 from dassault systèmes, nx 6 from siemens plm and pro/e wildfire 4 from parametric technology were used as the sending and receiving systems.

the results of this second prostep ivip / vda jt translator benchmark are presented in this document.

language: en format: pdf (43 pages)

3. JT Benchmark - Long Report

140 start benchmark jtbenchmark mitglied 31 1 2013 jt en 3. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the 2012 jt application benchmark is a project of the prostep ivip association and the german association of the automotive industry (vda). aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them. for the first time, a prostep ivip/vda jt benchmark did not focus on translators only but also on viewing applications.

the source formats for the translation tests are catia v5 r19, nx 8 and wildfire 5. the test models are converted to jt with settings provided by the translator vendors. focus of the benchmark is on the quality of the tessellation and the translation of pmi.

regarding tessellation, it is checked whether the naming and number of lods match the settings. the angular values are checked and the chordal deviations measured. the simplification of lower lods and the translation of model colors are checked also.

regarding pmi, it is analyzed whether different types of pmi annotations can be translated to jt. the layout and organization of pmi is benchmarked. color, style, size, symbols, position and orientation of the annotations shall be kept. organization of pmi regards the links between annotations and geometry, between different annotations and the allocation of annotations to model views are also relevant test criteria.

basic viewing and analysis functionalities are benchmarked in the viewer tests. the performance of the involved viewers is also measured.

sprache: en format: pdf (53 seiten)

---

3. JT Benchmark - Long Report

140 start benchmark jtbenchmark mitglied 31 1 2013 jt en 3. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the 2012 jt application benchmark is a project of the prostep ivip association and the german association of the automotive industry (vda). aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them. for the first time, a prostep ivip/vda jt benchmark did not focus on translators only but also on viewing applications.

the source formats for the translation tests are catia v5 r19, nx 8 and wildfire 5. the test models are converted to jt with settings provided by the translator vendors. focus of the benchmark is on the quality of the tessellation and the translation of pmi.

regarding tessellation, it is checked whether the naming and number of lods match the settings. the angular values are checked and the chordal deviations measured. the simplification of lower lods and the translation of model colors are checked also.

regarding pmi, it is analyzed whether different types of pmi annotations can be translated to jt. the layout and organization of pmi is benchmarked. color, style, size, symbols, position and orientation of the annotations shall be kept. organization of pmi regards the links between annotations and geometry, between different annotations and the allocation of annotations to model views are also relevant test criteria.

basic viewing and analysis functionalities are benchmarked in the viewer tests. the performance of the involved viewers is also measured.

language: en format: pdf (53 pages)

4. JT Benchmark - Long Report

138 start benchmark jtbenchmark mitglied 10 1 2014 jt en 4. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the jt application benchmark is a project of the prostep ivip association and the german association of the automotive industry (vda). aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them.

this benchmark is composed of two independent building blocks: the jt-loop test where translators from jt to cad and from cad to jt were checked and the jt with step ap242 xml test.

the cad formats for the jt-loop test are catia v5 r19, creo 2.0, nx 8.5 and solidworks 2012. the test models are converted with settings provided by the translator vendors. focus of the benchmark is on the quality of the geometry, the translation of pmi and the translation of attributes.

regarding geometry, it is checked whether the xt-brep is correct transferred. it if checked if all geometric elements like curves, faces and points are present and correct.

regarding pmi, type and content is benchmarked. color, style, size, position and orientation of the annotations shall be kept.

in the jt with step ap242 xml test the focus is on the capability of the translators to write the product structure correct in the ap242 xml. in special, the assembly attributes are checked.

sprache: en format: pdf (88 seiten)

---

4. JT Benchmark - Long Report

138 start benchmark jtbenchmark mitglied 10 1 2014 jt en 4. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the jt application benchmark is a project of the prostep ivip association and the german association of the automotive industry (vda). aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them.

this benchmark is composed of two independent building blocks: the jt-loop test where translators from jt to cad and from cad to jt were checked and the jt with step ap242 xml test.

the cad formats for the jt-loop test are catia v5 r19, creo 2.0, nx 8.5 and solidworks 2012. the test models are converted with settings provided by the translator vendors. focus of the benchmark is on the quality of the geometry, the translation of pmi and the translation of attributes.

regarding geometry, it is checked whether the xt-brep is correct transferred. it if checked if all geometric elements like curves, faces and points are present and correct.

regarding pmi, type and content is benchmarked. color, style, size, position and orientation of the annotations shall be kept.

in the jt with step ap242 xml test the focus is on the capability of the translators to write the product structure correct in the ap242 xml. in special, the assembly attributes are checked.

language: en format: pdf (88 pages)

5. JT Benchmark - Long Report

136 start benchmark jtbenchmark mitglied 13 2 2015 jt en 5. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the jt application benchmark is a prostep ivip association and german association of the automotive industry (vda) project. aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them.

this benchmark is composed of two independent building blocks: the “jt check tool” benchmark where check tools were tested and the “jt with step ap242 xml” benchmark.

within the jt check tool benchmark the validation and verification of jt files were carried out with check tools. for this purpose known bugs were introduced into the test models. in the validation tests the compliance of source files to translated jt files was examined. for instance the exact geometry within cad and jt were compared to each other, the completeness of pmi translation was checked as well as the completeness of attributes. in the verification tests, quality checks within the jt files were performed. thus introduced errors like removed edges or missing faces should have been identified by the involved check tools. regarding pmi, the check tool should have identified the missing pmi, the changed style (font and color) and the changed position of a pmi.

in the jt with step ap242 xml benchmark the focus lied on the capability of the translators to convert the product structure correctly into the step ap242 xml. in a second step, the written step ap242 xml files should have been properly read by translators and target applications. in special, the product structure and assembly attributes were checked.

sprache: en format: pdf (38 seiten)

---

5. JT Benchmark - Long Report

136 start benchmark jtbenchmark mitglied 13 2 2015 jt en 5. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the jt application benchmark is a prostep ivip association and german association of the automotive industry (vda) project. aim of the benchmark is to give a neutral overview of currently available jt application’s capabilities and improve interoperability between them.

this benchmark is composed of two independent building blocks: the “jt check tool” benchmark where check tools were tested and the “jt with step ap242 xml” benchmark.

within the jt check tool benchmark the validation and verification of jt files were carried out with check tools. for this purpose known bugs were introduced into the test models. in the validation tests the compliance of source files to translated jt files was examined. for instance the exact geometry within cad and jt were compared to each other, the completeness of pmi translation was checked as well as the completeness of attributes. in the verification tests, quality checks within the jt files were performed. thus introduced errors like removed edges or missing faces should have been identified by the involved check tools. regarding pmi, the check tool should have identified the missing pmi, the changed style (font and color) and the changed position of a pmi.

in the jt with step ap242 xml benchmark the focus lied on the capability of the translators to convert the product structure correctly into the step ap242 xml. in a second step, the written step ap242 xml files should have been properly read by translators and target applications. in special, the product structure and assembly attributes were checked.

language: en format: pdf (38 pages)

6. JT Benchmark - Long Report

134 start benchmark jtbenchmark mitglied 15 3 2016 jt en 6. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the jt application benchmark is a prostep ivip association and german association of the automotive industry (vda) project. aim of the benchmark is to give a neutral overview of capabilities from currently available jt applications and improve interoperability between them.

this benchmark is composed of two independent building blocks: the “cad-jt-cad” benchmark where cad to jt and jt to cad translators were tested and the “jt with step ap242 bom xml” benchmark, where jt applications with step ap242 xml capabilities were tested.

the focus of the cad-jt-cad benchmark was on the correct translation of geometry, tessellated data, pmi and metadata from cad to jt and in a second step from jt back to cad.

the jt with step ap242 xml benchmark focused on the capability of the translators to convert the product structure correctly into the step ap242 xml format. in a second step, the written step ap242 xml files should have been properly read by translators and target applications. particularly the product structure and assembly attributes were checked.

sprache: en format: pdf (45 seiten)

---

6. JT Benchmark - Long Report

134 start benchmark jtbenchmark mitglied 15 3 2016 jt en 6. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the jt application benchmark is a prostep ivip association and german association of the automotive industry (vda) project. aim of the benchmark is to give a neutral overview of capabilities from currently available jt applications and improve interoperability between them.

this benchmark is composed of two independent building blocks: the “cad-jt-cad” benchmark where cad to jt and jt to cad translators were tested and the “jt with step ap242 bom xml” benchmark, where jt applications with step ap242 xml capabilities were tested.

the focus of the cad-jt-cad benchmark was on the correct translation of geometry, tessellated data, pmi and metadata from cad to jt and in a second step from jt back to cad.

the jt with step ap242 xml benchmark focused on the capability of the translators to convert the product structure correctly into the step ap242 xml format. in a second step, the written step ap242 xml files should have been properly read by translators and target applications. particularly the product structure and assembly attributes were checked.

language: en format: pdf (45 pages)

7. JT Benchmark - Long Report

132 start benchmark jtbenchmark mitglied 20 3 2017 jt en 7. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt application benchmark is a project of prostep ivip association and german association of the automotive industry (vda). aim of the benchmark is the fair capability assessment and improvement of interoperability between currently available jt applications.

it is composed of two independent building blocks: a translation quality benchmark, where interoperability effectiveness of jt translators is examined from cad to jt and jt to cad as well as a performance benchmark, where handling efficiency of jt translators and viewing applications is benchmarked.

the focus in translation quality is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one hand, and from jt and step ap242 xml back to cad on the other.

the performance benchmark measures the time elapsing for converting complex single part models from cad to jt. it also investigates the efficiency of jt viewing applications on startup, loading, and viewing large and complex assembly files.

sprache: en format: pdf (40 seiten)

---

7. JT Benchmark - Long Report

132 start benchmark jtbenchmark mitglied 20 3 2017 jt en 7. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt application benchmark is a project of prostep ivip association and german association of the automotive industry (vda). aim of the benchmark is the fair capability assessment and improvement of interoperability between currently available jt applications.

it is composed of two independent building blocks: a translation quality benchmark, where interoperability effectiveness of jt translators is examined from cad to jt and jt to cad as well as a performance benchmark, where handling efficiency of jt translators and viewing applications is benchmarked.

the focus in translation quality is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one hand, and from jt and step ap242 xml back to cad on the other.

the performance benchmark measures the time elapsing for converting complex single part models from cad to jt. it also investigates the efficiency of jt viewing applications on startup, loading, and viewing large and complex assembly files.

language: en format: pdf (40 pages)

8. JT Benchmark - Long Report

130 start benchmark jtbenchmark mitglied 28 2 2019 jt en 8. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). aim of the benchmark is the fair capability as-sessment and improvement of interoperability between currently available jt applications.

it is composed of two building blocks: a translation quality benchmark, where interoperability effectiveness of jt translators is examined from cad to jt and jt to cad as well as a viewer benchmark, where the abilities of viewers in reading and displaying the generated files are tested.

the focus in translation quality is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one side, and from jt and step ap242 xml back to cad on the other. also, the transfer of graphical pmi annotations is exam-ined.

the viewer tests focus on the abilities of the viewer to load the generated jt and step ap242 xml models and display geometry, product structure, metadata and pmi annotations.

sprache: en format: pdf (55 seiten)

---

8. JT Benchmark - Long Report

130 start benchmark jtbenchmark mitglied 28 2 2019 jt en 8. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). aim of the benchmark is the fair capability as-sessment and improvement of interoperability between currently available jt applications.

it is composed of two building blocks: a translation quality benchmark, where interoperability effectiveness of jt translators is examined from cad to jt and jt to cad as well as a viewer benchmark, where the abilities of viewers in reading and displaying the generated files are tested.

the focus in translation quality is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one side, and from jt and step ap242 xml back to cad on the other. also, the transfer of graphical pmi annotations is exam-ined.

the viewer tests focus on the abilities of the viewer to load the generated jt and step ap242 xml models and display geometry, product structure, metadata and pmi annotations.

language: en format: pdf (55 pages)

9. JT Benchmark - Long Report

184 start benchmark jtbenchmark mitglied 10 2023 jt en 9. jt benchmark - long report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). aim of the benchmark is the fair capability assessment and improvement of interoperability between currently available jt applications.

it is composed of two building blocks: a test case focused on jt geometry with the optional extensions semantic product & manufacturing information (pmi) and validation properties, and a test case b concentrating on the combination of ap242 xml assembly structure with jt geometry with the optional extensions kinematic mechanism and validation properties.

the objective in both test cases is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one side, and from jt and step ap242 xml back to cad on the other.

consuming applications are also tested, with the focus on the abilities of the application to load the generated jt and step ap242 xml models and display geometry, product structure, metadata, and pmi annotations.

sprache: en format: pdf (96 seiten)

---

9. JT Benchmark - Long Report

184 start benchmark jtbenchmark mitglied 10 2023 jt en 9. jt benchmark - long report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). aim of the benchmark is the fair capability assessment and improvement of interoperability between currently available jt applications.

it is composed of two building blocks: a test case focused on jt geometry with the optional extensions semantic product & manufacturing information (pmi) and validation properties, and a test case b concentrating on the combination of ap242 xml assembly structure with jt geometry with the optional extensions kinematic mechanism and validation properties.

the objective in both test cases is the correct data exchange of geometry, product structure and metadata from cad to jt and step ap242 xml on the one side, and from jt and step ap242 xml back to cad on the other.

consuming applications are also tested, with the focus on the abilities of the application to load the generated jt and step ap242 xml models and display geometry, product structure, metadata, and pmi annotations.

language: en format: pdf (96 pages)

1. JT Benchmark - Short Report

143 benchmark jtbenchmark alle 2 2010 jt en 1. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

the publication of the jt specification as an iso publicly available specification (pas 14306) has laid the foundation for giving consideration to jt when designing efficient plm processes.

the challenges this entails are many. it is up to the users and the responsible management at the companies in question to decide which of the options that jt offers is to be used for which use case. how well jt then actually supports the individual process steps will depend first and foremost on the quality of the data generated.

in order to achieve a greater degree of clarity here, the prostep ivip association and the arbeitskreis plm of the german association of the automotive industry (vda) have joined forces and conducted a systematic benchmark.

the test criteria for the benchmark were derived from use cases defined by representatives of leading oems and suppliers from the automotive and aerospace industries in the prostep ivip / vda jt workflow forum. in addition to the core topics related to the application of jt – visualization and the use of jt in downstream processes – data exchange processes, were, of course also described.

since those involved saw the greatest need for clarification in classic data exchange scenarios and wanted to test the extent to which they could rely on the systems and translators already in use at their companies to implement the defined use cases, a pragmatic approach was selected for this first benchmark. this document will provide you with a summary of the results of the first prostep ivip / vda jt translator benchmark.

sprache: en format: pdf (10 seiten)

---

1. JT Benchmark - Short Report

143 benchmark jtbenchmark alle 2 2010 jt en 1. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

the publication of the jt specification as an iso publicly available specification (pas 14306) has laid the foundation for giving consideration to jt when designing efficient plm processes.

the challenges this entails are many. it is up to the users and the responsible management at the companies in question to decide which of the options that jt offers is to be used for which use case. how well jt then actually supports the individual process steps will depend first and foremost on the quality of the data generated.

in order to achieve a greater degree of clarity here, the prostep ivip association and the arbeitskreis plm of the german association of the automotive industry (vda) have joined forces and conducted a systematic benchmark.

the test criteria for the benchmark were derived from use cases defined by representatives of leading oems and suppliers from the automotive and aerospace industries in the prostep ivip / vda jt workflow forum. in addition to the core topics related to the application of jt – visualization and the use of jt in downstream processes – data exchange processes, were, of course also described.

since those involved saw the greatest need for clarification in classic data exchange scenarios and wanted to test the extent to which they could rely on the systems and translators already in use at their companies to implement the defined use cases, a pragmatic approach was selected for this first benchmark. this document will provide you with a summary of the results of the first prostep ivip / vda jt translator benchmark.

language: en format: pdf (10 pages)

2. JT Benchmark - Short Report

141 benchmark jtbenchmark alle 2 2011 jt en 2. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

publication of the jt specification 8.1c as an iso publicly available specification (pas 14306) has laid the foundation for establishing jt as a mandatory process format. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip/vda jt workflow forum, the prostep ivip/vda jt translator benchmark and the prostep ivip/vda jt implementor forum. furthermore, the prostep ivip association and siemens plm are working hand in hand toward standardizing jt with the iso. in august, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. on 26.11.10, the iso announced that the specification had been accepted for standardization. this means that the first and most important hurdle on the way to establishing jt as an iso standard has been taken. the objective is to bring the specification of jt as an iso standard to a successful close by the end of 2011.

the second jt translator benchmark was carried out in 2010 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of the testing was jt 8.1c (iso pas). the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark involved an independent activity, it was financed directly by the two organizations the prostep ivip association and the vda and not by the participating companies whose products were being tested. the aim was to create a neutral comparison of currently available jt translators with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also improvement to the interoperability of the translators.

sprache: en format: pdf (11 seiten)

---

2. JT Benchmark - Short Report

141 benchmark jtbenchmark alle 2 2011 jt en 2. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

publication of the jt specification 8.1c as an iso publicly available specification (pas 14306) has laid the foundation for establishing jt as a mandatory process format. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip/vda jt workflow forum, the prostep ivip/vda jt translator benchmark and the prostep ivip/vda jt implementor forum. furthermore, the prostep ivip association and siemens plm are working hand in hand toward standardizing jt with the iso. in august, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. on 26.11.10, the iso announced that the specification had been accepted for standardization. this means that the first and most important hurdle on the way to establishing jt as an iso standard has been taken. the objective is to bring the specification of jt as an iso standard to a successful close by the end of 2011.

the second jt translator benchmark was carried out in 2010 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of the testing was jt 8.1c (iso pas). the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark involved an independent activity, it was financed directly by the two organizations the prostep ivip association and the vda and not by the participating companies whose products were being tested. the aim was to create a neutral comparison of currently available jt translators with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also improvement to the interoperability of the translators.

language: en format: pdf (11 pages)

3. JT Benchmark - Short Report

139 benchmark jtbenchmark alle 31 1 2013 jt en 3. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip/vda jt application benchmark and the prostep ivip/vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the international standardization organization (iso) for standardization. 14 december 2012 jt 9.5 was published as iso standard iso 14306:2012.

as the latest in a row of three benchmarks, the jt application benchmark was carried out in 2012 to achieve an independent evaluation of the progress being made with regard to the development of jt translators and viewing applications. for the first time, the focus is not only on the translators, but also on viewing applications. the object of the testing was jt 9.5 (iso 14306:2012). the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark involved an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were being tested. the aim was to create a neutral comparison of currently available jt applications with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

additionally, the interoperability between jt and the step ap 242 xml scheme was tested by the vendors organized in the jt implementor forum. step ap 242 is still under development, but the intention was to gather first feedbacks. thus, first results of these tests are also published within this documentation.

sprache: en format: pdf (11 seiten)

---

3. JT Benchmark - Short Report

139 benchmark jtbenchmark alle 31 1 2013 jt en 3. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip/vda jt application benchmark and the prostep ivip/vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the international standardization organization (iso) for standardization. 14 december 2012 jt 9.5 was published as iso standard iso 14306:2012.

as the latest in a row of three benchmarks, the jt application benchmark was carried out in 2012 to achieve an independent evaluation of the progress being made with regard to the development of jt translators and viewing applications. for the first time, the focus is not only on the translators, but also on viewing applications. the object of the testing was jt 9.5 (iso 14306:2012). the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark involved an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were being tested. the aim was to create a neutral comparison of currently available jt applications with regard to selected test criteria. this means that the results of the benchmark can not only be used to evaluate the application of jt in plm environments but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

additionally, the interoperability between jt and the step ap 242 xml scheme was tested by the vendors organized in the jt implementor forum. step ap 242 is still under development, but the intention was to gather first feedbacks. thus, first results of these tests are also published within this documentation.

language: en format: pdf (11 pages)

4. JT Benchmark - Short Report

137 benchmark jtbenchmark alle 2 2014 jt en 4. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip/vda jt workflow forum, the prostep ivip/vda jt application benchmark and the prostep ivip/vda jt implementor forum.

as the latest in a row of four benchmarks, the jt application benchmark was carried out in 2013 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of the testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 xml schema (publication as iso standard planned for q1/2014) was also part of the benchmark. thus, this 4th benchmark covers results far beyond state-of-the-art technology.


the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore the results of the benchmark cannot only be used to evaluate the application of jt in plm environments but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

sprache: en format: pdf (13 seiten)

---

4. JT Benchmark - Short Report

137 benchmark jtbenchmark alle 2 2014 jt en 4. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession which are being coordinated with each other: the prostep ivip/vda jt workflow forum, the prostep ivip/vda jt application benchmark and the prostep ivip/vda jt implementor forum.

as the latest in a row of four benchmarks, the jt application benchmark was carried out in 2013 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of the testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 xml schema (publication as iso standard planned for q1/2014) was also part of the benchmark. thus, this 4th benchmark covers results far beyond state-of-the-art technology.


the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore the results of the benchmark cannot only be used to evaluate the application of jt in plm environments but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

language: en format: pdf (13 pages)

5. JT Benchmark - Short Report

135 benchmark jtbenchmark alle 3 2015 jt en 5. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

as the latest in a row of five benchmarks, the jt application benchmark was carried out in 2014 to achieve an independent evaluation of the progress being made with regard to the development of jt check tools. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (publication as iso standard iso 10303-242:2014) was also part of the benchmark. thus, this 5th benchmark covers results far beyond state-of-the-art technology.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

sprache: en format: pdf (15 seiten)

---

5. JT Benchmark - Short Report

135 benchmark jtbenchmark alle 3 2015 jt en 5. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

as the latest in a row of five benchmarks, the jt application benchmark was carried out in 2014 to achieve an independent evaluation of the progress being made with regard to the development of jt check tools. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (publication as iso standard iso 10303-242:2014) was also part of the benchmark. thus, this 5th benchmark covers results far beyond state-of-the-art technology.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

language: en format: pdf (15 pages)

6. JT Benchmark - Short Report

133 benchmark jtbenchmark alle 3 2016 jt en 6. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

as the latest in a row of six benchmarks, the jt application benchmark was carried out in 2015 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark. thus, this 6th benchmark covers results far beyond state-of-the-art technology.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

sprache: en format: pdf (15 seiten)

---

6. JT Benchmark - Short Report

133 benchmark jtbenchmark alle 3 2016 jt en 6. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

as the latest in a row of six benchmarks, the jt application benchmark was carried out in 2015 to achieve an independent evaluation of the progress being made with regard to the development of jt translators. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark. thus, this 6th benchmark covers results far beyond state-of-the-art technology.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral comparison of trendsetting jt applications with regard to the selected test criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

language: en format: pdf (15 pages)

7. JT Benchmark - Short Report

131 benchmark jtbenchmark alle 2 2017 jt en 7. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

since then, prostep ivip and vda have developed implementation guidelines for jt and discussed issues and further requirements. this eventually led to the publishing of the jt industrial application package (psi 14), combining the guidelines and enhancements with the latest jt specification. this specification is compatible with the iso standard released in 2012 as well as with the latest proprietary versions of jt.

as the latest in a row of seven benchmarks, the jt application benchmark was carried out in 2016 to achieve an independent evaluation of the progress being made with regard to the development of jt translators and viewing applications. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral test of trendsetting jt applications with regard to the selected criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

sprache: en format: pdf (14 seiten)

---

7. JT Benchmark - Short Report

131 benchmark jtbenchmark alle 2 2017 jt en 7. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used format for product visualization during the product development process. the prostep ivip association and the german association of the automotive industry (vda) have launched three jt-related projects in succession, which are being coordinated with each other: the prostep ivip / vda jt workflow forum, the prostep ivip / vda jt application benchmark and the prostep ivip / vda jt implementor forum. in august 2010, the prostep ivip association submitted the latest jt specification (version 9.5) to the iso for standardization. jt 9.5 was published by iso as iso 14306:2012 in december, 2012.

since then, prostep ivip and vda have developed implementation guidelines for jt and discussed issues and further requirements. this eventually led to the publishing of the jt industrial application package (psi 14), combining the guidelines and enhancements with the latest jt specification. this specification is compatible with the iso standard released in 2012 as well as with the latest proprietary versions of jt.

as the latest in a row of seven benchmarks, the jt application benchmark was carried out in 2016 to achieve an independent evaluation of the progress being made with regard to the development of jt translators and viewing applications. the object of testing was iso 14306:2012 (jt 9.5). additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies whose products were tested. it is a neutral test of trendsetting jt applications with regard to the selected criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications.

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

language: en format: pdf (14 pages)

8. JT Benchmark - Short Report

129 benchmark jtbenchmark alle 2 2019 jt en 8. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used standard format for product visualization in the industry. the prostep ivip association and the german association of the automotive industry (vda) are driving this adoption with three connected projects focusing on both users and vendors communities with:

the prostep ivip / vda jt workflow forum,

the prostep ivip / vda jt implementor forum and

the prostep ivip / vda jt application benchmark.

from the start, these projects have continuously developed jt recommendations and implementation guidelines; performed benchmarks, documented requirements and discussed issues.

in august 2010, the prostep ivip association submitted a jt specification to iso for standardization. iso published it as iso 14306 international standard in december 2012.

in june 2016 prostep ivip released the «jt industrial application package» version 2 (psi 14/jt iap v2): an enhanced specification of jt, combining guidelines and latest use case requirements. this psi recommendation is compatible with the jt iso standard released in 2012 and provides latest capabilities of the file format. it was also released as din spec 91383 in 2018.

as the latest in a row of eight benchmarks, this jt application benchmark was carried out in 2018 to achieve an independent evaluation of the progress being made concerning the development of jt translators and viewing applications. the object of testing was the psi 14/din spec 91383 jt specification. additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies, whose products were tested. it is a neutral test of trendsetting jt applications against selected criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications. as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

sprache: en format: pdf (18 seiten)

---

8. JT Benchmark - Short Report

129 benchmark jtbenchmark alle 2 2019 jt en 8. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used standard format for product visualization in the industry. the prostep ivip association and the german association of the automotive industry (vda) are driving this adoption with three connected projects focusing on both users and vendors communities with:

the prostep ivip / vda jt workflow forum,

the prostep ivip / vda jt implementor forum and

the prostep ivip / vda jt application benchmark.

from the start, these projects have continuously developed jt recommendations and implementation guidelines; performed benchmarks, documented requirements and discussed issues.

in august 2010, the prostep ivip association submitted a jt specification to iso for standardization. iso published it as iso 14306 international standard in december 2012.

in june 2016 prostep ivip released the «jt industrial application package» version 2 (psi 14/jt iap v2): an enhanced specification of jt, combining guidelines and latest use case requirements. this psi recommendation is compatible with the jt iso standard released in 2012 and provides latest capabilities of the file format. it was also released as din spec 91383 in 2018.

as the latest in a row of eight benchmarks, this jt application benchmark was carried out in 2018 to achieve an independent evaluation of the progress being made concerning the development of jt translators and viewing applications. the object of testing was the psi 14/din spec 91383 jt specification. additionally, the interoperability between jt and the step ap242 business object (bo) model xml schema (published as iso standard iso 10303-242:2014) was also part of the benchmark.

the benchmark was managed by the jt workflow forum and jt implementor forum. because the benchmark is an independent activity, it was financed directly by the two organizations, the prostep ivip association and the vda, and not by the participating companies, whose products were tested. it is a neutral test of trendsetting jt applications against selected criteria. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications. as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications.

language: en format: pdf (18 pages)

9. JT Benchmark - Short Report

183 start benchmark jtbenchmark alle 10 2023 jt en 9. jt benchmark - short report der jt application benchmark ist ein projekt des prostep ivip vereins (psi) und des verbandes der automobilindustrie (vda). das ziel des benchmarks ist es, die interoperabilität zwischen den derzeit verfügbaren jt-anwendungen auf eine faire und objektive weise zu bewerten und zu verbessern.

jt has become a widely used standard format for product visualization in the industry. the prostep ivip association and german association of the automotive industry (vda) are driving this adoption with three connected projects focusing on both users and vendors communities: 

• the prostep ivip / vda jt workflow forum, 
• the prostep ivip / vda jt implementor forum and 
• the prostep ivip / vda application benchmark. 

from the start, these projects have continuously developed jt recommendations and implementation guidelines; performed benchmarks, documented requirements and discussed issues. 

in august 2010, the prostep ivip association submitted a jt specification to iso for standardization. iso published it as iso 14306:2012 international standard in december 2012. 

in june 2021 prostep ivip association released the “jt industrial application package” version 3 (psi 14/part 1 v3): an enhanced specification of jt, combining guidelines and latest use case requirements. this prostep ivip recommendation is compatible with the jt iso standard released in 2012 and provides latest capabilities of the file format. it was also released as din spec 91383 in 2021. 

as the latest in a row of nine benchmarks, this jt application benchmark was carried out in 2022 and 2023 to achieve an independent evaluation of the progress being made concerning the development of jt translators and viewing applications. the object of testing was the din spec 91383 jt specification. additionally, the interoperability between jt and the step ap242 edition 3 domain model xml schema (published as iso standard iso 10303-242:2022) was also part of the benchmark. in particular, the aim of the benchmark was to carry out a neutral comparison of current jt applications with a focus on proving the maturity of jt and ap242 xml applications concerning jt geometry and semantic pmi, validation properties, assembly structure, and kinematic mechanism. 

the benchmark was managed by the jt workflow forum and jt implementor forum. it is an independent activity, financed directly by the prostep ivip association and vda, and by the participating companies, whose products were tested. it is a neutral test of trendsetting jt applications against selected criteria, carried out by a neutral service provider. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications. 

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications. 

sprache: en format: pdf (35 seiten)

---

9. JT Benchmark - Short Report

183 start benchmark jtbenchmark alle 10 2023 jt en 9. jt benchmark - short report the jt application benchmark is a project of the prostep ivip association (psi) and the german association of the automotive industry (vda). the goal of the benchmark is to evaluate and enhance the interoperability between currently available jt applications in a fair and objective way.

jt has become a widely used standard format for product visualization in the industry. the prostep ivip association and german association of the automotive industry (vda) are driving this adoption with three connected projects focusing on both users and vendors communities: 

• the prostep ivip / vda jt workflow forum, 
• the prostep ivip / vda jt implementor forum and 
• the prostep ivip / vda application benchmark. 

from the start, these projects have continuously developed jt recommendations and implementation guidelines; performed benchmarks, documented requirements and discussed issues. 

in august 2010, the prostep ivip association submitted a jt specification to iso for standardization. iso published it as iso 14306:2012 international standard in december 2012. 

in june 2021 prostep ivip association released the “jt industrial application package” version 3 (psi 14/part 1 v3): an enhanced specification of jt, combining guidelines and latest use case requirements. this prostep ivip recommendation is compatible with the jt iso standard released in 2012 and provides latest capabilities of the file format. it was also released as din spec 91383 in 2021. 

as the latest in a row of nine benchmarks, this jt application benchmark was carried out in 2022 and 2023 to achieve an independent evaluation of the progress being made concerning the development of jt translators and viewing applications. the object of testing was the din spec 91383 jt specification. additionally, the interoperability between jt and the step ap242 edition 3 domain model xml schema (published as iso standard iso 10303-242:2022) was also part of the benchmark. in particular, the aim of the benchmark was to carry out a neutral comparison of current jt applications with a focus on proving the maturity of jt and ap242 xml applications concerning jt geometry and semantic pmi, validation properties, assembly structure, and kinematic mechanism. 

the benchmark was managed by the jt workflow forum and jt implementor forum. it is an independent activity, financed directly by the prostep ivip association and vda, and by the participating companies, whose products were tested. it is a neutral test of trendsetting jt applications against selected criteria, carried out by a neutral service provider. therefore, the results of the benchmark cannot only be used to evaluate the application of jt in plm environments, but also for improvement of the interoperability of the applications. 

as such applications are undergoing a permanent development; the benchmark can only give a snapshot of the functions and qualities of the applications. 

language: en format: pdf (35 pages)

JT Content Harmonization Guideline

105 start guideline alle jt en 2024 11 30 jt content harmonization guideline harmonization proposal for jt and step ap242 xml

in the year 2009, the prostep ivip association had launched jt-activities in close cooperation with the vda (german association of the automotive industry). within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. based on these use cases, jt-translator benchmarks were initiated to investigate the quality of converted jt-data.

for optimized process support, two action points were identified:

p #1: so far, investigations were limited to the jt-format. however, not all requirements must address jt. for selective use cases, some of the necessary process supporting content (satisfying respective requirements), e.g. the product structure and according master data, can be provided by further formats in combination with jt. there is a need to analyze which contents are to be stored in jt and which contents are to be stored in accompanying formats (e.g. step ap242 xml). if jt and the accompanying format both provide containers for required content, there must be a unique understanding on which of the formats is responsible for the data. this is a prerequisite to application interoperability, in turn a prerequisite to the mentioned optimization of process support.

p #2: further, there is a need to harmonize the form, in which the above-mentioned content is to be provided. in order to classify (jt or accompanying format) and harmonize content, it is first necessary to have a common understanding on the meaning of requirements, as both go hand in hand. in general, it can be said that contents satisfy requirements. in some cases, requirements are detailed enough to be actually synonymous to the content. in others, the necessary content describes a closer look into the requirement, hence detailing it. in either case, there then exist different forms to store the required contents.

for a prioritized subset of the jt workflow forum requirements, this document provides a proposal for the harmonization of contents.

language: en format: pdf (48 pages)

---

JT Content Harmonization Guideline

105 start guideline alle jt en 2024 11 30 jt content harmonization guideline harmonization proposal for jt and step ap242 xml

in the year 2009, the prostep ivip association had launched jt-activities in close cooperation with the vda (german association of the automotive industry). within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. based on these use cases, jt-translator benchmarks were initiated to investigate the quality of converted jt-data.

for optimized process support, two action points were identified:

p #1: so far, investigations were limited to the jt-format. however, not all requirements must address jt. for selective use cases, some of the necessary process supporting content (satisfying respective requirements), e.g. the product structure and according master data, can be provided by further formats in combination with jt. there is a need to analyze which contents are to be stored in jt and which contents are to be stored in accompanying formats (e.g. step ap242 xml). if jt and the accompanying format both provide containers for required content, there must be a unique understanding on which of the formats is responsible for the data. this is a prerequisite to application interoperability, in turn a prerequisite to the mentioned optimization of process support.

p #2: further, there is a need to harmonize the form, in which the above-mentioned content is to be provided. in order to classify (jt or accompanying format) and harmonize content, it is first necessary to have a common understanding on the meaning of requirements, as both go hand in hand. in general, it can be said that contents satisfy requirements. in some cases, requirements are detailed enough to be actually synonymous to the content. in others, the necessary content describes a closer look into the requirement, hence detailing it. in either case, there then exist different forms to store the required contents.

for a prioritized subset of the jt workflow forum requirements, this document provides a proposal for the harmonization of contents.

sprache: en format: pdf (48 seiten)

JT Content Harmonization Guideline – Harmonization Proposal for JT and STEP AP242 XML

182 guideline implementationguidelines alle 27 6 2023 en jt content harmonization guideline – harmonization proposal for jt and step ap242 xml harmonization proposal for jt and step ap242 xml

in the year 2009, the prostep ivip association launched jt-activities in close cooperation with the vda (german association of the automotive industry). within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. based on these use cases, jt-translator benchmarks were initiated to investigate the quality of converted jt-data.

for optimized process support, two action points were identified:

• p #1: so far, investigations were limited to the jt-format. however, not all requirements must address jt. for selective use cases, some of the necessary process supporting content (satisfying respective requirements), e.g. the product structure and according master data, can be provided by further formats in combination with jt. there is a need to analyze which contents are to be stored in jt and which contents are to be stored in accompanying formats (e.g. step ap242 xml). if jt and the accompanying format both provide containers for required content, there must be a unique understanding on which of the formats is responsible for the data. this is a prerequisite to application interoperability, in turn a prerequisite to the mentioned optimization of process support.
• p #2: further, there is a need to harmonize the form, in which the above-mentioned content is to be provided.

in order to classify (jt or accompanying format) and harmonize content, it is first necessary to have a common understanding on the meaning of requirements, as both go hand in hand. in general, it can be said that contents satisfy requirements. in some cases, requirements are detailed enough to be actually synonymous to the content (see figure 1). in others, the necessary content describes a closer look into the requirement, hence detailing it. in either case, there then exist different forms to store the required contents.

for a prioritized subset of the jt workflow forum requirements, this document provides a proposal for the harmonization of contents.

language: en format: pdf (46 pages)

---

JT Content Harmonization Guideline – Harmonization Proposal for JT and STEP AP242 XML

182 guideline implementationguidelines alle 27 6 2023 en jt content harmonization guideline – harmonization proposal for jt and step ap242 xml harmonization proposal for jt and step ap242 xml

in the year 2009, the prostep ivip association launched jt-activities in close cooperation with the vda (german association of the automotive industry). within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. based on these use cases, jt-translator benchmarks were initiated to investigate the quality of converted jt-data.

for optimized process support, two action points were identified:

• p #1: so far, investigations were limited to the jt-format. however, not all requirements must address jt. for selective use cases, some of the necessary process supporting content (satisfying respective requirements), e.g. the product structure and according master data, can be provided by further formats in combination with jt. there is a need to analyze which contents are to be stored in jt and which contents are to be stored in accompanying formats (e.g. step ap242 xml). if jt and the accompanying format both provide containers for required content, there must be a unique understanding on which of the formats is responsible for the data. this is a prerequisite to application interoperability, in turn a prerequisite to the mentioned optimization of process support.
• p #2: further, there is a need to harmonize the form, in which the above-mentioned content is to be provided.

in order to classify (jt or accompanying format) and harmonize content, it is first necessary to have a common understanding on the meaning of requirements, as both go hand in hand. in general, it can be said that contents satisfy requirements. in some cases, requirements are detailed enough to be actually synonymous to the content (see figure 1). in others, the necessary content describes a closer look into the requirement, hence detailing it. in either case, there then exist different forms to store the required contents.

for a prioritized subset of the jt workflow forum requirements, this document provides a proposal for the harmonization of contents.

sprache: en format: pdf (46 seiten)

JT-IF Implementation Guidelines

111 start guideline implementationguidelines alle 20 12 2018 jt en jt-if implementation guidelines the implementation guidelines and recommendations provided in this document are aimed to close the gap between the jt specification (jt din spec and iso 14306) and “real world” implementation tasks. they are also aimed towards vendors with the objective to provide recommendations how to best implement certain aspects of the jt standards, by itself or in combination with accompanying formats such as step ap242 xml. the recommendations given in this document have been discussed intensively, and agreed on, by the jt implementor forum members and will be implemented by them as a means of enhancing interoperability of application using the jt format.

the implementation guidelines and recommendations provided in this document are aimed to close the gap between the jt specification (jt din spec and iso 14306) and “real world” implementation tasks. they are also aimed towards vendors with the objective to provide recommendations how to best implement certain aspects of the jt standards, by itself or in combination with accompanying formats such as step ap242 xml. the recommendations given in this document have been discussed intensively, and agreed on, by the jt implementor forum members and will be implemented by them as a means of enhancing interoperability of application using the jt format.

this document understands itself as a complement to the following documents:

• the jt file format specification (currently: iso 14306:2017; 2017-11), which defines the data model and file format itself.
• the jt din spec 91383:2018-09, jt industrial application package (jtiap), which defines the syntax and semantics of the jt file format and is compatible to the jt file format specification in iso 14306 (in its version from 2012 and successors) as well as to the essential implementations currently available to the market.
• the jt content harmonization guideline (currently: version 2.1; 2012-12-07), which gives recommendations about property names (keys), property values, and configuration settings to be applied by users.

consequently, the jt implementation guideline stands between the two documents listed above, as it gives additional information on the implementation of the jt file format specification where the group feels the given information is not sufficient, or ambiguous. it is aimed towards the implement_x0002_ers of jt translators and documents agreements on a technical level. the jt content harmonization guideline, on the other hand, is aimed towards users and documents agreements on the levels of process and content. the issues mentioned here were raised by one of the following bodies:

• during the iso ballot
• prostep ivip / vda jt workflow forum
• prostep ivip / vda jt implementor forum

language: en format: pdf (88 pages)

---

JT-IF Implementation Guidelines

111 start guideline implementationguidelines alle 20 12 2018 jt en jt-if implementation guidelines the implementation guidelines and recommendations provided in this document are aimed to close the gap between the jt specification (jt din spec and iso 14306) and “real world” implementation tasks. they are also aimed towards vendors with the objective to provide recommendations how to best implement certain aspects of the jt standards, by itself or in combination with accompanying formats such as step ap242 xml. the recommendations given in this document have been discussed intensively, and agreed on, by the jt implementor forum members and will be implemented by them as a means of enhancing interoperability of application using the jt format.

the implementation guidelines and recommendations provided in this document are aimed to close the gap between the jt specification (jt din spec and iso 14306) and “real world” implementation tasks. they are also aimed towards vendors with the objective to provide recommendations how to best implement certain aspects of the jt standards, by itself or in combination with accompanying formats such as step ap242 xml. the recommendations given in this document have been discussed intensively, and agreed on, by the jt implementor forum members and will be implemented by them as a means of enhancing interoperability of application using the jt format.

this document understands itself as a complement to the following documents:

• the jt file format specification (currently: iso 14306:2017; 2017-11), which defines the data model and file format itself.
• the jt din spec 91383:2018-09, jt industrial application package (jtiap), which defines the syntax and semantics of the jt file format and is compatible to the jt file format specification in iso 14306 (in its version from 2012 and successors) as well as to the essential implementations currently available to the market.
• the jt content harmonization guideline (currently: version 2.1; 2012-12-07), which gives recommendations about property names (keys), property values, and configuration settings to be applied by users.

consequently, the jt implementation guideline stands between the two documents listed above, as it gives additional information on the implementation of the jt file format specification where the group feels the given information is not sufficient, or ambiguous. it is aimed towards the implement_x0002_ers of jt translators and documents agreements on a technical level. the jt content harmonization guideline, on the other hand, is aimed towards users and documents agreements on the levels of process and content. the issues mentioned here were raised by one of the following bodies:

• during the iso ballot
• prostep ivip / vda jt workflow forum
• prostep ivip / vda jt implementor forum

sprache: en format: pdf (88 seiten)

Implementation Guideline JT Validation Properties

108 start guideline implementationguidelines alle jt en 2023 12 12 implementation guideline jt validation properties implementation guideline for jt validation properties this document specifies implementation guidelines for the exchange of validation properties with jt. it makes use of existing default properties as well as newly introduced properties to capture certain key aspects of the model that allow for validating the success of the data transfer after importing the jt file into a target application. language: en format: pdf (21 pages)

---

Implementation Guideline JT Validation Properties

108 start guideline implementationguidelines alle jt en 2023 12 12 implementation guideline jt validation properties implementation guideline for jt validation properties this document specifies implementation guidelines for the exchange of validation properties with jt. it makes use of existing default properties as well as newly introduced properties to capture certain key aspects of the model that allow for validating the success of the data transfer after importing the jt file into a target application. sprache: en format: pdf (21 seiten)

3D Visualization in MBSE

9 standards guideline alle 1 2020 jt en 3d visualization in mbse mbse 3d foundation - die aktuelle und zukünftige rolle von 3d-visualisierung im mbse

products and systems are getting more complex over the last years due to a trend to interconnected products, which are often realized as systems of systems (sos), and further influences like the rising globalization and more stringent regulations. new development approaches emerged to handle this complexity and to allow the realization of such complex systems. one of these approaches is systems engineering (se), where a system is developed from the beginning in a holistic approach to consider all influences and interfaces. the model-based systems engineering (mbse) uses models to describe the system in its requirements, architecture, behavior and many more aspects. this allows a single-source-of-truth-approach, dynamic usage of the constantly updated information stored in the system model as well as a better understanding, communication and collaboration inside of the project.

jupiter tessellation (jt) is the international standard for 3d visualization. it is an open standard format and thus independent from the used computer aided design (cad) system in use. together with step ap242 xml it is used to share information about components in respect to geometry (jt file) as well as technological aspects (ap242 xml). it allows an easier communication between project members over domains.

as mbse and jt both support the collaboration and communication, it is obvious to look at both to find synergies and general benefits. the current recommendation shall deliver the following:

an overview of the capabilities and elements of jt and mbse

current use cases of jt in mbse

possible use cases for further combination of jt and mbse

recommendations for the further research and development of jt in mbse

sprache: en format: pdf (24 seiten)

---

3D Visualization in MBSE

9 standards guideline alle 1 2020 jt en 3d visualization in mbse mbse 3d foundation - the current and future role of 3d visualization in mbse

products and systems are getting more complex over the last years due to a trend to interconnected products, which are often realized as systems of systems (sos), and further influences like the rising globalization and more stringent regulations. new development approaches emerged to handle this complexity and to allow the realization of such complex systems. one of these approaches is systems engineering (se), where a system is developed from the beginning in a holistic approach to consider all influences and interfaces. the model-based systems engineering (mbse) uses models to describe the system in its requirements, architecture, behavior and many more aspects. this allows a single-source-of-truth-approach, dynamic usage of the constantly updated information stored in the system model as well as a better understanding, communication and collaboration inside of the project.

jupiter tessellation (jt) is the international standard for 3d visualization. it is an open standard format and thus independent from the used computer aided design (cad) system in use. together with step ap242 xml it is used to share information about components in respect to geometry (jt file) as well as technological aspects (ap242 xml). it allows an easier communication between project members over domains.

as mbse and jt both support the collaboration and communication, it is obvious to look at both to find synergies and general benefits. the current recommendation shall deliver the following:

an overview of the capabilities and elements of jt and mbse

current use cases of jt in mbse

possible use cases for further combination of jt and mbse

recommendations for the further research and development of jt in mbse

language: en format: pdf (24 pages)

JT Communication Paper

63 start executive-summaries mitglied 21 4 2015 jt en jt communication paper management-summary language: en format: pdf (7 pages)

---

JT Communication Paper

63 start executive-summaries mitglied 21 4 2015 jt en jt communication paper management-summary sprache: en format: pdf (7 seiten)

Fields of JT Application

167 start use-case mitglied 4 2009 jt en fields of jt application 30 use cases of potential areas of jt application

the jt data format enables the creation and utilization of high-performance 3d models for all life stages of the product lifecycle. the compressible data format contains a cad-neutral description of product data and acts as a key factor in the integration of multiple cad and pdm systems. this recommendation gives an overview about jt, the lightweight format for 3d data. after a short introduction a look in the brief history is given. within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. these are presented in this document.

language: en format: zip file

---

Fields of JT Application

167 start use-case mitglied 4 2009 jt en fields of jt application 30 use cases of potential areas of jt application

the jt data format enables the creation and utilization of high-performance 3d models for all life stages of the product lifecycle. the compressible data format contains a cad-neutral description of product data and acts as a key factor in the integration of multiple cad and pdm systems. this recommendation gives an overview about jt, the lightweight format for 3d data. after a short introduction a look in the brief history is given. within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. these are presented in this document.

sprache: en format: zip-datei

White Paper JT Digital Master

75 start white-paper recommendations&standards alle 7 2018 jt en white paper jt digital master white paper jt digital master

this white paper gives a definition of the digital master approach and an overview of the jt format. it shows how jt can be used in a digital master process chain according to recommendation of prostep ivip. practical experience and benefits gained from current digital master implementations using jt as backbone are described. possible developments for the jt format and the digital master approach are discussed.

language: en format: pdf (10 pages)

---

White Paper JT Digital Master

75 start white-paper recommendations&standards alle 7 2018 jt en white paper jt digital master white paper jt digital master

this white paper gives a definition of the digital master approach and an overview of the jt format. it shows how jt can be used in a digital master process chain according to recommendation of prostep ivip. practical experience and benefits gained from current digital master implementations using jt as backbone are described. possible developments for the jt format and the digital master approach are discussed.

sprache: en format: pdf (10 seiten)

White Paper JT VAR

76 start white-paper recommendations&standards alle 7 2018 jt en white paper jt var jt - virtual augmented reality

this white paper gives a brief description of the different technologies used in virtual and augmented reality today. furthermore, use cases are described in which these technologies are used. the white paper also describes which formats are established in the field of virtual and augmented reality and shows how jt fits in.

language: en format: pdf (15 pages)

---

White Paper JT VAR

76 start white-paper recommendations&standards alle 7 2018 jt en white paper jt var jt - virtual augmented reality

this white paper gives a brief description of the different technologies used in virtual and augmented reality today. furthermore, use cases are described in which these technologies are used. the white paper also describes which formats are established in the field of virtual and augmented reality and shows how jt fits in.

sprache: en format: pdf (15 seiten)

193 start alle en de 2023 12 12 implementationguidelines jt-if implementation guidelines for pmi in jt the jt implementor forum was set up in 2010 and is a joint project organized by the prostep ivip association and the german association of the automotive industry (vda). the aim of the project group is to provide the participating vendors with a platform where they can test the translators that they are developing “behind closed doors”.  pdf 12 pages

---

193 start alle en de 2023 12 12 implementationguidelines jt-if implementation guidelines for pmi in jt jt-if implementation guidelines for pmi in jt the jt implementor forum was set up in 2010 and is a joint project organized by the prostep ivip association and the german association of the automotive industry (vda). the aim of the project group is to provide the participating vendors with a platform where they can test the translators that they are developing “behind closed doors”.  pdf 12 seiten

Analyse KBL Dialekte - Harmonisierung der KBL & VEC Dialekte

78 start white-paper alle 14 11 2016 ves de analyse kbl dialekte - harmonisierung der kbl & vec dialekte im mai 2016 wurde auf initiative der oems eine untergruppe des ecad-if zur konsolidierung der dateiformate gebildet. aufgabe dieser untergruppe war es, die unterschiedlichen dialekte herauszuarbeiten, zu klassifizieren und handlungsfelder zu identifizieren. die erarbeitung von lösungen, wie die dialekte beseitigt werden können, war nicht auftrag der projektgruppe. über die ableitung entsprechender maßnahmen (update der spezifikation, bereitstellung von tutorials oder empfehlung von work-arounds) wird die prostep ivip / vda projektgruppe pdm4ves entscheiden. lösungswege werden bereits in diesem dokument aufgezeigt.

die kbl (kabelbaumliste) ist heute unverzichtbarer teil des elektronischen datenaustausches in der automobilindustrie und wird mittelfristig durch den nachfolger vec (vehicle electric container) abgelöst. bei der nutzung der kbl haben sich dialekte herausgebildet. im mai 2016 wurde auf initiative der oems eine untergruppe des ecad-if zur konsolidierung der dateiformate gebildet. aufgabe dieser untergruppe war es, die unterschiedlichen dialekte herauszuarbeiten, zu klassifizieren und handlungsfelder zu identifizieren. die erarbeitung von lösungen, wie die dialekte beseitigt werden können, war nicht auftrag der projektgruppe. über die ableitung entsprechender maßnahmen (update der spezifikation, bereitstellung von tutorials oder empfehlung von work-arounds) wird die prostep ivip / vda projektgruppe pdm4ves entscheiden. lösungswege werden bereits in diesem dokument aufgezeigt.

dieses dokument bildet den abschlussbericht der unterarbeitsgruppe. die ergebnisse werden von der prostep ivip / vda projektgruppe pdm4ves aufgegriffen.

language: de format: zip file

---

Analyse KBL Dialekte - Harmonisierung der KBL & VEC Dialekte

78 start white-paper alle 14 11 2016 ves de analyse kbl dialekte - harmonisierung der kbl & vec dialekte im mai 2016 wurde auf initiative der oems eine untergruppe des ecad-if zur konsolidierung der dateiformate gebildet. aufgabe dieser untergruppe war es, die unterschiedlichen dialekte herauszuarbeiten, zu klassifizieren und handlungsfelder zu identifizieren. die erarbeitung von lösungen, wie die dialekte beseitigt werden können, war nicht auftrag der projektgruppe. über die ableitung entsprechender maßnahmen (update der spezifikation, bereitstellung von tutorials oder empfehlung von work-arounds) wird die prostep ivip / vda projektgruppe pdm4ves entscheiden. lösungswege werden bereits in diesem dokument aufgezeigt.

die kbl (kabelbaumliste) ist heute unverzichtbarer teil des elektronischen datenaustausches in der automobilindustrie und wird mittelfristig durch den nachfolger vec (vehicle electric container) abgelöst. bei der nutzung der kbl haben sich dialekte herausgebildet. im mai 2016 wurde auf initiative der oems eine untergruppe des ecad-if zur konsolidierung der dateiformate gebildet. aufgabe dieser untergruppe war es, die unterschiedlichen dialekte herauszuarbeiten, zu klassifizieren und handlungsfelder zu identifizieren. die erarbeitung von lösungen, wie die dialekte beseitigt werden können, war nicht auftrag der projektgruppe. über die ableitung entsprechender maßnahmen (update der spezifikation, bereitstellung von tutorials oder empfehlung von work-arounds) wird die prostep ivip / vda projektgruppe pdm4ves entscheiden. lösungswege werden bereits in diesem dokument aufgezeigt.

dieses dokument bildet den abschlussbericht der unterarbeitsgruppe. die ergebnisse werden von der prostep ivip / vda projektgruppe pdm4ves aufgegriffen.

sprache: de format: zip-datei

OMG PLM Services 2.0

25 standards omg alle 8 2009 en omg plm services 2.0 omg plm services 2.0 - final adopted specification für den austausch von plm-daten via web services

this specification defines a platform independent model (pim) for product lifecycle management services v2.0. its
informational model is derived from the iso 10303-214 step model by an express-x mapping specification and an
express-to-xmi mapping process. the functional model is derived from the omg pdm enablers v1.3 and to fulfill
requirements of the rfp.

the specification defines a platform specific model (psm) applicable to the web services implementation defined by a
wsdl specification, with a soap binding, and an xml schema specification.

language: en format: zip file

---

OMG PLM Services 2.0

25 standards omg alle 8 2009 en omg plm services 2.0 omg plm services 2.0 - final adopted specification für den austausch von plm-daten via web services

this specification defines a platform independent model (pim) for product lifecycle management services v2.0. its
informational model is derived from the iso 10303-214 step model by an express-x mapping specification and an
express-to-xmi mapping process. the functional model is derived from the omg pdm enablers v1.3 and to fulfill
requirements of the rfp.

the specification defines a platform specific model (psm) applicable to the web services implementation defined by a
wsdl specification, with a soap binding, and an xml schema specification.

sprache: en format: zip-datei

ReqIF

24 standards omg alle 7 2016 reqif en reqif omg reqif - final adopted specification of the requirements interchange format

requirements management has been an integral part of the development process in various industries (especially in the military, aeronautical, or the medical device industry) for years. other industries have been adopting requirements management recently.

this document is created to inform:

• persons interested in exchanging requirements data between organizations that do not have a possibility to share the same repository (see clause 4 for a definition of “repository”).
• requirements authoring tool vendors who want to support the requirements interchange format (reqif) with export and import interfaces for their requirements authoring tools. see clause 4 for a definition of “requirements authoring tool.”
• tool vendors other than requirements authoring tool vendors who wish to interchange requirements for documentation or other purposes.
• anyone interested in defining, interchanging, storing, etc., requirements in a standard interchange format.

language: en format: pdf (104 pages)

---

ReqIF

24 standards omg alle 7 2016 reqif en reqif omg reqif - final adopted specification of the requirements interchange format

requirements management has been an integral part of the development process in various industries (especially in the military, aeronautical, or the medical device industry) for years. other industries have been adopting requirements management recently.

this document is created to inform:

• persons interested in exchanging requirements data between organizations that do not have a possibility to share the same repository (see clause 4 for a definition of “repository”).
• requirements authoring tool vendors who want to support the requirements interchange format (reqif) with export and import interfaces for their requirements authoring tools. see clause 4 for a definition of “requirements authoring tool.”
• tool vendors other than requirements authoring tool vendors who wish to interchange requirements for documentation or other purposes.
• anyone interested in defining, interchanging, storing, etc., requirements in a standard interchange format.

sprache: en format: pdf (104 seiten)

6. Benchmark (Part II: PDM) 2001

160 start benchmark stepbenchmark mitglied 01 3 2001 step en 6. benchmark (part ii: pdm) 2001 benchmark - ausführlicher bericht zum 6. benchmark (pdm)

the exchange of cad model data using the neutral data exchange format according to the iso 10303 standard [iso], usually known as the step standard (standard for the exchange of product model data), has become popular in the last years. step processing is commonly supported by the major available cad systems and the appropriate step processors have been tested and evaluated in previous prostep benchmarks [xav99a], [xav99b]. recently not only the exchange of cad model data, but also the exchange of cad model meta data and general product data has become more and more interesting, especially within the automotive industry.

although the pdm data exchange is still in the beginning, some of the major commercially available pdm systems have integrated step processors to support the automotive manufacturers’ requirements of pdm data exchange within the cooperative engineering processes between the automotive manufacturers, suppliers and engineering service providers. the pdm step processor benchmark, as a part of the sixth prostep benchmark performed by the prostep association, gives a survey of the performance and the quality of these step processors with regard to the requirements of the pdm data exchange with the automotive manufacturers’ inhouse systems (target systems). the test procedure considers the import of delivered step files (post-processing) and the export of changed pdm data as a step files to be re-sent to the target system (pre-processing).

the participating commercial pdm systems are

cadim/edb (eigner + partner ag): 2.3#4

cim database (contact software gmbh): 2.7.3, processor 25.10.2000 (availability)

enoviavpm (dassault syst `emes): vpm 1.3 - ptf 3

sap plm module automotive (sap ag): version 2.0 (di4.6ci), processor 1.00.05 (released)

the target systems (test cases) are

prisma (bmw group ag)

gis (daimlerchrysler ag)

smaragd (daimlerchrysler ag)

kvs (volkswagen ag)

sprache: en format: pdf (69 seiten)

---

6. Benchmark (Part II: PDM) 2001

160 start benchmark stepbenchmark mitglied 01 3 2001 step en 6. benchmark (part ii: pdm) 2001 benchmark - detailed report to the 6th benchmark (pdm)

the exchange of cad model data using the neutral data exchange format according to the iso 10303 standard [iso], usually known as the step standard (standard for the exchange of product model data), has become popular in the last years. step processing is commonly supported by the major available cad systems and the appropriate step processors have been tested and evaluated in previous prostep benchmarks [xav99a], [xav99b]. recently not only the exchange of cad model data, but also the exchange of cad model meta data and general product data has become more and more interesting, especially within the automotive industry.

although the pdm data exchange is still in the beginning, some of the major commercially available pdm systems have integrated step processors to support the automotive manufacturers’ requirements of pdm data exchange within the cooperative engineering processes between the automotive manufacturers, suppliers and engineering service providers. the pdm step processor benchmark, as a part of the sixth prostep benchmark performed by the prostep association, gives a survey of the performance and the quality of these step processors with regard to the requirements of the pdm data exchange with the automotive manufacturers’ inhouse systems (target systems). the test procedure considers the import of delivered step files (post-processing) and the export of changed pdm data as a step files to be re-sent to the target system (pre-processing).

the participating commercial pdm systems are

cadim/edb (eigner + partner ag): 2.3#4

cim database (contact software gmbh): 2.7.3, processor 25.10.2000 (availability)

enoviavpm (dassault syst `emes): vpm 1.3 - ptf 3

sap plm module automotive (sap ag): version 2.0 (di4.6ci), processor 1.00.05 (released)

the target systems (test cases) are

prisma (bmw group ag)

gis (daimlerchrysler ag)

smaragd (daimlerchrysler ag)

kvs (volkswagen ag)

language: en format: pdf (69 pages)

6. Benchmark (Part II: PDM) 2001 - Short Report

159 benchmark stepbenchmark alle 4 2001 step en 6. benchmark (part ii: pdm) 2001 - short report step, benchmark - comparative test of stepprocessor language: en format: pdf (7 pages)

---

6. Benchmark (Part II: PDM) 2001 - Short Report

159 benchmark stepbenchmark alle 4 2001 step en 6. benchmark (part ii: pdm) 2001 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (7 seiten)

Usage Guide for the STEP PDM Schema

126 guideline usageguideline alle 23 1 2002 en usage guide for the step pdm schema iso 10303, step, pdm data exchange - usage guide for the application of the step pdm schema

the step pdm (product data management) schema is a reference information model for the exchange of a central, common subset of the data being managed within a pdm system. it represents the intersection of requirements and data structures from a range of step application protocols, all generally within the domains of design and development of discrete electro/mechanical parts and assemblies.

the step pdm schema is not a specification for the functionality required for the complete scope of all pdm system functionality – i.e., it is not the union, but the intersection, of functionality present in the set of step application protocols. there exists functionality important for complete pdm functionality that is not represented in the pdm schema, but is in other units of functionality present in step aps.

by definition, a pdm system is something that manages data about products. at the central core of pdm information is product identification. a product in step represents the concept of a general managed item within a pdm system. in the step pdm schema, the general product concept may be interpreted as either a part (see section 1) or a document (see section 5). in this way, parts and documents are managed in a consistent and parallel fashion. section 12 describes a mechanism to associate product data with an additional identifier (alias).

also central to the functionality of many pdm systems is identification of external files (both digital and physical), their relationship to managed documents (see section 8), and how they can be associated with core product identification (see section 10). the external file reference mechanism in the step pdm schema is described in section 7 of this document.

classification of products is important in a pdm system for information classification and retrieval. it also supports basic type distinction between products that are parts and those that are documents. in the pdm schema, product classification is used consistently for parts (see section 2) and documents (see section 6).

product properties are integrally related to the definition of an identified product, and so are naturally also included in the central core pdm information. sections 3 and 9 discuss properties associated with an identified product, interpreted, respectively, as either a part or a document.

various general authorization and organizational data that are related to core product identification play an important role in pdm systems. section 13 of this document describes the various organizational and management constructs that support product authorization in the step pdm schema.

product structures are the principle relationships that define assemblies and product configurations. section 4 details part structures in the step pdm schema; section 11 describes document structures. configuration identification and effectivity information related to these structures is detailed in section 14.

section 15 describes structures to manage the documentation of requests and corresponding orders for engineering action in support of the change management process. also included are representations for contract and project identification.

finally, section 16 summarizes recommendations related to measures and units.

language: en format: pdf (271 pages)

---

Usage Guide for the STEP PDM Schema

126 guideline usageguideline alle 23 1 2002 en usage guide for the step pdm schema iso 10303, step, pdm data exchange - usage guide for the application of the step pdm schema

the step pdm (product data management) schema is a reference information model for the exchange of a central, common subset of the data being managed within a pdm system. it represents the intersection of requirements and data structures from a range of step application protocols, all generally within the domains of design and development of discrete electro/mechanical parts and assemblies.

the step pdm schema is not a specification for the functionality required for the complete scope of all pdm system functionality – i.e., it is not the union, but the intersection, of functionality present in the set of step application protocols. there exists functionality important for complete pdm functionality that is not represented in the pdm schema, but is in other units of functionality present in step aps.

by definition, a pdm system is something that manages data about products. at the central core of pdm information is product identification. a product in step represents the concept of a general managed item within a pdm system. in the step pdm schema, the general product concept may be interpreted as either a part (see section 1) or a document (see section 5). in this way, parts and documents are managed in a consistent and parallel fashion. section 12 describes a mechanism to associate product data with an additional identifier (alias).

also central to the functionality of many pdm systems is identification of external files (both digital and physical), their relationship to managed documents (see section 8), and how they can be associated with core product identification (see section 10). the external file reference mechanism in the step pdm schema is described in section 7 of this document.

classification of products is important in a pdm system for information classification and retrieval. it also supports basic type distinction between products that are parts and those that are documents. in the pdm schema, product classification is used consistently for parts (see section 2) and documents (see section 6).

product properties are integrally related to the definition of an identified product, and so are naturally also included in the central core pdm information. sections 3 and 9 discuss properties associated with an identified product, interpreted, respectively, as either a part or a document.

various general authorization and organizational data that are related to core product identification play an important role in pdm systems. section 13 of this document describes the various organizational and management constructs that support product authorization in the step pdm schema.

product structures are the principle relationships that define assemblies and product configurations. section 4 details part structures in the step pdm schema; section 11 describes document structures. configuration identification and effectivity information related to these structures is detailed in section 14.

section 15 describes structures to manage the documentation of requests and corresponding orders for engineering action in support of the change management process. also included are representations for contract and project identification.

finally, section 16 summarizes recommendations related to measures and units.

sprache: en format: pdf (271 seiten)

PDTnet Project - Product Data Technology and Communication in an OEM and Supplier Network

171 use-case alle 3 2003 step en pdtnet project - product data technology and communication in an oem and supplier network pdtnet project, pdm data exchange - flyer for project conclusion, project description, methods, results language: en format: pdf (2 pages)

---

PDTnet Project - Product Data Technology and Communication in an OEM and Supplier Network

171 use-case alle 3 2003 step en pdtnet project - product data technology and communication in an oem and supplier network pdtnet project, pdm data exchange - flyer for project conclusion, project description, methods, results sprache: en format: pdf (2 seiten)

PDTnet Project - Application Scenario 1 "PDM Data Exchange"

170 use-case alle 3 2003 step en pdtnet project - application scenario 1 "pdm data exchange" pdtnet project, pdm data exchange - flyer for scenario 1, product data exchange between partners with different pdm systems language: en format: pdf (2 pages)

---

PDTnet Project - Application Scenario 1 "PDM Data Exchange"

170 use-case alle 3 2003 step en pdtnet project - application scenario 1 "pdm data exchange" pdtnet project, pdm data exchange - flyer for scenario 1, product data exchange between partners with different pdm systems sprache: en format: pdf (2 seiten)

PDTnet Project - Appl,ication Scenario 2 "PDM Web Integration"

169 use-case alle 3 2003 step en pdtnet project - appl,ication scenario 2 "pdm web integration" pdtnet project, pdm data exchange - flyer for scenario 2, access to the pdm system of development partners via the internet based on standardized protocols, synchronous and asynchronous data exchange language: en format: pdf (2 pages)

---

PDTnet Project - Appl,ication Scenario 2 "PDM Web Integration"

169 use-case alle 3 2003 step en pdtnet project - appl,ication scenario 2 "pdm web integration" pdtnet project, pdm data exchange - flyer for scenario 2, access to the pdm system of development partners via the internet based on standardized protocols, synchronous and asynchronous data exchange sprache: en format: pdf (2 seiten)

PDTnet Implementation Guideline

124 guideline implementationguidelines alle nan 2003 pdtnet en pdtnet implementation guideline pdtnet project, pdm data exchange - description of the implementation concept and the entities of the pdtnet schema language: en format: zip file

---

PDTnet Implementation Guideline

124 guideline implementationguidelines alle nan 2003 pdtnet en pdtnet implementation guideline pdtnet project, pdm data exchange - description of the implementation concept and the entities of the pdtnet schema sprache: en format: zip-datei

PDTnet Usage Guide

123 guideline usageguideline alle 6 2003 pdtnet en pdtnet usage guide pdtnet project, pdm data exchange - description of the pdtnet objects in their application for mapping of pdm data on the pdtnet schema language: en format: pdf (27 pages)

---

PDTnet Usage Guide

123 guideline usageguideline alle 6 2003 pdtnet en pdtnet usage guide pdtnet project, pdm data exchange - description of the pdtnet objects in their application for mapping of pdm data on the pdtnet schema sprache: en format: pdf (27 seiten)

Implementation Guideline PLM Services 2.0

121 start guideline implementationguidelines mitglied 11 3 2008 en implementation guideline plm services 2.0 implementation guideline concerning omg plm services 2.0

this document is the result of the prostep ivip project groups plm services and pdm implementor forum (pdm-if). both groups are industrial consortia aiming to specify, standardize, and implement the omg plm services. for further information please refer to the web-sites of the prostep ivip association (www.prostep.org).

this document is dedicated to users and vendors aiming to implement the omg plm services 2.0. thus, it contains a general overview, application scenarios, use case descriptions, and a detailed description on how the reference implementation was implemented (available for download at www.prostep.org).

language: en format: pdf (116 pages)

---

Implementation Guideline PLM Services 2.0

121 start guideline implementationguidelines mitglied 11 3 2008 en implementation guideline plm services 2.0 implementation guideline concerning omg plm services 2.0

this document is the result of the prostep ivip project groups plm services and pdm implementor forum (pdm-if). both groups are industrial consortia aiming to specify, standardize, and implement the omg plm services. for further information please refer to the web-sites of the prostep ivip association (www.prostep.org).

this document is dedicated to users and vendors aiming to implement the omg plm services 2.0. thus, it contains a general overview, application scenarios, use case descriptions, and a detailed description on how the reference implementation was implemented (available for download at www.prostep.org).

sprache: en format: pdf (116 seiten)

prEN 9300 - LOTAR Long Term Archiving and Retrieval (Item to Search: 9300)

26 standards asd-stan alle 12 2006 en pren 9300 - lotar long term archiving and retrieval (item to search: 9300) long-term archiving of product data within the aerospace industry (part 001, 004, 010 - 015)

aerospace series - lotar long term archiving and retrieval of digital technical product documentation such as 3d, cad and pdm data

• part 001: structure
• part 004: description methods
• part 010: overview data flow
• part 015: reference process description ''removal''

language: en format: url redirection

---

prEN 9300 - LOTAR Long Term Archiving and Retrieval (Item to Search: 9300)

26 standards asd-stan alle 12 2006 en pren 9300 - lotar long term archiving and retrieval (item to search: 9300) long-term archiving of product data within the aerospace industry (part 001, 004, 010 - 015)

aerospace series - lotar long term archiving and retrieval of digital technical product documentation such as 3d, cad and pdm data

• part 001: structure
• part 004: description methods
• part 010: overview data flow
• part 015: reference process description ''removal''

sprache: en format: url weiterleitung

prostep ivip AI-survey
Results & Follow-up

194 start en de 2023 12 12 mitglied prostep ivip prostep ivip ai-survey
results & follow-up review of survey results
50 participants
conducted july-september 2023 pdf 28 pages

---

prostep ivip AI-survey
Results & Follow-up

194 start en de 2023 12 12 mitglied prostep ivip prostep ivip ai-survey
results & follow-up prostep ivip ai-survey
results & follow-up review of survey results
50 participants
conducted july-september 2023 pdf 28 seiten

prostep ivip PSI 14-2 Recommendation V3.0

28 start jt 7 2024 prostep ivip alle de en prostep ivip psi 14-2 recommendation v3.0
jt recommendation -comprehensive collection of industrial jt use cases sprache: de format: pdf (66 seiten) prostep ivip psi 14-2 recommendation v3.0

---

prostep ivip PSI 14-2 Recommendation V3.0
 

28 start jt 7 2024 prostep ivip alle de en prostep ivip psi 14-2 recommendation v3.0
  prostep ivip psi 14-2 recommendation v3.0
jt recommendation -comprehensive collection of industrial jt use cases language: en format: pdf (66 pages)

prostep ivip SmartSE Recommendation 2022 PSI 11

682 start en alle prostep ivip 2022 sprache: en format: pdf (4 seiten)

---

prostep ivip SmartSE Recommendation 2022 PSI 11

682 start en alle prostep ivip 2022

driven by the increasing complexity of products, collaborative development networks, new technologies and legal requirements, systems engineering is nowadays one of the standard methodologies for product development. reduced hardware testing and shortening of development times require a significant boost in digital product development. with the advancing digital transformation, verification and validation with simulations are getting more and more important.

 

language: en format: pdf (4 pages)

697 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

 

 

pdf 132 seiten prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

---

prostep ivip SmartSE Recommendation 2025 PSI 11 Smart Systems Engineering - Collaborative Simulation-Based Engineering Version 4.0

 

697 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

 

prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

 

prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

 

pdf 132 pages prostep ivip smartse recommendation 2025 psi 11 smart systems engineering - collaborative simulation-based engineering version 4.0

698 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

 

 

pdf 10 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part A – Detailed Use-Case Description

698 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

 

pdf 10 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part a – detailed use-case description

699 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

 

pdf 13 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part B – Boundary Model Standardization

699 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

 

pdf 13 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part b – boundary model standardization

700 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

 

pdf 38 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part C – SmartSE Reference Process

700 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

 

pdf 38 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part c – smartse reference process

701 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection pdf 37 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part D – IP Protection

701 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection

 

pdf 37 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part d – ip protection

702 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide pdf 16 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part E – FMI Best-Practice Guide

702 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide

 

pdf 16 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part e – fmi best-practice guide

703 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

 

pdf 14 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part F – Virtual Electronic Control Units

703 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

 

pdf 14 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part f – virtual electronic control units

704 start alle en de 2025 5 smartse 6 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

 

pdf 11 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part G – SSP

704 start alle en de 2025 5 smartse 6

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

 

pdf 11 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part g – ssp

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part H – Credible Simulation Process Framework
with detailed process description

705 start alle en de 2025 smartse 7 16

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

 

pdf 99 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part H – Credible Simulation Process Framework
with detailed process description

705 start alle en de 2025 smartse 7 16 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

 

pdf 99 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part h – credible simulation process framework
with detailed process description

706 prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

 

pdf 17 seiten prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

---

prostep ivip SmartSE Recommendation 2025 PSI 11 V 4.0 - Part I – SE Data Management for Simulation Model Exchange

706

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

 

pdf 17 pages prostep ivip smartse recommendation 2025 psi 11 v 4.0 - part i – se data management for simulation model exchange

Relevance of Engineering IT Standards for Collaboration and Future PLM Architectures

696 start alle en de white-paper 2025 prostep ivip 5 1

relevance of engineering it standards for collaboration and future plm architectures

relevance of engineering it standards for collaboration and future plm architectures

in 2024, the prostep ivip association invited its members to take part in a survey. on the one hand, the aim was to discover how members assess the impact of success factors on collaboration in data spaces and the impact of it trends on future plm architectures. it was also hoped that the results of the survey would provide information about the motivations and obstacles influencing participation in prostep ivip project groups. in addition, the prostep ivip association wanted to find out how its members rated the market penetration and benefits of a large number of engineering it standards.
this white paper presents the results of the survey.
 

 

pdf 19 pages relevance of engineering it standards for collaboration and future plm architectures

---

Relevance of Engineering IT Standards for Collaboration and Future PLM Architectures

696 start alle en de white-paper 2025 prostep ivip 5 1 relevance of engineering it standards for collaboration and future plm architectures

in 2024, the prostep ivip association invited its members to take part in a survey. on the one hand, the aim was to discover how members assess the impact of success factors on collaboration in data spaces and the impact of it trends on future plm architectures. it was also hoped that the results of the survey would provide information about the motivations and obstacles influencing participation in prostep ivip project groups. in addition, the prostep ivip association wanted to find out how its members rated the market penetration and benefits of a large number of engineering it standards.
this white paper presents the results of the survey.
 

 

pdf 19 seiten relevance of engineering it standards for collaboration and future plm architectures

PSI 1-2: Collaborative Project Management (CPM)

50 standards prostepivip alle 2 2010 psms en psi 1-2: collaborative project management (cpm) part 2: data exchange model

collaborative project management helps implement project management that extends across the borders of individual corporate enterprises. the tools and processes that can be used to achieve this objective, the reason why collaborative project management is necessary, and the benefits to be gained from the cpm recommendation are described in detail in part 1 of this recommendation (reference model; psi 1-1).

the cpm usage guide provides information on using the tools presented in part 1.

part 2 of the cpm recommendation (data exchange model; psi 1-2) defines the data objects that can be used to exchange project management information relating to cpm between different pm systems. this includes the tools defined in psi 1-1 in particular. the associated transmission mechanisms are also described.

in addition to this second part of the recommendation, note should also be made of the implementation guide, which contains recommendations and explanations regarding implementation of the described data model within the context of cpm. all documents are available at www.prostep.org.

language: en format: pdf (86 pages)

---

PSI 1-2: Collaborative Project Management (CPM)

50 standards prostepivip alle 2 2010 psms en psi 1-2: collaborative project management (cpm) teil 2: data exchange model

collaborative project management helps implement project management that extends across the borders of individual corporate enterprises. the tools and processes that can be used to achieve this objective, the reason why collaborative project management is necessary, and the benefits to be gained from the cpm recommendation are described in detail in part 1 of this recommendation (reference model; psi 1-1).

the cpm usage guide provides information on using the tools presented in part 1.

part 2 of the cpm recommendation (data exchange model; psi 1-2) defines the data objects that can be used to exchange project management information relating to cpm between different pm systems. this includes the tools defined in psi 1-1 in particular. the associated transmission mechanisms are also described.

in addition to this second part of the recommendation, note should also be made of the implementation guide, which contains recommendations and explanations regarding implementation of the described data model within the context of cpm. all documents are available at www.prostep.org.

sprache: en format: pdf (86 seiten)

PSI 1-1: Collaborative Project Management (CPM)

51 standards prostepivip alle 2 2010 psms en psi 1-1: collaborative project management (cpm) part 1: reference model

this recommendation focuses on project management (pm) across companies. the document describes the project management tasks within the product development process (pdp) in the automotive industry that extend across the borders of partner enterprises, and focuses1 on time management, activity management and communication management. it covers the processes, roles, methods, information, language and culture in collaboration projects. the recommendation explicitly excludes project management within the enterprises involved. the recommendation is published in two parts. part 1 contains the reference model and part 2 contains the data model for exchanging project data.

language: en format: pdf (78 pages)

---

PSI 1-1: Collaborative Project Management (CPM)

51 standards prostepivip alle 2 2010 psms en psi 1-1: collaborative project management (cpm) teil 1: reference model

this recommendation focuses on project management (pm) across companies. the document describes the project management tasks within the product development process (pdp) in the automotive industry that extend across the borders of partner enterprises, and focuses1 on time management, activity management and communication management. it covers the processes, roles, methods, information, language and culture in collaboration projects. the recommendation explicitly excludes project management within the enterprises involved. the recommendation is published in two parts. part 1 contains the reference model and part 2 contains the data model for exchanging project data.

sprache: en format: pdf (78 seiten)

PSI 10 - PSM: Recommendation for schedule management

12 start standards guideline alle 8 2017 psms en de psi 10 - psm: recommendation for schedule management requirements relating to a schedule management tool for different industries - standardized criterion catalogue at detailed concept level

because the automotive industry and its suppliers constitute a strong and important sector within the german economy, countless projects are launched, conducted and successfully concluded in the country every year. alongside organizational, implementation, it and many other projects, a huge scope for multi-project activities has emerged in the product development sphere in particular. this is a sector which has for many years been growing increasingly professional, expanding and benefiting from increasing levels of tool-based support. this sustained trend has resulted in the development of a market in which tool suppliers interact with professional purchasers and tool users and are regularly in contact with them concerning the requirements placed on high-performance, forward-looking schedule management tools (sm tools). the aim of the present recommendation is to facilitate communications between the various parties and to create a common ground that will simplify the conduct of purposeful discussions. neither the experienced project management specialists in the automotive sector nor the consulting and it specialists employed by the tool suppliers should have to spend more time than necessary in the drafting of product specifications, lists of requirements or interface specifications. they should use this requirements standard as an aid in the design and detailed specification of customer-specific solutions as well as in the development of innovative systems.

language: en & de format: zip file

---

PSI 10 - PSM: Rekommendation für Terminmanagement

12 start standards guideline alle 8 2017 psms en de psi 10 - psm: rekommendation für terminmanagement anforderungen an ein terminplanungstool für verschiedene branchen - standardisierter kriterienkatalog auf detaillierter konzeptebene

da die automobilindustrie inkl. ihrer zulieferer ein bedeutender sektor, eine starke branche innerhalb der deutschen wirtschaft ist, werden hier jährlich unzählige projekte gestartet, durchgeführt und erfolgreich beendet. neben organisations-, implementierungs-, itund vielen weiteren projekten hat sich insbesondere eine enorme multiprojektlandschaft in der produktentwicklung herausgebildet. diese wird seit langem kontinuierlich professionalisiert, ergänzt und zunehmend toolgestützt ausgebaut. infolge dieses anhaltenden trends hat sich ein markt entwickelt, auf dem toolanbieter auf bedarfsträger und toolnutzer treffen und regelmäßig über anforderungen an ein leistungs- und zukunftsfähiges terminmanagement-tool (tm-tool) in kontakt stehen. zwischen diesen gesprächspartnern möchte vorliegende empfehlung vermitteln, aber primär eine gemeinsame basis schaffen, auf der aufwandsarm zielführend diskutiert werden kann. weder die erfahrenen projektmanagementspezialisten der automobilbranche, noch die consulting- und it-spezialisten auf seiten der toolanbieter sollen mehr als nötig zeit in das verfassen von lastenheften, anforderungskatalogen und schnittstellenspezifikationen investieren. sie sollten diesen anforderungsstandard nutzend kundenspezifische lösungen konzipieren, detaillieren und neue innovative lösungen entwickeln.

sprache: de & en format: zip-datei

PSI 12 - MCM

41 start standards prostep ivip alle 5 2015 en psi 12 - mcm management of changes during production

besides product development, production planning is arguably the most important process to take place within the creation of a product. however, the growing demands placed on production systems and their ongoing improvement pose ever new and difficult challenges to production planning. while there is a significant increase in changes within production planning and operations, there is at the same time an unwavering expectation for all the direct and indirect processes to retain their quality and efficiency, or even for these to improve. currently, many manufacturers lack comprehensive and seamless management for the change processes occurring between planning and the shop floor – particularly when it comes to cross-location, cross-disciplinary, and crossdepartmental planning and heterogeneous technical support of the planning processes. there simply are no sufficient organizational and technical solution concepts to provide for the comprehensive mapping and processing of changes between production planning and operations, to uniformly capture and track change measures, and to sensibly forecast and coordinate the capacities required for change processes in the planning and production departments.

the psi/vda recommendation at hand addresses this challenge. its manufacturing change management (mcm) defines a reference sequence of steps for managing the changes between planning and the shop floor. to define this reference process, the recommendation first discusses how mcm fits into the business environment and identifies the main participants of the change processes. next, the best possible structural steps involved in the processing of a change enquiry are detailed, and the typical tasks and their extents are described. leading on from the conceptual basis of the mcm process, its suitability for specific applications within companies is then discussed in reference to relevant use cases. next, the recommendation shows how to work out a softwarebased support structure for the concept and implemented as a prototype.

the key element of the software-based implementation is to map the changes within a superordinate change list – this significantly improves the transparency and coordination of a company’s change activities. this solution makes it possible for the first time to view the statuses of change requests and their planning versions, to match measures to each other, and to trigger follow-up changes based on production system characteristics. exactly how the software is deployed varies considerably depending on how its users are placed within their company. while an mcm coordinator, for example, requires a wide-ranging and complete overview of all the changes and how they are connected to the production system, an employee who processes the change enquiries needs specific predefined views in order to interact with the changes adequately. lastly, the solution provides an easy-to-use practical tool for initiating change enquiries. this can be deployed flexibly on mobile devices such as tablet pcs on the shop floor.

the participating companies will test and further develop the practical deployment of the described developments over a series of pilot projects. this will expose the main challenges to the concept’s implementation and demonstrate very accurately the opportunities presented by mcm.

language: en format: pdf (29 pages)

---

PSI 12 - MCM

41 start standards prostep ivip alle 5 2015 en psi 12 - mcm management of changes during production

besides product development, production planning is arguably the most important process to take place within the creation of a product. however, the growing demands placed on production systems and their ongoing improvement pose ever new and difficult challenges to production planning. while there is a significant increase in changes within production planning and operations, there is at the same time an unwavering expectation for all the direct and indirect processes to retain their quality and efficiency, or even for these to improve. currently, many manufacturers lack comprehensive and seamless management for the change processes occurring between planning and the shop floor – particularly when it comes to cross-location, cross-disciplinary, and crossdepartmental planning and heterogeneous technical support of the planning processes. there simply are no sufficient organizational and technical solution concepts to provide for the comprehensive mapping and processing of changes between production planning and operations, to uniformly capture and track change measures, and to sensibly forecast and coordinate the capacities required for change processes in the planning and production departments.

the psi/vda recommendation at hand addresses this challenge. its manufacturing change management (mcm) defines a reference sequence of steps for managing the changes between planning and the shop floor. to define this reference process, the recommendation first discusses how mcm fits into the business environment and identifies the main participants of the change processes. next, the best possible structural steps involved in the processing of a change enquiry are detailed, and the typical tasks and their extents are described. leading on from the conceptual basis of the mcm process, its suitability for specific applications within companies is then discussed in reference to relevant use cases. next, the recommendation shows how to work out a softwarebased support structure for the concept and implemented as a prototype.

the key element of the software-based implementation is to map the changes within a superordinate change list – this significantly improves the transparency and coordination of a company’s change activities. this solution makes it possible for the first time to view the statuses of change requests and their planning versions, to match measures to each other, and to trigger follow-up changes based on production system characteristics. exactly how the software is deployed varies considerably depending on how its users are placed within their company. while an mcm coordinator, for example, requires a wide-ranging and complete overview of all the changes and how they are connected to the production system, an employee who processes the change enquiries needs specific predefined views in order to interact with the changes adequately. lastly, the solution provides an easy-to-use practical tool for initiating change enquiries. this can be deployed flexibly on mobile devices such as tablet pcs on the shop floor.

the participating companies will test and further develop the practical deployment of the described developments over a series of pilot projects. this will expose the main challenges to the concept’s implementation and demonstrate very accurately the opportunities presented by mcm.

sprache: en format: pdf (29 seiten)

PSI 13 - OEM-OEM

38 start standards prostep ivip alle 1 2016 en psi 13 - oem-oem oem-oem and oem-joint venture collaboration

in the course of market globalization, the strategic collaboration between oems as well as between oems and jvs is becoming increasingly important.

against this background, these new forms of collaboration must be supported by effective system solutions, designed specifically for the underlying processes and work methods.

this recommendation contains a set of requirements based on best practice-scenarios of oem/oem as well as oem/jv collaboration. furthermore, this document provides an overview of the usual forms of cooperation in the pdm-context and is additionally intended for being a basis for the implementation of suitable system solutions.

even though this publication reflects the existing challenges for the automotive industry, these requirements are applicable in other areas of engineering industries as well.

from this point of view, the document represents a first compilation of scenarios and respective requirements with regard to collaboration in the specific case of oems-oems and oems-jvs.

however, further developments through scenarios of other industries are possible and also welcome.

language: en format: pdf (32 pages)

---

PSI 13 - OEM-OEM

38 start standards prostep ivip alle 1 2016 en psi 13 - oem-oem oem-oem and oem-joint venture collaboration

in the course of market globalization, the strategic collaboration between oems as well as between oems and jvs is becoming increasingly important.

against this background, these new forms of collaboration must be supported by effective system solutions, designed specifically for the underlying processes and work methods.

this recommendation contains a set of requirements based on best practice-scenarios of oem/oem as well as oem/jv collaboration. furthermore, this document provides an overview of the usual forms of cooperation in the pdm-context and is additionally intended for being a basis for the implementation of suitable system solutions.

even though this publication reflects the existing challenges for the automotive industry, these requirements are applicable in other areas of engineering industries as well.

from this point of view, the document represents a first compilation of scenarios and respective requirements with regard to collaboration in the specific case of oems-oems and oems-jvs.

however, further developments through scenarios of other industries are possible and also welcome.

sprache: en format: pdf (32 seiten)

PSI-14-1:2016 - JTIAP V2

37 start standards prostep ivip alle 01 11 2016 jt en psi-14-1:2016 - jtiap v2 jt industrial application package

the jt format is an industry focused, high-performance, lightweight, flexible file format for capturing and repurposing 3d product definition data that enables collaboration, validation and visualization throughout the extended enterprise.

the jt format is both robust, and streamable, and contains compression for compact and efficient representation. the format was designed to be easily integrated into enterprise translation solutions, producing a single set of 3d digital assets that support a full range of downstream processes from lightweight web-based viewing to full product digital mockups.

some of the highlights of the jt format include:

built-in support for assemblies, sub-assemblies and part constructs;

a flexible partitioning scheme, supporting single or multiple files;

b-rep solid shape representations;

product manufacturing information in support of paperless manufacturing initiatives;

precise and imprecise wireframe shape representations;

discrete purpose-built levels of detail;

triangle sets, polygon sets, point sets, line sets and implicit primitive sets (such as cylinder, cone and sphere);

a full array of visual attributes such as for materials, textures, lights;

hierarchical bounding box and bounding spheres;

data compression that allows producers of jt files to fine tune the trade-off between compression ratio and fidelity of the data.

beyond the data contents description of the jt format, the overall physical structure/organization of the format is also designed to support operations such as:

offline optimizations of the data contents, i.e. file granularity and flexibility optimized to meet the needs of enterprise data translation solutions;

asynchronous streaming of content, i.e. viewing optimizations such as view frustum and occlusion culling and fixed-framerate display modes;

layers, and layer filters.

language: en format: pdf (761 pages)

---

PSI-14-1:2016 - JTIAP V2

37 start standards prostep ivip alle 01 11 2016 jt en psi-14-1:2016 - jtiap v2 jt industrial application package

the jt format is an industry focused, high-performance, lightweight, flexible file format for capturing and repurposing 3d product definition data that enables collaboration, validation and visualization throughout the extended enterprise.

the jt format is both robust, and streamable, and contains compression for compact and efficient representation. the format was designed to be easily integrated into enterprise translation solutions, producing a single set of 3d digital assets that support a full range of downstream processes from lightweight web-based viewing to full product digital mockups.

some of the highlights of the jt format include:

built-in support for assemblies, sub-assemblies and part constructs;

a flexible partitioning scheme, supporting single or multiple files;

b-rep solid shape representations;

product manufacturing information in support of paperless manufacturing initiatives;

precise and imprecise wireframe shape representations;

discrete purpose-built levels of detail;

triangle sets, polygon sets, point sets, line sets and implicit primitive sets (such as cylinder, cone and sphere);

a full array of visual attributes such as for materials, textures, lights;

hierarchical bounding box and bounding spheres;

data compression that allows producers of jt files to fine tune the trade-off between compression ratio and fidelity of the data.

beyond the data contents description of the jt format, the overall physical structure/organization of the format is also designed to support operations such as:

offline optimizations of the data contents, i.e. file granularity and flexibility optimized to meet the needs of enterprise data translation solutions;

asynchronous streaming of content, i.e. viewing optimizations such as view frustum and occlusion culling and fixed-framerate display modes;

layers, and layer filters.

sprache: en format: pdf (761 seiten)

PSI-14-2:2015 - JT

39 start standards prostep ivip alle 9 2015 jt en psi-14-2:2015 - jt industrial use cases

the jt data format (iso 14306:2012) enables the creation and utilization of high-performance 3d models for all life stages of the product lifecycle. the compressible data format contains a cad-neutral description of product data and acts as a key factor in the integration of multiple cad and pdm systems.

this recommendation gives an overview about jt, the lightweight format for 3d data. after a short introduction a look in the brief history is given. within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. these are presented in this document.

language: en format: pdf (60 pages)

---

PSI-14-2:2015 - JT

39 start standards prostep ivip alle 9 2015 jt en psi-14-2:2015 - jt industrial use cases

the jt data format (iso 14306:2012) enables the creation and utilization of high-performance 3d models for all life stages of the product lifecycle. the compressible data format contains a cad-neutral description of product data and acts as a key factor in the integration of multiple cad and pdm systems.

this recommendation gives an overview about jt, the lightweight format for 3d data. after a short introduction a look in the brief history is given. within the jt workflow forum project group, use cases for the application of jt in the context of virtual product engineering were specified. these are presented in this document.

sprache: en format: pdf (60 seiten)

PSI 15 - ERM

36 start standards prostep ivip alle 12 2016 en psi 15 - erm enterprise rights management integration in engineering

this document provides recommendation for the integration of erm technology within engineering workflows. it provides a description of the required technical mechanisms for seamless integration of applications, policy extraction, and for the integration of long-term archiving. it supports decision making when driving erm pilots, by providing frameworks for erm operations with minimized complexity and efforts. it provides a technical overview for supplier integration within erm. a technical and organizational architecture for erm integration concludes this recommendation.

language: en format: pdf (30 pages)

---

PSI 15 - ERM

36 start standards prostep ivip alle 12 2016 en psi 15 - erm enterprise rights management integration in engineering

this document provides recommendation for the integration of erm technology within engineering workflows. it provides a description of the required technical mechanisms for seamless integration of applications, policy extraction, and for the integration of long-term archiving. it supports decision making when driving erm pilots, by providing frameworks for erm operations with minimized complexity and efforts. it provides a technical overview for supplier integration within erm. a technical and organizational architecture for erm integration concludes this recommendation.

sprache: en format: pdf (30 seiten)

PSI 16 - Code of PLM Openness

35 standards prostepivip alle 15 9 2015 cpo en psi 16 - code of plm openness offenheit in vernetzten it-umgebungen

the manufacturing of complex technical products requires a multi-layered process environment in a number of different departments, from development and production right through to after-sales, with a large number of heterogeneous it systems provided by numerous it vendors.

almost every one of these it systems has to be linked with other it systems. the amount of time and effort required by it customers for it integration is therefore extraordinarily high.

the openness of it systems, especially the ability to integrate them into various it system environments, is a key for reducing the amount of time and effort involved. this can be achieved most efficiently if the openness of the it system is based on established standards as far as possible (cf. 2.5 standards).

this code of plm openness (cpo) is intended to provide a basic understanding of the term “openness” and describe the associated basic requirements by impartial, non-discriminating criteria graduated in shall, should and may. those will be gradually enhanced and detailed to evolve plm openness. the cpo will be updated by decision of the cpo community to accommodate enhancement requirements.

the cpo is being created within the framework of a prostep ivip project in a joint activity carried out by it customers, it vendors and it service providers.

cpo-relevant definitions are defined in a glossary, which is a separate supplement to the cpo. keywords that are defined in the glossary are underlined in the cpo.

sprache: en format: pdf (20 seiten)

---

PSI 16 - Code of PLM Openness

35 standards prostepivip alle 15 9 2015 cpo en psi 16 - code of plm openness openness in networked it environments

the manufacturing of complex technical products requires a multi-layered process environment in a number of different departments, from development and production right through to after-sales, with a large number of heterogeneous it systems provided by numerous it vendors.

almost every one of these it systems has to be linked with other it systems. the amount of time and effort required by it customers for it integration is therefore extraordinarily high.

the openness of it systems, especially the ability to integrate them into various it system environments, is a key for reducing the amount of time and effort involved. this can be achieved most efficiently if the openness of the it system is based on established standards as far as possible (cf. 2.5 standards).

this code of plm openness (cpo) is intended to provide a basic understanding of the term “openness” and describe the associated basic requirements by impartial, non-discriminating criteria graduated in shall, should and may. those will be gradually enhanced and detailed to evolve plm openness. the cpo will be updated by decision of the cpo community to accommodate enhancement requirements.

the cpo is being created within the framework of a prostep ivip project in a joint activity carried out by it customers, it vendors and it service providers.

cpo-relevant definitions are defined in a glossary, which is a separate supplement to the cpo. keywords that are defined in the glossary are underlined in the cpo.

language: en format: pdf (20 pages)

PSI 17 - 3D Measurement Data Management

13 start standards guideline alle 7 2017 3dmdm en psi 17 - 3d measurement data management 3d measurement data management with i++ dms ?

a variety of measurement methods and equipment are used in the manufacturing industry today to ensure a specified level of product quality. these differ in functional properties, such as the way in which data is collected (contact or non-contact), the way in which measurement data is processed, and in the level of integration with manufacturing equipment. in addition to typical properties such as precision and speed, their performance also differs in terms of the degree to which they can be integrated into cross-domain plm processes. the multitude of devices and processes found in the manufacturing industry always presents a sizable challenge for the harmonization of processes and methods. the desire for a standardized interface for the flexible design of the measurement process, with its numerous participants and objects, is therefore a logical consequence. a complex object model is required that includes not just information on the product model but also the equipment and tools, as well as the relevant test and tolerance data (part of which is referred to as the product and manufacturing information), and its relation to the 3d geometry.

given that the quality process is increasingly drawing-free, the digital representation of product data – the so-called digital master – has a key function in this context, too.

cross-domain data management also gives rise to an additional need for powerful measurement data management. here, factors such as data-related recording, digital master, control of the measurement process as well as it systems and interfaces play a role. companies are hoping that this will bring about an increase in the level of process automation, improvements to the change process, further stabilization in the process, consistent quality statements, enhanced performance in individual process steps, and the early identification of process risks before they become a problem. this challenge was addressed collaboratively and in a timely fashion through the inspection plusplus (i++) initiative.

i++ dms is an interface definition that originated through the automotive sector’s inspection plusplus initiative and has since been evolved by automotive and aviation industry members of the 3d measurement data management project group. the interface definition describes an interface for the exchange of information between software applications involved in dimensional quality assurance. the description covers design, planning, programming, analysis and execution in the quality process.

i++ dms takes a service-based approach, and consists essentially of a uml information model, plus an xml schema that describes the uml model exactly. this extensive specification and its use in quality management systems are described here in this document.

language: en format: pdf (38 pages)

---

PSI 17 - 3D Messdatenmanagement

13 start standards guideline alle 7 2017 3dmdm en psi 17 - 3d messdatenmanagement 3d measurement data management with i++ dms ?

a variety of measurement methods and equipment are used in the manufacturing industry today to ensure a specified level of product quality. these differ in functional properties, such as the way in which data is collected (contact or non-contact), the way in which measurement data is processed, and in the level of integration with manufacturing equipment. in addition to typical properties such as precision and speed, their performance also differs in terms of the degree to which they can be integrated into cross-domain plm processes. the multitude of devices and processes found in the manufacturing industry always presents a sizable challenge for the harmonization of processes and methods. the desire for a standardized interface for the flexible design of the measurement process, with its numerous participants and objects, is therefore a logical consequence. a complex object model is required that includes not just information on the product model but also the equipment and tools, as well as the relevant test and tolerance data (part of which is referred to as the product and manufacturing information), and its relation to the 3d geometry.

given that the quality process is increasingly drawing-free, the digital representation of product data – the so-called digital master – has a key function in this context, too.

cross-domain data management also gives rise to an additional need for powerful measurement data management. here, factors such as data-related recording, digital master, control of the measurement process as well as it systems and interfaces play a role. companies are hoping that this will bring about an increase in the level of process automation, improvements to the change process, further stabilization in the process, consistent quality statements, enhanced performance in individual process steps, and the early identification of process risks before they become a problem. this challenge was addressed collaboratively and in a timely fashion through the inspection plusplus (i++) initiative.

i++ dms is an interface definition that originated through the automotive sector’s inspection plusplus initiative and has since been evolved by automotive and aviation industry members of the 3d measurement data management project group. the interface definition describes an interface for the exchange of information between software applications involved in dimensional quality assurance. the description covers design, planning, programming, analysis and execution in the quality process.

i++ dms takes a service-based approach, and consists essentially of a uml information model, plus an xml schema that describes the uml model exactly. this extensive specification and its use in quality management systems are described here in this document.

sprache: en format: pdf (38 seiten)

PSI 17 - 3D Measurement Data Management

8 standards guideline alle 3 2020 3dmdm en psi 17 - 3d measurement data management 3d measurement data management with i++ dms

a variety of measurement methods and equipment are used in the manufacturing industry today to ensure a specified level of product quality. these differ in functional properties such as way in which data is collected (contact or noncontact), the way in which measurement data is processed and in the level of integration with manufacturing equipment. in addition to typical properties such as precision and speed, their performance also differs in terms of the degree to which they can be integrated in cross-domain plm processes. the multitude of devices and processes found in the manufacturing industry always presents a sizable challenge for the harmonization of processes and methods. the desire for a standardized interface for the flexible design of the measurement process, with its numerous participants and objects, is therefore a logical consequence. an object model is required that includes not just information on the product model but also the equipment and tools, as well as the relevant test and tolerance data (part of which is referred to as the product and manufacturing information), and its relation to the 3d geometry.

given that the quality process is increasingly drawing-free, the digital representation of product data – referred to as the digital master and digital twin – has a key function in this context, too.

cross-domain data management also gives rise to an additional need for powerful measurement data management. here, factors such as data-related recording, digital master/twin, control of the measurement process as well as it systems and interfaces play a role. companies are hoping that this will bring about an increase in the level of process automation, improvements to the change process, further stabilization in the process, consistent quality statements, enhanced performance in individual process steps, and the early identification of process risks before they become a problem. this challenge was addressed collaboratively and in a timely fashion through the inspection plusplus (i++) initiative.

i++ dms is an interface definition that emerged from the automotive sector’s inspection plusplus initiative and which has been further developed by representatives of the automotive and aerospace industries in the 3d measurement data management workflow forum (3d mdm wf) and implementor forum (3d mdm if) project groups. the interface definition describes an interface for exchanging information between software applications in the field of dimensional quality assurance. the description covers design, planning, programming, analysis and execution in the quality process.

i++ dms takes a service-based approach and is primarily comprised of a uml information model and an xml schema that describes the model. this specification and its use in quality management systems are described in this document.

language: en format: pdf (41 pages)

---

PSI 17 - 3D Messdatenmanagement

8 standards guideline alle 3 2020 3dmdm en psi 17 - 3d messdatenmanagement 3d measurement data management with i++ dms

a variety of measurement methods and equipment are used in the manufacturing industry today to ensure a specified level of product quality. these differ in functional properties such as way in which data is collected (contact or noncontact), the way in which measurement data is processed and in the level of integration with manufacturing equipment. in addition to typical properties such as precision and speed, their performance also differs in terms of the degree to which they can be integrated in cross-domain plm processes. the multitude of devices and processes found in the manufacturing industry always presents a sizable challenge for the harmonization of processes and methods. the desire for a standardized interface for the flexible design of the measurement process, with its numerous participants and objects, is therefore a logical consequence. an object model is required that includes not just information on the product model but also the equipment and tools, as well as the relevant test and tolerance data (part of which is referred to as the product and manufacturing information), and its relation to the 3d geometry.

given that the quality process is increasingly drawing-free, the digital representation of product data – referred to as the digital master and digital twin – has a key function in this context, too.

cross-domain data management also gives rise to an additional need for powerful measurement data management. here, factors such as data-related recording, digital master/twin, control of the measurement process as well as it systems and interfaces play a role. companies are hoping that this will bring about an increase in the level of process automation, improvements to the change process, further stabilization in the process, consistent quality statements, enhanced performance in individual process steps, and the early identification of process risks before they become a problem. this challenge was addressed collaboratively and in a timely fashion through the inspection plusplus (i++) initiative.

i++ dms is an interface definition that emerged from the automotive sector’s inspection plusplus initiative and which has been further developed by representatives of the automotive and aerospace industries in the 3d measurement data management workflow forum (3d mdm wf) and implementor forum (3d mdm if) project groups. the interface definition describes an interface for exchanging information between software applications in the field of dimensional quality assurance. the description covers design, planning, programming, analysis and execution in the quality process.

i++ dms takes a service-based approach and is primarily comprised of a uml information model and an xml schema that describes the model. this specification and its use in quality management systems are described in this document.

sprache: en format: pdf (41 seiten)

PSI 18 - ReqIF

11 start standards guideline alle 11 2017 reqif en psi 18 - reqif comprehensive collection of industrial reqif use cases

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

language: en format: pdf (30 pages)

---

PSI 18 - ReqIF

11 start standards guideline alle 11 2017 reqif en psi 18 - reqif comprehensive collection of industrial reqif use cases

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

sprache: en format: pdf (30 seiten)

PSI 18 V2.1 - ReqIF Recommendation

3 standards guideline alle 2 2022 reqif en psi 18 v2.1 - reqif recommendation comprehensive collection of industrial reqif use cases v2.1 update

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

language: en format: pdf (38 pages)

---

PSI 18 V2.1 - ReqIF Recommendation

3 standards guideline alle 2 2022 reqif en psi 18 v2.1 - reqif recommendation comprehensive collection of industrial reqif use cases v2.1 update

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

sprache: en format: pdf (38 seiten)

PSI 18 V2.2 - ReqIF Recommendation

679 start standards guideline alle reqif en 7 2024 psi 18 v2.2 - reqif recommendation comprehensive collection of industrial reqif use cases v2.2

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

sprache: en format: pdf (40 seiten)

---

PSI 18 V2.2 - ReqIF Recommendation

679 start standards guideline alle reqif en 7 2024 psi 18 v2.2 - reqif recommendation comprehensive collection of industrial reqif use cases v2.2 

the reqif requirements interchange format [1] enables the exchange of requirement information by transferring xml documents.

this recommendation provides an overview of the prostep ivip project activities regarding reqif. after a short introduction, the interaction of the user-driven workflow forum and the vendor-driven implementor forum is explained in more detail. within the reqif workflow forum project group, use cases for the application of reqif in the context of product engineering were specified. these are presented in this document. for the industrial implementation of the use cases a workflow has been defined. to support the workflow the user community agreed on a set of user-defined attributes and their values. these attributes will become part of a reqif data exchange.

language: en format: pdf (40 pages)

PSI 19 prostep ivip Recommendation KBL

10 standards guideline alle 9 2018 ves en psi 19 prostep ivip recommendation kbl recommendation zur harness description list (kbl) language: en format: pdf (140 pages)

---

PSI 19 prostep ivip Recommendation KBL

10 standards guideline alle 9 2018 ves en psi 19 prostep ivip recommendation kbl recommendation zur harness description list (kbl) sprache: en format: pdf (140 seiten)

PSI 2 - Collaborative Product Visualization (CPV)

59 standards prostepivip alle 4 2007 jt en psi 2 - collaborative product visualization (cpv) collaborative product visualization, reference process

this recommendation serves to coordinate the exchange of visualization data for communication and information retrieval between collaborating companies. the exchange of visualization data is not restricted to a certain phase of the product life cycle.

reference use cases are described for this purpose.

this recommendation does not deal with data protection and data security. guidelines and agreements on data protection and data security should be observed and applied in a reasonable manner.

language: en format: pdf (25 pages)

---

PSI 2 - Collaborative Product Visualization (CPV)

59 standards prostepivip alle 4 2007 jt en psi 2 - collaborative product visualization (cpv) visualisierungsdatenaustausch, referenzprozesse

this recommendation serves to coordinate the exchange of visualization data for communication and information retrieval between collaborating companies. the exchange of visualization data is not restricted to a certain phase of the product life cycle.

reference use cases are described for this purpose.

this recommendation does not deal with data protection and data security. guidelines and agreements on data protection and data security should be observed and applied in a reasonable manner.

sprache: en format: pdf (25 seiten)

PSI 20 - Functional Data Exchange (FDX) Part 2; 3.1 & 3.2

4 standards guideline alle 2 2021 fdx en psi 20 - functional data exchange (fdx) part 2; 3.1 & 3.2 automated functional data exchange in the automotive industry part 2: overarching component concepts part 3.1: elastomer bushings part 3.2: dampers language: en format: zip file

---

PSI 20 - Functional Data Exchange (FDX) Part 2; 3.1 & 3.2

4 standards guideline alle 2 2021 fdx en psi 20 - functional data exchange (fdx) part 2; 3.1 & 3.2 automated functional data exchange in the automotive industry part 2: overarching component concepts part 3.1: elastomer bushings part 3.2: dampers sprache: en format: zip-datei

PSI 20 - Functional Data Exchange (FDX) Part 1

6 standards guideline alle 2 2020 fdx en psi 20 - functional data exchange (fdx) part 1 automated functional data exchange in the automotive industry part 1

this prostep ivip / vda recommendation has been devised by the fdx working group. it defines a standardized format for machine-readable specifications of a data model/format for the exchange of functional data (e.g. arrays of characteristics, single characteristics, parameters) between oems and suppliers, in order to enable the parties to exchange highly structured data. this recommendation aims at facilitating consistent and efficient implementation of these processes in the automotive industry.

objectives:

harmonization of exchange of functional data between oems and suppliers.

improved quality and availability of functional data for cae/simulation purposes

elimination of discrepancies in functional data between ordered and delivered data

greater automation in data generation, exchange and processing

note re. version 1.1.0
this prostep ivip / vda recommendation defines the fdx format. this version of the document describes the standardized rules for the development of compatible software tools. at the moment there are a number of development projects for specialized software tools that support the fdx data format in progress. after completion of a reference implementation, the required technical artefacts as well as parts 2 and 3-1 to 3-n will be added to this prostep ivip / vda recommendation in order to facilitate its practical implementation. in the course of the implementation of the software tool(s), it might become necessary to provide some clarifications regarding this document, which will be published as the need arises.

language: en format: pdf (83 pages)

---

PSI 20 - Functional Data Exchange (FDX) Part 1

6 standards guideline alle 2 2020 fdx en psi 20 - functional data exchange (fdx) part 1 automated functional data exchange in the automotive industry part 1

this prostep ivip / vda recommendation has been devised by the fdx working group. it defines a standardized format for machine-readable specifications of a data model/format for the exchange of functional data (e.g. arrays of characteristics, single characteristics, parameters) between oems and suppliers, in order to enable the parties to exchange highly structured data. this recommendation aims at facilitating consistent and efficient implementation of these processes in the automotive industry.

objectives:

harmonization of exchange of functional data between oems and suppliers.

improved quality and availability of functional data for cae/simulation purposes

elimination of discrepancies in functional data between ordered and delivered data

greater automation in data generation, exchange and processing

note re. version 1.1.0
this prostep ivip / vda recommendation defines the fdx format. this version of the document describes the standardized rules for the development of compatible software tools. at the moment there are a number of development projects for specialized software tools that support the fdx data format in progress. after completion of a reference implementation, the required technical artefacts as well as parts 2 and 3-1 to 3-n will be added to this prostep ivip / vda recommendation in order to facilitate its practical implementation. in the course of the implementation of the software tool(s), it might become necessary to provide some clarifications regarding this document, which will be published as the need arises.

sprache: en format: pdf (83 seiten)

PSI 21 - Vehicle Electric Container (VEC)

7 standards guideline alle 6 2020 ves en psi 21 - vehicle electric container (vec) specification of the vec data format language: en format: pdf (356 pages)

---

PSI 21 - Vehicle Electric Container (VEC)

7 standards guideline alle 6 2020 ves en psi 21 - vehicle electric container (vec) spezifikation des datenformats vec sprache: en format: pdf (356 seiten)

PSI 23 - Cross-Discipline Lifecycle Collaboration (CDLC)

5 standards guideline alle 8 2020 cdlc en psi 23 - cross-discipline lifecycle collaboration (cdlc) linking data and processes across disciplines

the prostep ivip association’s cross-discipline lifecycle collaboration (cdlc) working group is a community of manufacturers, suppliers, software vendors and process and tool experts, who are all facing the challenge of improving digital transparency and continuity and thus cross-discipline collaboration in the product development process.

this document summarizes best practices for cross-discipline collaboration (processes, roles, data model, architecture) and recommendations of the working group for setting up federated architectures and enabling end-to-end data continuity and traceability.

the recommendations presented here are derived from the lessons learned from three demonstrators developed by aras, ptc and contact software, based on an industrial change process use case and a mars rover dataset.

language: en format: pdf (55 pages)

---

PSI 23 - Cross-Discipline Lifecycle Collaboration (CDLC)

5 standards guideline alle 8 2020 cdlc en psi 23 - cross-discipline lifecycle collaboration (cdlc) linking data and processes across disciplines

the prostep ivip association’s cross-discipline lifecycle collaboration (cdlc) working group is a community of manufacturers, suppliers, software vendors and process and tool experts, who are all facing the challenge of improving digital transparency and continuity and thus cross-discipline collaboration in the product development process.

this document summarizes best practices for cross-discipline collaboration (processes, roles, data model, architecture) and recommendations of the working group for setting up federated architectures and enabling end-to-end data continuity and traceability.

the recommendations presented here are derived from the lessons learned from three demonstrators developed by aras, ptc and contact software, based on an industrial change process use case and a mars rover dataset.

sprache: en format: pdf (55 seiten)

PSI 24 / VDA 4961/4 Recommendation on Collaboration in Systems Engineering Projects – Collaborative Systems Engineering (CSE)

27 standards prostepivip alle 6 2022 en de psi 24 / vda 4961/4 recommendation on collaboration in systems engineering projects – collaborative systems engineering (cse) the existing se checklist (vda 4961/3) with focus on the area of mechanical product development/cad from 2013 has been revised and now has the focus on the collaboration between partners in systems engineering.

this document resulted from a cooperation between vda and psi.

this version replaces vda recommendation 4961/3 of april 2013.

this recommendation serves to coordinate data exchange, communication and organisation within the framework of cooperation between partners in systems engineering projects. due to the increasing digitalisation of products in the automotive industry and the associated extended integration requirements among the partners, this checklist expands the previous version to include all domains of the v-modell in product development. it has been given a new reference and a new name and will henceforth be known as the collaborative systems engineering checklist (cse checklist).

the vda and psi recommendation supports the preparation and implementation of project work by:

classifying the cooperation models to differentiate the development partnerships: the cooperation models classify the development partners according to their role in the development partnership and as-sign specific characteristics to them.

use of the cse checklist and associated templates to align data logistics in collaboration projects with the specified collab-oration models:

the cse checklist and associated templates address the following topics:

• specific communication and ca infrastructure (ca = computer aided) of the project partners.
• definition of data exchange formats for technical documents and models (data exchange content, quality, procedures) in all domains of systems engineering
• process-oriented specifications
• project management, change and release procedures
• determination of deadlines, times, costs and responsibilities
• legal aspects

language: en & de format: zip file

---

PSI_24/VDA 4961/4 Empfehlung zur Zusammenarbeit in Systems Engineering Projekten – Collaborative Systems Engineering (CSE)

27 standards prostepivip alle 6 2022 en de psi_24/vda 4961/4 empfehlung zur zusammenarbeit in systems engineering projekten – collaborative systems engineering (cse) the existing se checklist (vda 4961/3) with focus on the area of mechanical product development/cad from 2013 has been revised and now has the focus on the collaboration between partners in systems engineering.

dieses dokument entstand aus einer kooperation zwischen vda und psi.

diese version ersetzt die vda empfehlung 4961/3 vom april 2013.

diese empfehlung dient der abstimmung des datenaustauschs, der kommunikation und der organisation im rahmen der zusammenarbeit zwischen partnern in systems-engineering-projekten. auf grund der zunehmenden digitalisierung der produkte in der automobilindustrie und den damit verbundenen erweiterten integrationsanforderungen bei den partnern erweitert die vorliegende checkliste die bisherige version um alle domänen des v-modells in der produktentwicklung. sie erhält einen neuen bezug und einen neuen namen und wird fortan als collaborative systems engineering checkliste (cse-checkliste) geführt.

die vda- und psi-empfehlung unterstützt die vorbereitung und durchführung der projektarbeit durch:

klassifizierung der kooperationsmodelle zur differenzierung der entwicklungspartnerschaften: die kooperationsmodelle klassifizieren die entwicklungspartner entsprechend ihrer rolle in der entwicklungspartnerschaft und ordnen diesen spezifischen eigenschaften zu.

anwendung der cse-checkliste und der zugehörigen vorlagen zur abstimmung der datenlogistik in kollaborationsprojekten in bezug auf die vorgegebenen kooperationsmodelle:

mit der cse-checkliste und den zugehörigen vorlagen werden folgende themen behandelt:

• spezifische kommunikations- und ca-infrastruktur (ca = computer aided) der projektpartner
• festlegung von datenaustauschformaten für technische dokumente und modelle (datenaustausch-inhalte, -qualität, -verfahren) in allen domänen des systems engineering
• prozessorientierte festlegungen
• projektmanagement, änderungs- und freigabeverfahren
• bestimmung von terminen, zeiten, kosten und verantwortungen
• rechtliche aspekte

sprache: de & en format: zip-datei

PSI 25 PSMS Recommendation und Anhänge

2 standards guideline alle 3 2022 psms de psi 25 psms recommendation und anhänge die vorliegenden empfehlung adressiert die digitalisierte synchronisation (psms) von terminmanagement informationen zwischen den partnern in einem projekt, organisationsübergreifend und toolunabhängig.

die netzwerke und damit die anzahl der projektverbünde speziell im automobilbereich werden immer größer. damit steigen die notwendigkeit und herausforderungen, diese prozessual, methodisch als auch tool-seitig zu managen. die vorliegenden empfehlungen sind eine erweiterung der bestehenden empfehlungen zum thema project schedule management (psm) und adressiert die digitalisierte synchronisation (psms) von terminmanagement informationen - von einfachen meilensteininformationen bis hin zu kompletten netzplänen inkl. der referenzen und integration in andere fachdisziplinen hinein - zwischen den partnern in einem projekt, organisationsübergreifend und toolunabhängig.

die projektpartner synchronisieren ihre spezifischen pläne über einige wenige, hier vordefinierte psms nachrichten (psms messages). jede psms message als kommunikationseinheit hat eine klare struktur und einen definierten umfang. der inhalt passt sich je nach bezug zur jeweiligen synchronisation und den benötigten informationen flexibel an. dank des hier beschriebenen konsistenten regelwerks und des dahinterstehenden international standardisierten informationsmodells lassen sich nahezu alle denkbaren anwendungsfälle problemlos umsetzen.

die projektpartner implementieren die psms messages in den schnittstellen. der empfohlene schnittstellenprozess zur unterstützung typischer synchronisationsszenarien an den empfohlenen synchronisationspunkten basiert auf den projektmanagement prozessgruppen des project management institutes (pmi) nach [pmbok].

die spezifikationen für die kommunikation und synchronisation können auf der basis des standardisierten psm informationsmodells und durch befolgen der regeln automatisiert werden. das psm business object model (kurz psm schema) zur synchronisation der psm informationen ist aus der iso 101303-242, dem ap 242 domain model ([ap242]) als untermenge (ausschnitt) abgeleitet. es repräsentiert die elemente, eigenschaften und beziehungen, welche für die psm kommunikation und synchronisation zwischen den partnern und systemen relevant bzw. empfohlen sind.

die psms kann agil und phasenweise eingeführt werden. die aufeinander abgestimmten, funktionalen ausbaustufen machen es sogar möglich, dass partner auf unterschiedlichen, so genannten 'synchronization levels' auch im selben projektteam 'mitspielen' können. die psms empfehlungen können einerseits durch die verantwortlichen organisationseinheiten und personen auf anwenderseite als genereller leitfaden und referenz zur gestaltung ihrer psm abstimmungs- und synchronisationsprozesse in einem netzwerk von partnern genutzt werden. andrerseits können sie auch für die umsetzung in den psm systemen und schnittstellen durch die verantwortlichen einheiten, systemarchitekten und vendoren auf der service- und implementierungsebene verwendet werden.

die psm synchronisation …

unterstützt das psm von einfachen bis zu komplexesten kollaborationsnetzwerken und auf allen ebenen (projektstrukturen, meilensteine, arbeitspakete, vorgänge) inkl. der referenzen auf betroffene / resultierende objekte (liefergegenstände)

ermöglicht die integration unterschiedlicher psm methoden und (pm) werkzeuge über organisations-, unternehmens- und systemgrenzen hinweg, denn sie …

ist unabhängig von den planungswerkzeugen und -methoden, welche interne sowie externe kunden und lieferanten verwenden

verbessert die prozesse des pm von der initiierung über planung, ausführung, überwachung und steuerung bis zum abschluss da die informationen alle stakeholder richtig erreichen, weil die rollen und verantwortlichkeiten klar definiert und die abstimmungsschritte untereinander einfach sind

sichert als modellbasierte lösung eine hochgradige standardisierung da alle die gleiche 'psm sprache' sprechen

spart investitionen und erreicht langfristige nachhaltigkeit der pm integration

verhindert bzw. eliminiert proprietäre lösungen und manuelle übergänge

ist harmonisiert mit und unterstützt andere domänen bei der anwendung und integration der prozessbezogenen objekte (work management) des ap 242 domain object models

mit der psm synchronisation ist die kommunikation für alle beteiligten klar und der gemeinsame fortschritt kann in verteilten oder zentralen lösungen transparent analysiert, dokumentiert und nachverfolgt werden, und das auch bei hochdynamischen projekten mit vielfältigen abhängigkeiten zwischen allen partnern.

language: de format: zip file

---

PSI 25 PSMS Recommendation und Anhänge

2 standards guideline alle 3 2022 psms de psi 25 psms recommendation und anhänge die vorliegenden empfehlung adressiert die digitalisierte synchronisation (psms) von terminmanagement informationen zwischen den partnern in einem projekt, organisationsübergreifend und toolunabhängig.

die netzwerke und damit die anzahl der projektverbünde speziell im automobilbereich werden immer größer. damit steigen die notwendigkeit und herausforderungen, diese prozessual, methodisch als auch tool-seitig zu managen. die vorliegenden empfehlungen sind eine erweiterung der bestehenden empfehlungen zum thema project schedule management (psm) und adressiert die digitalisierte synchronisation (psms) von terminmanagement informationen - von einfachen meilensteininformationen bis hin zu kompletten netzplänen inkl. der referenzen und integration in andere fachdisziplinen hinein - zwischen den partnern in einem projekt, organisationsübergreifend und toolunabhängig.

die projektpartner synchronisieren ihre spezifischen pläne über einige wenige, hier vordefinierte psms nachrichten (psms messages). jede psms message als kommunikationseinheit hat eine klare struktur und einen definierten umfang. der inhalt passt sich je nach bezug zur jeweiligen synchronisation und den benötigten informationen flexibel an. dank des hier beschriebenen konsistenten regelwerks und des dahinterstehenden international standardisierten informationsmodells lassen sich nahezu alle denkbaren anwendungsfälle problemlos umsetzen.

die projektpartner implementieren die psms messages in den schnittstellen. der empfohlene schnittstellenprozess zur unterstützung typischer synchronisationsszenarien an den empfohlenen synchronisationspunkten basiert auf den projektmanagement prozessgruppen des project management institutes (pmi) nach [pmbok].

die spezifikationen für die kommunikation und synchronisation können auf der basis des standardisierten psm informationsmodells und durch befolgen der regeln automatisiert werden. das psm business object model (kurz psm schema) zur synchronisation der psm informationen ist aus der iso 101303-242, dem ap 242 domain model ([ap242]) als untermenge (ausschnitt) abgeleitet. es repräsentiert die elemente, eigenschaften und beziehungen, welche für die psm kommunikation und synchronisation zwischen den partnern und systemen relevant bzw. empfohlen sind.

die psms kann agil und phasenweise eingeführt werden. die aufeinander abgestimmten, funktionalen ausbaustufen machen es sogar möglich, dass partner auf unterschiedlichen, so genannten 'synchronization levels' auch im selben projektteam 'mitspielen' können. die psms empfehlungen können einerseits durch die verantwortlichen organisationseinheiten und personen auf anwenderseite als genereller leitfaden und referenz zur gestaltung ihrer psm abstimmungs- und synchronisationsprozesse in einem netzwerk von partnern genutzt werden. andrerseits können sie auch für die umsetzung in den psm systemen und schnittstellen durch die verantwortlichen einheiten, systemarchitekten und vendoren auf der service- und implementierungsebene verwendet werden.

die psm synchronisation …

unterstützt das psm von einfachen bis zu komplexesten kollaborationsnetzwerken und auf allen ebenen (projektstrukturen, meilensteine, arbeitspakete, vorgänge) inkl. der referenzen auf betroffene / resultierende objekte (liefergegenstände)

ermöglicht die integration unterschiedlicher psm methoden und (pm) werkzeuge über organisations-, unternehmens- und systemgrenzen hinweg, denn sie …

ist unabhängig von den planungswerkzeugen und -methoden, welche interne sowie externe kunden und lieferanten verwenden

verbessert die prozesse des pm von der initiierung über planung, ausführung, überwachung und steuerung bis zum abschluss da die informationen alle stakeholder richtig erreichen, weil die rollen und verantwortlichkeiten klar definiert und die abstimmungsschritte untereinander einfach sind

sichert als modellbasierte lösung eine hochgradige standardisierung da alle die gleiche 'psm sprache' sprechen

spart investitionen und erreicht langfristige nachhaltigkeit der pm integration

verhindert bzw. eliminiert proprietäre lösungen und manuelle übergänge

ist harmonisiert mit und unterstützt andere domänen bei der anwendung und integration der prozessbezogenen objekte (work management) des ap 242 domain object models

mit der psm synchronisation ist die kommunikation für alle beteiligten klar und der gemeinsame fortschritt kann in verteilten oder zentralen lösungen transparent analysiert, dokumentiert und nachverfolgt werden, und das auch bei hochdynamischen projekten mit vielfältigen abhängigkeiten zwischen allen partnern.

sprache: de format: zip-datei

PSI-26 12/2021 - PLiM Recommendation 2021

29 standards prostepivip alle 12 2021 plim en psi-26 12/2021 - plim recommendation 2021 bridging the gap – seamless information transfer in production environments

the demand for customized products, shorter product lifecycles and cost pressures require increased efficiency and flexibility in the development and operation of production systems, which are becoming increasingly complex. digital tools and models are being used for end-to-end model-based engineering in this context. exploitation of their full potential is currently being hindered by discontinuities in the flow of data and information, e.g. during collaboration between different internal and external departments, which leads to high subsequent costs. the evaluation of a recent survey indicated a significant impact on projects in terms of material and time. the apparent lack of data standards underscores industry's pressing need for the information model being put forward. continued media discontinuities in the companies' data management systems, however, make it imperative that a universal information model, which includes products, processes and resources (ppr), be standardized.

companies, however, often make insufficient use of current standard models, due in large part to their strongly generic character, and users struggle in the face of their abstraction and complexity. the prostep ivip association's production lifecycle information management (plim) group has developed an application-related data model based on two different industrial use cases. unlike existing standards, this model does not fully cover all use cases, but it is more clearly structured and more practice oriented. transfer to isa-95 and export to a generic exchange format (aml) as an existing industrial data interface demonstrated that the information model can also be used for tool-unspecific applications. with focus placed on achieving a high level of usability, it will be necessary in the future to investigate whether additional use cases could be used to derive a standard that a large number of companies could integrate.

language: en format: pdf (29 pages)

---

PSI-26 12/2021 - PLiM Recommendation 2021

29 standards prostepivip alle 12 2021 plim en psi-26 12/2021 - plim recommendation 2021 bridging the gap – seamless information transfer in production environments

the demand for customized products, shorter product lifecycles and cost pressures require increased efficiency and flexibility in the development and operation of production systems, which are becoming increasingly complex. digital tools and models are being used for end-to-end model-based engineering in this context. exploitation of their full potential is currently being hindered by discontinuities in the flow of data and information, e.g. during collaboration between different internal and external departments, which leads to high subsequent costs. the evaluation of a recent survey indicated a significant impact on projects in terms of material and time. the apparent lack of data standards underscores industry's pressing need for the information model being put forward. continued media discontinuities in the companies' data management systems, however, make it imperative that a universal information model, which includes products, processes and resources (ppr), be standardized.

companies, however, often make insufficient use of current standard models, due in large part to their strongly generic character, and users struggle in the face of their abstraction and complexity. the prostep ivip association's production lifecycle information management (plim) group has developed an application-related data model based on two different industrial use cases. unlike existing standards, this model does not fully cover all use cases, but it is more clearly structured and more practice oriented. transfer to isa-95 and export to a generic exchange format (aml) as an existing industrial data interface demonstrated that the information model can also be used for tool-unspecific applications. with focus placed on achieving a high level of usability, it will be necessary in the future to investigate whether additional use cases could be used to derive a standard that a large number of companies could integrate.

sprache: en format: pdf (29 seiten)

PSI-27 12.2021 - Additive Manufacturing Interfaces

30 standards prostepivip alle 12 2021 ami en psi-27 12.2021 - additive manufacturing interfaces this recommendation presents a summary of the potentials and challenges of additive manufacturing interfaces and defines the requirements for current and future data exchange formats.

additive manufacturing, often simply referred to as 3d printing, is creating new business opportunities for manufacturing industry.

additive manufacturing processes have been available for at least three decades and therefore have a long tradition in the field of prototyping, e.g. in automotive engineering. the motivation behind the use of this type of manufacturing technology was essentially the speed at which physical models of the designed components could be made available. hence, the term "rapid prototyping" was born.

the resulting physical models were predominantly used for visualization, packaging, etc., while series production of the components was implemented – without exception – using conventional manufacturing processes, which often required dies and fixtures (e.g. casting).

this situation still exists to a large extent today, which means that existing prototyping processes are not currently exploiting key potential that additive manufacturing offers. this includes:

extensive freedom in product design in terms of geometry, material distribution and functional integration

economic and fast production of small and very small lot sizes compared to resource- and processing-time-intensive production methods (often mentioned in the context of objectives like "individualization", "lot size of 1" or "rapid manufacturing")

greater opportunities for cross-company collaboration, e.g. with external print service providers, than is possible with conventional manufacturing technologies.

companies are gearing up for the transformation of existing processes needed to implement additive manufacturing for series production. however, while 3d printer technology and print material capabilities are advancing at a remarkable speed, existing digital tool chains and data formats face the challenge of trying to keep pace.

design freedom, new manufacturing strategies and the need for a high degree of automation to speed up print job generation require the loss-free exchange of data between best-in-class process tools. protecting valuable know-how and intellectual property (ip) when product data is exchanged between departments or companies is a key requirement. this recommendation presents a summary of the above-mentioned potential and challenges and defines the requirements for current and future data exchange formats. this provides us with a basis for making recommendations regarding digital interfaces, methods and architectural concepts for collaboration including ip protection.

language: en format: pdf (38 pages)

---

PSI-27 12.2021 - Additive Manufacturing Interfaces

30 standards prostepivip alle 12 2021 ami en psi-27 12.2021 - additive manufacturing interfaces this recommendation presents a summary of the potentials and challenges of additive manufacturing interfaces and defines the requirements for current and future data exchange formats.

additive manufacturing, often simply referred to as 3d printing, is creating new business opportunities for manufacturing industry.

additive manufacturing processes have been available for at least three decades and therefore have a long tradition in the field of prototyping, e.g. in automotive engineering. the motivation behind the use of this type of manufacturing technology was essentially the speed at which physical models of the designed components could be made available. hence, the term "rapid prototyping" was born.

the resulting physical models were predominantly used for visualization, packaging, etc., while series production of the components was implemented – without exception – using conventional manufacturing processes, which often required dies and fixtures (e.g. casting).

this situation still exists to a large extent today, which means that existing prototyping processes are not currently exploiting key potential that additive manufacturing offers. this includes:

extensive freedom in product design in terms of geometry, material distribution and functional integration

economic and fast production of small and very small lot sizes compared to resource- and processing-time-intensive production methods (often mentioned in the context of objectives like "individualization", "lot size of 1" or "rapid manufacturing")

greater opportunities for cross-company collaboration, e.g. with external print service providers, than is possible with conventional manufacturing technologies.

companies are gearing up for the transformation of existing processes needed to implement additive manufacturing for series production. however, while 3d printer technology and print material capabilities are advancing at a remarkable speed, existing digital tool chains and data formats face the challenge of trying to keep pace.

design freedom, new manufacturing strategies and the need for a high degree of automation to speed up print job generation require the loss-free exchange of data between best-in-class process tools. protecting valuable know-how and intellectual property (ip) when product data is exchanged between departments or companies is a key requirement. this recommendation presents a summary of the above-mentioned potential and challenges and defines the requirements for current and future data exchange formats. this provides us with a basis for making recommendations regarding digital interfaces, methods and architectural concepts for collaboration including ip protection.

sprache: en format: pdf (38 seiten)

PSI 3 - Engineering Change Management

58 standards prostepivip alle 12 2007 en psi 3 - engineering change management part: 3-2 draft-spezifikation for engineering change order (eco)

this recommendation documents the eco (engineering change order) related results of the prostep ivip/vda project group ecm (engineering change management). it includes the eco reference process phases, scenarios and data model. the current version 0.9 is mature for validation by concept pilots.

this recommendation was originally planed as part 2 of the vda recommendation 4965 (vda 4965). since the demand of the project group to ensure their results by concept pilots could not be fulfilled, the ecm project group decided to close its work at the end of 2007. but since the gathered eco content is seen as mature and valuable for public, it is documented by this psi 3-2 (draft) recommendation, especially for the members of the prostep ivip association.

it is recommended to make familiar with the concepts of vda 4965 to understand this recommendation.

"the vda 4965 is subdivided into individual parts reflecting the ecm reference sub-process involved during the course of a change; this subdivision is subject to change as a result of further developments.

the main document gives an overview of and offers general recommendations for the overall ecm reference process, its modeling and a partner model. it describes fundamentals and basic recommendations valid for each ecm reference sub-process. this document goes on to define

ecm reference sub-processes,

interaction scenarios,

messages for the communication,

ecm data model objects and,

mappings onto standards

which are shared by and relate to the specific parts of the recommendation as follows:

part 1 (ecr – specification and decision on change) offers recommendations with respect to communicating engineering change request (ecr) data to support the specification of proposed changes and the associated decisions. it describes the ecr reference process which permits synchronization of the different internal procedures of the partners involved using ecr messages. it offers recommendations for permitted sequences of ecr messages to provide support for business-typical ecr interaction scenarios (is) within the scope of bilateral communication between the cooperation partners and recommendations with respect to the minimum requirements applicable to communication and message content. the change data contained in the individual communication steps is described in the ecr data model. the recommendation goes on to define how this information can be mapped to internationally accepted and established standards in order to permit implementation in the systems and interfaces involved.

this recommendation was originally planed as part 2 of the vda recommendation 4965 (vda 4965). until today these results could not be validated in industrial pilot applications. but as the gathered eco content is seen as mature and valuable for public, the project group decided to publish it within this draft psi-3-2 recommendation, ready to be used and validated in industrial pilot eco applications.

language: en format: pdf (47 pages)

---

PSI 3 - Engineering Change Management

58 standards prostepivip alle 12 2007 en psi 3 - engineering change management teil: 3-2 draft-spezifikation zur engineering change order (eco)

this recommendation documents the eco (engineering change order) related results of the prostep ivip/vda project group ecm (engineering change management). it includes the eco reference process phases, scenarios and data model. the current version 0.9 is mature for validation by concept pilots.

this recommendation was originally planed as part 2 of the vda recommendation 4965 (vda 4965). since the demand of the project group to ensure their results by concept pilots could not be fulfilled, the ecm project group decided to close its work at the end of 2007. but since the gathered eco content is seen as mature and valuable for public, it is documented by this psi 3-2 (draft) recommendation, especially for the members of the prostep ivip association.

it is recommended to make familiar with the concepts of vda 4965 to understand this recommendation.

"the vda 4965 is subdivided into individual parts reflecting the ecm reference sub-process involved during the course of a change; this subdivision is subject to change as a result of further developments.

the main document gives an overview of and offers general recommendations for the overall ecm reference process, its modeling and a partner model. it describes fundamentals and basic recommendations valid for each ecm reference sub-process. this document goes on to define

ecm reference sub-processes,

interaction scenarios,

messages for the communication,

ecm data model objects and,

mappings onto standards

which are shared by and relate to the specific parts of the recommendation as follows:

part 1 (ecr – specification and decision on change) offers recommendations with respect to communicating engineering change request (ecr) data to support the specification of proposed changes and the associated decisions. it describes the ecr reference process which permits synchronization of the different internal procedures of the partners involved using ecr messages. it offers recommendations for permitted sequences of ecr messages to provide support for business-typical ecr interaction scenarios (is) within the scope of bilateral communication between the cooperation partners and recommendations with respect to the minimum requirements applicable to communication and message content. the change data contained in the individual communication steps is described in the ecr data model. the recommendation goes on to define how this information can be mapped to internationally accepted and established standards in order to permit implementation in the systems and interfaces involved.

this recommendation was originally planed as part 2 of the vda recommendation 4965 (vda 4965). until today these results could not be validated in industrial pilot applications. but as the gathered eco content is seen as mature and valuable for public, the project group decided to publish it within this draft psi-3-2 recommendation, ready to be used and validated in industrial pilot eco applications.

sprache: en format: pdf (47 seiten)

PSI 31 CBPC Recommendation

185 start standards guideline alle 12 2023 cbpc en psi 31 cbpc recommendation

challenges and lessons learned for successful implementations

this recommendation summarizes the results of the cloud-based production collaboration (cbpc) project group. the objective of the cbpc project group is to evaluate possibilities and solutions for heterogeneous cloud-based collaboration scenarios within and between companies in the manufacturing industry with focus placed on production. 

language: en format: pdf (31 pages)

---

PSI 31 CBPC Recommendation

185 start standards guideline alle 12 2023 cbpc en psi 31 cbpc recommendation

challenges and lessons learned for successful implementations

this recommendation summarizes the results of the cloud-based production collaboration (cbpc) project group. the objective of the cbpc project group is to evaluate possibilities and solutions for heterogeneous cloud-based collaboration scenarios within and between companies in the manufacturing industry with focus placed on production. 

sprache: en format: pdf (31 seiten)

PSI 4 v2.0 - Simulation Data Management

57 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0 - simulation data management empfehlung zur integration der simulation und berechnung in eine pdm-umgebung (simpdm)

this recommendation is intended to standardize the integration of simulation and computation data in a product data mana gement environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a metadata model to describe simulation and computation data. the metadata model is modularly designed to allow a customtailored solution for simulation data management. furthermore this recommendation describes necessary functionalities, clustered towards use cases. functionality and use cases are modular, too. this means that it is possible to customize simpdm to suit the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

the main recommendation document (the document in hand)

annex a: glossary (included in the main document)

annex b: business process diagrams (simulation data management for mbs, fem and cfd)

annex c: core data management functionality

annex d: system communication functionality

annex e: data model

the annexes b, c, d, e are available for download as separate documents on the websites of the prostep ivip association
(www.prostep.org) and vda (www.vda.de).

sprache: en format: pdf (64 seiten)

---

PSI 4 v2.0 - Simulation Data Management

57 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0 - simulation data management recommendation for the integration of simulation and computation in a pdm environment (simpdm)

this recommendation is intended to standardize the integration of simulation and computation data in a product data mana gement environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a metadata model to describe simulation and computation data. the metadata model is modularly designed to allow a customtailored solution for simulation data management. furthermore this recommendation describes necessary functionalities, clustered towards use cases. functionality and use cases are modular, too. this means that it is possible to customize simpdm to suit the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

the main recommendation document (the document in hand)

annex a: glossary (included in the main document)

annex b: business process diagrams (simulation data management for mbs, fem and cfd)

annex c: core data management functionality

annex d: system communication functionality

annex e: data model

the annexes b, c, d, e are available for download as separate documents on the websites of the prostep ivip association
(www.prostep.org) and vda (www.vda.de).

language: en format: pdf (64 pages)

PSI 5 ECAD-MCAD – IDXv3.5

34 start standards prostepivip alle 01 7 2018 ecad-mcad en psi 5 ecad-mcad – idxv3.5 empfehlung zum austausch von daten zwischen ecad- und mcad-systemen, umfasst idx schema, dokumentation und implementation guidelines sprache: en format: zip-datei

---

PSI 5 ECAD-MCAD – IDXv3.5

34 start standards prostepivip alle 01 7 2018 ecad-mcad en psi 5 ecad-mcad – idxv3.5 recommendation to exchange data between ecad and mcad systems, includes idx schema, documentation, and implementation guidelines language: en format: zip file

PSI 5 ECAD-MCAD – IDXv4.0

33 start standards prostep ivip alle 18 7 2019 ecad-mcad en psi 5 ecad-mcad – idxv4.0 empfehlung zum austausch von daten zwischen ecad- und mcad-systemen, umfasst dokumentation und empfehlungen für anwender und entwickler sprache: en format: zip-datei

---

PSI 5 ECAD-MCAD – IDXv4.0

33 start standards prostep ivip alle 18 7 2019 ecad-mcad en psi 5 ecad-mcad – idxv4.0 recommendation to exchange data between ecad and mcad systems, includes documentation and recommendations for users and developers language: en format: zip file

PSI 5 ECAD-MCAD – IDXv4.5

32 standards prostepivip alle 01 9 2020 ecad-mcad en psi 5 ecad-mcad – idxv4.5 empfehlung zum austausch von daten zwischen ecad- und mcad-systemen, umfasst dokumentation und empfehlungen für anwender und entwickler sprache: en format: zip-datei

---

PSI 5 ECAD-MCAD – IDXv4.5

32 standards prostepivip alle 01 9 2020 ecad-mcad en psi 5 ecad-mcad – idxv4.5 recommendation to exchange data between ecad and mcad systems, includes documentation and recommendations for users and developers language: en format: zip file

PSI 6 - Req IF

46 standards prostepivip alle 10 2008 reqif en psi 6 - req if psi 6 - requirements interchange format (rif) - durch omg reqif ersetzt

requirements management has been established in the industry as a primary method to get flawlessly from the early product target definitions over the implementation up to the validation and testing phase. despite its cross-functional nature requirements management is a key factor for successful partner integration within the development cycle. manufacturers specify requirements for their entire product as well as the aggregation of systems/components and their suppliers provide system specifications describing how their product will meet these needs. in order to manage the complexity growths due to the increase of requirements and requirement specifications, especially with regards to mechatronics, manufacturers and suppliers introduced requirements management systems. these systems are used within an organizational context but can not really bridge the gap between manufacturers and suppliers, as only tool specific exchange formats and methods exist.

in order to address the circumstance of the unavailability of a generic requirements exchange format the “simulation and tools” group of the his (hersteller initiative software) specified the requirement interchange format (rif). this specification was then handed over to the prostep ivip association to be published as prostep ivip recommendation. this recommendation will serve as a basis for a future international standardization of the rif to enable its broad application.

this prostep ivip recommendation covers the use cases to be supported, the format specification as data model description and additional implementation details to be considered.

language: en format: pdf (68 pages)

---

PSI 6 - Req IF

46 standards prostepivip alle 10 2008 reqif en psi 6 - req if psi 6 - requirements interchange format (rif) - durch omg reqif ersetzt

requirements management has been established in the industry as a primary method to get flawlessly from the early product target definitions over the implementation up to the validation and testing phase. despite its cross-functional nature requirements management is a key factor for successful partner integration within the development cycle. manufacturers specify requirements for their entire product as well as the aggregation of systems/components and their suppliers provide system specifications describing how their product will meet these needs. in order to manage the complexity growths due to the increase of requirements and requirement specifications, especially with regards to mechatronics, manufacturers and suppliers introduced requirements management systems. these systems are used within an organizational context but can not really bridge the gap between manufacturers and suppliers, as only tool specific exchange formats and methods exist.

in order to address the circumstance of the unavailability of a generic requirements exchange format the “simulation and tools” group of the his (hersteller initiative software) specified the requirement interchange format (rif). this specification was then handed over to the prostep ivip association to be published as prostep ivip recommendation. this recommendation will serve as a basis for a future international standardization of the rif to enable its broad application.

this prostep ivip recommendation covers the use cases to be supported, the format specification as data model description and additional implementation details to be considered.

sprache: en format: pdf (68 seiten)

PSI 7 - ERM

40 start standards prostep ivip alle 4 2015 en psi 7 - erm

this document provides recommendations for the adoption of erm technology especially for the cross-enterprise exchange of sensitive data such as product data or bidding documents. it describes a reference process for the introduction and use of the technology as well as a reference system architecture. where applicable, standards are proposed for the interfaces between the systems involved.

language: en format: pdf (43 pages)

---

PSI 7 - ERM

40 start standards prostep ivip alle 4 2015 en psi 7 - erm spezifikation zum enterprise rights management

this document provides recommendations for the adoption of erm technology especially for the cross-enterprise exchange of sensitive data such as product data or bidding documents. it describes a reference process for the introduction and use of the technology as well as a reference system architecture. where applicable, standards are proposed for the interfaces between the systems involved.

sprache: en format: pdf (43 seiten)

PSI 8 - Digital Manufacturing

42 start standards prostep ivip alle 3 2013 plim en psi 8 - digital manufacturing empfehlung zu produktions planungsprozessen

in the product creation process, production planning is perhaps the most important process, second only to product development. however, software-based support for production planning at companies currently takes place against the background of established structures and the fulfillment of location-specific requirements using what is frequently a number of different digital tools. this gives rise to an extremely heterogeneous environment as far as planning tools are concerned. this heterogeneity is also reflected in the planning processes themselves and hinders end-to-end planning. in particular, it makes cross-location planning, the comparison of planning results and the exchange between different planning disciplines and planning departments very difficult. a reference process for production planning is required to ensure end-to-end planning and the harmonization of multiple planning processes.

the creation of just such a reference planning process for production planning is the aim of this psi recommendation. for the purpose of defining this reference process, the production planning is first of all placed in the context of the product creation process. production planning starts shortly after the initial idea for a product using initial input from product development and runs in parallel with product development to a point well beyond the start of production. a further look is also taken at production planningrelated tasks required for series planning during manufacturing and assembly.

the reference process discussed in this recommendation has a strictly defined scope. on the one hand, it examines production planning for products in series production. on the other hand, only the tasks related to planning the production of such a product are analyzed. therefore, the control-based planning of orders, e.g. in production lots and production itself are not explicitly part of this recommendation. furthermore, as far as logistics are concerned, only internal logistics will be examined. external logistics as well as supply chain management will be dealt with, as appropriate, in the further work performed by the prostep ivip digital manufacturing project group.

in this recommendation, the reference process for production planning has been broken down in two ways, according to phases and planning discipline. on the one hand, the production planning process has been subdivided into the phases concept planning, rough planning, detailed planning and series planning according to the level of maturity of planning. in addition, the planning disciplines manufacturing planning, assembly planning, layout planning and logistics planning are examined in each phase. this results in a matrix of corresponding detailed sub-processes for the entire reference process. . important impulses are related to works which started at daimler and found their final documentation within the doctoral thesis of dr. mathias engel at the steinbeis university berlin (cp. engel). in this recommendation, these sub-processes are defined with the generally possible process steps, irrespective of functional or organizational constraints, and together constitute the reference process for production planning.

to illustrate how this type of reference process should be used in practice, typical use cases are described by way of example.

compared with version 2.0, some minor editorial changes were carried out, which let to the publication of this version 2.0.1.

sprache: en format: pdf (94 seiten)

---

PSI 8 - Digital Manufacturing

42 start standards prostep ivip alle 3 2013 plim en psi 8 - digital manufacturing recommendation for production planning processes

in the product creation process, production planning is perhaps the most important process, second only to product development. however, software-based support for production planning at companies currently takes place against the background of established structures and the fulfillment of location-specific requirements using what is frequently a number of different digital tools. this gives rise to an extremely heterogeneous environment as far as planning tools are concerned. this heterogeneity is also reflected in the planning processes themselves and hinders end-to-end planning. in particular, it makes cross-location planning, the comparison of planning results and the exchange between different planning disciplines and planning departments very difficult. a reference process for production planning is required to ensure end-to-end planning and the harmonization of multiple planning processes.

the creation of just such a reference planning process for production planning is the aim of this psi recommendation. for the purpose of defining this reference process, the production planning is first of all placed in the context of the product creation process. production planning starts shortly after the initial idea for a product using initial input from product development and runs in parallel with product development to a point well beyond the start of production. a further look is also taken at production planningrelated tasks required for series planning during manufacturing and assembly.

the reference process discussed in this recommendation has a strictly defined scope. on the one hand, it examines production planning for products in series production. on the other hand, only the tasks related to planning the production of such a product are analyzed. therefore, the control-based planning of orders, e.g. in production lots and production itself are not explicitly part of this recommendation. furthermore, as far as logistics are concerned, only internal logistics will be examined. external logistics as well as supply chain management will be dealt with, as appropriate, in the further work performed by the prostep ivip digital manufacturing project group.

in this recommendation, the reference process for production planning has been broken down in two ways, according to phases and planning discipline. on the one hand, the production planning process has been subdivided into the phases concept planning, rough planning, detailed planning and series planning according to the level of maturity of planning. in addition, the planning disciplines manufacturing planning, assembly planning, layout planning and logistics planning are examined in each phase. this results in a matrix of corresponding detailed sub-processes for the entire reference process. . important impulses are related to works which started at daimler and found their final documentation within the doctoral thesis of dr. mathias engel at the steinbeis university berlin (cp. engel). in this recommendation, these sub-processes are defined with the generally possible process steps, irrespective of functional or organizational constraints, and together constitute the reference process for production planning.

to illustrate how this type of reference process should be used in practice, typical use cases are described by way of example.

compared with version 2.0, some minor editorial changes were carried out, which let to the publication of this version 2.0.1.

language: en format: pdf (94 pages)

PSI 9 - C3I

45 start standards prostep ivip alle 6 2012 en psi 9 - c3i simulation data management in integrated collaborative cad / cae process chains

based on the recommendation for the integration of simulation and computation data in a product data management environment (simpdm), which was published at the end of 2008 by the prostep ivip association and vda, the document in hand aims to apply the simpdm results to user scenarios, focusing in particular on collaborative and cae/cad integration.

with this purpose in mind, the c³i recommendation defines processes, relations and use cases which fulfill the requirements regarding communication and integration. this covers cross-enterprise and cross-domain scenarios as well as the interaction between authoring tools and data management systems. the recommendation also gives standardized definitions of cae process modules and simulation data management (sdm) core functionalities. in order to enable system support, the recommendation also defines a general metadata model and describes possible system extensions. the metadata model is designed in a modular way to allow custom tailoring of solutions, and a mapping to existing data formats is given to illustrate how established interfaces can be extended to fulfill the requirements described in this recommendation. at the end of this document, descriptions of proof-of-concept implementations and the resulting experience are given.

the recommendation does not define an interchange format between different cae applications.

the recommendation consists of several documents:
the main recommendation document (the document in hand)
annex a: c³i metadata model
annex b: mapping of the c³i metadata model to other formats
annex c: tabular description of the c³i plug-in

the annexes a, b, c are available for download as separate documents at the websites of the prostep ivip association (www.prostep.org) and vda (www.vda.de).

language: en format: pdf (130 pages)

---

PSI 9 - C3I

45 start standards prostep ivip alle 6 2012 en psi 9 - c3i simulation data management in integrated collaborative cad / cae process chains

based on the recommendation for the integration of simulation and computation data in a product data management environment (simpdm), which was published at the end of 2008 by the prostep ivip association and vda, the document in hand aims to apply the simpdm results to user scenarios, focusing in particular on collaborative and cae/cad integration.

with this purpose in mind, the c³i recommendation defines processes, relations and use cases which fulfill the requirements regarding communication and integration. this covers cross-enterprise and cross-domain scenarios as well as the interaction between authoring tools and data management systems. the recommendation also gives standardized definitions of cae process modules and simulation data management (sdm) core functionalities. in order to enable system support, the recommendation also defines a general metadata model and describes possible system extensions. the metadata model is designed in a modular way to allow custom tailoring of solutions, and a mapping to existing data formats is given to illustrate how established interfaces can be extended to fulfill the requirements described in this recommendation. at the end of this document, descriptions of proof-of-concept implementations and the resulting experience are given.

the recommendation does not define an interchange format between different cae applications.

the recommendation consists of several documents:
the main recommendation document (the document in hand)
annex a: c³i metadata model
annex b: mapping of the c³i metadata model to other formats
annex c: tabular description of the c³i plug-in

the annexes a, b, c are available for download as separate documents at the websites of the prostep ivip association (www.prostep.org) and vda (www.vda.de).

sprache: en format: pdf (130 seiten)

PSI 9 - C3I - Annex A

44 start standards prostepivip mitglied 7 2012 en psi 9 - c3i - annex a datamodel language: en format: zip file

---

PSI 9 - C3I - Annex A

44 start standards prostepivip mitglied 7 2012 en psi 9 - c3i - annex a datamodel sprache: en format: zip-datei

PSI 9 - C3I - Annex B

43 start standards prostepivip mitglied 13 12 2011 en psi 9 - c3i - annex b mapping

the c³i recommendation defines a metadata model for simulation data (see main document, section 11), which is an evolution of the simpdm metadata model published end of 2008. this data model was not designed to be a data exchange format, but as a formalized data scope definition. this made it possible to design the model with the flexibility needed to describe the required data structure independent from actual implementation methods and involved systems.

consequently, the question came up, in how far existing data formats, which are either standardized or widely used in the industry, can be used to transfer the data in scope of the c³i recommendation. the motivation for the work described in this annex was that such a mapping removes the need to define a data exchange format for the project group on the one hand, and the need to introduce this additional format and its associated interfaces into the it landscape of the user companies on the other hand.

in this annex, the wording “simpdm metadata model” refers to the data model as defined in the prostep ivip / vda recommendation “integration of simulation and computation in a pdm environment (simpdm)”, published in 2008 as psi 4 / vda 4967, annex e. the wording “c³i metadata model” refers to the evolved data model as defined in annex a of the recommendation in hand.

to reach the aims described above, the following approach was taken:

first, a list of all applicable formats was collected and analyzed. the candidate formats were provided by the project group members. these were then compared to the simpdm metadata model to see to what extend the investigated formats cover the simpdm scope. the resulting table can be found in section 2.

next, the target formats had to be selected from this initial list. the “big picture” shown in section 3 was used to position the various formats in relation to their respective domain. in the end, one format was selected for each of the three directions:

• simpdm to pdm (sdm/pdm synchronization)
• simpdm to cae (data management / authoring tool integration)
• simpdm to cat

the criteria for the decision included:

• simpdm scope coverage – the overlap should be as big as possible
• standardization – a standardized target format would maintain neutrality of implementations from specific tools
• propagation of use in industry – use of an established format removes the need to implement new interfaces
• similarity of data model design philosophy – basic concepts should be transferrable

as result, the chosen formats are:

• simpdm to pdm: siemens plmxml
• simpdm to cae: iso 10303-209 (step ap209)
• simpdm to cat: asam ods

the finally selected formats had to undergo a technical analysis, which showed in detail their similarities and differences compared to the simpdm metadata model. the results are described in section 4.

over the course of the c³i project, as a result of the work done on collaborative and cad/cae integration use cases as well as workflow and change management, the simpdm metadata model was improved and extended, and thus evolved to become the c³i metadata model. wherever changes had to be made, the selected target formats were polled to see if similar data structures already existed and could be incorporated.

as the final step, after work on the c³i data model was completed, a detailed mapping was defined from c³i to the selected data formats for pdm (siemens plmxml) and cae (step ap 209). the intent of this unidirectional mapping is to show that in a scenario where plmxml or ap209 is already used to transfer data, how these formats can be used to convey the information required in the c³i processes and use cases, i.e. in which data object of the target format to store the data as defined in the c³i metadata model. the mapping tables can be found in section 6.

language: en format: zip file

---

PSI 9 - C3I - Annex B

43 start standards prostepivip mitglied 13 12 2011 en psi 9 - c3i - annex b mapping

the c³i recommendation defines a metadata model for simulation data (see main document, section 11), which is an evolution of the simpdm metadata model published end of 2008. this data model was not designed to be a data exchange format, but as a formalized data scope definition. this made it possible to design the model with the flexibility needed to describe the required data structure independent from actual implementation methods and involved systems.

consequently, the question came up, in how far existing data formats, which are either standardized or widely used in the industry, can be used to transfer the data in scope of the c³i recommendation. the motivation for the work described in this annex was that such a mapping removes the need to define a data exchange format for the project group on the one hand, and the need to introduce this additional format and its associated interfaces into the it landscape of the user companies on the other hand.

in this annex, the wording “simpdm metadata model” refers to the data model as defined in the prostep ivip / vda recommendation “integration of simulation and computation in a pdm environment (simpdm)”, published in 2008 as psi 4 / vda 4967, annex e. the wording “c³i metadata model” refers to the evolved data model as defined in annex a of the recommendation in hand.

to reach the aims described above, the following approach was taken:

first, a list of all applicable formats was collected and analyzed. the candidate formats were provided by the project group members. these were then compared to the simpdm metadata model to see to what extend the investigated formats cover the simpdm scope. the resulting table can be found in section 2.

next, the target formats had to be selected from this initial list. the “big picture” shown in section 3 was used to position the various formats in relation to their respective domain. in the end, one format was selected for each of the three directions:

• simpdm to pdm (sdm/pdm synchronization)
• simpdm to cae (data management / authoring tool integration)
• simpdm to cat

the criteria for the decision included:

• simpdm scope coverage – the overlap should be as big as possible
• standardization – a standardized target format would maintain neutrality of implementations from specific tools
• propagation of use in industry – use of an established format removes the need to implement new interfaces
• similarity of data model design philosophy – basic concepts should be transferrable

as result, the chosen formats are:

• simpdm to pdm: siemens plmxml
• simpdm to cae: iso 10303-209 (step ap209)
• simpdm to cat: asam ods

the finally selected formats had to undergo a technical analysis, which showed in detail their similarities and differences compared to the simpdm metadata model. the results are described in section 4.

over the course of the c³i project, as a result of the work done on collaborative and cad/cae integration use cases as well as workflow and change management, the simpdm metadata model was improved and extended, and thus evolved to become the c³i metadata model. wherever changes had to be made, the selected target formats were polled to see if similar data structures already existed and could be incorporated.

as the final step, after work on the c³i data model was completed, a detailed mapping was defined from c³i to the selected data formats for pdm (siemens plmxml) and cae (step ap 209). the intent of this unidirectional mapping is to show that in a scenario where plmxml or ap209 is already used to transfer data, how these formats can be used to convey the information required in the c³i processes and use cases, i.e. in which data object of the target format to store the data as defined in the c³i metadata model. the mapping tables can be found in section 6.

sprache: en format: zip-datei

White Paper: Strategiediskussion

186 start white-paper alle 01 9 2022 en white paper: strategiediskussion strategischen handlungsfeldern, auf denen der prostep ivip verein aktiv werden muss, um für die zukunft optimal aufgestellt zu sein. in diesem whitepaper betrachten wir drei der strategischen handlungsfelder, nämlich das image des vereins, seine zielgruppe und aktionsfeld und seine vision der digitalisierung. ausgehend von der beobachtung des umfelds und der definition der wesentlichen treiber für die digitale transformation wollen wir das künftige zielbild des vereins entwerfen und anschließend die maßnahmen für die umsetzung dieser ziele definieren. sprache: de & en format: pdf (12 seiten)

---

White Paper: Strategy Discussion

186 start white-paper alle 01 9 2022 en white paper: strategy discussion a range of strategic action areas in which the prostep ivip association must act in order to be optimally equipped for the future. in this white paper, we consider three of the strategic action areas, namely the association’s image, its target group and area of activity, and its vision of digitalization. based on observations of the current context and a definition of the main drivers of the digital transformation, we want to elaborate the association’s vision of the future before going on to indicate the measures necessary for the realization of these aims. language: en & de format: pdf (12 pages)

PSI 4 v2.0: Annex B - Business process diagrams

56 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex b - business process diagrams simulation data management for mbs, fem and cfd

the psi 4 version 2 recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b (this document): business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

language: en format: pdf (1 page)

---

PSI 4 v2.0: Annex B - Business process diagrams

56 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex b - business process diagrams simulationsdaten-management für mks, fem und cfd

the psi 4 version 2 recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b (this document): business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

sprache: en format: pdf (1 seite)

PSI 4 v2.0: Annex C - Core data management functionality

55 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex c - core data management functionality spezifikation der kerndatenmanagement-funktionalitäten von simpdm

this document is annex c of prostep ivip recommendation psi 4. this annex contains the technical description of simpdm core data management functionality.

the recommendation is intended to standardize the integration of simulation and computation data in a product data management environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a meta data model to describe simulation and computation data. the meta data model is modularly designed to allow a custom-tailored solution for simulation data management. furthermore this recommendation describes necessary functionality and its clustering towards use case. functionality and use cases are modular, too. so it is possible to customize simpdm to the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

sprache: en format: word-dokument (64 seiten)

---

PSI 4 v2.0: Annex C - Core data management functionality

55 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex c - core data management functionality technical description of simpdm core data management functionality

this document is annex c of prostep ivip recommendation psi 4. this annex contains the technical description of simpdm core data management functionality.

the recommendation is intended to standardize the integration of simulation and computation data in a product data management environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a meta data model to describe simulation and computation data. the meta data model is modularly designed to allow a custom-tailored solution for simulation data management. furthermore this recommendation describes necessary functionality and its clustering towards use case. functionality and use cases are modular, too. so it is possible to customize simpdm to the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

language: en format: word-document (64 pages)

PSI 4 v2.0: Annex D - System Communication functionality

54 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex d - system communication functionality spezifikation von kommunikations-mechanismen für simpdm

this document is annex d of prostep ivip recommendation psi 4. this annex contains the technical description of simpdm system communication functions.

the simpdm recommendation is intended to standardize the integration of simulation and computation data in a product data management environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a meta data model to describe simulation and computation data. the meta data model is modularly designed to allow a custom-tailored solution for simulation data management. furthermore this recommendation describes necessary functionality and its clustering towards use case. functionality and use cases are modular, too. so it is possible to customize simpdm to the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality
• annex d: system communication functionality (the document in hand)
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

sprache: en format: word-dokument (16 seiten)

---

PSI 4 v2.0: Annex D - System Communication functionality

54 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex d - system communication functionality technical description of simpdm system communication functions

this document is annex d of prostep ivip recommendation psi 4. this annex contains the technical description of simpdm system communication functions.

the simpdm recommendation is intended to standardize the integration of simulation and computation data in a product data management environment (pdm environment) in the form of simulation data management (sdm) and to define the communication processes between a simulation data management system (sdm system) and cae systems as well as between an sdm system and other data management systems within the pdm environment.

with this purpose in mind, the recommendation defines use cases and functional requirements for simulation data management and a meta data model to describe simulation and computation data. the meta data model is modularly designed to allow a custom-tailored solution for simulation data management. furthermore this recommendation describes necessary functionality and its clustering towards use case. functionality and use cases are modular, too. so it is possible to customize simpdm to the specific requirements of an enterprise.

the recommendation does not define an interchange data format between different cae applications.

the recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality
• annex d: system communication functionality (the document in hand)
• annex e: data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

language: en format: word-document (16 pages)

PSI 4 v2.0: Annex E - SimPDM Meta Data Model HTML

53 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex e - simpdm meta data model html simpdm meta data model dokumentation

simpdm meta data model v2 documentation 08-11-26

the psi 4 version 2 recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e (this document): data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

language: en format: zip file

---

PSI 4 v2.0: Annex E - SimPDM Meta Data Model HTML

53 standards prostepivip alle 11 2008 simpdm en psi 4 v2.0: annex e - simpdm meta data model html simpdm meta data model dokumentation

simpdm meta data model v2 documentation 08-11-26

the psi 4 version 2 recommendation consists of several documents:

• the main recommendation document
• annex a: glossary (included in the main document)
• annex b: business process diagrams (simulation data management for mbs, fem and cfd)
• annex c: core data management functionality (the document in hand)
• annex d: system communication functionality
• annex e (this document): data model

the annexes b, c, d, e are available for download as separated documents on the websites of prostep ivip e.v (www.prostep.org) and vda (www.vda.de).

sprache: en format: zip-datei

PSI 5 v2.0: Annex D

52 start standards prostepivip mitglied 11 2 2010 ecad-mcad en psi 5 v2.0: annex d conformance guidelines

the integration of mechanical and electrical components in mechatronic integrated products is becoming increasingly important. development takes place in separate domains using different cad tools (ecad and mcad). although powerful software tools are available on the market for the respective disciplines, support for existing processes and systems is reaching its functional limits with regard to collaboration between these systems. with increasing product complexity and the demand for shorter development cycles, there is a growing need for feasible solutions for sustainable collaboration on the basis the existing ecad and mcad systems.

this prostep ivip conformance guidelines describes the guideline for validation applications for being conform to ecad/mcad recommendation in the current valid version.

language: en format: pdf (16 pages)

---

PSI 5 v2.0: Annex D

52 start standards prostepivip mitglied 11 2 2010 ecad-mcad en psi 5 v2.0: annex d conformance guidelines

the integration of mechanical and electrical components in mechatronic integrated products is becoming increasingly important. development takes place in separate domains using different cad tools (ecad and mcad). although powerful software tools are available on the market for the respective disciplines, support for existing processes and systems is reaching its functional limits with regard to collaboration between these systems. with increasing product complexity and the demand for shorter development cycles, there is a growing need for feasible solutions for sustainable collaboration on the basis the existing ecad and mcad systems.

this prostep ivip conformance guidelines describes the guideline for validation applications for being conform to ecad/mcad recommendation in the current valid version.

sprache: en format: pdf (16 seiten)

PSI 7: ERM - Annex A

49 start standards prostepivip mitglied 04 5 2009 sp2 en psi 7: erm - annex a cross enterprise-id: solution outline

this document is annex a of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document recalls the background on identity management and sketches general solution strategies for the realization of a cross-enterprise identity management solutions.

language: en format: pdf (32 pages)

---

PSI 7: ERM - Annex A

49 start standards prostepivip mitglied 04 5 2009 sp2 en psi 7: erm - annex a cross enterprise-id: solution outline

this document is annex a of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document recalls the background on identity management and sketches general solution strategies for the realization of a cross-enterprise identity management solutions.

sprache: en format: pdf (32 seiten)

PSI 7: ERM - Annex B

48 start standards prostepivip mitglied 04 9 2009 sp2 en psi 7: erm - annex b cross enterprise-id: technical recommendation

this document is annex b of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document reviews existing standards and recommendations for single sign-on and provides a technical recommendation for the implementation of the federated identity management scenario.

language: en format: pdf (36 pages)

---

PSI 7: ERM - Annex B

48 start standards prostepivip mitglied 04 9 2009 sp2 en psi 7: erm - annex b cross enterprise-id: technical recommendation

this document is annex b of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document reviews existing standards and recommendations for single sign-on and provides a technical recommendation for the implementation of the federated identity management scenario.

sprache: en format: pdf (36 seiten)

PSI 7: ERM - Annex C

47 start standards prostepivip mitglied 14 8 2009 sp2 en psi 7: erm - annex c reference processes

this document is annex c of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document presents an overview of the reference workflows.

language: en format: pdf (11 pages)

---

PSI 7: ERM - Annex C

47 start standards prostepivip mitglied 14 8 2009 sp2 en psi 7: erm - annex c reference processes

this document is annex c of prostep ivip recommendation psi 7, which provides recommendations for the adoption of erm technology for the implementation of secure data exchange processes. the present document presents an overview of the reference workflows.

sprache: en format: pdf (11 seiten)

707 start alle en de 2025 5 6 as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. 

as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. for oems, the digital integration of suppliers is one particularly powerful way of making complex planning activities both efficient and manageable. digital support provided by effective, efficient project management (pm) tools and methods can make an important contribution here.

 

zip mit 4 dateien 
enthält:
psi_25_psms_recommendation_v20_en_aw
psi_25_anhang a
psi_25_anhang b
psi_25_anhang c psm synchronization in collaboration networks as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. for oems, the digital integration of suppliers is one particularly powerful way of making complex planning activities both efficient and manageable. digital support provided by effective, efficient project management (pm) tools and methods can make an important contribution here.

---

As products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. For OEMs, the digital integration of suppliers is one particularly

707 start alle en de 2025 5 6

as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. for oems, the digital integration of suppliers is one particularly powerful way of making complex planning activities both efficient and manageable. digital support provided by effective, efficient project management (pm) tools and methods can make an important contribution here.

as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. 

as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. for oems, the digital integration of suppliers is one particularly powerful way of making complex planning activities both efficient and manageable. digital support provided by effective, efficient project management (pm) tools and methods can make an important contribution here.

 

zip width 4 files - containing:
psi_25_psms_recommendation_v20_en_aw
psi_25_anhang a
psi_25_anhang b
psi_25_anhang c psm synchronization in collaboration networks as products become increasingly complex, the requirements placed on project development and production projects as well as maintenance and service projects are also growing. for oems, the digital integration of suppliers is one particularly powerful way of making complex planning activities both efficient and manageable. digital support provided by effective, efficient project management (pm) tools and methods can make an important contribution here.

ReqIF Benchmark 2021/2022 - Long Report

177 start benchmark mitglied 23 12 2022 en reqif benchmark 2021/2022 - long report

requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum.

language: en format: pdf (73 pages)

---

ReqIF Benchmark 2021/2022 - Long Report

177 start benchmark mitglied 23 12 2022 en reqif benchmark 2021/2022 - long report

requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum.

sprache: en format: pdf (73 seiten)

ReqIF Benchmark No. 5 2023 - Long Report

680 start benchmark 3 mitglied de 2023 reqif reqif benchmark no. 5 2023 - long report requirements management (rm) has been established to ensure seamless specifications throughout the
product creation process. to manage complex specification processes and requirements dependencies,
companies introduced requirements management systems (rm-systems). the generic „requirement
interchange format (rif)” was created to enable the exchange of information across different rm-systems.
in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum. sprache: en format: pdf (92 seiten)

---

ReqIF Benchmark No. 5 2023 - Long Report

680 start benchmark 3 mitglied de 2023 reqif reqif benchmark no. 5 2023 - long report requirements management (rm) has been established to ensure seamless specifications throughout the
product creation process. to manage complex specification processes and requirements dependencies,
companies introduced requirements management systems (rm-systems). the generic „requirement
interchange format (rif)” was created to enable the exchange of information across different rm-systems.
in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum. language: en format: pdf (92 pages)

ReqIF Benchmark No. 5 2023 - Short Report

681 start benchmark en 3 2024 alle reqif reqif benchmark no. 5 2023 - short report

requirements management (rm) has been established to ensure seamless specifications throughout the product creation process. to manage complex specification processes and requirements dependencies, companies introduced requirements management systems (rm-systems). 

longreport available for members only

 

language: en format: pdf (55 pages) short version - longreport available for members only

---

ReqIF Benchmark No. 5 2023 - Short Report

681 start benchmark en 3 2024 alle reqif reqif benchmark no. 5 2023 - short report

requirements management (rm) has been established to ensure seamless specifications throughout the product creation process. to manage complex specification processes and requirements dependencies, companies introduced requirements management systems (rm-systems). 

longreport available for members only

 

sprache: en format: pdf (55 seiten) short version - longreport available for members only

ReqIF Benchmark No. 6 2024
Short Report

692 start alle en de 9 benchmark 2025 4 reqif benchmark no. 6 2024
short report reqif benchmark no. 6 2024
short report requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems (rm-systems). 

requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems (rm-systems). the generic „requirement interchange format (rif)” was created to enable the exchange of information across different rm-systems.

pdf 64 pages

---

ReqIF Benchmark No. 6 2024
Short Report

692 start alle en de 9 benchmark 2025 4 reqif benchmark no. 6 2024
short report requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems (rm-systems).  requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems (rm-systems). the generic „requirement interchange format (rif)” was created to enable the exchange of information across different rm-systems. pdf 64 seiten reqif benchmark no. 6 2024
short report

187 start implementationguidelines alle 12 reqif en 2024 reqif implementor forum

reqif implementation guideline referring to omg reqif1.2

this specification is an additional, informal document concerning the omg reqif1.2 standard.
it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

language: en format: pdf (36 pages)

---

187 start implementationguidelines alle 12 reqif en 2024 reqif implementor forum

reqif implementation guideline referring to omg reqif1.2

this specification is an additional, informal document concerning the omg reqif1.2 standard.
it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations. sprache: en format: pdf (36 seiten)

ReqIF Benchmark 2018 - Long Report

153 start benchmark mitglied 22 2 2019 reqif en reqif benchmark 2018 - long report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif in order to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing strong technological basis. in 2016 the community of relevant user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, the two groups decided to perform a benchmark. focus of this benchmark is the exchange of formatted content and embedded objects in a requirement specification. the benchmark was run at prostep ivip site with support of the 6 participating vendors. the criteria and test data were defined by the users. this is the first attempt by prostep ivip and vda on a neutral evaluation of the reqif data exchange with multiple requirement management systems and connector tools.

advanced functionalities and use cases may be tested in planned upcoming benchmarks.

language: en format: pdf (26 pages)

---

ReqIF Benchmark 2018 - Long Report

153 start benchmark mitglied 22 2 2019 reqif en reqif benchmark 2018 - long report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif in order to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing strong technological basis. in 2016 the community of relevant user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, the two groups decided to perform a benchmark. focus of this benchmark is the exchange of formatted content and embedded objects in a requirement specification. the benchmark was run at prostep ivip site with support of the 6 participating vendors. the criteria and test data were defined by the users. this is the first attempt by prostep ivip and vda on a neutral evaluation of the reqif data exchange with multiple requirement management systems and connector tools.

advanced functionalities and use cases may be tested in planned upcoming benchmarks.

sprache: en format: pdf (26 seiten)

ReqIF Benchmark 2019 - Long Report

151 start benchmark mitglied 21 12 2019 reqif en reqif benchmark 2019 - long report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif in order to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing strong technological basis. in 2016 the community of relevant user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the first benchmark was well received by the users and implementers, as it provided valuable information for the usage and further development of requirement management tools. in this second benchmark, the tested scenario is a simple roundtrip without changes to the specification structure by customer or supplier. the benchmark was run at prostep ivip site with support of the 6 participating vendors. the criteria and test data were defined by the users.

language: en format: pdf (35 pages)

---

ReqIF Benchmark 2019 - Long Report

151 start benchmark mitglied 21 12 2019 reqif en reqif benchmark 2019 - long report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif in order to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing strong technological basis. in 2016 the community of relevant user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the first benchmark was well received by the users and implementers, as it provided valuable information for the usage and further development of requirement management tools. in this second benchmark, the tested scenario is a simple roundtrip without changes to the specification structure by customer or supplier. the benchmark was run at prostep ivip site with support of the 6 participating vendors. the criteria and test data were defined by the users.

sprache: en format: pdf (35 seiten)

ReqIF Benchmark 2020 - Long Report

148 start benchmark mitglied 30 11 2020 reqif en reqif benchmark 2020 - long report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this third benchmark, the tested scenario is a customer/supplier data exchange with updates on customer side. the benchmark was run at prostep ivip site with support of the participating vendors. the criteria and test data were defined by the users.

language: en format: pdf (30 pages)

---

ReqIF Benchmark 2020 - Long Report

148 start benchmark mitglied 30 11 2020 reqif en reqif benchmark 2020 - long report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this third benchmark, the tested scenario is a customer/supplier data exchange with updates on customer side. the benchmark was run at prostep ivip site with support of the participating vendors. the criteria and test data were defined by the users.

sprache: en format: pdf (30 seiten)

ReqIF Benchmark 2018 - Short Report

154 benchmark alle 2 2019 reqif en reqif benchmark 2018 - short report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies, companies introduced requirements management systems.

to support a proper requirements exchange between partners using different tools, the project group «simulation and tools» of the his (hersteller initiative software) specified the generic „requirement interchange format (rif)“.

in summer 2008, the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011, omg reqif 1.0.1 has been published as the official successor of rif.

prostep ivip established two project groups to further drive the reqif format:
the goal of the reqif implementor forum is to ensure interoperability between different reqif-based implementations. therefore, the reqif-if works very tightly together with the newly established reqif workflow forum.

in 2016, the community of relevant user representatives consequently made the next step: specifying relevant use cases for reqif application in industry.

thus, mayor aim of the prostep ivip / vda reqif-wf is to specify use cases as well as reference processes (oem-oem, oem-supplier etc.) and, related to this, deriving process requirements and test cases. the work is performed in close collaboration with the reqif implementor forum.

to prove the applicability of the reqif format, the project groups have decided to perform benchmarks. the first benchmark in 2018 focused on basic functionalities. advanced functionalities may be tested in upcoming benchmarks. goal of the benchmarks is a neutral evaluation of the current capabilities in requirement data exchange with reqif. additionally, issues that require further development of either the format itself or of the tested software tools will be identified and addressed.

language: en format: pdf (14 pages)

---

ReqIF Benchmark 2018 - Short Report

154 benchmark alle 2 2019 reqif en reqif benchmark 2018 - short report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies, companies introduced requirements management systems.

to support a proper requirements exchange between partners using different tools, the project group «simulation and tools» of the his (hersteller initiative software) specified the generic „requirement interchange format (rif)“.

in summer 2008, the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011, omg reqif 1.0.1 has been published as the official successor of rif.

prostep ivip established two project groups to further drive the reqif format:
the goal of the reqif implementor forum is to ensure interoperability between different reqif-based implementations. therefore, the reqif-if works very tightly together with the newly established reqif workflow forum.

in 2016, the community of relevant user representatives consequently made the next step: specifying relevant use cases for reqif application in industry.

thus, mayor aim of the prostep ivip / vda reqif-wf is to specify use cases as well as reference processes (oem-oem, oem-supplier etc.) and, related to this, deriving process requirements and test cases. the work is performed in close collaboration with the reqif implementor forum.

to prove the applicability of the reqif format, the project groups have decided to perform benchmarks. the first benchmark in 2018 focused on basic functionalities. advanced functionalities may be tested in upcoming benchmarks. goal of the benchmarks is a neutral evaluation of the current capabilities in requirement data exchange with reqif. additionally, issues that require further development of either the format itself or of the tested software tools will be identified and addressed.

sprache: en format: pdf (14 seiten)

ReqIF Benchmark 2019 - Short Report

152 benchmark alle 12 2019 reqif en reqif benchmark 2019 - short report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems.

to support a proper requirements exchange between partners using different tools, the project group "simulation and tools" of the his (hersteller initiative software) specified the generic „requirement interchange format (rif)”.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

prostep ivip established two project groups to further drive the reqif format:

the goal of the reqif implementor forum is to ensure interoperability between different reqif-based implementations. therefore, the reqif-if works very tight together with the newly established reqif workflow forum.

in 2016, the community of relevant user representatives consequently made the next step: specifying relevant use cases for reqif application in industry.

thus, mayor aim of the prostep ivip / vda reqif-wf is to specify use cases as well as reference processes (customer-customer, customer-supplier etc.) and, related to this, deriving process requirements and test cases. the work is performed in close collaboration with the reqif implementor forum.

to prove the applicability of the reqif format, the project groups have decided to perform benchmarks. the first benchmark in 2018 focused on basic functionalities. the first benchmark was well received by the users and implementers, as it provided valuable information for the usage and further development of requirement management tools.

in this second benchmark, the tested scenario is a simple roundtrip without changes to the specification structure by customer or supplier. goal of the benchmarks is a neutral evaluation of the current capabilities in requirement data exchange with reqif. additionally, issues that require further development of either the format itself or of the tested software tools will be identified and addressed.

language: en format: pdf (14 pages)

---

ReqIF Benchmark 2019 - Short Report

152 benchmark alle 12 2019 reqif en reqif benchmark 2019 - short report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. in order to manage complex specification processes and requirements dependencies companies introduced requirements management systems.

to support a proper requirements exchange between partners using different tools, the project group "simulation and tools" of the his (hersteller initiative software) specified the generic „requirement interchange format (rif)”.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

prostep ivip established two project groups to further drive the reqif format:

the goal of the reqif implementor forum is to ensure interoperability between different reqif-based implementations. therefore, the reqif-if works very tight together with the newly established reqif workflow forum.

in 2016, the community of relevant user representatives consequently made the next step: specifying relevant use cases for reqif application in industry.

thus, mayor aim of the prostep ivip / vda reqif-wf is to specify use cases as well as reference processes (customer-customer, customer-supplier etc.) and, related to this, deriving process requirements and test cases. the work is performed in close collaboration with the reqif implementor forum.

to prove the applicability of the reqif format, the project groups have decided to perform benchmarks. the first benchmark in 2018 focused on basic functionalities. the first benchmark was well received by the users and implementers, as it provided valuable information for the usage and further development of requirement management tools.

in this second benchmark, the tested scenario is a simple roundtrip without changes to the specification structure by customer or supplier. goal of the benchmarks is a neutral evaluation of the current capabilities in requirement data exchange with reqif. additionally, issues that require further development of either the format itself or of the tested software tools will be identified and addressed.

sprache: en format: pdf (14 seiten)

ReqIF Benchmark 2020 - Short Report

147 benchmark alle 30 11 2020 reqif en reqif benchmark 2020 - short report reqif application benchmark - comparative test of reqif applications

requirements management has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this third benchmark, the tested scenario is a customer/supplier data exchange with updates on customer side. the benchmark was run at prostep ivip site with support of the participating vendors. the criteria and test data were defined by the users.

language: en format: pdf (15 pages)

---

ReqIF Benchmark 2020 - Short Report

147 benchmark alle 30 11 2020 reqif en reqif benchmark 2020 - short report reqif applikation benchmark - vergleichtest von reqif-applikationen

requirements management has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this third benchmark, the tested scenario is a customer/supplier data exchange with updates on customer side. the benchmark was run at prostep ivip site with support of the participating vendors. the criteria and test data were defined by the users.

sprache: en format: pdf (15 seiten)

Implementation Guideline ReqIF

113 start guideline implementationguidelines alle 03 1 2017 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

language: en format: pdf (33 pages)

---

Implementation Guideline ReqIF

113 start guideline implementationguidelines alle 03 1 2017 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

sprache: en format: pdf (33 seiten)

Implementation Guideline ReqIF

110 start guideline implementationguidelines alle 13 12 2018 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

language: en format: pdf (33 pages)

---

Implementation Guideline ReqIF

110 start guideline implementationguidelines alle 13 12 2018 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

sprache: en format: pdf (33 seiten)

Implementation Guideline ReqIF

109 guideline implementationguidelines alle 16 12 2019 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

language: en format: pdf (33 pages)

---

Implementation Guideline ReqIF

109 guideline implementationguidelines alle 16 12 2019 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

sprache: en format: pdf (33 seiten)

Implementation Guideline ReqIF

107 guideline implementationguidelines alle 22 12 2021 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

language: en format: pdf (34 pages)

---

Implementation Guideline ReqIF

107 guideline implementationguidelines alle 22 12 2021 reqif en implementation guideline reqif implementation guideline for reqif

this specification is an additional, informal document concerning the omg reqif1.2 standard.

it answers implementation specific questions that have intentionally been left out of the omg reqif standard because they do not directly concern the exchange format but may be relevant for tool implementations.

sprache: en format: pdf (34 seiten)

ReqIF tool notes

114 start guideline implementationguidelines mitglied 06 11 2015 reqif en reqif tool notes points to note about reqif exchange using reqif tools

this document describes peculiarities of reqif tools.

it is based solely on information provided by the implementers of these tools to the prostep reqif implementor forum.

it is intended to be read by

employees of companies using or planning to use one of the mentioned tools, in order to get informed about the tools, or

anybody else interested in the peculiarities of the reqif tools in practice.

language: en format: pdf (15 pages)

---

ReqIF tool notes

114 start guideline implementationguidelines mitglied 06 11 2015 reqif en reqif tool notes points to note about reqif exchange using reqif tools

this document describes peculiarities of reqif tools.

it is based solely on information provided by the implementers of these tools to the prostep reqif implementor forum.

it is intended to be read by

employees of companies using or planning to use one of the mentioned tools, in order to get informed about the tools, or

anybody else interested in the peculiarities of the reqif tools in practice.

sprache: en format: pdf (15 seiten)

Implementation Guideline for ReqIF Use Case SRC

106 guideline implementationguidelines alle 11 2 2022 reqif en implementation guideline for reqif use case src implementation guideline for reqif use case stakeholder request clarification (src): a set of minimum requirements

this document describes a minimal exchange process for requirements specifications between 2 exchange partners, to clarify stakeholder requests. the partners exchange the specifications by exporting and importing them in the omg reqif xml format (https://www.omg.org/spec/reqif/).

language: en format: pdf (9 pages)

---

Implementation Guideline for ReqIF Use Case SRC

106 guideline implementationguidelines alle 11 2 2022 reqif en implementation guideline for reqif use case src implementation guideline for reqif use case stakeholder request clarification (src): a set of minimum requirements

this document describes a minimal exchange process for requirements specifications between 2 exchange partners, to clarify stakeholder requests. the partners exchange the specifications by exporting and importing them in the omg reqif xml format (https://www.omg.org/spec/reqif/).

sprache: en format: pdf (9 seiten)

683 start benchmark en alle reqif 1 2025 reqlf benchmark files this zip-files contains a documentation concerning the reqif benchmark activities, describing what kind of reference files are used for the reqif benchmark and how they can be used for own tests. and in addition, it contains the actual prostep ivip reqif bm files, that have been used. language: en format: zip reqlf benchmark files

---

This ZIP-files contains a documentation concerning the ReqIF benchmark activities, describing what kind of reference files are used for the ReqIF Benchmark and how they can be used for own tests. And in addition, it contains the actual prostep ivip

683 start benchmark en alle reqif 1 2025 this zip-files contains a documentation concerning the reqif benchmark activities, describing what kind of reference files are used for the reqif benchmark and how they can be used for own tests. and in addition, it contains the actual prostep ivip reqif bm files, that have been used. this zip-files contains a documentation concerning the reqif benchmark activities, describing what kind of reference files are used for the reqif benchmark and how they can be used for own tests. and in addition, it contains the actual prostep ivip reqif bm files, that have been used. sprache: en format: zip reqlf benchmark files

ReqIF Benchmark 2021/2022 - Short Report

178 benchmark stepbenchmark alle 23 12 2022 en reqif benchmark 2021/2022 - short report

requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum.

language: en format: pdf (40 pages)

---

ReqIF Benchmark 2021/2022 - Short Report

178 benchmark stepbenchmark alle 23 12 2022 en reqif benchmark 2021/2022 - short report

requirements management (rm) has been established to ensure seamless specifications along the product creation process. to manage complex specification processes and requirements dependencies companies introduced requirements management systems. the generic „requirement interchange format (rif)” was created to enable the exchange of information across different requirements management systems.

in summer 2008 the prostep ivip association initiated the project group intrif to increase the acceptance and application of rif by transferring the recommendation into an international standard. with the successful standardization in april 2011 omg reqif 1.0.1 has been published as the official successor of rif.

two project groups are currently working on the enhancement of the format and its application. in 2011 the reqif implementor forum was established for realizing a strong technological basis. in 2016 the community of user representatives then consequently made the next step: specifying relevant use cases for reqif application in industry.

to evaluate the feasibility of requirement data exchange with reqif, benchmarks are conducted, the very first in 2018. the benchmarks were well received by the users and implementers, as they provided valuable information for the usage and further development of requirement management tools. in this fourth benchmark, the tested scenario is a customer/supplier data exchange with comments on supplier and updates on customer side. with 6 participating software providers, there were a total of 9 participating rm-systems and connectors that were tested in 72 different tool combinations. the benchmark was run at prostep ivip site with support of the participating software providers. the criteria and test data were defined by the reqif workflow forum.

sprache: en format: pdf (40 seiten)

Studie Digital Manufacturing

81 start white-paper mitglied 08 5 2015 plim en de studie digital manufacturing ergebnisse studie digital manufacturing

im produktentstehungsprozess ist die produktionsplanung nach der produktentwicklung der wohl wichtigste prozess. die softwaretechnische unterstützung der produktionsplanung in den unternehmen erfolgt derzeit jedoch vor dem hintergrund gewachsener strukturen und der erfüllung standortspezifischer anforderungen durch eine vielzahl oft unterschiedlicher digitaler werkzeuge. dies führt zu einer sehr heterogenen planungslandschaft. diese heterogenität spiegelt sich auch in den planungsprozessen selbst wider und erschwert eine durchgängige planung. sie erschwert insbesondere die standortübergreifende planung, den vergleich von planungsergebnissen und den austausch zwischen verschiedenen planungsdisziplinen und planungsabteilungen. dies sind die ergebnisse einer studie mit identifizierten hot spots und handlungsempfehlungen für digital manufacturing.

sprache: de & en format: zip-datei

---

Study Digital Manufacturing

81 start white-paper mitglied 08 5 2015 plim en de study digital manufacturing results study digital manufacturing

in the product creation process, production planning is perhaps the most important process, second only to product development. however, software-based support for production planning at companies currently takes place against the background of established structures and the fulfillment of location-specific requirements using what is frequently a number of different digital tools. this gives rise to an extremely heterogeneous environment as far as planning tools are concerned. this heterogeneity is also reflected in the planning processes themselves and hinders end-to-end planning. in particular, it makes cross-location planning, the comparison of planning results and the exchange between different planning disciplines and planning departments very difficult. this are the results of a study with hot spots and recommendations for digital manufacturing.

language: en & de format: zip file

Mechatronic Process Integration (MPI)

173 start final-report mitglied 09 3 2009 step en mechatronic process integration (mpi) feldstudie zu "mechatronische produktentwicklungsprozesse heute"

mechatronic products have become very common nowadays. most product innovations are a result of the powerful possibilities offered by electric/electronic and/or software components. as product complexity increases, so, too, does the complexity of mechatronic product development. all three disciplines – mechanics, electrics/electronics, and software - have to be integrated, thus resulting in very complex processes and a wide array of challenges.

the prostep ivip field study “mechatronic process integration (mpi)” was conducted in order to identify these challenges and areas of potential difficulty. in 10 interviews, representatives from 5 different companies active in the automotive industry were asked to answer a set of key questions designed to identify the challenges they face in the field of mechatronic product development. the interview partners were: continental (including former siemens vdo), delphi, johnson controls, küster, zf sachs.

the key questions, the majority of which originate from the bestvor research project, were grouped together into three areas covering mechatronic product development, project management, and quality management as well as quality assurance. the area of “mechatronic product development” covers requirements management, problem solution, and mechatronic product design. the “project management” area covers the topics project management, resource management, project progress tracking, and collaboration between the three disciplines. “quality management and assurance” focused on quality assurance, error handling, versioning control, quality of supplier products, and stage of maturity of processes.

this document describes and discusses the results of the field study. it leads to a set of required actions that are closely related. these include supplier integration, requirements management, change management, and engineering traceability management. the latter reveals the integral character of these topics. one major finding was that within mechatronic product development, monitoring functionalities are required in order to monitor the level of product maturity throughout the entire product development process. such functionalities could be beneficial in particular with regard to the reduction of warranty costs.

sprache: en format: pdf (23 seiten)

---

Mechatronic Process Integration (MPI)

173 start final-report mitglied 09 3 2009 step en mechatronic process integration (mpi) field study covering "mechatronic product development processes today"

mechatronic products have become very common nowadays. most product innovations are a result of the powerful possibilities offered by electric/electronic and/or software components. as product complexity increases, so, too, does the complexity of mechatronic product development. all three disciplines – mechanics, electrics/electronics, and software - have to be integrated, thus resulting in very complex processes and a wide array of challenges.

the prostep ivip field study “mechatronic process integration (mpi)” was conducted in order to identify these challenges and areas of potential difficulty. in 10 interviews, representatives from 5 different companies active in the automotive industry were asked to answer a set of key questions designed to identify the challenges they face in the field of mechatronic product development. the interview partners were: continental (including former siemens vdo), delphi, johnson controls, küster, zf sachs.

the key questions, the majority of which originate from the bestvor research project, were grouped together into three areas covering mechatronic product development, project management, and quality management as well as quality assurance. the area of “mechatronic product development” covers requirements management, problem solution, and mechatronic product design. the “project management” area covers the topics project management, resource management, project progress tracking, and collaboration between the three disciplines. “quality management and assurance” focused on quality assurance, error handling, versioning control, quality of supplier products, and stage of maturity of processes.

this document describes and discusses the results of the field study. it leads to a set of required actions that are closely related. these include supplier integration, requirements management, change management, and engineering traceability management. the latter reveals the integral character of these topics. one major finding was that within mechatronic product development, monitoring functionalities are required in order to monitor the level of product maturity throughout the entire product development process. such functionalities could be beneficial in particular with regard to the reduction of warranty costs.

language: en format: pdf (23 pages)

SASIG ECM Recommendation - Part 0 ECM

62 standards sasig alle 1 2010 en sasig ecm recommendation - part 0 ecm part 0: engineering change management (ecm); overview general recommendations for the overall ecm reference process

the objective of this recommendation is to provide support for ecm processes with respect to the communication of change data between customers and suppliers. use of the recommendation allows more efficient integration of all the partners involved in a proposed change as a result of:

• a reduction in the variety of communications methods used in the partner network
• a reduction in the throughput time for a proposed change
• improvements in the quality and reliability of the process
• improvement with respect to the transparency of changes for all those involved
• the reusability of process agreements, interfaces and tools

the recommendation is subdivided into individual parts reflecting the ecm reference subprocess involved during the course of a change; this subdivision is subject to change as a result of further developments

this document gives an overview of and offers general recommendations for the overall ecm reference process, its modelling and a partner model. it describes fundamentals and basic recommendations valid for each ecm reference sub-process.

language: en format: pdf (155 pages)

---

SASIG ECM Recommendation - Part 0 ECM

62 standards sasig alle 1 2010 en sasig ecm recommendation - part 0 ecm part 0: engineering change management (ecm); overview general recommendations for the overall ecm reference process

the objective of this recommendation is to provide support for ecm processes with respect to the communication of change data between customers and suppliers. use of the recommendation allows more efficient integration of all the partners involved in a proposed change as a result of:

• a reduction in the variety of communications methods used in the partner network
• a reduction in the throughput time for a proposed change
• improvements in the quality and reliability of the process
• improvement with respect to the transparency of changes for all those involved
• the reusability of process agreements, interfaces and tools

the recommendation is subdivided into individual parts reflecting the ecm reference subprocess involved during the course of a change; this subdivision is subject to change as a result of further developments

this document gives an overview of and offers general recommendations for the overall ecm reference process, its modelling and a partner model. it describes fundamentals and basic recommendations valid for each ecm reference sub-process.

sprache: en format: pdf (155 seiten)

SASIG ECM Recommendation - Part 1 ECR

61 standards sasig alle 1 2010 en sasig ecm recommendation - part 1 ecr part 1: engineering change request (ecr); ecm reference sub-process used to communicate engineering change request (ecr)

the objective of this recommendation is to provide support for ecm processes with respect to the communication of change data between customers and suppliers. use of the recommendation allows more efficient integration of all the partners involved in a proposed change as a result of:

• a reduction in the variety of communications methods used in the partner network
• a reduction in the throughput time for a proposed change
• improvements in the quality and reliability of the process
• improvement with respect to the transparency of changes for all those involved
• the reusability of process agreements, interfaces and tools

the recommendation is subdivided into individual parts reflecting the ecm reference subprocess involved during the course of a change; this subdivision is subject to change as a result of further developments

part 1: ecr – specification and decision on change

part 1 offers recommendations with respect to communicating engineering change request (ecr) data to support the specification of proposed changes and the associated decisions. it describes the ecr reference process which permits synchronization of the different internal procedures of the partners involved using ecr messages. it offers recommendations for permitted sequences of ecr messages to provide support for business-typical ecr interaction scenarios (is) within the scope of bilateral communication between the cooperation partners and recommendations with respect to the minimum requirements applicable to communication and message content. the change data contained in the individual communication steps is described in the ecr data model.

language: en format: pdf (97 pages)

---

SASIG ECM Recommendation - Part 1 ECR

61 standards sasig alle 1 2010 en sasig ecm recommendation - part 1 ecr part 1: engineering change request (ecr); ecm reference sub-process used to communicate engineering change request (ecr)

the objective of this recommendation is to provide support for ecm processes with respect to the communication of change data between customers and suppliers. use of the recommendation allows more efficient integration of all the partners involved in a proposed change as a result of:

• a reduction in the variety of communications methods used in the partner network
• a reduction in the throughput time for a proposed change
• improvements in the quality and reliability of the process
• improvement with respect to the transparency of changes for all those involved
• the reusability of process agreements, interfaces and tools

the recommendation is subdivided into individual parts reflecting the ecm reference subprocess involved during the course of a change; this subdivision is subject to change as a result of further developments

part 1: ecr – specification and decision on change

part 1 offers recommendations with respect to communicating engineering change request (ecr) data to support the specification of proposed changes and the associated decisions. it describes the ecr reference process which permits synchronization of the different internal procedures of the partners involved using ecr messages. it offers recommendations for permitted sequences of ecr messages to provide support for business-typical ecr interaction scenarios (is) within the scope of bilateral communication between the cooperation partners and recommendations with respect to the minimum requirements applicable to communication and message content. the change data contained in the individual communication steps is described in the ecr data model.

sprache: en format: pdf (97 seiten)

SimPDM Implementation Guideline

119 start guideline implementationguidelines mitglied 15 1 2008 simpdm en simpdm implementation guideline implementation guideline for simpdm 2.0 (psi 4 / vda 4967)

this implementation guideline accompanies the prostep ivip psi 4 / vda 4967 recommendation, version 2.0.

it aims for a better understanding on technical level of the simpdm results. target audience are those who implement simpdm.

this document contains several annotated examples how simpdm works. it is structured like the recommendations main document. it is intended to be an additional document to the annexes c – e of the recommendation.

language: en format: pdf (91 pages)

---

SimPDM Implementation Guideline

119 start guideline implementationguidelines mitglied 15 1 2008 simpdm en simpdm implementation guideline implementation guideline for simpdm 2.0 (psi 4 / vda 4967)

this implementation guideline accompanies the prostep ivip psi 4 / vda 4967 recommendation, version 2.0.

it aims for a better understanding on technical level of the simpdm results. target audience are those who implement simpdm.

this document contains several annotated examples how simpdm works. it is structured like the recommendations main document. it is intended to be an additional document to the annexes c – e of the recommendation.

sprache: en format: pdf (91 seiten)

Smart Systems Engineering – Collaborative Simulation-Based Engineering Version 3.0

1 start guideline 10 2022 smartse en recommendations&standards smart systems engineering – collaborative simulation-based engineering version 3.0 this version of the prostep ivip psi 11 recommendation substitutes version 2 and extends the documentation with results of the project years 2019 – 2021. new topics and results included in version 3 of this psi 11 recommendation are (1) enablers for simulation-based decision making, (2) usage experiences and promotion of fmi 3.0 standard, (3)industrial requirements for the ssp format, (4) modelling and simulation standards for v-ecus, and (5) new requirements from the perspective of autonomous systems.

driven by the increasing complexity of products, collaborative development networks, new technologies and legal requirements, systems engineering is nowadays one of the standard methodologies for product development. reduced hardware testing and shortening of development times require a significant boost in digital product development. with the advancing digital transformation, verification and validation with simulations are getting more and more important.

for exchange and co-simulation of simulation models, a tool independent standard, the functional mock-up interface (fmi) was developed. fmi is the unique technical, standardized interface definition for the exchange of simulation models and the basis for model-based, collaborative systems engineering. the smart systems engineering (smartse) project within the prostep ivip association claims to foster the industrial use of fmi by definition of use cases and a process description to ensure a smooth process integration between the engineering disciplines and the collaborating partners.

this version of the prostep ivip psi 11 recommendation substitutes version 2 and extends the documentation with results of the project years 2019 – 2021. new topics and results included in version 3 of this psi 11 recommendation are (1) enablers for simulation-based decision making, (2) usage experiences and promotion of fmi 3.0 standard, (3)industrial requirements for the ssp format, (4) modelling and simulation standards for v-ecus, and (5) new requirements from the perspective of autonomous systems.

language: en format: zip file

---

Smart Systems Engineering – Collaborative Simulation-Based Engineering Version 3.0

1 start guideline 10 2022 smartse en recommendations&standards smart systems engineering – collaborative simulation-based engineering version 3.0 this version of the prostep ivip psi 11 recommendation substitutes version 2 and extends the documentation with results of the project years 2019 – 2021. new topics and results included in version 3 of this psi 11 recommendation are (1) enablers for simulation-based decision making, (2) usage experiences and promotion of fmi 3.0 standard, (3)industrial requirements for the ssp format, (4) modelling and simulation standards for v-ecus, and (5) new requirements from the perspective of autonomous systems.

driven by the increasing complexity of products, collaborative development networks, new technologies and legal requirements, systems engineering is nowadays one of the standard methodologies for product development. reduced hardware testing and shortening of development times require a significant boost in digital product development. with the advancing digital transformation, verification and validation with simulations are getting more and more important.

for exchange and co-simulation of simulation models, a tool independent standard, the functional mock-up interface (fmi) was developed. fmi is the unique technical, standardized interface definition for the exchange of simulation models and the basis for model-based, collaborative systems engineering. the smart systems engineering (smartse) project within the prostep ivip association claims to foster the industrial use of fmi by definition of use cases and a process description to ensure a smooth process integration between the engineering disciplines and the collaborating partners.

this version of the prostep ivip psi 11 recommendation substitutes version 2 and extends the documentation with results of the project years 2019 – 2021. new topics and results included in version 3 of this psi 11 recommendation are (1) enablers for simulation-based decision making, (2) usage experiences and promotion of fmi 3.0 standard, (3)industrial requirements for the ssp format, (4) modelling and simulation standards for v-ecus, and (5) new requirements from the perspective of autonomous systems.

sprache: en format: zip-datei

prostep ivip White Paper - SmartSE
 

191 start alle 2024 en de smartse 3 prostep ivip white paper - smartse
  this white paper aims to describe a process framework for embedding numerical engineering
simulations in the decision-making process of complex technical products and systems and thus to lay the foundations and guidelines for a "simulation credibility standard and recommendation" yet to be created. this document is based on the white paper “simulation-based decision making and release” published in 2021 by the project group smart systems engineering - smartse of the prostep ivip association and goes beyond the contents described therein by describing a possible way to create an international and cross-industry simulation credibility approach. this is intended to create a further basis for joint discussions with international standardization bodies and future standardization activities with regards to "simulation credibility standards and recommendation”. pdf 34 pages

---

prostep ivip White Paper - SmartSE
 

191 start alle 2024 en de smartse 3 prostep ivip white paper - smartse
  guard rails for “simulation credibility
standards and recommendation” this white paper aims to describe a process framework for embedding numerical engineering
simulations in the decision-making process of complex technical products and systems and thus to lay the foundations and guidelines for a "simulation credibility standard and recommendation" yet to be created. this document is based on the white paper “simulation-based decision making and release” published in 2021 by the project group smart systems engineering - smartse of the prostep ivip association and goes beyond the contents described therein by describing a possible way to create an international and cross-industry simulation credibility approach. this is intended to create a further basis for joint discussions with international standardization bodies and future standardization activities with regards to "simulation credibility standards and recommendation”. pdf 34 pages

Business Case Analysis SP²

116 start guideline implementationguidelines mitglied 05 4 2011 en business case analysis sp²

this document describes an approach to assess the costs and benefits of enterprise rights management (erm). the general approach is presented and exemplary benefits and costs are listed. the reader is enabled to perform a well-grounded analysis of the erm business-case.

language: en format: pdf (19 pages)

---

Business Case Analysis SP²

116 start guideline implementationguidelines mitglied 05 4 2011 en business case analysis sp²

this document describes an approach to assess the costs and benefits of enterprise rights management (erm). the general approach is presented and exemplary benefits and costs are listed. the reader is enabled to perform a well-grounded analysis of the erm business-case.

sprache: en format: pdf (19 seiten)

Implementation Guideline SP²

117 start guideline implementationguidelines mitglied 12 4 2011 sp2 en implementation guideline sp² implementation guideline for psi 7 "enterprise rights management"

these guidelines for introducing enterprise rights management (erm) follow prostep ivip recommendation psi 7, version 1.0.

the main objectives of the guidelines are to

help companies make strategic decisions, e.g. make or buy decisions

help companies introduce erm

help interested persons build and configure an erm environment

this document is intended to be a supplementary document to the annexes for the psi 7 recommendation.

language: en format: pdf (17 pages)

---

Implementation Guideline SP²

117 start guideline implementationguidelines mitglied 12 4 2011 sp2 en implementation guideline sp² implementation guideline for psi 7 "enterprise rights management"

these guidelines for introducing enterprise rights management (erm) follow prostep ivip recommendation psi 7, version 1.0.

the main objectives of the guidelines are to

help companies make strategic decisions, e.g. make or buy decisions

help companies introduce erm

help interested persons build and configure an erm environment

this document is intended to be a supplementary document to the annexes for the psi 7 recommendation.

sprache: en format: pdf (17 seiten)

Service-Engineering SP²

115 start guideline implementationguidelines mitglied 09 3 2011 en service-engineering sp²

the main objective of this document is:

broadening enterprise rights management help companies to introduce erm

help companies to take strategic decisions, for instance make or buy decision

help consulting companies to identify fields on which they can propose erm services

this document is intended to be an additional document to “guidelines to introduce enterprise rights management (erm)”, whereas “guidelines to introduce enterprise rights management (erm)” is an annex of the psi 7 recommendation

language: en format: pdf (27 pages)

---

Service-Engineering SP²

115 start guideline implementationguidelines mitglied 09 3 2011 en service-engineering sp²

the main objective of this document is:

broadening enterprise rights management help companies to introduce erm

help companies to take strategic decisions, for instance make or buy decision

help consulting companies to identify fields on which they can propose erm services

this document is intended to be an additional document to “guidelines to introduce enterprise rights management (erm)”, whereas “guidelines to introduce enterprise rights management (erm)” is an annex of the psi 7 recommendation

sprache: en format: pdf (27 seiten)

Test report for the STEP AP242 Benchmark #4 - Short Report

188 start stepap242benchmark benchmark alle 2 2024 step en de test report for the step ap242 benchmark #4 - short report

the step ap242 benchmark is an afnet and prostep ivip associations joint project with the support of several industry associations.

the objective of this benchmark is to provide a public status of step ap242 domain model functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this document presents the test results of the pdm test cases.

pdf 29 pages

---

Test report for the STEP AP242 Benchmark #4 - Short Report

188 start stepap242benchmark benchmark alle 2 2024 step en de test report for the step ap242 benchmark #4 - short report test report for the step ap242 benchmark #4 - short report

the step ap242 benchmark is an afnet and prostep ivip associations joint project with the support of several industry associations.

the objective of this benchmark is to provide a public status of step ap242 domain model functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this document presents the test results of the pdm test cases.

the step ap242 benchmark

Test report for the STEP AP242 Benchmark #4 - Long Report

189 start stepap242benchmark benchmark alle 2 2024 step en de test report for the step ap242 benchmark #4 - long report

the step ap242 benchmark is an afnet and prostep ivip associations joint project with the support of several industry associations.

the objective of this benchmark is to provide a public status of step ap242 domain model functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this document presents the test results of the pdm test cases.

pdf 29 pages

---

Test report for the STEP AP242 Benchmark #4 - Long Report

189 start stepap242benchmark benchmark alle 2 2024 step en de test report for the step ap242 benchmark #4 - long report test report for the step ap242 benchmark #4 - long report

the step ap242 benchmark is an afnet and prostep ivip associations joint project with the support of several industry associations.

the objective of this benchmark is to provide a public status of step ap242 domain model functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this document presents the test results of the pdm test cases.

the step ap242 benchmark

STEP AP242 Benchmark - PDM test case - Long Report

145 start benchmark stepap242benchmark mitglied 3 2017 step de step ap242 benchmark - pdm test case - long report test report for the step ap242 benchmark - pdm test case

iso 10303 step ap242 is available for the automotive and aerospace industries, as well as many other branches of the manufacturing industry, as a unique product standard for managed model based 3d engineering data interoperability. step ap242 has been released as “international standard” (is) in august 2014. multiple cots applications have been tested by the cax implementor forum and the pdm implementor forum.

step ap242 applications become increasingly important for cad and pdm interoperability in the manufacturing industries. this project will allow our communities to reach a status of maturity for these applications. the benchmarking activities are needed to apply quality control to ap242 based implementations.

therefore, afnet and prostep ivip decided to conduct the step ap242 benchmarks and to support the user community that will drive the project, with the support of several industry associations (asd ssg, galia, gifas, pfa, vda) and manufacturers, for getting an independent assessment of cots step ap242 interfaces

language: de format: pdf (42 pages)

---

STEP AP242 Benchmark - PDM test case - Long Report

145 start benchmark stepap242benchmark mitglied 3 2017 step de step ap242 benchmark - pdm test case - long report test report for the step ap242 benchmark - pdm test case

iso 10303 step ap242 is available for the automotive and aerospace industries, as well as many other branches of the manufacturing industry, as a unique product standard for managed model based 3d engineering data interoperability. step ap242 has been released as “international standard” (is) in august 2014. multiple cots applications have been tested by the cax implementor forum and the pdm implementor forum.

step ap242 applications become increasingly important for cad and pdm interoperability in the manufacturing industries. this project will allow our communities to reach a status of maturity for these applications. the benchmarking activities are needed to apply quality control to ap242 based implementations.

therefore, afnet and prostep ivip decided to conduct the step ap242 benchmarks and to support the user community that will drive the project, with the support of several industry associations (asd ssg, galia, gifas, pfa, vda) and manufacturers, for getting an independent assessment of cots step ap242 interfaces

sprache: de format: pdf (42 seiten)

STEP AP242 Benchmark - PDM test case - Short Report

146 benchmark stepap242benchmark alle 15 3 2017 step en step ap242 benchmark - pdm test case - short report test report for the step ap242 benchmark - pdm test case language: en format: pdf (13 pages)

---

STEP AP242 Benchmark - PDM test case - Short Report

146 benchmark stepap242benchmark alle 15 3 2017 step en step ap242 benchmark - pdm test case - short report test report for the step ap242 benchmark - pdm test case sprache: en format: pdf (13 seiten)

STEP AP242 Benchmark 2020 - Short Report

150 benchmark stepbenchmark alle 9 2020 step en step ap242 benchmark 2020 - short report test report for the step ap242 benchmark #3 - pdm test cases

the step ap242 benchmark is an afnet and prostep ivip associations project with the support of several industry associations (gifas, pfa).

the objective of this benchmark is to provide a public status of step ap242 functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this benchmark #3 includes two types of test cases: cad and pdm test cases. this document presents the test suites of the pdm test cases.

the tests are based on exchange of pdm information, correctness and conformity of the step files, fulfilment of end-to-end assembly validation properties, and end-user validation. furthermore, the test results are derived to provide conclusions on the general maturity of step ap242 bo model xml based implementations, related to the main pdm functionalities.

language: en format: pdf (25 pages)

---

STEP AP242 Benchmark 2020 - Short Report

150 benchmark stepbenchmark alle 9 2020 step en step ap242 benchmark 2020 - short report test report for the step ap242 benchmark #3 - pdm test cases

the step ap242 benchmark is an afnet and prostep ivip associations project with the support of several industry associations (gifas, pfa).

the objective of this benchmark is to provide a public status of step ap242 functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this benchmark #3 includes two types of test cases: cad and pdm test cases. this document presents the test suites of the pdm test cases.

the tests are based on exchange of pdm information, correctness and conformity of the step files, fulfilment of end-to-end assembly validation properties, and end-user validation. furthermore, the test results are derived to provide conclusions on the general maturity of step ap242 bo model xml based implementations, related to the main pdm functionalities.

sprache: en format: pdf (25 seiten)

4. Benchmark (CAD) 1999

166 start benchmark stepbenchmark mitglied 3 1999 step en 4. benchmark (cad) 1999 step, benchmark - ausführlicher bericht zum 4. benchmark (cad)

the automotive industry as a key user group for cad systems, recognising product data representation and exchange as a matter of high strategic importance for the future, has made tremendous e orts to create an international standard for automotive design data, the step ap214. this project was originally initiated by the german vda, but experts from the us, japan, france, sweden, and other european countries have long since involved themselves actively in these discussions.

the step standard has been under development since 1983, and many cad system vendors have been working on prototype implementations of step for years.

today, a cad user can buy a variety of step ap214 processors (or he gets them with his cad system updates). consequently, the users organised in the prostep association have high information requirements on the capabilities of these processors.

1996, the prostep association established a regular activity, the benchmark, to address the question of what quality the available step translators are o ering to the end user.

now, for the fourth time, we take a look at the current situation. the vendors have released new and improved versions of their translators. assemblies and presentation, newly introduced to the third benchmark's scope, meanwhile have been implemented broadly. for these reasons, the results of the former benchmarks are no more reecting the state of step implementation that is currently available.

the fourth benchmark was conducted in order to provide an update to the members of the prostep association: it was performed using the step translators that were available at the beginning of september 1998.

this benchmark documents the capabilities in exchange of solid, surface, assembly and presentation data.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the e ort of users providing the appropriate test cases.

sprache: en format: pdf (92 seiten)

---

4. Benchmark (CAD) 1999

166 start benchmark stepbenchmark mitglied 3 1999 step en 4. benchmark (cad) 1999 step, benchmark - detailed report to the 4th benchmark (cad)

the automotive industry as a key user group for cad systems, recognising product data representation and exchange as a matter of high strategic importance for the future, has made tremendous e orts to create an international standard for automotive design data, the step ap214. this project was originally initiated by the german vda, but experts from the us, japan, france, sweden, and other european countries have long since involved themselves actively in these discussions.

the step standard has been under development since 1983, and many cad system vendors have been working on prototype implementations of step for years.

today, a cad user can buy a variety of step ap214 processors (or he gets them with his cad system updates). consequently, the users organised in the prostep association have high information requirements on the capabilities of these processors.

1996, the prostep association established a regular activity, the benchmark, to address the question of what quality the available step translators are o ering to the end user.

now, for the fourth time, we take a look at the current situation. the vendors have released new and improved versions of their translators. assemblies and presentation, newly introduced to the third benchmark's scope, meanwhile have been implemented broadly. for these reasons, the results of the former benchmarks are no more reecting the state of step implementation that is currently available.

the fourth benchmark was conducted in order to provide an update to the members of the prostep association: it was performed using the step translators that were available at the beginning of september 1998.

this benchmark documents the capabilities in exchange of solid, surface, assembly and presentation data.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the e ort of users providing the appropriate test cases.

language: en format: pdf (92 pages)

5. Benchmark (CAD) 1999

164 start benchmark stepbenchmark mitglied 11 1999 step en 5. benchmark (cad) 1999 step, benchmark - ausführlicher bericht zum 5. benchmark (cad)

the automotive industry as a key user group for cad systems, recognising product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214.

under the motto “creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the fifth benchmark was conducted in order to provide an update to the members of the prostep association. it was performed using the step translators that were available at the beginning of june 1999.

this benchmark documents the capabilities in exchange of geometry, assembly and presentation data. special attention was paid to the points left open by the previously conducted fourth benchmark. these were the naming of assembly parts and the exchange of colours for couloured sub–elements. in addition the exchange of hybrid models was tested and requirements for handling the processors were also examined more closely.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of vendors and users providing the appropriate test cases.

language: en format: pdf (73 pages)

---

5. Benchmark (CAD) 1999

164 start benchmark stepbenchmark mitglied 11 1999 step en 5. benchmark (cad) 1999 step, benchmark - ausführlicher bericht zum 5. benchmark (cad)

the automotive industry as a key user group for cad systems, recognising product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214.

under the motto “creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the fifth benchmark was conducted in order to provide an update to the members of the prostep association. it was performed using the step translators that were available at the beginning of june 1999.

this benchmark documents the capabilities in exchange of geometry, assembly and presentation data. special attention was paid to the points left open by the previously conducted fourth benchmark. these were the naming of assembly parts and the exchange of colours for couloured sub–elements. in addition the exchange of hybrid models was tested and requirements for handling the processors were also examined more closely.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of vendors and users providing the appropriate test cases.

sprache: en format: pdf (73 seiten)

6. Benchmark (Part I: Stability) 2000

162 start benchmark stepbenchmark mitglied 11 2000 step en 6. benchmark (part i: stability) 2000 step, benchmark - ausführlicher bericht zum 6. benchmark (stability)

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the compatibility and scope of the implementation of the available step products. to enhance this goal the benchmark comes with new thematic and organizational aspects.

the 6th benchmark includes the themes ”stability”, draughting and pdm. this means that three separate benchmark parts will be realized and published.

this, the first part of the 6th benchmark, the ”stability” benchmark, particularly evaluated capabilities for product data exchange with respect to processor handling and geometry and the new topics validation properties and 3d-text annotation. open issues from the previous benchmark, the 5th benchmark, were also verified (e.g. part names, colours, layers).

the ”stability” benchmark was performed using the step translators that were available at the end of june 2000. the translators were used in their dis versions. dis (draft international standard) is the stage, step ap214 has reached becoming an international standard, and replaces the cd (committee draft) stage.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

sprache: en format: pdf (74 seiten)

---

6. Benchmark (Part I: Stability) 2000

162 start benchmark stepbenchmark mitglied 11 2000 step en 6. benchmark (part i: stability) 2000 step, benchmark - detailed report to the 6th benchmark (stability)

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the compatibility and scope of the implementation of the available step products. to enhance this goal the benchmark comes with new thematic and organizational aspects.

the 6th benchmark includes the themes ”stability”, draughting and pdm. this means that three separate benchmark parts will be realized and published.

this, the first part of the 6th benchmark, the ”stability” benchmark, particularly evaluated capabilities for product data exchange with respect to processor handling and geometry and the new topics validation properties and 3d-text annotation. open issues from the previous benchmark, the 5th benchmark, were also verified (e.g. part names, colours, layers).

the ”stability” benchmark was performed using the step translators that were available at the end of june 2000. the translators were used in their dis versions. dis (draft international standard) is the stage, step ap214 has reached becoming an international standard, and replaces the cd (committee draft) stage.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

language: en format: pdf (74 pages)

8. Benchmark 2003

156 start benchmark stepbenchmark mitglied 9 2003 step en 8. benchmark 2003 benchmark - ausführlicher bericht zum 8. benchmark

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep ivip association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep ivip benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the interoperability of the available step products with a special objective on the examination wheter a schema change (up to the is schema) has taken without any impairment of the quality of processors performance. the variety of tested step processors will be enlarged again by new products for additional cad systems. the 8th prostep ivip benchmark, particularly evaluated capabilities for product data exchange with respect to geometry and extended validation properties. because of the participation of two new step translators the exchange of assemblies were tested again, but with a new test model.

in january 2001 the ap214 standard was completed by the iso and achieved the status of an international standard (is). the 8th benchmark was performed using the step translators that were available by the end of april 2003. most of the translators were used in their is (international standard) versions. during the current year all the others will become is (international standard) as well.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

sprache: en format: pdf (54 seiten)

---

8. Benchmark 2003

156 start benchmark stepbenchmark mitglied 9 2003 step en 8. benchmark 2003 step, benchmark - detailed report to the 8th benchmark

the automotive industry as a key user group for cad systems, recognizing product data representation and exchange as a matter of high strategic importance for the future, has made tremendous efforts to create an international standard for automotive design data, the step ap214 (iso 10303).

under the motto ”creating quality instead of checking quality”, the prostep ivip association is pursuing a concept of performing quality assurance for step implementations in parallel with their development phase. the prostep ivip benchmark provides cad system vendors with an opportunity to measure the quality of their step processors against the requirements of the user as they relate to day–to–day usage.

the goal of the benchmark is to examine the interoperability of the available step products with a special objective on the examination wheter a schema change (up to the is schema) has taken without any impairment of the quality of processors performance. the variety of tested step processors will be enlarged again by new products for additional cad systems. the 8th prostep ivip benchmark, particularly evaluated capabilities for product data exchange with respect to geometry and extended validation properties. because of the participation of two new step translators the exchange of assemblies were tested again, but with a new test model.

in january 2001 the ap214 standard was completed by the iso and achieved the status of an international standard (is). the 8th benchmark was performed using the step translators that were available by the end of april 2003. most of the translators were used in their is (international standard) versions. during the current year all the others will become is (international standard) as well.

at this point we would like to thank all the participating system vendors whose kind donations of hardware and software made the benchmark possible. all the same we appreciate the effort of the vendors providing the appropriate geometry test cases.

language: en format: pdf (54 pages)

4. Benchmark (CAD) 1999 - Short Report

165 benchmark stepbenchmark alle 3 1999 step en 4. benchmark (cad) 1999 - short report step, benchmark - comparative test of stepprocessors language: en format: pdf (6 pages)

---

4. Benchmark (CAD) 1999 - Short Report

165 benchmark stepbenchmark alle 3 1999 step en 4. benchmark (cad) 1999 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (6 seiten)

5. Benchmark (CAD) 1999 - Short Report

163 benchmark stepbenchmark alle 11 1999 step en 5. benchmark (cad) 1999 - short report step, benchmark - comparative test stepprocessors language: en format: pdf (7 pages)

---

5. Benchmark (CAD) 1999 - Short Report

163 benchmark stepbenchmark alle 11 1999 step en 5. benchmark (cad) 1999 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (7 seiten)

6. Benchmark (Part I: Stability) 2000 - Short Report

161 benchmark stepbenchmark alle 11 2000 step en 6. benchmark (part i: stability) 2000 - short report step, benchmark - comparative test of stepprocessors language: en format: pdf (7 pages)

---

6. Benchmark (Part I: Stability) 2000 - Short Report

161 benchmark stepbenchmark alle 11 2000 step en 6. benchmark (part i: stability) 2000 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (7 seiten)

8. Benchmark 2003 - Short Report

155 benchmark stepbenchmark alle 9 2003 step en 8. benchmark 2003 - short report step, benchmark - comparative test of stepprocessors language: en format: pdf (8 pages)

---

8. Benchmark 2003 - Short Report

155 benchmark stepbenchmark alle 9 2003 step en 8. benchmark 2003 - short report step, benchmark - vergleichstest von step-prozessoren sprache: en format: pdf (8 seiten)

Recommendation SysML WF/IF

179 standards prostepivip alle 2 2023 en recommendation sysml wf/if collaboration based on sysml gets more and more important during the product development.

collaboration based on sysml gets more and more important during the product development. on the one hand the importance of collaboration for system development is increasing and on the other hand the usage of sysml as standard for model based systems engineering (mbse) is already considered in many companies.

in case of system modeling, the fact of having a common language does not mean at the same time, that there is a common exchange format available. looking to current system development projects it is obvious, that collaboration scenarios where different system modeling tools are used, are not unusual. on top collaboration partners frequently use individual sysml profiles in combination with individual methodologies.

all the points make it a challenging situation for many companies to exchange system models and were reasons, why the sysml workflow forum (sysml wf) was founded in 2017. besides the exchange of system models of course, related artefacts like requirements or test cases need also to be exchanged and bring the complexity of the exchange to an even higher level. the sysml wf decided to define three main use cases that were addressed in different work packages, to consider the main challenges of model exchange and the related artefacts. the three use cases are:

• model exchange
• requirements engineering & system design
• verification & validation

in 2021 the sysml implementor forum (sysml if) started its work, to have a closer look on the technical realization of the addressed use cases. several vendors are participating inside the sysml if representing different tool categories like authoring tools or traceability solution providers. goal of the sysml if is on the one hand to demonstrate current capabilities and approaches to the sysml wf and on the other hand to find technical solutions for the use cases and requirements addressed by the sysml wf.

this recommendation gives an overview on the findings and work results of both working groups, that have been elaborated so far. the different use cases are presented and an overview on the existing approaches for model exchange and existing exchange formats is given. the document closes with an outlook on the open points and the next steps.

language: en format: pdf (73 pages)

---

Recommendation SysML WF/IF

179 standards prostepivip alle 2 2023 en recommendation sysml wf/if collaboration based on sysml gets more and more important during the product development.

collaboration based on sysml gets more and more important during the product development. on the one hand the importance of collaboration for system development is increasing and on the other hand the usage of sysml as standard for model based systems engineering (mbse) is already considered in many companies.

in case of system modeling, the fact of having a common language does not mean at the same time, that there is a common exchange format available. looking to current system development projects it is obvious, that collaboration scenarios where different system modeling tools are used, are not unusual. on top collaboration partners frequently use individual sysml profiles in combination with individual methodologies.

all the points make it a challenging situation for many companies to exchange system models and were reasons, why the sysml workflow forum (sysml wf) was founded in 2017. besides the exchange of system models of course, related artefacts like requirements or test cases need also to be exchanged and bring the complexity of the exchange to an even higher level. the sysml wf decided to define three main use cases that were addressed in different work packages, to consider the main challenges of model exchange and the related artefacts. the three use cases are:

• model exchange
• requirements engineering & system design
• verification & validation

in 2021 the sysml implementor forum (sysml if) started its work, to have a closer look on the technical realization of the addressed use cases. several vendors are participating inside the sysml if representing different tool categories like authoring tools or traceability solution providers. goal of the sysml if is on the one hand to demonstrate current capabilities and approaches to the sysml wf and on the other hand to find technical solutions for the use cases and requirements addressed by the sysml wf.

this recommendation gives an overview on the findings and work results of both working groups, that have been elaborated so far. the different use cases are presented and an overview on the existing approaches for model exchange and existing exchange formats is given. the document closes with an outlook on the open points and the next steps.

sprache: en format: pdf (73 seiten)

prostep ivip White Paper
Systems Engineering and Agile Methods

192 start alle 2024 en de 3 white-paper prostep ivip white paper
systems engineering and agile methods this white paper focusses on how systems engineering and agile approaches could complement each other.
it describes a framework that can be used to embed agile development into a systems engineering driven
product development process. such a framework must consider constraints given by large projects and large,
historically grown organizations. therefore, this white paper makes suggestions on how to adapt the
framework to the different contexts and projects found in real world. it also explains how the framework can
be embedded into a classic product development process (pdp).
the “agile se” framework described in this whitepaper has many similarities with the scaled agile framework
(safe). several ideas from safe were adopted in agile se. however, agile se is not safe as it embeds
those ideas in a context of systems engineering and a typical product development process (pdp) and
describes, how they can coexist. pdf 44 pages

---

prostep ivip White Paper
Systems Engineering and Agile Methods

192 start alle 2024 en de 3 white-paper prostep ivip white paper
systems engineering and agile methods prostep ivip white paper
systems engineering and agile methods this white paper focusses on how systems engineering and agile approaches could complement each other.
it describes a framework that can be used to embed agile development into a systems engineering driven
product development process. such a framework must consider constraints given by large projects and large,
historically grown organizations. therefore, this white paper makes suggestions on how to adapt the
framework to the different contexts and projects found in real world. it also explains how the framework can
be embedded into a classic product development process (pdp).
the “agile se” framework described in this whitepaper has many similarities with the scaled agile framework
(safe). several ideas from safe were adopted in agile se. however, agile se is not safe as it embeds
those ideas in a context of systems engineering and a typical product development process (pdp) and
describes, how they can coexist. pdf 44 pages

STEP AP242 Benchmark 2020 - Long Report

149 start benchmark stepbenchmark mitglied 9 2020 step en step ap242 benchmark 2020 - long report test report for the step ap242 benchmark #3 - pdm test cases

the step ap242 benchmark is an afnet and prostep ivip associations project with the support of several industry associations (gifas, pfa).

the objective of this benchmark is to provide a public status of step ap242 functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this benchmark #3 includes two types of test cases: cad and pdm test cases. this document presents the test suites of the pdm test cases.

the tests are based on exchange of pdm information, correctness and conformity of the step files, fulfilment of end-to-end assembly validation properties, and end-user validation. furthermore, the test results are derived to provide conclusions on the general maturity of step ap242 bo model xml based implementations, related to the main pdm functionalities.

language: en format: pdf (42 pages)

---

STEP AP242 Benchmark 2020 - Long Report

149 start benchmark stepbenchmark mitglied 9 2020 step en step ap242 benchmark 2020 - long report test report for the step ap242 benchmark #3 - pdm test cases

the step ap242 benchmark is an afnet and prostep ivip associations project with the support of several industry associations (gifas, pfa).

the objective of this benchmark is to provide a public status of step ap242 functionalities available for operational use, tested by the industry and to identify limitations of the tested plm cots ap242 applications.

this benchmark #3 includes two types of test cases: cad and pdm test cases. this document presents the test suites of the pdm test cases.

the tests are based on exchange of pdm information, correctness and conformity of the step files, fulfilment of end-to-end assembly validation properties, and end-user validation. furthermore, the test results are derived to provide conclusions on the general maturity of step ap242 bo model xml based implementations, related to the main pdm functionalities.

sprache: en format: pdf (42 seiten)

Collaborative Product Visualization (CPV)

175 final-report alle 01 11 2006 jt en collaborative product visualization (cpv) use cases and reference processes concerning collaborative product visualization

prostep ivip’s project group “collaborative product visualization” had the simplification of product data exchange via harmonization of the visualization data exchange as aim. this project final report addresses the non-technical lessons learned as well as the issues. technical issues are addressed in the recommendation proposal; financial issues are addressed in the project plan.

in this document the project course is reflected. the done work packages are reflected shortly. parallel developments like the presentation of new visualization file formats or publication of related recommendation during project time are mentioned.

the course of the project didn’t work out as originally planned. some distinctive points are discussed, mostly concerning the small number and slow progress of pilots. it’s important to mention that there were only few and slow pilots.

an outlook gives some notes and information which should be regarded on a successor project.

language: en format: pdf (11 pages)

---

Collaborative Product Visualization (CPV)

175 final-report alle 01 11 2006 jt en collaborative product visualization (cpv) use cases and reference processes concerning collaborative product visualization

prostep ivip’s project group “collaborative product visualization” had the simplification of product data exchange via harmonization of the visualization data exchange as aim. this project final report addresses the non-technical lessons learned as well as the issues. technical issues are addressed in the recommendation proposal; financial issues are addressed in the project plan.

in this document the project course is reflected. the done work packages are reflected shortly. parallel developments like the presentation of new visualization file formats or publication of related recommendation during project time are mentioned.

the course of the project didn’t work out as originally planned. some distinctive points are discussed, mostly concerning the small number and slow progress of pilots. it’s important to mention that there were only few and slow pilots.

an outlook gives some notes and information which should be regarded on a successor project.

sprache: en format: pdf (11 seiten)

ECAD/MCAD Collaboration

168 use-case alle 5 2007 step en ecad/mcad collaboration position change of an item language: en format: pdf (46 pages)

---

ECAD/MCAD Collaboration

168 use-case alle 5 2007 step en ecad/mcad collaboration position change of an item sprache: en format: pdf (46 seiten)

Parametrical 3D Data Exchange via STEP

174 final-report alle 18 12 2006 step en parametrical 3d data exchange via step use cases and comparative analysis concerning parametrical 3d data exchange via step

studies show that approximately 80% of design solutions in the automotive industry are variant designs, respectively adaptations of existing solutions. the full potential for cost and development reduction inherent in variant designs cannot be implemented yet due to restrictions relating to the data exchange. fully modifiable designs including parametric and feature information can currently not be exchanged across different cax systems neither in a standardized nor in a proprietary way.

despite the availability of qualitative step processors, data exchange partnerships between automotive oems and their key suppliers are increasingly based on a policy to exchange native cad data. this policy is not cost effective and produces isolated islands of system specific data. moreover, many process chains at oem and supplier side are characterized by the need to bridge the shortcomings of data transfer between different cad systems, which is time consuming and cost intensive.

the document contains usage scenarios for parametric cad data exchanges. these where used to get an overview of the possibility for a parametric cad data exchange between several common cad systems. it gives also a mapping between the parametrical parameters of the different systems and problems in the parameter exchange.

language: en format: pdf (43 pages)

---

Parametrical 3D Data Exchange via STEP

174 final-report alle 18 12 2006 step en parametrical 3d data exchange via step use cases and comparative analysis concerning parametrical 3d data exchange via step

studies show that approximately 80% of design solutions in the automotive industry are variant designs, respectively adaptations of existing solutions. the full potential for cost and development reduction inherent in variant designs cannot be implemented yet due to restrictions relating to the data exchange. fully modifiable designs including parametric and feature information can currently not be exchanged across different cax systems neither in a standardized nor in a proprietary way.

despite the availability of qualitative step processors, data exchange partnerships between automotive oems and their key suppliers are increasingly based on a policy to exchange native cad data. this policy is not cost effective and produces isolated islands of system specific data. moreover, many process chains at oem and supplier side are characterized by the need to bridge the shortcomings of data transfer between different cad systems, which is time consuming and cost intensive.

the document contains usage scenarios for parametric cad data exchanges. these where used to get an overview of the possibility for a parametric cad data exchange between several common cad systems. it gives also a mapping between the parametrical parameters of the different systems and problems in the parameter exchange.

sprache: en format: pdf (43 seiten)

Usage Guide Feature Recognition in CAD Systems

128 start guideline usageguideline mitglied 13 12 2007 en de usage guide feature recognition in cad systems anleitung zur featureerkennung in catia v5 und ug-nx

moderne 3d cad-systeme sind in der lage features in einem körper, der keine entstehungsgeschichte besitzt, zu identifizieren und diese als komponenten in die baumstruktur zu erzeugen. diese fähigkeit ermöglicht dem anwender solche körper zu parametrisieren, um modifizierungen vornehmen zu können. in der regel treten solche modelle ohne historie nach einer konvertierung über step auf.

ein weiterer anwendungsfall der featureerkennung ist die modellvorbereitung für die ncprogrammierung. die funktionen erkennen konstruktions- und bearbeitungsfeatures und bieten diverse möglichkeiten, diesen zu filtern und zu identifizieren. so können konstruktionsfeatures auch in bearbeitungsfeatures konvertiert werden unter berücksichtigung von geometrischen und technologischen parameter wie toleranzen und gewinde. features und muster werden dabei identifiziert und in den herstellungsprozess eingebunden.

schwerpunkt dieser untersuchung ist die funktion „feature-recognition“ in catia v5 von dassault systèmes. die entsprechende funktionalität in ug-nx von siemens plm software wird nur grob aufgezeigt und muss in einer separaten untersuchung analysiert und bewertet werden.

diese dokument ist im rahmen der arbeiten des projekts infoplatform des prostep ivip vereins entstanden.

sprache: de & en format: pdf (27 seiten)

---

Usage Guide Feature Recognition in CAD Systems

128 start guideline usageguideline mitglied 13 12 2007 en de usage guide feature recognition in cad systems guidance for feature recognition with catia v5 and ug-nx

modern 3d cad systems are able to identify features in a body that has no history and add them to the tree structure as components. this allows you to parameterize such bodies in order to be able to make changes to them. models like this without a history are generally obtained following step conversion.

feature recognition is also used in model preparation for nc programming. the functions recognize design and machining features and offer a range of options for filtering and identifying them. design features can thus also be converted to machining features, taking into account geometric and technology parameters such as tolerances and threads. features and patterns are identified and integrated in the manufacturing process.

the focus of this study is the feature recognition function in dassault systèmes' catia v5. the corresponding functionality in siemens plm software's ug-nx is only outlined briefly. it will have to be analyzed and evaluated in a separate study.

this document was created as part of the work of the prostep ivip association's project infoplatform.

language: en & de format: pdf (27 pages)

MCM Adaptation Guideline

127 start guideline usageguideline mitglied 10 8 2016 en mcm adaptation guideline einführung eines manufacturing change managements in industriellen unternehmen

continual changes during running production processes, whether on the shop floor or, for instance, in planning, operating equipment construction, idea management, or industrial engineering, are among the recurring challenges for employees of modern industrial companies. changes for the shop floor can be introduced from any of these areas and have reciprocal effects on planned changes or those that are currently being implemented. an overview of all these change measures is necessary for whichever work area is considered, to facilitate assessment of the effects of new changes and their efficient implementation. management of change in production, referred to as manufacturing change management (mcm), is required. the project group digital manufacturing (dm) has particularized an mcm concept for this purpose, issued under psi recommendation 12.

the first step in introducing such an mcm concept to running processes is evaluation within the scope of a pilot project. yet even introducing a pilot project while processes are underway poses a challenge. new work methods need to be incorporated and evaluated alongside the operative processes. the extent of the pilot project is defined together with the persons and areas involved. sensible workflows are detailed and changes during running production operation are recorded in a formalized form. the question of suitable it support is also raised here. the employees of the dm project group faced these and other questions in their pilot projects, and gained varying experiences thereby.

building on psi recommendation 12, this mcm adaptation guideline is intended to support the introduction of an mcm in an industrial company. based on the experiences gained here and in addition to organizational and technical general conditions, different concentrations in the implementation are elucidated and recommendations for practical implementation of the formal concept are offered.

sprache: en format: pdf (45 seiten)

---

MCM Adaptation Guideline

127 start guideline usageguideline mitglied 10 8 2016 en mcm adaptation guideline introduction of a manufacturing change management in industrial companies

continual changes during running production processes, whether on the shop floor or, for instance, in planning, operating equipment construction, idea management, or industrial engineering, are among the recurring challenges for employees of modern industrial companies. changes for the shop floor can be introduced from any of these areas and have reciprocal effects on planned changes or those that are currently being implemented. an overview of all these change measures is necessary for whichever work area is considered, to facilitate assessment of the effects of new changes and their efficient implementation. management of change in production, referred to as manufacturing change management (mcm), is required. the project group digital manufacturing (dm) has particularized an mcm concept for this purpose, issued under psi recommendation 12.

the first step in introducing such an mcm concept to running processes is evaluation within the scope of a pilot project. yet even introducing a pilot project while processes are underway poses a challenge. new work methods need to be incorporated and evaluated alongside the operative processes. the extent of the pilot project is defined together with the persons and areas involved. sensible workflows are detailed and changes during running production operation are recorded in a formalized form. the question of suitable it support is also raised here. the employees of the dm project group faced these and other questions in their pilot projects, and gained varying experiences thereby.

building on psi recommendation 12, this mcm adaptation guideline is intended to support the introduction of an mcm in an industrial company. based on the experiences gained here and in addition to organizational and technical general conditions, different concentrations in the implementation are elucidated and recommendations for practical implementation of the formal concept are offered.

language: en format: pdf (45 pages)

prostep ivip White Paper - Systems Engineering and Agile Methods
 

190 start prostep ivip white-paper alle 2024 3 en de prostep ivip white paper - systems engineering and agile methods
 

this white paper focusses on how systems engineering and agile approaches could complement each other.
it describes a framework, that can be used to embed agile development into a system engineering driven product development process. such a framework must consider constraints given by large projects and large, historically grown organizations. therefore, this white paper makes suggestions on how to adapt the framework to the different contexts and projects found in real world. it also explains, how the framework can be embedded into a classic product development process (pdp). 

the “agile se” framework described in this whitepaper has many similarities with the scaled agile framework (safe). several ideas from safe were adopted in agile se. however, agile se is not safe as it embeds those ideas in a context of systems engineering and a typical product development process (pdp) and describes, how they can coexist.

 

pdf 44 pages

---

prostep ivip White Paper
Systems Engineering and Agile Methods

190 start prostep ivip white-paper alle 2024 3 en de prostep ivip white paper
systems engineering and agile methods prostep ivip white paper
systems engineering and agile methods
how to combine agility with systems engineering
version 1, 23. february 2024

this white paper focusses on how systems engineering and agile approaches could complement each other.
it describes a framework, that can be used to embed agile development into a system engineering driven product development process. such a framework must consider constraints given by large projects and large, historically grown organizations. therefore, this white paper makes suggestions on how to adapt the framework to the different contexts and projects found in real world. it also explains, how the framework can be embedded into a classic product development process (pdp). 

the “agile se” framework described in this whitepaper has many similarities with the scaled agile framework (safe). several ideas from safe were adopted in agile se. however, agile se is not safe as it embeds those ideas in a context of systems engineering and a typical product development process (pdp) and describes, how they can coexist.

 

pdf 44 seiten

prostep ivip PSI 14-2 Recommendation V3.0

JT Recommendation
Comprehensiv

195 start prostep ivip alle 4 2024 en de pdf 63 seiten

---

prostep ivip White Paper - Systems Engineering and Agile Methods
 

195 start prostep ivip alle 4 2024 en de prostep ivip white paper - systems engineering and agile methods
  pdf 63 pages

White Paper Applying JT

87 start white-paper alle 9 2009 jt en de white paper applying jt guidance for using jt in practice

cad has become what today is referred to as a “commodity”. it goes without saying that design engineering relies on authoring systems that enable a realistic model of the product being developed to be created on the screen –or on a powerwall – everybody appreciates that. but the model is not only easier to understand. it also allows digital methods to be used for validation, testing and quality assurance where once physical prototypes were imperative. the benefits reaped have now whet the appetite of completely new departments, which had previously never shown any interest in technical details. while technical drawings could only be read by “insiders”, design engineers, people with specialist know-how and spatial visuali-zation abilities, the 3d model can serve a wide variety of purposes for a wide variety of people.

at the same time, an enormous demand for exploiting this potential has developed. theoretically – and technically –there is hardly any task that cannot already be completed with the help of a virtual product model. theoretically, therefore, there is hardly any department in a modern manufacturing enterprise or other enterprise that would not also benefit from access to the 3d models created in the product development department. in practical terms, however, there are still a number of obstacles to be overcome.

if we want to put a name to the main obstacles involved, they are: cad systems require too much specialist know-how to allow them to be used everywhere – they are simply too expensive for that; in its original format, the volume of data for the precise geometry and product structure is too big and the data is illsuited for a number of tasks; its handling is too complicated and the overhead involved in converting it to the required format is too great. and in addition to the actual geometry, this data also contains know-how that should not be exchanged at all.

on the one hand, these obstacles have meant that many of the benefits offered by cax technologies have not yet been exploited to an extent that actually makes sense from the point of view of the processes, costs and quality of the work results. that is the negative aspect. on the other hand, they have also resulted in the creation of alternatives that allow industry to avoid these obstacles. that is the positive aspect. one of these alternatives is jt (jupiter tessellation). the reason why the vda working committee plm, together with the prostep ivip association, is lending its support to the process of standardizing jt on an international level is because this alternative enjoys both great popularity and widespread use within member companies. leading car manufacturers’ and automotive suppliers’ loud call for standardization is a clear indication of the enormous benefits that key sectors of the industry expect as a result of using jt. if the next stage of virtual product development is to be achieved and physical prototypes are to be rendered even more obsolete, it must be possible to display and use the data generated in the development departments with the required level of quality, regardless of its origin. and with the guarantee that, in this format, the data is based on internationally recognized standards and will therefore remain valid and processable for years to come.

this paper provides information on jt and the path it has take from a proprietary visualization format to an international standard. it illustrates which processes and tasks can derive significant benefits from the format, where the limitations regarding its use lie and what points need to be remembered when using jt.

another format, which was also created by siemens plm software and provides a mechanism for the lightweight, geometry-less transfer of metadata and structure data, often crops up in connection with jt: plmxml. this format is, however, not currently slated for standardization and is for the time being merely a product from siemens plm software and as such has not been included in this white paper. in the near future, the industry will also have to come to an agreement regarding the use of uniform, open standards for the exchange of structure data. only then can the use of visualization formats like jt lead to the hoped-for success and the promised cost savings actually be achieved.

language: en & de format: zip file

---

White Paper JT in der Anwendung

87 start white-paper alle 9 2009 jt en de white paper jt in der anwendung entscheidungshilfen zum einsatz von jt in der praxis

cad ist – um es neudeutsch zu sagen – zur commodity geworden. es ist selbstverständlich, dass sich konstruktion und design auf autorensysteme stützen, die ein realitätsnahes modell des zu entwickelnden produktes auf dem bild-schirm – oder der powerwall – entstehen lassen, das jeder begreift. das modell ist aber nicht nur besser zu verstehen. es gestattet die anwendung digitaler methoden für validierung, test und qualitätssicherung, wo vorher physikalische prototypen zwingend erforderlich waren. mit dem nutzen ist der appetit gewachsen, und es haben ganz neue bereiche appetit bekommen, die sich früher nie für technische details interessiert haben. war die technische zeichnung ausschließlich für eingeweihte, für konstrukteure, für menschen mit spezialausbildung und „räumlichem vorstellungsvermögen“ zu lesen, so kann das 3d-modell jedermann auf vielfältige weise dienen.

gleichzeitig ist ein enormer bedarf gewachsen, diese möglichkeit zu nutzen. theoretisch – und technisch – gibt es kaum eine aufgabe, die nicht bereits mithilfe des virtuellen produktmodells zu lösen ist. theoretisch gibt es deshalb kaum einen bereich im modernen fertigungsunternehmen und darüber hinaus, der nicht zugriff auch auf die 3d-modelle aus der produktentwicklung haben sollte. praktisch steht dem allerdings noch einiges im wege.

wenn wir die zentralen hindernisse beim namen nennen wollen, heißen sie: cad-systeme verlangen zuviel spezialwissen, als dass sie überall zum einsatz kommen können; sie sind zu teuer dafür; die exakten daten von geometrie und produktstruktur sind in ihren originalformaten zu groß und für etliche aufgabenstellungen wenig geeignet; für viele zwecke ist ihre handhabung zu umständlich und der aufwand zu hoch, sie in das jeweils benötigte format zu konvertieren. und neben der reinen geometrie enthalten sie auch know-how, das gar nicht ausgetauscht werden soll.

solche hindernisse haben einerseits dazu geführt, dass viele nutzeffekte der cax-technologien noch nicht in dem maß zum tragen gekommen sind, wie dies aus sicht der prozesse, der kosten und der qualität der arbeitsergebnisse eigentlich sinnvoll wäre. das ist das manko. andererseits haben sie aber auch dazu geführt, dass alternativen entstanden sind, die der industrie erlauben, den hindernissen aus dem weg zu gehen. das ist das positive. eine dieser alternativen heißt jt (jupiter tesselation). wenn jetzt der vda arbeitskreis plm gemeinsam mit dem prostep ivip vereinden prozess der internationalen normierung von jt unterstützt, dann deswegen, weil sich diese alternative durch besonderen zuspruch und besonders starke verbreitung in den mitgliedsfirmen auszeichnet. die nachdrückliche forderung führender automobilhersteller und zulieferer nach dieser standardisierung ist ein deutlicher hinweis auf den enormen nutzen, den sich wichtige teile der industrie vom jt-einsatz versprechen. um die nächste stufe der virtuellen produktentstehung zu erreichen und physikalische prototypen noch weiter obsolet zu machen, müssen die in der entwicklung erzeugten daten unabhängig von ihrer quelle in der benötigten qualität dargestellt und verwendet werden können. mit der sicherheit, dass sie in dieser form auf international anerkannten standards basieren und so auch in etlichen jahren noch gültig beziehungsweise verarbeitbar sind.

das vorliegende papier stellt jt und seinen weg vom proprietären visualisierungsformat zum internationalen standard vor und zeigt, für welche prozesse und aufgabenstellungen sich dadurch entscheidendes ändern kann, wo die grenzen der nutzung liegen und auf was beim einsatz von jt zu achten ist.

in zusammenhang mit jt taucht häufig ein anderes format auf, das ebenfalls von siemens plm software stammt und der leichtgewichtigen, geometrielosen übertragung von metadaten und strukturdaten dient: plmxml. dieses format steht aber derzeit nicht zur normierung an, ist bis auf weiteres also lediglich ein produkt von siemens plm software und deshalb auch nicht gegenstand des vorliegenden white papers. die industrie muss sich auch in zusammenhang mit dem thema strukturdatenaustausch in naher zukunft auf die nutzung einheitlicher, offener standards verständigen. nur so kann der einsatz von visualisierungsformaten wie jt zum erhofften erfolg führen und können die versprochenen kosteneinsparungen tatsächlich erreicht werden.

sprache: de & en format: zip-datei

White Paper for PDTnet Authorization and Security Concepts

103 white-paper alle 5 2003 pdtnet en white paper for pdtnet authorization and security concepts pdtnet projekt, pdm-data exchange - description of authorizied access on pdm systems and security concepts

the pdtnet project will give user outside a company network access to data inside the companies pdm system. this process involves a lot of security issues. the access to the pdm system has to be secured, so that only authorized users can login into the system, the transport from and to the system has to be secured so that third parties can not read the data and the users should only access data they are allowed to see.

a pdtnet scenario can only be successful if these three assumptions are valid. during the design of a pdtnet system the data security is a crucial part of the implementation.

this paper can only give an overview over the topics in connection with security. it is not intended to be a complete guide to a secure system. its goal is to give an overview about the involved topics. all implementation details depend on the scenario, the transport mechanisms and the used pdm system and are heavily scenario dependent.

language: en format: pdf (20 pages)

---

White Paper for PDTnet Authorization and Security Concepts

103 white-paper alle 5 2003 pdtnet en white paper for pdtnet authorization and security concepts pdtnet projekt, pdm-data exchange - description of authorizied access on pdm systems and security concepts

the pdtnet project will give user outside a company network access to data inside the companies pdm system. this process involves a lot of security issues. the access to the pdm system has to be secured, so that only authorized users can login into the system, the transport from and to the system has to be secured so that third parties can not read the data and the users should only access data they are allowed to see.

a pdtnet scenario can only be successful if these three assumptions are valid. during the design of a pdtnet system the data security is a crucial part of the implementation.

this paper can only give an overview over the topics in connection with security. it is not intended to be a complete guide to a secure system. its goal is to give an overview about the involved topics. all implementation details depend on the scenario, the transport mechanisms and the used pdm system and are heavily scenario dependent.

sprache: en format: pdf (20 seiten)

White Paper - Collaborative Requirements Management

94 start white-paper alle 3 2008 reqif en de white paper - collaborative requirements management requirements engineering and management in development networks

requirements engineering and management are fundamental engineering activities within the product creation life cycle. functional and nonfunctional product characteristics are defined in this very early phase and have a tremendous impact on the following engineering tasks. obscurities and errors within the requirements specification may lead to poor product quality and increased effort during development. the situation becomes more dramatic by having several development partners involved in product creation. the more partners involved, the more important it is to define a strict requirements engineering and management methodology to ensure flawless communication and execution.

over the last years the his (manufacturer initiative software) defined an interchange format for requirements management systems (rif). the goal is to have an agreed interchange format allowing development partners to exchange requirements specifications regardless of the tools used. methods that support the exchange of engineering specifications have not been defined so far, nor best practices, or reference work flows. due to the nature of this initiative, the perspective taken is oem-oriented. so far, rif can be regarded as a quasi-standard in the automotive e/e engineering domain.

in order to improve the exchange of requirements specifications between development partners, an interchange format is important, but this has to be enriched by corresponding best practices and reference work flows covering the different phases of product creation and considering the various engineering disciplines.

the prostep ivip association acknowledged the need to find solutions to so-called collaborative requirements management (corm) and sent out invitations to two expert workshops on this subject. this white paper contains the basic action plans elaborated at these workshops, possible solutions, and steps toward their implementation.

language: en & de format: zip file

---

White Paper - Collaborative Requirements Management

94 start white-paper alle 3 2008 reqif en de white paper - collaborative requirements management requirements engineering und management in entwicklungsverbünden

requirements engineering und management haben im produktenstehungsprozess eine herausragende bedeutung. funktionale wie nicht-funktionale produkteigenschaften werden in dieser frühen phase festgelegt und haben einen enormen einfluss auf die nachfolgenden entwicklungsaufgaben. ungenauigkeiten und fehler im lasten-/pflichtenheft können einen negativen einfluss auf die produktqualität haben und ziehen meist einen erhöhten entwicklungsaufwand nach sich. sind mehrere partner in der produktentwicklung involviert, ist diese situation noch dramatischer. je mehr partner beteiligt sind, desto wichtiger ist es, verbindliche methoden für das requirements engineering und management festzulegen, um so eine möglichst reibungslose kommunikation und bearbeitung zwischen ihnen zu gewährleisten.

in den letzten jahren hat die his (hersteller initiative software) ein format für den austausch von anforderungen spezifiziert – das requirements interchange format (rif). damit verbunden ist das ziel, ein anerkanntes austauschformat zu etablieren, das entwicklungspartnern erlaubt, anforderungsspezifikationen unabhängig von den eingesetzten systemen auszutauschen. methoden, die den austausch solcher spezifikationen unterstützen, wurden jedoch bisher ebenso wenig entwickelt, wie best practices und referenzprozesse. zudem ist rif deutlich vom blickwinkel der oems geprägt. dennoch gilt: rif kann als quasi-standard im elektrik/elektronik-umfeld im automobilbau angesehen werden.

um rif jedoch in der breite ausrollen zu können und maximalen nutzen daraus ziehen zu können, muss die spezifikation jedoch noch um entsprechende best practices und referenzmodelle, die die verschiedenen phasen der produktentstehung und die unterschiedlichen fachdisziplinen berücksichtigen, erweitert werden.

der prostep ivip verein hat diesen bedarf erkannt und unter der überschrift collaborative requirements management (corm) zu zwei experten-workshops eingeladen. dieses white paper gibt im wesentlichen die dabei herausgearbeiteten handlungsbedarfe, mögliche lösungsansätze sowie schritte zu deren umsetzung wider.

sprache: de & en format: zip-datei

White Paper "Firmenübergreifendes Projektmanangement und innovative Wege der praktischen Vermittlung"

96 start white-paper alle 4 2007 psms de white paper "firmenübergreifendes projektmanangement und innovative wege der praktischen vermittlung" white paper zum ersten teil der prostep ivip recommendation "collaborative projekt management" (psi 1-1)

die zeit, in der zulieferer nur als verlängerte werkbank betrachtet wurden, ist längst vorbei. so wird der anteil der eigenentwicklung in der automobilindustrie in fünf jahren nur noch ca. 30% betragen. gut funktionierende partnerbeziehungen zwischen systemlieferanten und oem benötigen zeit, um sich entwickeln und heranreifen zu können. diese ist heute meist nicht mehr gegeben. damit gemeinsame entwicklungsprozesse schnell und effektiv gestaltet werden können, haben firmen aus der automobil- und softwareindustrie im prostep ivip verein die projektgruppe „collaborative project management (cpm)“ ins leben gerufen, um empfehlungen (prostep ivip recommendations) für ein firmenübergreifendes projektmanagement zu erarbeiten.

dieses white paper beschreibt die bislang erarbeiteten ergebnisse der projektgruppe cpm sowie business-board-simulationen als innovative methode, um diese erlebbar zu vermitteln.

language: de format: pdf (12 pages)

---

White Paper "Firmenübergreifendes Projektmanangement und innovative Wege der praktischen Vermittlung"

96 start white-paper alle 4 2007 psms de white paper "firmenübergreifendes projektmanangement und innovative wege der praktischen vermittlung" white paper zum ersten teil der prostep ivip recommendation "collaborative projekt management" (psi 1-1)

die zeit, in der zulieferer nur als verlängerte werkbank betrachtet wurden, ist längst vorbei. so wird der anteil der eigenentwicklung in der automobilindustrie in fünf jahren nur noch ca. 30% betragen. gut funktionierende partnerbeziehungen zwischen systemlieferanten und oem benötigen zeit, um sich entwickeln und heranreifen zu können. diese ist heute meist nicht mehr gegeben. damit gemeinsame entwicklungsprozesse schnell und effektiv gestaltet werden können, haben firmen aus der automobil- und softwareindustrie im prostep ivip verein die projektgruppe „collaborative project management (cpm)“ ins leben gerufen, um empfehlungen (prostep ivip recommendations) für ein firmenübergreifendes projektmanagement zu erarbeiten.

dieses white paper beschreibt die bislang erarbeiteten ergebnisse der projektgruppe cpm sowie business-board-simulationen als innovative methode, um diese erlebbar zu vermitteln.

sprache: de format: pdf (12 seiten)

White Paper CPO

77 start white-paper recommendations&standards alle 21 9 2017 cpo en white paper cpo impact of cloud computing on plm openness

more than 80% of new software is being developed for the cloud1. in product lifecycle management (plm), it vendors provide, or plan to provide cloud-based offerings for all or part of their portfolio. dramatic growth in cloud-based solutions is being driven by numerous benefits in cloud computing:

increased power for processor-intensive operations such as rendering, simulation and analysis

scalable storage capacity

better cost control from reduced capital expenditure and flexible software as a service, subscription and managed services models

predictable costs and lower total costs of ownership

faster time to value and reduced time for implementation

opportunities for extended service level agreements such as guaranteed application uptime

support for integrations and customizations

automatic roll-out of upgrades and updates

increasing the ability to scale quickly based on needs to be agile in the marketplace

assurance of meeting security standards - 94% of smb cloud adopters report that they have experienced security benefits since moving to the cloud

simplified client collaboration throughout the supply chain using, for example, popular web browsers

higher employee mobility through client/server distribution and enablement of tablet and smartphone use

improved employee mobility and collaboration, in addition to more flexible licensing models are clear benefits for plm openness.
it customers who use cloud based offerings also need to consider potential challenges for certain aspects of openness (interoperability, extensibility, etc.). these may arise due to various reasons, including:

dependency on cloud service providers who manage infrastructure, service level agreements and upgrades

availability of customization and integration options in cloud environments

the objective of this white paper is to provide cpo members with a guide to those aspects of openness discussed in cpo version 1.4 which may be impacted when using cloud-based solutions compared with traditional on-premise installations. it customers and service providers can then seek more detailed elaboration from it vendors for their specific solutions.

language: en format: pdf (6 pages)

---

White Paper CPO

77 start white-paper recommendations&standards alle 21 9 2017 cpo en white paper cpo impact of cloud computing on plm openness

more than 80% of new software is being developed for the cloud1. in product lifecycle management (plm), it vendors provide, or plan to provide cloud-based offerings for all or part of their portfolio. dramatic growth in cloud-based solutions is being driven by numerous benefits in cloud computing:

increased power for processor-intensive operations such as rendering, simulation and analysis

scalable storage capacity

better cost control from reduced capital expenditure and flexible software as a service, subscription and managed services models

predictable costs and lower total costs of ownership

faster time to value and reduced time for implementation

opportunities for extended service level agreements such as guaranteed application uptime

support for integrations and customizations

automatic roll-out of upgrades and updates

increasing the ability to scale quickly based on needs to be agile in the marketplace

assurance of meeting security standards - 94% of smb cloud adopters report that they have experienced security benefits since moving to the cloud

simplified client collaboration throughout the supply chain using, for example, popular web browsers

higher employee mobility through client/server distribution and enablement of tablet and smartphone use

improved employee mobility and collaboration, in addition to more flexible licensing models are clear benefits for plm openness.
it customers who use cloud based offerings also need to consider potential challenges for certain aspects of openness (interoperability, extensibility, etc.). these may arise due to various reasons, including:

dependency on cloud service providers who manage infrastructure, service level agreements and upgrades

availability of customization and integration options in cloud environments

the objective of this white paper is to provide cpo members with a guide to those aspects of openness discussed in cpo version 1.4 which may be impacted when using cloud-based solutions compared with traditional on-premise installations. it customers and service providers can then seek more detailed elaboration from it vendors for their specific solutions.

sprache: en format: pdf (6 seiten)

Management Summary – Data Preparation for Data Analytics (DPDA)

172 final-report alle 12 2021 dpda en management summary – data preparation for data analytics (dpda) data preparation for industrial value creation

whether they are multinational corporations or hidden champions, companies in the developing and manufacturing industry are facing enormous challenges due to advancing digitalization. growing demands for flexibility, shorter development and product life cycles, and new business models are permanently changing the way data is handled as a factor in production. however, in order to use data to generate value across the product life cycles, suitable prerequisites in the form of processes, methods and technology need to be put in place to make the transformation of raw data into usable information manageable while at the same time incorporating domain know-how.

the dpda (data preparation for data analytics) project group unites industry users, system vendors and the research community under a common vision of developing a universal, standardized and adaptable tool for process-driven data preparation. in joint workshops, participants discuss practical use cases and best practices that demonstrate, among other things, that the systematization of data preparation and anchoring it as an integral part of product development and production have the potential to facilitate control and optimization of complex processes and products. with the development of role and procedure models, the project group is making an initial contribution to putting the existing wealth of experience to real use in industry.

language: en format: pdf (11 pages)

---

Management Summary – Data Preparation for Data Analytics (DPDA)

172 final-report alle 12 2021 dpda en management summary – data preparation for data analytics (dpda) data preparation for industrial value creation

whether they are multinational corporations or hidden champions, companies in the developing and manufacturing industry are facing enormous challenges due to advancing digitalization. growing demands for flexibility, shorter development and product life cycles, and new business models are permanently changing the way data is handled as a factor in production. however, in order to use data to generate value across the product life cycles, suitable prerequisites in the form of processes, methods and technology need to be put in place to make the transformation of raw data into usable information manageable while at the same time incorporating domain know-how.

the dpda (data preparation for data analytics) project group unites industry users, system vendors and the research community under a common vision of developing a universal, standardized and adaptable tool for process-driven data preparation. in joint workshops, participants discuss practical use cases and best practices that demonstrate, among other things, that the systematization of data preparation and anchoring it as an integral part of product development and production have the potential to facilitate control and optimization of complex processes and products. with the development of role and procedure models, the project group is making an initial contribution to putting the existing wealth of experience to real use in industry.

sprache: en format: pdf (11 seiten)

White Paper ECM Reference Process

60 standards sasig alle 1 2010 en white paper ecm reference process this document is an addendum which provides an explanation of the sasig ecm reference process.

this document is an overview of the sasig ecm reference process. the purpose of this document is to further elaborate on and cover topics not specifically addressed by the sasig ecm recommendation. the sasig ecm wg feels that additional simplification will help the end users better understand the strategy and thought process behind the sasig ecm recommendation.

the sasig ecm reference process (in idef0 notation) covered in this documents reflects the collective, consensus based position taken by the global sasig work group on the said reference process and all it’s sub-process on level 1 e.g. engineering change request (ecr) and engineering change order (eco). details and special cases (back jumps and iterations) are not shown intentionally because all such details are covered in the sasig ecm recommendation.

this idef0 notation is not a substitute to the detailed ecm reference process outlined in the sasig ecm recommendation, which is the master document.

the term “reference process” is used to emphasize the fact that the ecm process here is not intended to reflect any in-house ecm process of any contributing member companies.

language: en format: pdf (28 pages)

---

White Paper ECM Reference Process

60 standards sasig alle 1 2010 en white paper ecm reference process this document is an addendum which provides an explanation of the sasig ecm reference process.

this document is an overview of the sasig ecm reference process. the purpose of this document is to further elaborate on and cover topics not specifically addressed by the sasig ecm recommendation. the sasig ecm wg feels that additional simplification will help the end users better understand the strategy and thought process behind the sasig ecm recommendation.

the sasig ecm reference process (in idef0 notation) covered in this documents reflects the collective, consensus based position taken by the global sasig work group on the said reference process and all it’s sub-process on level 1 e.g. engineering change request (ecr) and engineering change order (eco). details and special cases (back jumps and iterations) are not shown intentionally because all such details are covered in the sasig ecm recommendation.

this idef0 notation is not a substitute to the detailed ecm reference process outlined in the sasig ecm recommendation, which is the master document.

the term “reference process” is used to emphasize the fact that the ecm process here is not intended to reflect any in-house ecm process of any contributing member companies.

sprache: en format: pdf (28 seiten)

White Paper - ECAD/MCAD

90 start white-paper alle 7 2009 ecad-mcad en de white paper - ecad/mcad processes and application for ecad/mcad-collaboration

from washing machine to rolling mill – today there is scarcely a product that does not incorporate mechatronic assemblies. these electronic parts, which have been integrated in the smallest possible space, ensure gentle start-up procedures, regulate changing operating conditions and optimize energy consumption. as a result, products are becoming more sophisticated and complex, which means that their mechanics, electronics and software have to be coordinated with one another to an ever increasing extent even though development cycles are becoming shorter and shorter, and cost pressures continue to increase.

these challenges can only be mastered by simultaneous engineering and above all through development partnerships. in a globalized world, this type of collaboration not only requires the efficient and error-free exchange of data but also a clear overview and strict monitoring of which information may be transferred to an outsourcing partner and which may not. for this reason, the content of any data exchange should be narrowed down to the electrical and/or mechanical parameters to such an extent that the joint development task can be completed but there is no danger of a company’s own corporate capital being lost as the result of the uncontrolled transfer of the intellectual property contained in the data.

language: en & de format: zip file

---

White Paper - ECAD/MCAD

90 start white-paper alle 7 2009 ecad-mcad en de white paper - ecad/mcad prozesse und anwendungen zur ecad/mcad-kollaboration

angefangen von der waschmaschine bis zur walzstraße – es gibt heute kaum noch ein produkt ohne mechatronische baugruppen. dabei sorgen die auf kleinstem raum integrierten elektronikbauteile für sanfte anlaufvorgänge, sie regeln sich verändernde betriebsbedingungen oder optimieren den energieverbrauch. damit werden die produkte ständig anspruchsvoller und komplexer, so dass deren mechanik, elektronik und software immer umfassender miteinander koordiniert werden muss – bei ständig kürzeren entwicklungszeiten und steigendem kostendruck.

diese herausforderungen sind nur durch ein simultaneous engineering und vor allem durch entwicklungspartnerschaften zu bewältigen. in einer globalisierten welt erfordert eine solche zusammenarbeit aber nicht nur einen effektiven und fehlerfreien austausch der daten, sondern auch eine klare übersicht und kontrolle, welche informationen an einen outsourcing-partner übertragen werden dürfen und welche nicht. darum sollte der inhalt eines datenaustauschs auf die elektrischen bzw. mechanischen parameter so gezielt eingegrenzt werden, dass einerseits die gemeinsame entwicklungsaufgabe erfüllt werden kann, aber andererseits durch einen unkontrollierten transfer des darin enthaltenen intellectual property das eigene unternehmenskapital nicht verloren geht.

sprache: de & en format: zip-datei

White Paper ERM

83 start white-paper alle 3 2014 sp2 en de white paper erm enterprise rights management (erm) ermöglicht sichere datenaustauschprozesse

ohne eine intensive zusammenarbeit zwischen projektpartnern und zulieferern ist die entwicklung innovativer produkte nicht mehr denkbar. sie erfordert jedoch einen permanenten und vor allem vertrauensvollen austausch von dokumenten - in beiden richtungen, in immer kürzeren abständen und häufig mit vielen partnern gleichzeitig. eins darf dabei aber nicht passieren – firmen-know-how darf nicht in falsche hände geraten!

früher war dieser informationsaustausch eher mit dem volleyball zu vergleichen: „wir stehen hier und wir kennen alle mitspieler auf der gegenseite“. heute dagegen entspricht die situation eher dem basketball: bei erhöhtem tempo wechseln alle mitspieler ständig ihre positionen.

jedes entwicklungsprojekt entwickelt auch seine eigene individuelle dynamik, vielfältigkeit und komplexität. dadurch kann der überblick leicht verloren gehen, so dass durch fahrlässigkeit, unwissenheit und zeitdruck daten nicht korrekt weitergeleitet oder einfach nicht genug geschützt werden. was passiert z.b. mit daten, die nach einem ende des projektes auf der festplatte des partners liegen? werden die wirklich gelöscht? oder schlummern sie dort vor sich hin und dienen vielleicht sogar einmal bei einer akquise als vorzeigeprojekt?

neben diesem rein menschlichen versagen darf kriminelle energie nicht außer acht gelassen werden – als bewusste weitergabe von informationen an die konkurrenz oder durch gezielte wirtschaftsspionage. da werden z.b. in mittelständischen unternehmen spionageprogramme eingeschleust, die dann über monate hinweg produktinformationen „absaugen“. die dadurch für die deutsche wirtschaft entstehenden schäden steigen von jahr zu jahr permanent an: umsatzeinbrüche, eventuell der verlust der marktführerschaft, vertragsstrafen durch den projektpartner bis hin zum ende einer jahrelangen erfolgreichen kundenbeziehung. und wenn schließlich z.b. durch gefälschte und minderwertige ersatzteile durch unfälle sach- und personenschäden auftreten, ist auch der gute ruf der eigenen marke dahin.

was also ist zu tun? sich von der komplexität der herausforderung schrecken lassen und auf das perfekte und umfassende it-system warten?

oder sollte nicht hier und jetzt gezielt nach praktisch umsetzbaren lösungen gesucht werden, um in ersten überschaubaren bereichen potentielle sicherheitslücken schon heute effektiv schließen zu können?

dazu müssen mit den zur verfügung stehenden tools mechanismen geschaffen werden, die den zugriff auf dokumente sowie deren austausch automatisiert kontrollieren. aus diesen erfahrungen können wiederum regeln und handlungsanweisungen abgleitet werden, mit denen zukünftig vertrauensvolle kollaborationen schneller realisiert werden können. denn es verstreicht heute immer noch zu viel zeit, bis die projektpartner sukzessiv und individuell alle sicherheitsbedenken beseitigt und sich auf einen gemeinsamen weg geeinigt haben.

sprache: de & en format: zip-datei

---

White Paper ERM

83 start white-paper alle 3 2014 sp2 en de white paper erm enterprise rights management (erm) facilitates secure data transfer processes

a close business relationship between project partners and suppliers is a necessary part of developing innovative products. this requires a continuous, secure exchange of documents in both directions – at an increasingly rapid pace and often with many partners at the same time. and all while preventing sensitive company information from falling into the wrong hands.

exchanging information used to be comparable to playing volleyball: “we are on one side and we know all of the players on the other team.” today, the situation is more like basketball: all of the players on the court are constantly changing positions at a rapid pace.

each development project develops its own individual dynamics, challenges, and complexity. in all of this it can be easy to lose sight of the project as a whole, and carelessness, ignorance, or hastiness can result in data being insufficiently protected or forwarded to the wrong parties. for example, what happens to data stored on a partner’s hard drive after the project is over? is this data really deleted? or does it just sit around on the partner’s computer, perhaps even waiting to be used as a sample project for a new acquisition?

in addition to human error, criminal intent must not be ignored; parties may intentionally forward information to the competition or engage in targeted industrial espionage. for example, spies are often sent to infiltrate medium-sized companies to collect product information over a period of several months. the damage this causes to the german economy increases year on year: decreasing revenue, loss of a company’s position on the market, contractual penalties imposed by a project partner, or even the end of an otherwise successful long-term client relationship. in addition, if fake or low-quality replacement parts cause accidents which result in personal injury or damage to property, this can ruin a company’s good reputation.

so what can we do about it? should we be afraid of the complexity of the challenges that face us and just wait for the perfect, comprehensive it system to materialize?

or should we start here and now to look for practical, viable solutions to help us effectively close potential gaps in security in some initial, manageable areas of the organization today?

to do this, we must use the tools at our disposal to create mechanisms that can automatically manage the ways in which parties access and transfer documents. the experiences we derive from this process help to shape rules and guidelines for actions that can be used to establish trustworthy relationships with future collaboration partners more quickly. in today’s business world it still takes far too long for project partners to successively eliminate all individual security concerns and agree upon a common way in which to proceed.

language: en & de format: zip file

White Paper - ERM

91 start white-paper alle 7 2008 sp2 en de white paper - erm concepts to realization of enterprise rights management (erm)

electronic documents are bearers of one of the most important assets a company has: its intellectual property. however, it is so easy to exchange information by electronic media that there is a danger this asset will end up in the hands of recipients for whom it was not intended, through carelessness or malice. enterprise rights management (erm) provides a technical way to control access to this asset and so stop unauthorized recipients from receiving it.

erm ensures that only people with access authorization can access distributed documents, no matter where they are located. so, for example, among other things, erm enables new, more flexible ways of working together that until now were not possible due to mistrust between partners. this opens up new strategic options in cross-enterprise collaboration.

implementing erm in practice is a challenge. it is a complex subject. until now there was a lack of methods, processes and technologies to support the smooth introduction of erm, and to ensure interoperability in cross-enterprise collaboration. providing solutions for use to achieve this, in line with current practice, is the aim of prostep ivip's secure product creation processes (sp2) project group, founded 2007. currently the project consortium's membership comprises representatives from adobe, audi, bmw, casolute, continental, daimler, ford, mdtvision, microsoft, prostep, siemens plm software, t-systems, tu darmstadt, vw, zgdv, and zf.

to date, following a use case analysis, detailed requirements that cross-enterprise erm solutions must meet have been determined.

currently the project group is working on recommendations for a cross-enterprise roles and rights management system and the integration of erm solutions in existing system landscapes, on reference processes for erm-based data exchange, on an analysis of the financial and strategic benefits, as well as the costs and possible risks, and finally on shedding light on legal issues that to be taken into account when erm is used.

in 2009 it is planned to publish the results of this work as a prostep ivip recommendation. in parallel to this, the results will be validated in commercial pilot tests. the commitment of leading it suppliers in the project group means that products that are ready for market will result.

this white paper reports the current state of the discussions in the project group and provides an overview of the topic of enterprise rights management. the main emphasis of the white paper is on cross-enterprise collaboration.

it also invites interested members to actively engage in the sp2 project group.

language: en & de format: zip file

---

White Paper - ERM

91 start white-paper alle 7 2008 sp2 en de white paper - erm konzepte zur realisierung von enterprise rights management (erm)

elektronische dokumente sind träger eines der wichtigsten werte in einem unternehmen: dem geistigen eigentum. gerade weil es mit elektronischen medien so leicht ist, informationen auszutauschen, besteht die gefahr, dass dieses kapital durch unachtsamkeit oder böswilligkeit empfänger erreicht, für die es nicht bestimmt ist. enterprise rights management (erm) bietet eine technische möglichkeit, den zugriff auf dieses kapital zu steuern und ihn so z.b. für unberechtigte empfänger zu unterbinden.

erm stellt sicher, dass nur zugriffsberechtigte personen auf verteilte dokumente zugreifen können, egal wo diese sich befinden. so ermöglicht erm u.a. neue, flexiblere formen der zusammenarbeit, die bisher durch das zwischen partnern bestehende misstrauen nicht möglich waren. so eröffnen sich neue strategische optionen in der unternehmensübergreifenden kooperation.

erm in die praxis umzusetzen, ist eine herausforderung. das themenfeld ist komplex. bislang fehlen methoden, prozesse und technologien, die eine reibungslose einführung unterstützen und interoperabilität in der unternehmensübergreifenden zusammenarbeit gewährleisten. hierfür praxisgerechte lösungen bereitzustellen, ist das ziel der 2007 initiierten prostep ivip projektgruppe secure product creation processes (sp2). derzeit setzt sich das projektkonsortium aus vertretern von adobe, audi, bmw, casolute, continental, daimler, ford, mdtvision, microsoft, prostep, siemens plm software, t-systems, vw, zgdv und zf zusammen.

bislang wurden aufbauend auf einer anwendungsfallanalyse umfassende anforderungen an unternehmensübergreifende erm-lösungen ermittelt.

jetzt werden empfehlungen für ein unternehmensübergreifendes rollen- und rechtemanagement und die integration von ermlösungen in bestehende systemlandschaften, referenzprozesse für den erm-basierten datenaustausch, eine analyse der finanziellen und strategischen vorteile sowie der kosten und möglichen risiken und schließlich eine beleuchtung von rechtlichen aspekten, die beim einsatz von erm zu berücksichtigen sind, erarbeitet.

2009 sollen die ergebnisse dieser arbeiten dann als prostep ivip recommendation veröffentlicht werden. parallel dazu erfolgt die validierung der ergebnisse in industriepiloten. durch das engagement führender it-anbieter in der projektgruppe wird mit der verfügbarkeit marktreifer produkte gerechnet.

dieses white paper gibt den aktuellen stand der diskussionen in der projektgruppe wieder und bietet einen überblick zum thema enterprise rights management. der schwerpunkt liegt dabei auf der unternehmensübergreifenden zusammenarbeit.

interessierte mitglieder sind auch weiterhin eingeladen, sich in der projektgruppe sp2 aktiv zu engagieren.

sprache: de & en format: zip-datei

White Paper FDX - Automated Functional Data Exchange in the Automobile Industry

67 start white-paper recommendations&standards alle 10 2022 fdx en white paper fdx - automated functional data exchange in the automobile industry the white paper presents a new standardized machine-readable data format for the exchange of functional data between oems and suppliers.

this prostep ivip / vda white paper has been devised by the fdx working group. the document presents a new standardized machine-readable data format for the exchange of functional data between oems and suppliers. functional data refers to characteristic values, characteristic curves and characteristic fields for different parts and components. they are usually determined by physically or virtually created measurements.

the new standard enables parties to exchange their functional data in a highly structured way. the main goals of the standard are

harmonization of exchange of functional data between oems and suppliers.

improved quality and availability of functional data for cae/simulation purposes

elimination of discrepancies in functional data between ordered and delivered data

reduction of misinterpretation of data during exchange and lifecycle

more extensive automation in data generation, exchange, and processing

the fdx format is based on proven industry standards such as asam ods, the corresponding data exchange format atfx and the open-source eclipse openmdm® application model.

language: en format: pdf (19 pages)

---

White Paper FDX - Automated Functional Data Exchange in the Automobile Industry

67 start white-paper recommendations&standards alle 10 2022 fdx en white paper fdx - automated functional data exchange in the automobile industry the white paper presents a new standardized machine-readable data format for the exchange of functional data between oems and suppliers.

this prostep ivip / vda white paper has been devised by the fdx working group. the document presents a new standardized machine-readable data format for the exchange of functional data between oems and suppliers. functional data refers to characteristic values, characteristic curves and characteristic fields for different parts and components. they are usually determined by physically or virtually created measurements.

the new standard enables parties to exchange their functional data in a highly structured way. the main goals of the standard are

harmonization of exchange of functional data between oems and suppliers.

improved quality and availability of functional data for cae/simulation purposes

elimination of discrepancies in functional data between ordered and delivered data

reduction of misinterpretation of data during exchange and lifecycle

more extensive automation in data generation, exchange, and processing

the fdx format is based on proven industry standards such as asam ods, the corresponding data exchange format atfx and the open-source eclipse openmdm® application model.

sprache: en format: pdf (19 seiten)

White Paper - Fahrzeugelektrik

89 start white-paper alle 9 2009 ves en de white paper - fahrzeugelektrik meilensteine zum digitalen fahrzeugmodell

nur noch etwa ein drittel der wertschöpfung entfällt hier mittlerweile auf die mechanik. in rasendem tempo haben die anderen disziplinen die oberhand gewonnen. allgemein anerkannt heißt der trend heute „elektromobilität“, und in den nächsten jahren wird die bedeutung der fahrzeugelektrik mit sicherheit noch stark zunehmen. allein 70 miteinander vernetzte steuergeräte, drei kilometer kabelbaum und etwa 700 elektrisch realisierte funktionen – so wurde bereits 2007 der stand der technik beschrieben. über kilometerlange kabelbäume vernetzte steuergeräte sichern schon jetzt einen großteil der funktionalität des automobils, das sich in dieser hinsicht nicht wesentlich von den produkten in der luft- und raumfahrt unterscheidet. eine gemeinsame basis zur beschreibung der logik der schaltungen, deren technischer realisierung mittels einzel-komponenten und verbindungen sowie der funktion des gesamtsystems ist dringend erforderlich, und damit letztlich ein funktionsmodell, das das digital mock-up – heute fast ausschließlich geometrisch geprägt – um diese aspekte erweitert.

sprache: de & en format: zip-datei

---

White Paper - Vehicle Electric

89 start white-paper alle 9 2009 ves en de white paper - vehicle electric milestone for a digital vehicle model

nowadays, only around a third of the value added can be attributed to mechanical components. the other disciplines have taken the lead at an astonishing speed. it is generally accepted that the trend today is towards what has been dubbed "electromobility", and the importance of the vehicle electric will undoubtedly grow over the coming years. no less than 70 internetworked control units, three kilometers of wiring harness and some 700 electrically implemented functions – that was how the state of the art was described back in 2007. control units that communicate with each other over wiring harnesses several kilometers in length already deliver a large proportion of the functionality of cars, and in this respect, the car differs little from the products in the aerospace industry. a common basis is urgently required for describing the logic of the circuits, the technical implementation of these circuits using individual components and connections and the function of the overall system. this will ultimately result in a functional model that extends the digital mock-up – which is currently almost exclusively geometrical in nature – to incorporate these aspects.

language: en & de format: zip file

White Paper - HOPE 1.0

95 start white-paper alle 4 2008 en de white paper - hope 1.0 herausforderungen und handlungsbedarfe der fertigungsindustrie von morgen

das vorliegende white paper hat die vielfältigen probleme der kleinen und mittelständischen unternehmen (kmu) bei der nutzung von rechnerunterstützung für die aufgaben der produkt- und produktionsentwicklung (>produktentstehung), vor allem auch im rahmen von zusammenarbeit mit auftraggebern wie systemlieferanten oder oem (original equipment manufacturer), aufgegriffen. es basiert auf den erfahrungen der autoren aus einer großen anzahl von forschungsund industrieprojekten und stellt eine zusammenfassung von potenzialen der rechnerunterstützung im produktentstehungsprozess (pep) dar, die beim stand der technik eine schlüsselstellung für erhalt und ausbau der marktführerschaft produzierender deutscher unternehmen haben. die autoren gehen davon aus, dass mit dem white paper kein dogma gesetzt wird, sondern es ist gerade intention, die speziellen bedürfnisse von kmu in wertschöpfungsketten mit oem auch mit individuellen und flexiblen lösungsansätzen entsprechend den tatsächlichen anforderungen gestalten zu können.

sprache: de & en format: zip-datei

---

White Paper - HOPE 1.0

95 start white-paper alle 4 2008 en de white paper - hope 1.0 needs for solutions of tomorrow’s manufacturing industry

this white paper deals with the manifold problems facing small and medium-sized enterprises (sme) when using computer-aided technology to accomplish the tasks involved in product and production development (> product creation), most notably within the framework of collaboration with customers such as system suppliers or oem (original equipment manufacturer). it is based on the experience gained by the authors over the course of numerous research and industry projects, and it presents a summary of the potential offered by computer-aided technology in the product creation process, which, with the current state of the art, will play a key role in maintaining and enhancing the market leadership of german manufacturing companies. the authors do not intend for the white paper to be interpreted as dogma. its intention is to allow the special needs of sme in value added chains involving oem to be met using individual and flexible approaches corresponding to the actual requirements at hand.

language: en & de format: zip file

White Paper "Analyse des unternehmens - übergreifenden Visualisierungsdaten- und Strukturdatenaustauschs

98 start white-paper alle 4 2005 jt de white paper "analyse des unternehmens - übergreifenden visualisierungsdaten- und strukturdatenaustauschs analyse des unternehmensübergreifenden visualisierungs- und strukturdatenaustauschs zwischen produktentwicklungspartnern

aufgrund gestiegener produktkomplexität sowie gleichzeitig kürzerer entwicklungs- und herstellungszyklen ist eine enge zusammenarbeit zwischen produktentwicklungspartnern notwendig. solche kooperationen überschreiten heute in der regel unternehmensgrenzen; die entwicklungspartner sind vielfach weltweit verteilt.

die notwendige zusammenarbeit führt zu einem erhöhten datenaustausch. der austausch von visualisierungsdaten gewinnt aufgrund seines attraktiven preis-/leistungsverhältnisses und seines breiten anwendungsspektrums zunehmend an bedeutung. für die zusammenarbeit zwischen den entwiklungspartnern ist in diesem kontext zusätzlich die übertragung von strukturdaten notwendig, da sie die zuordnung der visualisierten bauteile zu administrativen und organisatorischen daten ermöglicht.

um seinen mitgliedern in diesem spannungsfeld umfassendere informationen zu verschaffen, hat der prostep ivip verein dieses white paper zur analyse des unternehmensübergreifenden visualisierungs- und strukturdatenaustauschs in auftrag gegeben.

language: de format: pdf (16 pages)

---

White Paper "Analyse des unternehmens - übergreifenden Visualisierungsdaten- und Strukturdatenaustauschs

98 start white-paper alle 4 2005 jt de white paper "analyse des unternehmens - übergreifenden visualisierungsdaten- und strukturdatenaustauschs analyse des unternehmensübergreifenden visualisierungs- und strukturdatenaustauschs zwischen produktentwicklungspartnern

aufgrund gestiegener produktkomplexität sowie gleichzeitig kürzerer entwicklungs- und herstellungszyklen ist eine enge zusammenarbeit zwischen produktentwicklungspartnern notwendig. solche kooperationen überschreiten heute in der regel unternehmensgrenzen; die entwicklungspartner sind vielfach weltweit verteilt.

die notwendige zusammenarbeit führt zu einem erhöhten datenaustausch. der austausch von visualisierungsdaten gewinnt aufgrund seines attraktiven preis-/leistungsverhältnisses und seines breiten anwendungsspektrums zunehmend an bedeutung. für die zusammenarbeit zwischen den entwiklungspartnern ist in diesem kontext zusätzlich die übertragung von strukturdaten notwendig, da sie die zuordnung der visualisierten bauteile zu administrativen und organisatorischen daten ermöglicht.

um seinen mitgliedern in diesem spannungsfeld umfassendere informationen zu verschaffen, hat der prostep ivip verein dieses white paper zur analyse des unternehmensübergreifenden visualisierungs- und strukturdatenaustauschs in auftrag gegeben.

sprache: de format: pdf (16 seiten)

White Paper: Are your Engineering IT Standards ready for AI?

68 white-paper recommendations&standards alle 10 2022 kim en de white paper: are your engineering it standards ready for ai? in the "ai marketplace" project, prostep ivip, together with fiware and the heinz nixdorf institute, conducted an analysis of the best-known engineering it standards with regard to their usability for ai applications.

data is literally the „new gold“ of our time. while two zettabytes (equivalent to one billion terabytes) of data were generated worldwide in 2010, this figure had already risen to 47 zettabytes by 2020. moreover, this immense growth is predicted to exceed 2142 zettabytes (in 2035) in the coming years [sta22-ol]. in addition to the amount of data, the number of end or producer devices is also increasing: according to statista, the number of internet-enabled products is estimated to reach 75 billion by 2025.

the use of artificial intelligence holds enormous potential for utilizing this flood of data, especially for product development. the successful use of ai can lower production costs, reduce development time, and help to optimize the use of resources. for example, it is assumed that the use of ai will increase profitability by an average of 38% by 2035 [dau17-ol].

in order to fully exploit the potentials of artificial intelligence for product creation, the data from product creation plays a central role: the heterogeneous, complex data from the different software frameworks used in engineering it must be usable (or made usable) for ai applications. vendors of software solutions, especially in the ai field, are adapting to the increasing demand from industry. but industry standards and those in the still new „ai sector“ differ, which is why collaboration between the two domains has not yet reached its full potential. for this reason, the „ai marketplace“ project is investigating, among other things, the extent to which the data standards commonly used in engineering it can be read in and used directly by the most common ai frameworks, and in which cases this will not work without problems. for this purpose, the project defined the term „ai readiness“ of a standard as the ability of the standard to be read by defined ai frameworks or to be transformed into formats that have this ability. the goal is to provide a recommendation on the use of appropriate data standards from engineering it for use in ai applications, as well as to address specific challenges. this white paper provides an initial overview of the results of the analysis. the focus is on neutral, open standards to ensure a cross-tool and cross-vendor view.

language: en & de format: zip file

---

White Paper: Sind Ihre Engineering IT Standards KI-nutzbar?

68 white-paper recommendations&standards alle 10 2022 kim en de white paper: sind ihre engineering it standards ki-nutzbar? im projekt „ki-marktplatz“ hat prostep ivip gemeinsam mit fiware und dem heinz-nixdorf-institut eine analyse der bekanntesten engineering it standards hinsichtlich ihrer nutzbarkeit für ki anwendungen durchgeführt.

daten sind sprichwörtlich das “neue gold“ unserer zeit. während 2010 weltweit zwei zettabytes (dies entspricht einer milliarde terabytes) an daten generiert wurden, waren es 2020 bereits 47 zettabytes. dieser immense zuwachs wird zudem für die kommenden jahre auf über 2142 zettabytes (in 2035) prognostiziert [sta19]. es zeigt sich, dass neben der menge an daten auch die anzahl an end- bzw. erzeugergeräten zunimmt: laut statista wird die anzahl an internetfähigen produkten bis 2025 auf 75 milliarden geschätzt.

zur erschließung und nutzung dieser datenflut birgt der einsatz künstlicher intelligenz enorme potentiale, gerade für die produktentstehung. durch den erfolgreichen einsatz von ki können produktionskosten gesenkt, die entwicklungszeit verringert und ressourcen optimal genutzt werden. so wird beispielsweise von einer durchschnittlich um 38% gesteigerter rentabilitätsrate bis 2035 durch den einsatz von ki ausgegangen [dau17].

um die potentiale von künstlicher intelligenz für die produktentstehung voll entfalten zu können, spielen die daten aus der produktentstehung eine zentrale rolle: die heterogenen , komplexen daten aus den unterschiedlichen softwareframeworks der engineering it müssen für ki-anwendungen nutzbar sein (oder nutzbar gemacht werden). hersteller von softwarelösungen, besonders im kibereich, passen sich auf die steigende nachfrage der industrie an. doch die standards der industrie und solche im noch neueren „ki-sektor“ unterscheiden sich, weshalb die zusammenarbeit beider domänen noch nicht ihr volles potential erreicht hat. daher wird im projekt „ki-marktplatz“ unter anderem der fragestellung nachgegangen, inwiefern die in der engineering it üblichen datenstandards von den gängigsten ki-frameworks direkt eingelesen und genutzt werden können, und in welchen fällen dies eventuell nicht problemlos funktioniert. dazu wurde im projekt der begriff der „ai readiness“ eines standards definiert, als die fähigkeit des standards, von definierten ki frameworks eingelesen zu werden bzw. transformiert werden zu können in formate, die diese fähigkeit besitzen. ziel ist es, eine empfehlung zur nutzung geeigneter datenstandards aus der engineering it für den einsatz von ki-anwendungen zu geben, sowie auf spezifische herausforderungen einzugehen. dieses whitepaper gibt einen ersten überblick über die ergebnisse der analyse. der fokus liegt auf neutralen, offenen standards, um eine tool- und vendorübergreifende sicht zu gewährleisten.

sprache: de & en format: zip-datei

White Paper for Long-Term Archiving and Retrieval

104 white-paper alle 30 8 2002 lotar en white paper for long-term archiving and retrieval lotar, long-term archiving, product data - white paper for long-term archiving in the aerospace industry, developed within the prostep ivip

this document describes the results of the project group based on:

consolidation, common understanding, legal and business requirements

development of a strategy and preferred approach

it has to be seen as a starting point to specify methods, scenarios, applications and process modules for the aircraft industry which support long-term archiving as well as re-use (readability first, furthermore ability for further processing) of product data including 3d geometry.

since communication processes with suppliers, partners or customers manage archiving-relevant information, scenarios and resulting descriptions of processes are to be developed in a way to be applicable also for these communication processes (data exchange and data integration). the results of the specification shall be submitted first as aecma standard.

language: en format: pdf (49 pages)

---

White Paper for Long-Term Archiving and Retrieval

104 white-paper alle 30 8 2002 lotar en white paper for long-term archiving and retrieval lotar, long-term archiving, product data - white paper for long-term archiving in the aerospace industry, developed within the prostep ivip

this document describes the results of the project group based on:

consolidation, common understanding, legal and business requirements

development of a strategy and preferred approach

it has to be seen as a starting point to specify methods, scenarios, applications and process modules for the aircraft industry which support long-term archiving as well as re-use (readability first, furthermore ability for further processing) of product data including 3d geometry.

since communication processes with suppliers, partners or customers manage archiving-relevant information, scenarios and resulting descriptions of processes are to be developed in a way to be applicable also for these communication processes (data exchange and data integration). the results of the specification shall be submitted first as aecma standard.

sprache: en format: pdf (49 seiten)

White Paper MCM

82 start white-paper alle 6 2014 plim en de white paper mcm management von änderungen in der produktion

variantenreiche fertigung in großserien will gut geplant sein. die ständig noch zunehmende individualisierung der produktion mit blick auf die kundenwünsche zwingt dazu genauso, wie sie zu einer ständigen optimierung der laufenden prozesse führt. dies gilt für weiße ware ebenso wie für zuliefer-komponenten, für konsumgüter wie für fahrzeuge. in der automobilindustrie beispielsweise ist wegen der enorm gewachsenen breite des angebots an fahrzeugtypen und wegen der extremen variantenvielfalt innerhalb aller typenreihen die exakte planung der produktion und ihre möglichst genaue umsetzung eine wettbewerbsentscheidende herausforderung. die kontinuierliche prozessoptimierung sorgt aber dafür, dass es keinen produktionsplan gibt, der im laufe der zeit nicht mehrfach geändert wird. bei allen herstellern weicht die produktion mehr oder weniger stark von der ursprünglichen planung ab. um die erreichung der angestrebten ziele hinsichtlich qualität, zeit und kosten prüfen, bewerten und schließlich erreichen zu können, ist es nötig, den plan immer wieder mit der wirklichkeit abzugleichen. notwendige änderungen am produktionsablauf und planvorgaben müssen in einem iterativen prozess mit zahlreichen beteiligten miteinander in einklang gebracht werden.

die schwierigkeit besteht heute darin, dass sich die beteiligten bereiche bei änderungen nicht auf allgemein anerkannte vorgehensweisen stützen können und in der folge mit abstimmungsschwierigkeiten zu kämpfen haben. dies führt zu verzögerungen bei der dokumentation und bei der anpassung der planvorgaben bzw. bei deren umsetzung auf dem shopfloor. es besteht dringender bedarf an gemeinsamen anstrengungen, vor allem um

die nachhaltige implementierung geplanter produktionsprozesse zu optimieren,

die abweichungen der produktion vom plan zu identifizieren und zu minimieren,

die synchronisation zwischen produktionsplanung und produktion zu verbessern

und das management von veränderungen it-technisch zu unterstützen.

die projektgruppe digital manufacturing ist bestandteil des prostep ivip e.v. und wurde 2010 gegründet. seit 2013 befasst sie sich mit dem thema manufacturing change management. industrieteilnehmer sind daimler, dassault systèmes, pdtec, prostep, siemens plm software und zf friedrichshafen. auf seite der forschung sind die fh augsburg, das fraunhofer ipk berlin und die tu dortmund eingebunden.

dieses whitepaper verfolgt zwei ziele:

1. aus mit hilfe von interviews gewonnenen erkenntnissen über den verallgemeinerbaren praxisbedarf werden änderungsabläufe in einzelne, formalisierte teilprozesse zerlegt, die die grundlage für eine empfehlung eines referenzprozesses manufacturing change management bilden sollen.
2. das whitepaper beschreibt den gegenwärtigen stand der prozesse rund um das manufacturing change management, die rollen der diversen beteiligten in diesen prozessen und die probleme, die sich aus der nicht ausreichenden synchronisation von produktion und planung infolge nicht zeitnah aktualisierter dokumentation ergeben.

dazu hat die projektgruppe begonnen, anwendungsszenarien zu definieren und zu beschreiben, wie sie für den betrachteten änderungsprozess typisch sind. am ende des mcm-projektes wird, wie in vielen anderen projekten des prostep ivip vereins, eine empfehlung stehen, die das genaue vorgehen und die detailprozesse beschreibt, die sich nach ansicht der projektbeteiligten als unternehmensübergreifend sinnvoll und hilfreich erwiesen haben.

sprache: de & en format: zip-datei

---

White Paper MCM

82 start white-paper alle 6 2014 plim en de white paper mcm managing changes to production

versatile large-scale production requires careful planning, a must have amongst today’s constantly increasing product individualization, designed to answer customer demands. also required: continual optimization of existing processes. this is true for white goods and supplier components, for consumer goods and motor vehicles. the auto industry is a good example: due to the extreme growth in product ranges, and the variations available within each model series, detailed production planning and exacting implementation have become a critical market challenge. however, continual process optimization ensures that every production plan is changed several times over. all manufacturers know that the final production process will differ from the original plan, to a greater or lesser degree. in order to test, evaluate, and finally, reach the goals set in terms of quality, time required, and cost-effectiveness, the plan must be constantly compared to the reality. any changes to the production process and planning then take place over the course of an iterative process requiring the agreement of numerous participants.

the problem today is that the departments involved in changing the process cannot fall back on generally acknowledged methods, which leads to coordination problems further down the line. this results in delays in the documentation process, not to mention delays in adapting the plan and/or delays implementing the plan on the shop floor. there is a definite need to work together, in particular in order to

optimize sustainable implementation of planned production processes

identify and minimize discrepancies between the plan and the production process

improve synchronization between production planning and production

provide it support for management during the manufacturing change process.

the project group digital manufacturing was founded in 2010 and is a part of prostep ivip e.v. it has been working on manufacturing change management since 2013. industry participants include daimler, dassault systèmes, pdtec, prostep, siemens plm software, and zf friedrichshafen. fh augsburg, the fraunhofer ipk berlin, and the tu dortmund are involved in a research capacity.

this white paper has two goals:

1. with insights gained from interviews on general practical needs, change processes are divided into individual, formalized sub-processes. these sub-processes are to build the basis of a recommendation for a manufacturing change management reference process.
2. the white paper describes the current state of processes within manufacturing change management, the role of various participants within these processes, and the problems that arise from inadequate synchronization of production and planning due to documents that are not updated as frequently as is required.

the project group has also begun to define and describe implementation scenarios as typically seen in the change processes examined. as in many other projects coordinated by the prostep ivip association, the final goal of this project is to create a recommendation that describes the exact procedure and detailed processes which, according to the project participants, have been proven to be meaningful and helpful for all companies.

language: en & de format: zip file

White Paper for the Use of Standards-based Data Communication Methods in the Automotive Industry

101 white-paper alle 7 2003 pdtnet en white paper for the use of standards-based data communication methods in the automotive industry pdtnet project, pdm data exchange - white paper for integrated product development and manufacturing

in the world-wide automobile industry one of the goals is to reduce development time and costs. the complete development and simulation of the manufacturing resources and factories for a new product on a computer is the first step towards achieving this goal. the computer model of the "digital plant" can be used to perform trials and calculations for which expensive physical trials are still needed today. this computer model is created by the combined effort of a number of developers using different data creation systems.

due to the fact that each system defines its own data format the communication process along the computer-aided process chain today is tackled by duplicate data creation, redundant data management and expensive data conversion processes.

in order for the vision of “digital plant” to become reality, a neutral representation of the digital plant is needed, which can be processed by all the partners involved irrespective of data creation system used. this is why the car industry has been investing a great deal of time and money in the development and application of the neutral product data description in accordance with iso 10303 (step) for several years.

however, the standardized data model is only one precondition to allow data sharing, exchange and transfer in a heterogeneous data creation systems environment. a common understanding about processes and operations creating and processing product and manufacturing data as well as standardized implementation methods are required in addition.

in addition, an increasing portion of engineering development work is given out by oems to suppliers. this requires a stronger integration of processes, information and systems between oem and supplier. in order to cope with this, various it solutions were developed during the last years. they can be generally classified into four groups:

asynchronous file-based data exchange

data integration based on web-clients

synchronous data sharing

small-sized concepts and solutions, that are based on the techniques listed above.

encouraged by the progress made with the digital car vision, automotive companies started to continue this work in the production planning area. starting with a pdtnet application project between scania and abb, the interest group digital plant was initiated.

this paper provides an overview on the factory processes, discusses the data requirements and emphasizes the relevant standards. it also presents a concept how the concept can be brought into praxis.

in a nutshell, the goals of the interest group are:

preparing solutions for the integrated development of products and manufacturing resources

enabling and accelerating the collaboration between vehicle manufacturers and manufacturing equipment suppliers

providing access to actual product, resource and process data in a heterogeneous system environment (pdm, cax, process and manufacturing resources planning systems)

enabling the coupling of systems

driving vendors to develop interfaces

establishing flexible and comprehensive data communication based on international standards

to reach these goals the following approach will be taken:

definition of application and system scenarios for the exchange of product and resource data (resource data: product data of manufacturing equipment)

definition of use cases

definition of recommendations for the use of iso 10303 and related standards for the exchange of product and resource data

definition of implementation guidelines

language: en format: pdf (19 pages)

---

White Paper for the Use of Standards-based Data Communication Methods in the Automotive Industry

101 white-paper alle 7 2003 pdtnet en white paper for the use of standards-based data communication methods in the automotive industry pdtnet project, pdm data exchange - white paper for integrated product development and manufacturing

in the world-wide automobile industry one of the goals is to reduce development time and costs. the complete development and simulation of the manufacturing resources and factories for a new product on a computer is the first step towards achieving this goal. the computer model of the "digital plant" can be used to perform trials and calculations for which expensive physical trials are still needed today. this computer model is created by the combined effort of a number of developers using different data creation systems.

due to the fact that each system defines its own data format the communication process along the computer-aided process chain today is tackled by duplicate data creation, redundant data management and expensive data conversion processes.

in order for the vision of “digital plant” to become reality, a neutral representation of the digital plant is needed, which can be processed by all the partners involved irrespective of data creation system used. this is why the car industry has been investing a great deal of time and money in the development and application of the neutral product data description in accordance with iso 10303 (step) for several years.

however, the standardized data model is only one precondition to allow data sharing, exchange and transfer in a heterogeneous data creation systems environment. a common understanding about processes and operations creating and processing product and manufacturing data as well as standardized implementation methods are required in addition.

in addition, an increasing portion of engineering development work is given out by oems to suppliers. this requires a stronger integration of processes, information and systems between oem and supplier. in order to cope with this, various it solutions were developed during the last years. they can be generally classified into four groups:

asynchronous file-based data exchange

data integration based on web-clients

synchronous data sharing

small-sized concepts and solutions, that are based on the techniques listed above.

encouraged by the progress made with the digital car vision, automotive companies started to continue this work in the production planning area. starting with a pdtnet application project between scania and abb, the interest group digital plant was initiated.

this paper provides an overview on the factory processes, discusses the data requirements and emphasizes the relevant standards. it also presents a concept how the concept can be brought into praxis.

in a nutshell, the goals of the interest group are:

preparing solutions for the integrated development of products and manufacturing resources

enabling and accelerating the collaboration between vehicle manufacturers and manufacturing equipment suppliers

providing access to actual product, resource and process data in a heterogeneous system environment (pdm, cax, process and manufacturing resources planning systems)

enabling the coupling of systems

driving vendors to develop interfaces

establishing flexible and comprehensive data communication based on international standards

to reach these goals the following approach will be taken:

definition of application and system scenarios for the exchange of product and resource data (resource data: product data of manufacturing equipment)

definition of use cases

definition of recommendations for the use of iso 10303 and related standards for the exchange of product and resource data

definition of implementation guidelines

sprache: en format: pdf (19 seiten)

White Paper for PDM Implementation of OEM and Supplier in the Automotive Industry

102 white-paper alle 3 2003 pdtnet en white paper for pdm implementation of oem and supplier in the automotive industry pdtnet projekt, pdm-data exchange - use cases and scenarios, technical approaches and recommendations for pdm integration

product data management (pdm) with the parts geometry management, document management, product management and configuration is the platform for research & development (r&d) in the manufacturing industry.

in the world-wide automobile industry one of the goals is to reduce development time and costs. the complete development and simulation of a new product on a computer is the first step towards achieving this goal. the computer model of the "digital car" can be used to perform trials and calculations for which expensive prototypes are still needed today. this computer model is created by the combined effort of a number of developers using different data creation systems.

due to the fact that each system defines its own data format the communication process along the computer-aided process chain today is tackled by duplicate data creation, redundant data management and expensive data conversion processes.

in order for the vision of “digital car” to become reality, a neutral representation of the digital car is needed, which can be processed by all the partners involved irrespective of data creation system used. this is why the car industry has been investing a great deal of time and money in the development and application of the neutral product data description in accordance with iso 10303 (step) for several years. the parts of the step standard that are especially relevant for the automobile industry are the application protocols ap214 and ap212.

however, the standardized data model is only one precondition to allow data sharing, exchange and transfer in a heterogeneous data creation systems environment. a common understanding about processes and operations creating and processing product data as well as standardized implementation methods are required in addition.

in addition, an increasing portion of engineering development work is given out by oems to suppliers. this requires a stronger integration of processes, information and systems between oem and supplier. in order to cope with this, various it solutions were developed during the last years. they can be generally classified into four groups:

asynchronous file-based data exchange

pdm integration based on web-clients

synchronous data sharing

small-sized concepts and solutions, that are based on the techniques listed above.

the automotive companies gained experiences in the development, configuration and use of these technologies. this paper summarizes these experiences and tries to give recommendations and hints specifically for sme suppliers regarding the selection and implementation of the different technologies.

language: en format: pdf (77 pages)

---

White Paper for PDM Implementation of OEM and Supplier in the Automotive Industry

102 white-paper alle 3 2003 pdtnet en white paper for pdm implementation of oem and supplier in the automotive industry pdtnet projekt, pdm-data exchange - use cases and scenarios, technical approaches and recommendations for pdm integration

product data management (pdm) with the parts geometry management, document management, product management and configuration is the platform for research & development (r&d) in the manufacturing industry.

in the world-wide automobile industry one of the goals is to reduce development time and costs. the complete development and simulation of a new product on a computer is the first step towards achieving this goal. the computer model of the "digital car" can be used to perform trials and calculations for which expensive prototypes are still needed today. this computer model is created by the combined effort of a number of developers using different data creation systems.

due to the fact that each system defines its own data format the communication process along the computer-aided process chain today is tackled by duplicate data creation, redundant data management and expensive data conversion processes.

in order for the vision of “digital car” to become reality, a neutral representation of the digital car is needed, which can be processed by all the partners involved irrespective of data creation system used. this is why the car industry has been investing a great deal of time and money in the development and application of the neutral product data description in accordance with iso 10303 (step) for several years. the parts of the step standard that are especially relevant for the automobile industry are the application protocols ap214 and ap212.

however, the standardized data model is only one precondition to allow data sharing, exchange and transfer in a heterogeneous data creation systems environment. a common understanding about processes and operations creating and processing product data as well as standardized implementation methods are required in addition.

in addition, an increasing portion of engineering development work is given out by oems to suppliers. this requires a stronger integration of processes, information and systems between oem and supplier. in order to cope with this, various it solutions were developed during the last years. they can be generally classified into four groups:

asynchronous file-based data exchange

pdm integration based on web-clients

synchronous data sharing

small-sized concepts and solutions, that are based on the techniques listed above.

the automotive companies gained experiences in the development, configuration and use of these technologies. this paper summarizes these experiences and tries to give recommendations and hints specifically for sme suppliers regarding the selection and implementation of the different technologies.

sprache: en format: pdf (77 seiten)

White Paper "PDM Integration Strategies"

99 start white-paper alle 8 2007 en white paper "pdm integration strategies" possibilities for realizing company-wide pdm

this document was elaborated by the pdm user group of the prostep ivip association. the pdm user group is a forum where companies discuss experiences gained from actual implementation projects related to the exchange of pdm data. current members are e.g. companies like behr, bmw, cenit, continental, daimlerchrysler, delphi, magna steyr, porsche and zf. one of the latest documents released by the pdm user group were the “best practice catia v5 step ap 214 mapping”, also available at the association’s website.

in 2006, focus of the pdm user group was placed on a discussion of future data exchange strategies. an inter-national workshop dealing with the topic “data exchange of the future” was held with this in mind. the large number of people attending the workshop (60 participants from 39 companies) underscored the high level of interest generated by this topic. one major requirement of this workshop was to provide an overview of current strategies for integrating pdm (product data management) systems. this document covers the results of the related activities.

in order to answer the question why to think about pdm data integration and/or pdm data exchange, one has to remember that engineering processes are strongly team-oriented and the development of modern products is distributed. these processes are performed in the very different departments of a company, and the engineering work is often distributed across different companies.

therefore, exchanging cad (computer aided design) models and pdm meta data between the partners involved is an everyday task. an easy way to accomplish this exchange of data is to have all the users who are working with the data use the same pdm system. but what can be done if, for example, engineers do not have access to the same pdm system?

another challenge is when different pdm systems or, in more general terms, different systems that support the engineering processes are used. it is very common for the data describing identical items (parts, documents, etc.) to be stored in different systems. for example, part master data is stored in a bom (bill of material) system as well as in a dmu (digital mock-up) system. this requires tools to synchronize the data between those systems.

today, requirements such as these can be met through the use of integration technology. it is possible to implement offline and online integration within a company as well as asynchronous data exchange between engineering partners.

this document provides an introduction to enterprise-wide pdm integration technologies. the first part of the document describes scenarios for exchanging pdm data between engineering partners in collaborative scenarios. the requisite it infrastructure for integration and data exchange is dealt with in the second section. the appendix provides an overview, in table form, of data exchange concepts.

other publications relating to pdm data integration, such as managing assembly and delta data exchange, can be found in the download area of the prostep ivip website (www.prostep.org), too.

language: en format: pdf (15 pages)

---

White Paper "PDM Integration Strategies"

99 start white-paper alle 8 2007 en white paper "pdm integration strategies" possibilities for realizing company-wide pdm

this document was elaborated by the pdm user group of the prostep ivip association. the pdm user group is a forum where companies discuss experiences gained from actual implementation projects related to the exchange of pdm data. current members are e.g. companies like behr, bmw, cenit, continental, daimlerchrysler, delphi, magna steyr, porsche and zf. one of the latest documents released by the pdm user group were the “best practice catia v5 step ap 214 mapping”, also available at the association’s website.

in 2006, focus of the pdm user group was placed on a discussion of future data exchange strategies. an inter-national workshop dealing with the topic “data exchange of the future” was held with this in mind. the large number of people attending the workshop (60 participants from 39 companies) underscored the high level of interest generated by this topic. one major requirement of this workshop was to provide an overview of current strategies for integrating pdm (product data management) systems. this document covers the results of the related activities.

in order to answer the question why to think about pdm data integration and/or pdm data exchange, one has to remember that engineering processes are strongly team-oriented and the development of modern products is distributed. these processes are performed in the very different departments of a company, and the engineering work is often distributed across different companies.

therefore, exchanging cad (computer aided design) models and pdm meta data between the partners involved is an everyday task. an easy way to accomplish this exchange of data is to have all the users who are working with the data use the same pdm system. but what can be done if, for example, engineers do not have access to the same pdm system?

another challenge is when different pdm systems or, in more general terms, different systems that support the engineering processes are used. it is very common for the data describing identical items (parts, documents, etc.) to be stored in different systems. for example, part master data is stored in a bom (bill of material) system as well as in a dmu (digital mock-up) system. this requires tools to synchronize the data between those systems.

today, requirements such as these can be met through the use of integration technology. it is possible to implement offline and online integration within a company as well as asynchronous data exchange between engineering partners.

this document provides an introduction to enterprise-wide pdm integration technologies. the first part of the document describes scenarios for exchanging pdm data between engineering partners in collaborative scenarios. the requisite it infrastructure for integration and data exchange is dealt with in the second section. the appendix provides an overview, in table form, of data exchange concepts.

other publications relating to pdm data integration, such as managing assembly and delta data exchange, can be found in the download area of the prostep ivip website (www.prostep.org), too.

sprache: en format: pdf (15 seiten)

White Paper - Production Lifecycle Information Management

74 white-paper recommendations&standards alle 2 2019 plim en de white paper - production lifecycle information management information management from engineering to the shop floor

nowadays, companies that operate globally are confronted with growing demands for flexibility and shorter development cycles. among other things, this is due to the increasing complexity of products and the associated manufacturing processes. to cope with the increasingly demanding requirements, it is necessary to develop new standards and models for the uniform exchange of information throughout the entire product lifecycle. the project group plim (production lifecycle information management) brings together users from industry, system providers and service providers with a common vision of designing a universal information model throughout the entire product lifecycle. practical use cases are discussed in joint workshops. these show how it is possible to flexibly adapt highly dynamic production systems in which human-robot collaboration is implemented. development of detailed test suites for the use cases makes it possible for users and system providers to utilize the information model. users can validate their processes and interfaces and system providers can use the test suites to further develop their products. joint development ensures that the interfaces are harmonized in a targeted manner.

language: en & de format: zip file

---

White Paper - Production Lifecycle Information Management

74 white-paper recommendations&standards alle 2 2019 plim en de white paper - production lifecycle information management informationsmanagement vom engineering bis zum shopfloor

global operierende unternehmen werden heutzutage mit wachsenden anforderungen an flexibilität und verkürzten entwicklungszyklen konfrontiert. dies ist bedingt unter anderem durch die steigende komplexität der produkte und der damit verbundenen herstellprozesse. die bewältigung der stark gestiegenen anforderungen erfordert die erarbeitung und entwicklung neuer standards und modelle für einen einheitlichen informationsaustausch entlang des produktlebenszyklus. die projektgruppe plim (production lifecycle information management) vereint anwender aus der industrie, systemanbieter und serviceprovider mit der vision, ein durchgängiges informationsmodell entlang des produktlebenszyklus zu entwerfen. in gemeinsamen workshops werden praxisnahe anwendungsfälle diskutiert. diese zeigen auf, wie ein flexibles anpassen von hochdynamischen produktionssystemen mit umgesetzter mensch-roboter-kollaboration stattfinden kann. die entwicklung von detaillierten test suites zu den anwendungsfällen ermöglicht die nutzung des informationsmodells für anwender und systemanbieter. anwender können hierdurch ihre prozesse und schnittstellen validieren und systemanbieter die test suites zur weiterentwicklung ihrer produkte nutzen. die gemeinsame erarbeitung sichert die zielgerichtete harmonisierung der schnittstellen.

sprache: de & en format: zip-datei

Prostep ivip White Paper PLM: Future IT Architectures in Engineering Requirements – Technologies – Approaches

181 white-paper alle 02 5 2023 en prostep ivip white paper plm: future it architectures in engineering requirements – technologies – approaches this white paper focuses on the design of future plm it architectures against the backdrop of current trends in product and system development.

this white paper focuses on the design of future plm it architectures against the backdrop of current trends in product and system development. it first of all examines these trends with the aim of determining the key components, the technologies and the framework conditions needed for their implementation and operation. this is followed by a presentation of existing approaches and new areas of activity relating to the design of future it architectures for product development.

language: en format: pdf (23 pages)

---

Prostep ivip White Paper PLM: Future IT Architectures in Engineering Requirements – Technologies – Approaches

181 white-paper alle 02 5 2023 en prostep ivip white paper plm: future it architectures in engineering requirements – technologies – approaches this white paper focuses on the design of future plm it architectures against the backdrop of current trends in product and system development.

this white paper focuses on the design of future plm it architectures against the backdrop of current trends in product and system development. it first of all examines these trends with the aim of determining the key components, the technologies and the framework conditions needed for their implementation and operation. this is followed by a presentation of existing approaches and new areas of activity relating to the design of future it architectures for product development.

sprache: en format: pdf (23 seiten)

White Paper Production-Planning-Processes

85 start white-paper alle 3 2013 plim en de white paper production-planning-processes basic principles to the reference process for production planning

unlike product development and production operations, where sophisticated software systems (cax, plm and ppc) are universally deployed, the production planning phase, which lies between these two activities, is marked by the frequent use of isolated solutions. procurement of the tools deployed here is often driven by the needs of the moment (effectively “cherry picking“) and the tools are then used in isolation for planning tasks specific to a given tool. and like the it environment, the planning processes used also often seem to be uncoordinated and even department-centered.

as a result, it is often the case that the individual planning tasks are not performed in a clearly structured way. this leads to inefficient planning workflows with redundant activities, duplicated work, transmission errors and incomplete information, to name but a few of the potential stumbling blocks. consequently, standardization of the necessary planning processes on the basis of established best practice in the realm of production planning makes it possible to leverage much untapped potential. standardization of this type provides users with recommendations for dealing with their various planning tasks, which in turn simplifies the individual processes and makes them more transparent.

in order to meet this challenge, prostep ivip's “digital manufacturing“ project group set about developing a uniformly defined, end-to-end reference planning process for series production. this process supports the creation of planning processes tailored to the specific needs of companies and locations and thus supports efficient production planning.

language: en & de format: zip file

---

White Paper Produktionsplanungsprozesse

85 start white-paper alle 3 2013 plim en de white paper produktionsplanungsprozesse grundlagen zum referenzprozesse für die produktionsplanung

während im bereich der produktentwicklung und der produktion ausgereifte softwaresysteme (cax, plm bzw. pps) durchgängig eingesetzt werden, sind in dem dazwischen liegenden aufgabenfeld, der produktionsplanung, meist noch insellösungen zu finden. die hier verwendeten werkzeuge wurden häufig aus dem aktuellen bedarf heraus – nach der sogenannten „cherry-picking“ methode – beschafft und dann individuell und isoliert für werkzeugspezifische planungsaufgaben eingesetzt. analog zur it-landschaft zeigen auch die angewendeten planungsprozesse ein nicht aufeinander abgestimmtes, oft sogar abteilungszentriertes bild.

als folge laufen die einzelnen planungsaufgaben oftmals nicht klar strukturiert ab. dies führt zu ineffizienten planungsabläufen mit redundanten vorgängen, doppelarbeit, übertragungsfehlern und unvollständigen informationen, um nur einige hemmnisse zu erwähnen. dementsprechend kann eine standardisierung der notwendigen planungsprozesse auf der grundlage von best-practice-erfahrungen im wirkungsbereich der produktionsplanung viele brachliegende potentiale heben. dieser standard dient dann dem anwender als handlungsempfehlung für seine unterschiedlichen planungsaufgaben, wodurch die einzelnen prozesse vereinfacht und transparent ablaufen können.

zur lösung dieser herausforderung hat sich die prostep ivip projektgruppe „digital manufacturing“ die aufgabe gestellt, einen einheitlich definierten und durchgängigen referenzplanungsprozess für die serienfertigung zu entwickeln. dieser unterstützt die erarbeitung unternehmens- und standortspezifisch angepasster planungsprozesse und ermöglicht so eine effiziente planung der produktion.

sprache: de & en format: zip-datei

White Paper Project Schedule Management

84 start white-paper alle 5 2013 psms en de white paper project schedule management project schedule management

the prostep ivip association, the german association of the automotive industry (vda) and the german project management association (gpm) have issued a joint recommendation on the subject of schedule management (psi 10 / vda 4959 / gpm). to do this, the various german oems (audi, bmw, daimler, porsche, volkswagen) joined together within the framework of the prostep ivip association to launch a project group that developed the recommendation within a period of six months. the requirements identified by all the different parties were ascertained and consolidated during the course of numerous interviews.

the recommendation was presented in a workshop in darmstadt attended by representatives of the tool manufacturers and consulting firms active in the project management sector. the fact that a result was arrived at within such a short space of time is indicative of the urgency of this type of recommendation.

fundamentally, it presents a catalog of standard requirements which the above-mentioned associations consider to apply to the automotive industry as a whole. users, consultants and tool vendors can use this consolidated catalog of criteria to ensure efficiency when verifying their own methods, drafting functional specifications or developing tools.

language: en & de format: zip file

---

White Paper Projektterminmanagement

84 start white-paper alle 5 2013 psms en de white paper projektterminmanagement projektterminmanagement

der prostep ivip verein, der verband der automobilindustrie (vda) und die gesellschaft für projektmanagement (gpm) haben eine gemeinsame empfehlung zum termin management (tm) herausgegeben (gpm / psi 10 / vda 4959). unter dem dach des prostep ivip vereins haben dazu alle deutschen oems (audi, bmw, daimler, porsche, volkswagen) eine projektgruppe initiiert, die innerhalb eines halben jahres die empfehlung erarbeitet hat. in zahlreichen interviews wurden dazu die anforderungen aus allen häusern zusammengetragen und konsolidiert.

die empfehlung wurde in darmstadt in einem workshop vorgestellt, an dem vertreter der tool-hersteller sowie der im umfeld des projektmanagements tätigen beratungshäuser teilnahmen. die tatsache, dass innerhalb so kurzer zeit ein ergebnis erarbeitet wurde, spricht für die dringlichkeit einer solchen empfehlung.

in ihrem kern stellt sie einen katalog von standardanforderungen dar, die nach auffassung der genannten verbände für die automobilindustrie insgesamt gelten. anwender, berater und tool-anbieter können diesen konsolidierten kriterienkatalog als basis für effizienz bei der überprüfung der eigenen methoden, bei der erstellung von lastenheften beziehungsweise bei der entwicklung von tools nutzen.

sprache: de & en format: zip-datei

White Paper - SimPDM

93 start white-paper alle 3 2008 simpdm en de white paper - simpdm integration der simulation und berechnung in eine pdm-umgebung

dass man heutzutage schon produkte getestet hat, flugzeuge schon geflogen und auto bereits gefahren sind, bevor auch nur ein einziges teil davon gefertigt ist, ist mittlerweile eine selbstverständlichkeit. mit der fortschreitenden virtualisierung der produktentstehung haben wir schon fast vergessen, mit welchem aufwand das styling, die entwicklung, der prototypenbau, die tests, aber auch die fertigungsplanung noch vor einem jahrzehnt verbunden war. ein wesentlicher impulsgeber sind dabei die systeme zur simulation und berechnung (computer aided engineering (cae)) und deren stetig wachsendes leistungsspektrum. die mit diesen systemen einhergehende digitale revolution hat es ermöglicht, in immer kürzer werdenden zyklen, innovative produkte mit immer komplexer werdenden systemen, kostengünstig auf die märkte zu bringen und diese gleichzeitig immer sicherer, umweltfreundlicher uvm. zu machen.

der einsatz von systemen zur simulation und berechnung hat wesentliche aspekte der produktentstehungsprozesse maßgeblich beeinflusst und ist mittlerweile von strategischer bedeutung für unternehmen.

obwohl die bedeutung der simulation in den letzten jahren so gestiegen ist, ist sie meist wie in den anfangszeiten in der produktentwicklung verankert. abteilungen zur simulation und berechnung sind dabei oft informationstechnische inseln in einer ansonsten integrierten entwicklungsprozesskette. die „integration“ ist eher zwischenmenschlich und die kommunikation funktioniert auf zuruf. allein die datenbeschaffung, also das zusammentragen aller zur durchführung einer simulation oder einer berechnung benötigten daten und informationen, wird dadurch schon zu einer zeitraubenden und meist fehlerträchtigen angelegenheit (vgl. abbildung 1).

da die entwicklung eines produkts stetig vorangetrieben wird, änderungen aber nur – wenn überhaupt – mittelbar an die simulation und berechnung kommuniziert werden, werden berechnungen immer wieder auch zu einem produkt durchgeführt, das es in dieser ausprägung gar nicht mehr gibt. dass hier ressourcen verschwendet werden, leuchtet jedem ein. es werden dringend lösungen gebraucht, die es ermöglichen, dass sich die konstruktion auf der einen und die simulation und berechnung auf der anderen seite besser – wenn möglich rechnerunterstützt – abstimmen können. bedenkt man, dass heute entwicklungsprozesse oft global, über mehrere unternehmen hinweg verteilt sind und produkte in immer kürzer werdenden zyklen entwickelt werden sollen, wird noch deutlicher, wie notwendig solche lösungen sind. während die konstruktion bereits seit langem durch produktdatenmanagementsysteme (pdm-systeme) in ihrer datenverwaltung und in den prozessabläufen unterstützt wird, sucht man nach vergleichbaren lösungen für die simulation und berechnung oft vergebens.

um jedoch durchgängige prozessketten zu realisieren und damit zeit- und kostenvorteile zu erschließen und ein mehr an prozesssicherheit zu gewinnen, bedarf es genau solcher lösungen (vgl. abbildung 2) – lösungen zur integration von simulation und berechnung in eine pdm-umgebung. denn das unternehmen, das seinen mitarbeitern die richtigen informationen und daten zur simulation und berechnung zum richtigen zeitpunkt, in der richtigen qualität und quantität zur verfügung stellen kann, hat einen strategischen vorteil gegenüber der konkurrenz.

diese herausforderung anzugehen und einheitliche lösungen bereit zu stellen, das hat sich die projektgruppe simpdm (integration der simulation und berechnung in eine pdm-umgebung) im prostep ivip verein zur aufgabe gemacht. mit diesem white paper will der prostep ivip verein seine mitglieder über simpdm und die ergebnisse dieser projektgruppe informieren.

sprache: de & en format: zip-datei

---

White Paper - SimPDM

93 start white-paper alle 3 2008 simpdm en de white paper - simpdm integration of simulation and computation in a pdm-environment

today it is a given that products are tested, airplanes flown and automobiles driven before even one single part has been manufactured. the advance of virtualization in product development has already almost made us forget the time, money and effort involved in styling, development, prototyping, testing and production planning just a decade ago. an important driving force behind this development are the systems for simulation and computation (computer aided engineering (cae)) and the steadily increasing range of functionality they provide. the digital revolution associated with these systems has made it possible to introduce innovative new products with increasingly complex systems onto the market economically in ever-shorter cycles while at the same time making these products progressively safer and more environmentally friendly, among many other things.

the use of cae systems has had a significant impact on fundamental aspects of the product development processes, and it is now of strategic importance to companies.

although the importance of simulation has increased so significantly over the past few years, it is usually anchored – as in the early days – in product development. departments involved in simulation and computation often constitute information technology islands in what is otherwise an integrated development process chain. “integration” is more likely to be of the interpersonal kind and communication functions upon request. this means that data retrieval alone, i.e. compiling all the data and information required to execute a simulation or computation, becomes a time-consuming and, for the most part, error-prone affair (cf. figure 1).

since the development of a product is an ever-ongoing process, but changes are only communicated to the departments involved with simulation and computation indirectly, if at all, computations are often carried out for a product which no longer actual exists in this particular form. it is apparent to anyone that this is a waste of resources. there is an urgent need for solutions that allow design engineering, on the one hand, and simulation and computation, on the other hand, to be harmonized better – and with the aid of computers, if possible. bearing in mind that today’s development processes are often distributed globally over a number of different companies, and products need to be developed in ever-shorter cycles, it becomes even more obvious just how necessary such solutions are. although product data management systems (pdm systems) have long provided design engineering with support relating to its data management and process flows, anyone looking for comparable solutions for simulation and computation will often look in vain.

however, if end-to-end process chains are to be realized and thus time and cost advantages exploited and process reliability increased, it is exactly this type of solution that is needed (cf. figure 2), i.e. solutions for the integration of simulation and computation in a pdm environment. it is the companies which provide their employees with the right amount of right information and data for simulation and computation at the right time, with the right level of quality that have a strategic advantage over the competition.

the objective of the prostep ivip association’s simpdm (integration of simulation and computation in a pdm environment) project group is to accept these challenge and provide uniform solutions. the prostep ivip association has compiled this white paper to provide its members with information about the simpdm project group and the results that this project group has achieved.

language: en & de format: zip file

White Paper - Smart Systems Engineering

80 start white-paper alle 6 2015 smartse en de white paper - smart systems engineering data management for smart systems engineering (smart se)

according to a 2013 study on systems engineering (se) in industrial applications, future products will be smarter and more interconnected and feature complex, individually configurable functions [1].

at the same time competition for market share will increase time and cost pressures and raise standards in terms of product quality. one major challenge faced in future development processes is the ability to bring to market increasingly complex, high-quality products within ever shorter product life cycles.

this, in particular, raises the requirements in terms of interdisciplinary collaboration. in most cases, the individual disciplines do not cooperate and tend to carry out their work at different times, something that not only costs lots of time but also generally prevents multidisciplinary systems from being developed. simulating and validating how the subsystems work together can only be done in a multidisciplinary environment. this is an area where interdisciplinary data management is crucial, but also one where the available data management solutions have shortcomings that are on display especially during the early stages of product development. there is also considerable room for improvement in terms of the methodological work being performed by r&d departments in the industrial sector.

this white paper from the smart systems engineering (smart se) project group describes use cases and user requirements while also presenting initial thoughts regarding the necessary information objects and it infrastructure. this will be further expanded on over the course of the project group’s future work, the results of which shall be published in a prostep ivip recommendation.

language: en & de format: zip file

---

White Paper - Smart Systems Engineering

80 start white-paper alle 6 2015 smartse en de white paper - smart systems engineering datenmanagement für smart systems engineering (smartse)

nach einer im jahr 2013 durchgeführten studie zum systems engineering (se) in der industriellen praxis werden zukünftige produkte dadurch gekennzeichnet sein, dass sie zunehmend „intelligenter“ und stärker miteinander vernetzt sind und komplexe, individuell konfigurierbare funktionalitäten aufweisen [1].

zugleich wird der wettbewerb um marktanteile von zunehmendem zeit- und kostendruck sowie steigenden ansprüchen an die produktqualität bestimmt. immer komplexere produkte innerhalb kürzer werdender produktlebenszyklen mit hoher qualität am markt zu positionieren, stellt eine große herausforderung an zukünftige entwicklungsprozesse dar.

insbesondere steigen die anforderungen an die disziplinübergreifende zusammenarbeit. das vielfach noch vorherrschende nacheinander und nebeneinander der einzelnen fachdisziplinen kostet nicht nur zu viel zeit. es behindert auch grundsätzlich die entwicklung multidisziplinärer systeme. das funktionieren der miteinander arbeitenden teilsysteme kann nur in einer multidisziplinären umgebung simuliert und validiert werden. dabei ist ein disziplinübergreifendes datenmanagement von entscheidender bedeutung. insbesondere in den frühen produktentwicklungsphasen sind hier in den verfügbaren datenmanagementlösungen defizite festzustellen. aber auch in der methodischen arbeit der entwicklungsabteilungen in der industrie gibt es erhebliches optimierungspotenzial.

das vorliegende whitepaper der projektgruppe smart systems engineering (smart se) beschreibt anwendungsfälle und anforderungen aus sicht der anwender und stellt erste überlegungen zu den erforderlichen informationsobjekten sowie zu einer notwendigen it-infrastruktur vor. eine weitere detaillierung bleibt der zukünftigen arbeit der projektgruppe vorbehalten, deren ergebnisse in einer prostep ivip recommendation veröffentlicht werden.

sprache: de & en format: zip-datei

White Paper - SmartSE - Simulation-based Decision Making and Release

71 white-paper recommendations&standards alle 28 6 2021 smartse en white paper - smartse - simulation-based decision making and release the white paper summarizes findings on the growing importance of simulation-based decision making and release in the cross-company development of complex systems. language: en format: zip file

---

White Paper - SmartSE - Simulation-based Decision Making and Release

71 white-paper recommendations&standards alle 28 6 2021 smartse en white paper - smartse - simulation-based decision making and release the white paper summarizes findings on the growing importance of simulation-based decision making and release in the cross-company development of complex systems. sprache: en format: zip-datei

White Paper - SmartSE - System Structure and Parameterization

70 white-paper recommendations&standards alle 1 2022 smartse en white paper - smartse - system structure and parameterization the white paper provides an introduction to the ssp standard, the use cases addressed and the benefits of using the standard. language: en format: pdf (15 pages)

---

White Paper - SmartSE - System Structure and Parameterization

70 white-paper recommendations&standards alle 1 2022 smartse en white paper - smartse - system structure and parameterization the white paper provides an introduction to the ssp standard, the use cases addressed and the benefits of using the standard. sprache: en format: pdf (15 seiten)

White Paper - SmartSE - Virtual Electronic Control Units

72 white-paper recommendations&standards alle 3 2020 en white paper - smartse - virtual electronic control units smart systems engineering: requirements for the standardization of virtual electronic control units (v-ecus) language: en format: pdf (23 pages)

---

White Paper - SmartSE - Virtual Electronic Control Units

72 white-paper recommendations&standards alle 3 2020 en white paper - smartse - virtual electronic control units smart systems engineering: requirements for the standardization of virtual electronic control units (v-ecus) sprache: en format: pdf (23 seiten)

White Paper - SOA4PLM

92 start white-paper alle 3 2008 soa4plm en de white paper - soa4plm möglichkeiten und herausforderungen zum einsatz von soa im plm-umfeld

mehr und mehr wird das unternehmen als ein gefüge vieler einzelner geschäftsfelder betrachtet, deren beziehungen untereinander ebenso kontinuierlichen veränderungen unterworfen werden wie die frage, welche tätigkeitsbereiche intern oder extern anzusiedeln sind. das erweiterte unternehmen ist realität geworden. zusammenschlüsse mit anderen firmen – auch nur projektbezogen – sind genauso an der tagesordnung wie die ausgliederung von teilen eines unternehmens. der daraus resultierenden komplexität und vor allem dem hohen grad an kontinuierlichem wandel in den organisations- und prozessstrukturen werden die in vielen jahren gewachsenen it-strukturen immer weniger gerecht. die umstellung von der bisher üblichen applikationsorientierung auf eine serviceorientierte architektur (soa) wird nun als möglichkeit diskutiert, für diese aufgaben einen besseren lösungsansatz zu finden und verkrustungen zu überwinden. auch und gerade im bereich des produktentstehungsprozesses.

sprache: de & en format: zip-datei

---

White Paper - SOA4PLM

92 start white-paper alle 3 2008 soa4plm en de white paper - soa4plm opportunities and challenges of soa in plm environments

companies are increasingly being viewed as large collections of individual business areas whose relationships to each other are subject to constant change as is the question of which areas should be insourced and which outsourced. the extended enterprise has become reality. consortiums, joint ventures, mergers – some just for the duration of a specific project – are becoming the order of the day in much the same way as corporate spin-offs. the it structures that have grown over the years are less and less able to deal with the resulting complexity and, above all, the high level of continual change in organizational and process structures. the possibility of changing from the traditional application-oriented approach to a service-oriented architecture (soa) is now being discussed as a way of finding a better solution to these tasks and overcoming rigidities – also, and in particular, in the product development process.

language: en & de format: zip file

White Paper - SSB: Kollaboratives Systems Engineering auf Basis von Engineering IT Standards

73 white-paper recommendations&standards alle 2 2019 ssb en de white paper - ssb: kollaboratives systems engineering auf basis von engineering it standards kollaboratives systems engineering auf basis von engineering it standards

das standardization strategy board (ssb) ist ein durch den verband der automobilindustrie (vda) initiiertes projekt des prostep ivip vereins. die projektgruppe ssb wurde 2017 mit der vision gegründet, ein zukünftiges unternehmensübergreifendes systems engineering (collaborative systems engineering - cse) basierend auf engineering it standards zu ermöglichen. dazu werden erstmalig im prostep ivip verein die im umfeld des systems engineering relevanten it standards analysiert, priorisiert und deren reife bewertet, um gemeinsame strategien und handlungsempfehlungen zu deren anwendung und umsetzung abzuleiten. damit soll eine durchgängige abdeckung der im cse-prozess notwendigen geschäftsobjekte und schnittstellen auf basis dieser engineering it standards angestrebt werden.

die motivatoren für die notwendigkeit zur etablierung von engineering it standards liegen auf der hand. die komplexität der produkte und deren interdisziplinarität nehmen dramatisch zu. systems engineering wird zunehmend eingeführt und das arbeiten nach dem v-modell ist immer mehr verbreitet. auf der anderen seite fordert die digitalisierung eine zunehmende kollaboration zwischen unterschiedlichen unternehmen, die von der digitalen wertschöpfungskette profitieren.

sprache: de & en format: zip-datei

---

White Paper - Szandardization Strategy Board

73 white-paper recommendations&standards alle 2 2019 ssb en de white paper - szandardization strategy board collaborative systems engineering on the basis of engineering it standards

the standardization strategy board (ssb) is a project initiated by the german association of the automotive industry (vda) and carried out by the prostep ivip association. the ssb project group was set up in 2017 with the aim of enabling future cross-company systems engineering, i.e. collaborative systems engineering(cse), on the basis of engineering it standards. to do this, the prostep ivip association is for the first time analyzing, prioritizing and evaluating the maturity of the it standards relevant to systems engineering in order to derive common strategies and recommendations for their use and implementation. the objective is to achieve end-to-end coverage of the business objects and interfaces needed in the cse process on the basis of these engineering it standards.
the motivating factors behind the need to establish engineering it standards are obvious. on the one hand, the complexity of the products and their level of interdisciplinarity are increasing dramatically. systems engineering is being used to a growing extent, and working according to the v-model is becoming more and more common. on the other hand, digitalization requires greater collaboration between different companies that benefit from the digital value chain.

language: en & de format: zip file

White Paper - SSB- Results of the "Flow of Software Components" survey

69 white-paper recommendations&standards alle 5 2022 ssb en white paper - ssb- results of the "flow of software components" survey this white paper provides the fosc survey results collaboration processes in software development for the exchange of software components between companies

the requirements relating to how software components are to be handled in collaborative development scenarios are currently often defined individually by companies in the automotive industry. there are no standardized cross-enterprise processes for the development and deployment of software components at carmakers and companies in the supplier industry. against the backdrop of increasing technical and legal complexity in the development of safety-related software, the prostep ivip association has conducted a survey to determine how carmakers and their tier 1/tier 2 suppliers currently handle the development and management of software components and what the current state of the art looks like at the participating companies. the survey, entitled flow of software components (fosc), was organized and conducted by the standardization strategy board (ssb). the standardization strategy board is a joint project group set up by prostep ivip and the vda to address issues relating to the need for standardization in the context of crossenterprise collaboration in product development and manufacturing.

the survey and its results will be used to develop a common understanding of the constraints and shared expectations regarding technical and legal issues between oems and tier 1/tier 2 suppliers. it is also intended that the survey results provide a basis for providing assistance for the future design of cross-enterprise software development in projects.

the survey prepared and conducted by the standardization strategy board comprised a total of 26 questions. some questions were closed-ended with a predefined list of response options, while others provided not only specific predefined response options but also the option of a non-specific response ("other"), which allowed participants to respond in their own words. the original responses are not provided in their entirety here; a summary of the content is provided instead. some questions allowed the selection of multiple response options. in this case, the sum of all the responses may be greater than the number of survey participants. questions that allowed multiple responses are indicated in the caption by ("multiple choice"). as some survey participants may not have answered all of the questions using the predefined response options, the number of responses may be smaller than the number of survey participants. the total number of responses to a question is indicated on the right-hand side of the bar charts/diagrams. questions with predefined responses are displayed as ungrouped, unstacked and non-standardized horizontal bar charts.

the question of oems' expectations regarding supplier response times in the event of software errors with different severity levels from the oems' perspective and the same question from the suppliers' perspective represents a special case. the results of these two questions are displayed together in a matrix and each individual response is represented by a blue or green dot (see figure 8).

the survey involved the participation of 28 people from 19 companies, which can be divided into two groups. 17 respondents (61%) stated that they were employed by a supplier, while 11 respondents (39%) stated that they worked for an oem. figure 1 shows this distribution in a bar chart.

this white paper first of all examines the importance of software as a component for automotive products and the resulting challenges this poses in the context of software development and software component management in the automotive industry. the survey and its key results are then presented.

language: en format: pdf (18 pages)

---

White Paper - SSB- Results of the "Flow of Software Components" survey

69 white-paper recommendations&standards alle 5 2022 ssb en white paper - ssb- results of the "flow of software components" survey this white paper provides the fosc survey results collaboration processes in software development for the exchange of software components between companies

the requirements relating to how software components are to be handled in collaborative development scenarios are currently often defined individually by companies in the automotive industry. there are no standardized cross-enterprise processes for the development and deployment of software components at carmakers and companies in the supplier industry. against the backdrop of increasing technical and legal complexity in the development of safety-related software, the prostep ivip association has conducted a survey to determine how carmakers and their tier 1/tier 2 suppliers currently handle the development and management of software components and what the current state of the art looks like at the participating companies. the survey, entitled flow of software components (fosc), was organized and conducted by the standardization strategy board (ssb). the standardization strategy board is a joint project group set up by prostep ivip and the vda to address issues relating to the need for standardization in the context of crossenterprise collaboration in product development and manufacturing.

the survey and its results will be used to develop a common understanding of the constraints and shared expectations regarding technical and legal issues between oems and tier 1/tier 2 suppliers. it is also intended that the survey results provide a basis for providing assistance for the future design of cross-enterprise software development in projects.

the survey prepared and conducted by the standardization strategy board comprised a total of 26 questions. some questions were closed-ended with a predefined list of response options, while others provided not only specific predefined response options but also the option of a non-specific response ("other"), which allowed participants to respond in their own words. the original responses are not provided in their entirety here; a summary of the content is provided instead. some questions allowed the selection of multiple response options. in this case, the sum of all the responses may be greater than the number of survey participants. questions that allowed multiple responses are indicated in the caption by ("multiple choice"). as some survey participants may not have answered all of the questions using the predefined response options, the number of responses may be smaller than the number of survey participants. the total number of responses to a question is indicated on the right-hand side of the bar charts/diagrams. questions with predefined responses are displayed as ungrouped, unstacked and non-standardized horizontal bar charts.

the question of oems' expectations regarding supplier response times in the event of software errors with different severity levels from the oems' perspective and the same question from the suppliers' perspective represents a special case. the results of these two questions are displayed together in a matrix and each individual response is represented by a blue or green dot (see figure 8).

the survey involved the participation of 28 people from 19 companies, which can be divided into two groups. 17 respondents (61%) stated that they were employed by a supplier, while 11 respondents (39%) stated that they worked for an oem. figure 1 shows this distribution in a bar chart.

this white paper first of all examines the importance of software as a component for automotive products and the resulting challenges this poses in the context of software development and software component management in the automotive industry. the survey and its key results are then presented.

sprache: en format: pdf (18 seiten)

White Paper "Parametrical 3D Data Exchange via STEP"

100 start white-paper alle 8 2007 step en white paper "parametrical 3d data exchange via step" use cases and solutions for parametrical data exchange via step

studies show that approximately 80% of design solutions in the automotive industry are variant designs or adaptations of existing solutions. the full potential for cost and development reduction inherent in variant designs cannot be implemented yet due to restrictions relating to data exchange. fully modifiable designs, including parametric and feature information, cannot currently be exchanged across different cax systems – neither in a standardized nor in a proprietary manner.

some cad vendors offer initial solutions for importing cad models from systems of other vendors while at the same time retaining feature information (e.g. feature recognition in catia v5). but these solutions are unidirectional, and they are neither fully functional nor have they yet been standardized.

several international standards relating to parametrics have recently been published. these are part 55, 108, and 109 of the iso 10303 (step) standard. the objective of the prostep ivip project “parametrical 3d data exchange via step” was therefore to overcome this limitation and enable the exchange of parametric cad models in a standardized (step-based) manner. members of this group were audi, borgwarner turbo systems, daimlerchrysler, delphi, university of applied sciences augsburg, university of applied sciences st. gallen, ptc, prostep, robert bosch, siemens vdo, ugs, volkswagen, zf friedrichshafen et al.

the main results achieved in the “parametrical 3d data exchange via step” project are discussed in the following. this includes a description of the relevant use cases, as well as the experience gained within the context of a comparative analysis. the aim of the analysis was to evaluate the feasibility of a step-based parametric data exchange between leading cad systems.

more detailed information can be found in the final report of the “parametrical 3d data exchange via step” project group, which is available in the download area of the prostep ivip website (www.prostep.org).

language: en format: pdf (10 pages)

---

White Paper "Parametrical 3D Data Exchange via STEP"

100 start white-paper alle 8 2007 step en white paper "parametrical 3d data exchange via step" use cases and solutions for parametrical data exchange via step

studies show that approximately 80% of design solutions in the automotive industry are variant designs or adaptations of existing solutions. the full potential for cost and development reduction inherent in variant designs cannot be implemented yet due to restrictions relating to data exchange. fully modifiable designs, including parametric and feature information, cannot currently be exchanged across different cax systems – neither in a standardized nor in a proprietary manner.

some cad vendors offer initial solutions for importing cad models from systems of other vendors while at the same time retaining feature information (e.g. feature recognition in catia v5). but these solutions are unidirectional, and they are neither fully functional nor have they yet been standardized.

several international standards relating to parametrics have recently been published. these are part 55, 108, and 109 of the iso 10303 (step) standard. the objective of the prostep ivip project “parametrical 3d data exchange via step” was therefore to overcome this limitation and enable the exchange of parametric cad models in a standardized (step-based) manner. members of this group were audi, borgwarner turbo systems, daimlerchrysler, delphi, university of applied sciences augsburg, university of applied sciences st. gallen, ptc, prostep, robert bosch, siemens vdo, ugs, volkswagen, zf friedrichshafen et al.

the main results achieved in the “parametrical 3d data exchange via step” project are discussed in the following. this includes a description of the relevant use cases, as well as the experience gained within the context of a comparative analysis. the aim of the analysis was to evaluate the feasibility of a step-based parametric data exchange between leading cad systems.

more detailed information can be found in the final report of the “parametrical 3d data exchange via step” project group, which is available in the download area of the prostep ivip website (www.prostep.org).

sprache: en format: pdf (10 seiten)

White Paper VEC

86 start white-paper alle 6 2012 ves en de white paper vec vec makes for optimum development processes

forty-one percent of the electronic components currently sold in germany are destined for use in automotive electronics. up to 100 control units are now linked via 2700 contacts in the electrical system of a german premium vehicle. and the importance of vehicle electrical systems is set to rise even further - not only in terms of value added, but also by reason of their complexity. the development of these systems thus calls for a high degree of specialization and division of labor, as well as an increasingly thorough integration of interdisciplinary processes. it is therefore more important than ever that ideas are exchanged with project partners at an early stage.

however, implementation of an end-to-end development process to tackle such tasks has proved impossible to date: the concepts of the respective development processes are simply too varied and diverse. standardization of the data to be exchanged is nevertheless essential if work is to be performed more efficiently. it is the only way of reducing the ever more extensive information, wide range of systems, language regulations and description types to a common denominator and controlling rising development costs.

the above considerations prompted the vda “process chain vehicle electrics“ project group to start addressing these challenges in 2000. the group was made up of representatives from german automotive manufacturers as well as their direct suppliers. its initial aim was to develop definitions and standards solely from the user’s perspective, without having to take existing it solutions into consideration from the outset.

on the other hand, it was a sensible idea to involve system vendors in the process as early as possible. thus the “ecad implementor forum (ecad-if)” was founded at the instigation of prostep ivip that same year, with a view to debating interim results and providing feedback to the vda project group.

this forum now supports system vendors and users in particular with implementations based on vda project group recommendations. expert workshops and webinars are held, sample and test files made available, and vda results marketed by means of information material and tutorials. further information on the prostep ivip association is available at www.prostep.org.

language: en & de format: zip file

---

White Paper VEC

86 start white-paper alle 6 2012 ves en de white paper vec vec sorgt für optimale entwicklungsprozesse

schon heute fließen 41% der in deutschland verkauften elektronischen bauelemente in die kfz-elektronik. so werden im bordnetz eines deutschen premium-fahrzeugs mittlerweile bis zu 100 steuergeräte über 2700 kontakte miteinander verbunden. diese bedeutung der fahrzeugelektrik wird noch weiter steigen – nicht nur hinsichtlich der wertschöpfung, sondern auch auf grund ihrer komplexität. die entwicklung solcher bordnetzsysteme erfordert deshalb ein hohes maß an arbeitsteilung und spezialisierung, sowie eine immer tiefere integration interdisziplinärer prozesse. der frühzeitige austausch mit den projektpartnern wird folglich immer wichtiger.

ein durchgängiger entwicklungsprozess zur bewältigung dieser aufgaben war jedoch bisher nicht zu realisieren: zu vielfältig und unterschiedlich sind die konzepte der jeweiligen entwicklungsprozesse. um dennoch effizient arbeiten zu können, ist eine standardisierung der auszutauschenden daten unabdingbar. nur so sind die immer umfangreicheren informationen, die unterschiedlichen systeme, sprachregelungen und beschreibungsarten auf einen nenner zu bringen und die steigenden entwicklungskosten zu beherrschen.

im jahre 2000 hatte daraufhin die vda-projektgruppe „prozesskette fahrzeugelektrik“ begonnen, sich diesen herausforderungen zu stellen. sie bestand aus den vertretern der deutschen automobilhersteller und deren direkten zulieferern. ihr ziel war, zunächst allein aus anwendersicht definitionen und standards zu entwickeln, ohne von vorn herein auf vorhandene it-lösungen rücksicht nehmen zu müssen.

andererseits war es sinnvoll, systemanbieter bzw. vendoren möglichst früh in diesen prozess mit einzubinden. deshalb wurde auf initiative von prostep ivip noch im selben jahr das „ecad implementor forum (ecad-if)“ gegründet, um hier zwischenergebnisse einfließen zu lassen und der vda-projektgruppe ein feedback zu geben.

dieses forum unterstützt heute vor allem systemanbieter und anwender bei implementierungen, die mittlerweile auf den empfehlungen der vda-projektgruppe basieren. dazu werden experten-workshops und webseminare durchgeführt, beispiel- und testdateien zur verfügung gestellt und die vdaergebnisse mittels informationsmaterialien und tutorials vermarktet. weiterführende informationen des prostep ivip vereins sind unter www.prostep.org zu finden.

sprache: de & en format: zip-datei

White Paper - Wirtschaftlichkeits - betrachtung von IT-Integrationsprojekten

97 start white-paper alle 6 2006 de white paper - wirtschaftlichkeits - betrachtung von it-integrationsprojekten quantitaiver nutzen von it-integrationsprojekten

eine investition in it-integrationsprojekten muss heutzutage aus ökonomischen gesichtspunkten heraus begründet werden – der qualitative nutzen alleine ist nicht mehr ausreichend. häufig konkurriert die anschaffung neuer it-systeme mit anderen investitionsvorhaben, die gleichzeitig an die unternehmensleitung herangetragen werden. das management benötigt daher eine wirtschaftlichkeitsbetrachtung als entscheidungsgrundlage. leistungsfähige methoden und aussagekräftige messkriterien sind notwendig, um den quantitativen nutzen von it-integrationsprojekten zweifelsfrei den anfallenden kosten gegenüberstellen zu können.

der prostep ivip verein hat daher in zusammenarbeit mit siemens business services in der projektgruppe „wirtschaftlichkeitsbetrachtung“ eine methodik zur quantifizierung und qualifizierung des nutzens von it-integrationsprojekten, also deren it-effizienz und it-effektivität, erarbeitet. mit interessierten mitgliedsunternehmen wurden eintägige in-house-workshops durchgeführt, um die methodik zu validieren und um erste praktische erfahrungen im umgang mit der methodik zu sammeln.

dieses white paper erläutet die erarbeitete methodik, gibt einblicke darüber, wie eine wirtschaftlichkeitsbetrachtung durchgeführt werden kann und fasst die erfahrungen aus den in-house-workshops zusammen.

language: de format: pdf (17 pages)

---

White Paper - Wirtschaftlichkeits - betrachtung von IT-Integrationsprojekten

97 start white-paper alle 6 2006 de white paper - wirtschaftlichkeits - betrachtung von it-integrationsprojekten quantitaiver nutzen von it-integrationsprojekten

eine investition in it-integrationsprojekten muss heutzutage aus ökonomischen gesichtspunkten heraus begründet werden – der qualitative nutzen alleine ist nicht mehr ausreichend. häufig konkurriert die anschaffung neuer it-systeme mit anderen investitionsvorhaben, die gleichzeitig an die unternehmensleitung herangetragen werden. das management benötigt daher eine wirtschaftlichkeitsbetrachtung als entscheidungsgrundlage. leistungsfähige methoden und aussagekräftige messkriterien sind notwendig, um den quantitativen nutzen von it-integrationsprojekten zweifelsfrei den anfallenden kosten gegenüberstellen zu können.

der prostep ivip verein hat daher in zusammenarbeit mit siemens business services in der projektgruppe „wirtschaftlichkeitsbetrachtung“ eine methodik zur quantifizierung und qualifizierung des nutzens von it-integrationsprojekten, also deren it-effizienz und it-effektivität, erarbeitet. mit interessierten mitgliedsunternehmen wurden eintägige in-house-workshops durchgeführt, um die methodik zu validieren und um erste praktische erfahrungen im umgang mit der methodik zu sammeln.

dieses white paper erläutet die erarbeitete methodik, gibt einblicke darüber, wie eine wirtschaftlichkeitsbetrachtung durchgeführt werden kann und fasst die erfahrungen aus den in-house-workshops zusammen.

sprache: de format: pdf (17 seiten)