2
TDM Timeline and Deployment Management tool Information contained in this document is indicative only. No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project. This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice. Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited. TDM is Alstom Grid’s Timeline and Deployment Management tool. It bridges the gap between the data modeling / display building subsystem and the e-terraplatform environments. It is intended as an optional tool for customers that desire an off-the-shelf solution for managing their power system models and display artifacts. The e-terraplatform applications require a model of the power system and corresponding displays for operators to operate reliably, securely and efficiently the electric power grid. e-terrasource is the modeling tool for maintaining the e-terraplatform power system models. The tools used for maintaining e-terraplatform displays include the FG Display Builder, iGRID Designer and e-terravision Authoring Tool. TDM functionally integrates the data engineering environment (e-terrasource and display authoring tools) and e-terraplatform. TDM serves two main functions: Integrated version control for the management of modeling and display artifacts. Under version control, models and displays, from any point in time can be retrieved for deployment, study, or auditing. Services for building, integrating, and deploying models and displays to e-terraplatform target environments, as well as maintaining history for auditing purpose, of deployment to target environments. HOW DOES TDM FIT INTO ALSTOM’S EMS SOLUTION? The Deployment Artifact Repository is the TDM version control system where the model and display artifacts are stored as TDM Components. The concepts of a component, component snapshot, and release are fundamental to TDM and understanding its functionality. Component – A component is a set of one or more modeling/display elements managed by TDM and stored in the TDM deployment artifact repository. Typically, an e-terraplatform configuration will have one component for the database models, and one or more components for the displays. Model components include the following files: CIM/XML export file from e-terrasource CSV-format hdbimport files for model databases Hdb model savecases (SCADAMDL, NETMODEL, GENMODEL, DTSMODEL, ALARM, OAGMODEL, …) Display components include the following files: e-terrabrowser display set and element set files (DSETs and ESETs) e-terrabrowser binary display files (.fgdisplay) iGRID display files (.grid) e-terravision displays (XAML) Image and configuration files to support the displays What is TDM? QA System Real-Time EMS e-terrasource and Display Authoring Tools TDM UI TDM Server TDM Deployment Artifact Repository TDM Application Database Planning/Study Environments Training Environments Data Engineering Subsystem TDM Subsystem e-terraplatform Environments

Timeline and Development Manager

Embed Size (px)

DESCRIPTION

Timeline and Development Manager

Citation preview

Page 1: Timeline and Development Manager

TDMTimeline and DeploymentManagement tool

Information contained in this document is indicative only. No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project. This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice. Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited.

TDM is Alstom Grid’s Timeline and Deployment Management tool. It bridges the gap between the data modeling / display building subsystem and the e-terraplatform environments. It is intended as an optional tool for customers that desire an off-the-shelf solution for managing their power system models and display artifacts.

The e-terraplatform applications require a model of the power system and corresponding displays for operators to operate reliably, securely and efficiently the electric power grid. e-terrasource is the modeling tool for maintaining the e-terraplatform power system models. The tools used for maintaining e-terraplatform displays include the FG Display Builder, iGRID Designer and e-terravision Authoring Tool.

TDM functionally integrates the data engineering environment (e-terrasource and display authoring tools) and e-terraplatform. TDM serves two main functions:

●● Integrated version control for the management of modeling and display artifacts. Under version control, models and displays, from any point in time can be retrieved for deployment, study, or auditing.

●● Services for building, integrating, and deploying models and displays to e-terraplatform target environments, as well as maintaining history for auditing purpose, of deployment to target environments.

HOW DOES TDM FIT INTO ALSTOM’S EMS SOLUTION?

The Deployment Artifact Repository is the TDM version control system where the model and display artifacts are stored as TDM Components. The concepts of a component, component snapshot, and release are fundamental to TDM and understanding its functionality.

Component – A component is a set of one or more modeling/display elements managed by TDM and stored in the TDM deployment artifact repository. Typically, an e-terraplatform configuration will have one component for the database models, and one or more components for the displays.

Model components include the following files:

●● CIM/XML export file from e-terrasource●● CSV-format hdbimport files for model databases●● Hdb model savecases (SCADAMDL, NETMODEL, GENMODEL, DTSMODEL, ALARM,

OAGMODEL, …)

Display components include the following files:

●● e-terrabrowser display set and element set files (DSETs and ESETs)●● e-terrabrowser binary display files (.fgdisplay)●● iGRID display files (.grid)●● e-terravision displays (XAML)●● Image and configuration files to support the displays

What is TDM?

QA System

Real-Time EMS

e-terrasource andDisplay Authoring Tools

TDM UI TDM Server

TDM DeploymentArtifact Repository

TDMApplication Database

Planning/StudyEnvironments

TrainingEnvironments

Data EngineeringSubsystem

TDMSubsystem

e-terraplatformEnvironments

Page 2: Timeline and Development Manager

Information contained in this document is indicative only. No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project. This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice. Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited.

For more information please contact:

Alstom Grid Inc.

10865 Willows Rd. NE, RedmondWA 98052-2502, USA

Tel: +1 (425) 822 6800e-mail: [email protected]

Visit us online: www.alstom.com

TDM

Snapshot – a component snapshot is a version of a component from a specific point in time. Once built, snapshots are frozen and cannot be modified. Snapshots can be combined into TDM releases for deployment.

Release – a release is a set of component snapshots which will be deployed together to an e-terraplatform environment. A Release includes either or both e-terraplatform model snapshots and display snapshots.

Typical Use Cases

INTEGRATING MULTIPLE e-terrasource PROJECTS AND DISPLAY MODIFICATIONSTDM can be used to help manage the activities of multiple concurrent data modeling and display building activities. It provides the facilities to integrate multiple data model updates (e-terrasource baseline models and projects) and display updates into a single TDM Release.

DEPLOYMENT TO TARGET ENVIRONMENTS

Specific model and display versions can be combined into a TDM Release. This Release can be deployed to multiple e-terraplatform target environments with the assurance that each environment is receiving a consistent set of models and displays. In a configuration with multiple e-terraplatform sites, QA environments, Testing environments, and possibly other environments, TDM provides the ability to reliably deploy a consistent Release and validate that it was deployed across all of the appropriate environments.

DEPLOYMENT AUDITING

The TDM deployment auditing function provides the ability to audit the deployments; allowing review of who (John Smith) deployed what (specific models and displays), where (which environments ) and when.

DEPLOYMENT OF A HISTORICAL MODEL TO A STUDY ENVIRONMENT

A historical model can be retrieved from TDM and deployed to a Study Network environment for the purpose of running the network applications against a model from a specific time in the past present and future). This functionality can be combined with the study network partial savecase retrieval function to combine operational data from one savecase with a model from the past, current and future.

DEPLOYMENT OF A MODEL FOR TESTING

A database modeler, using TDM within the e-terrasource environment, can easily deploy a model under development directly to a test environment without first committing to the TDM deployment artifact repository. This provides an easy mechanism for the modeler to iteratively test model changes that are in progress.

Component BuildProcess Snapshot Create

ReleaseDeployRelease

Targete-terraplatformEnvironments

ReleaseModel Snapshot

Display Snapshot