diff --git a/qualities/J/_posts/2022-12-28-jitter.md b/qualities/J/_posts/2022-12-28-jitter.md
index e41ff8d..9c8534d 100644
--- a/qualities/J/_posts/2022-12-28-jitter.md
+++ b/qualities/J/_posts/2022-12-28-jitter.md
@@ -1,7 +1,7 @@
 ---
 title: Jitter
-tags: efficient
-related: performance-efficiency, latency
+tags: efficient operable
+related: performance-efficiency, latency, predictability
 permalink: /qualities/jitter
 ---
 
diff --git a/requirements/I/_posts/2023-12-05-installability-new-feature b/requirements/I/_posts/2023-12-05-installability-new-feature.md
similarity index 100%
rename from requirements/I/_posts/2023-12-05-installability-new-feature
rename to requirements/I/_posts/2023-12-05-installability-new-feature.md
diff --git a/requirements/J/_posts/2023-12-05-minimize-jitter-in-data-streaming.md b/requirements/J/_posts/2023-12-05-minimize-jitter-in-data-streaming.md
new file mode 100644
index 0000000..37cce4e
--- /dev/null
+++ b/requirements/J/_posts/2023-12-05-minimize-jitter-in-data-streaming.md
@@ -0,0 +1,26 @@
+---
+title: "Minimize jitter in real-time data streaming"
+tags: reliable operable
+related: jitter, predictability, latency
+permalink: /requirements/minimize-jitter
+---
+
+<div class="quality-requirement" markdown="1">
+
+### Overall goal: Reduce and control [jitter](/qualities/jitter) in the real-time streaming of data.
+
+
+**Stimulus**: Continuous transmission of real-time data (from sensors) over a network,.
+
+**Environment**: Operational phase under standard network conditions.
+
+**Response**: The system handles variations in delay of data packet delivery.
+
+**Response Measure**:
+
+* The variance in delay between data packets (jitter) should not exceed 5 milliseconds for 95% of the transmitted packets
+* In instances where jitter exceeds this threshold, the system should employ buffering mechanisms to smooth the data flow, ensuring that the effective jitter experienced by the end-user remains below 7 milliseconds
+* The system must detect and log instances of high jitter (above 5 milliseconds) in real-time, triggering alerts for the technical team when such instances exceed 5% of the total packets in any 10-minute window
+* During peak load times, the allowable jitter can increase to a maximum of 10 milliseconds, but such instances should not exceed 2% of the total packets transmitted in a 24-hour period.
+
+</div><br>
\ No newline at end of file