Enriching STEP Product Model With Geometric Dimension and Tolerance Information for One-Dimensional Tolerance Analysis

2017 ◽  
Vol 17 (2) ◽  
Author(s):  
Mehmet I. Sarigecili ◽  
Utpal Roy ◽  
Sudarsan Rachuri
Keyword(s):  
Information Exchange ◽  
Information Structure ◽  
Data Exchange ◽  
Geometric Dimension ◽  
Tolerance Analysis ◽  
Product Model ◽  
Functional Activities ◽  
Information Models ◽  
Small Set ◽  
Rapid Pace

Information exchange and sharing become a necessity for digital factory but they have been more challenging as the industry is computerized more. This is mainly because the capabilities of computerized systems have grown significantly in a very rapid pace in their own information structure, and they require to retrieve various data from different computer systems. ISO 10303–STEP has been developed to provide a neutral format for exchanging product data. However, implementation of STEP has several issues, including the following two: (1) the complete STEP file should be processed even for querying a small set of data, and (2) information required for realizing any functional activity (e.g., any analysis on any part of a product) is not explicitly identified. Hence, in this study, functionality-based conformance classes (FCCs) are developed to organize the current conformance classes (CCs) (which are the classes required to be implemented fully in order to be conformant to any particular STEP standard) for supporting different functional activities. Following the concept of data exchange specification (DEX)/template, several templates that are repeatedly used small information groups are introduced in order to create manageable sets of data constructs. In this study, the FCCs for 1D tolerance analysis are developed by enriching the available STEP information models with GD&T. The use of extended STEP models is illustrated with a case study.

scholarly journals DATA-flow in the field of urban planning: basics, concept, methodology

2021 ◽  
Vol 258 ◽  
pp. 09054
Author(s):  
Pavel Chelyshkov ◽  
Sergey Volkov ◽  
Evgeny Babushkin
Keyword(s):  
Life Cycle ◽  
Urban Planning ◽  
Information Exchange ◽  
Data Exchange ◽  
Data Flow ◽  
Digital Information ◽  
Information Models ◽  
Exchange Processes ◽  
Capital Construction ◽  
Exhaustive List

This article discusses the basics, concept and methodology for constructing tools that implement data exchange processes, including an exhaustive list of necessary data for the formation of information models of capital construction objects at each stage of the life cycle, as well as a plan for the development of these tools that provide information exchange processes. The technical and technological foundations for the formation of a digital information model and a scheme for verifying information transmitted from stage to stage of the life cycle of a capital construction object are stated.

Data Probe: A Tool for EXPRESS-Based Data

1993 ◽  
Author(s):  
K. C. Morris
Keyword(s):  
Software Architecture ◽  
Data Storage ◽  
Data Exchange ◽  
Conceptual Modeling ◽  
General Purpose ◽  
Product Model ◽  
Development Environment ◽  
Information Models ◽  
Share Data ◽  
Application Protocols

Abstract The problem of sharing data has many facets. The need to share data across multiple enterprises, different hardware platforms, different data storage paradigms and systems, and a variety of network architectures is growing. The emerging Standard for The Exchange of Product Model Data (STEP), being developed in the International Organization for Standardization (ISO), addresses this need by providing information models, called application protocols, which clearly and unambiguously describe data. The validity of these information models is essential for success in sharing data in a highly automated engineering environment. This paper describes the Data Probe: a tool for examining, editing, and managing EXPRESS-based data. The Data Probe tool supports the validation of STEP application protocols. The paper includes a description of the software architecture, the initial implementation, and plans for future enhancements. The software is designed as independent components which can be incorporated into other STEP-related systems or software requiring general purpose editing tools for structured information. The initial version of the Data Probe tool is based on two implementation mechanisms defined within STEP: the conceptual modeling language EXPRESS and the STEP exchange file format. Future work will focus on integrating a database system into the software. The software architecture and the use of object-oriented techniques enables code reusability and system extensibility and has been instrumental for a phased implementation. The software is under development at the National Institute of Standards and Technology and is in the public-domain. The software supports the Validation Testing System, part of the Application Protocol Development Environment, at the CALS-sponsored National PDES Testbed. (PDES, Product Data Exchange using STEP, is the U.S. effort in support of the international standard.)

Product Information Exchange Using Open Assembly Model: Issues Related to Representation of Geometric Information

2005 ◽  
Author(s):  
Mehmet Murat Baysal ◽  
Utpal Roy ◽  
Rachuri Sudarsan ◽  
Ram D. Sriram ◽  
Kevin W. Lyons
Keyword(s):  
Information Exchange ◽  
Information Structure ◽  
Product Information ◽  
Unified Modeling Language ◽  
Product Development Process ◽  
Assembly Model ◽  
Object Constraint Language ◽  
Product Model ◽  
Geometric Information ◽  
Assembly Features

The objective of this paper is to discuss the main issues for product information exchange through the Open Assembly Model (OAM). The OAM model provides a base level product model that is open, simple, generic, expandable, independent of any vendor software and product development process, and capable of engineering context that is shared throughout the product lifecycle. Two of the main issues in the OAM model are the representation of geometric information of the artifacts (and assembly features) and maintenance of the consistency of the product information among relevant classes based on geometry information. This paper considers the geometry information at three levels: 1) basic geometric information of artifact with position and orientation information, 2) assembly features and their interrelations, and 3) detailed geometric information of all features in the artifact. In addition to geometric information, other relations/associations between the classes in the Unified Modeling Language (UML) based OAM model are maintained by constraints written in Object Constraint Language (OCL). This information structure in the UML and OCL is then mapped into the Extensible Markup Language (XML) for easy information exchange. XML is commonly used and supported by many softwares. Therefore, integration of XML with UML will provide an excellent tool for internet based collaboration.

scholarly journals Maturity assessment of Kenya’s health information system interoperability readiness

2021 ◽  
Vol 28 (1) ◽  
pp. e100241
Author(s):  
Job Nyangena ◽  
Rohini Rajgopal ◽  
Elizabeth Adhiambo Ombech ◽  
Enock Oloo ◽  
Humphrey Luchetu ◽  
...  
Keyword(s):  
Health Information ◽  
Information Exchange ◽  
Working Group ◽  
Data Exchange ◽  
Enterprise Architecture ◽  
Health Information Exchange ◽  
Digital Health ◽  
Health Information System ◽  
Maturity Level ◽  
Technical Standards

BackgroundThe use of digital technology in healthcare promises to improve quality of care and reduce costs over time. This promise will be difficult to attain without interoperability: facilitating seamless health information exchange between the deployed digital health information systems (HIS).ObjectiveTo determine the maturity readiness of the interoperability capacity of Kenya’s HIS.MethodsWe used the HIS Interoperability Maturity Toolkit, developed by MEASURE Evaluation and the Health Data Collaborative’s Digital Health and Interoperability Working Group. The assessment was undertaken by eHealth stakeholder representatives primarily from the Ministry of Health’s Digital Health Technical Working Group. The toolkit focused on three major domains: leadership and governance, human resources and technology.ResultsMost domains are at the lowest two levels of maturity: nascent or emerging. At the nascent level, HIS activities happen by chance or represent isolated, ad hoc efforts. An emerging maturity level characterises a system with defined HIS processes and structures. However, such processes are not systematically documented and lack ongoing monitoring mechanisms.ConclusionNone of the domains had a maturity level greater than level 2 (emerging). The subdomains of governance structures for HIS, defined national enterprise architecture for HIS, defined technical standards for data exchange, nationwide communication network infrastructure, and capacity for operations and maintenance of hardware attained higher maturity levels. These findings are similar to those from interoperability maturity assessments done in Ghana and Uganda.

Semantic Interoperability of GD&T Data Through ISO 10303 Step AP242

2016 ◽  
Author(s):  
Adarsh Venkiteswaran ◽  
Sayed Mohammad Hejazi ◽  
Deepanjan Biswas ◽  
Jami J. Shah ◽  
Joseph K. Davidson
Keyword(s):  
Data Exchange ◽  
Smart Manufacturing ◽  
Context Model ◽  
Product Model ◽  
Shape Information ◽  
Computer Aided Process Planning ◽  
Model Based ◽  
Computer Aided ◽  
Iso 10303 ◽  
Manufacturing Applications

Industries are continuously trying to improve the time to market through automation and optimization of existing product development processes. Large companies vow to save significant time and resources through seamless communication of data between design, manufacturing, supply chain and quality assurance teams. In this context, Model Based Definition/Engineering (MBD) / (MBE) has gained popularity, particularly in its effort to replace traditional engineering drawings and documentations with a unified digital product model in a multi-disciplinary environment. Widely used 3D data exchange models (STEP AP 203, 214) contains mere shape information, which does not provide much value for reuse in downstream manufacturing applications. However, the latest STEP AP 242 (ISO 10303-242) “Managed model based 3D engineering” aims to support smart manufacturing by capturing semantic Product Manufacturing Information (PMI) within the 3D model and also helping with long-term archival. As a primary, for interoperability of Geometric Dimensions & Tolerances (GD&T) through AP 242, CAx Implementor Forum has published a set of recommended practices for the implementation of a translator. In line with these recommendations, this paper discusses the implementation of an AP 203 to AP 242 translator by attaching semantic GD&T available in an in-house Constraint Tolerance Graph (CTF) file. Further, semantic GD&T data can be automatically consumed by downstream applications such as Computer Aided Process Planning (CAPP), Computer Aided Inspection (CAI), Computer Aided Tolerance Systems (CATS) and Coordinate Measuring Machines (CMM). Also, this paper will briefly touch base on the important elements that will constitute a comprehensive product data model for model-based interoperability.

scholarly journals Nova Genesis - An Advanced Architecture for Internet of Things

2020 ◽  
Vol 9 (1) ◽  
pp. 1661-1666
Keyword(s):  
Information Exchange ◽  
Data Exchange ◽  
Service Oriented Architecture ◽  
Future Internet ◽  
Limiting Factor ◽  
Efficient Storage ◽  
Efficient Data ◽  
Service Oriented ◽  
New Applications ◽  
Control Management

The Internet has become the most important medium for information exchange and the core communication environment for business relations as well as for social interactions. The current internet architecture itself might become the limiting factor of Internet growth and deployment of new applications including 5G and future internet. Architectural limitations of internet include weak security, lack of efficient storage and caching, data distribution and traceability issues, lack of interoperability and so on. The proposed system overcomes these limitations by an alternate architecture for internet called NovaGenesis. This architecture integrates the concepts of Information Centric Networking (ICN), Service Oriented Architecture (SOA), network caching and name based routing. ICN evolve internet from a host-centric model to a content-centric model through efficient data exchange, storage and processing. SOA enables software-control/management of network devices based on service requirements. Network caching improves performance in terms of throughput, network traffic and retrieval delay. Name based routing is for discovering and delivering of data. The framework proposed increases the scalability and reliability of the delivery of IoT data for services.

The Establishment and Management of a Production Data Exchange Group

2005 ◽  
Vol 21 (02) ◽  
pp. 73-80
Author(s):  
Gregory F. Morea
Keyword(s):  
Data Exchange ◽  
Production Data ◽  
Computer Assisted ◽  
Product Model ◽  
Aircraft Carrier ◽  
Exchange Group ◽  
Digital Format ◽  
Marine Industry ◽  
The Future ◽  
Design And Construction

The design and construction of any marine vessel designed on a computer-assisted design (CAD) system, from a nuclear aircraft carrier to the smallest work boat, requires the interaction of many electronic databases, all of which must be continually updated for the work to proceed. The exchange of this information, especially geometry, in digital format is accomplished using many different tools and techniques. Much has been presented to the marine community about the tools used, such as the Initial Graphics Exchange Specification (IGES) and the Standard for the Exchange of Product Model Data (STEP), and how these tools might be used for exchanges in the future, but little has been presented on how production data exchanges actually occur. At Electric Boat, current submarine programs cannot wait for future data transfer solutions. Design and construction data must be exchanged among various activities, internal and external, with such volume as to make manual reentry of data an unrealistic solution. Because of the complexities associated with the electronic exchange of these data, the General Dynamics (GD) Marine organization of Electric Boat has a dedicated group that both performs production data exchanges and researches and implements new methods of electronic transfer. This paper discusses the rationale for and the formation of the data exchange group at Electric Boat, along with its place within GD Marine. It then presents an overview of the tools used by the group and how production transfers occur, both routine and unique. Notable transfers provide examples of how the group works to solve transfer problems. Importantly, this paper shows how many of the exchange standards developed for the marine industry actually work in production. Special emphasis will be placed on the exchange of solid models in a day-to-day environment. The paper concludes with a look at the future of production data exchanges for Electric Boat and the larger marine industry.

An Engineering Product Model Based on STEP Protocols

1994 ◽  
Vol 10 (04) ◽  
pp. 281-296
Author(s):  
James T. Higney ◽  
Joanne J. Ouillette
Keyword(s):  
Information Content ◽  
Computer Aided Design ◽  
Data Exchange ◽  
Digital Data ◽  
Product Model ◽  
Engineering Product ◽  
Significant Step ◽  
Cad Models ◽  
Application Protocols ◽  
Graphic Database

Draft STEP (Standard for the Exchange of Product Model Data) application protocols, developed by the Navy Industry Digital Data Exchange Standards Committee (NIDDESC), have been issued to define the information content of a product model for a ship. The work reported in this paper combines the existing CAD models of the DDG51 Class design with a newly developed non-graphic database so that the overall information content complies with the STEP protocols. This work represents the first-time implementation of the application protocols and is a significant step in the Navy's plan to do the design of variants of the DDG51 Class totally in computer-aided design (CAD). The combined graphic/non-graphic database is referred to as the DDG51 engineering product model. Emphasis has been placed on populating the non-graphic database with the information necessary to perform all required engineering analyses. The basic schema described in this paper may be extended to support other areas of interest, such as logistics support.

Modeling of Feature-Based Design Process

1998 ◽  
Author(s):  
Fei Gao ◽  
Dieter Roller
Keyword(s):  
Design Process ◽  
Data Exchange ◽  
Concurrent Design ◽  
Product Model ◽  
Product Data ◽  
Product Models ◽  
Critical Issues ◽  
Feature Based ◽  
Feature Based Design ◽  
Feature Evolution

Abstract Capturing design process is becoming an important topic of feature-based modeling, as well as in product data exchange, concurrent design, and cooperative design. Three critical issues on the modeling of design process are considered in this paper, namely, feature concepts, feature evolution, and the semantic consistencies of the states of product models. A semantics-based product model is introduced to facilitate the description of both conceptual and detailed models, and to maintain the semantic consistencies of product states. The process is represented by feature states and their evolution records. Feature type variation and prototype-based design are proposed to support feature evolution. A conceptual description of the design process and an example are given.

Sign in / Sign up

Export Citation Format

Share Document