Data publishing
- Last UpdatedAug 11, 2025
- 4 minute read
Support for remote databases
You can now publish data to remote SQL databases, in addition to local ones.
A Connect button has been added next to the Server field in the data publishing dialogs. The button becomes active when you enter a remote URL in the Server field. Click the button to connect to the remote database with the provided authentication credentials. This results in a success or error message, as with local databases.
Template support for database publishing
When publishing to a database, you can now select a template to publish just the categories of data you need, rather than the whole model.
When creating a database, click the arrow next to the Create button and select Create with template. The Select Template File dialog opens, where you can choose the template you want to use. You can then proceed with publishing as usual: the resulting database will contain only the tables corresponding to the data included in the template.
Database views
When you publish your model data to a database, a number of views are now automatically created. These views are modeled after various pages and tabs in the Plan and Network environments, letting you focus on the data you are most interested in.
The following table lists the available views. Note that all view names in the database include the prefix Plan. (for example, Plan.Exchanges), which has been omitted in the table for brevity.
|
AllPurchases |
AllSales |
CargoGroups |
|
DemandGroups |
Demands |
Exchanges |
|
GroupedCargoSupplies |
GroupedDemands |
GroupedExchanges |
|
GroupedSupplies |
GroupedTerminalInventories |
GroupedTerminalOperations |
|
GroupedTransportLinks |
NetworkConstraintsAndAlerts |
Nodes |
|
Periods |
Supplies |
SupplyGroups |
|
TerminalBlends |
TerminalInventories_PeriodResults |
TerminalInventoryGroups_PeriodResults |
|
TerminalOperationGroups |
TerminalOperations |
TransportLinkGroups |
|
TransportLinks |
Database error messages
Errors related to database publishing are now shown in non-technical, easier to understand language. You can still see the original error message by clicking the Details link.
Information on assets
The new Flowsheets section includes information on the assets in the topology of each plant in the model. Each flowsheet has a unique FlowsheetId value which is repeated in the Plants section, allowing you to match each topology with the corresponding plant.
For each flowsheet, an array of Elements lists every asset in the topology. Name, unique ID and type of the asset are reported, together with a list of InputSockets and OutputSockets. With this information you can recreate the full topology of a plant from the published data.
"Flowsheets": [
{
"FlowsheetId": "d98a37e6-a3aa-4631-b822-ac09604c3a91",
"Elements": [
{
"ElementId": "ca2e9606-e355-44d0-bd21-d574e628f18f",
"ElementName": "Naphtha Hydrotreater",
"Type": "Process Unit",
"InputSockets": [
{
"InputSocketId": "ba842d2e-44f8-4123-b658-a432d26444aa",
"InputSocketName": "NHT Feed",
"Index": 0
},
...
],
"OutputSockets": [
{
"OutputSocketId": "0a879adb-257c-41f0-8a76-2f563ea418ab",
"OutputSocketName": "HNap HT SG",
"Index": 0
},
...
]
},
...
]
},
...
]
Additional case details
The following data items have been added for each case: AnalyticId, AnalyticName, ParentCaseId, ParentCaseName and Path.
The values for these data items are null or empty if they don't apply to a specific case, for example because it is not part of an analytic. Path refers to the position of the case in the case hierarchy of the model.
These data items help you to locate each case in the model hierarchy. This is especially useful when publishing data to multiple files.
Modes
The new Modes array includes information on all the modes defined in the model.
"Modes": [
{
"ModeId": "e4474600-8ddd-4127-8867-021934259052",
"ModeName": "Default",
"ElementId": "78cf35d0-5332-4ab6-8af3-98b6ecf06d38",
"ElementName": "I221",
"Index": 0,
"Description": null,
"Active": null
},
...
]
Inventory properties
Inventory properties are now included in the published data. Each element of the Inventories array now includes a PropertyResults array with property values and units of measure:
"PropertyResults": [
{
"PropertyEnvironmentId": "f00ef106-14d5-475a-86aa-24ec9c2b594d",
"PropertyEnvironment": "Carbon Residue (MCRT)",
"Value": 5.934285936017967,
"ValueUom": "%"
},
...
]
Stream routing splitting rules
The new StreamRoutingSplittingRules section contains the information shown in the Splitting tab of the Stream Routing page in the Plan environment. Each array element contains information about one splitting rule.
"StreamRoutingSplittingRules": [
{
"SourceElementId": "6d50c409-72d7-4411-936e-78a8f6e6e3f8",
"SourceElementName": "LVGO Splitter",
"SourceModeId": "d4adbcbf-7045-4e35-8bbe-fc9e2d73ef34",
"SourceModeName": "Default",
...
"Availability": 100,
"AvailabilityUom": "%",
"Solution": 100,
"SolutionUom": "%",
"Marginal": null,
"MarginalUom": "M$/d/%"
},
...
]
Additional period information
Additional information on periods has been added to supplies, demands, transport links, terminal blends and calculations. Typical period information for these items now reads as follows (note that StartDate and EndDate were already included in previous releases, except for calculations):
{
...
"StartDate": "2018-03-01T00:00:00Z",
"StartPeriodId": "9f5f4cd0-5fd0-4933-91a3-1d85d5965548",
"StartPeriodName": "P 03 Mar 18",
"StartPeriodSortIndex": 1,
"EndDate": "2018-03-31T23:00:00Z",
"EndPeriodId": "3d30b5bb-180d-4f68-8b74-63da23113838",
"EndPeriodName": "P 04 Apr 18",
"EndPeriodSortIndex": 2,
...
}
Member count constraints for groups
Member count constraints for supply, demand, terminal inventory and terminal operation groups have been added as CountMax and CountMaxActive.