Aspen HYSYS Planning Model Update

•••••••••••••••••••••••••••••••••••••••••••••••••••••
Working with the Example File

© 2016 Aspen Technology, Inc. AspenTech®, aspenONE®, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks
of Aspen Technology, Inc. All rights reserved.11-3248-0413
 Planning Model Update Example File
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Introduction
The Planning Model Update example file can help get you started with using Aspen
HYSYS V9 to update PIMS planning submodels. In V9, we support two major
workflows for updating your planning submodel from engineering models: HYSYS Case
Study & ASW Front-End to refinery reactor models.
This document brings you through an example using the FCC reactor model. The Case
Study is standard HYSYS functionality, so is relevant to nearly all HYSYS unit
operations. The ASW Front-End is currently available only for the FCC, Hydrocracker,
and Naphtha Reformer reactor models.

Planning Model Update using the HYSYS Case Study

To update your planning model from your engineering model using standard HYSYS
functionality, AspenTech recommends you use the updated case study tool in V9. The
case study tool has a new mode called ‘Base & Shift’ that replaces the Planning
Support Utility in earlier versions of HYSYS. In this example file, the case study is set up
to generate the simulation data required to update the SCCU submodel in the PIMS
example file “Gulf Coast”. The contained ‘CaseStudyWorkflow.xslx’ file shows the case
study output linked to the PIMS SCCU submodel that is calculating shift vectors directly
from simulation data.

First, take a look at the format of the SCCU page in the ‘CaseStudyWorkflow.xslx’ file.
The top part of this page shows the vectors being used in the PIMS model. Notice that
they are being calculated from elsewhere in the spreadsheet. In the bottom of the
spreadsheet, there is a gray highlighted section commented out of the PIMS model
titled FCC Yields Data. This is where the vectors are calculated from simulation data.
The aim of this example file is to generate the simulation data to fill in this part of the
submodel file in order to update the PIMS submodel. We need the simulation model to
be able to vary the independent variables in the top section of this file and report the
dependent variables in the bottom section.

Next, open the HYSYS case ‘PlanningModelUpdate_FCC_Example.hsc’ in Aspen

HYSYS V9. In this file we have an FCC and a downstream fractionator. Notice a
couple of additional unit operations in this case used to get the appropriate data for
planning model update:
 The assay manipulator – The feed has been characterized using a HYSYS petroleum
assay on the stream. From the simulation environment, you can change the input
variables and recharacterize the assay. However, for this example case, we want to
isolate changes to the feed stream properties without affecting other properties. For
example, to get the required data for the PIMS SCCU model, we need to be able to
change feed density without changing feed VABP, contaminants, etc. In order to do
that, we use an assay manipulator. The assay manipulator can shift property curves
independently from one another in order to get the desired target bulk value.
Note: In other circumstances, you may want to re-characterize the complete assay to
account for effects density changes have on other properties. In those situations, you

© 2016 Aspen Technology, Inc. AspenTech®, aspenONE®, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks
of Aspen Technology, Inc. All rights reserved.11-3248-0413
 Planning Model Update Example File
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

can change the input data to the assay directly, and use that data in a case study.
However, it will require a re-characterization of the assay for every run of the case study,
which may slow the case study down a bit depending on how many cases you are
running.
 The adjust blocks & spreadsheet – Since this case is using a short cut distillation
column, the column cut points are set by ECP (effective cut point) values. The PIMS
SCCU model is controlled by the 90% cut points of the 3 major products off the column,
so these need to be set as independent variables. Since the short-cut column does not
allow this to be set directly, adjust blocks are used to control the ECP of the various
product cuts. They are summarized in the Column Cut Control spreadsheet.
Note: The spreadsheet summary also helps with eventual links to ASW, where there are
some known issues with adjust blocks.
 The component splitters for light ends – Depending on what data the PIMS SCCU model
needs from the simulation model, you may need to further separate out your products.
In this case, we separate out Mixed C3s, C4s, C5s from Fuel Gas & H2S to generate the
appropriate product yield calculations for the PIMS SCCU submodel.

Now, take a look at the case study in this case “PlanningModelUpdate_1”. First, look at
the Variable Selection tab. Here is where the variables are added to the case study. In
this case, we’ve added all variables needed by the PIMS SCCU model, and provided
the PIMS tags for the independent variables. In this case, for ease of linking results,
we’ve put the variables in the same order needed for the PIMS SCCU submodel. This
way, once the order has been set there will be no need to relink or copy/paste variables
every time.
Note: If variables change status from calculated to specified while the case study form is
visible, the variables will move from the dependent to independent and back. Therefore,
if you are making topology changes to the flowsheet, or putting the solver on hold, it is
recommended to close the case study form while changes are made to preserve the
order of variables. Otherwise, you may have to use the arrows to move variables back
to where you want them.

For more information on the new case study feature in V9, see the F1 help where there
is information about the new variable navigator and the new case study analysis types.

Move to the Setup tab, where you can see “Base & Shift” was selected as the case
study type. This is the mode designed specifically for updating planning models. Since
the PIMS SCCU model only has one base, only one base is designated here. For each
independent variable, the base value is set (the same as the base values in the PIMS
SCCU spreadsheet) as well as the shift value (the amount the variable value should
change when it is it’s turn to shift).

On the Results page, you can look at all of the case study results and Export them to
Excel for further analysis. In the ‘CaseStudyWorkflow.xslx’ file, you can see exported
results from the case study. These results have been linked to the PIMS SCCU sheet

© 2016 Aspen Technology, Inc. AspenTech®, aspenONE®, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks
of Aspen Technology, Inc. All rights reserved.11-3248-0413
 Planning Model Update Example File
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

in this file, so you can paste updated simulation data in the same format right into this
file and see the updates on the SCCU page. Of course, the best practice is always to
double check that formats remain the same between the exported simulation results
and the file you are pasting into.

On the Plots page, you can look at your results visually. If you had multiple bases in
this analysis, you would see multiple lines on this plot representing each base.

Planning Model Update using the ASW Reactor Front End

While the recommended Planning Model Update workflow is using Aspen HYSYS and
the case study tools, some may feel more comfortable using an Excel-based front end
to their reactor model for generating simulation data.

The contained ‘ASWFrontEnd_FCC_Example.xslm’ file gives an example of how you

can use the ASW Front End to refinery reactor models in Aspen HYSYS to interact with
your simulation case and generate data for planning submodel update from ASW.

When opening this file, you will be prompted to enable ASW. After enabling, the file will
load, and you will see the Aspen Simulation Workbook ribbon become available in
Excel. On this ribbon, you will be able to connect to the case, and make the HYSYS
case visible if you choose. This particular ASW file is connected to the same example
case as was used for the case study example.
To avoid issues with saving the file and writing to the AspenTech directory on your
machine, it may be best to copy the .xslm file and the .hsc file to another location and
run the models from there.

In this workbook, you will see a number of worksheets. First, the Simulation sheet. This
sheet was created automatically from the “Create ASW Front End” button in the FCC
reactor model subflowsheet in HYSYS. When the sheet is automatically generated, it
only contains the internal variables to the FCC model. The other variables representing
feed, column, and product stream data were added after initial generation of the file
using ASW functionality. This page shows all major variables to reflect what is going on
in the case.
When the ASW file is created from the reactor model, any independent variables are
made bold and blue to reflect standard HYSYS formatting. However, if after initial
generation of the file, variables change state from independent to dependent, this
formatting is not updated and must be manually updated if you wish to keep formatting
consistent. The variables will behave appropriately whether or not the formatting
reflects HYSYS standards.

Once you have attached the case, you can change variables in this sheet and review
model responses.

© 2016 Aspen Technology, Inc. AspenTech®, aspenONE®, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks
of Aspen Technology, Inc. All rights reserved.11-3248-0413
 Planning Model Update Example File
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

The other page in the workbook that is generated automatically from HYSYS upon initial
creation of the front end is the Factor Sets page. This page gives all calibration factors
in a single column. Factor sets are the calculated results from calibration runs. If you
have multiple factor sets that you use for your model and you want to be able to switch
from one to another, you can save them here, and use the “Make Active” button to
specify the new factors for the simulation model. Here, you can also average multiple
factor sets.

Notice that the PIMS_SCCU worksheet is the same as the SCCU worksheet in the case
study part of this example. In this ASW Front End, we are interacting with the same
model, and generating the same simulation results to update the same SCCU file, just
via ASW and not HYSYS directly.

In order to generate the simulation data for updating the SCCU model, an ASW case
study, called a Scenario Table, has been created. The scenario table is referencing the
same variables as the HYSYS case study. In order to use scenario tables in ASW, all
required independent and dependent variables need to be available in the Organizer.
Once a variable has been added to the ASW case, it will automatically show up in the
Organizer and can then be included in the scenario table.

Notice that the PIMS_SCCU simulation data is linked directly to this scenario table. If
we were to re-run the scenario table after making some changes to the underlying
HYSYS model, or with different input variables, we would see that the PIMS_SCCU
worksheet would be updated automatically with the new data reported in the scenario
table.

Please Note: The ASW Front End interacts only with the Simulation mode of the reactor
model. In V9, we’ve also added another ASW based tool, the ASW Dataset Editor. The
ASW Dataset Editor is similar to the ASW Front End, but interacts with the Calibration
mode of the reactor model. It can help you to link data in Excel directly to your
Calibration environment via ASW. For a look at this same example model in calibration
mode and with the ASW Dataset Editor connected, take a look at the “Calibration ASW
Dataset Editor” folder in the Refining examples directory.

About AspenTech
AspenTech is a leading supplier of software that optimizes process manufacturing—for energy,
chemicals, engineering and construction, and other industries that manufacture and produce products
from a chemical process. With integrated aspenONE® solutions, process manufacturers can implement
best practices for optimizing their engineering, manufacturing, and supply chain operations. As a result,
AspenTech customers are better able to increase capacity, improve margins, reduce costs, and become
more energy efficient. To see how the world’s leading process manufacturers rely on AspenTech to
achieve their operational excellence goals, visit www.aspentech.com.

© 2016 Aspen Technology, Inc. AspenTech®, aspenONE®, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks
of Aspen Technology, Inc. All rights reserved.11-3248-0413