What are the limitations of the current standard?
There is insufficient guidance to clearly indicate what is, and what is not, data of opportunity.
The current standard does not specify how "data of opportunity" should be specifically logged as such when it is missing.
Standards currently read:
Appropriate notification must be logged indicating that the job is continuing without this data source (similar to use of backup data above).
A warning that does not explicitly mention the phrase "data of opportunity" is not enough.
What changes are being proposed to the current standard?
The current language cited above should be changed to:
Appropriate notification must be logged indicating that the job is continuing without this data source (similar to use of backup data above). The logged notification must include the words "WARNING" and the missing data should explicity be identified using the phrase "data of opportunity."
How do these changes improve the current standard?
These changes will synchronize expectations between development and operations teams, remove ambiguity, and clarify production code dependencies.
What are potential impacts by changing this standard?
This change could potentially lead to warning messages that wrongly identify required data as data of opportunity, but these instances should be captured during EE2 testing.
How will this standard be enforced?
Existing standards on data of opportunity are already tested during routine EE2 failure mode testing. This proposal will clarify the existing enforcement.
Additional context or notes (optional)
No response
What are the limitations of the current standard?
There is insufficient guidance to clearly indicate what is, and what is not, data of opportunity.
The current standard does not specify how "data of opportunity" should be specifically logged as such when it is missing.
Standards currently read:
A warning that does not explicitly mention the phrase "data of opportunity" is not enough.
What changes are being proposed to the current standard?
The current language cited above should be changed to:
How do these changes improve the current standard?
These changes will synchronize expectations between development and operations teams, remove ambiguity, and clarify production code dependencies.
What are potential impacts by changing this standard?
This change could potentially lead to warning messages that wrongly identify required data as data of opportunity, but these instances should be captured during EE2 testing.
How will this standard be enforced?
Existing standards on data of opportunity are already tested during routine EE2 failure mode testing. This proposal will clarify the existing enforcement.
Additional context or notes (optional)
No response