aspenONE Infrastructure

Overview
Version Number: V9
May 2016
Copyright (c) 2004 - 2016 by Aspen Technology, Inc. All rights reserved.

aspenONE Integration Foundation, aspenONE Infrastructure, Aspen Integration Designer, Aspen Enterprise
Integration Framework, Aspen Event Management, Aspen Role-Based Visualization, Aspen Manufacturing Master
Data Manager, Aspen mMDM Editor, Aspen Operations Manager, Aspen Bulk Load, Aspen InfoPlus.21, Aspen IP.21
Process Browser, Aspen Web.21, Aspen License Manager, and the aspen leaf logo are trademarks or registered
trademarks of Aspen Technology, Inc., Bedford, MA.

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

This manual is intended as a guide to using AspenTech's software. This documentation contains AspenTech
proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of
AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of
the software and the application of the results obtained.

Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION,
ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Aspen Technology, Inc.

20 Crosby Drive
Bedford, MA 01730
USA
Phone: (781) 221-6400
Website: http://www.aspentech.com
Contents
1 Introduction .........................................................................................................5
About This Document .......................................................................................5
Organization ..........................................................................................5
Related Documentation .....................................................................................5
Aspen Manufacturing Master Data Manager Documentation .........................6
aspenONE Integration Foundation Documentation ......................................6
Aspen Reporting Framework Documentation..............................................6
Technical Support ............................................................................................6

2 Aspen Integration Foundation..............................................................................8

Overview.........................................................................................................8
Why aspenONE Integration Foundation?....................................................8
Point-to-Point Integration Methodology .....................................................9
Central Database Integration Methodology ................................................9
Message Bus Integration Methodology ......................................................9
Architecture Overview..................................................................................... 10
aspenONE Integration Foundation Message Bus ....................................... 11

3 Aspen Manufacturing Master Data Manager .......................................................13

Other Aspen mMDM Features........................................................................... 16
Aspen mMDM Architecture............................................................................... 19
Aspen mMDM Editor ....................................................................................... 20
Aspen mMDM Bulk Load .................................................................................. 21
The mMDM Bulk Load Spreadsheet......................................................... 22
mMDM Bulk Load Utility ........................................................................ 22

4 Aspen Reporting Framework ..............................................................................25

Contents 3
4 1 Introduction
1 Introduction

This document gives an overview of aspenONE Infrastructure™ software and

describes how it works together to benefit your business process.
aspenONE Infrastructure provides a common set of capabilities which, when
configured as part of aspenONE’s modules, give you the functionality to
visualize, analyze and optimize your operations in a collaborative
environment. It includes the following:
1 Integration foundation. Integrate applications and data from
AspenTech and third parties through aspenONE Integration Foundation’s
Enterprise Integration Framework™.
2 Common operations domain model. Manage enterprise configuration
data and let applications share this data easily through aspenONE
Integration Foundation’s Aspen Manufacturing Master Data Manager™,
formerly known as Aspen Operations Domain Model.
3 Reporting and analysis. Configure reports and KPIs using data
aggregated for reporting and analysis through Aspen Reporting
Framework™.

About This Document

Organization
This document contains the following:
Chapter 1 − Introduction − provides a brief overview of the document and a
list of related documentation.
Chapter 2 – Aspen Integration Foundation
Chapter 3 – Aspen Manufacturing Master Data Manager
Chapter 4 – Aspen Reporting Framework

Related Documentation
In addition to this document, a number of other documents are available to
help you learn and use aspenONE Infrastructure software. The documentation
set consists of the following:

1 Introduction 5
 Aspen Manufacturing Master Data Manager
Documentation
Aspen Manufacturing Master Data Manager Installation Guide
Aspen Manufacturing Master Data Manager Implementation Guide
Aspen mMDM Getting Started Guide
aspenONE Integration Foundation Release Notes
Aspen mMDM Editor Help
Aspen mMDM Bulk Load Help
Aspen mMDM Administrator Help

aspenONE Integration Foundation

Documentation
aspenONE Integration Foundation Installation Guide
aspenONE Integration Foundation Release Notes
Aspen Integration Designer Help

Aspen Reporting Framework

Documentation
Aspen Reporting Framework Installation and Configuration Guide
Aspen Reporting Framework Release Notes
Aspen Reporting Framework User Guide

Technical Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the online AspenTech Support Center at:
https://support.aspentech.com
This Web support site allows you to:
• Access current product documentation
• Search for tech 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
• Send suggestions
• Report product defects
• Review lists of known deficiencies and defects

6 1 Introduction
 Registered users can also subscribe to our Technical Support e-Bulletins.
These e-Bulletins are used to alert users to important technical support
information such as:
• Technical advisories
• Product updates and releases
Customer support is also available by phone, fax, and email. The most up-to-
date contact information is available at the AspenTech Support Center at
https://support.aspentech.com.

1 Introduction 7
2 Aspen Integration
Foundation

Overview
The aspenONE integration strategy is enabled by aspenONE Integration
Foundation (AIF), the infrastructure foundation that delivers quicker
integrations and higher performance with a lower Total Cost of Ownership by
standardizing the way AspenTech applications integrate with AspenTech and
other process-oriented applications.

aspenONE Integration Foundation

Why aspenONE Integration Foundation?

Is aspenONE Integration Foundation the right approach for integrating my
aspenONE solution? This is an important question that must be answered
when choosing aspenONE Integration Foundation. To do this, we must look at
the evolution of integration and the aspenONE integration methodology.

8 2 Aspen Integration Foundation

 Point-to-Point Integration Methodology
In the beginning, there were point-to-point interfaces. A large Supply Chain
and Manufacturing project could require as many as a hundred separate
interfaces to be developed, often using different development tools, as it was
driven by the technologies available in the platforms of the systems being
integrated. The logic of the integration was hard-coded in the interface.
This approach was not scalable and ultimately very difficult to support.

Central Database Integration Methodology

The next integration approach introduced a central database to the
methodology. While conceptually superior to the point-to-point approach and
almost universally adopted elsewhere in the software industry today, this
does not work well in applications where there is a large mix of different
products, applications, and technologies.

Evolution of AspenTech’s Integration Strategy

Message Bus Integration Methodology

Eventually, we discovered that each component should be able to exist on its
own terms in order to ensure an integrated workflow. It is valuable to share
models where it makes sense but not attempt to force them when they do not
share a common understanding.
The goal of AIF is to provide best-practice Execution Management and to
deliver the flexibility to combine and recombine application components
without custom software development.
CIOs are looking for infrastructure solutions with a smaller footprint that are
easy to deploy and maintain, leading to a lower Total Cost of Ownership. To
address this, AspenTech has employed .NET 3.5 and Microsoft’s Windows

2 Aspen Integration Foundation 9

 Communication Foundation (WCF) technologies, ensuring AIF is built upon
existing technologies already deployed on corporate servers and desktops.
The exposure of aspenONE data through open gateways leads to integrated
aspenONE solutions existing and operating in a Service Oriented Architecture
(SOA) fashion, enabling simple integration with other corporate business
systems. The gateway approach is a positive step away from a reliance on
one technology or infrastructure provider, enabling aspenONE integration to
be easily deployed in any corporate IT landscape.
As shown below, the core components of the AspenTech AIF architecture
include:
• The aspenONE Integration Foundation BPD Message Bus
• Manufacturing Master Data Manager (mMDM)
• aspenONE Integration Foundation adapters that allow AspenTech
applications to plug into the integration Foundation
• Web Service Gateways to other communications networks

W/S
Gateway

Master
Data Model

BPD Security Management

Message

Bus

AspenTech
Applications

Integration architecture between AspenTech applications

Architecture Overview
aspenONE Integration Foundation architecture components are summarized
below.

10 2 Aspen Integration Foundation

 aspenONE Integration Foundation Message
Bus
The Message Bus is the transport layer of AIF that connects applications
together via messages.
These messages are based on Business Process Documents (BPDs), which are
defined schema definitions implemented in XML (eXtensible Markup
Language) Schema Definition (XSD) language using the guidelines outlined by
AspenTech.

Business Process Documents (BPDs)

The AIF BPDs are grouped into two basic groups: the core set that all other
BPDs build upon, and the integration set. The list of core BPDs is:
• BPDCommon – contains all classes and types that are common across
multiple BPD schemas.
• BPDCommonMessages – common business process documents shared
across many solution offerings.
• BPDHeader – this is the standard header definition used for all compliant
BPD messages.
The integration BPDs include the Supply Chain BPD (used for AIF flows) and
the ASCC BPD (used for PSCP and CDM flows). The PIMS to PSCP flow is SQL-
derived.

Communication with the Message Bus

The communication capability of the Message Bus is built on the following key
attributes:
• Asynchronous Publish / Subscribe messaging
• Synchronous Request / Reply messaging
• Certified Publish and Subscribe
• AspenTech and industry standard XML messages based on ISA-95
These elements in the Message Bus provide the ability to integrate application
components, yet maintain enough flexibility to cope with a range of business
process evolution directions.
This approach greatly reduces the need for a single enterprise-wide database,
increasing system agility, robustness, and performance.
The components of the Message Bus are as follows:
• Core – The Message Bus
• Aspen Integration Designer – The administration tool
• Routing Daemon – for communications across subnets
• Software Development Kit
• Common XML Schemas
• Enterprise Logging Mechanism
• Web Services Gateways and RendezVous Gateways

2 Aspen Integration Foundation 11

 The following diagram shows Aspen Integration Designer, a single GUI which
provides the ability to remotely discover, configure, and administer
applications and services throughout the enterprise. The infrastructure can be
viewed, analyzed, and configured from a central location.

Aspen Integration Designer

12 2 Aspen Integration Foundation

3 Aspen Manufacturing
Master Data Manager

Master Data in the integrated aspenONE solution is defined and maintained

based on a centralized master data model using Aspen Manufacturing Master
Data Manager™ (Aspen mMDM).
Aspen mMDM provides a common repository for defining master data for all
the different business and process systems in the integrated aspenONE
system.
Aspen mMDM is universal to all applications and integration within an
AspenTech integration project and provides the following functions:
• Definition of all assets in master data model
• Common Lookup and Aliasing of master data for all AIF adapters
• Universal Common Functions such as UOM conversion

Note: For V9, the web-based mMDM Configuration Manager tool is disabled.
The mMDM Editor can provide access to all the data management features
previously provided by mMDM Configuration Manager.

Canonical Master Data

Although it is not possible to centralize the whole model of all of our products,
there are certain aspects that you can centralize. Material codes, for example,
or equipment names, units of measure, physical properties – master data.
The Aspen Manufacturing Master Data Manager (mMDM) product defines this
model and provides the ability to alias the names of all these things between
the products.
For example, the blend component MTBE in Aspen Petroleum Scheduler (our
refinery scheduling application) might be called MTB in Aspen PIMS (our
refinery planning application), because material codes are 4 characters in
Aspen Petroleum Scheduler but only 3 in Aspen PIMS.
The message itself will not contain either MTB or MTBE, but instead will
contain Aspen mMDM’s unique identifier for that material, in the form of a
large number, such as 100125. When an adapter wants to read or write a
message using that material, it simply asks Aspen mMDM for its own name
for that identifier. For example, the Petroleum Scheduler adapter might
receive a message with the material 100125, and when it asks the mMDM for
a name, Aspen mMDM will tell it MTBE.

Important: Due to the message bus, no product has any knowledge of any
other.

3 Aspen Manufacturing Master Data Manager 13

 There are no “Petroleum Scheduler to PIMS” interfaces, only a Petroleum
Scheduler message bus adapter and a PIMS message bus adapter, and
possibly some additional orchestration.

Components
The components of Aspen mMDM are based on the ISA-95 standard, including
the following:
• Alias – Translates the mapping code used to define objects, so Aspen
products and/or third-party applications can easily exchange data (as
shown in the picture below). Aliasing can be defined for attribute,
material, generic, equipment, Unit of Measure (UOMs), geographic
locations and physical properties.

• Equipment – Lets you define and maintain a list of all equipment used by
Aspen products or third-party applications that exchange data with Aspen
products. Pieces of equipment may have attributes assigned to them and
may be referenced by the Hierarchy component. Both physical equipment
(such as tanks or reactors within a plant) and logical groupings of
equipment (such as the entire plant itself) are included in the list of
equipment.
• Location – Lets you define and maintain a list of all geographic locations
that are used in the business processes. These locations can also be used
for equipment definitions.
• Hierarchy – Lets you generically classify and group configuration
definitions and define parent/child relationships between definitions. S95
Hierarchy definitions (equipment hierarchies) can be defined in addition to
the non- S95 Hierarchy definitions. S95 hierarchy definitions are created
based on the S95 rules for equipment hierarchies.

14 3 Aspen Manufacturing Master Data Manager

 • Material – Lets you define and maintain a list of all materials used by
Aspen products or third-party applications that exchange data with Aspen
products. Materials may have both attributes and properties assigned to
them. Additionally, materials may be referenced by both the Hierarchy
and Price components.
• Physical Property – Lets you define and manage a list of all physical
property definitions including their default, minimum, and maximum
values. These definitions are used in the property values that are assigned
to material definitions.
• Unit of Measure (UOM) – Contains a master list of all UOMs used by
Aspen products or third-party applications that exchange data with Aspen
products. These UOMs are organized by quantity type and may be
converted to any other UOM of the same quantity type. For each quantity
type within a UOM set, a default UOM can be assigned so that applications
can easily convert any UOM to a standard default for that application.
The following figure shows the Aspen mMDM Editor, used to define and
maintain all master data assets.

Aspen mMDM Editor

3 Aspen Manufacturing Master Data Manager 15

 Other Aspen mMDM Features
In addition to providing the basic requirements of a reference data repository,
Aspen mMDM delivers the following key features:

Feature Description
Time-based Aspen mMDM tracks all changes to the information over time. This
Data lets you type configuration data that is time sensitive and see the
changes to the information at the current time or any time in the
past or future. This applies to all information that is contained
within Aspen mMDM.
Versioning The information is also tracked by version. This allows the data to
be published out to users, who can then use this information off
line without worrying about the data changing. When data is
published, it becomes immutable and cannot be changed. This lets
the user reproduce results with planning, scheduling, or
accounting systems exactly as they had done when they initially
ran those systems. The versioning of the information is critical to
the distribution of the master data.
Data Aspen mMDM allows copies of the master data to be distributed to
Distribution other computers within a network. Having local cached copies of
the data greatly improves performance when referencing the
data. Master data is distributed using a subscription-based
architecture whereby master data is published to subscribing
computers. This architecture greatly improves network efficiency
when compared to point-to-point distribution paradigms. Before
publishing data, the data can be validated to ensure the integrity
of the data.
Transactional All modifications to the Manufacturing Master Data Manager are
Integrity performed within a transaction. If these changes are required to
be part of a larger transaction, then the components can be
enrolled in a distributed transaction, thus ensuring the integrity of
the business transaction. This transactional behavior is
fundamental in the design of the components.
Auditing of Changes to reference data are tracked by Aspen mMDM by
Changes recording the user and timestamp involved in the change event.
This information is stored in the database with each record and
can be viewed from the web administration tool. The auditing
feature is integral to the components; therefore, it cannot be
circumvented.
Incremental Uses event driven messaging (via Aspen Enterprise Integration
Updates Framework) to synchronize mMDM to an external master data
system, or to synchronize a downstream subordinate system to a
master mMDM system.
Document Transactionally caches incoming and outgoing XML documents
Caching (BPDs) and can optionally process the documents. Aspen mMDM
uses this feature as part of the incremental update feature.
Document Uses the document cache to store published XML documents
Archiving (BPDs), and then enables external applications to request
historized documents from the archive using a message-based
interface.

16 3 Aspen Manufacturing Master Data Manager

 Feature Description
Access Control Access control, also called authorization services, is one aspect of
Security securing an application whereby a user (or group of users) is
granted the ability to view or modify application data. Access
control features have been added to Aspen mMDM to help secure
the master database. When enabled, administrators can grant
user access to specific Aspen mMDM components or to Aspen
mMDM entirely. Aspen mMDM uses a role-based security
framework where members of a role are granted access to data or
services within Aspen mMDM.
Editor The Aspen mMDM Editor program provides another alternative
mechanism for maintaining mMDM data. The Aspen mMDM Editor
is a rich client (Windows Forms-based GUI) that has been
designed using Microsoft's "Smart Client" technology. This allows
the GUI to be launched from a web browser, then automatically
be downloaded and installed onto the client computer. The Aspen
mMDM Editor provides a rich environment for editing mMDM data
because it supports advanced features, such as drag-and-drop
editing, cut-copy-and-paste functionality, resizable panes, and
useful visual feedback while editing.
Bulk Load The Bulk Load program provides an alternative to the Aspen
mMDM Editor for maintaining mMDM data. It is typically used
when large amounts of data must be manipulated. The system is
based on Microsoft Excel, which provides a common user interface
that is familiar to many users. For example, this mechanism lets a
project team define the information, review it with the client, and
then load it into the system as a complete set. It also lets the user
create a template of a solution for quick implementation in
multiple plants. The online help provides significant details about
the flexibility and power of the system.
Calculations Allows you to define calculations, using either an external engine,
such Aspen Calc, or by writing your own using Microsoft’s C#.
These calculations can be as complex as the user needs. Once
they are defined, the user can associate the calculation to a class
attribute.
SQL Queries Allows you to define SQL Queries that can then be associated to
dynamic attributes in a class definition. These queries can be as
simple or as complex as necessary.
Status Allows you to define and configure status indicators that can be
Indicators used to turn numerical values into a status values. A status value
has a name, description, image, and URL that represent the status
of any process value. This is used with the Operations Navigator
in Aspen Role-Based Visualization to dynamically show values to
users in real time. A simple example of this is to have the status
of a tank display in red when the volume reaches within 5 percent
of the tank capacity. The algorithms that you can create can be
very complex, but the configuration is driven through a simple to
use interface. Both dynamic values and calculations can be used
as the input values to status indicators.

3 Aspen Manufacturing Master Data Manager 17

 Feature Description
Identification An important aspect of a reference data system such as Aspen
Features mMDM is the ability to easily find data. To this end, Aspen mMDM
provides the following ways to identify and classify data:
• The business component items in Aspen mMDM support basic
identity features, such as name, identifier (integer), and
globally unique identifier (GUID). The query features provided
by Aspen mMDM make it easy to search based on these
criteria.
• Aspen mMDM supports display names, which allows the name
of an item to be changed when it is displayed to the user. This
facility allows alternate names based on the current locale
setting (language) and/or the current business process (such
as the user's role). So a Chinese lab technician might see a
different name for a material than an Italian production
scheduler.
• A primary feature of Aspen mMDM is support for aliases. This
helps to identify external data by mapping the name to and
from a standard. This also helps to map identities between two
external systems.
• Aspen mMDM automatically classifies components based on
the business component type. The query features in Aspen
mMDM support searching for items using their default mMDM
class. Items can also be searched based on the interfaces that
they support.
• In some cases, there may be requirements to customize how
data is classified in Aspen mMDM. Custom classifications are
supported by using the Class component. This provides a
configurable way to group component items of a similar type.
The Class component also supports an inheritance model which
allows items to be classified hierarchically.
Note: This is similar to the functionality delivered by the
Hierarchy component.
Organizational Aspen mMDM provides the following mechanisms to configure the
Features organization of data:
• The Hierarchy component can be used to organize component
items into a parent/child structure. The tree structure can be
programmatically traversed to locate the data. The nodes
within a hierarchy can be sorted by node name, display name,
or by a custom user-defined index.
• The Class component provides an inheritance model that is
hierarchical, which is similar to the Hierarchy component.
However, the Class component also supports extending an
item by adding class attributes.

18 3 Aspen Manufacturing Master Data Manager

 Feature Description
Extensibility Aspen mMDM provides a set of components sufficient for most
Features situations; however, sometimes it is necessary to extend the
system to support customizations. Aspen mMDM provides
numerous facilities to extend the base component model:
• The Class component can extend the existing components by
adding class attributes.
• The Calculation component allows behavior to be added to a
class by assigning formulas to a class attribute.
• The Generic component is similar to the Class component and
can be used for simple cases.
• Dynamic Data definitions can be associated with a component
item to reference external data, such as process variables. For
instance, you can extend a tank equipment to get the current
level value from Aspen InfoPlus.21. The tank level reading can
be acquired easily through the mMDM API without (directly)
using external APIs.
• SQL Query definitions can be defined to "look up" data values
from an external SQL data source. An SQL query definition can
be associated to a dynamic data definition (on a class
attribute) to cause a class attribute to return a value from a
column within a relational database table.
Web Services All data in the Aspen mMDM can be accessed and modified
through a standard web service. This web service also lets users
access dynamic data, calculations and status indicators for real-
time state. This feature is used by the Operations Navigator and
the AeBRS product to provide real-time access to this information.
The structure of the web service API is based on the S95 Part 4
specification.

Aspen mMDM Architecture

The Aspen mMDM architecture is based on an object-oriented component
design. Most, if not all, components are developed using object classes via
Microsoft's C# language and the .NET framework. Master data can be
accessed by client-side applications using a variety of protocols. For example,
Aspen mMDM provides the following data access models:
• Client-server Model - Data is accessed directly from relational database
via proprietary RDBMS protocols. This model supports both reading and
updating of data. To use this model, connect to a workspace where the
components have been configured to get data directly from an RDBMS.
You must have the mMDM assemblies installed on the client-side
computer.
• Publish-subscribe Model - Data is accessed from local XML files that
contain copies of the master mMDM data. This model only supports
reading of data. Typically, the XML files are obtained automatically by
configuring subscription services for each client. To use this model,
connect to a workspace where the components have been configured to
get data from the local XML files. You must have the mMDM assemblies
installed on the client-side computer.

3 Aspen Manufacturing Master Data Manager 19

 The following diagram illustrates the overall architecture of each deployment:

Aspen Manufacturing Master Data Manager (mMDM) Architecture

Note: For V9, the web-based mMDM Configuration Manager tool is now
disabled. The mMDM Editor can provide access to all the data management
features previously provided by mMDM Configuration Manager.

Aspen mMDM Editor

The Aspen mMDM Editor is a Microsoft Windows-based user interface
application that lets users add, modify, or delete data in an mMDM datastore.
It provides a rich environment for editing mMDM data by supporting advanced
features, such as drag-and-drop editing, cut-copy-and-paste functionality,
resizable panes, and visual feedback while editing.
Depending on how it has been installed, the Aspen mMDM Editor can be
accessed a variety of ways, such as from the Windows Start menu or from
the Aspen mMDM Bulk Load application. The Aspen mMDM Editor can also be
accessed from other AspenTech applications, such as Aspen Operations
Navigator, Aspen InfoPlus.21 Administrator, or Aspen IP.21 Process Browser
(formerly known as Web.21) Graphics Studio.

20 3 Aspen Manufacturing Master Data Manager

 Aspen mMDM Editor

Aspen mMDM Bulk Load

Aspen mMDM Bulk Load is a specialized tool that helps to load bulk amounts
of configuration data into an Aspen Manufacturing Master Data Manager
(mMDM) datastore, or to save data from an mMDM datastore for later use. If
you must add small or incremental amounts of data, we recommend using the
Aspen mMDM Editor instead. The data is first defined in a special Microsoft
Excel file known as a Bulk Load Excel file. Using an Excel file provides users
with a familiar user interface.
Aspen mMDM Bulk Load can help you perform other tasks, such as exporting
data from an existing mMDM database to an Excel or XML file. You can use
this file as a backup or use it to add or modify data that you would later
import back into an mMDM database.

3 Aspen Manufacturing Master Data Manager 21

 Aspen mMDM Bulk Load
Data in an Aspen mMDM Bulk Load Excel file can be saved to XML format.
This XML file is the same format used when exporting from an mMDM
datastore, so these files are interchangeable and provide considerable
flexibility when dealing with sets of mMDM data.
The Aspen mMDM Bulk Load program is comprised of two utilities: the mMDM
Bulk Load spreadsheet and the mMDM Bulk Load utility.

The mMDM Bulk Load Spreadsheet

Use the spreadsheet to:
• Manually type data to be imported into Aspen mMDM.
• Use the features of Excel to transfer bulk amounts of data from an
external source into the spreadsheet, and then adjust the data (if needed)
before the final import operation.
• Load previously exported XML files into the spreadsheet for editing.
• Save the spreadsheet data to an XML file which can later be reloaded (or
imported using the mMDM Bulk Load utility).

mMDM Bulk Load Utility

Using the mMDM Bulk Load utility, you can perform the following tasks:
• Import (bulk load) configuration data from one or more Bulk Load XML
files or Excel files into the mMDM datastore.
• Export configuration data from an mMDM datastore to an XML file or an
Excel file.
• View configuration data within an mMDM datastore.

22 3 Aspen Manufacturing Master Data Manager

 • Validate Aspen mMDM data.
• View pending changes that will occur when a user decides to commit
imported data to an mMDM datastore.
• View a session log of all the operations that have occurred.

3 Aspen Manufacturing Master Data Manager 23

24 3 Aspen Manufacturing Master Data Manager
4 Aspen Reporting
Framework

Aspen Reporting Framework™ is an application that serves as a data

integration platform for the aspenONE suite of products. In V9, focusing on
the Supply Chain space, Aspen Reporting Framework subscribes to the plans
and schedules published from other AspenTech applications. The data from
these varied applications are aligned using AspenTech’s master data model,
Aspen mMDM. These documents are stored in a data warehouse, and the data
is then converted to several business data marts that focus on inventory,
production, consumption, supply, and demand. These data marts feed an
OLAP cube that is hierarchically aggregated in the material and equipment
dimensions. The result is a set of KPIs and analytic reports that can be
visualized by third-party reporting systems, such as Microsoft Reporting
Services Microsoft Excel, Microsoft Excel Services, or Microsoft
PerformancePoint.

4 Aspen Reporting Framework 25