Skip to content

Commit f20cbf6

Browse files
authored
Merge pull request #8 from com-pas/added_README
Improved readme.md
2 parents 32056ed + 78fe764 commit f20cbf6

File tree

4 files changed

+113
-3
lines changed

4 files changed

+113
-3
lines changed

.reuse/dep5

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@ Files: .mvn/wrapper/*
1111
Copyright: 2023 Alliander N.V.
1212
License: Apache-2.0
1313

14-
Files: doc/images/*
14+
Files: docs/images/*
1515
Copyright: 2023 Alliander N.V.
1616
License: Apache-2.0
1717

18-
Files: doc/drawio/*
18+
Files: docs/drawio/*
1919
Copyright: 2023 Alliander N.V.
2020
License: Apache-2.0

README.md

Lines changed: 111 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,117 @@ SPDX-License-Identifier: Apache-2.0
1111
[![Slack](https://raw.githubusercontent.com/com-pas/compas-architecture/master/public/LFEnergy-slack.svg)](http://lfenergy.slack.com/)
1212

1313
# CoMPAS Sitipe-service
14-
The CoMPAS Sitipe-Service Allows users to integrate Siemens Sitipe within the CoMPAS environment.
14+
Siemens SITIPE for CoMPAS
15+
16+
This repository contains an CoMPAS extension in order to integrate with Siemens SITIPE.
17+
It is open source software to interact with Siemens SITIPE.
18+
19+
Siemens SITIPE allows users to import an SCD file in order to work as much vendor independent as possible.
20+
In order to make that work, the SCD file should contain the required Siemens SITPE extensions.
21+
In order to get these 61850 private extensions.
22+
The SITIPE database is used to have a single source of true for all templates used (IEC61850 and Siemens specific settings).
23+
24+
The architecture looks like this:
25+
![Sitipe architecture](./docs/images/sitipe_architecture.png)
26+
27+
The output of CoMPAS (the SCD file) can be loaded into the SITIPE using the Excel SCD import macro inside de SCF file. Please note that their could be SCD import restrictions for SITIPE. This is outside the control of the CoMPAS project.
28+
29+
30+
The contract framework and versions are currently a deployment setting. The SITIPE back-end consist of 3 seperate components.
31+
32+
#### Sitipe-Service-app
33+
34+
Interaction with the front-end application.
35+
The front-end app can choose between XML or Json output.
36+
37+
38+
#### Sitipe-Service-Service
39+
40+
Business logic to convert the API calls to SQL logic.
41+
42+
43+
#### Sitipe-Service repository
44+
45+
Making the connection to the SITIPE database.
46+
47+
![Sitipe Service](./docs/images/sitipe_service.png)
48+
49+
Example XML output of the Sitipe-Service app
50+
51+
```xml
52+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
53+
<ns3:BayTypicalResponse xmlns:compas-commons="https://www.lfenergy.org/compas/commons/v1"
54+
xmlns:ns3="https://www.lfenergy.org/compas/SitipeService/v1">
55+
<ns3:BayTypical>
56+
<ns3:Id>1</ns3:Id>
57+
<ns3:AccessId>3BD3CA17-8136-4F72-A381-9C047FF1F3A8</ns3:AccessId>
58+
<ns3:Name>E01</ns3:Name>
59+
<ns3:Version>1</ns3:Version>
60+
<ns3:Description></ns3:Description>
61+
<ns3:Released>1</ns3:Released>
62+
<ns3:LockedBy></ns3:LockedBy>
63+
<ns3:LockedOn>0</ns3:LockedOn>
64+
<ns3:ModifiedOn>0</ns3:ModifiedOn>
65+
<ns3:SmrFile>SMR_4_BT_PAS-SS_IID_DM - enhanced Vienna.smr</ns3:SmrFile>
66+
<ns3:ContentVersion>4.0</ns3:ContentVersion>
67+
<ns3:ReferenceAccessId>00000000-0000-0000-0000-000000000000</ns3:ReferenceAccessId>
68+
</ns3:BayTypical>
69+
<ns3:BayTypical>
70+
<ns3:Id>2</ns3:Id>
71+
<ns3:AccessId>3A80B5B7-B42E-41DD-BD4C-CD4AE454017C</ns3:AccessId>
72+
<ns3:Name>E02</ns3:Name>
73+
<ns3:Version>1</ns3:Version>
74+
<ns3:Description></ns3:Description>
75+
<ns3:Released>1</ns3:Released>
76+
<ns3:LockedBy></ns3:LockedBy>
77+
<ns3:LockedOn>0</ns3:LockedOn>
78+
<ns3:ModifiedOn>0</ns3:ModifiedOn>
79+
<ns3:SmrFile>SMR_4_BT_PAS-SS_IID_DM - enhanced Vienna.smr</ns3:SmrFile>
80+
<ns3:ContentVersion>4.0</ns3:ContentVersion>
81+
<ns3:ReferenceAccessId>00000000-0000-0000-0000-000000000000</ns3:ReferenceAccessId>
82+
</ns3:BayTypical>
83+
</ns3:BayTypicalResponse>
84+
```
85+
86+
Example Json output:
87+
88+
```json
89+
[
90+
{
91+
"id": 1,
92+
"accessId": "3BD3CA17-8136-4F72-A381-9C047FF1F3A8",
93+
"name": "E01",
94+
"version": "1",
95+
"description": "",
96+
"released": 1,
97+
"lockedBy": "",
98+
"lockedOn": 0,
99+
"modifiedOn": 0,
100+
"smrFile": "SMR_4_BT_PAS-SS_IID_DM - enhanced Vienna.smr",
101+
"contentVersion": "4.0",
102+
"referenceAccessId": "00000000-0000-0000-0000-000000000000"
103+
},
104+
{
105+
"id": 2,
106+
"accessId": "3A80B5B7-B42E-41DD-BD4C-CD4AE454017C",
107+
"name": "E02",
108+
"version": "1",
109+
"description": "",
110+
"released": 1,
111+
"lockedBy": "",
112+
"lockedOn": 0,
113+
"modifiedOn": 0,
114+
"smrFile": "SMR_4_BT_PAS-SS_IID_DM - enhanced Vienna.smr",
115+
"contentVersion": "4.0",
116+
"referenceAccessId": "00000000-0000-0000-0000-000000000000"
117+
}
118+
]
119+
```
120+
121+
Please note; This is not an official Siemens (supported) project.
122+
Check the license to see what is possible with the code.
123+
Siemens is registered trademark.
124+
The database contains example data from Siemens.
15125

16126
## Development
17127

docs/images/sitipe_architecture.png

51.2 KB
Loading

docs/images/sitipe_service.png

37.1 KB
Loading

0 commit comments

Comments
 (0)