+

WO2007038707A2 - Affectation de plusieurs structures de produits - Google Patents

Affectation de plusieurs structures de produits Download PDF

Info

Publication number
WO2007038707A2
WO2007038707A2 PCT/US2006/037958 US2006037958W WO2007038707A2 WO 2007038707 A2 WO2007038707 A2 WO 2007038707A2 US 2006037958 W US2006037958 W US 2006037958W WO 2007038707 A2 WO2007038707 A2 WO 2007038707A2
Authority
WO
WIPO (PCT)
Prior art keywords
product
product structure
allocation
target
structures
Prior art date
Application number
PCT/US2006/037958
Other languages
English (en)
Other versions
WO2007038707A3 (fr
Inventor
Nicholas Pascarella
Krishna Nadimetla
Original Assignee
Ugs Corp.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ugs Corp. filed Critical Ugs Corp.
Priority to EP06815741A priority Critical patent/EP1938240A4/fr
Priority to KR1020087010075A priority patent/KR101356331B1/ko
Publication of WO2007038707A2 publication Critical patent/WO2007038707A2/fr
Publication of WO2007038707A3 publication Critical patent/WO2007038707A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms

Definitions

  • preferred embodiment relates to allocating multiple product structures.
  • constituents such as assembly components are typically used to model the
  • PLM product life cycle management
  • the product and is commonly referred to as a product structure.
  • electro-mechanical products are modeled using multiple product structures, e.g.,
  • product structure is a bill of material. The method, wherein said bill of material
  • the vehicle is to one of a functional model, a physical model, and a logical model.
  • relationship is a fulfillment from a first product structure to at least one more
  • product structure implemented by at least one other product structure.
  • source BOM view with a plurality of target components each having a target
  • said domain relationship is one of a fulfillment, an implemented-by, and a
  • first product structure implemented by at least one other product structure.
  • mapping a domain relationship from said at least one product structure
  • Figure 1 is a block diagram of a computer environment in which
  • Figure 2 is a flowchart of the major components for a system
  • Figure 4 is an illustration of a conditional allocation relationship
  • Figure 5 is an illustration an allocation between functional and
  • Figure 6 is a diagram illustrating conditional allocations
  • Figure 7 is an illustration of components and views for allocating
  • Figure 8 is an illustration of a UML class diagram for allocating
  • the presently preferred embodiment provides, among other things, a
  • program modules include routines, programs, objects,
  • a device in the form of a computer 100, such as a desktop or laptop computer,
  • the computer including a plurality of related peripheral devices (not depicted).
  • the computer including a plurality of related peripheral devices (not depicted).
  • microprocessor 105 includes a microprocessor 105 and a bus 110 employed to connect and enable communication between the microprocessor 105 and a plurality of bus 110.
  • bus 110 may be any of several types of bus structures including a memory bus
  • the computer 100 typically includes a user interface adapter
  • interface devices such as a keyboard 120, mouse 125, and/or other interface
  • the bus 110 also connects a display device
  • the bus 110 also connects the microprocessor 105 to a memory
  • 145 which can include ROM, RAM, etc.
  • the computer 100 further includes a drive interface 150 that
  • the storage device 155 can include a hard disk drive, not shown, for
  • optical drive 160 or writing to a removable magnetic disk drive. Likewise the optical drive 160
  • optical disk drive for reading from or writing to a
  • removable optical disk such as a CD ROM or other optical media.
  • the computer 100 can communicate via a communications channel
  • the computer 100 may be associated with such other computers in a local area network (LAN) or a wide LAN (LAN) or a wide LAN (WAN)
  • WAN wide area network
  • modules may be located in both local and remote memory storage devices. All
  • embodiment is typically stored in the memory 145 of the computer 100.
  • such software programming code may be stored with
  • the software programming code may also be
  • va ⁇ ety of non-volatile data storage device such as a hard-
  • the code may be distributed on such media, or
  • Figure 2 is a flowchart of the major components for a system
  • system represents a product that has at least one product structure (Step 200). Next the system maps a domain relationship from the at least one product
  • Step 205 the system derives a fulfilled product structure
  • Step 210 From the mapped domain relationship (Step 210).
  • Figure 3 is an illustration of an allocation between two product
  • a first product structure representing a functional model 300 and a
  • model 300 represents the functionalities of the product, for example, the
  • the user can configure various allocations in and out of a product.
  • the design object should be Y in the design model otherwise, the design object should
  • Allocation Context 410 For each allocation set can be represented by an Allocation Context 410.
  • the context could be mapped for cost
  • allocations are created through an application programming
  • API API
  • the allocation is related to the absolute occurrence of the
  • Figure 5 is an illustration an allocation between functional and
  • model 415 is revised the allocation remains intact, and the user changes the
  • Figure 6 is a diagram illustrating conditional allocations. Referring
  • an option set 600 is assigned to a product 605.
  • the option set is assigned to a product 605.
  • a structure map 620 has a list of allocations, generally
  • Part 1.2 provides the realization of Function 1.2, generally illustrated
  • the basic rule is, if the
  • a parts list is not related to a particular product
  • the system can determine exactly which instances of a product structure
  • the first is to report an error stating that a target
  • structure 645 is not configured properly because there are unfulfilled allocations.
  • the second is to add the allocated components to the configuration, essentially
  • Figure 7 is an illustration of components and views for allocating
  • Allocations connect, or tie, together a source with a
  • target e.g., a source BOM with a target BOM.
  • allocation object 700 ties a source component 705 with a target component
  • a StructureMap object 715 ties a source BOMview 720 of a source
  • product structure e.g., the functional model 415
  • BOMview 725 of a target product structure e.g., the design model 420.
  • object 700 is not tied to a specific revision of the components, so an absolute
  • occurrence object 730 makes allocations independent of the revisions of the
  • the StructureMap object 715 refers to two structures of
  • ImanType object defines domain relationships of the allocation object 700 and
  • parts 1 and 2 provide the fulfillment of the system component Sysl; or functions 1 and 2 are implemented
  • system component Sysl or part 1 provides the realization of functions 1, 2,
  • Figure 8 is an implementation object model
  • an Allocation class 800 shares the source product
  • ImanType class 810 ImanType class 810
  • AbsOccurrence class 815 An AbsOccurrence class 815.
  • the StructureMap class 820 also shares the source
  • the StructureMapRev class 805 is shared by the
  • Allocation class 800 and the StructureMap class 820.
  • the Allocation class 800 is
  • class 510 whether to configure.
  • An apparatus of the presently preferred embodiment may
  • programmable system including at least one programmable processor coupled to
  • data storage system at least one input device, and at least one output device.
  • the application program may be implemented in a high-level procedural or
  • the language may be a compiled or interpreted
  • a processor will receive instructions and data from a
  • nonvolatile memory including by way of example semiconductor memory
  • source BOM view can be configured, along with a series of
  • structures could be a system structure, an electrical structure, manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Operations Research (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Multi-Process Working Machines And Systems (AREA)

Abstract

L'invention porte sur un système, sur un procédé et sur un programme informatique visant à affecter des structures de produits et consistant à représenter un produit pourvu d'au moins une structure; mettre en concordance une relation de domaine depuis au moins une structure de produits et dériver une structure de produits réalisée par mise en concordance et un système approprié et des instructions lisibles par ordinateur.
PCT/US2006/037958 2005-09-27 2006-09-27 Affectation de plusieurs structures de produits WO2007038707A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP06815741A EP1938240A4 (fr) 2005-09-27 2006-09-27 Affectation de plusieurs structures de produits
KR1020087010075A KR101356331B1 (ko) 2005-09-27 2006-09-27 복수의 제품 구조의 할당

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US72078005P 2005-09-27 2005-09-27
US60/720,780 2005-09-27
US11/535,445 US8224471B2 (en) 2005-09-27 2006-09-26 Allocation of multiple product structures
US11/535,445 2006-09-26

Publications (2)

Publication Number Publication Date
WO2007038707A2 true WO2007038707A2 (fr) 2007-04-05
WO2007038707A3 WO2007038707A3 (fr) 2007-11-08

Family

ID=37900476

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/037958 WO2007038707A2 (fr) 2005-09-27 2006-09-27 Affectation de plusieurs structures de produits

Country Status (4)

Country Link
US (1) US8224471B2 (fr)
EP (1) EP1938240A4 (fr)
KR (1) KR101356331B1 (fr)
WO (1) WO2007038707A2 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8510752B2 (en) * 2007-08-31 2013-08-13 Siemens Product Lifecycle Management Software Inc. System and method for data management of embedded systems
US8797342B2 (en) * 2010-09-10 2014-08-05 Siemens Aktiengesellschaft Method for visual project modeling
FI20125700A7 (fi) * 2012-06-21 2013-12-22 Tekla Corp Yhteisdata suhdetiedolla
US12008624B1 (en) * 2015-05-05 2024-06-11 Centric Software, Inc. Method for product recommendations using three-dimensional modeling and points of measure

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4847761A (en) * 1987-09-24 1989-07-11 International Business Machines Corp. Automated bill of material
US5119307A (en) * 1989-12-22 1992-06-02 General Electric Company Method and system for automated bill-of-material generation
US6002854A (en) * 1993-03-29 1999-12-14 Trilogy Developmetn Group, Inc. Method and apparatus for configuring systems
US6885902B2 (en) * 2001-12-27 2005-04-26 Manugistics, Inc. System and method for replenishment by purchase with attribute based planning
US7085776B2 (en) * 2002-04-24 2006-08-01 The Boeing Company Logical hierarchical data model for sharing product information across product families
US20030220852A1 (en) * 2002-05-22 2003-11-27 Andrew Back Bill of materials change management schema
US7337170B2 (en) * 2005-01-18 2008-02-26 International Business Machines Corporation System and method for planning and generating queries for multi-dimensional analysis using domain models and data federation
US8402007B2 (en) * 2005-08-02 2013-03-19 The Boeing Company Methods and apparatus for creating and utilizing templates in connection with information modeling

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None
See also references of EP1938240A4

Also Published As

Publication number Publication date
EP1938240A4 (fr) 2011-01-26
US8224471B2 (en) 2012-07-17
US20070106486A1 (en) 2007-05-10
KR101356331B1 (ko) 2014-01-27
WO2007038707A3 (fr) 2007-11-08
KR20080059603A (ko) 2008-06-30
EP1938240A2 (fr) 2008-07-02

Similar Documents

Publication Publication Date Title
US6351734B1 (en) System and method for resource allocation and planning
US8527316B2 (en) System and method for risk adjusted strategic planning and phased decision management
US8739047B1 (en) Integrated planning environment for agile software development
US8875088B1 (en) Methods and systems for performing project schedule forecasting
EP2132655B1 (fr) Procédé de création et de repérage de données de système externe via une carte conceptuelle
JP5460941B2 (ja) ソフトウェアシステムのための拡張可能なカスタマイズフレームワークおよび方法
US20120116834A1 (en) Hybrid task board and critical path method based project application
EP1710744A1 (fr) Association et visualisation de réseaux d'affaire schématisés
US20030221165A1 (en) System and method for metadata-driven user interface
US7596803B1 (en) Method and system for generating access policies
CN101197025A (zh) 用于管理企业资源计划项目的方法和系统
US8224471B2 (en) Allocation of multiple product structures
JP3964632B2 (ja) プロジェクト管理方法及びその実施システム並びにその処理プログラム
US20060052896A1 (en) Methods and systems for modeling a bill of material for a configurable product
US8386653B2 (en) Instrumenting configuration and system settings
Nagamine et al. A case study of applying software product line engineering to the air conditioner domain
US7970587B2 (en) System and method for defining part interfaces
CN108089737A (zh) 单台计算机的多鼠标控制方法及装置
US20050159971A1 (en) Systems and methods for planning demand for configurable products
WO2009036398A2 (fr) Système et procédé pour une définition de produit
US8620895B1 (en) Mapping organizational accounting codes to access business information
Botterweck Variability and evolution in systems of systems
KR101957916B1 (ko) 건물 에너지 시뮬레이션 서버 및 이를 포함하는 운영 시스템
CN110083339A (zh) 一种新型计算机编程语言
CN116931880A (zh) 过程定义模型生成方法、资源分配方法、电子设备和介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2006815741

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006815741

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020087010075

Country of ref document: KR

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载