CONFIGURED IP MANAGEMENT OBJECTIVE

Transcription

1 CONFIGURED IP MANAGEMENT OBJECTIVE Configured IP Management provides engineers with full control and thorough traceability of modifications made with 3DEXPERIENCE applications for designing and simulating a product and its manufacturing processes from CATIA, DELMIA, and SIMULIA. Users can govern change implementation through the product development cycle across the impacted teams, enabling consistent change propagation to downstream processes and performance validation

2 OVERVIEW Configured IP Management enables engineers to define, save and edit configurations with real time 3D rendering and immediate resolution of valid option combinations based on configuration rules. Users can select between various modes for defining the configuration and multiple ways of applying the rules (or not). Configured IP Management allows engineers to navigate on configured contexts and create the configured context they want to work in for authoring the product structure. This can be consistently applied for all engineering activities throughout the product lifecycle (such as system engineering, physical product engineering, and manufacturing engineering). Configured structure authoring is performed through operations (add, replace, delete, evolve instances) that can be assigned an effectivity. By using effectivities, users can specify which added or removed components correspond to which variants or evolutions of the model or of the models (in the case where multiple models have been assigned as configuration context). It enables sharing of a single configured structure across multiple variations and models. Maintaining all variations within a single configured structure aims at optimizing configured product structure reuse, minimizing engineering efforts while enabling to deliver on time and accurate product variants to the market. Configured IP Management also allows managers and engineers to create Engineering Change Actions (ECA) that are dedicated to authorize and track changes performed in structures and assigned to the relevant contributors within the engineering community. It governs change implementation through the various stages of the product development cycle (design, manufacturing, maintenance, etc.) and across all impacted teams. In addition, it can also ensure consistent change propagation to downstream processes. Different views of the engineering data can be accessed by selectively taking into account the modifications tracked under an ECA, thus enabling advanced visibility to the results of an ECA and anticipate its possible consequences. It also allows specifying configuration effectivity on the ECA that will be applied consistently and transparently to all the configured structure modifications. In addition, enterprise change management authority can govern the whole change process when using Project Manager. The ECA can be driven by enterprise governance for a comprehensive end-to-end process. Companies gain a critical advantage by efficiently tracking fast evolving workin-progress environment, closely monitoring activities, and controlling modifications as the product definition matures. Configured IP Management provides easy and immersive access to advanced configuration and change analysis for finer product structure understanding, project tracking and decision-making. Key Benefits: Seamless integration of enterprise configuration into engineering. Transparently access configuration and change management applications directly in the 3DEXPERIENCE applications for designing and simulating a product and its manufacturing processes. Provide accurate visibility of a component s configuration and change related information to potentially be reused across multiple products. Apply effectivity granularly at any level to manage unresolved structures with reduced engineering effort. Save time and money by letting users analyze and anticipate the impact of modifications throughout global product development (design, manufacturing, etc.). Provide flexible alternative studies to ease comparisons and make trade-off decisions. Execute a consistent and integrated engineering Change Management process between engineering and enterprise operations. Ensure change traceability and monitor design modifications through the various stages of the product development cycle (design, manufacturing, maintenance, etc ). Enable complete and robust propagation of changes to downstream engineering process. Perform complex system-wide changes assigned to multiple engineering groups. HIGHLIGHTS Configuration Product Structures Configured IP Management can be enabled on any engineering IP data structure by assigning a configuration context to it, which results in it being configured. If Product Manager or Product Architect are also used, models can define the configuration context and effectivity criteria. When the configuration context is assigned to the structure, the user selects the effectivity configuration variables to apply. Multi-Configuration Context Share a single configured structure across multiple models and optimize configured product structure reuse. Maintain all variations within a single configured structure to deliver on time and accurate product variants to the market. Configuration Filtering during Navigation Users can navigate a configured structure after specifying the configuration filter to be applied by either selecting a predefined configuration or by defining an ad hoc configuration. A configuration can represent various combinations of the product features to be offered to the marketplace or the configuration may just represent specific criteria to be evaluated.

3 Design in Configured Context Engineers can select and filter a configured context based on specified criteria. The authoring of configured engineering IP data structures is performed through configured operations (add, replace, delete, evolve instances) that can be assigned an effectivity. By using effectivities, users can specify which added or removed components correspond to which variants or evolutions of the model. Users define the authoring context to drive the way configured operation are assigned effectivity. The user can select the following options: No configuration: Work with no configuration so effectivity values can be defined afterwards. Define effectivity: Effectivity selection is required for each modification performed on the product Session effectivity: Effectivity is defined once and assigned to all incoming changes performed in the session. Define Effectivity Configured IP Management provides the capability to define effectivity values. Within each context (organized by tab), available criteria to build an effectivity expression is available. The effectivity definition panel is organized in two sections. The Criteria Selection section is based upon the criteria enabled for each context. The Expression section is divided in two frames for displaying inherited effectivity values and displaying the local effectivity expression in a matrix format. Effectivity can be also defined by inheriting the one from another instance while keeping the associativity. This is enabled in effectivity edition. It enforces effectivity consistency for all related instances by defining validity expression once and reference it everywhere it is appropriate. The referenced effectivity can also be overloaded by some local criteria Instance Effectivity Display The effectivity tab in the properties panel clearly displays the defined effectivity either in a global view (displays the combination of individual model effectivity, the history date and the change applicabilities), or in a model-by-model view (one tab per model) that provides easy access to the expression defined for the selected context. Define Configurations with 3D Configurator Configured IP Management includes a 3D configurator that provides an intuitive and productive user experience to define configurations with real time 3D rendering. The immediate resolution of valid option combinations is based upon the latest configurator rule resolution technology. Build or Refine a Configuration To define a configuration, the user can choose either Build or Refine mode. With Build mode the configuration definition starts from scratch build the product step-by-step by selecting Options from the available Features. With Refine mode the configuration starts with all Options virtually selected and is refined by either selecting one or multiple Options within each Feature, or rejecting some of the virtually selected Options. In addition to specifying whether to apply rules or not, a user can select the way to apply them. Disable incompatibilities is chosen the rules are only used to grey-out the Options that are incompatible with the current user selection. If Select dependencies is chosen the rules automatically select the other Options that are required based upon the current user selection. Select Options to Define the Configuration When defining a configuration with the 3D configurator, the user accesses the complete set of Configuration Features to apply to the product. The display name and the associated image (if any) of the Features are displayed by default but can easily be completed with more information by simply displaying additional attributes of the Features. Moreover, the user can directly search for a feature by its name. This will bring up to the top of the list all the Features matching the search criteria. The user intent regarding option selection (or rejection) is captured all along the configuration definition process and visually accessible through dedicated icons. The configurator also highlights the selected or rejected options that are incompatible by putting in red the user icon in front of the Features and Options. A status bar also summarizes the number of conflicting options. When an Option conflicts with another Option, a red question-mark icon is displayed next to the Option and can be selected to get information about the conflicting user choice and the rules that are involved Define Configurations with Instant Status Feedback in the Configurator A specific gauge indicator in the status bar indicates the completeness of the current configuration definition. There are three possible levels for this gauge. If it is a Partial product, at least one must select Feature is not chosen by the user and part of the product definition is missing. If it is a Complete product, all must select Features are chosen and single select Features have no more than one Option selected. If it is a Hybrid product, at least one single select Feature has multiple Options selected by the user, so the resulting product is a mix of several valid products. A user can save the configuration at any time. It can be re-opened later for further modifications or used to navigate on configured IP data structures. Execute and Monitor Design Modifications Configured IP Management allows managers and engineers to create Engineering Change Actions (ECA) that are dedicated to authorize and track changes performed in product structures and assigned to the relevant contributors within the engineering community. It governs change implementation through the various stages of the product development cycle (design, manufacturing, maintenance, etc.) and across all impacted teams.

4 Users can fully edit and explore an ECA in progress. The ECA contains a precise description of the modifications to perform as it enables to communicate accurately the intent and ensure a good execution. An ECA provides direct access to all relevant information. It enables designers to understand the work they have to perform, and is organized in different sections: Reported Against Items is the context in which to work. Attachments is any document, objects, etc. that can convey understanding of the work to be done. Affected Items is the objects on which the modification needs to be done. The ECA can be transferred to the relevant user to go forward with the change implementation under the ECA authority ( work under ). Users can add information and even break them down into several more granular ECAs that can be transferred to other users. The status of an ECA is monitored easily with the 3D Compass, which also provides information such as critical timing, lateness, etc. On completion of the engineering updates, the ECA can be transferred to the reviewer for approval. Ensure Change Traceability under ECA Enforcement Users can enable change control (authoring under ECA enforcement) to ensure that all the changes requested are tracked. For example, when the first design stages are finished, a user may decide that the product is mature enough for deployment. Going forward, any modifications made on the product should be traceable, so users will start enforcing change control. By doing so, they can enforce the need to implement changes under the authority of an ECA, meaning no modification will be allowed unless the ECA has been set as current through the work under command. As soon as working with an ECA set as current, any modification of engineering data is automatically tracked in the implemented items section of the ECA. In other words, all modifications made, including creation, deletion, updates, and the objects modified, are logged under that ECA for further reference. Project leaders and other engineering community contributors can easily understand what has been done and eventually quickly make the decision to validate the modifications or not. Change Validation Process on ECA Change validation can be enforced on any configured structure to ensure that all the changes are made under the authority of an ECA that defines the effectivity to be applied on all modified instances. Therefore, configuration management is simplified and prevents costly and time-consuming corrections. When work begins under an ECA with change validation the authoring context is updated. The Change Validation enables users to define an ECA s proposed applicability and convey it transparently to all modified instances. So that these instances effectivity can then be accessed through proposed and official view reflecting the application of non-validated ECA or not. Change validation enforces the need to approve all modifications applied on a configured structure, under authority of a change, before being included in the official view. When an ECA is made official, its modifications are integrated and ECA applicability is frozen and propagated to all modified instances (proposed applicability can be modified up to its validation). An ECA can also be Rejected so that all modifications are canceled (i.e. no more visible in the structures). Advanced Navigation on Structures Based on Configuration and Change As a byproduct of the change validation, users can browse a structure as it would appear if all the current changes affecting it were validated. It helps users analyze and anticipate the impact of modifications on global product development (design, manufacturing, etc ). Reviewing the product with the changes enables the team leader to understand better the modifications proposed and make knowledgeable decisions. There are several possible views by applying filters based upon configuration and change criteria. The Validated view takes only validated changes with compatible applicability into account. The Projected view takes into account any changes with compatible applicability. In-work changes can also be added in Official & Projected views for those changes with no defined applicability. The Stack of Changes view allows the user to navigate a configuration based on a list of changes (in work or validated). Lifecycle Coupling The validation of changes is traditionally highly coupled to ECA lifecycle validation. Configured IP Management customization capabilities enable users to address these customer practices in two directions in order to link the maturity of the ECA to the one of the tracked modified objects. Bottom up checks (e.g. Check implemented items (status) are based upon the status of child ECAs to enable ECA promotion. A trickle down approach promotes implemented items at ECA promotion Change Propagation to Downstream Processes Configured IP Management provides the capability to finely and consistently decompose change implementation by transferring recorded changes from an upstream ECA into another downstream ECA to drive downstream changes. A typical example is the need for propagating from engineering to manufacturing engineering (in order to ensure that all modifications of the as designed engineering data are transferred to as build engineering team). Flowing down information to downstream processes results in ECA cascading. Status is added on transferred objects and managed to enable fine reporting on downstream implementation progress. In addition, the capability to analyze flow down completeness from the upstream ECA enables users to make sure all items have been transferred downstream. Configuration and Change Analysis Configured IP Management provides easy and immersive access to advanced configuration and change analysis for finer understanding, project tracking and decision-making. The PLM Compass and the property panel enable users to quickly visualize the effectivity of each component. Access and analyze the configured product structure directly from 3D (or any other authoring environment).

5 Perform Complex System-Wide Changes for Multiple Engineering Groups The Engineering community is the primary user of Configured IP Management. However, enterprise change management authority can govern the whole process when used with Project Manager for a comprehensive end-to-end process. Companies gain a critical advantage by efficiently tracking fast evolving work-in-progress environments, closely monitoring activities, and controlling modifications as the product definition matures. Configured IP Management with Project Manager can use an ECA as a deliverable of a project change task. With Project Manager, users determine the scope and cost of all product changes that impact multiple functional disciplines (e.g., software, mechanical, electrical) before they are implemented. As products collect change requests, each functional department can capture the impact, scope, and cost of the proposed change with meetings and decisions early in the change request process. All change information for a given product or program can be rolled up and aggregated for analysis and approval. As the change process is executed, the change task status is updated automatically to provide a change summary status at the task or project level. This enables total control and visibility of all changes throughout the product development process leading to improved productivity, higher quality and faster time-to-market. Our 3DEXPERIENCE platform powers our brand applications, serving 12 industries, and provides a rich portfolio of industry solution experiences. Dassault Systèmes, the 3DEXPERIENCE Company, provides business and people with virtual universes to imagine sustainable innovations. Its world-leading solutions transform the way products are designed, produced, and supported. Dassault Systèmes collaborative solutions foster social innovation, expanding possibilities for the virtual world to improve the real world. The group brings value to over 190,000 customers of all sizes in all industries in more than 140 countries. For more information, visit Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, 3DSWYM, BIOVIA, NETVIBES, and 3DEXCITE are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. VCL_v6r2015x Europe/Middle East/Africa Dassault Systèmes 10, rue Marcel Dassault CS Vélizy-Villacoublay Cedex France Asia-Pacific Dassault Systèmes K.K. ThinkPark Tower Osaki, Shinagawa-ku, Tokyo Japan Americas Dassault Systèmes 175 Wyman Street Waltham, Massachusetts USA