Glossary

A

advanced search

A search method that enables you to create simple or complex search expressions based on object properties using AND/OR logic.

alert setting

A setting that specifies whether an email will be sent when an object is modified in an EKM repository.

audit log

A daily log file automatically written by EKM that captures EKM server usage details.

audit trail

A feature available in the process view that can be used to track the decisions and actions that are made during a process for tasks that have been completed. This information is helpful fulfilling audit requirements for regulatory compliance.

auto node

A type of node in a process template definition that can be used to model an automated task such as generating a report, archiving data, or performing a validation. It is executed automatically by a process when it is encountered.

automatic deletion setting

A setting that specifies the policy for automatically deleting an object from a repository.

B

batch job

A sequence of commands to be executed by the operating system without user intervention.

batch node

A type of node in a process template definition that can be used to model long-running automated tasks in a process such as executing an external application for preprocessing, running a batch simulation, and postprocessing a simulation result.

built-in type

An object type that is provided by EKM off-the-shelf.

C

cache service

An internal service to make file sharing across a Wide Area Network (WAN) more efficient.

CAE Model File

The base object type of all simulation files that contains computer aided engineering model information.

catalog

A custom container that is defined and stored in a shared EKM repository, and is designed to hold large numbers of similar objects.

comparison report

A report file that contains a comparison of two or more objects.

connection

A mechanism that must be created and opened in order to communicate with an EKM server.

custom application

A user-defined interface or application that can be used to run automated tasks and produce outputs in EKM.

custom dialog node

An element in a process template that consists of a user-defined dialog box.

D

data extraction

The process of extracting simulation details from files for reporting purposes. Data is extracted automatically from files when they are uploaded to EKM or synchronized.

data model

The set of type specifications that have been registered on an EKM server.

E

EKM

Engineering Knowledge Manager. The server application in the EKM family of software.

EKM Administrative Interface

A special interface for managing workspaces that the superuser can sign in to from a web browser. It can be used to add a new empty workspace or an exported workspace, migrate a workspace that is in configuration mode, and download a log file detailing the last executed migration.

EKM server

A single system or multiple-configured systems that host the components of the Engineering Knowledge Manager product. An EKM server can be partitioned into any number of workspaces to which different users can be assigned. Users interact with an EKM server by connecting to it using the web client or ANSYS Workbench client, and sign in to a workspace on the server.

EKM Studio

An application that enables you to interactively define and edit EKM process template and lifecycle XML files using a graphical user interface.

EKM web client

The web-based interface that opens when you connect to an EKM server using a web browser.

EKM process

A set of tasks (sequential, parallel, or iterative) defined in terms of nodes, transitions, and variables, that users, groups and machines can perform in a coordinated way.

extraction monitor

An object that enables you to monitor the progress of data extraction when files are uploaded to EKM.

F

File Transfer Client

A Java webstart application that enables you to efficiently upload files to EKM.

I

iteration node

A type of node used to model an iterative process in a process template definition, such as review and approval. The iteration condition is held until it is no longer satisfied.

J

job

A process that runs when an external application is launched from EKM.

job template

A set of saved, predefined settings that determine how a job is to be executed.

journal

A special type of script file that can be created using scripting actions in EKM through the recording of user interface actions. Also referred to as a “journal script” or a “journal file”.

L

lifecycle

A set of predefined stages and transitions that an object under lifecycle control moves through during its lifetime. For example, a set of simulation results contained in a folder can have a lifecycle defined for it that includes a "Reviewed" stage followed by an "Approved" stage that requires a signoff.

lifecycle file

An XML file of type Lifecycle that specifies the stages, transitions, object type associations, and other parameters that define the lifecycle. It has the .lc.xml file extension (or .lcfxml for previous EKM versions).

localized label

Labels that will be translated into a different language or “locale” in the EKM user interface, when this option is selected.

M

macro

A method defined in a supported language that can execute a sequence of tasks or call other macros. The arguments that a macro can be passed, and the values that it can return, will depend on the context in which it is used. Macros can be specified in separate script files or defined within process templates, lifecycles, custom types, and custom applications.

metadata

A term that is used to describe properties of files.

metadata extraction

Special properties that are automatically extracted from any file after it is uploaded to an EKM repository or synchronized. Extracted metadata are key data about a file that help to define it.

monitor node

A type of node in an EKM process template definition that can be used to monitor the progress of a process or an asynchronous batch task that is spawned by an auto-node. A monitor node will wait until all monitored processes are completed before it transitions to the next node.

My Applications

A private folder under Home where you can save custom applications.

My Queries

A private folder under Home where you can save search expressions that you have defined.

N

node

The simplest type of node in an EKM process template graph that can be used to model a task performed manually by a user.

non-localized label

Labels that will be not be translated into a different language or “locale” in the EKM user interface, when this option is selected. They are listed in parenthesis next to localized labels in the built-in types reference guide in the Appendix.

O

object type

The data type that is automatically assigned to an object when it is created, uploaded, added, or referenced in an EKM repository.

P

pedigree

A term that is associated with analysis project folders in EKM. Refers to information about the location of inputs and outputs that EKM uses to create dependencies when an analysis is executed.

process

A set of tasks (sequential, parallel, or iterative) that users, groups and machines execute in a coordinated way.

process monitor

An interactive interface on the Processes page that can be used to manage tasks in a process, get details about a process, and monitor its status. It is designed to increase efficiency when managing single-user short-running processes by providing quick access to tasks in a user's queue. It is only accessible from the EKM web client.

process report

A report generated from a process that displays details about each completed task as well as a process graph, variable status table, and audit trail.

process template

An XML file that defines the set of activities to be performed in a process, the assignees of those activities, and their interdependencies. It has the .pt.xml file extension (or .wf.xml or .wfxml from previous EKM versions).

properties

Information about an object that is stored in a relational database that is associated with an EKM repository. Properties can be system-created, extracted, and user-defined and can be displayed, edited in some cases, added, searched on and used in other various ways. Also referred to as “metadata.”

R

Recycle Bin

The folder where deleted files are temporarily held before being permanently deleted from the system.

remote file server

An external location containing files that may be referenced by EKM. Files in this location are only referenced by EKM and are not transferred to EKM.

remote folder

A special object type that is created when you create a new connection to a remote folder on an external file server using the EKM web client. The folder is symbolically linked to an EKM repository while the physical folder resides on the file server referenced by EKM.

repository

The generic term used to describe the container for storing data for a workspace on an EKM server. Within a workspace, data is stored in the My Data and Shared Data folders.

Root User

The primary administrator of a workspace. The user designated as the Root User is the only user who can perform a restricted workspace configuration. The Root User does not have the same privileges as the superuser, who performs actions from the EKM Administrative Interface. One user is designated as the default Root User for all defined workspaces. If an LDAP mapping module is being used to control workspace access, a different Root User can be specified for each workspace.

RSM

Remote Solve Manager. A job queueing system developed by ANSYS for scheduling and managing simulations on remote devices.

S

saved query

A search expression that has been saved to memory for future reuse.

script

A file written in the Python or BeanShell scripting language that contains one or more macros. BeanShell scripts have the .bsh extension; Python scripts have the .py extension. Script files can be embedded in process templates, lifecycle and custom type files, and used in other powerful ways to extend the features of EKM.

search snippet

A few lines of text around the keyword that is extracted from a file when a keyword search is invoked. A snippet provides relevant information about the result without having to open the object. Snippets are extracted for text files such as .txt, .doc, .pdf, .ppt, .rtf, .xml, .xls, and .html, and any file whose MIME type is set as text/plain in EKM.

Shared Applications

A folder containing saved custom applications which all users can access.

Shared Queries

A folder containing saved search queries which all users can access.

shortcut

A direct link to an object designed to help you access the object quickly.

signoff process

A specialized type of process (sequential) that can be used in a lifecycle definition when signoff by an individual or committee is required before the object can be promoted to the next stage.

simulation details report

A report that is automatically created by EKM for supported types that contains a summary of model information and settings for the CAE simulation file.

SPDM

Software Process and Data Management

stage

An element in a lifecycle definition that is used to define the lifecycle.

staging area

A temporary location on the EKM server that is used to hold uploaded and ready-to-extract files until they can be imported or copied to the repository.

superuser

A type of user with superuser administrative privileges who can perform all actions that are associated with an EKM server, including those that are accessible from the EKM Administrative Interface. Only a superuser can access the EKM Administrative Interface.

T

task

A node in a process that is assigned to a user/group or batch task to complete. Tasks assigned to a user can be accessed from a user’s My Tasks page.

transition

In a process template definition, it is a link between a starting node (source) and an ending node (destination). In a lifecycle definition, it is a link between two stages.

U

update analysis project node

A type of node in an EKM process template definition that can be used to update the analysis contained within an Analysis Project folder. An analysis may need to be updated when the project contents have changed, or when external files that are referenced by the analysis have changed.

W

workspace

An EKM server can be partitioned into any number of workspaces. Each workspace has its own data repository and set of users. When you launch EKM, you are signed into your default workspace, and can access other defined workspaces if you have access permission for those workspaces.


Release 18.2 - © ANSYS, Inc. All rights reserved.