Glossary for ODM

A command which enables the user to perform specific operations on an ODM object and is assigned a particular role. For example, a Create Change Request action (CR_NEW) is associated with the Change Request object. Several actions can be associated with every object. Similarly, actions can be common to several objects.

Functionality to clear the application data is locked by the system due to a life cycle problem or network problems.

The status to indicate that the respective object is approved for implementation.

The directory recognized by the Document Management module to store the registered files.

An area located on a host to define the designated storage of files, such as work area.

The classification of areas, such as the work area and the vault area to register/work with and vault the files, respectively.

A (physical) file attached to a document revision.

The hard copy (information) attached to a document revision.

The attribute is the field in a session for which you must generate a mask.

The Browse option displays the object explorer for the selected object. This option displays the members, owner families and member families for the selected object.

A unique identifier for any specific changes. A change header is a change which consists of similar change requests that can be grouped and submitted to a single change header. This identifier is a database entity that represents the change.

The list of objects defined in ODM are used in Change Management. Some of the change affected objects that can be used in the lifecycle process of a change in ODM are Item, BOM, routing operations, and so on.

A list of codes with descriptions defined by the system administrator to classify the optional changes.

The committee of a chairperson and reviewers who implement a change using change management. Only authorized users can create a change committee.

A module in LN ODM that controls the processes of product changes in the life cycle. Change Management ensures that the product changes are implemented in a visible, controlled, and orderly fashion. The Change Management module provides the flexibility of creating a change process to optimize an organization’s Enterprise Resource Planning (ERP) system.

A generic mechanism to change a change controlled LN linked entity. A change order date is specified to set the linked entity to effective or expired on that specified date.

The date on which the change is implemented for the linked LN entity. The change order date is specified in the change order to make the linked LN entity effective or expire on the specified date.

A list of codes and descriptions that are defined according to organizational requirements to rate the priority level of the change.

The process to create, review, approve or reject and complete the change.

The description of the proposal for a change. All affected LN entities, reviewer lists, business partner links, tasks and task groups, change orders are included in this proposal. A default new change proposal is created automatically when a change is created.

The change proposal can have the following status:

Change request initiates the change process. Change requests are recorded from a variety of request sources, such as demands in the marketplace, product reviews, and customer response for making product innovations and upgrades. Information stored in each change request form enables you to track various changes as requested by various sources.

A change request can have the following status:

The status of the change through the life cycle. Change can have the following statuses:

A status of the files present in the vault area. Files in Check In status cannot be edited but can only be viewed.

A status of the files present in the work area. Files in Check Out status can be edited.

A change order that is linked to a parent change order and inherits the parent change order date automatically.

Common ODM Parameters are used to set the default values for the parameters in ODM.

The status indicates that the change has been implemented.

The initial status of the change request or change itself.

The work area assigned to a user by default, to register files. When no work area is defined for a user, work area is generated automatically by the system and the default work area is assigned. Only one work area can be assigned as the default work area for a user. The system administrator can assign default work areas for all users. Individual users can assign their own default work area.

Displays identification, document type, title, creator, role responsibility, and revision information. You can store the document information in electronic computer files (physical files) or on a non-electronic medium, such as paper (hard copies). Access to this information is always from the document, which is the unit of control for the user. If no file or hard copy is attached to a a document, the document is a purely logical entity, generally used for grouping documents.

The logical libraries created for documents to organize data in a hierarchical structure. Document libraries are used to catalog documents. The objects contained in document libraries can be: sub-libraries, documents, and vault areas.

The lifecycle of a document from concept stage to completion stage. The document lifecycle involves various phases, such as In Design, Submitted, Approved, Released, Withdrawn, Expired, and Rejected.

A module in ODM, that provides general document management facilities such as controlled access to the documents, secure storage of the document contents, document life cycle support, and management of the relationships between documents and other objects in the LN system. Document Management ensures the efficient and secure use of consistent and reliable document information.

The committee of a chairperson and reviewers who approve or reject a document using document management. Only authorized users can create a document management committee.

A generic system to generate a unique identification number for a document. In the Document Management module, masks can be defined for the document ID, the document revision value, the hard copy ID, and the file ID. The document ID mask and document revision mask depend on the document type.

Document revisions track changes to their attached files and hard copies. When a document is created, the document revision is created by default. Most of the work with documents is actually performed by means of the document revisions. Document revisions are assigned a status that indicates the revisions' position in the lifecycle. The operations that you can perform on a document revision depend on the revision's status.

A parent/child link between two document revisions. The child document is logically an element of the parent document.

Unidirectional or two way link between two document revisions. If the link is unidirectional, the document revision is linked in one direction, in other words, document revision 2 is linked to document revision 1, and if the document revision 1 is also linked to document revision 2, the link is called a two way link.

The document revision has the following status through the document lifecycle:

Assigned to every document. Each document type is assigned a revision mode that is applicable to all documents of that document type. The document mask and document revision mask can be dependent upon the document type. The document types determine whether the hard copies and files attached to document revisions must be assigned revisions. Examples of the type of documents a company keeps can be, safety regulations, assembly documents, wiring diagram, maintenance instructions, drawing documents and standard documents.

Attachment of a document or file to a document type in the form of templates.

The status to indicate the completion of task execution.

Enables users to obtain the local host name dynamically when users from the local host connect to the LN server.

An option that limits the revise process of document revision and exclusively to a single individual. Multiple document revisions of the document cannot be revised at the same time when this option is in use for the respective document.

Export: A process in data management module that selects data from System Table List of ODM and transfers the ODM system data to a storage directory. Import: A process in data management module that imports the data from the dump files in a specified directory, to the system tables of ODM.

All the object families that have a particular object as the owner.

An object related to an object family. The object family can have objects as members.

The object is a member in the specified object family.

The object that points to a physical file. All the files are assigned versions by LN, automatically. When a file is first attached to a document revision, it is assigned the first version. This version is retained until the file is checked out of the vault area. To edit a file in the vault area, the user must checkout the file into a work area. The checked out file is registered in the database as a new version of the file.

Upon registration, a file is assigned a file type. Each file type is associated with one or more file extensions. If a file type is specified for a particular document type, files of the specified file type only can be attached to a document of that document type. The system administrator can constrain the set of file types that can be attached to a document revision of a particular document type. For example, word processing files have three-letter extension that indicates the file's type, such as .txt or .doc. Similarly, graphic files have various extensions, such as .jpg, .bmp, and so on.

A data item container that stores the group of related objects. Every folder has a life cycle mechanism. Folders provide a flexible solution for defining the relationships, links and dependencies between different aspects of product data in the form of objects. Folder can be personal or shared.

A module that maintains folder and simplifies the management of product information. The Folder Management module provides a generic flexible solution to address the problem of links and dependencies. Linking a folder to an LN object creates a simple and efficient method to extend the object’s data domain, and to facilitate the fast retrieval of any type of information related to the object.

The status in the change lifecycle that indicates that the change entity has been rendered inactive or delayed for some reason.

An object that represents the physical nature, for example, hard copies of documents. The contents of hard copy documents are printed on paper. storage media, such as casette and film, are considered hard copies.

A host is the network node that is recognized in the network. All network nodes that can be accessed by the document file server or the vault server component can be defined as hosts.

The status assigned to a new document revision.

The status of a task while in progress. This status is assigned when an executed task is revised by using the redo action.

A logical place to save data in a hierarchy. Libraries enable you to define a collection of related objects and classification of documents. These objects can themselves be libraries. A library can have vault areas linked to it.

A predefined entity linked to LN objects in ODM. Objects are predefined in ODM and are allowed to link to document revision/change proposal/folders depending on their status.

The place where hard copies, for example, documents, are stored.

If multiple files are attached to a document revision, the system checks for the main file and runs the file operations (View/Print/Edit) accordingly.

The code defined for the attribute of the object. You can maintain unique mask codes for the attribute of an object.

The detailed configuration of masks to generate IDs in the format used by the organization. To configure masks, you must configure the mask code associated with the attribute.

The physical substance of the hard copy to store, for example, data, such as paper, mylar, disk, CD-ROM, aperture cards, and so on.

A procedure that defines the way, a remote work area can be accessed from the local host.

The concept of writing and editing multiple tables in a single session. MMT is intended to improve the ease of use of the LN applications by displaying the related sessions of the header as satellites in the MMT session itself.

A nonphysical entity that is defined in ODM to manage the life cycle of the product in a simple way. For example, an LN main table is considered an object. Objects are classified as ODM objects and LN objects. ODM objects are related to ODM, for example, libraries, documents, changes, folders, queries, and so on. The non- LN objects are item, BOM, sales order, purchase order, and so on.

The object explorer that enables the user to view the object's links in the form of a horizontal tree-like structure.

A family with one or more objects as family members, which are linked to the family owner.

The history of revisions made to an object.

Any LN entity that can be linked to a folder. For example, an engineering folder, sales proposal, or employee file.

A mechanism that generates a unique identification number to the attribute of the object represented by an unique mask code. The actual number generated depends upon the mask configuration defined by the user for the mask code. If no mask configuration is defined for an object mask, the default value of the object mask is taken into consideration to generate the number. Active object mask is used to generate the number for the attribute of an object.

A feature that displays statistical details, such as the number of hard copies and files linked to a document revision and the total size of the files linked to the revision.

The secondary status of an object that is dependent on status of another system defined object in a life cycle of document or change.

An independent package in LN that provides effective data management solutions in a product development scenario with truly embedded data management functionality. ODM ensures that the product data is handled properly and that the most stringent product lifecycle management processes are applied. ODM provides fully integrated document management, change management and folder management facilities for LN users. ODM is accessed directly from LN, which enables users to attach documents to LN objects, and view corresponding files attached to documents.

The family owner is the source object of a link that belongs to the family.

A generic mechanism to filter a set of records based on the provided conditions.

The condition provided by a user, based on the respective object attribute values, to set up a query. A query can be based on one or more conditions. For example, you can set up conditions to retrieve all documents of a particular type.

A list of codes and descriptions that provide a reason for the change. The codes and descriptions are defined by the system administrator.

An action that enables the user to redesign the rejected document revision. The document revision status changes from Rejected to In Design.

A document that describes the details of the change request that is stored in ODM for reference purpose.

A status that indicates that the object has been rejected and requires no further review.

Group of actions for a specific object.

The Relative Change Order (RCO) governs the date effectivity for the linked LN entity which will trigger depending on the duration with respect to the base change order date.

A status that indicates that a document has got a formal approval and is ready for distribution.

The parameters used to specify the criteria for data selection and to be displayed for an existing report.

A basic format to represent information in a structured way.

The person responsible for the review of the change proposal or document revision.

The individual assigned to a change or document management committee to review the change proposal or document revision accordingly and give appropriate recommendations.

The mechanism adopted by the reviewers of the change or document management committee. The mechanism enables controlled execution of the process by the reviewers of the committee.

Revise enables the user to create a new revision from the existing approved (Change/Folder) or released (Document Revision) state, for example, new revision in case of document revision and new proposal in case of change proposal.

Each document type is assigned a revision mode, which is applied to all documents of that document type. The revision mode specified can be alphanumeric revision, such as rev 01 or A1. The revision mode can also be set automatically to the release date of the revision, for example, 1998-05-12.

Role specifies the employee's position and the authorizations the employee must perform specific actions and processes or to access specific data.

Assignment of proper actions to a particular role according to the need, to perform the respective actions in ODM, for example, designer, engineer, programmer, and administrator.

Roles that are defined in ODM are assigned to the employee as part of the authorizations that are stipulated in an organization.

A principle or condition that can be used as a one-point provision to trigger dependent events/entities.

Statuses that an administrator assigns to ODM objects based on the system defined status. Also referred to as user-defined status.

The dimension of the hard copy, such as A2 and A4 paper size.

The main object to which a secondary object is linked, for example, the family owner.

A readable arrangement of reports in a standard way. The report layout includes the following fields: Company Number, Company Name, Date/Time, User, Page Number and Report Header description.

A status that indicates that a document or a change is submitted for approval or rejection.

The fundamental actions applicable to all the operations in ODM. All the actions that are related to ODM objects are systems actions, by default, which cannot be deleted or modified. Users cannot create system actions.

Table that lists all objects related to ODM configuration by sequence number, package, and module for exporting information.

The object that is linked to the source object.

The actual change to be implemented at a prescribed date. You can link tasks directly to a change proposal if the proposal is in Created status.

Although task groups are optional, Infor recommends strongly that you use task groups. The task group business function maintains the task group and the group's tasks. The objective of the tasks, the task's results, and how and when the task is implemented can be maintained in the task group. Task groups are optional. However, for an organization that has hundreds of tasks, task groups are essential in the successful implementation of a group of related tasks.

Denotes various positions in the execution of a task life cycle. The statuses are Created, In-Work, Done, and Skipped.

The status indicates that the created change is submitted for review.

The change status, which indicates that an inactive change entity (frozen change) is activated and is currently in the change implementation process.

The authorization level assigned to a user to determine the various actions that can be performed in ODM, for example, creation, deletion, edit, and viewing of a document

One of the classified areas where checked-in files are stored when a document is submitted for review or released in case of quick approval document. Users have read-only access to this area.

A software program that is installed on the client or server systems, depending on the requirement. Running the vault server program enables the transfer of the files between the areas that are designated in ODM during certain operations and also enables you to register and access the files in the case of mounted area.

The document revision status, which indicates that the document revision has been withdrawn after release. The revision is no longer in use after a document is withdrawn.

An uncontrolled area where all the files are created and stored before a user views and and edits them. This area contains one version of each file. Users can edit files which are assigned as work areas. One or more work areas may be assigned to the same user, and more than one user can be assigned to the same work area. Each user who works with files is assigned a default work area. When the user checks the files out of the vault, the files are copied to this work area. The default work area is also used in other circumstances, such as when the files are registered in ODM.