Overview of Capital

Systems Modeler

The Capital Systems application suite comprises Function Design in Capital Systems Modeler and Platform Design in Capital Systems Architect. Together they enable you to create proposals for downstream development and implementation flows. They enable rapid design iterations to validate and understand the technical impact of decisions on the overall platform level. In addition Capital Device Modeler facilitates the management of Interface Control Documents (ICDs) which feed into the functional designs and contain device specification information and enable the auto-routing of signals to ports.

Capital Systems Modeler provides almost instantaneous feedback on design decisions allowing choices on device placement and implementation to be quickly modelled and verified or reversed and retested depending on their forecast metrics, in order to meet both technical and financial design requirements.

Once a platform design is proven it can be extracted and exported downstream for use in other products such as the Autosar Development flow, the detailed network flow or within Capital so that, for example, the data can be used to generate logical schematics or network designs.

Capital Systems Modeler is designed to facilitate functional implementation planning and foster collaboration between domain experts. Capital Systems Modeler designs differ from logical and electrical designs in that, instead of devices connected by pins and electrical or logic signals there are functions and function blocks connected via ports, signals or highways to other functions and blocks. These functions and blocks could comprise such objects as sensors, actuators or an ECU (electronic control unit) that controls an electrical subsystem within a vehicle design.

In the following example, shown in Figure 1, sensor_01 receives input from the area that it is monitoring. It transmits a signal through to the software mounted within logic_ function_01 and ECU_101, which in turn relay it to actuator_01 which can then initiate the appropriate action. In some industries this is termed an “event chain”.

Figure 1: Capital Systems Modeler Event Chain

At this point, within the event chain, the signals are only functional signals. It has not yet been determined whether they will be one of the following:

• electrical signals

• software signals

• network signals

• radio frequency transmitted wireless signals

This is because at the functional level or implementation the event is shown as independent of features or functionality. It is possible that the design engineer is, at yet, undecided on how the feature will be implemented. Capital Systems Modeler allows the design engineer to create a concept that will be used to envisage the functionality. It enables an understanding of what the model could be used for and by using different style sets allows the engineer to attach different attributes and properties.

Capital Systems Modeler is the application that is used to create functional designs and diagrams.

Accessing Capital Systems Modeler

You access Capital Systems Modeler by running the CapitalSystemsModeler.exe file in the bin directory of your installation.

Alternatively, you can run the CapitalSystemsArchitect.exe file; this allows you to access Capital Systems Architect designs, Capital Systems Modeler designs and Capital Logic Designer designs from the same application window.

User Access Rights in Capital Systems Modeler

The access that you have to the various aspects of Capital Systems Modeler is controlled by the Capital Access Manager application. See your Capital administrator and /or the Capital Access Manager help system for more information on the access controls and levels available.

Parent Topic:

Overview

Capital Systems Modeler User Guide, 2512.2606

Unpublished work. © 2026 Siemens