Erik Jaegervall (Jägervall)

MoM: - Erik presented the PR - Pierre Pierre: We are interested, will check with internal subject matter experts - Please review

Note - to be reopened - upstream repo deleted by mistake

MoM: - Pierre Pierre - no update yet - Adnan: Check if interest, looks promising - Continue discussion next week

@adobekan - we could add this for "seat" instead so you could use it for all seats/persons if you think that might be useful in the future. I am not...

> > That would be good i think to model on seat level. When it comes position i was just thinking do we have to say what type of position...

PR updated after comments that it would be good to have data on all seats (for all occupants). This has been done by: - Reusing the existing `Occupant` branch, i.e....

Something I think we should discuss - do we want occupant data to remain with Cabin/Seats? That gives quite long paths, and theoretically a single seat may serve multiple passengers....

MoM: From Daniel: ``` Seat.Occupant or Occupant.SeatenOn ? Instead of that, you model SeatOccupancy that has pointers to the seat and the person ``` - Continue discussion - After AMM...

MoM: - Add a comment that this can be used to Euro NCAP evaluation - Merge decision week next

MoM: - OK to merge when suggested change fixed