AspenBasicEngV7 3 Start

8/17/2019 AspenBasicEngV7 3 Start

1/57

Getting Started Guide

Aspen Basic Engineering


2/57

Version: V7.3

March 2011

Copyright © 1981 – 2011 Aspen Technology, Inc. All rights reserved.

Aspen Basic Engineering, Aspen Plus, Aspen HYSYS, and the aspen leaf logo are trademarks or registered

trademarks of Aspen Technology, Inc., Burlington, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This documentation contains AspenTech proprietary and confidential information and may not be disclosed, used,

or copied without the prior consent of AspenTech.

ASPENTECH MAKES NO WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WIT RESPECT TOTHIS DOCUMENTATION, ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULARPURPOSE.

Aspen Technology, Inc.200 Wheeler RoadBurlington, MA 01803-5501USAPhone: (781) 221-6400Toll free: (888) 996-7001

Website http://www.aspentech.com


3/57

Contents iii

Contents1 About This Guide ..................................................................................................1

About Aspen Basic Engineering ..........................................................................1Related Documentation.....................................................................................1Technical Support ............................................................................................3

Phone and E-mail ...................................................................................3

2 Aspen Basic Engineering Applications ..................................................................5

Datasheet Applications......................................................................................5Datasheet Editor ....................................................................................5

Datasheet Definer ..................................................................................6Datasheet Generator ..............................................................................7

Drawing Applications ........................................................................................7

Drawing Editor .......................................................................................7

Graphics Definer ....................................................................................8Configuration Applications .................................................................................9

Administration .......................................................................................9

Class Library Editor ................................................................................9

Interface Applications ..................................................................................... 13Bridge................................................................................................. 13Costing Interface..................................................................................13

Object Mapper ..................................................................................... 13

Simulator Interface .............................................................................. 13Rules Editor.........................................................................................14

Explorer ........................................................................................................ 14

Packages............................................................................................. 14Project Management and Smartplant ................................................................ 15

Project Management within Aspen Basic Engineering ................................ 15

Project Support within Smartplant .......................................................... 15

3 Aspen Basic Engineering Basics .........................................................................17

Starting Aspen Basic Engineering ..................................................................... 17

Opening Workspaces ...................................................................................... 18Aspen Basic Engineering Windows .................................................................... 19

Toolbars.............................................................................................. 19

Status Bar ........................................................................................... 19

4 Using Aspen Basic Engineering ..........................................................................21

Working with Database Objects ........................................................................ 21Creating Database Objects ....................................................................21

Deleting Database Objects .................................................................... 22

Copying Database Objects..................................................................... 22Cloning Database Objects...................................................................... 22


4/57

iv Contents

Working with Holds .............................................................................. 23

Current Object Filters ...........................................................................23

Working with Cases ........................................................................................24Creating Cases..................................................................................... 24Deleting Cases.....................................................................................24

Renaming Cases .................................................................................. 24

Copying Cases ..................................................................................... 25Working with Documents ................................................................................ 25

Accessing Documents ..................................................................................... 25Creating New Datasheets ...................................................................... 26

Creating New Diagrams ........................................................................ 27Opening Existing Documents ................................................................. 27

Viewing Document Status...................................................................... 28

Printing Documents .............................................................................. 28Renaming Documents...........................................................................28

Document Revision Control.............................................................................. 29Submitting a Document ........................................................................ 31

Checking a Document ...........................................................................32Issuing a Document.............................................................................. 33

Deleting a Document ............................................................................34Removing a Document from the Revision Process..................................... 34

5 Glossary .............................................................................................................35

Glossary of Terms .......................................................................................... 35Administration User .............................................................................. 35

AES .................................................................................................... 35Aggregation.........................................................................................35Annotation ..........................................................................................35

API datasheet ...................................................................................... 35

Application ..........................................................................................36Application Interface............................................................................. 36

As-Built............................................................................................... 36Association.......................................................................................... 36Attribute ............................................................................................. 36ATESA ................................................................................................ 36

Authoring Application............................................................................ 36

Base Class...........................................................................................36BEDD.................................................................................................. 36Boolean .............................................................................................. 37

Bridge................................................................................................. 37Case................................................................................................... 37Case Fixed ..........................................................................................37

Category ............................................................................................. 37

CCDM ................................................................................................. 37Claim.................................................................................................. 37Class .................................................................................................. 37

Class Library........................................................................................38

Class Store.......................................................................................... 38Class View........................................................................................... 38

Clone..................................................................................................38

Clone Fixed .........................................................................................38Composite (Class) View ........................................................................ 38


5/57

Contents v

Conceptual Data Model ......................................................................... 38

Configuration User ............................................................................... 38

Connection ..........................................................................................39Copy...................................................................................................39Data Model..........................................................................................39

Data Model Construct ........................................................................... 39

Datasheet ........................................................................................... 39Datasheet Builder................................................................................. 39

Datasheet Group .................................................................................. 39Default Fixed .......................................................................................39

Delete................................................................................................. 40Destroy............................................................................................... 40

Discipline ............................................................................................ 40

Display Name ...................................................................................... 40Document ........................................................................................... 40

Drawing .............................................................................................. 40End User ............................................................................................. 40

Engineering Framework ........................................................................ 41Enumeration Data Type ........................................................................ 41

Equipment List..................................................................................... 41EXPRESS............................................................................................. 41FEED .................................................................................................. 41Field ................................................................................................... 41

Field Lock............................................................................................ 41

Field Status .........................................................................................41Fitting................................................................................................. 42

Folder ................................................................................................. 42GAIP................................................................................................... 42

Generalization ..................................................................................... 42Global Case .........................................................................................42

Graphic Hold........................................................................................ 42

GUI .................................................................................................... 42Hold ................................................................................................... 42

Knowledge Base (KB) ...........................................................................42Link .................................................................................................... 43

Link set...............................................................................................43Lock ................................................................................................... 43

Mapping.............................................................................................. 43

Mass Balance Header............................................................................43Mass Balance Column ...........................................................................43

MMC ................................................................................................... 43Multiplicity...........................................................................................43

Object ................................................................................................ 44Overspill ............................................................................................. 44

Overspill Sheet .................................................................................... 44Page................................................................................................... 44

PIP Datasheet...................................................................................... 44

Piping System...................................................................................... 44Privilege.............................................................................................. 44

Project................................................................................................ 45Quantity Type...................................................................................... 45

Reference Point....................................................................................45Remove .............................................................................................. 45


6/57

vi Contents

Restricted Case.................................................................................... 45

PFD .................................................................................................... 45

Role (1) .............................................................................................. 45Role (2) .............................................................................................. 46Role Members...................................................................................... 46

Simulator Interface .............................................................................. 46

Smart Plant Foundation (SPF) ................................................................ 46Snapin ................................................................................................ 46

STEP .................................................................................................. 46STEP File............................................................................................. 46

Stream ............................................................................................... 46Subclass ............................................................................................. 46

Superclass...........................................................................................46

Summary Sheet ................................................................................... 47System Class .......................................................................................47

System Library .................................................................................... 47Table .................................................................................................. 47

Smartplant® .......................................................................................47Transaction Lock .................................................................................. 47

UO ..................................................................................................... 47UOM ................................................................................................... 47User Library ........................................................................................47User Lock ............................................................................................ 48

W3C ................................................................................................... 48

Workspace ..........................................................................................48Workspace Package.............................................................................. 48

Index .......................................................................................................................i


7/57

1 About This Guide 1

1 About This Guide

This guide provides an overview of the Aspen Basic Engineering applicationset and takes a first-time user through basic Aspen Basic Engineering

procedures.

After completing this guide, you will be able to open/close workspaces, work

with database objects, cases, documents (drawings and diagrams) and

understand document control and revision processes.

About Aspen Basic EngineeringAspen Basic Engineering is a client/server application that allows multiple

process designers to be connected to a single workspace or project.

Changes made by one client are immediately reflected in the informationshown to other clients.

To generate a process design, you create database objects that represent the

real world process. You can view and modify data for these objects usingdrawings, or datasheets (Before you can work with datasheets or diagrams,you must open a Workspace or Project).

Related DocumentationIn addition to this document, the following documents are provided to helpusers learn and use the Aspen Basic Engineering applications:

Title Content

What’s New This guide provides an overview of new features and functionality

within the Aspen Basic Engineering application set and describeshow to work with Aspen Basic Engineering Projects within AspenBasic Engineering and within Smartplant®


8/57

2 1 About This Guide

Title Content

AdministratorReferenceManual

This manual contains advanced details of Aspen BasicEngineering applications and functionality. Contents includedetails of the Aspen Basic Engineering processes applicable to auser with Administrative rights. The following sections/functionsare covered:

Generating datasheets, (and using the Datasheet Definer)including preparing datasheets in Microsoft Excel 2000/XP

Using the Graphics Definer (including defining symbols and

labels, with worked examples and extracting legacy symbolsand labels)

Using the Explorer application, including interaction withSmartplant®

Using the Administration application

Using the Class Library Editor application

Using the Rules Editor (and Knowledge Bases)

Using the Bridge application

On-line Help A comprehensive set of help systems are also provided withAspen Basic Engineering. Help within specific applications (for

example Bridge Help) is available from the Help menu of theopen application

A generic, self-contained Help system (detailing all Aspen BasicEngineering applications, their use and interaction) is available byclicking on the Help icon within the windows Start | Programs |AspenTech | Aspen Basic Engineering path


9/57

1 About This Guide 3

Technical Support

Online Technical Support Center AspenTech customers with a valid license and software maintenanceagreement can register to access the Online Technical Support Center at:

http://support.aspentech.com

You use the Online Technical Support Center to:

Access current product documentation.

Search for technical tips, solutions, and frequently asked questions (FAQs).

Search for and download application examples.

Search for and download service packs and product updates.Submit and track technical issues.

Search for and review known limitations.

Send suggestions.

Registered users can also subscribe to our Technical Support

e-Bulletins. These e-Bulletins proactively alert you to important technicalsupport information such as:

Technical advisories.

Product updates.

Service Pack announcements.

Product release announcements.

Phone and E-mailCustomer support is also available by phone, fax, and e-mail for customers

who have a current support contract for their product(s). Toll-free charges are

listed where available; otherwise local and international rates apply.

For the most up-to-date phone listings; please see the Online TechnicalSupport Center at:

http://support.aspentech.com

Support Centers Operating Hours

North America 8:00 – 20:00 Eastern time

South America 9:00 – 17:00 Local time

Europe 8:30 – 18:00 Central European time

Asia and Pacific Region 9:00 – 17:30 Local time

http://support.aspentech.com/http://support.aspentech.com/http://support.aspentech.com/http://support.aspentech.com/


10/57

4 1 About This Guide


11/57

2 Aspen Basic Engineering Applications 5

2 Aspen Basic EngineeringApplications

This section provides an overview of Aspen Basic Engineering applications andfunctionality within the applications listed below:

Administration

Bridge

Class Library Editor

Common Core Data Model – CCDM Costing Interface

Datasheet Editor

Datasheet Definer

Drawing Editor

Datasheet Generator

Explorer

Graphics Definer

Project Management

Object Mapper

Simulator Interface Smartplant®

Rules Editor

Datasheet Applications

Datasheet Editor

The Datasheet Editor is one of three key end user tools (the others are theDrawing Editor and Explorer. This application is used to create and edit

datasheets and move these documents through your work process.

The datasheet editor can also be used to perform a range of basic operationson objects contained within the Aspen Basic Engineering Workspace, such ascopy, delete and so on. It can also be used to launch rules on the data

contained within the workspace.

It is intended for all general users of the software. However, datasheettemplates must already exist for the documents you wish to work on. You can

use the delivered templates or use your own (see Datasheet Definer below).


12/57

6 2 Aspen Basic Engineering Applications

Recent improvements to the Datasheet Editor include:

Multiple-page Datasheet option – Multiple-page datasheets can be:

o Created

o Opened

o Added: From another template to the current document

o Reordered: Modify the order of the pages in a document

o Removed: Delete pages from the current document

Removed: Datasheet groups – multi-page datasheets provide replacementfunctionality. Other flexibility provided by datasheet groups will be retro-

fitted into subsequent releases.

Radio Buttons can be set, unset and cleared individually.

Check Boxes can be selected, unselected and cleared.

Support for other new data types such as Date, Booleans, and

Enumerations.

Support for background color.

Insert page.

Datasheet templates can be changed and reapplied to a workspace

without loss of document format information.

Overspill pages functionality has been returned (existed in 11.1).

Datasheet Definer

The Datasheet Definer is a tool used to develop templates for Datasheetsbased on Microsoft Excel 2000/XP (previous versions of Excel areincompatible). You must pre-install Microsoft Excel 2000/XP to use the

Datasheet Definer – refer to the Installation Guide).

Datasheet Definer features include:

Class View Browsing – Routes are defined using Class Views provided by

the new Data Model.

Generate function – It is now possible to generate the datasheet andobtain a template file using the new .xml file format.

New definition of fields – All existing fields are definable using the new cellbased definition metaphor. This has the following capabilities and side-

effects:

o No need for a design mode, no need for a separate executable and sono need to switch windows. The menu bar disappears and is replacedby a dockable Excel toolbar. There is no need to manually attach the

AddIn as it is now a COM AddIn.o Cells can be 'tagged' as being a field. So no controls float above the

spreadsheet that are moved and sized independently. Cells are the

Fields.

o A Single file is produced with the extension .ztf that replaces both .gdf and .tpl files. No .raw file is required.

o Remark fields have now been removed.


13/57


o Multi-page datasheets: Documents can now be defined as separate

worksheets, in the same workbook, in the Excel definer (a single

datasheet page on each spreadsheet sheet).

o Radio Buttons: Radio buttons can be defined and grouped together -

different shapes and check marks for buttons can also be defined.

o Check Boxes: Create user-defined check boxes and define different

shapes and check marks for buttons.

o “Other” fields: Create user-defined “Other” fields in radio buttongroup.

o Qualified Fields: You can now add qualified fields and groups.

o Generate Template File: User-generated (valid) template file fromdatasheet definition.

Excel drawing shapes can be used to produce sketches on the datasheet.

As the datasheet generator uses the excel file to produce its finaldocument, any drawing will be reproduced faithfully when exported.However, when viewing in the datasheet editor not all shapes will appearas only basic shapes are supported (check the datasheet definer help for

details). It means that drawings appearing in the datasheet editor mayhave missing details depending on the shapes and formatting you use.This is a practical limitation of the datasheet editor as it does not emulate

Excel in this respect.

Datasheet Generator

This tool (launched from Start | Programs | AspenTech | Aspen BasicEngineering | Excel Datasheet Generator) enables you to bring a

datasheet file created in the Datasheet Editor (exported as .xml format) into

Microsoft Excel. You must install Microsoft Excel 2000/XP to use theDatasheet Definer – refer to the Installation Guide supplied on the product .

Previous versions of Excel are incompatible.Once in Excel 2000/XP, the file (in .xls format) is independent of the AspenBasic Engineering database and can be used, for example, for furtherdistribution or review.

Datasheets generated by the Datasheet Generator and opened in Excel are

completely accurate and reproduce the original definition sheets exactly.

Changes to the data in the spreadsheet cannot be re-imported later. This toolis intended for report purposes only.

Drawing Applications

Drawing Editor

The Drawing Editor is a primary tool used for creating drawings as part of

your engineering project. It is configured out of the box with symbols andlabels used to produce PFD drawings.

You can create as many drawings as required in your workspace. You build up

drawings by dragging and dropping symbols and labels onto the drawing


14/57


canvas. Connections are created by using one of the available connection

symbols. Some symbols operate as fittings and can be simply dropped into

lines. Connection gapping and un-gapping are also supported along withnumerous features required to produce professional drawings.

Objects placed on a drawing create equipment objects on the database. Theseare also added to the stockpile of objects that you can view with the Drawing

Editor. The stockpile is the actual view of the content of the database. Youcan remove symbols/objects from the drawing without deleting them from the

stockpile/database, or you can permanently delete them from both thedrawing and stockpile/database, or indeed reinstate an object back onto a

drawing if it only exists in the stockpile.

Recent Drawing Editor features include the following:

Label Fields – Support all the data types of the new version system,

including:

o Real and integer fields with prefix/suffix and substitution text

o Boolean fields with drop down on/off/yes/no select list

o Date fields with date picker and dropdown calendar

o Enumerations with drop down list

o Format options specific to the data types

Piping Systems – An improved user interface makes editing piping

systems easier.

Mouse/selection improvements to assist usability when making

connections or when placing and moving symbols.

Project support by de-emphasizing symbols not in the project scope and

disallowing connectivity edits to symbols that are not within the project

scope.

Note: Parametric Symbols

The supplied parametric symbol "Parametric Column.sym" has had the widthparameter removed. This is to enable fittings to fit the column width. If youneed to change to the width, scale the symbol by using the corner handles

(rectangular). This way, any fittings attached will "Inherit" this scaling and

therefore fit correctly. Height of column can still be set parametrically usingthe single (diamond) handle at the apex of the column.

Graphics Definer

The Graphics Definer enables you to produce templates of Symbols andLabels for use with Aspen Basic Engineering.

You construct symbols and the graphical elements of labels by using the

available drawing tools to lay down lines, arcs, text, rectangles etc onto thedrawing canvas. The tool has all the usual drawing tool features such as snap

to grid, rotate, reflect, scale plus dynamic drag features (for stretching forexample).

The tool also uses Intergraph SmartMouse features that allow you to snap togeometry (for example interception points).


15/57


In recent versions, the Graphics Definer allows you to use the Class View

features of Aspen Basic Engineering. This means that you are presented with

a browser to find the class view attribute to be associated with a label.

Value fields of labels can now have a description as well a tag, so that label

designers can reduce clutter and overlap of fields. Furthermore, the symbolextraction functionality has been improved.

Configuration Applications

Administration

The Administration application is used to administer (view, edit and create,

Aspen Basic Engineering Workspaces - previously Workgroups), configureuser and user group privileges and set security options.

A Wizard is provided for setting up a new Workspace. This prompts you for

information relating to your chosen OLEDB database, Class Store to be used,and so on.

Other features include:

View Workspace Users (and applications) connected to a workspace and

change them.

View Roles and change them.

Add/remove Data Servers.

Import/Export Access Policy File:

o Import a policy file to add Users and Roles into a workspace instead of by working with the user interface – this helps reuse of informationbetween projects.

o Export a policy file to record Users and Roles configured for aworkspace for later reuse.

The application is a Microsoft Management Console Snap-in. The format of

the user interface is identical to that provided by many ‘ManagementTools’ installed on your PC. It means you can plug the snap-in into asingle console along with others such as the standard Windows users and

groups management snap-in and possibly the configuration snap-in for

your chosen RDB (such as Oracle or SQL Server). This gives you a singlecustomized window for all your administrative tasks.

Class Library Editor

The Class Library Editor application allows configuration users to create and

edit a Data Model to be used by Aspen Basic Engineering. The Data Modelsource is held in a collection of Class Libraries and the Editor is used to writethese and to compile them into a Class Store. A Class Store, nominated

during Workspace configuration (see the Administration Tool), is loaded into

the server to support a Workspace. This organization of a collection of ClassLibraries is used to give flexibility in combining data model fragments into


16/57


different Class Stores, and to allow you to more easily manage your data

model customizations.

A Class Library comprises a collection of class definitions and related datamodel definitions. Typically, the set of definitions contained in each class

library will be related by a common purpose, e.g. a class library maycontain constructs for rotating equipment, or constructs for heat transfer.

The Class Library Editor is designed as a purpose made tool for working with

the new 3-Tier Data Model Architecture. In Version 11.1 and many otherdatabase products you work directly with the core data model and allapplications of the data map explicitly to the model via ‘routes’ or ‘paths’ to

the required attributes. This is fine until the data model becomes difficult for

the ordinary user to navigate or comprehend. Imagine the scenario withapplications needing access to process data:

Here many applications want access to the CORRECT attribute in an

engineering sense. At the same time, when you work with the data model,

you have to ensure the route you use is the correct one for the purposesof SHARING data with all the other applications accessing the data.

The problem is made complex for ordinary users as the data model is

very, very rich in content and is highly structured either from ahierarchical perspective or by inheritance. If you were to customize the

Aspen Basic Engineering Data Model it would take significant effort toensure you did not inadvertently overwrite some key attribute which was

being input into some design calculation.

The 3-Tier data model solves this problem by making everything much

more transparent:


17/57


Class Views

The top tier contains Class Views. A Class View is a simple, engineer friendly,

mini-data model of an applications use of data. The principles excludeinheritance and they are usually flat or have only very shallow hierarchies.

The idea is that the attributes of a class view are the properties of theapplication in the applications terminology. So a Class View for a simulator

may sensibly use Model Variable names as attributes. Similarly, a datasheetattribute name would be taken almost directly from the datasheet text.

Once (for example) a datasheet is mapped to a Class View the datasheet

need never change if the lower tiers of the data model change. Also themapping exercise becomes much faster in the first place as you are linking

two highly related engineering views. This helps dramatically in subsequent

maintenance efforts.


18/57


Composite Class Views

Composite Class Views are the glue between the outside world defined byClass Views, and the core data model. In the middle tier of the data model,

they allow engineers to ensure data is shared correctly across applications

independently of the core model. One or many related applications

represented by Class Views map to a single Composite Class View which inturn has a unique mapping to the core data model.

Using the Class Library Editor you perform many operations using drag and

drop to simplify and speed the mapping processes. You can also view the

usage of individual attributes so you can explicitly see which class views (andtherefore applications) use the attribute. The Editor also maintains some

integrity to your data modeling by retaining mappings when you make simplename changes.

Classes

These are the fundamental building blocks of the Class Library. These support

all the modeling richness of Aspen Zyqad 11.1, and add support forAssociations and a range of new data types supported by Aspen Basic

Engineering. The Class Library Editor allows you to create and edit these withthe ability to check your work at the click of a button. Errors and warnings are

produced if necessary, and from these you can navigate to the source of the

problem. Graphical views are also provided to help model understanding.

Common Core Data Model (CCDM)

The Aspen Basic Engineering delivered Equipment Model is the Common CoreData Model or CCDM. Class Views and Composite Class Views have beenadded to support all of the interfaces, datasheets and applications delivered

with Aspen Basic Engineering. All of the classes that make up the systemlevel needs (not equipment) are broken out into a separate class store calledthe System Model.

Customizations are now stored in separate class libraries and ‘include’

libraries from the delivered class stores (that are now read only). Multipleclass stores can be combined to produce different model combinations.Existing delivered data model elements can be customized at will even though

these are read only. All changes are stored as extensions to the out of the

box data model.


19/57


Interface Applications

Bridge

The Aspen Basic Engineering bridge application is used to create a bridge

allowing two-way data transfer between an Aspen Basic Engineering

Workspace and either Microsoft Word or Microsoft Excel files. Users caninteract with the transfer process, data can be viewed as it is transferred anda bridge object can be configured to link data objects in applications.

New Bridges are defined in the design mode of the application. You define

‘links’ between Aspen Basic Engineering Class Views and the desktop tool in

this mode. Bridges can be saved and reused.

In this version of Aspen Basic Engineering, Microsoft Word and Microsoft Excel

are Bridge applications. The Bridge concept is designed for extension to otherdesktop applications at a later date.

Costing Interface

The Costing Interface is a two-way interface for estimating equipment costsand transfers equipment data between Aspen Basic Engineering and Costing

Tools and vice-versa:

Costing Tool to Aspen Basic EngineeringUse the interface to transfer data to equipment items in the Aspen Basic

Engineering database.

Aspen Basic Engineering to Costing Tool

Use the interface to update equipment data in the Costing Tool database,for example, after performing a thermal heat exchanger design from the

Aspen Basic Engineering database.

Supports only one-to-one mappings.

Object Mapper

This interface incorporates the Class View (and the three-tier data model)

functionality. (The New button item has been removed from each tab, and thedisabled Components tab has also been removed.)

Simulator InterfaceThis interface has been updated to incorporate the Class View (and the three-tier data model) functionality.

Aspen Basic Engineering supports the following simulators:

Aspen Plus Version 12.1 and later

HYSYS Version 3.1 and later

Pro/II Version .5.5 and later and client/server


20/57


Rules Editor

The Rules Editor is a syntax coloring editor for the creation and modificationof knowledge base (KB) script source files. It also allows these source files to

be compiled and loaded into the server, and allows you to execute Methods,

Rules, Sorts and Filters.

Rules, methods, demons, and events are the primary means of implementinga knowledge base. Rules is a generic term used to cover all knowledge base

elements regardless of their specific type.

ExplorerThe Aspen Basic Engineering Explorer provides an organizational view of

objects and data, diagrams and datasheets in an open workspace. You collectdatabase content into a tree view of folders from which you can then perform

a variety of operations.

Subject to your permissions, you can perform basic object operations such ascopy and clone through to browsing or editing object attributes. The attributeviews can either allow you to navigate the actual stored object structure or to

view the data in a flat engineering-oriented display. This latter view is helpful

to end-users rather than configuration users.

Authorized users can also assign security to folders giving another way of

managing access to objects, documents and data. The access rights simply

control access to the folder content. This is provided in addition to the mainaccess control features of the new Aspen Basic Engineering.

Folders are also used as a central part of the new Modular Design features of

Aspen Basic Engineering. The Explorer is used to import and export modulesin the form of Packages.

Packages

The Packages functionality includes the following:

Export a folder: An XML file is created in the packages directory with thefolder and all contained objects.

Import a package: Objects in the package are added into the currentfolder.

Export a drawing: An XML file is created in the packages directory with the

drawing and all contained objects.

Export a datasheet: An XML file is created in the packages directory with

the datasheet and all contained objects.

List Packages: When exporting/Importing Packages a list of all existingPackages is available.


21/57


Project Management andSmartplant

Project Management within Aspen BasicEngineering

A project within Aspen Basic Engineering is an isolated piece of work whosechanges are only visible to users logged on to that Project.

Projects typically are used for numerous purposes including:

Modifying an existing ‘as-built’ plant

Modifications can be made in a project so the main design is unaffected.Once the modifications have been carried out to the physical plant thenthe project can be ‘committed’, at which point the changes will be applied

to the main design.

Design alternativesDuring a design different topology options can be created and analyzed,each in its own project. Once the preferred design alternative is identified

then the corresponding project can be ‘committed’ to the main design andthe projects for the other alternatives discarded.

Segregating a Design

A design can be broken up into a number of sections, each section being aproject, so that users would work on the section(s) that they have beengiven access to. On completion of sections the corresponding projectswould be ‘committed’ to create a single contiguous design.

Project Support within SmartplantSmartplant® is a central data and document repository, and centralizedproject administration function. Aspen Basic Engineering supports thisfunction, allowing projects to be published and retrieved to Smartplant.

Intergraph’s SmartPlant Foundation (SPF) is at the core of Smartplant® andis required to allow Aspen Basic Engineering/Smartplant functionality.

Note: Before you can use Aspen Basic Engineering with Smartplant, aworkspace must be registered with an Smartplant plant database. This only

needs to be done the first time a workspace is to be used with Smartplant.

Registration is achieved via the Register Framework menu option.

Refer to the Aspen Basic Engineering online Help for further details of Project

Management within Aspen Basic Engineering and working with Smartplant.


22/57



23/57

3 Aspen Basic Engineering Basics 17

3 Aspen Basic EngineeringBasics

Aspen Basic Engineering is a client/server application that allows multiple

process designers to be connected to a single workspace. Changes made by

one client are immediately reflected in the information shown to other clients.To generate a process design, you create database objects that represent the

real world process. You can view and modify data for these objects using

several client applications.

This chapter contains the following sections:

Starting Aspen Basic Engineering

Accessing a project workspace

Datasheet Editor

Page setup configuration

Using workspaces

Quitting Aspen Basic Engineering

Starting Aspen BasicEngineeringTo start the Aspen Basic Engineering Datasheet Editor:

Do one of the following:

o On the desktop, double-click the Aspen Basic Engineering icon.

or

o From the Start Menu, point to Programs | AspenTech | AspenBasic Engineering, and click Datasheet Editor.

Note: To work with datasheets or diagrams, you must access a project

workspace.


24/57

18 3 Aspen Basic Engineering Basics

Opening WorkspacesBefore you can work with datasheets or diagrams, you must open aworkspace.

Note: The Aspen Basic Engineering client can only be connected to oneworkspace at a time. The Status bar shows the current workspace name andthe server machine on which it resides.

To change from the current workspace to another workspace, you must closethe current workspace and then open a new workspace.

To open a workspace:

1 From the File menu, click Open Workspace.

2 After Aspen Basic Engineering has verified the user name and password,

the Open Workspace dialog box is displayed. The list of workspacespresented depends upon the username entered. This information isconfigured by the project administrator who maintains a list of users thatcan access each workspace.

3 To connect to a workspace, select a workspace name, and then click OK.If you are the first user to connect to a workspace, or you are the firstuser to rejoin an inactive workspace, you may experience a delay while

the Aspen Basic Engineering server starts the workspace.

4 To close the current workspace click File | Close Workspace. After theworkspace is closed, the Status bar reflects the change in status. Both the

workspace and hostname areas are blank, indicating that you are no

longer connected to a workspace.


25/57

3 Aspen Basic Engineering Basics 19

Aspen Basic EngineeringWindowsThe names and layout of the items in the Aspen Basic Engineering windows(Datasheet Editor shown in this example) are:

Toolbars

Toolbars are used to access commonly used commands.

If the toolbar is not already displayed, click View | Toolbar.

To discover more about toolbar buttons:

Position the mouse pointer over a button. A tooltip appears beside thebutton, showing its name. The Status bar contains a longer description of

toolbar buttons.

To turn tooltips off, click View | Tooltips.

Note: When you turn off tooltips, the short description appears in the Statusbar when the pointer passes over a toolbar button.

Status BarThe Status bar displays the following information:

Messages generated by the system

User name

Name of the current workspace

Name of the server on which this workspace is running

To display the Status bar, click View | Status Bar.


26/57

20 3 Aspen Basic Engineering Basics


27/57

4 Using Aspen Basic Engineering 21

4 Using Aspen BasicEngineering

This section details procedures enabling you to understand:

Database objects

Cases

Documents (drawings and diagrams)

Revision control

Working with Database ObjectsAspen Basic Engineering uses an object-oriented database, containing

discrete data items, known as objects. An object can represent:

A real object

A connection between one or more real objects

An abstract data item

You create objects by:

Adding symbols to a diagram

Entering values on a datasheet

Using the commands from the Object menu or the Aspen BasicEngineering toolbar

Creating Database Objects

To create an object in the database:

1 From the Object menu, click Create.The Select Class dialog box appears, listing all the available types of object that can be created in this workspace.

2 Type or select the name of the type of object required and then click OK.

The object selected is created in the database.

To select more than one object class, hold down the SHIFT or CTRL key

at the same time as selecting a class:


28/57

22 4 Using Aspen Basic Engineering

To Select Use

A range of objects from the previous selection to the currentselection

SHIFT

Multiple separate items CTRL

Note: This is standard Microsoft Windows behavior and can be used on manyof the dialog boxes in Aspen Basic Engineering.

Deleting Database Objects

To delete a database object:

1 From the Object menu, click Delete.The Select Object dialog box appears, listing the objects that exist in thedatabase.

2 Type or select the name of the object to be deleted and then click OK.

The object is deleted from the database, along with any associated fittingobjects.

Copying Database Objects

A copy is a duplicate of a selected object in which the copied object has no

association with the original object. The attribute values of either the originalsor the copies can be modified without affecting the other.

Copying an object copies not only the original object, but also any fittings orsub-objects of the original. For example, if you copy a vessel that has an

agitator, the result is a new vessel which has a new agitator as a fitting. All of

the attributes of the original vessel and agitator are copied to the newobjects, including their status. That is, a locked value on the original vessel is

locked on the copy.

To copy an existing database object:

1 From the Object menu, click Copy.The Select Object dialog box appears, listing all the objects that exist in

the database.

2 Select the object(s) to be copied and then click OK.

Cloning Database Objects

A clone is a duplicate of a selected object in which certain attributes of the

original remain linked to the clone. A change to the original attribute's value

is reflected in the clone. The attributes that are linked are determined by thedefinition of the object's class in the prototype store. See also Copying

Database Objects above.

Cloning an object clones not only the original object, but also any fittings orsub-objects of the original. For example, if you clone a vessel that has an

agitator, the result is a new vessel clone, which has a new agitator clone as a

fitting.


29/57


To clone an existing database object:

1 From the Object menu, click Clone.

The Select Object dialog box appears, listing all the objects that exist inthe database.

2 Select the object or objects to be cloned and then click OK.

Working with Holds

A hold is a database object. You apply it to other database objects and

attributes to flag them as being held. Use holds to warn other users that the

held attribute or object data is uncertain, or liable to change.

You create and remove holds by:

Using the commands from the Object menu.

Drawing hold clouds on a diagram.

Setting the properties of a datasheet or label field.

Creating a HoldTo create a hold in the Aspen Basic Engineering window:

1 From the Object menu, click Create Hold.

2 Typically, you are prompted to supply a reason for creating the hold.

Removing a Hold

To remove (close) a hold:

1 From the Object menu, click Close Hold.

The Select Hold dialog box appears.

2 In the Select hold list, select the held object and then click OK.

3 Typically, you are prompted to supply a reason for removing (closing) thehold.

Current Object Filters

Many Aspen Basic Engineering commands require you to select one or moreobjects from the standard Select Object dialog box. When a large number of

objects exist, this list becomes extremely long and difficult to navigate.

When over 500 objects are in the selection, the list of objects is presented asa set of object ranges.

To focus on a particular object range:

1 Select the range from the object list.

The standard Select Object dialog box appears, containing only theobjects in the range selected.

To reduce the list of objects available for selection:

1 Change the object filter.


30/57


Changing the Object Filter

To change the current object filter shown in the central window at the top of

the Datasheet Editor window:

1 Click the down arrow at the right of the filter window and select therequired filter from the pull down list.

Working with CasesA case in Aspen Basic Engineering is a named set of values that applies to the

same objects and connections. Its scope does not cover topological cases

where the number of objects or connectivity of the same objects is different.

There are two types of cases:

Global cases – These apply to all objects in the database.

Restricted cases – These apply to individual objects in the database.

Initially, all database values on a project are part of the same global design

case. You can create, delete and rename other cases. For datasheets that

show more than one case, you can show or hide field values and copy datafrom one case to another.

Creating Cases

To create a new case:

1 From the Case menu, point to Create, then click Global or Restricted.

2 For restricted cases only, you must now select the object for the case.

3 In the Case Name dialog box, type a new name and click OK.

Deleting Cases

To delete a design case:

1 From the Case menu, click Delete.

2 In the Select Case dialog box, click the required case and then click OK.A dialog box appears, giving you the option of deleting any documents

that are based on the selected case.

3 Click OK.The case is deleted, along with all its database values.

Renaming CasesTo rename an existing case:

1 From the Case menu, click Rename.

2 In the Existing Case dialog box, select the case to be renamed.

3 In the New Name field, type a new name for the case, and click OK.

Note: You cannot rename a case to a name that already exists.


31/57


Copying Cases

To copy the data associated with a case to another case:

1 From the Case menu, click Copy Object Case.

2 In the Select Object dialog box, click the relevant object(s) and then

click OK.The Copy From Case dialog box is displayed, listing all of the casesavailable in the current project.

3 Click the source case, from which data is to be copied, and then click OK.

4 From the Copy To Case dialog box, click the destination case, to whichthe data is to be copied, and then click OK.

All data associated with the source case is copied to the destination case.

Working with DocumentsUse documents to manipulate objects and their values in a database. Aspen

Basic Engineering uses two different types of document:

DocumentType

HandledThrough

Description

Datasheet DatasheetEditor

Shows database values for one or more objects in thedatabase. You can then perform document managementactions on the group and not the individual documents.Document groups can be created as a pre-defined set or

manually built up from existing datasheets

Drawing DrawingEditor

Shows a graphical representation of objects and theconnections between them, and enables you tomanipulate these objects and their connectivity. Alsoenables you to modify database values through labels

placed on the diagram

Accessing DocumentsDocuments (datasheets and diagrams) are accessed from the File menu.

Accessing Datasheets

From the File menu, point to Datasheets and click one of the five 'by'options.

The following table explains the five menu options:

Menu Option Use To Access When You Click This Option

by Object New or existingdatasheets byobject

The Select Object dialog box opens, whereyou select the required database object.

You then click OK to open the Datasheetsdialog box


32/57


by Type New or existingdatasheets bytheir type

The Select Datasheet Type dialog box opens,where you select the required datasheet type.You then click OK to open the Datasheetsdialog box

by Submitted Existingsubmitted

datasheets

The Datasheets dialog box opens directly

by Checked Existing checked

datasheets


by Issued Existing issueddatasheets


With all options, you ultimately reach the Datasheets dialog box.

Use the buttons on the right of the dialog box to perform tasks, such asrenaming a datasheet or issuing a checked datasheet.

Accessing Diagrams

From the File menu, click Diagrams.The Diagrams dialog box appears, which has the same features as the

Datasheets dialog box, described above.

Creating New Datasheets

To create a new datasheet:

1 From the File menu, point to Datasheet, and then click by Object or by

Type.

2 From the displayed list, click the name of the required database object,datasheet type, or group, and then click OK.

3 In the Datasheets dialog box, ensure New is selected, select the

document you want and then click Open.


33/57


Creating New Diagrams

Before creating a new diagram, you must decide if you want it to be:

A one-off diagram of a plant, representing one operational case.

One of several (shared) diagrams of the same plant, each representing adifferent operational case. For example, you may have two shared

diagrams, representing winter and summer operating conditions.

Creating One-Off Diagrams

1 From the File menu, click Diagrams (the Diagrams dialog box isdisplayed).

2 Select New at the top of the dialog box.

A list appears with two entries: New Diagram and Shared Diagram.

3 Select New Diagram and click the Open button.

4 In the dialog box that appears, enter the diagram name and click OK.

The Aspen Basic Engineering Drawing Editor opens, with the diagramappearing in the Drawing Window. The diagram status is now current.

Note:You need the drawing application installed to use diagrams. You canchange a diagram from one-off to shared, at a later date.

Creating Shared Diagrams

To create a shared diagram:

1 From the File menu, click Diagrams.

The Diagrams dialog box appears.

2 Select New at the top of the dialog box.

A list appears with two entries: New Diagram and Shared Diagram.

3 Select Shared Diagram and click the Open button.The Select Diagram dialog box appears, listing the existing diagramsplus an option entitled 'New Shared'.

To create a shared diagram based on an existing diagram, select the

existing diagram.

Select New Share to create a shared diagram that will form the template

for future shared diagrams.

Opening Existing Documents

With either choice, you are prompted for the diagram name (see CreatingOne-Off Diagrams, above).

You open existing documents from the File menu:

1 Follow the accessing documents procedure (see Accessing Documents)

until you reach either the Datasheets or the Diagrams dialog box.These dialog boxes have the same features.

2 In the Datasheets or Diagrams dialog box, select the datasheet or

diagram and click the Open button.


34/57


Tip: Use the Current, Submitted, Checked or Issued radio buttons to switch

between categories of documents.

Note: If you open the current version of a document that is also submitted orchecked, you are prompted to confirm opening. If you select a datasheetgroup, all members of the group are opened.

Viewing Document Status

To view the status of documents:

1 From the File menu, follow the accessing documents procedure (seeAccessing Documents) to reach the Datasheets or Diagrams dialog box,

as appropriate.

These dialog boxes have the same features.

2 Use the tabs at the top of the dialog box, to list the datasheets by their

status.

Printing Documents Printing a currently open datasheet.

Printing multiple datasheets.

Printing diagrams.

For information on printing datasheets, see the User Guide - Using Datasheets

and Diagrams.

Renaming Documents

To rename a document:


until you reach either the Datasheets or the Diagrams dialog box.These dialog boxes have the same features.

2 Select Current at the top of the dialog box (Datasheets or Diagrams

dialog box).

3 Select a datasheet or diagram and then click the Rename button.

4 Type the new name for the document in the dialog box and click OK.


35/57


36/57


Submitted Version

For information on how to submit a document for checking, see Submitting a

Document.

Documents submitted for checking are read-only versions of the current

documents, whose fields show the values as they were in the database at the

time that the document was submitted. You cannot edit the fields on asubmitted datasheet, so cannot change the database through a submittedsheet. The submitted document still retains the concept of changed since last

issue and these changed values are displayed in the same way as the current

version of the document.

The submitted revision level allows you to check the data entered on the

submitted datasheet. You can perform the following revision control actions

on a Submitted document:

Check

Withdraw (delete)

To use these options, you must have Check privileges; otherwise, you cannot

check or withdraw documents.

Checked Version

For information on how to check a document, see Checking a Document.

Checked documents are read-only versions of the current documents, whosevalue fields reflect the values in the database at the time they were submitted

for checking. You cannot edit the fields on a checked datasheet and therefore

cannot modify the database through a checked document. The checkeddocument still retains the concept of changed since last issue and thesechanged values are displayed in the same way as the current version of the

document.

The checked revision level shows that a document that was submitted hasbeen checked and is now awaiting issue.

You can perform the following revision control actions on a Checked

document:

Issue

Withdraw (delete)

To use these options, you must have Issue privileges; otherwise, you cannot

issue or withdraw documents.

Issued Version

For information on how to issue a document, see Issuing a Document.

Issued documents are read-only versions of the last issue of the current

documents of the same name. The values in issued documents are those thatthe fields had at the time that the document was submitted. This version is

the one against which the comparison with the last issue is made.

Only the last issued version is recorded within Aspen Basic Engineering. Theonly way to remove the issued document is to withdraw the current versionfrom the database.


37/57


Submitting a Document

Any user can submit a document for checking. You can submit an open orclosed document. For information about submitted documents, see Submitted

Version, under Document Revision Control.

Note: You cannot submit individual members of a datasheet group.

Submitting a Closed Document

To submit a document without having to open it:

1 From the File menu, do one of the following:

For datasheets point to Datasheet, click by Object or by Type and then

from the displayed list, click the name of the required database object,type or group.

– or –

For diagrams, click Diagram.

2 In the Datasheets or Diagrams dialog box, select Current at the top of the dialog box.

3 Select the required document(s) from the list, and then click the Control

button.

4 From the menu click Submit.If any of the selected documents are already in the Submitted or Checkedstates, you are prompted to confirm the re-submission.

To Click

Resubmit the document, replacing the version that is currentlysubmitted, even if it was in the checked state

Yes

Abandon the submission of the named document, or group of documents, but continue submitting the other documents

No

Abandon the submission of all chosen documents Cancel

Submitting an Open Document

To submit an open datasheet:

From the Datasheet menu, click Submit.

Note: This menu option is active only when you are viewing the currentversion of a datasheet.

Diagrams open in the Aspen Basic Engineering Drawing Editor, and this is

where you change their status.

To submit an open diagram:

From the Aspen Basic Engineering Drawing Editor File menu, point to

Status and click Submit.


38/57


Checking a Document

Only submitted documents can be checked.

You can pass a submitted document as checked without opening it or while

the document is open. For information about checked documents, seeChecked Version, under Document Revision Control.

Note: You cannot check individual members of a datasheet group.

Checking a Closed Document

To pass a submitted document as checked:


For datasheets, point to Datasheet and click by Submitted.

– or –


The Datasheets or Diagram dialog box appears.

2 If necessary, select Submitted at the top of the dialog box.

3 Select the required document(s) from the list, and then click the Controlbutton.

4 From the menu that appears, click Check.

The selected documents are checked.

Note: If the current version of the document has been modified after it wassubmitted, you are prompted for confirmation to proceed.

Checking an Open Document

To check an open submitted datasheet:

From the Datasheet menu, click Check.

Note: This menu option is active only when you are viewing the submittedversion of a datasheet.

Diagrams open in the Aspen Basic Engineering Drawing Editor, and this iswhere you change their status.

To check an open submitted diagram:

From the Aspen Basic Engineering Drawing Editor File menu, point toStatus and click Check.


39/57


Issuing a Document

Only checked documents can be issued.

You can issue a checked document that is open or closed. For information

about issued documents, see Issued Version under Document RevisionControl.

Note: You cannot issue individual members of a datasheet group.

Issuing a Closed Document

To issue a closed document:


For datasheets, point to Datasheet and click by Checked.

– or –



2 If necessary, select Checked at the top of the dialog box.

3 Select the required document(s) from the list, and then click the Controlbutton.

4 From the menu that appears, click Issue.

5 When prompted, type the revision level for the document and click OK.

Note: The revision level entered here is used to mark the values that havechanged since the last issue.

The selected documents are issued.

Issuing an Open Document

To issue an open checked datasheet:

From the Datasheet menu, click Issue.

Note: This menu option is only active when you are viewing the checkedversion of a datasheet.

Diagrams open in the Aspen Basic Engineering Drawing Editor and this is

where you change their status.

To issue an open checked diagram:

From the Aspen Basic Engineering Drawing Editor File menu, point to

Status and click Issue.


40/57


Deleting a Document

When you use the Withdraw command on the current version of a

document, the document is deleted, provided that it is not open in any user's

session. To delete a document:


until you reach either the Datasheets or the Diagrams dialog box.

These dialog boxes have the same features.

2 In the Datasheets dialog box, or Diagrams dialog box, select Current at

the top of the dialog box.

3 Select the required document(s) and click the Control button.

4 From the Menu that appears, click Withdraw.

You are prompted to confirm the deletion before proceeding.

Note: If any of the selected documents are open in any user’s Aspen BasicEngineering client, a warning dialog is displayed and the named documents

are not deleted.

Removing a Document from the Revision

Process

If you decide not to proceed with checking and issuing a submitted document,you can remove the document from the revision control process using the

Withdraw command. To do this:

1 From the File menu,

For datasheets, point to Datasheet and click by Submitted or byChecked.

– or –



2 If necessary, select Submitted or Checked at the top of the dialog box.

3 In either the Datasheets or Diagrams dialog box, select the required

document(s) and click the Control button.

4 From the menu click Withdraw.

The selected documents are removed from their submitted or checked

states. (If you click Withdraw when viewing the Current version list of documents, the document is deleted.)

Note: You cannot independently withdraw individual members of a datasheet

group from the revision procedure.


41/57

5 Glossary 35

5 Glossary

Glossary of Terms

Administration User

A user with responsibility for the creation and management of Workspaces,

including the registration of users and allocation of roles and responsibilities.

AES

Aspen Engineering Suite, a collection of AspenTech products for process

engineering or the functional organization that produces the same suite of

products.

Aggregation

A special kind of association representing a “whole/part” relationship. Theobject at one end of the association represents a whole and the object at the

other end represents the part. For example, a centrifugal pump may have an

aggregation association with the class “impeller”.

Annotation

A free form single line of text that can be used to place comments on a

document.

API datasheet

The American Petroleum Institute is the primary trade associationrepresenting the oil and natural gas industry in the United States. It publishes

a wide range of standards for the design of equipment, many of which includedatasheets. Some of the API datasheets will be included in Aspen Basic

Engineering.


42/57

36 5 Glossary

Application

A tool/program that is interfaced to Aspen Basic Engineering to exchangedata.

Application InterfaceA provisional title given to the mechanism to easily interface an application to

the product. This feature is likely to be renamed.

As-Built

As-built refers to the design representing the physical state of a plant as it

exists at that point in time. A workspace/design becomes ‘as-built’ when the

plant is physically constructed. The plant and therefore the as-builtdesign/workspace will change throughout the life of the plant as modificationsare made to the plant as the result of projects carried out to improve

performance and/or operability of the plant.

Association

An association is a structural or semantic relationship between two objects.For example, a piping system may have an association with the equipment

items where the piping system terminates.

Attribute

The property of an object instanced from the data model.

ATESA

AspenTech Enterprise Server Architecture

Authoring Application

The term is used to refer to a GAIP application in which data is edited by

designers. This equates to: Aspen Basic Engineering, SP P&ID, INTools, SP 3D(there are others also). It does not include SPF that doesn’t allow editing of

data.

Base ClassA class from which another class is derived.

BEDD

Basic Engineering Design Data. The information concerning the site, climatic

conditions, utilities etc., that pertain to a particular process plant or site.


43/57

5 Glossary 37

Boolean

A data type, for an attribute, that restricts the attribute to hold only the valueTrue or False. This data type is used to model data items normally

represented by check boxes or Yes/No values.

Bridge

An instance of an interface between the workspace and another tool (forexample a desktop tool).

Case

A named set of data associated with the objects in a project database. You

can create design cases to hold different design data for the same topology of the objects. See also Restricted Case and Global Case.

Case FixedA property of an attribute, that indicates whether this attribute has the same

value for all design cases. For attributes where the data type is an objectclass then this is always true. A vector attribute that is case variant may havea different number of elements for each design case.

Category

A keyword or keywords that may be attached to a data model construct tosupport sorting, searching and filtering of data model constructs andinstances.

CCDM

Common Core Data Model. The Equipment Data model used to represent

engineering objects. The out of the box CCDM contains all the data modelconstructs to support the delivered datasheets and application interfaces.

Claim

Status of an object that indicates whether it is included in the scope of a

project.

Class

A class is a set of objects that share the same set of attributes. A class

definition acts as a template for all instances of the objects of the class.Classes may have relationships between them. Relationships include

generalization and association.


44/57

38 5 Glossary

Class Library

A named collection of data model constructs related in some way. Forexample a Class Library may contain all the constructs related to rotating

equipment.

Class Store

A self-consistent collection of data model constructs required to support aWorkspace. A Class Store is created using the Class Library Editor and loadedinto a Workspace when the Workspace is first opened.

Class View

An Aspen Basic Engineering application or third party external applicationview of the data in, or associated with, a class.

CloneA duplicate of a selected object in which certain attributes (see clone fixed

below) of the original remain linked to the clone. A change to the originalattributes’ value is reflected in the clone.

Clone Fixed

A property of an attribute that indicates whether an attribute has the same

value for all clones of an object.

Composite (Class) ViewAn engineering view of the data represented by, or associated with, a classthat is the result of merging the class views for a class. Typically a single

composite view is used to represent all the data required by a major

engineering artifact such as a pump.

Conceptual Data Model

The Aspen Basic Engineering data model expressed in the form of classes,

associations and enumeration data model construct. The conceptual model is

based on data modelling principles that employ abstraction and normalisation

to create a compact and re-usable model. Typically many data modelconstructs are used to model one major engineering object.

Configuration User

A configuration user is an Aspen Basic Engineering user responsible for the

customization of Aspen Basic Engineering within their organization. Forexample, the creation of organization specific data models, datasheets, labels,

scripts and configuration tasks.


45/57

5 Glossary 39

Connection

A two-ended link between database objects, used to represent the flowsbetween these objects.

CopyA duplicate of a selected object in which the copied object has no association

with the original object. A change to the original attributes’ value has noeffect on the copy.

Data Model

A formal representation of the data that may be stored in the Aspen Basic

Engineering Workspace. The data model is expressed in the data modelconstructs, held in one or more class libraries.

Data Model ConstructAny basic building block of the data model. Data Model Constructs include:

class, association, enumeration, class view, and composite view.

Datasheet

The pre-established form that is filled in by an end-user working on anengineering project.

Old Definition: A single page document.

New Definition: A multi-page document.

Datasheet Builder

A user who constructs datasheets as a primary task, or a user who is doingthe task of defining a datasheet.

Datasheet Group

A collection of datasheets that are treated as a single document for thepurpose of creation and revision control.

Default FixedA property of an attribute that determines if the attribute values can be

changed from its default value.


46/57

40 5 Glossary

Delete

A command to delete the active/visible item and should not be inferred as

meaning delete workspace object. For example, deleting a graphical

representation does not destroy the underlying workspace object. In usecases, the preferred terms are Remove and Destroy.

Destroy

To destroy an object in the workspace such that it no longer exists.

Discipline

A discipline is a privilege that can be defined by a configuration user torestrict access to the attributes of a class.

Display Name

A property of a data model construct that is used to identify the construct inthe end user interface but is not used to reference the construct internally

within the system. For example, the display name of a class may be changed

by the configuration user without affecting internal references to the class.

Document

Old Definition: A database item that is one of:

A single page datasheet.

A summary sheet.

A Drawing.

New Definition: A database item that is one of:

A multi-page datasheet.

A summary sheet.

A Drawing.

Drawing

A document that is edited using the Drawing Application.

End User

An engineer using Aspen Basic Engineering and other tools to execute anengineering project, with little or no interest in, or responsibility for, theconfiguration or administration of the Aspen Basic Engineering software

installation.


47/57

5 Glossary 41

Engineering Framework

Intergraph/AspenTech developed application that is used to integrate FEEDtools, currently Aspen Basic Engineering, INTools, SP P&ID and a data

repository (Notia) together.

Enumeration Data Type

A data type that specifies the allowed values which an attribute of that datatype may hold.

Equipment List

An alternative name for a summary sheet.

EXPRESS

A data modeling language adopted by the ISO working group on STEP.

FEED

Front-End Engineering and Design. In this context primarily relates to the

ease by which objects and/or data can be created or updated on the basis of

object data from simulators, under conditions where the simulation topologycan be relatively abstract in comparison to the desired engineering PFD.

Field

In a datasheet or label, a location where a user can enter or view data from aworkspace object.

Field Lock

An access control mechanism that allows only users with Lock privilege tomodify the field.

Field Status

An attribute value can have a number of status flags:

D – value is derived. The value has been generated by the knowledgebase.

S – value is secure. The value can only be viewed by users with secure

privilege.

L – value is locked. The value can only be modified by users withoverwrite privilege.

AspenBasicEngV7 3 Start

Documents

Transcript of AspenBasicEngV7 3 Start