Data usage from cabin within seats

[PatrickSchmehl]

Request summary: The following list is a summary of data used or potentionally needed by passenger seats.

ATA Chapter: todo

Security Domain: crew, pax

Existing Types: none yet

Required data: The list is a first draft of all ideas from the seat group.

• [ ] Aircraft data - discussed in #7
• [ ] Light scenarios
• [ ] Seat commands: Cleaning, single motion commands - discussed in #3
• [ ] Window shades / blinds: status / control
• [ ] Lavatory: general status, occupied status, book slots
• [ ] Cabin status: fasten seat belts, no smoking, key service indication (next meal,…)
• [ ] Crew controls: attendant call, passenger announcements, TTL seat lock for TTL phase
• [ ] Maintenance features: self test mode, calibration, fault codes, cabin maintenance status
• [ ] Control of monuments: privacy divider
• [ ] Minibar replacements, meal choice, selection of meal
• [ ] Passenger: Do not disturb, wake for meal, preferred seat positions, passenger ID, menu content

[uwe-salomon]

@PatrickSchmehl for aircraft data:

• please provide more detail which data is needed, and
• please compare to the preliminary list of aircraft data in #7.

Then we can request additional data there, if items are missing.

[uwe-salomon]

For the seat commands, aren't these inputs to the seat objects? Then you could just add them to the object types defined in #3.