Enhancement of product development through product information mark-up language

2005 ◽  
Vol 16 (1) ◽  
pp. 91-110 ◽  
Author(s):  
C. K. M. Lee ◽  
H. C. W. Lau ◽  
K. M. Yu ◽  
W. H. Ip
Keyword(s):  
Product Development ◽  
Product Information

Product development platform for real-time capture and reuse of evolving product information

2007 ◽  
Vol 2 (3) ◽  
pp. 207 ◽  
Author(s):  
Amaresh Chakrabarti ◽  
Srinivas Kota ◽  
Nageshwar Rao ◽  
Sekhar Chowdary
Keyword(s):  
Product Development ◽  
Real Time ◽  
Product Information ◽  
Development Platform

scholarly journals Reconciling Quality by Design and Transdermal Product Development

Pharmaceutics ◽  
2020 ◽  
Vol 12 (3) ◽  
pp. 273
Author(s):  
Kenneth Miller
Keyword(s):  
Product Development ◽  
Quality By Design ◽  
Experimental Approach ◽  
Product Information ◽  
New Product ◽  
Years Of Experience ◽  
Regulatory Review

Since my first exposure to the acronym ‘QbD’ more than ten years ago, I have been trying to understand exactly what QbD is and how I might incorporate its teachings into my twenty-odd years of experience developing transdermal systems. I feel I have made little progress since then. Eventually, I came to realize that while QbD has its merits, it is not a guide for (transdermal) product development, despite so often being described as such. Instead, I have come to consider QbD as a language useful for organizing and presenting the array of data supporting the approval of a new product, but it still leaves the experimental approach entirely up to the developer. What QbD does provide to the development community is a means of conveying product information through a consistent framework facilitating both internal and regulatory review. As a result, new ‘QbD’ product applications tend to be more uniform and complete than the applications that preceded the initiative.

scholarly journals Neglecting genetic diversity hinders timely diagnosis of Cryptococcus infections

2021 ◽  
Author(s):  
Dongmei Shi ◽  
Pieter-Jan Haas ◽  
Teun Boekhout ◽  
Rosane C. Hahn ◽  
Ferry Hagen
Keyword(s):  
Genetic Diversity ◽  
Early Detection ◽  
Product Development ◽  
Effective Treatment ◽  
Cryptococcus Neoformans ◽  
Product Information ◽  
Point Of Care ◽  
False Negative ◽  
Point Of Care Test ◽  
Species Complexes

Over a decade ago the first cryptococcal lateral flow assay (LFA) became available. This affordable point-of-care test has undeniably led to tremendous improvements in early detection of cryptococcosis (1,2). However, from several studies it must be concluded that the reliability of recently introduced LFA’s falls short, thereby negatively impact timely detection and thus hinders an effective treatment of cryptococcal infections (3-6). The apparent reduced performance of newly commercialized cryptococcal LFA’s might be caused by ignoring the genetic diversity as manufacturers focus on the four serotypes A-D. While the first commercially available cryptococcal LFA (IMMY Diagnostics, Norman, OK, U.S.A.) was extensively evaluated (1,7), this seems not the case with LFA’s from other manufacturers as their product information indicates that only one strain per serotype was used for product development. The observation of neglecting the genetic diversity within the Cryptococcus gattii/Cryptococcus neoformans species complexes, combined with reports of false-negative LFA’s not related to the pro/post-zone effect (8-10) inspired us to compare commercially available LFA’s to a set of well-defined strains that reflects the genetic diversity within the C. gattii/C. neoformans species complexes.

A Foundation for Interoperability in Next-Generation Product Development Systems

2000 ◽  
Author(s):  
Simon Szykman ◽  
Steven J. Fenves ◽  
Walid Keirouz ◽  
Steven B. Shooter
Keyword(s):  
Product Development ◽  
Product Information ◽  
Computer Aided Engineering ◽  
Next Generation ◽  
Development Environment ◽  
Feed Forward ◽  
Engineering Software ◽  
Computer Aided ◽  
Cad Cam ◽  
The Cost

Abstract U.S. industry spends billions of dollars as a result of poor interoperability between computer-aided engineering software tools. While ongoing standards development efforts are attempting to address this problem in today’s tools, the more significant demand in next-generation tools will be for representations that allow information used or generated during various product development activities to feed forward and backward into others by way of direct electronic interchange. Although the next generation of tools has the potential for greatly increased benefits, there is also a potential for the cost of poor interoperability to multiply. The goal of this work is to develop representations of information that are unavailable in traditional CAD/CAM/CAE tools to support the exchange of product information in a distributed product development environment. This paper develops a vision of next-generation product development systems and provides a core representation for product development information on which future systems can be built.

Assessing Multimedia Content Adaptation Techniques With a View to Using Heterogeneous Handheld Devices in Performing Product Development Tasks

2012 ◽  
Author(s):  
Eliab Z. Opiyo
Keyword(s):  
Product Development ◽  
Product Information ◽  
Handheld Devices ◽  
Content Adaptation ◽  
Adaptation Mechanism ◽  
Wide Range ◽  
Task Requirements ◽  
Functional Features ◽  
Heterogeneous Terminal ◽  
Development Tasks

This paper articulates the potentials and limitations of the existing techniques for adapting product information contents for transmission among heterogeneous terminal devices and networks. The principal aim of the work was to understand, through a literature survey and empirical investigations, the affordances of the existing content adaptation techniques with a view to using handheld devices in performing product development tasks. Specifically, we reviewed and analyzed a wide range of the existing and emerging content adaptation techniques. The review has both revealed the potentials and shortcomings of the prevailing content adaptation strategies, and also has raised several questions for further research. Among the main shortcomings include lack of suitable mechanisms for adapting some specific contents used in product development such as for adapting 3D product models in context; and the inability of the existing mechanisms to guarantee the synchronization of both the meaning and the context of the content among heterogeneous terminal devices whilst meeting both resource constraints and task requirements. We have also identified the characteristic features we expect an ideal content adaptation mechanism to encompass, and used them as the basis for assessing the extents to which the existing techniques meet the adaptation requirements in product development. A concept and a generic architecture for content adaptation in a product development environment have subsequently been proposed. Overall, the existing content adaptation solutions provide only a subset of the desirable functional features. What is needed is a comprehensive adaptation mechanism, which among other things, handles 3D models and other types of product data; guarantees the synchronization of both the context and the meaning of the information content; considers the constraints posed by the heterogeneity of terminal devices and networks, and which at the same time also takes into account the task requirements and the specific needs and preferences of the users (who in the context of the work reported in this paper are the designers and engineers).

scholarly journals The Open Assembly Model for the Exchange of Assembly and Tolerance Information: Overview and Example

2004 ◽  
Author(s):  
M. M. Baysal ◽  
U. Roy ◽  
R. Sudarsan ◽  
R. D. Sriram ◽  
K. W. Lyons
Keyword(s):  
Product Development ◽  
Information Exchange ◽  
Computer Aided Design ◽  
Product Information ◽  
Product Lifecycle Management ◽  
Product Development Process ◽  
Assembly Model ◽  
Model Data ◽  
Product Model ◽  
Seamless Integration

In early design phases an effective information exchange among CAD (Computer Aided Design) tools depends on a standardized representation for the product data in all PLM (Product Lifecycle Management) tools. The NIST Core Product Model (CPM) and its extension are proposed to provide the required base-level product model that is open, non-proprietary, generic, extensible, independent of any one product development process and capable of capturing the full engineering context commonly shared in product development [1,2]. The Open Assembly Model (OAM) Model extends CPM to provide a standard representation and exchange protocol for assembly. The assembly information model emphasizes the nature and information requirements for part features and assembly relationships. The model includes both assembly as a concept and assembly as a data structure. For the latter it uses the model data structures of ISO 10303, informally known as the Standard for the Exchange of Product model data (STEP)[3]. The objective of the paper is to show how the OAM can be used to realize seamless integration of product information, with an emphasis on assembly, throughout all phases of a product design. A gearbox design example is used to illustrate the process.

Critical Capabilities for Successful Distributed Collaborative Product Development

2004 ◽  
Author(s):  
Victor B. Gerdes
Keyword(s):  
Product Development ◽  
Value Chain ◽  
Computer Aided Design ◽  
Product Information ◽  
Product Lifecycle Management ◽  
Manufacturing Companies ◽  
Collaborative Product Development ◽  
Digital Products ◽  
Development System ◽  
Aided Design

Discrete manufacturing companies practicing distributed product development encounter challenges creating digital products, collaborating cross functionally in an organization and throughout the value chain, and controlling and managing product information and product development processes throughout the product’s lifecycle. This paper investigates the critical capabilities of a product development system for distributed product lifecycle management (PLM). A comprehensive product development system consisting of PTC’s Windchill PDMLink (control), Windchill ProjectLink (collaborate), and Pro/ENGINEER Wildfire (create - mechanical computer-aided design - MCAD) is presented in this paper with use cases and examples as a software solution for enabling distributed collaborative product development.

Engineering Portal for Collaborative Product Development

2003 ◽  
Author(s):  
Zhixin Yang ◽  
Zhejie Liu ◽  
Jinmin Zhao ◽  
Zhenqun Shen ◽  
Zhao Xie ◽  
...  
Keyword(s):  
Product Development ◽  
Data Storage ◽  
System Integration ◽  
Product Information ◽  
Spindle Motor ◽  
Manufacturing Companies ◽  
Collaborative Product Development ◽  
Development Processes ◽  
Typical Component ◽  
Product Development Processes

The product development processes nowadays are featured with ever-increasing complexity of product configurations, diverse data resources, and multi-disciplinary, geographical dispersed engineering teams, and intensive use of various software tools for managing the data associated with the product and its life cycle. These characteristics result in the need of a collaborative product development (CPD) environment for today’s industries. This paper describes the methodology which enables the engineering collaboration within a compressed product development cycle, and presents our results with the development of a CPD environment. A four-tiered client/server collaboration architecture, which allows system integration, data sharing, and collaboration among team members in an internet platform, is described. By integrating the distributed application servers, such as product specification server, CAD/CAE server, project management, collaborative visualization workspace, and product data management module, using web technologies, an engineering CPD portal is proposed and implemented. This portal environment could bring entire engineering team together in one place in real-time, irrespective of geography, enterprise boundaries, or native systems, to share product information throughout the product development processes, which include product definition, design, engineering analysis, and manufacturing, etc. Manufacturing companies could therefore collaborate closely with their suppliers/collaborators global widely. A case study is carried out for collaborative development of a typical component used in data storage industry, the spindle motor, to illustrate the proposed approach and to validate the developed systems.

Consistency of Assembly Related Product Information: Part 1 — Representation

2014 ◽  
Author(s):  
Mehmet Murat Baysal ◽  
Utpal Roy
Keyword(s):  
Decision Making ◽  
Product Development ◽  
Information Exchange ◽  
Product Information ◽  
Spatial Relationships ◽  
Assembly Model ◽  
Product Lifecycle ◽  
Product Model ◽  
Space Requirements ◽  
And Behavior

In this work, NIST’s Core Product Model (CPM) and the Open Assembly Model (OAM) are extended to integrate product information including function and behavior, with an emphasis on assembly, throughout all phases of product development. The consistency validation of product information, and the verification of modified product information are discussed. These processes ensure that the product information has no contradictions and allows tracing through associations without any deficiency or disconnection. In other words, the information model has to be complete in terms of traceability of function, behavior, spatial relationships, etc., in order to support all information exchange activities. The product information representation provides a mechanism for capturing product information and storing it in a database. This representation schema also provides necessary information for any future decision making activities at the End_Of_Life (EOL) environment, such as the replacement or reuse of any part or subassembly. When there is a need to replace one artifact with another, one must consider all of the associations of the existing artifact with other artifacts and the environment, not just functional and space requirements, and the relevant modification(s) of the associated objects has to be verified. So one can manage product lifecycle activities in different perspectives by knowing how the product information is interconnected in various domains and how its characteristics affect each other.

Sign in / Sign up

Export Citation Format

Share Document