Description :
ENOVIA Studio Modeling Platform provides the configuration and administration capabilities for ENOVIA, which was designed from the ground up to support change and flexibility. As an organization’s processes change, customers can easily change the standard processes and user interface to retain their competitive advantage. Companies can easily configure solutions to meet specific business needs. The ENOVIA Studio Modeling Platform provides the necessary tools to quickly configure, and extend the standard product capabilities and business processes.
The ENOVIA Studio Modeling Platform includes the following primary tools:
- ENOVIA Studio MQL — Command line interface tool for executing commands and scripts for ease of migrating changes across multiple
- ENOVIA systems ENOVIA Studio System Administration — Tool for managing and configuring the database and file vaults for storage of the ENOVIA data.
- ENOVIA Studio Business Modeler — Tool to manage the data model and its associated business process including data types, attributes, relationships, security, lifecycle, workflow, and web user interface design.
- ENOVIA Matrix Navigator — Tool to query the ENOVIA instantiated data objects based on the data model. This application is required to administer triggers and other configuration objects.
- ENOVIA Studio VPM Data Model Configuration — Tool to administer the VPM data model. It complements ENOVIA Studio Business Modeler and provides additional capabilities to simplify VPM data model customizations.
Key features and capabilities ENOVIA Studio Modeling Platform include:
User Interface Components
A rich set of user interface tools are provided to deliver significant functionality with minimal programming effort in order to easily change the presentation and capabilities of standard ENOVIA products and best of all, changes are upgradeable with future software updates. The user interface tools are access-controlled to provide role-specific views and are used to model the entire user experience – menus, forms, tables, structure, actions, etc. -- in the user’s preferred language.
Dynamic Modeling
The underlying schema and business processes are all modeled and configured using the ENOVIA Studio Modeling Platform. Administrators can easily extend the business model or make changes to the standard model. Such capabilities include the ability to define new business types, attributes, relationships, policies, workflows, organizations, people, etc.
Advanced Full-text Search Component
Full-text functionality is standard capability with ENOVIA Live Collaboration. This advanced search functionality leverages the OEM IDOL platform from Autonomy and is encapsulated into a generic, configurable search component that is used throughout the applications providing rich and consistent search experience. Administrators can not only use this component in their development, but can extend its behavior through configuration. Configuration includes specifying search types, attributes and related business object data for end-user keyword searching. In addition, administrators define and configure additional taxonomies and parametric fields to aid the user in refining and reducing the search results. Administrators can deploy additional IDOL servers to maintain optimal performance and scalability.
The full-text search component does require additional infrastructure and setup requirements of a full-text index server. In order to avoid infrastructure requirements and setup of full-text index server, a toggle mode to enable/disable full-text search is provided in favor of traditional ENOVIA database searching. ,
Persistent Object Identifiers
The ENOVIA system automatically generates “persistent” object identifiers for all business objects and relationships. These identifiers are not only persistent as meta-data changes but also guaranteed to be unique across multiple instances and deployments. With persistent and unique identifiers across all ENOVIA deployments, replicating and synchronizing data across systems can be simplified by detecting that an object has been previously replicated based on the existence of a persistent id in the target system.
Distributed File Store Management
Distributed file storage ensures optimal performance for remote users. Files are copied and placed at various remote file servers positioned close to the end-user for best file transfer times. To establish new remote file stores, administrators can leverage tools provided to clone existing file locations and pre-populate the remote sites with file data; otherwise, data is replicated on-demand as files are accessed by remote users. As disk storage runs low, administrators can purge files that are least-accessed while the master copy is still maintained at a different site. Note that an ENOVIA File Collaboration Server (FCS) product license is required for each remote site requiring distributed file store management.
Case Sensitive/Insensitive Databases
The deployment of the ENOVIA system can be based on a number of databases such Oracle, DB2, SQL Server and MySQL. With the exception of DB2 which is always case insensitive, all other deployments can be configured as case sensitive or insensitive. While most deployments are case sensitive, some implementations prefer a case insensitive database so that all user searches are case insensitive by default without having to specify it per search criteria.
Service-Oriented Architecture
Web services enable implementers to manipulate ENOVIA data and business processes using a service-oriented architecture (SOA). Using an interactive web interface, administrators can manage and deploy web services delivered with the ENOVIA system and applications. In addition, administrators can choose which services to deploy as well as establish access rights for what services can be executed by a given user.