Manhole level monitoring - object definitions.

[workgreg]

Registration Information

1. Choose the type of registration:

• [x] Object
• [ ] Reusable Resource

2. Choose the Object Class:

• [ ] 3rd party Standards or Alliances
• [x] Private companies
• [ ] Private individuals (not allowed Reusable Resources registration)

3. Confirm Software License

• [x] Tick this box confirming that your submission has included a software license.

Concept	Description
Number of Object(s) or Reusable Resource(s) to register	7 new objects
Name of SDO, Company or individual	South East Water Corporation
Object Name (as defined in the .xml file)	Water Level Readings
Short Object description, to be used in the public registry (max 134 characters)	Periodic water level measurements.
Object Name (as defined in the .xml file)	Tilt Readings
Short Object description, to be used in the public registry (max 134 characters)	Periodic tilt measurements.
Object Name (as defined in the .xml file)	Water Level Alarm
Short Object description, to be used in the public registry (max 134 characters)	This alarm is raised when the water level in a tank, manhole, etc. exceeds the specified threshold.
Object Name (as defined in the .xml file)	Trend Readings
Short Object description, to be used in the public registry (max 134 characters)	Periodic trend (rate of change) measurements.
Object Name (as defined in the .xml file)	Tilt Alarm
Short Object description, to be used in the public registry (max 134 characters)	This alarm is raised when the tilt/inclination of the device exceeds the specified threshold.
Object Name (as defined in the .xml file)	Trend Alarm
Short Object description, to be used in the public registry (max 134 characters)	This alarm is raised when the trend (rate of change) of a sensor input exceeds a specified threshold.
Object Name (as defined in the .xml file)	Manhole
Short Object description, to be used in the public registry (max 134 characters)	This object provides site commissioning configuration for devices operating in a sewer manhole.

[gocadimic]

@workgreg,

The DDF.xml file was updated with new Object 10487-10493 placeholders and customized as requested. All changes have been made to the new branch sew-reserve-placeholder. Submitting the new object should be continued there.

A fully qualified Obj-10487.xml, Obj-10488.xml, Obj-10489.xml, Obj-10490.xml, Obj-10491.xml, Obj-10492.xml, Obj-10493.xml files should be submitted to the given branch for version 1.0. Please make sure that the content of the DDF.xml matches the request in https://github.com/OpenMobileAlliance/lwm2m-registry/issues/761.

Once the new objects are submitted, the same objects Obj-10487.xml....Obj-10493.xml files have to be submitted to the version_history folder, with the same content as in DDF.xml, named 10487-1_0.xml....10493-1_0.xm The final step would be creating a PR against the prod branch.

For more explanation, see README.md.

[mkgillmore]

@workgreg Do you intend to address issue #752 with this issue and PR?

[workgreg]

@workgreg Do you intend to address issue #752 with this issue and PR?

Happy to address #752 in the PR for this issue.

[workgreg]

I've identified a requirement for one more object which I'd like to add as part of this issue.

Concept	Description
Number of Object(s) or Reusable Resource(s) to register	1
Name of SDO, Company or individual	South East Water Corporation
Object Name (as defined in the .xml file)	Fault Code
Short Object description, to be used in the public registry (max 134 characters)	This object reports device specific fault codes

[mkgillmore]

ok, let me know if you need any help

[workgreg]

ok, let me know if you need any help

I've already sent a pull request for this issue. Should I create a new issue for the additional object? If not, will you reserve a placeholder object ID or should I choose an object ID?

[mkgillmore]

Your call if you would like to create a new issue. It would be easier for me if you created an issue for the new object.

From: workgreg @.> Sent: Thursday, June 27, 2024 8:28 PM To: OpenMobileAlliance/lwm2m-registry @.> Cc: Gillmore, Matthew @.>; Comment @.> Subject: [EXTERNAL] Re: [OpenMobileAlliance/lwm2m-registry] Manhole level monitoring - object definitions. (Issue #761)

ok, let me know if you need any help I've already sent a pull request for this issue. Should I create a new issue for the additional object? If not, will you reserve a placeholder object ID or should I choose an object ID? —Reply to this ZjQcmQRYFpfptBannerStart Warning! This email comes from outside the company. This message came from outside of Itron, if you suspect it to be spam, please delete it or if you suspect a phishing attempt, please report it using the Phish Alert Report button. Be careful and think before you click. ZjQcmQRYFpfptBannerEnd

ok, let me know if you need any help

I've already sent a pull request for this issue. Should I create a new issue for the additional object? If not, will you reserve a placeholder object ID or should I choose an object ID?

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/OpenMobileAlliance/lwm2m-registry/issues/761*issuecomment-2195873468__;Iw!!F7jv3iA!3bL50zozwcJz9V5F9t9fXhDUqH5Pj--df2gfrNBZEyHCS6iUPsbAZ9zXkAGJnfgIUm8PSMdvRRTjgP6XLn7fTfmExRRvXQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AJSSA5UC27ECVFPAGIB7HVDZJSUY5AVCNFSM6AAAAABIGRKQEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVHA3TGNBWHA__;!!F7jv3iA!3bL50zozwcJz9V5F9t9fXhDUqH5Pj--df2gfrNBZEyHCS6iUPsbAZ9zXkAGJnfgIUm8PSMdvRRTjgP6XLn7fTfmY6Xnthg$. You are receiving this because you commented.Message ID: @.**@.>>

[workgreg]

I've created a new issue - #770

[mkgillmore]

Addressed with PR #768