Feedback

ENOVIAVPM V1.6 optimized for CATIA V5

IBM United States Software Announcement 206-199
September 5, 2006

 

 ENUS206-199.PDF (122KB)

Table of contents   Document options  
TOC link At a glance TOC link Reference information
TOC link Overview TOC link Additional details
TOC link Key prerequisites TOC link Technical information
TOC link Planned availability date TOC link Ordering information
TOC link Description TOC link Terms and conditions
TOC link Product positioning TOC link Prices
TOC link Hardware and software support services  
 
Printable version Printable version

 
At a glance

ENOVIAVPM V1.6 includes the following features and benefits:

  • Delivers ENOVIAVPM V1.6 UNIX functional coverage on the Microsoft Windows platform, enabling Virtual Product Manager (VPM) users to migrate from UNIX-based CATIA (V4 or V5) to CATIA V5 running on Microsoft Windows
  • Provides excellent CATIA V5 integration within ENOVIAVPM V1.6, including a wide set of support and management capabilities for V5 data entities that strengthens V5 relational design practices with enhanced impact analysis capabilities
  • Introduces an XML-based distribution process for multi-site support, addressing heterogeneous environments, customization and selective checking of the delta replication. Moreover, V1.6 widens the scope of supported objects to replicate
  • Enhances DELMIA integration, SAP interoperability, Product Structure Navigator (PSN), and product configuration and action management
  • Delivers significant performance improvements to the user's daily tasks of action and product structure management, and greatly reduces V5 data loading time.
  • Further protects a user's existing investment in IT technology by supporting newer versions of operating systems and middleware

 
Back topBack to top
 
Overview

This new release promotes massive migration from CATIA UNIX® (V4 or V5) to CATIA V5 Windows™, in conjunction with ENOVIA — Multi PDM — CDM/VPM plug-in. Fully compatible with CATIA V5.17, it provides functional coverage completeness available on the Microsoft™ Windows platform. Users take advantage of all-in-one machines for office applications and CATIA, minimizing costs of support. No VPM migration is needed, and the same concept with a similar interface ensures a rapid learning curve from ENOVIAVPM on UNIX to Windows.

Customers will benefit from a continuous but significant and robust improvement of integration between ENOVIAVPM and CATIA V5. It delivers comprehensive support and management of V5 information and objects, including information support of knowledgeware, analysis, part catalogs and management of DMU and kinematics inside applicative containers.

This integration improvement also fosters V5 relational design practices with advanced impact graph capabilities, including a highly productive in-context building session. It accomplishes this by retrieving the related objects and enhancing impact analysis of modifications.

This new release of ENOVIAVPM V1.6 solutions reinforces the customer choice of ENOVIAVPM and protects the investment by delivering the latest operating systems and middleware support in addition to significant enhancements and increased performance.

ENOVIAVPM V1.6 provides multisite support completeness for all types of extended enterprise. A new XML-based protocol between sites enables users to manage heterogeneous data managers such as DB2® and Oracle and to control the delta data to replicate. Moreover, ENOVIAVPM V1.6 delivers additional replication support for more objects, such as action and effectivities.

Performance improvements affecting the user's daily tasks include action and Product Structure Navigator (PSN) management, and V5 data loading time. New enhancements result in large productivity gains:

  • Searching parts in non-expanded tree
  • Getting the context for a drawing
  • Opening assembly from contextual part

ENOVIAVPM V1.6 reinforces Product Lifecycle Management (PLM) values with DELMIA integration and enterprise integration with new capabilities of SAP interoperability. In addition, it delivers productivity and usability improvements in the PSN, product configuration management, and action management.
 
Back topBack to top
 

Key prerequisites

Workstation platforms

  • IBM RS/6000®
  • HP-UX 9000 Series
  • Sun Solaris SPARC system family

A properly sized database is required, using either the Database 2™ (DB2) or the Oracle database manager.

Note: DB2 UDB Enterprise Edition V8.2.2 is shipped with ENOVIAVPM V1.6.
 
Back topBack to top
 

Planned availability date

September 29, 2006
 
Back topBack to top
 

Description

ENOVIAVPM V1.6 supports a new operating system to protect the customer investment. The following operating systems are now supported (the levels described below are the minimum level supported for both buildtime and runtime):

  • AIX® V5.3 ML03: AIX V5.3 ML03 runtime for 32-bit and 64-bit is supported on Power 4 and Power 5.
  • HP 11i Dec 2004
  • Solaris 10.03/05

New levels supported for middleware include:

  • Additional support for Oracle runtime is Oracle 10gR2.
  • DB2 V8.2.2 is a prerequisite for DB2 database on all operating systems.
  • Release prerequisite for Orbix is Orbix 3.0.1.
  • MOTIF 2.1 is a prerequisite for graphical component on AIX 32-bit and Solaris 32-bit.

ENOVIAVPM V1.6 continues the dynamics performed in earlier releases. It offers a large scope of new function, which is presented in two separate sections.

There has been a large amount of new function delivered after the V1.5 general availability date through a maintenance/enhancement PTF delivery. Most of the V1.5 customers are already familiar with these functions up to PTF 31. The first section, New enhancements for ENOVIAVPM V1.6 , deals with highlights delivered after V1.5 PTF31. The second section, Enhancements delivered in ENOVIAVPM V1.5 PTF31, details all the enhancements delivered in PTF31.

New enhancements for ENOVIAVPM V1.6

  • User exit and API to overwrite representation — The main purpose of this API/user exit is to overwrite existing representation, preventing a user from deleting and recreating a representation.
  • Physical/logical link for revision — Behavior of current multi-model link (MML) graph is enhanced in case of revisioning. When a parent document is now revised, the child document still points to the previous revision, but the link information shows that a new revision exists. Synchronization can be done in CATIA V5.
  • Accept upissue — MML link statuses are directly impacted by versions of the objects, and the aim of the impact graph is to manage these change propagations. However, a new version of a pointed object (for example, a part) may lead to a different user's decision on the pointing object (for example, a drawing).

    Because of UpIssue, Accept and Ignore functions, users can choose one of the following options:

    • Link will now point to the latest version of the object (UpIssue).
    • Link will continue to point to the same version of the object to which it already points (Accept).
    • Link will now ignore the modification on pointed object (Ignore).

    Note: Upissue and Accept functions were already provided on V4 models. This new version makes them available for V5 objects as well, as it provides the new Ignore option for both. This flexibility greatly improves users' supervision of their product development, based on relational design methodology and part versioning.

  • Security cluster view action/config — The concept of easy, customizable security data groups based on attribute conditions and named as security clusters has been widely adopted by customers because it simplifies the security definition and administration. Security clusters are now extended to actions and configurations.
  • Versioning cross hub/ID logic — A new logical ID on objects is now attached to objects, which is kept with the object modification. It results in performance improvements when loading .psn files, clash results, or any V5 assembly from VPM to CATIA V5.

    The performance gains are directly linked to the number of modifications that have been done on the pointed objects, and so the gain can be important in large concurrent and relational design scenarios. It also provides significant performance when working on a remote site.

  • Other methods on clash — Users now have the opportunity to manage selected clash result through a user exit in order to launch a custom application.
  • Login VPM in batch — Users are now able to start VPM as a batch command with multiple arguments. For instance, it enables user to launch VPM in batch by night to have VPM ready to work in the morning.
  • Check parameters multireport — A global report file, which details the erroneous configuration effectivities, is now available when checking parameters in order to validate an action. This enables the expert to have a clear view of the problems to solve before attempting another check.
  • C_SIZE in megabytes (MB) for document — The C_SIZE, which is the column where the size of the document is actually stored, is now displayed in MB instead of bytes (B). This greatly enhances visibility for the users, especially for the large documents that VPM can handle.
  • Massive import with drawing — Users can perform a massive import to import an assembly in VPM while also importing the drawings pointing to this assembly at the same time. This productivity enhancement simplifies the assembly drawing management.
  • Database connection removal — Security and administration are enhanced by removing the redundant database connection from CATIA V5 to VPM database that existed in addition to the ENOVIAVPM client connection to the VPM database.
  • Vault sharing — VPM 1.6 strengthens VPM V4 to VPM V5 transition with vault sharing. It avoids duplication of physical data (longfields) between the two solutions, and only the meta data is copied from one solution to the other while files are shared. This results in significant performance gain to the customer in both major steps of the migration with no more file extraction and write on disk on the export side. On the import side, there is no more read on disk and write on the vault.
  • Open parts without representations — Users can now load parts into CATIA V5 from VPM. The procedure for opening the part is the same as that for opening a document from PSN.

Refer to the Enhancements delivered in ENOVIAVPM V1.5 PTF31 section in the Additional information section for details.

Accessibility by people with disabilities

Owing to the graphics-intensive nature of its engineering design applications, this product has been granted a deviation for 2006.
 
Back topBack to top
 

Product positioning

Refer to Software Announcement 201-137 , dated May 1, 2001.

Product positioning — Globalization

The ENOVIAVPM V1.6 Engineer Solution product and the Engineer Solution Users Guide are the only translated sections contained on four platform-specific CDs. The other ENOVIAVPM products and publications are only available in English.
 
Back topBack to top
 

Hardware and software support services

SmoothStart™/installation services

IBM SmoothStart and Installation Services are not provided.
 
Back topBack to top
 

Reference information

For information about PLM V5.17, refer to Software Announcement 206-194 , dated September 5, 2006.

For information about CATIA V5.17, refer to Software Announcement 206-195 , dated September 5, 2006.

For information about ENOVIA VPLM V5.17, refer to Software Announcement 206-196 , dated September 5, 2006.

For information about CAA RADE V5.17, refer to Software Announcement 206-198 , dated September 5, 2006.

For information about ENOVIA SMARTEAM V5.17, refer to Software Announcement 206-197 , dated September 5, 2006.

Business Partner information

If you are a Direct Reseller - System Reseller acquiring products from IBM, you may link directly to Business Partner information for this announcement. A PartnerWorld ID and password are required (use IBM ID).

BP Attachment for Announcement Letter 206-199

Trademarks

 
Database 2 and SmoothStart are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
DB2, RS/6000, and AIX are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows and Microsoft are trademarks of Microsoft Corporation.
 
UNIX is a registered trademark of the Open Company in the United States and other countries.
 
Other company, product, and service names may be trademarks or service marks of others.

 
Back topBack to top
 
Additional details

For descriptions of previously announced ENOVIAVPM products, visit

From the menu frame select ENOVIA Products to get to the ENOVIA page. From the menu frame on the ENOVIA page, select ENOVIA Lifecycle Applications , then scroll down and click on ENOVIA Product Lifecycle Applications .

Enhancements delivered in ENOVIAVPM V1.5 PTF31

Enhanced navigation in the Product Structure Navigator (PSN) graph

  • Confirmation is now required when using collapse all on root functions.
  • Automatic Current can be selected as the default mode: When moving parts, an automatic current mode can be automatically activated. By default, this identifies the immediate parent as current (relative to the move).
  • A function is available to interrupt the expand any function after a level explosion has been completed.
  • Selected part instances can be used along with other filters, such as configuration criteria, to control expansion of a PSN graph.
  • The user can simplify the graph for assemblies containing multiple instances of the same part reference; the multiple instances can be made to collapse onto a single part instance and display a part quantity.
  • On simple queries, the user can limit display of parts with multiple versions to the most recent version only.
  • An option is provided when expanding a configuration to identify (color) parts that have a more recent version in the database than the one displayed on the graph.
  • The user can define PSN object filter to identify a subset of objects that should be visualized on the PSN graph. The filter is expressed as a database object predicate (for example, PART_TYPE = 'ASSEMBLY' AND C_PART_OWNER ='ALAN') that can reduce the number of objects transferred from the database to working storage. As such, it can enhance ENOVIAVPM query performance. The predicate can also include data type and environment criteria.

    Other enhancements relative to the PSN include:

    • Allows .psn files to be stored, accessed and managed as ENOVIAVPM documents.
    • Makes available new version with different part number in PSN.
    • Includes report that follows read of a .psn file.
    • Lets user keep last Get last revision state in PSN select object.
    • Includes .qry in .psn.

Enhancements relative to Bill of Material (BOM) management

  • The C_COMMENT field on an assembly link ($EXT table) can be updated without forcing creation of a new occurrence.
  • Automatically displays report on commit failed.

Multisite distribution: Heterogeneous multisite support — Replication information sent to remote sites now implements XML for message formatting. This enables communication between sites based on different relational data managers such as DB2® and Oracle. In addition, the user can control the data sent to the remote site to adhere to local security and other rules. In the same way, the remote site can modify the data format and content prior to it being incorporated into the local ENOVIAVPM system. Before replicating data to a remote site, ENOVIAVPM tests its current state. If it is checked out, the object is not transferred.

Data can be replicated and deleted by users who are not data owners.

A batch mode facilitates large replication operations.

Multisite distribution is supported with use of XML protocol:

  • XML protocol allows the user to identify differences between XML and database data prior to an import operation, controlling whether or not the previous data should be replaced.
  • A user-defined filter allows selected documents only ( long fields ) to be transferred.
  • A new data dictionary supports the ability to assign a public/private characteristic to a complex object component (table), easing replication management across the extended enterprise where some data is considered to be proprietary to a site.
  • Replication of Actions to remote sites as read-only objects is available.
  • Replication of proposed effectivity is supported.
  • Management functions allow an authorized user to administer ( add/delete ) the replication queue. When using replication across multiple sites, the functions provide site control to cause replication of each site independently of the others.
  • Web client users can Subscribe with replication .

Other enhancements relative to multi-site distribution:

  • Entry point at the end of import and export — The user can launch post-process such as encumbrance computation at the end of import. Information about the objects imported or exported can be passed to other applications for improved automation.
  • Batch adds drawing in replication queue
    • Batch to automate replication of drawing when 3D model is subscribed with replication. In earlier releases, the replication manager had to manually select the associate drawing of the 3D models in the replication queue. The technical reason behind that is that drawing in V4 (same limitation or implementation in V5) knows about the parent object (the 3d model, the part), but not conversely.
    • The batch available in the release scans the drawing to check if the parent object is in the replication queue. If so, then the drawing is added to the replication queue. Because this tedious task can be avoided, this translates into time saved for the replication manager.

Clash management

  • Clash deletion is managed by $LIST_DELETE in ENOVIAVPM profile.
  • Clash update is managed by $LIST_UPDATE (interactive update) in ENOVIAVPM profile.
  • Input file is generated for ITFCHECK from AT0EXPND.

Configuration management (CFG)

  • The name of the active configuration handlers is displayed at all times. This is useful for long-lasting sessions.
  • Configuration effectivity displayed in the PSN is no longer limited to the size of the node but can extend across several lines. This is useful when complex effectivity options are used with numerous Boolean conditions causing long resulting expressions.
  • A configuration handler now includes an optional default that forces proposed effectivity to be considered when resolving a configuration. This is an enhancement on the user ergonomics; previously, users had to manually choose this option each time the configuration handler was used.
  • A dictionary category may now contain multiple default options. This enhances the user interface, simplifying the systematic use of multiple options.
  • A complete session configuration context may be saved in a file. This is useful when the top node of the PSN graph is not a product (that is, associated with an option dictionary). In this case, the user is prompted in session to identify the parent product. The configuration file contains the parent product identifier and thus allows replay of the configuration choices during a later session.

    Without this option, if the same part is opened in a later session, the parent node used by default is the one most recently used and may therefore not produce the same context.

  • In the PSN graph, all the links in the product structure that are affected by the same set of options and that lead to a selected node are highlighted.
  • Options and rules now carry user and date information identifying last changes.
  • Corporate dictionary categories and options can be renamed.
  • Milestones can be renamed.
  • Multiselection of CH in configuration analysis is available.
  • Configuration handlers can support proposed effectivities.
  • Rules check to imported CH (without opening them) is applied.
  • User can change the name of the Action associated with modification effectivity.
  • User can define effectivity on models, documents and features.
  • Multiple default options can be specified for non-exclusive categories.
  • User can scan all dictionaries to retrieve all existing categories.
  • More information about action in Edit Configuration Parameters panel can be displayed.
  • Modification attributes to rules, options and categories objects are added.
  • User can set effectivity functions for documents, models and features are provided.
  • More information about Action in Edit Configuration Parameters panel can be displayed.
  • LAST_MODIFIER_ID and LAST_UPDATE_DATE on rule, option, category are added.
  • User can save last product used for milestones and options.
  • User can paste effectivities.
  • User can quickly select field in dictionary graph.
  • Date, range and milestones when adding new row can be propagated.
  • Real option defines effectivity function on models, documents and features.
  • Multiple default options in non-exclusive categories are included.
  • The system can force uppercase in ConfigHandler, options and categories — For historical reason, VPM V4 requires that Configuration Handlers, Options and Categories be uppercase. However, when keying them in, the system would let you do it in lowercase and then reject it because it wants it in uppercase. To avoid user frustration, the system automatically forces uppercase when keying in those fields.
  • Default values on category creation can be removed.
  • Configuration analysis results can be printed.
  • VPM V4 Publish/Subscribe support mechanism on modify configuration event is enhanced. Notification mechanism can be triggered on the modification of a configuration (modify config event). This translates to improved collaboration processes where all the actors working with configuration can be notified of changes

Actions Management (AFL)

  • Actions can be used as briefcases to collect data from ENOVIAVPM and transfer it using ENOVIA 3d com to the user's workstation. The action and data are stored on the workstation in XML format where it can be modified and then sent back to ENOVIAVPM to update the database.
  • An enhancement to the user dialogue when saving changes under an action provides automatic transfer of ownership to the user and ensures that concurrent changes are incremental.
  • Action contents can be queried in a multi-site installation.
  • Manage properly complex effectivities in action completed.

People and Organization (P&O)

  • P&O management of the part move operation (previously, users had to be authorized to delete and insert in order to implement a move) is simplified.
  • Users may replicate or delete replicated data even if they are not the data owners.
  • A distinction can be made in P&O between data that is public or private to any particular site, enabling control of the replication functions.

Publish/Subscribe: Enhanced Subscribe function allows users to subscribe with replication to parts on remote sites, thus implementing a pull mechanism. This is useful in a multisite environment to define the remote site parts they require without having to involve the remote site's system administrator. Parts used in the replication may be identified using the cluster mechanism.

Interoperability with SAP manufacturing

A new implementation of SAP interoperability provides changes and new functions:

  • Generate and check in geometric data to SAP (not only metadata).
  • Direct access to Material Master data from the PSN
  • Automatic synchronization between ENOVIAVPM and SAP for parts and documents
  • Support for multiple ENOVIAVPM environments
  • Push link attributes (for example, quantity )
  • Event-driven push from ENOVIAVPM to SAP
  • Improved attribute mapping
  • Initial release and change management
  • Release-controlled synchronization of BOM data (updatable BOM)
  • Process rules implementation

CATIA V4 Integration: CATIA V5 CATParts (in .cgr format) can be loaded into CATIA V4.

CATIA V4 link management

  • A revised dependency graph that now includes document-to-document links (all CATIA V4 links are document-to-document links), document-to-instance links and instance-to-instance links (as can be defined in CATIA V5).
  • The dependency graph can be printed.
  • Dependency graph objects can be highlighted as a result of selecting the displayed CATIA V4 models.
  • An entity mode function, Check UUID (show models with same UUID in dependency graph), allows more precise model identification for accurate impact analysis.
  • UUID or selected models can be changed.
  • Published knowledge parameters can be saved.
  • Non CATASS link (PART-PART) can be created in PSN.
  • Reference-reference and reference-instance links in a dependency graph can be displayed.

CATIA V5 Integration

Store and load CATIA V5 documents

  • Loads product structure (including contextual and constraint links) and geometry into CATIA V5. It also enables:
    • Load assembly drawing, build associated assembly in CATIA V5, update drawing and save document changes to ENOVIAVPM
    • Load assembly analysis, build associated assembly in CATIA V5, update analysis and save document changes to ENOVIAVPM
  • Saves product structure changes made in CATIA V5 with synchronous commit confirmation in both systems. It now allows for changes to be made in a single transaction.
    • Copy/paste instance (either from within the same or a different CAT IA frame). New instances have their names saved in ENOVIAVPM.
    • Move instance.
    • Delete instance.
    • Ability to define new parts in CATIA V5 and have them created in ENOVIAVPM (requires a user exit and installation of CAA products, allowing attribute definition). CATParts are identified in ENOVIA VPLM as elementary parts .
  • Includes associativity between the digital mock-up in CATIA V5 and the product structure graph (cross highlight, show/no-show).
  • Converts CATIA V5 CATParts into CATIA V4 models and store in ENOVIAVPM either as separate documents or as alternate representations on the same document.
  • Includes save and restore CATIA V5 catalogues from ENOVIAVPM.
  • Stores CATIA V5 assembly as a publish exposed (PE) document. This avoids explosion of the assembly structure and constraints into ENOVIA VPLM. All the information in the CATProduct is stored in the PE document, including applicative, tolerancing, and other data. Assemblies that do not require being exposed in the PPR can make use of this function to simplify assembly management and ensure persistence of all assembly data. This method of storing data is useful for assemblies in which no configuration effectivities are required and versioning is simply used to manage multiple evolutions.
  • Includes create/save options with CATIA V5. Previously, when an object was modified in CATIA V5 and saved in VPM V4, the newly created part would be loaded back in CATIA V5. In this release, the user has the choice of how CATIA V5 will behave after the modifications have been saved in CATIA V5. In other words, the user can save/replace or update the documents within the CATIA V5 session while taking care of any relational information. Three modes are available:
    • Extract Save Keep Modified — This mode creates a new Part/Document in VPM and keeps all the modifications in the original part in the CATIA session.
    • Extract Save Reload Source — This mode creates a new Part/Document in VPM and replaces the modified part in the session by the original version in the database. (All links pointing to the replaced part will be rerouted if possible; if not, the corresponding links are broken.)
    • Extract Save Replace by target — This mode creates a new Part/Document in VPM and replaces the modified part in the session by the new part (all links rerouted to the new version).

    Examples include:

    • The user loads part A from VPM V4 in CATIAV5 and modifies it into A' (VPM A -(GT/EQ) CATIA A').
    • The user saves part A' back to VPM V4 as part B (VPM B (LT/EQ)- CATIA A').

    In the earlier release of the software, CATIA would automatically reload part B from VPM V4 (VPM B -(GT/EQ) CATIA B)

    The new functions provide three choices:

    • Keep modified: after creation of part B in VPM, A' stays in CATIA
    • Reload source: after creation of part B in VPM, A is reloaded in CATIA
    • Replace by target: after creation of part B in VPM, B is loaded in CATIA (previous release behavior)

CATIA V5 information support

  • Integration of product level knowledge objects (delivered through CATIA Knowledge Advisor product)
  • Integration of product level Knowledgeware relationships (delivered through CATIA Object Manager product)
  • Integration of analysis documents (results and computation data)
  • Bundle segment integration (delivered through Electrical Harness Installation product)
  • CATIA V5 catalogue integration allowing CATIA users to search within ENOVIAVPM for part catalogues
  • Ability to manage alternates shapes (DMU interoperability)
  • Ability to extract/save a CATProduct as a document, allowing application data in the CATProduct to be made persistent
  • Ability to save DMU applicative data in ENOVIAVPM: Create, Delete applicative container
    • Section
    • Measurements
    • 3D annotations
  • Kinematics integration (either storing data in a CATProduct publish exposed document or saving kinematics dress-up data as an application container)
  • Material types to be saved in appropriate CATIA V5 document (CATPart, CATProduct)
  • ENOVIAVPM Cache support for CATIA V5 documents
    • CATIA V5 document can be supported in the VPM Cache the same way it was possible with CATIA V4 model.
    • The VPM V4 cache mechanism only worked for CATIA V4 data previously. These enhancements make the caching mechanism available for CATIA V5 documents. This mechanism provides improved performance to the end-user when opening CATIA V5 documents from VPM V4.

CATIA V5 link management

  • Save/restore instance-instance and reference links (for example, assembly constraints/external reference). This includes publications defined at the assembly level.
  • Save/restore document-document links (for example, CATDrawing -(GT/EQ) CATPart).
  • Save/restore document-instance links (for example, CATDrawing -(GT/EQ) assembly). Exposed assembly drawing links point to leaf instances.
  • Expose links to high-level nodes in drawings.
  • Enable publications based on CATIA V4 geometry.

Other enhancements

  • Forces a unique copy of CATPart (new UUID creation) when using create and Save command.
  • Duplicates instances when versioning root part.
  • Provides a heterogeneous selection with select object.
  • Check in/out with multi-selection.
  • Updates instances when replace intermediate part with a version.
  • Includes an enhancement on open instance (only some instances).
  • Recreates the ENOVIAVPM session from a CATAnalysis or CATProcess document.
  • Includes file-based import function. It creates new objects (parts, documents, assembly structure links, constraints and publications) in ENOVIAVPM from CATIA V5 files. Cyclic constraints and dependencies cannot currently be recreated in ENOVIAVPM. Multiple files containing the same part may result in multiple part references.
  • Includes performance enhancements. Various internal algorithmic changes contribute to improved performance. Applications that only require access to CATIA V5 visualization geometry are no longer also sent the complete set of design geometry. Multi-level deep assembly performance and cross-highlighting is improved. Moreover, CATPart documents stored in ENOVIAVPM now contain calculated Brep data to avoid the systematic requirement to load design data into CATIA when Brep data will suffice. This capability was previously only available for file-based CATPart documents; it accelerates model load times.
  • Replaces component performed in CATIA V5 is supported.
  • Adds new assemblies and parts to the product structure (used by mobile users).
  • Includes generative drafting (P2). Reroute assembly drawing on new version of root product.
  • Includes a new option to check frozen object at loading time. Avoid user frustration by not allowing the modification of CATIA documents in session that can not be saved back for any business process reason.
  • Delivers asynchronous communications with CATIA V5. Enhanced flexibility lets the user perform more than one load process in VPM (VPMA or PSN) to CATIA V5.
  • Expands dependencies (assembly drawing). A new command enables the user to expand in the current PSN only the necessary instances used to define the Assembly CATDrawing. This brings productivity for performing assembly drawing updates when only a part of the assembly is linked to a drawing.
  • Provides open assembly from contextual CATPart — Designers can use a new contextual command to easily retrieve the assembly context of a contextual CATPart stored in VPM V4 in a PSN. This takes into account the right instance of this CATPart.
  • Provides publication-where-used function — Improved impact analysis with the ability to see the parts that have the associated publication.
  • Supports groups in the clash analysis. Users can now set up two groups for computation. No clash analysis is computed between the representations within a given group. A group is represented by a session file either saved as a file or as a database.
    • Populates clash panel with information about the parts involved in the clash
    • Includes new batchpack to define clash computation specifications by batch
    • Adds Selection against selection option in ITFCHECK batch panel
  • Allows user to open a new PSN from a node selected within an open PSN.
  • Exposes applicative container links. Relation between container and instances/document revision are now exposed and managed in impact graph.
  • Includes a Massive Duplicate command. Enables the user to perform a single command in VPM to:
    • Run the duplication of the whole assembly: parts, assembly links, all documents (included containers)
    • Load connected Assembly Constraints and Contextual Design
  • Resets positioning matrix: translation and rotation.
  • Includes improved CATIA V5 save mechanism — Provides access to better granularity that enables users to:
    • Know exactly what will be saved
    • Decide precisely what will be saved
    • Preserve data integrity during this granular save, especially in the context of links

    There are additional benefits:

    • Enables the user to have access to a detailed report
    • Improves performances/usability DMU /ENOVIAVPM Interoperability
  • Gets context from drawing
    • When a user has designed a CATIA V5 assembly drawing, it can be stored anywhere and even attached to a part that is not instantiated in the related assembly. Users can then define a methodology to remind themselves which root was used to define the assembly drawing in order to open the right one.
    • Get Context for CATIA V5 Assembly Drawings performs queries to identify which root part was used to design the assembly drawing and which instances have been used. Once done, the following occurs:
      • The corresponding PSN is opened.
      • Instances involved in assembly drawing design are expanded.
      • Related representations are highlighted.
  • Includes new pub/sub event on update version/revision that allows better collaborative work.
  • Supports cache filling while reading CATIA V5 document — cache filled on the flight.
  • Allows new feature management at the database level — Accurate information published at the database level in order to avoid save irrelevant blobs and obtain better performance.
  • Shows up-to-date status on document in impact graph — This capacity allows user to differentiate the status on a relation from a status on a document if an update of the document itself is necessary.
  • Delivers refresh attributes in PSN. If other users are modifying attributes in the database, ability to refresh the values in the current PSN is already loaded.
  • Exposes document size in the way documents are currently available on V4 models.

DELMIA Integration

  • DELMIA IGRIP Release 5.4 support — Recognition of .gz documents as coming from IGRIP (V1R5PTF15)
  • DELMIA via PPR Hub support
    • Transfer of product structure data, configuration effectivities and 3D graphical representations (in CGR format) from ENOVIAVPM to DELMIA applications through the PPR Hub (requires an ENOVIA 3d com license)
    • Transfer of instance data
    • Management of delta changes to be sent to DELMIA applications via the PPR Hub

      Note: The PPR Hub is a common source for product, process and product data for all DELMIA E5, D5 and V5 products.

Open architecture: Expose new APIs during the following operations or to influence behavior:

  • Create part, model, document
  • Delete part, model, document
  • Copy
  • Paste same position
  • Duplicate link
  • Replace
  • Set child Action type
  • Configuration Handler visibility
  • Validate attribute before PrepareWrite
  • Retrieve link and entities
  • Control visualization of objects on the PSN graph: icons, part colors, hide/unhide, and so on
  • Depart — When leaving ENOVIAVPM (prior to DB disconnection)
  • Allow attribute management on CATVPMNode API
  • Add user methods on PSN pull-down
  • Provide user exit to control proposed effectivities
  • Provide user exit for AuthorizedDuplicatePart
  • Provide user exit to sort environment list

Miscellaneous

  • Allows more than 10 strings in the simple query history. Extends the query history.
  • Manages time-out for unused ENOVIAVPM — First implementation of a time-out intended to automatically terminate ENOVIAVPM applications after a period of inactivity, thus releasing any associated resources such as licenses.
  • Acts without BLOB.
  • Declares PSN user method without specifying table.
  • Filters document in batch STEP export.
  • Transfers security clusters.
  • Supports database views supported while creating security clusters. This allows users to use table view attributes (for example, a join between tables) when creating a security cluster.
  • Searches part in a non-expanded tree.
  • Cleans event record and blank effectivities — Remove unnecessary effectivity links in the PSN in order to improve performances in bounding box generation.

 
Back topBack to top
 
Technical information

Hardware requirements

Because ENOVIAVPM V1.6 is a workstation application, consideration should be given to the type of workstation, operating systems, amount of disk space and real memory required, supported relational databases, and recommended software levels. These prerequisites are outlined below. Depending on the implementation, use of a license management tool, such as IBM License Use Management (LUM), may be required.

Hardware requirements in an AIX® environment

Processor requirements: ENOVIAVPM may be used on any RS/6000®, based on PowerPC 604™ (166 MHz minimum clock speed), POWER4™ or POWER5™ processor families, supported on AIX V5.3 ML03, provided that requirements described below are met.

Required processor components and features

  • Real memory: A minimum of 256 MB of real memory is required.
  • A CD-ROM drive for program installation.

    Installation of ENOVIAVPM V1.6 for IBM RS/6000 requires an internal or external CD-ROM drive. This drive requires a SCSI High-Performance Input/Output (I/O) Controller, which is either standard or an optional feature (depending on the RS/6000 model).

    A CD-ROM drive is required to view the on-line documentation in HTML format.

    Product documentation explains installation on other network-connected RS/6000 machines after the initial installation with the drive.

  • Direct Access Storage: ENOVIAVPM V1.6 licensed programs and configurations, user data and user programs may be stored on any internal or external Direct Access Storage Devices (DASD) supported by the RS/6000.

    The following DASD requirements are approximate:

    • All installed products of ENOVIAVPM V1.6: 700MB + usage environment. Refer to the Program Directory to estimate disk space requirements for specific products and configurations.
    • Minimum Paging Space: 256 MB.

Optional components and features

  • Locally-attached plotters

    ENOVIAVPM V1.6 directly supports locally attached IBM color pen plotters and can be used with other OEM plotters. (Refer to the Software requirements for AIX section for more details).

  • The following plotter/printer languages are supported:
    • CGM-ISO, ATA, CALS
    • Hewlett Packard HP-GL/2-RTL and HP-GL or IBM-GL subsets
    • OCE Graphics GPR50: VDF plotting routines
    • PostScript

Note: Customers should contact the appropriate plotter vendor for plotter connection and technical support.

Configuration requirements

RS/6000                        Required
Graphics device adapter        Required
Color graphics display         Required
Keyboard                       Required
3-button mouse                 Required
CD-ROM drive                   Required*
 
(*) For installation only.

Required processor components and features

Graphics devices (one of the following):

  • POWER™ GXT500P 12-Bit and GXT550P 24-Bit (feature numbers 2854 and 2855)
  • POWER GXT800P 24-Bit and GXT800M 24-Bit (feature number 2853 or 2859 and 2850)
  • POWER GXT2000P
  • POWER GXT3000P (feature number 2825)
  • POWER GXT4000P
  • POWER GXT4500P
  • POWER GXT6000P
  • POWER GXT6500P

Note: Other adapters are not supported by ENOVIAVPM V1.6. Although this product might run with other adapters, incidents encountered that are specific to other adapters will not be accepted for analysis or correction.

Peripheral requirements

Required components and features

  • Three-button mouse (feature number 6041)
  • Alphanumeric keyboard
  • Display

    One display compatible with the graphics devices is listed.

Hardware requirements in a Hewlett-Packard environment

Processor requirements: Any B-Class, C-Class or J-Class workstation based on a PA8000 processor family, supported under HP-UX 11.11 (HP-UX 11i Dec 2004), provided that requirements described below are met

Required processor components and features

  • Real memory: A minimum of 256 MB of real memory is required.
  • An internal or external CD-ROM drive is required for program installation.

    This equipment is required to perform an initial installation. Product documentation explains installation on other network-connected HP workstations after the initial installation with the drive.

    A CD-ROM drive is required to view the online documentation in HTML format.

  • Disk space: ENOVIAVPM V1.6 licensed programs and configurations, user data, and user programs may be stored on any internal or external disk by the HP workstation.

    Approximate disk space requirements are as follows:

    • All installed products of ENOVIAVPM V1.6: 700 MB + usage environment
    • Refer to the Program Directory to estimate disk space requirements for specific products and configurations.
    • Minimum swap space: 256 MB

Configuration requirements

HP Workstation Processor       Required
Graphics card                  Required
Color graphics display         Required
Keyboard                       Required
3-button mouse                 Required
CD-ROM                         Required*
 
(*) For installation only

Required graphics processors

Graphics cards

  • VISUALIZE FXE
  • VISUALIZE FX2
  • VISUALIZE FX4
  • VISUALIZE FX5
  • VISUALIZE FX6
  • VISUALIZE FX10
  • Fire GL-UX
  • Fire GL T2-128
  • Fire GL X1
  • FireGL X3

Peripheral requirements

Two types of connectors can be used for a peripheral component:

  • HP-HIL connector
  • Serial connector

Required components and features

  • Three-button mouse (A2839B or A2838A)
  • Alphanumeric keyboard
  • One display compatible with the graphics cards listed

Hardware requirements in an SGI environment

Important note: SGI platforms (clients and servers) are no longer supported (end of support — ENOVIAVPM V1.5 PTF34).

Hardware requirements in a Sun environment

Processor requirements: Any Ultra1, Ultra2, Ultra10, Ultra30, Ultra60, Ultra80, SUN Blade 100, SUN Blade 150, SUN Blade 1000, SUN Blade 1500, SUN Blade 2000, SUN Blade 2500 or SUN Blade 1500+ (1.5GHz)workstation based on UltraSPARC processor, supported on Solaris 10.03/05, provided that the following requirements described are met.

Required processor components and features

  • Real memory: A minimum of 256 MB of real memory is required.
  • A CD-ROM drive is required for program installation; this drive must be compatible with the following Sun models:

    Product documentation explains installation on other network-connected SUN machines after the initial installation with CD drive.

    A CD-ROM drive is required to view the on-line documentation in HTML format.

  • Disk space: ENOVIAVPM V1.6 licensed programs and configurations, user data and user programs may be stored on any internal or external disk by the SUN machines.

    Approximate disk space requirements are as follows:

    • All installed products of ENOVIAVPM V1.6 solutions: 700 MB + usage environment

      Refer to the Program Directory to estimate disk space requirements for specific products and configurations.

    • Minimum swap space: 256 MB

Configuration requirements

SUN workstation                  Required
Graphics card                    Required
Color graphics display           Required
Keyboard                         Required
3-button mouse                   Required
CD-ROM drive                     Required*
 
(*) For installation only

Required processor components and features

Graphic device adapter (one of the following):

  • Creator3D
  • Creator Series III
  • Elite3D model M3 for Ultra10 440MHz workstation
  • Elite 3D model M3 and M6 for Ultra60 workstation
  • Expert3D
  • Expert3D-Lite
  • XVR-500
  • XVR-1000
  • XVR-1200
  • XVR 600 (Support of XVR-600 requires OpenGL 1.3)

Peripheral requirements

  • SUN three-button mouse
  • Alphanumeric keyboard
  • One display compatible with the graphics card listed above

Relational database DASD requirements:

A relational database is required for proper operation of ENOVIAVPM V1.6. A minimum of 700 MB of hard disk space is necessary for system installation. 150 MB should be available for database application and data files. Refer to the Software requirements section for supported database products.

Compatibility: ENOVIAVPM provides a consistent user, database, and application programming interface. Data is compatible among the supported operating systems: AIX, HP-UX, and Solaris, and ENOVIAVPM can use and exchange data in industry-standard formats including STEP AP203 and AP214.

Performance considerations: Performance and response time are influenced by several factors including processor and operating system, amount of system memory, channel speeds, the number, type, and organization of terminals, and the size of the data elements being used. ENOVIAVPM is designed for optimum benefit under all supported operating systems.

Software requirements

The overall requirements for ENOVIAVPM V1.6 are identical to those described in the announcement letter for ENOVIAVPM R1. Refer to Software Announcement 298-246 , dated July 7, 1998. CATIA and DELMIA plug-ins are supplied with the products and require no additional prerequisites. However, for CATIA V4, CDA and CDR must be separately installed. If ENOVIAVPM is used to manage CATIA V5 data only, there is no requirement to install CATIA V4.

Statement of Direction: To assist CATIA customer planning, IBM intends to announce and make available a future release level of CATIA V4, which will interoperate with ENOVIAVPM V1.6. As with any development plan, the timing and our ability to deliver is subject to change.

Refer to the Program Directory for interoperability level required relative to CATIA V5 and DELMIA V5.

Software requirements in the AIX environment

Note: Standard support for AIX V5.1 ended on April 1, 2006, and end of support (EOS) for AIX V5.2 is September 1, 2007. To ensure a consistent level of maintenance and service for CATIA and ENOVIA VPLM, customers are encouraged to migrate to AIX V5.3.

AIX V5.3 Maintenance Level 03 (using 64-bit kernel) with the following components:

  • XL C/C++ Enterprise Edition V7.0.0 Run-time Environment
  • XL 7 May 2005 PTF R/T (xlC.aix50.rte at level 7.0.0.6), delivered through APAR IY71976
  • XL Fortran Enterprise Edition V9.1.0 for AIX Run-Time November 2004 XL Fortran for AIX V9.1 Runtime PTF, available at
  • IBM eServer® P5 Server Support and IBM IntelliStation® POWER 285 support requires AIX V5.3 ML03.

    Note: AIX V5.3 ML03 is supported on Power 4 and Power 5-based system only.

  • Compiler: Visual Age C++ 6 for AIX V5 at level 6.0.0.7 ( March 2004 Visual Age C++ 6 for AIX PTF)
  • An HTML browser is required to access this documentation: for example, Mozilla 1.7 with Java™ plug-in installed.

Note: Refer to RETAIN® and/or the ENOVIAVPM Version 1 Release 6 Program Directory for the appropriate PTF to be applied.

DBCS support requirements

DBCS-enabled version of the operating system

Software requirements in the HP environment

HP 11i December 2004 support requires:

  • HP-UX Technical Computing OE Component, December 2004
  • Hardware Enablement Patches for HP-UX 11i v1, December 2004
  • Gold Applications Patches for HP-UX 11i v1, December 2004
  • Gold Base Patches for HP-UX 11i v1, December 2004
  • With following patches applied:
    • PHCO_31923: libc cumulative header file patch
    • PHCO_33360: libc cumulative patch
    • PHKL_31918: fsadm;ACL;locking order;8K mount;readdir
    • PHNE_32477: ONC/NFS General Release/Performance Patch
    • PHSS_29483: HP aC++ Compiler (A.03.52)
    • PHSS_31271: PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
    • PHSS_31274: Starbase/Hardcopy Dev (PA2.0 only)
    • PHSS_31275: OpenGL 1.1 Dev (PA2.0 only)
    • PHSS_32573: HP aC++ -AA runtime libraries (aCC A.03.61)
    • PHSS_32928: 3D Common Run (PA2.0 only)
    • PHSS_32934: OpenGL 1.1 Run (PA2.0 only)
    • PHSS_32939: Xserver cumulative patch
    • PHSS_33033: ld(1) and linker tools cumulative patch

Note: Refer to RETAIN and/or ENOVIAVPM Version 1 Release 6 Program Directory for the appropriate PTF to be applied.

Contact your HP representative for further information on hardware and software migration programs.

DBCS support requirements

DBCS-enabled version of the operating system.

Software requirements in the SGI environment

Important note: SGI platforms (clients and servers) are no longer supported (end of support — ENOVIAVPM V1.5 PTF34).

Software requirements in the Sun environment: ENOVIAVPM V1.6 is designed to operate with Solaris 10 SPARC Operating System Release 03/05, no additional patches: C, C++ Sun Studio 10 compiler

Note: Refer to RETAIN and/or ENOVIAVPM Version 1 Release 6 Program Directory for the appropriate PTF to be applied.

DBCS support requirements

DBCS-enabled version of the operating system

DBMS requirements

  • DB2 Universal Database® (DB2 UDB)
    • On the database server side, DB2 UDB V8.2.2
    • On Client side: when running on Windows™, IBM AIX, HP-UX 11i or Sun Solaris, DB2 UDB Client V8.2.2 minimum
  • Oracle Enterprise Edition
    • On the database server side, ORACLE Enterprise Edition, 9.2.0.3 or 10.2.0.2
    • On the Client side: when running on Windows, IBM AIX, HP-UX or Sun Solaris, ORACLE 9.2.0.3 or 10.2.0.2 minimum

Software installation: Refer to the Virtual Product Model Installation and Administration Guide .

National language support: English is the only language delivered for ENOVIAVPM V1.6.

Double byte character set-enabled: Yes.

Documentation

  • Virtual Product Model Installation and Administration Guide
  • Virtual Product Model User's Guide
  • Generative Technical Publications
  • ENOVIA VPM/PM Interoperability
  • ENOVIA VPM/SAP Interoperability

Note: Refer to documentation for ENOVIA 3d com when using ENOVIAVPM client functions on Windows platforms.

Improvements in HTML searching and printing capabilities eliminate the need to duplicate product information in the Portable Document Format (PDF) format. PDF CDs are therefore no longer included in the ENOVIAVPM softcopy collection kit.

Licensing

Named user and concurrent user licensing

ENOVIAVPM Version 1 up to and including Release 4 was available only with named-user licensing. To provide customers with additional purchasing and licensing flexibility, ENOVIAVPM V1.5 introduced concurrent-user licensed, role-based configurations (Engineer, Manager, and so on)

ENOVIAVPM utilizes a People & Organization (P&O) database to define and manage these configurations and the individual usage profiles available to users. At sign-on, ENOVIAVPM looks identical to users whether they continue to use named-user licensing or move to the new concurrent-user licensing method. Licenses for configurations defined in usage profiles will be taken at sign-on time and released when the user session is discontinued.

Named-user requires that one role-based configuration is available for each corresponding user defined in the P&O database. Concurrent-user requires users to have sufficient quantities of each role-based configuration available for concurrently signed-on users of that configuration.

Use of CATIA licenses

When an ENOVIAVPM V1.6 user first calls CATIA V4 for design in context, the CATIA V4 plug-in is called which takes one each of CATIA CDA, CDR, and COM licenses. Similarly, CATIA COM licenses are also taken if one of the following operations is attempted:

  • Create a part
  • "Version" a part with same or new part number
  • Duplicate a part
  • Revise a CATIA model
  • Perform a quick import
  • Create a read STEP file

Note: If ENOVIAVPM is used to manage CATIA V5 data only, there is no requirement to install CATIA V4 products or licenses.

Use of ENOVIAPM licenses

When an ENOVIAVPM V1.6 user calls ENOVIAPM for any of the interoperability functions, an ENOVIAPM Software Development Kit (SDK) Author license is requested. If the SDK license is not available, an ENOVIAPM Director license is requested.

Concurrent and nodelocked licensing

Multi-user environment

When using ENOVIAVPM in a multiuser environment with LUM, LUM Runtime code V4.5.5 is the minimum level required on AIX, HP-UX, and Sun license servers and clients. LUM for AIX is delivered as a standard component of AIX. For HP and Sun platforms, you can download LUM Runtime V4.5.5 or later from the following IBM Internet site

LUM is available to licensed ENOVIAVPM users whose installations include multiple IBM, HP, or Sun workstation machines that are interconnected by a TCP/IP-supported Token-Ring or Ethernet local area network or for concurrent execution of ENOVIAVPM programs on a single workstation.

ENOVIAVPM for UNIX® workstations use LUM to control the number of licenses acquired for the program. Using LUM administration facilities, system administrators can configure ENOVIAVPM products for workstations to permit access to ENOVIAVPM programs on one of the several workstation platforms provided.

Single-user environment without License Manager: In an installation without LUM, ENOVIAVPM Solutions for workstations licensed programs can be licensed to operate on a single workstation. In this mode of operation, ENOVIAVPM program use is restricted to the workstation for which it is registered during the installation process. In any configuration, either stand-alone or LAN when more than one use of an ENOVIAVPM licensed program is desired on a single workstation, LUM is required.

Note: For more information about LUM, go to the LUM Web page

For use with HP-UX and Sun Solaris, LUM is available for free from the following IBM Internet site

Performance considerations: Performance and response time are influenced by several factors including processor and operating system, amount of system memory, channel speeds, the number, type, and organization of terminals and the size of the data elements being used. ENOVIAVPM is designed for optimum benefit under all supported operating systems.

Planning information

Packaging

ENOVIAVPM V1.6 packaging: Contents include:

VPM V1.6

  • Four code CDs (LCD4-2040) in a quad jewel case contain:
    • AIX for Concurrent and Named User
    • HP-UX for Concurrent and Named User
    • Sun Solaris for Concurrent and Named User
    • VPM Program Directory
  • English Online Documentation in a single jewel case (SK21-0292)
  • One LUM Run Time V4.6.8 CD in a trim pack (LCD4-7885)
  • DB2 V8.2 Enterprise Server Edition CDs (LCD4-7874) — 19 code CDs in Univenture sleeve
  • DB2 V8.2 Enterprise Server Edition Fix Pack 9a (LCD4-7884), equivalent to V8.2.2 — 9 code CDs in a Univenture CD sleeve
    • AIX (2 CDs)
    • HP-UX
    • Solaris (2 CDs)
    • Windows (4 CDs)
  • Informal documents
    • PLM Products Current User Memorandum (GI11-4403)
    • PLM Products Software Registration Memorandum (GI11-4404)
    • VPM 1.6 Licensed Program Specification (GH52-1321)

Security, auditability, and control

The announced programs use the security and auditability features of the operating system software. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
 
Back topBack to top
 

Ordering information

Current licensees

Current licensees will receive this update from IBM Software Delivery and Fulfillment automatically.

Shipment of ENOVIAVPM V1.6 is scheduled to be completed by October 13, 2006.

New licensees

Orders for new licenses can be placed now.

Unless a later date is specified, orders entered before the planned availability date will be assigned a schedule date of one week following availability.

Shipment will begin on the planned availability date.

Basic license: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the feature number of the desired distribution medium shown below.

New products: There are no new products for V1.6.

Withdrawn products: There are no withdrawn products for V1.6

Renamed products: There are no renamed products for V1.6.

Configuring orders: For orders of ENOVIAVPM V1.6 for Microsoft™ Windows, IBM AIX, HP-UX, SGI IRIX, or Sun Solaris platforms, configure ENOVIA VPLM using the ECFGRS6000 configurator.

To configure orders, specify the platform feature numbers specified below with a quantity equal to the number of users.

Software                                             Feature
platform                                             number
 
AIX                                                  5350
Hewlett Packard HP-UX                                5351
Sun Solaris                                          5354

To ship machine-readable materials and publications and to register for future updates, one System Program Order (SPO) (5628-VPM) must be placed in addition to the basic license orders (5691-xxx).

Product feature numbers:                             SPO
Type and                                             feature
model       Product name                             number
 
5691-ADX    ENOVIAVPM Casual User Solution           2710
5691-CDX    ENOVIAVPM Administrator Solution         2711
5691-DEX    ENOVIAVPM CDM Engineer Solution          2712
5691-MSX    ENOVIAVPM Engineer Solution              2713
5691-REX    ENOVIAVPM Manager Solution               2714
5691-VPX    ENOVIAVPM Product Engineer Solution      2715
5691-VSX    ENOVIAVPM SAP-Interoperability Solutions 2716
5691-ADE    ENOVIAVPM Engineer Solution              2700
5691-TPS    ENOVIAVPM Generative Technical           2701
 
             Publications Solution
5691-MSS    ENOVIAVPM Manager Solution               2702
5691-REV    ENOVIAVPM Casual User Solution           2703
5691-ADM    ENOVIAVPM Administrator Solution         2704
5691-VPM    ENOVIAVPM Infrastructure Product         2705
5691-CDE    ENOVIAVPM CDM Engineer Solution          2706
5691-VPD    ENOVIAVPM Product Engineer Solution      2707
5691-VSI    ENOVIAVPM-SAP Interoperability Solution  2709

Within the SPO, specify the media feature number for each of the workstation platforms you will be using.

Media feature numbers:

                  Media
Workstation       feature        Distribution
Platform          number         medium
 
AIX               3410           CD-ROM
HP-UX             3417           CD-ROM
Sun Solaris       3420           CD-ROM

Customization options: Select the appropriate feature numbers to customize your order to specify the delivery options desired. These features can be specified on the initial or MES orders.

For example, if publications are not desired for the initial order, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then the publications will ship with the next release of the program.

Feature                Description
 

Initial shipments

 
3470                   Ship Media Only
                        (suppresses initial shipment
                        of documentation)
 
3471                   Ship Documentation Only
                        (suppresses initial shipment
                        of media)
 

Update shipments

 
3480                   Ship Media Updates Only
                        (suppresses update shipment
                        of documentation)
 
3481                   Ship Documentation Only
                        (suppresses update shipment
                        of media)
 
3482                   Suppress Updates
                        (suppresses update shipment of
                        media and documentation)
 

Expedite shipments

 
3445                   Local IBM Office Expedite
                        (for IBM use only)
 
3446                   Customer Expedite Process Charge
                        ($30 charge for each product)

Expedite shipments will be processed to receive 72-hour delivery from the time IBM Integrated Supply Chain (ISC) receives the order. ISC will then ship the order via overnight air transportation.

Unlicensed documentation: One English softcopy publication CD-ROM, ENOVIAVPM V1.6 Softcopy Collection Kit -- English, is automatically included in all shipments. To order, specify the language using the feature number 7100. Only one additional copy of a kit can be ordered per license.

Additional Softcopy Collection Kits can be ordered through your IBM representative or business partner using the publication number SK21-0292, for the ENOVIAVPM Version 1 Release 6 Softcopy Collection Kit — English.

Displayable Softcopy Publications

ENOVIAVPM V1.6 product publications are offered in displayable and printable HTML form. All unlicensed manuals are included. These softcopy manuals are part of the basic machine-readable material that at automatically ships with an order for a standard or custom configuration. The manuals are shipped on CD-ROM. Terms and conditions for use of the machine-readable files are shipped with the product.

The displayable manuals are in HTML format and can be viewed in any of the supported environments using one of the HTML browsers specified in the Software requirements section. The Adobe Acrobat Reader may be downloaded, at no charge, from

Additionally, customers with the Enhanced Support Offering can view the latest ENOVIAVPM V1.6 publications in HTML form by going to

Then select the Technical Support choice.

Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed.
 
Back topBack to top
 

Terms and conditions

Agreement: IBM Customer Agreement

Designated machine: Not required

Variable charges apply: No

Location license applies: No

Use limitation applies: Yes

Additional licenses, features, or authorizations, as appropriate must be obtained to extend use levels.

Additional licenses or features, as appropriate, must be obtained to exceed usage limits.

Use of DB2 UDB components:

ENOVIAVPM V1.6 is shipped with the DB2 Universal Database (DB2 UDB) program. You are authorized to use this DB2 UDB only in conjunction with and in support of the Solution (as defined below), and are authorized to install and use this DB2 UDB only in association with your licensed use of the ENOVIA VPLM products for the storage and management of data used or generated by the Solution and not for any other data management purposes. Only inbound and outbound data transactions in which the Solution directly either creates, reads, updates or deletes data are permitted.

Examples of uses not permitted include (i) inbound connections to the database from other applications for queries or report generation, or (ii) outbound database connections in which the Solution provides no added value to the data transaction.

The Solution and DB2 UDB can be installed on either the same server or separate servers. In the case where DB2 UDB is installed on a separate server, the access point to the DB2 UDB server must be solely through the Solution server.

Solution is defined as any ENOVIA VPLM or ENOVIA SMARTEAM program product other than those listed as follows:

  • SMARTEAM — Development Suite, a component of the IBM program product SMARTEAM — Development Suite Configuration (5691-SDV)
  • All CAA RADE products and APIs

Educational allowance available: No.

Volume orders: Contact your IBM representative.

Warranty applies: Yes

Licensed program material availability

  • Restricted Materials of IBM: None
  • Non-Restricted Source Materials: None
  • Object Code Only (OCO): All

Program services: Program Services offer a method of reporting code-related problems for ENOVIAVPM licensed software products. Program Services are available electronically using the problem submission process at the PLM Technical Support Web site at

Note: In order to use this facility, you must use an IBM ID which has associated to it the licensed IBM customer number under which the product was purchased. If you have not yet obtained an IBM ID, visit

If you have not yet associated the licensed IBM customer number to your IBM ID, you will be prompted to do so when accessing the problem submission facility.

When using Program Services, the problem report is submitted via the PLM Technical Support web site; all subsequent communications will be via e-mail. The response time for these problem reports, regardless of the severity, will be within two business days. All communications must be in English.

Not all options of the Product Lifecycle Management (PLM) technical support e-services are available in all countries.

Program Services for ENOVIAVPM also includes problem submission via telephone through the IBM Support Center at 800-IBM-SERV.

During the Program Services period, Corrective Service for ENOVIAVPM V1.6 will be delivered through PTFs (Program Temporary Fixes) on a regular basis. PTFs are provided at the same time for all platforms currently supported. PTFs are a cumulative collection of fixes; each PTF supersedes the previous one and may be installed on top of the released level or on top of a previous PTF.

For critical situations, individual fix packages may be provided for a specific PTF level (for code defects, based on technical feasibility, where a search for a work-around has been performed and was unsuccessful, and where an impact analysis has shown no risk of destabilization). These fix packages are called Hot Fixes and are cumulative for that PTF level. These interim fix packages will only be produced for PTF levels that have been available for less than 24 months. Fixes provided in these fix packages will be included in the next available PTF.

Note: Customers experiencing problems with DB2 UDB V8.2 delivered with the ENOVIAVPM product may report these problems through PLM product support, as long as DB2 UDB is being used in conjunction with ENOVIAVPM and the DB2 and ENOVIAVPM products are still within their respective support periods. Customers will receive the same level of support as they are entitled to for their ENOVIAVPM products.

Customers experiencing problems with IBM License Use Management (LUM) products when used with ENOVIAVPM products may report these problems through PLM product support. Note this only applies when the LUM product is being used in conjunction with an ENOVIAVPM product and the ENOVIAVPM product is within its support period.

End of support for ENOVIAVPM V1.5.0 will be December 31, 2007.

End of support for ENOVIAVPM V1.6 will be December 31, 2009.

For a list of all currently supported releases of CATIA, ENOVIA VPLM and ENOVIA SMARTEAM products, visit

At the bottom of the page, select "End of support dates" under Plan -> Product life cycle.

IBM Operational Support Services — SupportLine: No

Other support: PLM Support Centers
 
Back topBack to top
 

Prices

The prices provided in this announcement are suggested retail prices for the U.S. only and are provided for your information only. Dealer prices may vary, and prices may also vary by country. Prices are subject to change without notice. For additional information and current prices, contact your local IBM representative.

License charges

Types of charges

  • Annual License Charge (ALC)
  • Primary License Charge (PLC)

PLC

PLM software offerings are licensed under the terms and conditions of the ICA (IBM Customer Agreement) or the IICA (IBM International Customer Agreement) or equivalent agreement in effect between us. The customer must sign one of these agreements as a prerequisite to processing the purchase order for licensing a PLM software product offering. The ICA, IICA, or equivalent is signed only once by an IBM customer.

With a valid ICA/IICA and purchase order for this PLM product and while paying the PLC and applicable recurring charge, the customer has:

  • The right to use the license
  • Warranty support and use of program services as described under Program services in the Terms and conditions section
  • The right to receive enhancements and future releases, if any, of the same version at no additional cost. Significant new functions may be offered as an optional feature and charged for separately. If a replacement program is announced, and the customer elects to license the replacement program for a PLC/ALC and replace the prior program, an upgrade charge may apply. The upgrade charge will be less than the full PLC for the replacement version.

The first payment consists of the PLC and ALC. The ALC applies yearly thereafter.

Program upgrades

Program upgrade charges will apply for upgrades from CATIA Solutions V4 on a "like-for-like" basis.

The program upgrade charge applies to orders for the replacement program when it replaces a prior program that was obtained for a PLC/ALC and is discontinued upon installation of the new version. If the prior program is not discontinued, the full PLC and ALC apply to the replacement program.

Entry support license OTC: An OTC authorizes use only on IBM Entry End User/390 Machines.

Program upgrade charge

Use level charge: Charges for this program are based on usage levels. When a customer upgrades to a higher level of usage, a usage upgrade charge will apply, equal to the difference between the charge for the current level of usage and the higher level of usage.

IBM Global Financing

IBM Global Financing offers competitive financing to credit-qualified customers to assist them in acquiring IT solutions. Our offerings include financing for IT acquisition, including hardware, software, and services, both from IBM and other manufacturers or vendors. Offerings (for all customer segments: small, medium, and large enterprise), rates, terms, and availability can vary by country. Contact your local IBM Global Financing organization or visit the Web site

IBM Global Financing offerings are provided through IBM Credit LLC in the United States and other IBM subsidiaries and divisions worldwide to qualified commercial and government customers. Rates are based on a customer's credit rating, financing terms, offering type, equipment type, and options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension, or withdrawal without notice.

Trademarks

 
PowerPC 604, POWER4, POWER5, and POWER are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
DB2, AIX, RS/6000, eServer, IntelliStation, RETAIN, and DB2 Universal Database are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Microsoft, and Windows are trademarks of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
UNIX is a registered trademark of the Open Company in the United States and other countries.
 
Other company, product, and service names may be trademarks or service marks of others.

Back to topBack to top
 

 
Printable version Printable version