Scribd
Upload
2 views4 pages

SIMATIC Machine Monitor Overview

The document outlines the configuration management for the SIMATIC Machine Monitor, detailing the automated CI/CD pipeline processes for building and deploying various project components. It describes the repository structure, including the main components such as the frontend, communication layer, and backend services, all of which are stored and managed in Siemens' Captain Artifactory. Additionally, it mentions the deployment logic for the Machine Monitor application across different environments and tenants.

Uploaded by

Darko Stalevski
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views4 pages

SIMATIC Machine Monitor Overview

The document outlines the configuration management for the SIMATIC Machine Monitor, detailing the automated CI/CD pipeline processes for building and deploying various project components. It describes the repository structure, including the main components such as the frontend, communication layer, and backend services, all of which are stored and managed in Siemens' Captain Artifactory. Additionally, it mentions the deployment logic for the Machine Monitor application across different environments and tenants.

Uploaded by

Darko Stalevski
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

SIMATIC Machine Monitor DI FA PMA DMI

Machine Monitor Configuration Management

General concept
The application bundle files are available only by using [Link] CI/CD pipeline operations.
Any RC or release version is reproducible without using any of the developer PCs.

All code stored in [Link] repositories. All individual project’s build processes are done in
[Link] CI/CD Pipelines in an automated way. All project builds are stored in Siemens
Captain Artifactory. The assemble of the individual project builds are done also in CI/CD Pipelines.

Repositories
The structure of the Machine Monitor repository and the projects are the following:

- SIMAPPS Machine Monitor (Group)

o V2 (Group)
 smm-frontend-v2
 Hosts the code of the UI and the build configuration for Edge and
MindSphere.
 Artifacts deployment goes to Captain Repository.
 smm-communication-layer
 Hosts the self-written part of the communication layer for Edge and
MindSphere. The builds are done in pipelines, and the project assembles the
complete layer with all the required services for both Edge and MindSphere.
 Artifacts deployment goes to Captain Repository.
 docker-images
 Creates and hosts the docker images that are used for building the Edge
application
 Hosts the main Edge application configuration file
 The application can be downloaded from the Host PC
 smm-docs
 OpenAPI documentation for the backend services
 smm-maintenance-data-service
 Hosts the code for the core Java backend and the internal routing
configuration
 Creates builds for both MindSphere and Edge versions
 Artifacts deployment goes to Captain Repository
 smm-calculation-service
 Hosts the code for the core NodeJs application
 Creates builds for both MindSphere and Edge versions
 Artifacts deployment goes to Captain Repository

o smm-deployment

SIMATIC Machine Monitor for MindSphere and Industrial Edge


Copyright © Siemens AG, 2005 - 2023 All Rights Reserved
 Contains the logic for assembling the Machine Monitor MindSphere
application of the nightly, the RC and the release version for the following
tenants: smminteg, pmaacctd and simapps.
 The Application can be downloaded as Pipeline Artifacts.
Structure of Repository Pipelines
Detailed view of assembling of communication layer for Edge and MindSphere

Figure 1.0
Signatures:

Darko Stalevski Tibor Kocsis


Project manager Architect / Software developer
ADV D EU HU OPS 2 4 ADV D EU HU OPS 2 4

You might also like