enovia basic

Matrix PLM Platform Basics

Version 10.7

© Dassault Systèmes, , 2007.

All rights reserved.

PROPRIETARY RIGHTS NOTICE: This documentation is proprietary property of MatrixOne, Inc. and Dassault Systèmes. In accordance with the terms and conditions of the Software License Agreement between the Customer and MatrixOne, the Customer is allowed to print as many copies as necessary of documentation copyrighted by Dassault Systèmes relating to the ENOVIA MatrixOne software being used. This documentation shall be treated as confidential information and may only be used by employees or contractors with the Customer in accordance with the Agreement.

MatrixOne®, eMatrix®, and Adaplet® are registered trademarks of Dassault Systèmes or its subsidiaries in the US and/or other countries.

AEF, Application Exchange Framework, MatrixOne Design for Workgroups Accelerator, MatrixOne Design to Manufacture Accelerator, MatrixOne Engineering Central, MatrixOne Enterprise Project Management Accelerator, MatrixOne Library Central, MatrixOne IP Management Accelerator, MatrixOne Materials Compliance Central, MatrixOne Program Central, MatrixOne Sourcing Central, MatrixOne Specification Central, MatrixOne Supplier Central, MatrixOne Team Central, IconMail, ImageIcon, Primary Browser, Star Browser, and State Browser are trademarks of Dassault Systèmes or its subsidiaries in the US and/or other countries Oracle® is a registered trademark of Oracle Corporation, Redwood City, California. DB2, AIX, and WebSphere are registered trademarks of IBM Corporation. WebLogic is a registered trademark of BEA Systems, Inc. Solaris, UltraSPARC, Java, JavaServer Pages, JDBC, and J2EE are registered trademarks of Sun Microsystems, Inc. Windows XP and Internet Explorer are registered trademarks of Microsoft Corp. HP and HP-UX are registered trademarks of HP. All other product names and services identified throughout this book are recognized as trademarks, registered trademarks, or service marks of their respective companies.

MatrixOne, Inc. is a wholly owned subsidiary of Dassault Systèmes.

This product includes software developed by the Apache Software Foundation. (http://www.apache.org/)

This product includes software developed by the OpenLDAP™ Project for use in the openLDAP Toolkit. (http://www.openldap.org/)

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

This product includes cryptographic software written by Eric Young. ([email protected])

This product includes GifEncoder and ImageEncoder software written by Jef Poskanzer ([email protected]). Copyright ©1996,1998. All rights reserved.

ENOVIA MatrixOne210 Littleton RoadWestford, MA 01886, USATelephone: 978-589 4000Fax: 978-589-5700Email: [email protected]

Web Address: http://www.matrixone.com

DM-MX-04-10-70

Table of Contents

The Matrix System™ ................................................................................................ 5Matrix Components................................................................................................... 6Business Objects ...................................................................................................... 7Persons and Roles.................................................................................................... 8Groups of People ...................................................................................................... 9Business Object Types............................................................................................ 10Object Attributes ..................................................................................................... 12Powerful User Interface........................................................................................... 13

Icon vs. ImageIcon........................................................................................... 14Icons vs. Details ............................................................................................... 14Visuals Manager .............................................................................................. 16Using Views ..................................................................................................... 17

Relationships .......................................................................................................... 18Navigation ............................................................................................................... 19Files and Formats ................................................................................................... 21File Check-In and Check-Out.................................................................................. 22Object Lifecycle....................................................................................................... 23Policies.................................................................................................................... 24Policies and Lifecycle.............................................................................................. 25States and Signatures ............................................................................................ 26States and Ownership ............................................................................................ 27States and Revisions .............................................................................................. 28Annotations and Attachments................................................................................. 29IconMail .................................................................................................................. 30Automating Processes ............................................................................................ 32Vaults and Stores.................................................................................................... 35Distribution of Data ................................................................................................. 37Incorporation of Legacy Data.................................................................................. 38Business to Business Collaboration........................................................................ 39ENOVIA MatrixOne Applications ............................................................................ 40Dynamic UI Components........................................................................................ 41

Glossary ........................................................................................................................ 43

Table of Contents 3

4 Matrix PLM Platform Basics

The Matrix System™

Matrix is an information management system.

Matrix is a comprehensive system for managing any type of information in any business environment. Matrix provides the flexibility required to organize this information according to your projects, products, or business model.

Most companies produce volumes of documentation and information that must be shared and controlled. Data overload is a common problem in any business environment. Imagine these scenarios:

• You are an engineering manager who manages the design and development of a new product. Distributing information, scheduling, and tracking the status of the project through its design cycle are critical steps in meeting the product delivery date.

• You are a designer who designs a fire extinguisher for a vehicle engine compartment. You work with other members of the design team to access their design layouts and ensure the proper fit and functionality of your design.

• You are a purchasing agent who examines all invoices received from a vendor for a specific project.

Any type of job activity—managing time, developing plans, supervising people, overseeing projects, coordinating team members, tracking critical assignments—can contribute to information and documentation overload. Matrix helps you manage, control, and improve the process and related information flow. You can turn potential chaos into managed control by using Matrix as the central shared information repository.

The heart of Matrix is a database which may contain the types of products created in your business, the attributes associated with those products, and the processes that govern their lifecycles. Storage locations, called vaults, are used to organize the data within the database.

Matrix operates in virtually any configuration to support your unique operating, organizational, and performance needs—on a single computer or in a

networked system environment.

This book introduces you to the concepts and features of the Matrix system.

5

Matrix Components

The Matrix system is a client/server software suite consisting of the following components:

• System ManagerThe System Manager application is used to perform activities related to the configuration and maintenance of database storage locations.

• Business ModelerThe Business Modeler application is used to model the types of objects used in your business, along with the attributes, process rules, and persons associated with those objects. Your business model defines how you will use Matrix, and can be changed as often as your business needs change.

• Matrix NavigatorThe Matrix Navigator application is used to create specific instances of the objects that were defined in the Business Modeler.

• Matrix Query Language (MQL)The MQL application uses a command driven interface to all of the above components. The MQL language helps the Business or System Administrator set up and test an Matrix database quickly and efficiently. The MQL language can be used within the Business Modeler to create custom programs that allow you to tailor Matrix to your specific business needs.

In addition to the applications listed above, the following components are also provided as part of the Matrix system:

• Collaboration Server When access to the database is provided through web browsers, a web or application server as well as one of the Matrix collaboration servers is required. The collaboration server includes several servlets used to communicate with the Matrix collaboration kernel.

• Web NavigatorWeb Navigator is used to access the Matrix database from any Web browser.

The ENOVIA MatrixOne applications are also available to accelerate development of your unique Matrix system.

Integration capabilities are available through the following development environments:

• Matrix Applet ADKThe Matrix Applet ADK allows programmers to write custom applications in either C++ or Java. These custom programs require that a Collaboration Server is in place that accesses the database.

• Matrix Servlet ADKThe Matrix Servlet ADK allows programmers to write custom servlets to extend the functionality of the Collaboration Server.

• Matrix Adaplet™ Development Kit Adaplets™ can be written that allow data from virtually any source to be modeled as Matrix business objects, allowing legacy systems to coexist with Matrix.


Business Objects

Matrix manages objects: documents and related information.

Think of the Matrix database as an efficiently organized library filled with all the documents and related information needed by people within your company or department.

When you look at the Matrix database, you see business objects. Each object represents information needed by Matrix users. In this example, each video, audio, periodical, and book is a separate business object in Matrix.

7

Persons and Roles

Your definition as a person tells Matrix who you are.

You are identified as an Matrix user when you are defined as a person within Matrix. Your person definition enables you to own and access business objects contained within Matrix. It identifies your relationship to other people who use the database.

Your person definition also identifies the role that you play in the organization—your job function. You might be a Manager, Purchasing Agent, Forms Adjuster, Writer, Editor, Desktop Publisher, etc. In this example, the person identified as Mary Kate has the role of an Editor.

It is possible for a person to have more than one role within Matrix. For example, you might be a Manager and an Editor.

Depending on your role, you have access in defined ways to specific types of business objects. Your role also might restrict you from accessing business objects that you do not need.

Roles may have particular Visuals available. For example, if you are a Manager, you may use any tables, tips, filters, cues, and toolsets that have been associated with the role Manager.

Notice the icons shown here for the person and role.

Icons graphically display objects within Matrix so they are easy to identify.


Groups of People

A group shares information.

A group identifies a set of people who are members of the same organization. They may share access to business objects for a common reason, such as a particular project or functional skills. Within a group, people of different talents and abilities may act in different roles.

For example, a general Book Publishing group might include writers, graphic artists, editors, and desktop publishers. This group is centered on the function of publishing books and includes the roles important for group performance.

Another group, consisting of only writers, might be established to research and write a new book. Each member of this group also is a member of the Book Publishing group. However, the Research & Writing group is focused on a specific project (rather than an overall function). Each member of the group has access to the information needed to complete the new book project.

Depending on where the project is in its lifecycle, different people in different groups may work on the project or use the business objects related to it.

9

Business Object Types

A type defines a business object.

Just as you are identified within Matrix as a person with a role, each business object has a name and is defined as a specific type having specific characteristics (attributes). A type defines a kind of business object and the collection of attributes it can have. In a library example, business objects might be of these basic types:

And a type can have any number of sub-types, creating a hierarchy:

Matrix is designed to manage business objects which represent any type of document or related information in your company. A business object might be one of the following types:

• A document such as a drawing, specification, or memo.

• A concept such as a part, change description, or comment.

• A description such as a solid model or N/C path.

TypeFiction

TypeNon-Fiction

TypeHow-to


Each business object in Matrix is uniquely identified in Matrix by its type, name, and revision. Business objects are created by users based on definitions that are established by the Matrix Business Administrator.

Each business object is easily identified with an icon for each object type or with a pictorial Matrix ImageIcon for each individual object. A graphical icon and label indicates the object’s type and name and optional revision. An ImageIcon can be assigned to a specific object to graphically describe it.

IconTypeName

11

Object Attributes

Attributes further define an object within Matrix.

An attribute is any characteristic that you can assign to an object or to its relationship with other objects.

For example, any Non-Fiction book might have attributes describing characteristics about the book (Description, Author, Book Title, Audience, First Edition, and Latest Edition) as well as information related to editing the book (Required Edits, Edit Priority, and Cost):


Powerful User Interface

Matrix offers a complete set of tools so users can configure their desktop to suit their own work style.

Matrix windows are used to display information and to request information from you. Matrix allows you to open separate windows for each activity. In this way, you can manage each window independently.

Each business object shown in the work area of the Matrix browser is displayed as indicated in the user’s preferences. The work area itself even has different visual modes, so users may work in a manner that is efficient for the tasks they must perform, as well as their own unique work style.

work area in Icon mode

message bar

menu bar

toolbar

filter bar

business objects in Icon mode

scroll bars

toolset toolbar

role bar

13

Icon vs. ImageIcon You can change how business objects are displayed in a window by selecting a view preference:

Icons vs. Details Objects themselves are displayed in the browser in the manner that you specify (name, icon, or image). Additionally there are two options to determine which mode the browser uses.

Icon Displays business objects in a browser as icons.

Image Displays business objects in a browser as ImageIcons. When an ImageIcon is not available, Matrix displays the business object as an icon.

ImageIcons can be created either manually by using a raster image clip tool or automatically by using color printing routines for the source applications. (Refer to the descriptions of the grabbing and importing ImageIcons in the Navigator Guide.)

Name

Displays business objects in a window as text information only: the object name, type, and revision.

Icon mode Objects are displayed in rows.

Details mode Objects are displayed in a table in which the rows are the business objects, and the columns contain user-defined data about the objects, such as owner, attribute value, or current state.


When either mode is used, the objects are displayed by Name, Icon, or ImageIcon, as indicated by the user.

Icons

ImageIcons

Matrix browser in Icon mode, with ImageIcon option selected. Objects that are shown as icons, have no associated ImageIcon.

15

When Details mode is used, the table can be sorted based on the contents of any column and printed to any available printer.

Visuals Manager The Visuals Manager provides Matrix users with a variety of user workspace tools which allow you to configure your view of the database to facilitate information flow.

• Cues—Color and font changes can be applied to objects by creating cues. For instance, objects representing work to be done could appear in Red. Once you have completed your task on the object, it could be made to automatically change to green.

• Filters—Filters can be used to display only those objects that you will need to access for a particular task. For example, if you did a search on all Drawing objects, you would probably find many. But if you were to set up a filter for the latest revision, the list presented would be more refined.

• Object Tips—When the mouse is held over a button in the toolbar, the name of the button is displayed. Similarly, you can create and apply object tips that display any selectable information about an object when the mouse points to it.

The Visuals Manager is also used to create and activate tables and toolsets.

The intent of the Visuals Manager is to prepare for a working session—to adjust (and probably restrict) your view of the database according to the tasks you intend to perform. You will use filters to restrict your view of the database by displaying only the objects and relationships that are pertinent to the task at hand. You will use particular tips and cues to graphically highlight information about them. Tables define which details are displayed; toolsets provide access to programs.

Roles may also have workspace items associated with them that users can access through the role bar. The role bar shows only the roles associated with the logged on user.

Matrix browser in Details mode, with Icon option selected.


Using Views Views offer a very flexible and convenient way to package frequently used sets of visuals. Any combination of visuals that are used often can be saved as a view, which allows users to view objects in Matrix browsers using different combinations of active visuals.

For example, an Engineering Manager has many duties including:

• Tracking the work of the engineers in the group. For this job, the review of the work must be done both technically and with respect to project schedules. To do so, the manager may work with Assembly, Component and Specification objects, as well as assorted Manuals and the relationships that interconnect them.

• Project Manager. Assignments involved here might include defining and monitoring those parts of project schedules for which the group is responsible. In this role, the Engineering Manager may work with Project, Function, and Task objects and relationships.

• The processing of ECO’s (Engineering Change Orders). These may be connected to Product, Assembly, or Component objects.

Other objects that managers work with include purchase requisitions, equipment inventory and personnel management. For each role that a user has, a different view may be created that provides access only to the parts of the database required for that job function, keeping the focus on the task at hand.

17

Relationships

Matrix shows you how objects are organized and related.

A relationship is a type of connection made between associated business objects. These connections enable you to see how one business object relates to other objects. By exploring relationships, you can navigate through Matrix without knowing in advance where an object is located or how objects are connected. A Matrix database typically will have many different types of relationships, each specifying the types of objects it can connect. The definitions determine the meanings of each end of the relationship as well as any attributes it may have.

Matrix Navigator Browser in Star mode, with Icon option selected.

In this example, five different objects are related to the How To book, Basics of Cooking. As many as five different relationship types or as few as one could have been defined to create the connections. Connections are easily established using the Matrix graphical interface.


Navigation

It’s easy to navigate through Matrix and retrieve information.

In addition to performing database searches for business objects, you can find an object by navigating the relationships between objects. Navigation is the ability to traverse business object relationships. Through navigation, Matrix makes identification and retrieval of information quick and easy. Once you discover an object through navigation, you can in turn view its connections, history, attributes, forms, etc.

The Navigator browser has three modes: Star, Indented, and Details.

Individual business objects reside in vaults, which can be physically located on any server on the network. A person can navigate from an object in one vault to an object in another vault without knowing where the objects are physically located.

Matrix Navigator browser in Indented mode, showing a connected object’s form.

19

Like the Details mode of the Matrix browser, the Navigator in Details mode displays a user-defined table of information about the objects. These tables can include data about the relationships between the objects.

Matrix Navigator browser in Details mode, with Icon option selected and several cues applied.


Files and Formats

Business objects may have associated files.

A Matrix business object may be used to store application files that have been generated by virtually any software application. For example, a CAD file may be placed in a Drawing object in Matrix. The appropriate software application is launched to edit or view the file because Matrix is aware of the file’s format.

A file format specifies the type of file (such as ASCII, HTML, etc.) that may be associated with an object. Types of file formats available for a specific business object are defined by the object’s policy. Also defined is the default format for the object. Each Matrix file format specifies how the file(s) in the object will be edited, viewed, and printed.

Formats define:

• the application software and version (“FrameMaker 5.5”);

• default extension for the filename (.fm);

• the programs to launch when the edit, view, or print requests are received by Matrix.

A single object may have files in various formats. This Manual object may contain files of several different formats:

If desired, a format can have no specific program assigned. In this case, the operating system’s file association mechanism will be used to open files.

21

File Check-In and Check-Out

You manage the files controlled by an object.

With Matrix, you manage the files that are under the control of a business object. Matrix depends on you to place the appropriate files in each object. You do so by checking a file into Matrix.

The Matrix check-in feature allows files of various formats to be managed by the business object—and, therefore, by Matrix—as governed by the policy. When a file is checked into the Matrix database, the file’s format definition informs Matrix of the application software and commands required to process the file.

When you retrieve a file from an object and place it on your workstation, you check it out of Matrix. A file is always copied to the destination workstation during check-out: A master copy of the file is under Matrix control at all times. This ensures that the file is not deleted from the database and remains under the control of Matrix at all times, until you explicitly delete it.

For example, as the Desktop Publisher, you might check out the PrintPerfect file in order to edit the text of a particular recipe. Matrix copies the file from the database to a location on your workstation that you specify.

You can lock a file when you check it out so that no one else can update the copy saved in Matrix while you are working on it.

When you complete your work on the checked-out file, you must check the file back into the database in order to update Matrix with the new version of the file.

The Cooking book object may have several different files of varying formats checked in.

You can check out a copy of the text file for a recipe.


Object Lifecycle

Each business object has a lifecycle.

A lifecycle is a series of states through which a business object passes during its existence. When a new business object is created, its policy defines a lifecycle—the states through which it will pass from inception to completion. The policy governs all activities during each lifecycle state.

In this example, the policy controls when a new cookbook can be promoted from recipe development in the Chef’s kitchen to book draft preparation by the Desktop Publisher. The policy defines the conditions that must be met for the promotion.

Once the draft is promoted to the Editor, she must provide final signature approval before the book is ready for production. If the Editor does not approve of the draft, she can demote it to the Desktop Publisher with changes.

23

Policies

A business object is controlled by its policy.

A policy is a set of rules that governs the behavior of a business object—its lifecycle, access privileges, revisioning schemes, the file formats associated with the object, and where/how checked-in files are stored in the database. The Matrix Business Administrator creates the policies that will govern Matrix types.

Each type of business object can have a different policy. For example, a How To book object might have a set of rules entirely different from an object that defines Book Editing.

Within the policy, various types of access are defined for the roles people have in an organization. People can have different roles (and therefore different access privileges) depending on who they are and their assignments. A policy may govern more than one type of object, and there may be more than one possible policy for any one object type. But specific business objects follow the lifecycle and access rules of just one policy at any one time.

The Book Editing policy might specify that an Editor has access to all books (How To, Travel, Novel, Sci-Fi, Cooking, etc.)

A Chef might have access only to Cooking books.


Policies and Lifecycle

Privileges may vary during an object’s lifecycle.

A policy governs the various states through which the object will pass during its lifecycle, the people who have access at each state, and the conditions required for changing from one state to another.

For example, in the editing state of a book, the policy might define what access each role has to files associated with the book:

Policy Book Editing

However, the Desktop Publisher has view and edit access to the object’s files.

Under the Book Editing policy, the Editor has view access to the files for an object.

25

States and Signatures

Approval allows promotion of an object to the next state.

Within Matrix, the lifecycle that has been defined by an object’s policy is displayed in the State browser. Five states of the object are shown in the example below, and the scroll bar enables you to see the entire lifecycle. This part of the Manual’s lifecycle controls when the object is assigned, researched, and reviewed. The current state of the Manual is Researching. as indicated by the vertical arrow below its name.

Signatures provide a means to authorize the promotion of an object, and to which state (branch) it will move. For example, depending on which transition arrow is selected (the one before First Review is selected above), the writer signs off on either the First Draft Complete signature, or the Final Draft Complete Signature. Based on this selection, the object will move from Researching to either the First Review or the Final Review state.


States and Ownership

Ownership of a business object may change in each state.

At each state in a lifecycle, the object’s policy defines the actions that can take place. The policy also specifies the person or groups of people who can perform each action.

One action that might take place is to review an object and then annotate it with a comment, as illustrated in the example below.

Ownership and access privileges of the object may change in each state, as specified by the policy.

Matrix retains the history of actions that take place on the business object. You can access and review this history at any time.

Chef accesses a copy of an object: a Cookbook.

Chef tests recipes and connects comments (an attachment) to the object.

Desktop Publisher checks the associated text files into the database and edits the files, as necessary.

Desktop Publisher reviews comments.

27

States and Revisions

Revisions are usually associated with a change in state.

A revision of a business object is a special kind of copy of an object. An edition of a book is a revision. The revised object may have all of the same attribute values and the same policy—or these may vary.

When an object is revised, its type and name remain the same, however, the revision label changes to identify the new object. The policy specifies the scheme for labeling revisions with letters and/or numbers. For example, revision labels might appear such as: AA, AB, AC or 110, 111, 112 or 1st Print, 2nd Print, 3rd Print.

Editor has authority to approve (or reject) changes. Once approved, revision is sent to Production.

Desktop Publisher has permission to create a revision of the Cookbook.


Annotations and Attachments

Connecting information to an object is a powerful tool.

You can make an attachment to an object using virtually any software application. For example, depending on the applications available on your system, you might attach a photograph or a CAD drawing. Attachments enable you to associate pertinent information with the object.

You also can create an annotation (such as a text mark-up) using a software application (such as a word processing package). Then, within Matrix, you can connect the annotation as an object to the business object that it affects. Annotations enable you to make commentary on an object.

29

IconMail

IconMail makes it easy to access information.

You can send information to other Matrix users involved in work during a business object’s lifecycle. You also can receive information from other Matrix users. IconMail™ (an internal mail system included with Matrix) can be distributed (sent and received) automatically based on an object’s lifecycle states.Iconmail may also be distributed to a user’s external email address in addition to their Icon mailbox.

IconMail is actually an object with an attached message. This provides access to all of the information for that object. IconMail makes it easy to access all related objects and associated files. After selecting a mailed object, you (as the IconMail recipient) can manipulate and navigate the object directly from within the IconMail message. This means you can quickly access the files associated with the object in IconMail (if the policy permits).


Chef sends Desktop Publisher a message saying he completed his testing.

Each person in the Book Publishing group then can open the object to review the completed book.

Editor promotes the object to Production - the policy specifies that a message is sent automatically to

everyone in the Book Publishing Group.

Desktop Publisher reads the message and navigates the database to look at the Chef’s mark-ups directly from IconMail.

31

Automating Processes

Programatic process implementation is much less error prone.

Matrix provides internal access to the programs written to drive your processes. Program objects, which contain executable code, may be created or imported. Programs may be explicitly executed as a method against an object, to perform any database transaction or even an external process, such as updating a report. They may be collected in a toolset, which can then be displayed in the Matrix browser as a toolbar, allowing push button execution access to them. But the power of program objects becomes more apparent when they are used as the building blocks for event triggers, business wizards, and workflow processes.

Event triggers are programs which are executed based on the occurrence of specific database events (like the modification of an attribute value, or the connection of an object). An event trigger may consist of any combination of three different types of programs: a check program, which tests that the state of the database is what the other programs expect, and can even block the event from occurring; an override program, which can perform additional checking or actually replace the event that triggered it; and an action program, which executes after the event occurs.

Business wizards may be written that automate routine processes with a user-friendly interface similar to a windows installation routine. Wizards consist of several program objects that display any number of frames to provide easy, step-by-step instructions for the user. Wizards are created by administrators to simplify procedures and ensure data accuracy.


A wizard (as well as other programs) may be launched as a method, from the toolset toolbar, or directly from a desktop icon, without displaying the rest of the Matrix interface at all.

Workflow processes can be defined that map out the activities involved in completing a business function. These process definitions may be comprised of automated activities, which can be run without user intervention, and interactive activities which are sent via IconMail, (or “TaskMail”) to the users responsible for completing them. These “nodes” of the process can be linked together with “and” connectors that allow multiple activities to be performed simultaneously, or “or” connectors that provide flexibility and branching within the process. When one task (or set of tasks) is completed, the process automatically initiates the next task by sending a TaskMail, or by running the autoactivity program that is next in the process definition.

33

Vaults and Stores

Matrix objects are stored securely in vaults, and their associated files are kept in stores.

A vault is a storage location residing in the underlying database that is defined by a Matrix System Administrator for use by Matrix. Vaults allow the designer of the Matrix database to construct one or more logical storage locations within the database. These business object storage locations can be defined to classify the intended contents. For instance, one such grouping or vault might be “Books,” another might be “Videos, Audios, and Periodicals” and yet another “Cooking: Videos, Books, Periodicals.”

A vault may represent a department not only by containing departmental data but also by being physically located on the database server that is closer to its user base, minimizing network traffic. Or, vaults may be given more arbitrary names, describing its users, as in “A thru L” which might be used by everyone who’s name begins with the letters A through L. In this way Business Administrator’s can easily assign the proper vault to new users.

35

Stores are also defined by a Matrix System Administrator and are designed to hold the application files which are associated with business objects. Matrix offers three different types of stores, each providing a different degree of control over the file. Ingested stores become an actual part of the database tables; Captured stores are directories on a file system whose contents are named and managed by Matrix; Tracked stores provide the ability to keep track of files, without moving them from their original file system location.


Distribution of Data

Data may be distributed and replicated between locations.

Matrix may be used throughout an enterprise, and as such has the ability of being disbursed across a LAN or WAN. When many sites are to use the same database, Vaults may be distributed to multiple locations in several ways. Master Vaults may be linked, copied, or even shared with an entirely different database. Remote vaults allow business partners to share access to common data when both are using Matrix, but with entirely different schemas.

Ingested stores may also be distributed via a copy or a link. Additionally, Captured stores may be replicated, with the system administrator either manually or programmatically updating all locations periodically.

Databases may be shared globally in the users’ own dialect. Language aliases allow definitions to be localized with any number of translations — each site or user may select the defined language with which they feel most comfortable.

37

Incorporation of Legacy Data

Legacy data sources may be integrated through Adaplets™.

Another type of vault may be established to contain data from an alternate data source that is mapped to Matrix schema. This foreign vault type requires an Adaplet™, which is comprised of a shared library and a schema map. The Matrix Adaplet Development Toolkit contains a standard Adaplet that may be used for Oracle and other relational databases by customizing the schema map that is included. Additionally, the toolkit provides an API that allows C or C++ programmer’s to write shared libraries for use with other applications.

When an adaplet is in place, legacy data is available through Matrix for readonly (published), readwrite (updates made to the other data source only), migrate (updates made in Matrix only) or extend (updates made to both Matrix and the other datasource) access, depending on the mode set in the adaplet. Adaplets provide a way to publish data from all systems throughout the enterprise based on access rules established within Matrix.


Business to Business Collaboration

B2B exchanges use XML to leverage Matrix business rules.

In business-to-business (B2B) transactions, servers from two distinct companies (or departments) communicate directly with each other, without human intervention. Exchanges may use XML to convey the information in sufficient detail for the servers to process it according to each company’s business rules. One server receives a purchase order from the other company’s inventory control system, for example, and sends back confirmation that the order was received.

The Matrix XML exchange service extends this functionality by entering the applicable data into Matrix automatically. Users can then leverage the access rules, notification, workflow, and lifecycle capabilities of Matrix as these requests are processed. For example, the exchange can create a Sales Order object in Matrix, where it is routed to the Fulfillment department. A Sales Order workflow may be started either manually or automatically that assigns the necessary tasks for order fulfillment. Either the object’s lifecycle or the workflow could handle notification back to the customer about availability and shipping dates.

In fact, the whole process could have been started by Matrix on the customer’s side, if Matrix was used to manage the lifecycle and approval of the P.O. Then, using Matrix’s redirector tool within a program, the XML request could be created and sent to the vendor’s server, at the appropriate time in the lifecycle or workflow.

39

ENOVIA MatrixOne Applications

ENOVIA MatrixOne applications deliver task-specific software that maximizes your investment in the Matrix business collaboration solution. Each application supports either an explicit business process, such as, managing product options, information for suppliers, and software builds, or provides organizational functionality, such as routing tasks, managing programs, or finding documents. The applications provide a Web-enabled graphical user interface and a customizable template, both ideally suited to the particular process the software facilitates.

ENOVIA MatrixOne applications provide a solid, fully-functional, flexible foundation that you can tailor as needed to accelerate development of your unique Matrix system. Start with the application that meets your present need and then expand to others as your business requirements evolve. The combination of applications allows you to build an increasingly robust and effective PLM solution, without retrofit or reconfiguration.

Most importantly, Matrix integration technology makes the differences among diverse applications and data sources transparent, so enterprise systems and databases can become central players in the Internet-based product lifecycle.


Dynamic UI Components

Creating and updating the content of Web pages is simplified.

The contents of an application, such as any of the ENOVIA MatrixOne applications, can be easily and consistently tailored to user requirements via administration objects. The standard UI for ENOVIA MatrixOne applications has been created using the classic Matrix dynamic modeling approach. For example, Command and Menu objects have been defined in the Application Exchange Framework. These are then referenced in the applications’ JSPs. Implementors can add additional menus or commands, or modify the existing ones using Business or MQL. These changes are instantly available to the applications that use them.

Inquiry objects and system-wide tables are also available to implementors. Inquiries are designed to create a list of business objects that can then be used to load objects into these system tables. Columns in the table, as well as commands in menus, are role-based; that is they can be defined so as to only be shown to a particular set of users.

41

Glossary

A B C D E F G H I J K L M N O P

Q R S T U V W X Y Z

A

access rule 1. an administrative object that defines user privileges based on owner, public, and user definitions. Access rules may be applied to relationships, forms, programs, and business objects. 2. each user is granted a level of access for all objects in their Person definition. This access is sometimes referred to as an access mask.

action 1. a program that is part of an event trigger. The Action program executes after the event occurs or is overridden. See also event triggers. 2. specifies a Program that executes upon promotion of an object.

activity workflow processes can contain interactive and auto activities. Interactive activities are mailed to the users responsible for completing them (“taskmail”). Autoactivities are tasks that may be performed without user intervention, and are defined by Program objects. See also interactive activity and autoactivity.

adaplet an integration to a legacy system comprised of a shared library (interface) and a schema map file. Adaplets model data from other data sources to look like Matrix objects, allowing Matrix functions to be performed on them.

43

administrative object an object created in the Business Modeler or System Manager applications that describes and controls the business objects created in the Matrix Navigator application. Also called administrative definitions, they include Attributes, Types, Policies, Relationships, Formats, Forms, Reports, Rules, Programs, Wizards, Persons, Groups, Roles, Associations, Locations, Vaults, Sites, and Stores.

annotation an object such as a drawing mark-up that is connected to another object.

association a defined set of users based on a combination of the roles they play in the groups in which they belong.

attachment a note or comment object that gives additional information about a connected object.

attribute any characteristic that is assigned to an object Type or Relationship.

autoactivity a node of a workflow process that does not require user interaction. Instead, a Program object is associated with it that is executed when all tasks before it in the workflow process have been completed.

B

branch a parameter of a signature which defines what the next state will be after the signature is applied and the object is promoted. For each state, it is possible to have more than one branch. Which branch is taken depends on which signature is satisfied.

business object an item within Matrix that is used to contain, control, and manipulate information. A business object is designed to store application files that can be generated by any software application.

business wizard a program used to simplify and automate user tasks that contains code and frames, which prompt for information from the user and executes the code using the information received.

C

check 1. a program that is part of an event trigger. The Check program executes first, before the event occurs. See also event triggers. 2. a requirement on the lifecycle of a business object. Checks specify Programs that execute upon promotion. The promotion will fail if the return value is false.

checkin the process of placing a file into a business object from a workstation, to be controlled by Matrix.

checkout the process of retrieving a copy of a file contained in a business object to a workstation.

chooser a window that presents a list of objects from which you can make a selection.

clone a copy of an existing object. Also refers to the act of copying an existing object.

command an administrative object that can be used by JSP applications to comprise a Menu. Commands may be role-based; that is defined to be shown only to a particular set of users.

context your identification to Matrix based upon your user name and vault. A password may optionally be required.

cue see visual cue.


D

details mode both the Navigator and the primary Matrix browsers may be set to details mode, which displays the user’s active table.

E

ellipsis button a button whose label is an ellipsis (…), which, when clicked, opens a chooser. See also chooser.

event triggers items that allow the execution of Program object(s) to be associated with the occurrence of an event. May contain check, override, and action programs.

F

file any computer application file which is checked into a business object to be controlled by Matrix.

filter a workspace object that is created in the visuals manager. Filters provide a way to refine the data displayed in the working area.

filter bar An optional toolbar to quickly access currently active filters in Matrix browser windows.

find to search for a group of objects meeting certain criteria and display them in the working area.

format the definition of a file type and how it is accessed, viewed, and printed.

frame one of a series of windows within a wizard that contains instructions and/or asks for information from the user.

G

group a set of persons that collectively may share ownership of and access to business objects. Groups are created by the Business Administrator. See also person.

H

history information about each activity that took place for an object from the time of its creation to its current state. Can be viewed and extracted.

I

icon a GIF image that can be associated with a Matrix administrative object.

iconmail a message attached to an object which can be automatically or manually sent from within Matrix. It can be received by Matrix or via alternate email systems (or both).

icon mode both the Navigator and the primary Matrix browsers may be set to icon mode, which displays objects in an alphabetic list.

Imageicon a small raster picture of the actual business object. ImageIcons may also be associated with administrative objects.

45

Indented Browser mode

a mode of the Navigator browser that displays an object’s connections in an indented configuration.

Inquiry an administrative object that can be used by JSP applications to provide a list of objects that can then be loaded into a system table in a Web page.

interactive activity a node of a workflow process that requires user interaction. TaskMail, which has the activity object attached, is sent to the user who is responsible for completing the task. The task may contain instructions, attached business object(s), attribute(s), Tools, and a due date.

L

language alias a property assigned to an administrative object which defines its name in another language.

lifecycle a series of states through which a business object passes during its existence.

location an administrative object which defines an alternate file location for a captured store. Used to replicate a store on multiple servers. Locations are created by System Administrators.

M

menu an administrative definition for use in JSP applications that contains command objects and may also contain other menu objects.

menu bar a window component consisting of pull-down menus containing commands you can select to initiate Matrix functions.

message bar a window component that displays software and system status messages as Matrix executes selected functions.

MQL (Matrix Query Language)

a scripting language used to interact with Matrix from a command line, rather than through the application interfaces.

N

navigate the action of exploring the database by selecting an object and requesting a view of the objects connected to it.

navigator the browser within Matrix that displays the relationships between objects. The navigator has 3 modes: Star, Indented, and Details.

O

object tip a workspace object created with the visuals manager to display any selectable item about an object when the mouse is briefly held over it.

owner each business object is owned by a single person, group or role. An owner of an object has specific object access privileges.

override a program that may be part of an event trigger. The override program may perform required operations before an event occurs. As its name implies, it may also replace the event. See also event triggers.


P

password a mechanism used with a User name to authenticate access to Matrix. Only the user with a valid user name and password can have access to the information.

person an individual who can own and access business objects. Persons are created by the Business Administrator. See also group, role.

policy a set of rules that govern business objects, such as who has access to an object, what levels of access are available, and when access is permitted. Policies define the lifecycle of objects and the conditions required to move through the stages of its life.

primary browser the default window for viewing Matrix objects.

process an administrative object, created with the Business Modeler or MQL applications, that defines the activities, connections, event triggers, etc. of a workflow process. Instantiated in Matrix as a workflow object.

Q

query a request for information or data from the database based on certain criteria. A query can be named and saved.

R

relationship a type of connection made between associated business objects. Relationship rules are defined by the Business Administrator and the actual connections are made in the Matrix Navigator application.

revision another copy of an object to which changes can be made. A revision chain can be viewed in the revision browser.

role a person’s job type, used to categorize people to simplify the definition of access rules in policies. See also group, person, association.

S

set a saved collection of specific business objects, which can be loaded at any time into a Matrix browser by the user who created it.

signature a requirement on a state in a lifecycle. Signatures may be approved, rejected, or ignored. The business object cannot move to the next state if rejected.

site an administrative object that is a set of locations, which may be associated with a group or person, to define the servers that are physically located the closest to them. Sites are created by System Administrators.

star browser mode a Navigator browser mode that displays a selected object in the center of the window, surrounded by its connected objects.

state a specific step in an object’s lifecycle. Each state defines who has access to the object, as well as the requirements that satisfy the state and allow promotion.

store an administrative object that defines a file system location to hold objects’ files.

47

T

table a user defined visual that displays business objects in the first column with any related information displayed in the rest of the columns when the primary or navigator browsers are in details mode. A system table may also be defined for use in JSP applications, such as any ENOVIA MatrixOne application. Its columns may be defined such that they are only shown to particular users.

taskmail a message received in a user’s iconmail inbox which has an attached activity object that is part of a workflow.

tool bar a window component consisting of icon buttons that you can select instead of selecting the corresponding command from a menu.

toolset a group of programs or wizards. When toolsets are active, each tool they contain is displayed as a button on the toolset toolbar, located just below the Matrix toolbar.

tool tip a pop up description that appears when your mouse stops on an Matrix icon or administrative object.

type an administrative object that defines a kind of business object and the collection of attributes it can have. Types are created by the Business Administrator.

U

user a person, group, role, or association that is defined by the Business Administrator.

V

vault a storage location in a server for a group of business objects.

view a saved collection of visual workspace objects, grouped together in such a way so as to enhance productivity by focusing users on only the objects and relationships they need to complete the task at hand.

visual cue an object that controls of the appearance of business objects and relationships in Matrix browsers so that objects and relationships stand out visually for the user. Consists of a query, which specifies the criteria, and the visuals (font, color, line type) to use to display the matching objects.

visuals manager used to create visual workspace objects: cues, filters, object tips, tables and toolsets. Also used to activate and deactivate saved visuals.

W

widget a component of a frame within a Business Wizard.

wizard see business wizard.

work area the area of a window in which objects are displayed.

workflow a specific instance of a workflow process. For example, the “Design” process may be used to create Design Model 4567 widget workflow object.

workspace a system area containing a single person’s iconmail, sets, and saved Queries, and Visuals.


enovia basic

Documents