Abstract:
In today's world, information is abundant. No longer are we paced by the time it takes to generate information. Today, our problem is how to deal with all the information we are immersed in. While the information that surrounds us is doubling about every three years, we are challenged to find, organize, and exchange it. Systems Engineering is not exempt from this trend.

A proven approach to this situation is to cast information into a computer interpretable model. If such a model is standardized, it will immensely improve the prospect of its use in commercial tools for the purpose of archiving and exchanging information. Such a standardized model of information relevant to Systems Engineering has been developed. It is referred to as AP233 and it is being developed under the auspices of the International Organization for Standardization (ISO).

This presentation will provide the context for understanding AP233 and detail on its scope and status.

Abstract:
The combination of open-source software and open standards are known to be considered as a key success factor of further technology development. The interest around the STEP standard is growing these last years, since the release of Application Protocols that allow to foresee new software solutions able to ensure a consistent product data description covering the whole lifecycle.

This presentation focuses on the features of a free 3D modeling/data exchange library in the context of a research work dealing with the STEP AP239 standard for PDM/ERP interoperability.

The goal is to merge these two approaches and describe the product from design to manufacturing, with a granularity that allow to keep the control over product configuration.

Abstract:
XACML (eXtensible Access Control Markup Language) can be a good mechanism for making standardized export control decisions.

We have found that it is possible to incorporate export control data (like the DPL and CCL) into XACML policies. We believe that it would be beneficial to continue this work, and involve others from the defense/aerospace industries, as well as the appropriate gov't agencies.

The goals of ECADS are:

1. Seek participation from aerospace and defense industry organizations.

2. Work with the OASIS XACML committee.

3. Define an XACML profile for export control authorization decisions.

4. Engage with the Bureau of Industry and Security to publish the authoritative data to include in the XACML ECADS profile.

5. Encourage software vendor adoption of XACML ECADS profile.


My motivation to present this at PDE 2009 is to generate interest and participation in the ECADS project among the PDE attendees.

Abstract:
ICE is a web-centric environment which will be used by industry, academia and government for: sharing, collaborating, integrating, accessing and controlling management information and product data defining all of the products which are part of Exploration Systems.

As part of this environment the program has been focused on creating a Service Oriented Architecture (SOA) that allows NASA to reuse and make accessible functionality that exists within the environment. The goal is to define services that provide access to this functionality in a manner that is standards based and focuses on interoperability. The data exchange will provide an interface for delivery of data and a program interface for collaborating on different aspects of NASA products through their life cycle.

Abstract:
Presented work is focused on design model communicating between CAD and CAE systems, CATIA v5 and GEANT4 in our case.
GEANT4 is a toolkit for the simulation of the passage of particles through matter, requiring a lot of geometrical calculations. Such calculations are fast enough only if relatively simple analytical formulae can be used. For this reason a solid body should be described as a Boolean combination of predefined primitives having analytical descriptions of all the geometrical features.
ISO 10303 STEP functionality allows to represent (CSG) model, but for some reasons there are no commercially-available STEP pre-processors generating CSG models.
So beside GEANT STEP post-processor new alternate STEP pre-processor have to be developed for existing CAD. Our approach to converters (STEP pre- & post-processors) is two divide converter source to two counter-parts: invariant STEP data handler and application-dependent handler of proprietary model.

Abstract:
Nowadays aerospace industries are faced with fundamental changes in the field of product documentation and information management. New technologies and the requirement for concurrent engineering oblige modern aircraft builders to implement and operate model based product data management techniques. In addition to this well-structured information aerospace industry is challenged to manage unstructured information, such as technical documents created and maintained in the office environment. The joint EADS-Jotne OPDIM project proposes a new direction by deploying ISO 10303-239 PLCS, Product Life Cycle Support.

The key challenge is to relate both structured and unstructured worlds of technical product documentation in a global business environment during the entire lifecycle. The OPDIM project aims to solve this issue by introducing a standards based information integration backbone for both technical data for design and lifecycle data for operation and support.

Abstract:
We are happy to announce that the next NASA/ESA PDE Workshop will be held May 18 - 20, 2010, in Oslo, Norway -- we hope to see you there!

Abstract:
A product design describes a class of implementations or realizations of the design. OWL 2, a logic based knowledge representation languages, is used for representing product designs. A design is represented in OWL as a Knowledge Base (KB). However, OWL 2 presents difficulties in constraining the possible models of the design KB. Description Graph extensions of OWL have been proposed as a solution to the problem of constraining the KB models. An alternative approach for representing detailed designs in OWL without using the explicit DG extension is explored. The approach use a property for roles, called edge which is not part of OWL 2. An edge role is used to represent structural relations of a design. A description graph can be defined from the edge roles. This OWL extension has the expressiveness of SysML block diagrams and provides a partial unification of SysML and OWL. A simple design modelling example is used to illustrate the OWL extension.

Abstract:
We will report on progress made in research and development activities on enabling Model Based Systems Engineering and related data exchange standardization at ESA.

Topics:

- European Cooperation for Space Standardization (ECSS) developments to support MBSE for space applications. First releases of ECSS E-TM-10-23 for a full conceptual data model for the space system life cycle, and E-TM-10-25 for model exchange between concurrent engineering facilities for the conceptual design phase.

- Use and upgrades of OMG SysML for space.

- Upgrade of STEP-TAS and TASverter for full exchange of ESATAN and SINDA thermal analysis models including user-defined logic. A generic neutral representation has been developed that may also be of interest to other exchange protocols for models containing user-defined algorithmic parts.

- Status of implementation of STEP-TAS interfaces in the established space thermal analysis tools ESATAN-TMS/ESARAD, THERMICA, CORATHERM/CIGAL and TMG.

Abstract:
After a long involvement in standards development, Eurostep have had customers using a standards based collaboration tool for the last 8 years. The initial objective was to support collaborative design across an extended enterprise. Since then the emphasis has moved to enabling data orchestration and change management across heterogeneous systems. This shift has matched the movement in the standards through the introduction of STEP standards for Product Life Cycle Support and Systems Engineering data. Technology has also shifted and the arrival of Web Services has opened up the possibilities to take advantage of the collected information in the hub. The presentation will review the different business problems being solved, illustrated using specific cases, the lessons learned since 2001 and review the trends in the data standards and in data centric collaboration.

Abstract:
A short introduction to PLCS covering key messages.

Abstract:
The relationship between design data and analysis data can be a complex one. It can be further complicated if physical experiments, such as wind tunnel experiments, are used too. Increasingly both the analyses and the experiments are outsourced to other organizations. Models are created based on variations of geometry and provided to other organizations. The resulting process lacks memory so work can be repeated unecessarily and opportunities to optimize are missed. Where a lot of variations are being tested, traceability can easily be lost.
Eurostep is part of a UK Government funded project around improved Computational Fluid Mechanics (CFMS). As part of the CFMS project Eurostep worked with other CFMS member companies on applying a collaborative hub to provide more effective extended enterprise design validation. The result is smarter working, more re-use and better communication using a standards-based hub and accessing it through the PLCS PLM web services.

Abstract:
T. Charles Chen, Ph.D.
Terry McGowan
Boeing Research and Technology

CAD data exchange technologies and standards are integral to a lean MBD (model based definition) environment. Heterogeneous environments will continue to present challenges in capturing, managing and distributing MBD CAD product authority.

What does MBD (Model Based Definition) data exchange mean? What data exchange challenges must be recognized to enable lean practices? What solutions and work arounds exist?

The speakers will discuss high level subject matter on MBD data exchange concepts and best practices. The classification of consumable and collaborative data type formats and their use in heterogeneous environments will be covered. New capabilities in MBD data exchange will be introduced, this includes Adobe Acrobat 3D for collaboration, and STEP AP203 E2 for sharing GD&T information.

Finally information for the upcoming 2009 Boeing Product Data Exchange Conference will be shared with the audience.

Abstract:
Model-based enterprise (MBE) processes are undermined if the model is not validated at critical transitions in the product lifecycle. At design release it must not contain any defects which impede downstream reuse. Any translation or conversion into a derivative form must be equivalent. Design revisions must not introduce unintentional changes; and intentional changes must be clearly communicated. The model must be preserved in an accurate, reusable form for the life of the product--often well beyond the life of the design system. In each case, validation must include model structure, shape, dimensions and tolerances.

This presentation will overview how these principles have been applied in recent model validation implementations at NASA Marshall and Boeing Space in support of the Constellation Program. Attendees will learn best practices and pitfalls to avoid.

Abstract:
Collaborative design & analysis of complex systems requires an open standards-based framework that: (1) provides flexible control & fine-grained integration of multiple analysis models to system design models and databases, and (2) enables system & domain engineers to plug-and-play their design & analysis models formulated in COTS tools. OMG SysML is rapidly emerging as the open standard for representing & integrating system design and analysis models. Parametrics (subset of SysML) provides the constructs to model fine-grained relationships between model parameters.

In this presentation, a conceptual model of such a framework--founded on SysML & other open standards--will be presented. A Parametrics-based Solver Manager (SM) is presented as the first tool in this framework. SM interfaces SysML modeling tools (e.g. MagicDraw) with math solvers (e.g. Matlab/Simulink & Mathematica) and spreadsheets thereby enabling requirements verification and system validation.

Abstract:
Designing complex products around integrated electronics requires a high-tech toolset and tight ECAD/MCAD/CAE collaboration. This session will show you how printed circuit model, rigid and flexible can be quickly and easily designed in NX environment, how the model can be further refined by using the PCB.xchange product for attribute information and transmission of the model to an ECAD system. The final ECAD design will be used to associatively update the NX assembly using PCB.xchange. PCB.xchange updates the 3D NX assembly automatically. The resulting NX assembly is not limited to the basic data only: the board, components, holes, keepin and kepout regions, but contains also more information, like traces, pads, masks, etc. The NX assembly can then be efficiently used for mechanical design review, assembly and tolerance analysis, as well as detailed structural, thermal and flow simulations within the same environment.

Abstract:
This presentation will provide an introduction to the lightweight 3D JT file format and will show the components that make up a JT file. Also discussed will be how JT is used by various companies for collaboration, visualization, digital mockup, long-term data retention and CAD neutral interoperability. An introduction to the JT Open program will be given and how that program has driven Siemens PLM Software to make the JT format an open, published file specification and also begin the process to obtain ISO certification for JT.

Abstract:
Based on a "Composite Evolution" presentations given at Boeing Data Exchange Conferences and some concepts developed working with the STEP community - Boeing teamed with Lockheed Martin,
and Adobe to kick off a pilot program through PDES Inc. The primary objective was to demonstrate taking an explicit composite design from CATIA on to an AP203E2 representation and then interrogate the model in a "free" ADOBE viewer. This presentation will review where we have been, show the current status of the effort and outline the goals and objectives of follow on Phases.

Abstract:
There is a new Earned Value Management (EVM) data standard for program management composed of XML schemas for reporting cost and schedule information. It supports common formats that program offices, prime contractors and multiple tiers of suppliers use for data exchange and analysis. In this presentation, we describe how we are mapping this EVM standard into the STEP AP233 Systems Engineering information model using reference data so that we can relate cost and schedule with engineering artifacts such as requirements, system structure/interfaces, behavior, etc. The engineering information is also mapped into AP233 using reference data for DoDAF and SysML models. This integration of engineering and program management will enable the exchange of cost and schedule information with their related engineering artifacts, as well as analysis and prediction of cost and schedule as a function of the engineering artifacts and their complexity.

Abstract:
Increasingly, enterprises are moving towards Service Oriented Architectures (SOA) and the use of semantics, ontologies and Semantic Web technologies to provide this efficiency. Enabling reuse and interoperability between these technologies is a critical requirement. ISO TC184 SC4 Industrial Data standards have been in development for two decades and provide rich source of consensus-based domain-specific information models. Adapting the best of that work can be a big step down the path of integrated information management for many engineering enterprises.

This talk will describe NIST-funded efforts to investigate suitability of OMG/W3C technologies for use by ISO TC184/SC4. This project is defining a process and implementing migration tools enabling enterprises to adopt/adapt STEP for their software systems integration needs. A reference example within the Systems Engineering domain will be used to execute the harvesting process using the migration tools, thereby validating both.

Abstract:
Authors:
Paul Downing, Andreas Schreiber, Matthias Grau

Outline:
- OMG PLM Services intro
- What is new with v2.0?
- Implementation by PROSTEP: OpenPDM
- Aims - Scenarios
- Architecture
- Available Connectors (PDM, SDM, ERP, Req.Mngmt. ...)
- Technology
- References

Abstract:
The electronics industry is experiencing a global trend of increased environmental regulations. Countries around the world are establishing environmental regulations all designed to protect human health and the environment. To help with this issue, NIST developed a UML data model to address the underlying material declaration problem associated with establishing product material composition. This data model was used in the development of IPC's 1752 Material Declaration standard. IPC 1752 version 1 was created with a focus on EU RoHS and now that industry is faced with a multitude of new environmental legislations and regulations. To address this problem, NIST has developed an updated model for IPC 1752 version 2.0. This model has a larger scope and is more modular making it better suited to address regulations beyond RoHS and be integrated into stakeholder data management systems. This paper looks at the data models used in both version of IPC 1752 and highlights the differences.

Abstract:
This presentation describes a system in production that implements model-based interoperability between cross-domain engineering functions thereby enabling enhanced communication among the multiple disciplines and across the supply chain. By focusing on interoperability between engineering functions and not just interoperability between tools, the value of business operations is increased. Producibility engineers are part of the design team and yet need a different design environment than the electrical designers. The producibility engineering design environment needs to execute sophisticated analysis algorithms in a timely manner to provide corrective action requests to electrical designers as well as provide an appropriate graphical user experience. The content of the AP 210 product model includes significantly more data types than available from a traditional ECAD tool in order to support the communication requirements between producibility engineers and electrical designers.

Abstract:
The Constellation Data Architecture (CxDA) uses the NASA Exploration Initiative Ontology Models (NExIOM) ontologies for Metadata and Data Exchange. NExIOM addresses the challenges of establishing common vocabularies for administrative, governance, provenance, and associative metadata in different systems; and interoperability between tools and applications through semantic alignment of XML-based approaches. CxDA comprises specifications for Naming and Identifier Rules, Data Types, Information Structures and Algorithms and Equations. Controlled vocabularies can be expressed in RDF/OWL, XML and ASN.1, examples are Units, Quantities, Dimensions and System Properties. Ontologies are used to generate XML Schemas using a new language, XML SchemaPlus, that provides additional OWL semantics. Examples of vocabularies and other work-products are given for telemetry and commanding. SysMO, a System Ontology for SysML, and the use of ontology-based interoperability between tools are also covered.

Abstract:
Concurrent Engineering in Aircraft programs is crucial to manage engineering data (ED) & processes in heterogeneous software environment of Extended Enterprise.
Role of such collaborative platforms is to enable interoperability, relationship & traceability of ED along aircraft life cycle, beyond scope of static Digital Mock-up (DMU) representation, limited to necessary & not sufficient CAD domain objects.
Management of full ED model for Aero Industry is addressed by Engineering Data Management (EDM) development along European 6th Framework Project VIVACE. PDM approach was expanded with broader EDM scope in 3 domains:
Requirements related to product capabilities, performance.
Product information
Simulation
EDM developed innovative framework expanding DMU-oriented data management to entire distributed modeling & simulation.
Exposing EDM results we conclude on perspectives VIVACE industrialization offer with STEP & OASIS PLCS DEX applied to Model Based Collaborative applications.

Abstract:
After nearly two decades with many false-starts, High Level Synthesis (HLS) is now being adopted steadily and incrementally by most of the world's leading semiconductor companies. This presentation will survey the requirements for building a High Level Synthesis (HLS) methodology/flow that integrates seamlessly with today's standard RTL design flow targeting ASICs and FPGAs. In particular, we will focus on the criteria for maximizing the three main goals of the resulting ESL-to-GDSII flow: accelerating IP creation with fewer bugs; automating IP reuse by separating functionality and constraints; and enhancing IP optimization in terms in area/power/performance via automated micro architecture exploration. This presentation will make extensive use of real-world case studies to make the case that the electronics industry will soon see a broad-scale transition from RTL-driven to TLM-driven design.

Abstract:
Delivering innovative electromechanical designs is challenging for even the most experienced teams. Communicating design changes between disparate electrical and mechanical design solutions can be cumbersome and inefficient. Coordinating design efforts between functionally or geographically dispersed teams adds even more complexity to the challenge. The Pro/ENGINEER ECAD-MCAD Collaboration Extension can help you overcome these obstacles and improve design collaboration between electrical and mechanical designers. PTC is the only MCAD vendor offering this new technology, which leverages both Pro/ENGINEER and ProductView. This technology will help you improve your electromechanical detailed design processes, reduce collaboration errors, and get products to market faster.

Benefits:
-Next generation technology enhances today's IDF-based flows to identify changes and collaborate on incremental changes
-Enable mechanical and electrical engineers to communicate faster, more frequently and with less disruption
-Identify and manage unforeseen consequences of a change across disciplines earlier to reduce late-stage changes
-Enable mechanical engineers to better understand the impact on electrical designs, before they propose a change
-Communicate design changes faster with the ability to show incremental changes and cross-highlight between MCAD and ECAD model views
-Propose, accept, or reject changes synchronously or asynchronously

Abstract:
Gartner's three year study of Product Lifecycle Management (PLM) practices across more than 60 companies in 7 manufacturing verticals reveals that the most successful deployments of Product Lifecycle Management software and practices requires properly balanced configurations of business level planning and technology toolsets. The presentation will share findings and best practices uncovered from this study as well as inquiries from Gartner's Aerospace and Defense (A&D) clients and suggest how they can be adapted to the A&D industry in light of Information Technology trends and developments in the market for PLM software and standards such as ISO STEP.

Abstract:
From conception to completion, the decision to adopt a re-use methodology requires careful planning. Identifying building blocks for future products and defining the correct design, implementation and management strategy is crucial for success. This presentation outlines the methodology behind modular processes used successfully by existing Cadence customers. Examples will be shown that were regarded as key milestones during radical changes to the traditional 'front to back' design process. Practical examples provide a valuable insight into achieving major design time reductions for the latest generation of Engine Management Systems for today's high efficiency airframes.

Abstract:
The Pan Galactic Engineering Framework is an open-source, open-architecture, standards-based software framework being developed as a toolkit for creating engineering support applications. Its primary purpose is to provide tools for the integration of data from a variety of engineering tools into a synthesized system-level schema, import/export via domain views, and integration with knowledge-based engineering applications. This presentation will describe its technology vision, specific goals, current state, and development roadmap.