Skip to main content
Docs / Engineering Studies | Network Map Docs
Docs Menu

Engineering Studies

Prepare a network model, run a study, and review its tables, plots, and map layers.

Open Engineering Studies

Watch the Video: Engineering Studies: Getting Started (1:06)
  1. Open the Rosetta products menu above the map.
  2. Choose Engineering Studies.
  3. Start in Study Builder, or choose another tab for your task.

Engineering Studies requires Professional or Enterprise access. Other plans show a lock and Upgrade. Shared public viewer links do not provide this workspace. Choose Quick Start for the in-product checklist. Close the panel to return to the map.

Run engineering calculations on map-derived or user-built models. Review source data, assumptions, and missing values alongside each result.
Engineering Studies workspace in dark theme with the left menu groups Build and Organise, Studies and Planning, Run and Review, Validation and Handoffs, and System.
The Engineering Studies workspace. The left menu groups the tools by task.

Choose a Workspace

GroupTabUse
Build & OrganiseGrid Circuit BuilderCreate, import, validate, and publish a network model. See Grid Circuit Builder.
Projects & FlowsBuild a flow of typed steps, save revisions, run it, and review the status, result and log of each step. See Projects and Flows.
Study BuilderArrange scope, readiness, study, and output nodes for a classic study. See Engineering Study Types Reference.
Study TemplatesBrowse published templates and apply their setup.
Studies & PlanningSystem Feasibility and Connection StudyAssess a system or compare connection alternatives. See Connection Study and System Feasibility.
Power PlanningBuild a planning case with buses, loads, generators, storage and profiles. Run dispatch, unit commitment, expansion, adequacy, stochastic or hydro studies, and export a PLEXOS 12 package. The package is export only and is a compatibility candidate. A PLEXOS licence is not included. See Power Planning.
Project Scenario ModellingCompare project designs and commercial assumptions. See Project Modelling.
Legacy EstimatesUse the earlier commercial estimate workspace.
Run & ReviewSetup & RunChoose the scope, study, engine, and assumptions.
Model ReadinessCheck the model and read its diagnostics.
Study ResultsInspect status, methods, summary values, and result tables. See Engineering Study Results and Statuses.
Plot StudioBuild plots from available result data.
Result LayersAdd study output to the main map and control its visibility.
Study HistoryFind and reopen earlier runs.
Validation & HandoffsPowerFactory Model Builder and Exports & HandoffsPrepare model and result packages. See Network Model Builder and Engineering Exports and Handoffs.
Grid Code ReferenceReview cited grid-code clauses and values. See Read the Grid Code Reference.
SystemEngine StatusCheck service availability, engine availability, queues, and daily quotas.

Use Study Builder

Study Builder is the classic study setup canvas. It is separate from the executable graphs in Projects & Flows. The Run action submits the current study and engine selection. It does not run every study node as a sequence.

  1. Choose a preset under Study Templates. This replaces the current canvas.
  2. Click a component in Components, or drag it onto Study Flow.
  3. Click a node to select it.
  4. Drag the node to change its position.
  5. For a study node, set Study and Engine in the Inspector.
  6. Choose Setup & Run to complete the inputs.
  7. Choose Check to check readiness.
  8. Choose Run to submit the selected study.
Study Builder with the default study flow: Map Scope, Readiness Gate, Power Flow and Hosting Capacity nodes, then Map Layers, Result Tables and Export Package, with the Inspector on the right.
Study Builder shows the study steps as a flow, with a status for each step.
PresetSetup
Power FlowPower-flow study with map-layer and table outputs.
Hosting CapacityFeeder hosting-capacity study. See Hosting Capacity Screening.
ProtectionShort-circuit and protection-coordination study nodes. Select the study you want to run.
Planning ScenarioPlanning and cross-check study nodes.
Model QAModel-quality study with readiness checks and focused assets.

Components and Inspector

  • Scope contains Map Scope, Selected Assets, and Readiness Gate.
  • Study Nodes lists the study types available from the service.
  • Outputs contains Map Layers, Result Tables, Export Package, and History.
  • The Inspector shows Node, Purpose, Study, Engine, Scope, and Position.
  • Use the inspector links to open Setup & Run, Result Layers, Exports & Handoffs, or Study History, where available.
  • Choose Delete to remove the selected node. Locked nodes cannot be removed.
  • Choose Reset to restore the default canvas.

The canvas shows the number of nodes and edges. Its badges show scope, readiness, queue, and output state. Empty scope or Select assets means inputs are missing. Pending means readiness has not been checked. Needs review means the readiness result needs attention. Queue full means a run limit has been reached. Run first and Waiting for results mean an output is not ready. Use Study Results for the actual run status.

Use Study Templates

  1. Open Study Templates.
  2. Filter the Compliance Template Library by Country, Software, or Search.
  3. Choose Refresh to reload the catalog.
  4. Select a template in Catalog.
  5. Check its country, version, status, description, and supported study types.
  6. Read Source traceability, Operating-condition matrix, Global subplot definitions, and the listed sections.
  7. Choose Source to open the source document, when a source link exists.
  8. Choose Apply or Apply To Flow.
  9. Review the applied study, engine, and assumptions in Setup & Run before running.

Conditions and Subplots count template definitions, not completed calculations. A superseded template is an older version. Check the current source before using it. If no templates match, clear the filters. Applying a template updates the study setup and may replace its flow nodes. It does not start a study.

Apply a template to create a steady-state study setup. For tests that require dynamic simulation, prepare a vendor run package and review the returned results.

Read the Grid Code Reference

Grid Code Reference shows grid-code values and clause text from the primary regulator documents. Each item has its citation. Use it to look up cited requirements. You decide which requirements apply to your project.

Use the view to compare cited requirements and open their source documents.

  1. Under Validation & Handoffs, choose Grid Code Reference.
  2. Choose Clause map, DMAT tests or Grid-code comparison.
ViewWhat it shows
Clause mapChoose a Template. A summary line counts the clauses, the verified clauses, the linked DMAT tests and the automated checks. The view also lists the IDs of the automated checks and the runnable vendor tests. Each clause shows its clause number, its title, its status (Verified, Unverified or Draft - never decides pass/fail), the number of linked DMAT tests, a citation link to the source document and the quoted source text. Where a clause has cited values, the view lists them with their citation. The words automated check next to a value mean that the Power API compliance-evidence check can use this value. They are not a result. A template without such checks shows No automated pass/fail check for this template.
DMAT testsChoose a DMAT table from Table 2 to Table 17 of AEMO DMAT v3.0. The view shows the table title, the number of tests, the closest runnable vendor tests, a link to the source document, and one row for each test with its page number and test values, such as fault duration, fault type, SCR and X/R. It ends with the DMAT acceptance criteria (clause 2.4) and their citation.
Grid-code comparisonA table of topics by jurisdiction: Australia NEM (NER, AEMO), Western Australia WEM (ESM Rules, Western Power) and European Union (RfG 2016/631). Topics include voltage and reactive power regulation accuracy, rise and settling times, rate of change of frequency withstand, and overvoltage and undervoltage ride-through. A cell shows the cited values with the access standard they belong to, or Not compared in this release, or The instrument gives no number.

The closest runnable vendor tests use typical values. Set the values of the DMAT row in your study before a run counts as that DMAT test.

The Template list has six reference templates:

  • AEMO DMAT v3.0
  • AEMO Early Assessment Framework
  • Western Power model acceptance (WEM)
  • Inverter based loads (ERC0394 draft)
  • EU RfG connection
  • AEMO GPS (ERC0393)
Verified means the value was checked against the cited text. The listed automated checks run in the separate Power API compliance-evidence check. Draft rules, such as the ERC0394 draft, retain their draft status. Read the cited source document for each requirement.
Grid Code Reference, Clause map view, dark theme. The note at the top says the view is reference material only and gives no pass/fail result. The AEMO DMAT v3.0 template shows 23 clauses, 23 verified, 234 linked DMAT tests and 2 automated checks, and clauses with the Verified status, citation links and quoted text.
The Clause map view. Each clause shows its status, its citation and the quoted source text.
Grid Code Reference, DMAT tests view with Table 3 selected: balanced fault large disturbance test cases, 36 tests, the closest runnable vendor test fault_3ph, the source link and the first test rows with their page numbers and test values.
The DMAT tests view. Each row shows one AEMO DMAT v3.0 test with its page number.
Grid Code Reference, Grid-code comparison table with the topics voltage regulation accuracy, reactive power regulation accuracy and maximum rise time, and the columns Australia NEM, Western Australia WEM and European Union RfG. The EU cells show Not compared in this release.
The Grid-code comparison view. Each cell shows cited values or says that the topic is not compared.

Keep Project and Market Context Separate

Use Current Project to select shared project context, or leave the session exploratory. See Workspace Collaboration and Sharing for access and collaboration controls.

Market observations sent with Use in Study appear as Market reference context. Check their timestamp, cadence, revision, and freshness or partial-data status. These observations are Reference only. They do not supply topology, impedance, equipment ratings, or verified electrical inputs. Choose Return to Markets to reopen their source, or Remove to clear the reference.

New in Engineering Studies

  • Result charts follow the dark theme and draw in once when they open. See Charts in workflow runs.
  • Charts can use mixed axes, an oscillation fit, a wrapped power factor axis and a regression fit.
  • Projects and Flows has a flow canvas, Check flow, and a run view with the status, result and log of each step.
  • You can prepare a vendor run package for Siemens PSS/E, DIgSILENT PowerFactory, PSCAD or DSATools TSAT, import the returned results and benchmark two result sets. A PSS/E licence is not included. See Prepare a vendor run package.
  • Flow runs can make a PDF or HTML plot report. Run files can be downloaded from Artifacts and evidence.
  • Grid Code Reference shows cited grid-code values and clause text for comparison and review.
  • Power Planning is now available on Professional and Enterprise plans. Build a planning case, run planning studies and export a PLEXOS 12 package. The package is a compatibility candidate. A PLEXOS licence is not included.

Choose the Next Step

  1. Prepare inputs in Setup & Run.
  2. Check Model Readiness.
  3. Run the study and read Study Results.
  4. Review plots and map layers.
  5. Export the required evidence.

Review the Study Evidence

Keep the model basis, actual results and acceptance criteria together. See the reproducible study checklist, licensed-solver handoff guidance and report output choices.

Related Guides

Can't find what you need? Email support@networkmap.energy or call 1300 936 116. Sign in to Network Map.