We are having an open Community Call on Monday every two weeks.

The agenda will be published on the wiki: https://wiki.lfenergy.org/display/HOME/CoMPAS+Community+Calls

The notes of past community calls are also located in the #community-calls channel.

Sorry I will not be able to join ☹

De : CoMPAS@... <CoMPAS@...> De la part de Rob Tjalma
Envoyé : lundi 26 octobre 2020 11:55
À : 'CoMPAS@...' <CoMPAS@...>
Objet : EXT: Re: [CoMPAS] Open Community Call for CoMPAS next monday October 26th

A friendly reminder to the Open Community Call this afternoon (14.30 UTC)

See below for a short introduction about the call.

If you want to join, please let me know!

With kind regards,

Rob Tjalma

Hi all,

Next Monday, I would like to have a community call for CoMPAS.

I did sent a mail about it, but I didn’t get that much reactions.

The Community Call is meant for talking about stuff we did, stuff we have to do and other questions we can ask each other.

So who wants to join next Monday 14.30 UTC? 😊

We already have some Alliander colleagues that join, so don’t hesitate!

With kind regards,

Rob Tjalma

A friendly reminder to the Open Community Call this afternoon (14.30 UTC)

See below for a short introduction about the call.

If you want to join, please let me know!

With kind regards,

Rob Tjalma

Hi all,

Next Monday, I would like to have a community call for CoMPAS.

I did sent a mail about it, but I didn’t get that much reactions.

The Community Call is meant for talking about stuff we did, stuff we have to do and other questions we can ask each other.

So who wants to join next Monday 14.30 UTC? 😊

We already have some Alliander colleagues that join, so don’t hesitate!

With kind regards,

Rob Tjalma

Hi Naveen,

For the first meeting, 30 minutes will be fine!

Is that LFE Architecture meeting every Monday?

With kind regards,

Rob Tjalma

Hi Rob,

Thanks, I would be happy to join, however I think there’s an LFE Architecture meeting that starts at 15:00 UTC though.  Will this CoMPAS meeting be only 30 minutes long?

Cheers,

Naveen

Naveen Goswamy, P.Eng., M.A.Sc.

Science and Technology Advisor | Office of Energy Research and Development

Natural Resources Canada | Government of Canada

naveen.goswamy@... | Tel: +1-343-543-1179

Conseiller en science et technologie | Bureau de recherche et de développement énergétiques

Ressources naturelles Canada | Gouvernement du Canada

naveen.goswamy@... | Tél: +1-343-543-1179

Hi all,

Next Monday, I would like to have a community call for CoMPAS.

I did sent a mail about it, but I didn’t get that much reactions.

The Community Call is meant for talking about stuff we did, stuff we have to do and other questions we can ask each other.

So who wants to join next Monday 14.30 UTC? 😊

We already have some Alliander colleagues that join, so don’t hesitate!

With kind regards,

Rob Tjalma

Hi Rob,

Thanks, I would be happy to join, however I think there’s an LFE Architecture meeting that starts at 15:00 UTC though.  Will this CoMPAS meeting be only 30 minutes long?

Cheers,

Naveen

Naveen Goswamy, P.Eng., M.A.Sc.

Science and Technology Advisor | Office of Energy Research and Development

Natural Resources Canada | Government of Canada

naveen.goswamy@... | Tel: +1-343-543-1179

Conseiller en science et technologie | Bureau de recherche et de développement énergétiques

Ressources naturelles Canada | Gouvernement du Canada

naveen.goswamy@... | Tél: +1-343-543-1179

Hi all,

Next Monday, I would like to have a community call for CoMPAS.

I did sent a mail about it, but I didn’t get that much reactions.

The Community Call is meant for talking about stuff we did, stuff we have to do and other questions we can ask each other.

So who wants to join next Monday 14.30 UTC? 😊

We already have some Alliander colleagues that join, so don’t hesitate!

With kind regards,

Rob Tjalma

Hi all,

This morning, I was talking with Mohamed about a weekly Community Call for CoMPAS.

So, I want to take this opportunity to initiate an open Community Call every Monday, starting next week.

This way, we can keep the community involved to ask questions and hear us out.

We can tell what we did last week and what we’re going to do next week and so on.

I added the explanation in a Pull Request (needs to be merged): https://github.com/com-pas/compas-architecture/pull/36

I propose to have the meeting between 14:30 – 15:00 UTC, so people from Canada for example can also join.

I also made a #community-calls channel in the LF Energy Slack, this will be the place for the notes of previous meetings.

People can also get invitations for the meeting in this channel, I have to think about the technology to use (Zoom, Skype maybe?)

Suggestions are welcome! 😊

I hope many of you will join!

With kind regards,

Rob Tjalma

Re: SSD to SCD

My rapid WBS based on IEC 61850-6 10.2 System configurator

• The SSD describes the one-line diagram and the automation functions
• Essential – make corrections = CRUD operations on any item, or sets of items, preserving referential integrity
• Nice to have :  visualize this on a diagram  = requires extensions for graphics plus pan/zoom/layering features

• The SSD will describe the communications devices
• Essential – import ICD, CID, IID files of various versions and compile composite DataTypeTemplates for the client(s)
• Delete devices and all associated relationships
• Edit IP addresses
• Nice to have :  visualize this on a diagram  = requires pan/zoom/layering features

• The SCD describes the binding (mapping) between the required LNs per equipment/function
• Assign / unassign / reassign LNs from IEDs to equipment
• Per IED, show/ edit data set definitions
• Per IED, show / edit report control block definitions

• Export functions
• Export SCD in appropriate version for clients
• Nice-to-have: export subset per IED in appropriate version (i.e. ICD + goose subscription information)
• (IEC 61850-6 says this is an IED configurator function)

IEC 61850-6 Table G.2 – System configurator conformance statement  has three pages of function headings some of which are complex

And of course it is simpler if the SCT only needs to support one version of IEC 61850.

Hi Tom,

Welcome to the group! A part of the CoMPAS project will convert the CIM modelled substations into a single line diagram of 61850. This SLD can be the basis for apply custom scripts/templates to generate full SCD’s.

This is my current idea (up for debate):

Suggestions for the new edition:

Conversion of IEC CIM substations (e.g. CGMES EQ profile) to SCL SLD’s for automation purposes (it shows a paper process in 62361-102 figure 1).

Add globally unique functional identification to all LN’s (functional ID’s in IEC CIM are PowerSystemResource objects). It would be nice of de PSR id’s can match with relevant classes in IEC 61850.

It would be nice if signals from the IED’s can be related to the IEC CIM identification (where relevant).

Functional identification instead of the current asset identification in IEC 61850-7-3:2011;

It currently states: Master resource ID – unique identification of an asset or device;

If this is functional identification, the asset can be replaced with the same functional ID.

It would be nice if (IEC61850?) protection settings can be added to IEC CIM.

Hi everyone

I just joined the group

For those of you who don’t know me, I lead the task force that produced IEC 62361-102.

We plan to produce a new Edition 2 this year, so any comments and questions about Edition 1 are welcome.

IEC TS 62361-102 Edition 1 was published in 2018 and is based on input from IEC 61970-301 Ed 6 (CIM16) and IEC 61850-7-4 Ed 2.

Edition 2 will be updated with mappings for Distributed Energy Resources (DER) based on draft IEC 61850-7-420 Ed 2 and IEEE1547.

In addition, there are minor changes to be consistent with IEC 61970-301:2020 Ed 7 (CIM17), IEC 61850-7-4 Ed 2.1, plus add some Logical Nodes from IEC 61850-7-410 and other technical reports from the IEC 61850-90 series.

*Please consider the environment before printing this e-mail

Hi Tom,

Thanks for the interest and the WG10 update. We currently looking for the best technology fits for the CoMPAS project. The (e.g. database) technology will be checked against the high level requirements: https://com-pas.github.io/compas-architecture/HIGH_LEVEL_REQUIREMENTS.html

After the CoMPAS community selects the right technology, basic functionality can be build including continues integration etc. RTE is looking into resusing the existing entso-e tool.

We could consider reusing RiseClipse which already supports OCL.

“The first one on slide 7 is SSD to SCD which is a replication of existing commercial tools and could take several 10s of person-years.”

Do you know why this takes 10s of person years?

What exactly is being developed at present?

The CoMPAS Initial Roadmap has lots of topics,

The first one on slide 7 is SSD to SCD which is a replication of existing commercial tools and could take several 10s of person-years.

Some of the other bullet points are simpler, e.g. standalone SCL verification tools to complement schema validation.

On this topic, I can give you an update:

A new work item proposal is being prepared for discussion in IEC TC57 WG10 that will propose using OCL Object Constraint Language for machine readable rules to be used for SCL validation.

It is expected that there will be one document with recommendations on how a software tool should apply rules written in OCL

plus a series of documents / machine readable code components that describe the rules for different types of SCL (ICD, CID, SSD, SCD etc)

and different stages of the engineering process.

What exactly is being developed at present?

The CoMPAS Initial Roadmap has lots of topics,

The first one on slide 7 is SSD to SCD which is a replication of existing commercial tools and could take several 10s of person-years.

Some of the other bullet points are simpler, e.g. standalone SCL verification tools to complement schema validation.

On this topic, I can give you an update:

A new work item proposal is being prepared for discussion in IEC TC57 WG10 that will propose using OCL Object Constraint Language for machine readable rules to be used for SCL validation.

It is expected that there will be one document with recommendations on how a software tool should apply rules written in OCL

plus a series of documents / machine readable code components that describe the rules for different types of SCL (ICD, CID, SSD, SCD etc)

and different stages of the engineering process.

Hi Rob

On the RTE side, Mohamed Sylla is committed to the project. However, we are behind on another project that should have ended earlier because of the current health situation. That’s why he could not participate at 100% on CoMPAS.

In addition, we are in the process of creating a broader development team that will participate in our internal project, of which compas is a significant part.

That’s why, we hope to be fully available as soon as possible.

I understand that this current situation is not optimum for you, but don’t hesitate to interact already with Mohamed.

Regards,

Frédéric