External interface requirements

From SIMSTADT
Jump to: navigation, search

Contents

[edit] User interfaces

How to

Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.

[edit] Hardware interfaces

How to

Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.

[edit] Software interfaces

How to

Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.

[edit] STANET®

[edit] Overview

STANET® is a program package for stationary and dynamic calculation of utility networks etc.

Fischer-Uhrig
Ingenieurbuero Fischer-Uhrig
Wuerttembergallee 27
D-14052 Berlin
Germany
Phone: +49-(0)30-30099390
Fax: +49-(0)30-30824212
Email: info@stafu.de
Homepage: http://www.stafu.de

Dipl.-Ing. Dieter Büttner Tel.  : 03494- 40 15 51 Fax  : 03494- 40 15 50 Funk  : 0177 796 44 06 Internet: www.ib-buettner.de Email  : d-buettner@t-online.de

Dipl.-Ing. Stefan Wörthmüller Email  : info@stafu.de

[edit] Potential uses in SimStadt environment

[edit] Simulation of heat distribution networks

verification of hydraulic feasibility, dimensioning, calculation for pumping electricity and heat losses

2 Calculation modes:

  • Stationary (sizing calculation during design winter/summer conditions)
  • Tagessimulation -> quasi-stationary simulation, with time step of 1/4, 1/2, 1 hour

[edit] Typical workflow

  1. create a hydraulic model (import network data from other software or draw it manually) -> Gas, water, heat, waste water or steam net.
  2. test calculations to get a model that calculates
  3. calibration of the hydraulic model with measured values or experienced data
  4. simulation of a hydraulic situation -> 3 Modes: stationär, Taggessimulation (=semi-dynamic simulation), Durchmesseroptimierung
  5. analysis of the results

[edit] Objects and parameters

Nodes

  • Properties: ID, Geo-coordinates (x,y,z)
  • network connection = 4 nodes (supply pipe connection / supply consumer point / return consumer point / return pipe connection)

Pipes

  • Properties: Start node, end node, length, inner diameter (can be calculated with STANET, given a max water flow speed value), type of pipe (plastic, metal, insulation... double pipe are not accepted)

Consumer (Abnehmer)

  • Properties: Max. power, Consumer profile (in case of Tagessimulation)

Supply system (Einspeisewerk)

  • Properties: ?

Heat exchanger

  • Properties: ?


[edit] Working with the Graphical User Interface

Stanet has 3 User Interface: 1. table, 2. graphic presentation, 3. menu bar iterative calculation with a approximation method Import and export with the menu bar and standardised tables

[edit] Batch mode/command lines

It is possible to call Stanet with command lines in Batch mode. For more details: File:STANET Handbuch Part Kommandozeilen.pdf

[edit] Interfaces

[edit] File formats for import and export

SDF/CDV, ArcView, SWMM 5, Smallword, ODBC, txt, ASCII-Text, Shape (ESRI), MID-MIF (Mapinfo), DXF (AutoCAD)

Import/export text file: STANET SDF/CSV For more details: File:STANET Handbuch Part Stanet SDF-CSV.pdf

[edit] (Direct) interfaces to Databases, GIS, etc.

[edit] Other interfaces

Besides file interfaces and running in batch mode (see above), no interfaces to other processes are built into Stanet. However, web services have been implemented using batch mode calls to Stanet for backend computations.

[edit] Calculation and solver methods/algorithms

[edit] Installation requirements

standard Personal Computer

[edit] Extensibility

It is necessary to export standardized export files from other programms. Than it is possible to import them into Stanet. The concrete structure of the export file has to be discussed in a team meeting.


[edit] INSEL®

[edit] Overview

INSEL® is a graphical programming language for the simulation of renewable energy systems

[edit] Potential uses in SimStadt environment

[edit] Weather and sky

Insel disposes of a complete library of Meteorological blocks, from wordlwide climate data, to sky or ground models as well as radiation calculations for every surface orientations. It allows monthly mean values or hourly weather data for the building simulation requirements to pre-calculate.

[edit] Photovoltaic installations

Phovoltaic installations represent the initial application of the Software Insel. Here, Insel disposed of a rich manufactured component library of photovoltaic pannels as well as surrounded electrical systems(inverters, storages etc...)

[edit] Thermal systems

Insel disposes also of several thermal system models: Solar collectors, water tanks, heat exchangers, air ducts and absorption cooling machine.

[edit] Building components

Insel disposes since recently of a building library, composed of dynamical models of each building component (Outside/inside walls, windows, basement) and of calculation algorithms (zone temperature, shape factors, long wave heat exchange).

[edit] Typical workflow

[edit] Working with the Graphical User Interface

[edit] Batch mode

[edit] Interfaces

[edit] File formats for import and export

[edit] (Direct) interfaces to Databases, GIS, etc.

[edit] Other interfaces

E.g.:

  • the system or specific components of it can be reused by other applications by starting a new process, calling functions or as plugin
  • other applications or their components are called from within the system
  • system offers pipes or sockets for streaming data
  • system offers web services

[edit] Calculation and solver methods/algorithms

[edit] Installation requirements

[edit] Extensibility

How can the systems functionality be adapted or enhanced (configuration, hard coding, plugins, ...)

[edit] Communications interfaces

How to

Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox