From 1dd091f15e00ccfefae64d9e4b17da2fe1640187 Mon Sep 17 00:00:00 2001
From: JieXiong9119 <69597597+JieXiong9119@users.noreply.github.com>
Date: Thu, 29 Oct 2026 23:26:05 -0600
Subject: [PATCH 1/2] add proposal
---
.../2026/Add Binary Schedule Availability.md | 274 ++++++++++++++++++
1 file changed, 274 insertions(+)
create mode 100644 proposals/2026/Add Binary Schedule Availability.md
diff --git a/proposals/2026/Add Binary Schedule Availability.md b/proposals/2026/Add Binary Schedule Availability.md
new file mode 100644
index 00000000..1e3be345
--- /dev/null
+++ b/proposals/2026/Add Binary Schedule Availability.md
@@ -0,0 +1,274 @@
+# Add Binary Schedule Availability
+
+## Overview
+
+This proposal addresses [issue #260](https://github.com/BuildingSync/schema/issues/260) by adding explicit binary availability data to `ScheduleType`. Availability describes whether equipment is enabled and permitted to operate; it does not indicate that the equipment is actually running. The existing `PartialOperationPercentage` remains the operating-level value, with its existing category-dependent meaning.
+
+**Status: proposal only; neither the schema nor the validated XML examples are changed.** Two independent design decisions remain open:
+
+| Decision | Candidate A / 1 | Candidate B / 2 | Status |
+| ------------------------------------ | ---------------------------- | -------------------------------- | ------- |
+| Availability encoding | A: XML boolean | B: text enumeration | Pending |
+| Relationship to operating percentage | 1: optional exclusive choice | 2: independent optional siblings | Pending |
+
+All four combinations are candidates. Keeping two encodings in this proposal does **not** mean accepting both encodings in the eventual schema. Select one encoding and one structure before implementing the feature.
+
+## Justification
+
+The [discussion that led to #260](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378) distinguishes HVAC availability from partial operation of HVAC components. An HVAC system may be available to operate while controls or demand keep it idle. A component's operating percentage describes a different quantity. Expressing availability through a percentage alone loses that distinction.
+
+The current [schedule value definition](../../BuildingSync.xsd#L1825-L1837) provides only optional `PartialOperationPercentage`, implemented as unrestricted `xs:decimal` with optional `auc:Source`. Its documentation describes occupancy relative to typical maximum occupancy, or equipment power relative to installed capacity. Although the documentation says 0–100 (%), those bounds are not XSD restrictions.
+
+Some existing documents contain [time-only details](../../examples/AT_example_NYC_audit_report_property.xml#L4229-L4240), without an explicit value. Those records must remain valid; omitted data is not an explicit unavailable state. Other documents contain [small decimal percentages](../../examples/Single_building_gbxml_externalreference_geometry.xml#L8200-L8230). Their fraction-versus-percentage interpretation is separate work: values below one alone do not establish an incorrect scale, and this proposal neither converts nor tightens them.
+
+A dedicated availability field makes the two data meanings explicit without renaming existing elements, changing schedule links, or undertaking the broader generalized schedule-type-limits design discussed in the original issue.
+
+## Implementation
+
+### Classification and compatibility
+
+The eventual implementation is a **non-breaking MINOR addition** under [the versioning policy](../../docs/versioning.md), whichever of the four combinations is selected. The proposal-only contribution has **No Schema Changes**.
+
+Preserve every existing element's XML path, order relative to other existing elements, effective cardinality, type, attributes, and meaning. In particular, retain the complete existing `PartialOperationPercentage` declaration, including its unrestricted decimal value space, documentation, optionality, and optional `auc:Source`.
+
+An optional, single-occurrence XSD choice at the existing percentage position does not create an XML instance wrapper or make the percentage required. It continues to accept every previously valid detail. Independent optional siblings likewise preserve all existing details. Neither structure requires a migration script or deferral to a major release.
+
+This is backward compatibility for existing documents, not a promise that old schemas or downstream tools understand new availability data. Adoption requirements are listed below. Do not change schema version declarations or the changelog in this feature contribution.
+
+### Common element and semantics
+
+The working name is `ScheduleAvailability`. Add it as an optional child of `ScheduleDetail` in [ScheduleType](../../BuildingSync.xsd#L1748-L1851), with this proposed instance path:
+
+`auc:BuildingSync/auc:Facilities/auc:Facility/auc:Schedules/auc:Schedule/auc:ScheduleDetails/auc:ScheduleDetail/auc:ScheduleAvailability`
+
+Use the following common definition sentence in its documentation:
+
+> Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied.
+
+The encoding-specific definitions below add the corresponding value meanings. Common rules are:
+
+- Available means operation is permitted by this schedule, subject to demand and other controls. Unavailable means operation is not enabled by this schedule. This is not a hardware failure or equipment-condition indicator.
+- Availability does not imply 100% operation. A zero operating percentage does not, by itself, imply that equipment is unavailable.
+- Do not derive either quantity from the other or introduce an implicit value. No `default`, `fixed`, or `nillable="true"` is proposed.
+- Use optional `auc:Source` on the new scalar through `xs:simpleContent`, matching the existing provenance pattern. Do not use `xs:complexContent`.
+- Keep the existing optional day, category, time, and date metadata. Keep `Schedule/@ID`, `auc:Status`, `LinkedPremises`, and other schedule content unchanged.
+- Existing categories such as `HVAC equipment`, `Cooling equipment`, and `Heating equipment` can describe the equipment. No category is added, renamed, or made mandatory, and no category-dependent restriction is added to the base XSD.
+- The element name identifies the availability data; no schedule-level data-kind discriminator is introduced. Neither structural candidate enforces a uniform value kind across every detail in a schedule.
+- Do not redefine time boundaries, overlapping intervals, uncovered periods, or day-type precedence. The illustrative intervals below are partial examples, not instructions to fill gaps with false, zero, or the previous value.
+
+The proposed element name and the enumeration type name below were not found in the current BuildingSync or cached gbXML schemas during planning. Repeat the collision checks against the implementation base before adding them.
+
+### Encoding A: XML boolean
+
+Use an inline complex type whose simple content extends `xs:boolean`, with optional `auc:Source`:
+
+```xml
+
+
+ Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied. The values true and 1 mean available; false and 0 mean unavailable.
+
+
+
+
+
+
+
+
+
+```
+
+- **Accepted values:** `true`, `false`, `1`, and `0`, with standard XML boolean whitespace handling. Examples and producer guidance should prefer `true` and `false`.
+- **Advantages:** standard XML typing, native boolean mappings, no custom simple type.
+- **Trade-offs:** four lexical forms represent two states. A consumer must parse the value rather than test whether the element exists or whether its text is nonempty. In particular, a present `false` is not true.
+
+### Encoding B: text enumeration
+
+Add a named simple type `ScheduleAvailabilityType`, restricting `xs:string` to the exact labels `Available` and `Unavailable`:
+
+```xml
+
+
+ Binary availability of equipment during a scheduled interval, distinct from actual operation or an operating percentage.
+
+
+
+
+ Equipment is enabled and permitted to operate by this schedule, subject to demand and other controls.
+
+
+
+
+ Equipment is not enabled to operate by this schedule.
+
+
+
+
+```
+
+The optional element would extend that type to support provenance:
+
+```xml
+
+
+ Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied. Available means enabled; Unavailable means not enabled.
+
+
+
+
+
+
+
+
+
+```
+
+- **Accepted values:** exactly `Available` and `Unavailable`, with this casing. Using `xs:string` does not introduce whitespace trimming.
+- **Advantages:** explicit availability meaning, human-readable values, an enumeration available to generated documentation and clients.
+- **Trade-offs:** requires a custom simple type and explicit conversion to simulation availability values rather than native boolean parsing.
+- Do not use `On`/`Off` or `Operating`/`Closed`, which can suggest actual operation. Do not add `Unknown` or `Other`: this field has two states, and omission represents unsupplied data.
+
+The encoding blocks are alternative **XSD fragments**, not standalone schemas. Namespace declarations make the fragments readable independently; the schema already declares these namespaces. Only the selected encoding would be inserted into the XSD.
+
+### Structure 1: optional exclusive choice
+
+At the current `PartialOperationPercentage` position immediately after `DayEndTime` in the detail's sequence:
+
+1. Insert `xs:choice` with `minOccurs="0"` and `maxOccurs="1"`.
+2. Put the existing, unchanged optional `PartialOperationPercentage` declaration inside it.
+3. Add the optional `ScheduleAvailability` declaration from encoding A or B as the other branch.
+4. Leave every other sequence member in place. Declare each element only once; do not duplicate the percentage definition elsewhere.
+
+This permits a percentage alone, availability alone, or neither. It rejects both values in the same detail and rejects repeated values. The choice is per detail, not per whole schedule.
+
+**Advantages:** XSD enforces a single value kind per detail, and consumers can distinguish the two kinds by element name.
+
+**Trade-offs:** reporting both independent quantities requires separate entries or schedules, potentially duplicating interval metadata. Separate schedules can use the existing repeatable schedule links; no new linking element is needed.
+
+The following **proposed XML fragment** illustrates encoding A with structure 1. These new availability elements are not valid against the unchanged current schema. It is not a complete BuildingSync document.
+
+```xml
+
+
+
+
+ Weekday
+ HVAC equipment
+ 06:00:00
+ 18:00:00
+ true
+
+
+ Weekday
+ HVAC equipment
+ 18:00:00
+ 22:00:00
+ false
+
+
+
+
+
+
+ Weekday
+ HVAC equipment
+ 06:00:00
+ 18:00:00
+ 40
+
+
+
+
+```
+
+For encoding B with structure 1, replace only availability values: `true` becomes `Available` and `false` becomes `Unavailable`. The percentage remains `40`, not `0.4`, `1`, or `Available`.
+
+For example, an existing [thermal-zone schedule link container](../../BuildingSync.xsd#L1545-L1558) can refer to both schedule IDs above. This link fragment belongs under a `ThermalZone`, not inside `Schedules`:
+
+```xml
+
+
+
+
+```
+
+### Structure 2: independent optional siblings
+
+Leave the current optional `PartialOperationPercentage` declaration exactly where it is. Append optional `ScheduleAvailability` from encoding A or B immediately after it in the detail's sequence, with `minOccurs="0"` and the default `maxOccurs="1"`.
+
+This permits neither value, either value, or both once. When both appear, the percentage must precede availability. Reversed order and duplicate values are invalid.
+
+**Advantages:** independently reports availability and operating level with shared interval metadata. Being available and operating at 40% is not the same as being 40% available.
+
+**Trade-offs:** consumers must handle two quantities. There is no automatic conversion, precedence, or overwriting of either field. An unavailable interval with a positive reported operating percentage would require domain reconciliation; this proposal does not introduce a cross-value consistency constraint into the base XSD. A consumer or use case would need an explicit policy rather than silently changing the supplied values.
+
+The following **proposed XML fragment** illustrates encoding B with structure 2. It belongs within `ScheduleDetails` and is not valid against the unchanged current schema:
+
+```xml
+
+ Weekday
+ HVAC equipment
+ 06:00:00
+ 18:00:00
+ 40
+ Available
+
+```
+
+For encoding A with structure 2, replace `Available` with `true`. Both structures also allow an availability-only detail, so the explicitly unavailable interval shown under structure 1 remains expressible without inventing an operating percentage.
+
+### Downstream compatibility and follow-up
+
+The following findings were checked during planning on 2026-10-29. They distinguish preserved behavior for old percentage documents from support for newly introduced availability data. These are follow-up recommendations, not external changes or already-opened issues.
+
+| Repository / consumer | Verified evidence or search limitation | Proposed follow-up |
+| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **use-cases / TestSuite** | In the current [L200 rules](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/schematron/L200_Audit-1.0.0.sch), `general_schedule_requirements` requires `auc:PartialOperationPercentage` on every `ScheduleDetail`. The separate `occupancy_schedules` rule requires it for `Occupied`. Availability-only details would fail the current L200 schedules phase even if valid against the candidate XSD. | Review a version-aware, category- and meaning-aware rule update, including the [source CSV](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/src/L200_Audit-1.0.0.csv), generated Schematron, and fixtures. Do not globally replace the percentage assertion with an unrestricted either/or: occupancy-density requirements still need operating percentages. Coordinate use-case adoption; no TestSuite library change is established by this finding. |
+| **buildingsync-measures-gem** | [ModifySchedules](https://github.com/BuildingSync/buildingsync-measures-gem/blob/develop/lib/measures/modify_schedules/measure.rb) accepts JSON/compact payloads, not raw BuildingSync XML. `parse_schedule_payload` reads `value_percent`, `partialoperationpercentage`, `value`, or `fraction`; missing values are errors. It uses numeric conversion, divides explicit percentages by 100, and clamps to 0–1. The `hvac_availability_schedule_json` target currently uses the same fraction schedule machinery, including Continuous limits, before `setAvailabilitySchedule`. | Add explicit parsing/mapping for the selected availability encoding and discrete 0/1 availability values, separate from percentage normalization. Preserve legacy numeric behavior and test false/unavailable distinctly from omission. A payload carrying only the new availability key is not currently supported. |
+| **BOSS** | Exact `PartialOperationPercentage` searches returned no matches; `ScheduleDetail` matches were XML fixtures. Those searches do not establish how runtime code handles schedules or what defaults it uses. | Trace the relevant XML-to-measure payload handoff and determine whether availability needs additional forwarding, selection, or unsupported-data reporting. Do not claim end-to-end support from fixture presence. |
+| **BuildingSync-asset-extractor** | Exact percentage searches returned no matches; schedule-detail matches were test fixtures. No direct availability consumer was established. | Confirm whether any extraction path consumes schedules before deciding whether implementation changes are needed. A bounded search is not proof of no impact. |
+| **Generated clients and BuildingSync-website** | Newly introduced elements/types require consumers to adopt the corresponding schema. No compatibility result for the candidate feature has been established for current generated clients, the viewer, or the hosted validator. | Verify generated bindings, documentation/viewer presentation, enumeration output if encoding B is selected, and validation against the eventual released schema. Do not expect an older released schema to accept availability data. |
+
+The existing schedule paths and links are not renamed, moved, or deprecated. However, schema backward compatibility alone does not make new availability-only data usable by percentage-only consumers. Do not generate placeholder percentages just to bypass an older consumer's requirements.
+
+### Verification and acceptance criteria
+
+After selecting the design, add focused regression contexts to [the existing validation spec](../../spec/validation_spec.rb), reusing its `@xsd` and local gbXML import handling. Add one complete, linked example only when its representation is supported by the implemented schema. Invalid cases should be constructed in tests, not committed as failing examples.
+
+| Area | Expected checks |
+| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Legacy percentages | All existing examples remain valid without edits. Preserve `0`, `1`, `40`, `100`, small decimal values, and optional `auc:Source`. Include unrestricted decimal edge cases to catch accidental bounds tightening; those are compatibility tests, not recommended data values. |
+| Legacy omission | Preserve time-only details, empty details, an empty optional `ScheduleDetails`, and omitted schedule metadata wherever currently valid. Absence is not automatically false or zero. |
+| Availability and provenance | Explicit available and unavailable values validate, with and without valid `auc:Source`. Invalid provenance values fail. Omission remains valid; empty content and `xsi:nil="true"` fail. |
+| Encoding A, if selected | Accept `true`, `false`, `1`, `0`, and XML boolean whitespace normalization. Reject `2`, `-1`, `0.5`, `1.0`, `True`, `yes`, and `Available`. Consumers must distinguish false/0 from an omitted value. |
+| Encoding B, if selected | Accept only `Available` and `Unavailable`. Reject `On`, `Off`, `true`, `false`, `0`, `1`, `Unknown`, `Other`, wrong casing, and surrounding whitespace. |
+| Structure 1, if selected | Accept either value or neither. Reject both together in either order and duplicates of either value. Separate details/schedules may report different data kinds. |
+| Structure 2, if selected | Accept both once with percentage before availability, as well as either alone or neither. Reject reversed order and duplicates. Do not impose an undocumented cross-value calculation. |
+| Unchanged context | Preserve date/time types, day/category enumerations, required schedule IDs, optional status, and existing IDref paths. Check that example references resolve to the intended schedules, not merely an arbitrary ID. |
+| Documentation and consumers | Explain available-but-not-running and available-plus-40%-operation. Verify candidate documentation/type exports and list downstream adoption limitations separately from XSD results. |
+
+For the proposal-only contribution, review all fragments, links, required headings, and the two pending decisions, and run `poetry run pre-commit run --all-files`. Keep all candidate XML embedded here rather than adding it to the currently validated examples.
+
+For the later implementation, run `bundle exec rake remove_tabs`, `bundle exec rake`, `bundle exec rake generate_data_dictionary`, and pre-commit. Inspect formatting changes and remove generated release artifacts after inspection; do not commit those artifacts or unrelated formatting changes.
+
+### Decision and scope
+
+- **Agreed requirement:** binary availability/enabled data alongside continued support for percentage operating schedules.
+- **Encoding decision:** pending, A or B.
+- **Structure decision:** pending, 1 or 2.
+- **Implementation gate:** obtain design approval and implementation authorization before changing the schema, examples, or regression tests. This proposal does not claim team acceptance or resolution of #260.
+- **Contribution labels:** `No Schema Changes` for the proposal-only PR. An eventual additive implementation would use `Non-breaking Change` and `Schema: General`. Reference #260 without closing it in the proposal-only contribution.
+- **Out of scope:** interpreting availability as measured running status; changing or normalizing percentage data; new percentage bounds; generalized numeric/temperature/integer schedule types; schedule-wide discriminators; interval/overlap/gap redesign; new links; version/changelog edits; external repository edits or issue creation.
+
+## References
+
+- [BuildingSync/schema issue #260](https://github.com/BuildingSync/schema/issues/260).
+- [Original availability-versus-operation discussion in TestSuite #37](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378).
+- [BuildingSync versioning](../../docs/versioning.md).
+- [BuildingSync proposal process](../README.md).
+- [Existing schedule linking definitions](../../docs/linking_elements.md).
+- [Earlier proposal comparing occupancy schedule linking alternatives](../2020/Add%20Occupancy%20Schedule%20Linking.md).
From 8430530ac276d41c4c1147dd41797b9e32f1b202 Mon Sep 17 00:00:00 2001
From: JieXiong9119 <69597597+JieXiong9119@users.noreply.github.com>
Date: Thu, 12 Nov 2026 14:27:01 -0700
Subject: [PATCH 2/2] update proposal to distinguish between operation and
availability
---
.../2026/Add Binary Schedule Availability.md | 274 -----------------
proposals/2026/Add Binary Schedule.md | 281 ++++++++++++++++++
2 files changed, 281 insertions(+), 274 deletions(-)
delete mode 100644 proposals/2026/Add Binary Schedule Availability.md
create mode 100644 proposals/2026/Add Binary Schedule.md
diff --git a/proposals/2026/Add Binary Schedule Availability.md b/proposals/2026/Add Binary Schedule Availability.md
deleted file mode 100644
index 1e3be345..00000000
--- a/proposals/2026/Add Binary Schedule Availability.md
+++ /dev/null
@@ -1,274 +0,0 @@
-# Add Binary Schedule Availability
-
-## Overview
-
-This proposal addresses [issue #260](https://github.com/BuildingSync/schema/issues/260) by adding explicit binary availability data to `ScheduleType`. Availability describes whether equipment is enabled and permitted to operate; it does not indicate that the equipment is actually running. The existing `PartialOperationPercentage` remains the operating-level value, with its existing category-dependent meaning.
-
-**Status: proposal only; neither the schema nor the validated XML examples are changed.** Two independent design decisions remain open:
-
-| Decision | Candidate A / 1 | Candidate B / 2 | Status |
-| ------------------------------------ | ---------------------------- | -------------------------------- | ------- |
-| Availability encoding | A: XML boolean | B: text enumeration | Pending |
-| Relationship to operating percentage | 1: optional exclusive choice | 2: independent optional siblings | Pending |
-
-All four combinations are candidates. Keeping two encodings in this proposal does **not** mean accepting both encodings in the eventual schema. Select one encoding and one structure before implementing the feature.
-
-## Justification
-
-The [discussion that led to #260](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378) distinguishes HVAC availability from partial operation of HVAC components. An HVAC system may be available to operate while controls or demand keep it idle. A component's operating percentage describes a different quantity. Expressing availability through a percentage alone loses that distinction.
-
-The current [schedule value definition](../../BuildingSync.xsd#L1825-L1837) provides only optional `PartialOperationPercentage`, implemented as unrestricted `xs:decimal` with optional `auc:Source`. Its documentation describes occupancy relative to typical maximum occupancy, or equipment power relative to installed capacity. Although the documentation says 0–100 (%), those bounds are not XSD restrictions.
-
-Some existing documents contain [time-only details](../../examples/AT_example_NYC_audit_report_property.xml#L4229-L4240), without an explicit value. Those records must remain valid; omitted data is not an explicit unavailable state. Other documents contain [small decimal percentages](../../examples/Single_building_gbxml_externalreference_geometry.xml#L8200-L8230). Their fraction-versus-percentage interpretation is separate work: values below one alone do not establish an incorrect scale, and this proposal neither converts nor tightens them.
-
-A dedicated availability field makes the two data meanings explicit without renaming existing elements, changing schedule links, or undertaking the broader generalized schedule-type-limits design discussed in the original issue.
-
-## Implementation
-
-### Classification and compatibility
-
-The eventual implementation is a **non-breaking MINOR addition** under [the versioning policy](../../docs/versioning.md), whichever of the four combinations is selected. The proposal-only contribution has **No Schema Changes**.
-
-Preserve every existing element's XML path, order relative to other existing elements, effective cardinality, type, attributes, and meaning. In particular, retain the complete existing `PartialOperationPercentage` declaration, including its unrestricted decimal value space, documentation, optionality, and optional `auc:Source`.
-
-An optional, single-occurrence XSD choice at the existing percentage position does not create an XML instance wrapper or make the percentage required. It continues to accept every previously valid detail. Independent optional siblings likewise preserve all existing details. Neither structure requires a migration script or deferral to a major release.
-
-This is backward compatibility for existing documents, not a promise that old schemas or downstream tools understand new availability data. Adoption requirements are listed below. Do not change schema version declarations or the changelog in this feature contribution.
-
-### Common element and semantics
-
-The working name is `ScheduleAvailability`. Add it as an optional child of `ScheduleDetail` in [ScheduleType](../../BuildingSync.xsd#L1748-L1851), with this proposed instance path:
-
-`auc:BuildingSync/auc:Facilities/auc:Facility/auc:Schedules/auc:Schedule/auc:ScheduleDetails/auc:ScheduleDetail/auc:ScheduleAvailability`
-
-Use the following common definition sentence in its documentation:
-
-> Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied.
-
-The encoding-specific definitions below add the corresponding value meanings. Common rules are:
-
-- Available means operation is permitted by this schedule, subject to demand and other controls. Unavailable means operation is not enabled by this schedule. This is not a hardware failure or equipment-condition indicator.
-- Availability does not imply 100% operation. A zero operating percentage does not, by itself, imply that equipment is unavailable.
-- Do not derive either quantity from the other or introduce an implicit value. No `default`, `fixed`, or `nillable="true"` is proposed.
-- Use optional `auc:Source` on the new scalar through `xs:simpleContent`, matching the existing provenance pattern. Do not use `xs:complexContent`.
-- Keep the existing optional day, category, time, and date metadata. Keep `Schedule/@ID`, `auc:Status`, `LinkedPremises`, and other schedule content unchanged.
-- Existing categories such as `HVAC equipment`, `Cooling equipment`, and `Heating equipment` can describe the equipment. No category is added, renamed, or made mandatory, and no category-dependent restriction is added to the base XSD.
-- The element name identifies the availability data; no schedule-level data-kind discriminator is introduced. Neither structural candidate enforces a uniform value kind across every detail in a schedule.
-- Do not redefine time boundaries, overlapping intervals, uncovered periods, or day-type precedence. The illustrative intervals below are partial examples, not instructions to fill gaps with false, zero, or the previous value.
-
-The proposed element name and the enumeration type name below were not found in the current BuildingSync or cached gbXML schemas during planning. Repeat the collision checks against the implementation base before adding them.
-
-### Encoding A: XML boolean
-
-Use an inline complex type whose simple content extends `xs:boolean`, with optional `auc:Source`:
-
-```xml
-
-
- Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied. The values true and 1 mean available; false and 0 mean unavailable.
-
-
-
-
-
-
-
-
-
-```
-
-- **Accepted values:** `true`, `false`, `1`, and `0`, with standard XML boolean whitespace handling. Examples and producer guidance should prefer `true` and `false`.
-- **Advantages:** standard XML typing, native boolean mappings, no custom simple type.
-- **Trade-offs:** four lexical forms represent two states. A consumer must parse the value rather than test whether the element exists or whether its text is nonempty. In particular, a present `false` is not true.
-
-### Encoding B: text enumeration
-
-Add a named simple type `ScheduleAvailabilityType`, restricting `xs:string` to the exact labels `Available` and `Unavailable`:
-
-```xml
-
-
- Binary availability of equipment during a scheduled interval, distinct from actual operation or an operating percentage.
-
-
-
-
- Equipment is enabled and permitted to operate by this schedule, subject to demand and other controls.
-
-
-
-
- Equipment is not enabled to operate by this schedule.
-
-
-
-
-```
-
-The optional element would extend that type to support provenance:
-
-```xml
-
-
- Indicates whether the equipment associated with the schedule is enabled and available to operate during the interval. Availability does not indicate actual operation or an operating percentage. Omission means availability is not supplied. Available means enabled; Unavailable means not enabled.
-
-
-
-
-
-
-
-
-
-```
-
-- **Accepted values:** exactly `Available` and `Unavailable`, with this casing. Using `xs:string` does not introduce whitespace trimming.
-- **Advantages:** explicit availability meaning, human-readable values, an enumeration available to generated documentation and clients.
-- **Trade-offs:** requires a custom simple type and explicit conversion to simulation availability values rather than native boolean parsing.
-- Do not use `On`/`Off` or `Operating`/`Closed`, which can suggest actual operation. Do not add `Unknown` or `Other`: this field has two states, and omission represents unsupplied data.
-
-The encoding blocks are alternative **XSD fragments**, not standalone schemas. Namespace declarations make the fragments readable independently; the schema already declares these namespaces. Only the selected encoding would be inserted into the XSD.
-
-### Structure 1: optional exclusive choice
-
-At the current `PartialOperationPercentage` position immediately after `DayEndTime` in the detail's sequence:
-
-1. Insert `xs:choice` with `minOccurs="0"` and `maxOccurs="1"`.
-2. Put the existing, unchanged optional `PartialOperationPercentage` declaration inside it.
-3. Add the optional `ScheduleAvailability` declaration from encoding A or B as the other branch.
-4. Leave every other sequence member in place. Declare each element only once; do not duplicate the percentage definition elsewhere.
-
-This permits a percentage alone, availability alone, or neither. It rejects both values in the same detail and rejects repeated values. The choice is per detail, not per whole schedule.
-
-**Advantages:** XSD enforces a single value kind per detail, and consumers can distinguish the two kinds by element name.
-
-**Trade-offs:** reporting both independent quantities requires separate entries or schedules, potentially duplicating interval metadata. Separate schedules can use the existing repeatable schedule links; no new linking element is needed.
-
-The following **proposed XML fragment** illustrates encoding A with structure 1. These new availability elements are not valid against the unchanged current schema. It is not a complete BuildingSync document.
-
-```xml
-
-
-
-
- Weekday
- HVAC equipment
- 06:00:00
- 18:00:00
- true
-
-
- Weekday
- HVAC equipment
- 18:00:00
- 22:00:00
- false
-
-
-
-
-
-
- Weekday
- HVAC equipment
- 06:00:00
- 18:00:00
- 40
-
-
-
-
-```
-
-For encoding B with structure 1, replace only availability values: `true` becomes `Available` and `false` becomes `Unavailable`. The percentage remains `40`, not `0.4`, `1`, or `Available`.
-
-For example, an existing [thermal-zone schedule link container](../../BuildingSync.xsd#L1545-L1558) can refer to both schedule IDs above. This link fragment belongs under a `ThermalZone`, not inside `Schedules`:
-
-```xml
-
-
-
-
-```
-
-### Structure 2: independent optional siblings
-
-Leave the current optional `PartialOperationPercentage` declaration exactly where it is. Append optional `ScheduleAvailability` from encoding A or B immediately after it in the detail's sequence, with `minOccurs="0"` and the default `maxOccurs="1"`.
-
-This permits neither value, either value, or both once. When both appear, the percentage must precede availability. Reversed order and duplicate values are invalid.
-
-**Advantages:** independently reports availability and operating level with shared interval metadata. Being available and operating at 40% is not the same as being 40% available.
-
-**Trade-offs:** consumers must handle two quantities. There is no automatic conversion, precedence, or overwriting of either field. An unavailable interval with a positive reported operating percentage would require domain reconciliation; this proposal does not introduce a cross-value consistency constraint into the base XSD. A consumer or use case would need an explicit policy rather than silently changing the supplied values.
-
-The following **proposed XML fragment** illustrates encoding B with structure 2. It belongs within `ScheduleDetails` and is not valid against the unchanged current schema:
-
-```xml
-
- Weekday
- HVAC equipment
- 06:00:00
- 18:00:00
- 40
- Available
-
-```
-
-For encoding A with structure 2, replace `Available` with `true`. Both structures also allow an availability-only detail, so the explicitly unavailable interval shown under structure 1 remains expressible without inventing an operating percentage.
-
-### Downstream compatibility and follow-up
-
-The following findings were checked during planning on 2026-10-29. They distinguish preserved behavior for old percentage documents from support for newly introduced availability data. These are follow-up recommendations, not external changes or already-opened issues.
-
-| Repository / consumer | Verified evidence or search limitation | Proposed follow-up |
-| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **use-cases / TestSuite** | In the current [L200 rules](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/schematron/L200_Audit-1.0.0.sch), `general_schedule_requirements` requires `auc:PartialOperationPercentage` on every `ScheduleDetail`. The separate `occupancy_schedules` rule requires it for `Occupied`. Availability-only details would fail the current L200 schedules phase even if valid against the candidate XSD. | Review a version-aware, category- and meaning-aware rule update, including the [source CSV](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/src/L200_Audit-1.0.0.csv), generated Schematron, and fixtures. Do not globally replace the percentage assertion with an unrestricted either/or: occupancy-density requirements still need operating percentages. Coordinate use-case adoption; no TestSuite library change is established by this finding. |
-| **buildingsync-measures-gem** | [ModifySchedules](https://github.com/BuildingSync/buildingsync-measures-gem/blob/develop/lib/measures/modify_schedules/measure.rb) accepts JSON/compact payloads, not raw BuildingSync XML. `parse_schedule_payload` reads `value_percent`, `partialoperationpercentage`, `value`, or `fraction`; missing values are errors. It uses numeric conversion, divides explicit percentages by 100, and clamps to 0–1. The `hvac_availability_schedule_json` target currently uses the same fraction schedule machinery, including Continuous limits, before `setAvailabilitySchedule`. | Add explicit parsing/mapping for the selected availability encoding and discrete 0/1 availability values, separate from percentage normalization. Preserve legacy numeric behavior and test false/unavailable distinctly from omission. A payload carrying only the new availability key is not currently supported. |
-| **BOSS** | Exact `PartialOperationPercentage` searches returned no matches; `ScheduleDetail` matches were XML fixtures. Those searches do not establish how runtime code handles schedules or what defaults it uses. | Trace the relevant XML-to-measure payload handoff and determine whether availability needs additional forwarding, selection, or unsupported-data reporting. Do not claim end-to-end support from fixture presence. |
-| **BuildingSync-asset-extractor** | Exact percentage searches returned no matches; schedule-detail matches were test fixtures. No direct availability consumer was established. | Confirm whether any extraction path consumes schedules before deciding whether implementation changes are needed. A bounded search is not proof of no impact. |
-| **Generated clients and BuildingSync-website** | Newly introduced elements/types require consumers to adopt the corresponding schema. No compatibility result for the candidate feature has been established for current generated clients, the viewer, or the hosted validator. | Verify generated bindings, documentation/viewer presentation, enumeration output if encoding B is selected, and validation against the eventual released schema. Do not expect an older released schema to accept availability data. |
-
-The existing schedule paths and links are not renamed, moved, or deprecated. However, schema backward compatibility alone does not make new availability-only data usable by percentage-only consumers. Do not generate placeholder percentages just to bypass an older consumer's requirements.
-
-### Verification and acceptance criteria
-
-After selecting the design, add focused regression contexts to [the existing validation spec](../../spec/validation_spec.rb), reusing its `@xsd` and local gbXML import handling. Add one complete, linked example only when its representation is supported by the implemented schema. Invalid cases should be constructed in tests, not committed as failing examples.
-
-| Area | Expected checks |
-| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Legacy percentages | All existing examples remain valid without edits. Preserve `0`, `1`, `40`, `100`, small decimal values, and optional `auc:Source`. Include unrestricted decimal edge cases to catch accidental bounds tightening; those are compatibility tests, not recommended data values. |
-| Legacy omission | Preserve time-only details, empty details, an empty optional `ScheduleDetails`, and omitted schedule metadata wherever currently valid. Absence is not automatically false or zero. |
-| Availability and provenance | Explicit available and unavailable values validate, with and without valid `auc:Source`. Invalid provenance values fail. Omission remains valid; empty content and `xsi:nil="true"` fail. |
-| Encoding A, if selected | Accept `true`, `false`, `1`, `0`, and XML boolean whitespace normalization. Reject `2`, `-1`, `0.5`, `1.0`, `True`, `yes`, and `Available`. Consumers must distinguish false/0 from an omitted value. |
-| Encoding B, if selected | Accept only `Available` and `Unavailable`. Reject `On`, `Off`, `true`, `false`, `0`, `1`, `Unknown`, `Other`, wrong casing, and surrounding whitespace. |
-| Structure 1, if selected | Accept either value or neither. Reject both together in either order and duplicates of either value. Separate details/schedules may report different data kinds. |
-| Structure 2, if selected | Accept both once with percentage before availability, as well as either alone or neither. Reject reversed order and duplicates. Do not impose an undocumented cross-value calculation. |
-| Unchanged context | Preserve date/time types, day/category enumerations, required schedule IDs, optional status, and existing IDref paths. Check that example references resolve to the intended schedules, not merely an arbitrary ID. |
-| Documentation and consumers | Explain available-but-not-running and available-plus-40%-operation. Verify candidate documentation/type exports and list downstream adoption limitations separately from XSD results. |
-
-For the proposal-only contribution, review all fragments, links, required headings, and the two pending decisions, and run `poetry run pre-commit run --all-files`. Keep all candidate XML embedded here rather than adding it to the currently validated examples.
-
-For the later implementation, run `bundle exec rake remove_tabs`, `bundle exec rake`, `bundle exec rake generate_data_dictionary`, and pre-commit. Inspect formatting changes and remove generated release artifacts after inspection; do not commit those artifacts or unrelated formatting changes.
-
-### Decision and scope
-
-- **Agreed requirement:** binary availability/enabled data alongside continued support for percentage operating schedules.
-- **Encoding decision:** pending, A or B.
-- **Structure decision:** pending, 1 or 2.
-- **Implementation gate:** obtain design approval and implementation authorization before changing the schema, examples, or regression tests. This proposal does not claim team acceptance or resolution of #260.
-- **Contribution labels:** `No Schema Changes` for the proposal-only PR. An eventual additive implementation would use `Non-breaking Change` and `Schema: General`. Reference #260 without closing it in the proposal-only contribution.
-- **Out of scope:** interpreting availability as measured running status; changing or normalizing percentage data; new percentage bounds; generalized numeric/temperature/integer schedule types; schedule-wide discriminators; interval/overlap/gap redesign; new links; version/changelog edits; external repository edits or issue creation.
-
-## References
-
-- [BuildingSync/schema issue #260](https://github.com/BuildingSync/schema/issues/260).
-- [Original availability-versus-operation discussion in TestSuite #37](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378).
-- [BuildingSync versioning](../../docs/versioning.md).
-- [BuildingSync proposal process](../README.md).
-- [Existing schedule linking definitions](../../docs/linking_elements.md).
-- [Earlier proposal comparing occupancy schedule linking alternatives](../2020/Add%20Occupancy%20Schedule%20Linking.md).
diff --git a/proposals/2026/Add Binary Schedule.md b/proposals/2026/Add Binary Schedule.md
new file mode 100644
index 00000000..d049725b
--- /dev/null
+++ b/proposals/2026/Add Binary Schedule.md
@@ -0,0 +1,281 @@
+# Add Binary Schedule
+
+## Overview
+
+This proposal addresses [issue #260](https://github.com/BuildingSync/schema/issues/260) by adding binary (on/off) schedule values to `ScheduleType`. A new optional container on each schedule detail, `BinarySchedule`, holds a required `BinaryValue` (the binary state for the interval) and a required `BinaryScheduleType` (what the state means), initially `Availability` (equipment is enabled and permitted to operate) or `Operation` (equipment is scheduled on or off). The existing `PartialOperationPercentage` remains the fractional operating-level value, with its existing category-dependent meaning.
+
+**Status: proposal only; neither the schema nor the validated XML examples are changed.** The generalized design (a binary value paired with a meaning qualifier in one container) is the preferred approach. Two lower-level design decisions remain open:
+
+| Decision | Candidate A / 1 | Candidate B / 2 | Status |
+| ------------------------------------ | ---------------------------- | -------------------------------- | ------- |
+| Binary value encoding | A: XML boolean | B: `On`/`Off` text enumeration | Pending |
+| Relationship to operating percentage | 1: optional exclusive choice | 2: independent optional siblings | Pending |
+
+All four combinations are candidates. Keeping two encodings in this proposal does **not** mean accepting both encodings in the eventual schema.
+
+## Justification
+
+### Use case
+
+Issue #260 asks for a schedule that describes the ON/OFF operation of HVAC equipment. The [discussion that led to #260](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378) adds a closely related need: HVAC systems are _available or not available_, while HVAC components may partially operate. Today the only schedule value is [`PartialOperationPercentage`](../../BuildingSync.xsd#L1825-L1837), an unrestricted `xs:decimal` documented as 0–100 %. Producers must encode on/off as `100`/`0`, and consumers cannot tell whether such a schedule means "running at full load", "enabled to run", or "scheduled on". The meaning matters downstream:
+
+- Audit tools and Audit Template-style exports report HVAC, lighting, and other equipment operating hours as on/off intervals. Several existing documents contain [time-only details](../../examples/AT_example_NYC_audit_report_property.xml#L4229-L4240), which suggest operating hours but do not state a value.
+- Energy models represent HVAC on/off and availability with discrete 0/1 schedules (for example OpenStudio air-loop availability schedules), not fractional load profiles.
+- ASHRAE Standard 211 Level 2 audits ask for HVAC operating schedules; today the [L200 rules](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/schematron/L200_Audit-1.0.0.sch) force a percentage on every schedule detail.
+
+### Why a generalized binary schedule
+
+A schedule of true/false values does not carry its own meaning. In EnergyPlus, an On/Off schedule gets its meaning from the object that references it (availability manager, fan operating mode, and so on). BuildingSync schedules are referenced generically, so the meaning must be stated in the data. Three options were considered:
+
+| Option | Shape | Assessment |
+| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| **a. Binary value plus type qualifier (chosen)** | `BinarySchedule` per detail containing `BinaryValue` and `BinaryScheduleType` (`Availability`, `Operation`, `Other`) | One value element covers availability, ON/OFF operation, and future meanings. Consumers branch on one qualifier. Additive and non-breaking. |
+| b. Infer meaning from `ScheduleCategory` | Binary value only | No new qualifier, but category says _which equipment_, not _what kind of state_. HVAC availability and HVAC on/off would be indistinguishable. |
+| c. One element per meaning | `ScheduleAvailability`, `ScheduleOperationStatus`, … | Unambiguous, but the number of elements grows with each meaning and consumers must know them all. |
+
+Option (a) satisfies the ON/OFF request in #260 and the availability distinction from the original discussion without proliferating elements, and leaves room for other binary meanings.
+
+### Scope of "schedule"
+
+A schedule is planned or intended state. Observed, measured run status (for example from trend logs) belongs in `TimeSeries`, not `ScheduleType`. This proposal does not change that.
+
+## Implementation
+
+### Classification and compatibility
+
+The eventual implementation is a **non-breaking MINOR addition** under [the versioning policy](../../docs/versioning.md), whichever combination is selected. The new `BinarySchedule` container is optional; its two children are required only inside the new container, so no existing document is affected. The proposal-only contribution has **No Schema Changes**.
+
+Preserve every existing element's XML path, order relative to other existing elements, effective cardinality, type, attributes, and meaning. In particular, retain the complete existing `PartialOperationPercentage` declaration, including its unrestricted decimal value space, documentation, optionality, and optional `auc:Source`. An optional, single-occurrence XSD choice does not create an XML instance wrapper, so structure 1 also accepts every previously valid detail. No migration script is needed.
+
+Backward compatibility for existing documents is not a promise that old schemas or downstream tools understand the new data; see [Potential consumers and adoption](#potential-consumers-and-adoption).
+
+### New elements and paths
+
+All paths are below `auc:BuildingSync/auc:Facilities/auc:Facility/auc:Schedules/auc:Schedule/auc:ScheduleDetails/auc:ScheduleDetail`:
+
+| Element | Relative path | Cardinality |
+| -------------------- | ------------------------------------------- | ------------------------- |
+| `BinarySchedule` | `auc:BinarySchedule` | 0..1 per detail |
+| `BinaryValue` | `auc:BinarySchedule/auc:BinaryValue` | 1..1 per `BinarySchedule` |
+| `BinaryScheduleType` | `auc:BinarySchedule/auc:BinaryScheduleType` | 1..1 per `BinarySchedule` |
+
+`BinarySchedule` extends the existing [ScheduleDetail](../../BuildingSync.xsd#L1748-L1851) at the current `PartialOperationPercentage` position (see the structure options). It reuses the detail's `DayType`, `ScheduleCategory`, `DayStartTime`, and `DayEndTime`, so no parallel detail structure is introduced. None of the three names was found in the current BuildingSync or cached gbXML schemas; repeat the collision checks against the implementation base.
+
+Because both children are required inside the container:
+
+- A meaning cannot appear without a binary value, and a binary value cannot appear without a meaning. A schedule whose details carry only `PartialOperationPercentage` cannot carry a stray `BinaryScheduleType`.
+- The XSD cannot require all details in one schedule to use the same `BinaryScheduleType`. Producers should use one meaning per schedule and put availability and on/off data in separate schedules; use cases may enforce this with Schematron.
+
+### `BinarySchedule`
+
+```xml
+
+
+ Binary (on/off) schedule value for the interval of this schedule detail, with its meaning.
+
+
+
+
+
+
+
+
+```
+
+### `BinaryScheduleType`
+
+A required enumeration inside `BinarySchedule`, declared inline like other BuildingSync enumerations:
+
+```xml
+
+
+ Meaning of the sibling BinaryValue.
+
+
+
+
+
+ True/On means the equipment is enabled and permitted to operate, subject to demand and other controls. It does not indicate that the equipment is running.
+
+
+
+
+ True/On means the equipment is scheduled to be on (operating); False/Off means it is scheduled to be off.
+
+
+
+
+ Another binary meaning, described in UserDefinedFields.
+
+
+
+
+
+```
+
+Rules:
+
+- A building that needs both HVAC availability and HVAC on/off data uses two schedules, linked through the existing repeatable schedule references.
+- `Occupancy` is not proposed: occupied/unoccupied is already expressed by the `Occupied`/`Unoccupied` schedule categories and occupancy density by `PartialOperationPercentage`. Further meanings can be added later as non-breaking enumeration values.
+
+### `BinaryValue`
+
+Common documentation:
+
+> Binary state of the scheduled equipment during the interval. The meaning of the state is given by the sibling BinaryScheduleType.
+
+Common rules:
+
+- Optional `auc:Source` through `xs:simpleContent`, matching the existing provenance pattern. No `xs:complexContent`, `default`, `fixed`, or `nillable`.
+- Do not derive the binary value from the operating percentage or the reverse. True/On under `Availability` does not imply 100 % operation; a zero percentage does not imply unavailable.
+- Keep the existing day, category, time, and date metadata, `Schedule/@ID`, `auc:Status`, and links unchanged. No category is added or made mandatory.
+- Do not redefine time boundaries, overlaps, gaps, or day-type precedence. Uncovered intervals are not implicitly false/Off.
+
+#### Encoding A: XML boolean
+
+```xml
+
+
+ Binary state of the scheduled equipment during the interval. The meaning of the state is given by the sibling BinaryScheduleType. true and 1 mean on/available; false and 0 mean off/unavailable.
+
+
+
+
+
+
+
+
+
+```
+
+- **Accepted values:** `true`, `false`, `1`, `0`. Examples should prefer `true`/`false`.
+- **Advantages:** standard type and native bindings; a meaning-neutral value pairs naturally with `BinaryScheduleType`.
+- **Trade-offs:** four lexical forms for two states; a present `false` must not be treated as truthy text.
+
+#### Encoding B: `On`/`Off` enumeration
+
+Same element, with the value restricted to the exact labels `On` and `Off` through a named simple type `BinaryValueType` (restriction of `xs:string`) extended with `auc:Source`.
+
+- **Advantages:** human-readable; matches the wording of #260; exported as an enumeration.
+- **Trade-offs:** `On` reads awkwardly for `Availability` schedules ("On" meaning "available"); requires a custom type and explicit conversion to 0/1.
+
+### Structure 1: optional exclusive choice
+
+At the current `PartialOperationPercentage` position after `DayEndTime`, insert `xs:choice minOccurs="0" maxOccurs="1"` containing the unchanged `PartialOperationPercentage` declaration and the new `BinarySchedule`. Each detail carries a percentage, a binary schedule, or neither; both together and duplicates are rejected.
+
+- **Advantages:** one value kind per detail; simple consumption.
+- **Trade-offs:** reporting both a binary state and an operating level for the same interval requires separate schedules.
+
+### Structure 2: independent optional siblings
+
+Leave `PartialOperationPercentage` untouched and append optional `BinarySchedule` immediately after it. Neither, either, or both (percentage first) are allowed.
+
+- **Advantages:** "available and operating at 40 %" fits in one detail.
+- **Trade-offs:** consumers handle two quantities; inconsistent pairs (Off with a positive percentage) are not prevented by the XSD and need a consumer or use-case policy.
+
+### Illustrative XML
+
+The following **proposed fragment** (encoding A, either structure) is not valid against the unchanged current schema and is not a complete document:
+
+```xml
+
+
+
+
+ Weekday
+ HVAC equipment
+ 06:00:00
+ 18:00:00
+
+ true
+ Operation
+
+
+
+ Weekday
+ HVAC equipment
+ 18:00:00
+ 22:00:00
+
+ false
+ Operation
+
+
+
+
+
+
+
+ Weekday
+ HVAC equipment
+ 05:00:00
+ 20:00:00
+
+ true
+ Availability
+
+
+
+
+
+```
+
+For encoding B, replace `true`/`false` with `On`/`Off`. Both schedules can be linked from a thermal zone through the existing [HVACScheduleIDs](../../BuildingSync.xsd#L1545-L1558) container:
+
+```xml
+
+
+
+
+```
+
+### Potential consumers and adoption
+
+| Consumer | Expected use | Current state and follow-up |
+| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **BOSS → OpenStudio (primary)** | Translate binary schedules to discrete 0/1 schedules (`ScheduleTypeLimits` On/Off) and apply them as `AirLoopHVAC`/plant-loop availability schedules, zone HVAC and terminal availability, fan operating-mode (continuous vs. cycling) schedules, exhaust fan and DHW recirculation availability, and exterior lighting on/off. | BOSS runtime schedule handling was not verified (searches found only XML fixtures). Follow-up: forward `BinarySchedule` (`BinaryValue`, `BinaryScheduleType`) in the payload BOSS builds. |
+| **buildingsync-measures-gem** | `ModifySchedules` applies schedules to the model, including `hvac_availability_schedule_json` → `setAvailabilitySchedule`. | [ModifySchedules](https://github.com/BuildingSync/buildingsync-measures-gem/blob/develop/lib/measures/modify_schedules/measure.rb) parses only numeric `value_percent`/`partialoperationpercentage`/`value`/`fraction`, divides percentages by 100, and uses Continuous fraction limits. Follow-up: a binary path with discrete limits that bypasses percentage normalization. |
+| **use-cases (ASHRAE 211 L200)** | Require HVAC operating schedules as `Operation` binary schedules instead of percentages. | [L200 rules](https://github.com/BuildingSync/use-cases/blob/main/ASHRAE_211/schematron/L200_Audit-1.0.0.sch) require `PartialOperationPercentage` on every detail. Follow-up: version-aware, category-aware rules; occupancy still needs percentages. |
+| **Audit Template / LL87 / other audit exports** | Report equipment operating hours as explicit On/Off intervals instead of time-only details. | Producer adoption; not verified. |
+| **BuildingSync-asset-extractor / SEED / Portfolio Manager** | Derive weekly operating hours by summing On intervals of `Operation` schedules. | No schedule reader verified; confirm before planning changes. |
+| **bsyncr / NMEC** | Occupied/operating-mode indicators as regression inputs. | Plausible; not verified. |
+| **Generated clients and BuildingSync-website** | Bindings, viewer, validator, enumeration export. | Require the released schema; verify after release. |
+
+Do not generate placeholder percentages to satisfy percentage-only consumers.
+
+### Verification and acceptance criteria
+
+After the design is selected, add focused regression contexts to [the validation spec](../../spec/validation_spec.rb) and one complete linked example. Construct invalid cases in tests rather than committing failing examples.
+
+| Area | Expected checks |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Legacy | All existing examples remain valid unchanged, including time-only details and small decimal percentages. |
+| `BinarySchedule` | Accept with both children in order; reject a missing `BinaryValue` or `BinaryScheduleType`, reversed order, duplicates, and `BinaryScheduleType` directly under `Schedule` or `ScheduleDetail`. |
+| `BinaryScheduleType` | Accept `Availability`, `Operation`, `Other`; reject other values and wrong casing. |
+| Encoding A | Accept `true`, `false`, `1`, `0`; reject `2`, `0.5`, `True`, `On`, empty, and `xsi:nil`. |
+| Encoding B | Accept only `On`, `Off`; reject `true`, `1`, `on`, `Available`, empty, and `xsi:nil`. |
+| Structure 1 | Reject percentage and `BinarySchedule` together; accept either alone or neither. |
+| Structure 2 | Accept both with percentage first; reject reversed order and duplicates. |
+| Provenance and context | Valid `auc:Source` accepted, invalid rejected; IDs, links, dates/times, and `Status` unchanged. |
+
+Implementation checks: `bundle exec rake remove_tabs`, `bundle exec rake`, `bundle exec rake generate_data_dictionary`, and `poetry run pre-commit run --all-files`. Do not commit generated artifacts.
+
+### Decision and scope
+
+- **Chosen approach:** generalized binary value plus meaning qualifier (option a), paired in a `ScheduleDetail/BinarySchedule` container.
+- **Pending:** value encoding (A or B) and structure (1 or 2).
+- **Labels:** `No Schema Changes` for the proposal-only PR; `Non-breaking Change` and `Schema: General` for the implementation. Reference #260 without closing it in the proposal PR.
+- **Out of scope:** measured run status (`TimeSeries`); changing or bounding percentage data; generalized numeric/temperature schedule types; interval/gap redesign; new links; version/changelog edits; external repository changes.
+
+## References
+
+- [BuildingSync/schema issue #260](https://github.com/BuildingSync/schema/issues/260).
+- [Original availability-versus-operation discussion in TestSuite #37](https://github.com/BuildingSync/TestSuite/pull/37#discussion_r496136378).
+- [BuildingSync versioning](../../docs/versioning.md).
+- [BuildingSync proposal process](../README.md).
+- [Existing schedule linking definitions](../../docs/linking_elements.md).