Attaching reference to PDD via programmatically built monitoring report

[gautamp8]

Context

Usually external monitoring data is sent by an installer or sensor with a new DID. Technically, ref variable becomes the DID of the new device.

In metered energy policy, there is a need to prepare monitoring report schema programmatically by stitching daily usage data(sent by sensors) with PDD data originally entered by project proponent.

There's two approaches provided in the policy for creating a monitoring report.

1) Using Add Report button and filling the form manually

In this case a ref unique to the project gets attached to it automatically(notice the UUID row ).

2) External data comes in, goes via a calculate block to generate a monitoring report. In this case, ref is automatically added as DID. This MR doesn't have reference to existing project.

I need to figure out a way to keep the programmatically generated monitoring report via option 2 to retain original PDD reference.

Attachments

• Policy file, recording file and a vc_generator.py script are within the zip Archive.zip

Python script needs the path to .config file downloaded. It's not possible to send nested schema VCs with MRV sender component, hence script is needed.

[anvabr]

Thank you for capturing this in the ticket @gautamp8. We discussed this internally at length. It appears that the current structure is as follows:

• Project (with UUID)
• Monitoring Report (MR) which is manually generated (with unique DID)
• Daily Report (DR) coming from the outside
• MR generated on the basis of DR

This is unusual and somewhat confusing for the following reasons:

• DR is linked to the MR, perhaps it would've been better to link it to the Project?
• For each MR a new DID is generated, perhaps a DID needs to be generated for the Project (and download config), and for the MR a UUID?

At the moment the structure is as follows:

• Project
  • MR 1
  • MR 2
    • DR 1
    • MR 3
    • DR 2
    • MR 4
  • MR 5

Perhaps the following is more appropriate:

• Project
  • MR 1
  • MR 2
  • DR 1
  • MR 3
  • DR 2
  • MR 4
  • MR 5

Please let me know if this makes sense to you. If what we are suggesting is good for you then the following would be our suggestion:

• Move the Download config button from MR into the Project
• change Project UUID to DID

This will sort out the issue for linking manual and automatic MRs.