seats/tables in a restaurant (or plane or cinema)

[hans_bakker]

Good day to everybody.

I need advice: in which entity would you store a "table with 4 seats" in
a certain restaurant which is reserved for a certain date and time?

Would facility with facility location be a possibility?

or should it be a fixed-asset (table for 4) for a date/time such as a
hotelroom?

what is the best way to go?

We need a seat numbering because a customer asks a table near the window
which we know is either table 3,4,5

what about when we have plane-seats or bus-seats or cinema-seats with a
floorplan?

Regards,
Hans


--
AntWebsystems.com: Quality OFBiz services for competitive rates.....

[Jacopo Cappellato]

Hi Hans,

did you already consider to use rental products for this?

Jacopo

Hans Bakker wrote:

> Good day to everybody.
>
> I need advice: in which entity would you store a "table with 4 seats" in
> a certain restaurant which is reserved for a certain date and time?
>
> Would facility with facility location be a possibility?
>
> or should it be a fixed-asset (table for 4) for a date/time such as a
> hotelroom?
>
> what is the best way to go?
>
> We need a seat numbering because a customer asks a table near the window
> which we know is either table 3,4,5
>
> what about when we have plane-seats or bus-seats or cinema-seats with a
> floorplan?
>
> Regards,
> Hans
>
>

[Bilgin Ibryam]

Hi Hans,

The restaurant could be a facility, and the tables could be fixed assets
located at that facility on the specified location(fixed assets also has
location field). You can go even further and add a fixed asset for every
chair and assign it to the table as child fixed asset. Production
capacity field can be used to store the number of chairs for every
table.

About plane-seats or bus-seats or cinema-seats, i think it is explained
in Data Model Resource Book v2 page 370. May be it is time to import
these entities into OFBiz?

I believe, the best way for OFBiz would be to import these entities from
Data Model Resource Book, and use a common model for storing all kind of
reservations - room, table, cinema etc. But obviously this is a lot of
work...

Regards,
Bilgin

[David E Jones]

On Jan 16, 2008, at 2:49 AM, Bilgin Ibryam wrote:

> Hi Hans,
>
> The restaurant could be a facility, and the tables could be fixed  
> assets
> located at that facility on the specified location(fixed assets also  
> has
> location field). You can go even further and add a fixed asset for  
> every
> chair and assign it to the table as child fixed asset. Production
> capacity field can be used to store the number of chairs for every
> table.
>
> About plane-seats or bus-seats or cinema-seats, i think it is  
> explained
> in Data Model Resource Book v2 page 370. May be it is time to import
> these entities into OFBiz?
>
> I believe, the best way for OFBiz would be to import these entities  
> from
> Data Model Resource Book, and use a common model for storing all  
> kind of
> reservations - room, table, cinema etc. But obviously this is a lot of
> work...

It shouldn't be too much work, probably not compared with trying to  
shoe-horn those concepts into entities with other purposes where it  
doesn't quite fit.

I agree this is the approach to go with. I don't have my books nearby  
to look it up, but if someone wants to write up entities I'd be happy  
to review them.

-David

[Valentina Sirkova]

Hans, everyone,

In my opinion the seat/table numbering problematic could be solved with
the help of the entities AccommodationClass, AccommodationMap  described
in the book vol2.I will give you a short description of these entities
and example of the "numbering issue" solution.

AccommodationClass - description:
It is designed to store classes information(these could be plane, bus
classes, table types, chair types, room types etc)
AccommodationClass - definition(based on the book but modified a little)
fields: accClassId, parentAccClassId, description

AccommodationMap - description:
Its idea is to provide information of the number of spaces offered by a
fa/accClass. Here we can extend it to provide overbooking information
and seat numbering information(the last two fields in the definition
below)
fields: mapId, accClassId, faId, nrOfSpaces, overBooked, number

Example:
Define two tables.
 - Table number 5 has 3 chairs. Chair with number 1 is baby_chair. The
other two chairs with number 2 and 3 are high_chairs.
 - Table number 9 has 2 chairs. Chairs number 1 and 2 are normal_chairs.

In FixedAsset relate the tables to the chairs.
FixedAsset:fixedAssetId=table1
FixedAsset:fixedAssetId=table2
FixedAsset:fixedAssetId=chair11, parentFixedAssetId=table1 //chair11
belongs to table1
FixedAsset:fixedAssetId=chair12, parentFixedAssetId=table1 //chair12
belongs to table1
FixedAsset:fixedAssetId=chair13, parentFixedAssetId=table1 //chair13
belongs to table1
FixedAsset:fixedAssetId=chair14, parentFixedAssetId=table2 //chair14
belongs to table2
FixedAsset:fixedAssetId=chair15, parentFixedAssetId=table2 //chair15
belongs to table2

In Accommodationclass define the table/chair classes.
AccommodationClass: accClassId=tables
AccommodationClass: accClassId=chairs
AccommodationClass: accClassId=plane_classes
AccommodationClass: accClassId=baby_chair,    parentAccClassId=chairs;
AccommodationClass: accClassId=high_chair,    parentAccClassId=chairs;
AccommodationClass: accClassId=normal_chair,  parentAccClassId=chairs;


In AccommodationMap define how many places each table or chair has and
which is its number.
AccommodationMap: accClassId=tables,        fixedAssetId=table1,
nrOfSpaces=3, number=5 //table number 5 has 3 chairs(faId=table1)
AccommodationMap: accClassId=baby_chair,    fixedAssetId=chair11,
nrOfSpaces=1, number=1 //chair number 1 has one place(faId=chair11)
AccommodationMap: accClassId=high_chair,    fixedAssetId=chair12,
nrOfSpaces=1, number=2 //chair number 2 has one place(faId=chair12)
AccommodationMap: accClassId=high_chair,    fixedAssetId=chair13,
nrOfSpaces=1, number=3 //chair number 3 has one place(faId=chair13)
AccommodationMap: accClassId=tables,        fixedAssetId=table2,
nrOfSpaces=2, number=9 //table number 9 has two places(faId=table2)
AccommodationMap: accClassId=normal_chair,  fixedAssetId=chair14,
nrOfSpaces=1, number=1 //chair number 1 has one place(faId=chair14)
AccommodationMap: accClassId=normal_chair,  fixedAssetId=chair15,
nrOfSpaces=1, number=2 //chair number 2 has one place(faId=chair15)

In similar fashion you can define theaters, planes etc.Also overbooking
data could be kept in the AccommodationMap entity which could be used
for hotel reservations. Hourly reservations could be enabled as well
with the introduction of the AccommodationSpot entity. If you are
interested I can provide a patch. Should I create issue and patch or
just paste it here?

[hans_bakker]

Hi Valentina and others,

I have created a wiki page where we can discuss this further:
http://docs.ofbiz.org/x/aA4

please feel free to add your text below and patch to this document

Regards,
Hans


On Wed, 2008-01-16 at 21:17 +0200, Valentina Sirkova wrote:

> Hans, everyone,
>
> In my opinion the seat/table numbering problematic could be solved with
> the help of the entities AccommodationClass, AccommodationMap  described
> in the book vol2.I will give you a short description of these entities
> and example of the "numbering issue" solution.
>
> AccommodationClass - description:
> It is designed to store classes information(these could be plane, bus
> classes, table types, chair types, room types etc)
> AccommodationClass - definition(based on the book but modified a little)
> fields: accClassId, parentAccClassId, description
>
> AccommodationMap - description:
> Its idea is to provide information of the number of spaces offered by a
> fa/accClass. Here we can extend it to provide overbooking information
> and seat numbering information(the last two fields in the definition
> below)
> fields: mapId, accClassId, faId, nrOfSpaces, overBooked, number
>
> Example:
> Define two tables.
>  - Table number 5 has 3 chairs. Chair with number 1 is baby_chair. The
> other two chairs with number 2 and 3 are high_chairs.
>  - Table number 9 has 2 chairs. Chairs number 1 and 2 are normal_chairs.
>
> In FixedAsset relate the tables to the chairs.
> FixedAsset:fixedAssetId=table1
> FixedAsset:fixedAssetId=table2
> FixedAsset:fixedAssetId=chair11, parentFixedAssetId=table1 //chair11
> belongs to table1
> FixedAsset:fixedAssetId=chair12, parentFixedAssetId=table1 //chair12
> belongs to table1
> FixedAsset:fixedAssetId=chair13, parentFixedAssetId=table1 //chair13
> belongs to table1
> FixedAsset:fixedAssetId=chair14, parentFixedAssetId=table2 //chair14
> belongs to table2
> FixedAsset:fixedAssetId=chair15, parentFixedAssetId=table2 //chair15
> belongs to table2
>
> In Accommodationclass define the table/chair classes.
> AccommodationClass: accClassId=tables
> AccommodationClass: accClassId=chairs
> AccommodationClass: accClassId=plane_classes
> AccommodationClass: accClassId=baby_chair,    parentAccClassId=chairs;
> AccommodationClass: accClassId=high_chair,    parentAccClassId=chairs;
> AccommodationClass: accClassId=normal_chair,  parentAccClassId=chairs;
>
>
> In AccommodationMap define how many places each table or chair has and
> which is its number.
> AccommodationMap: accClassId=tables,        fixedAssetId=table1,
> nrOfSpaces=3, number=5 //table number 5 has 3 chairs(faId=table1)
> AccommodationMap: accClassId=baby_chair,    fixedAssetId=chair11,
> nrOfSpaces=1, number=1 //chair number 1 has one place(faId=chair11)
> AccommodationMap: accClassId=high_chair,    fixedAssetId=chair12,
> nrOfSpaces=1, number=2 //chair number 2 has one place(faId=chair12)
> AccommodationMap: accClassId=high_chair,    fixedAssetId=chair13,
> nrOfSpaces=1, number=3 //chair number 3 has one place(faId=chair13)
> AccommodationMap: accClassId=tables,        fixedAssetId=table2,
> nrOfSpaces=2, number=9 //table number 9 has two places(faId=table2)
> AccommodationMap: accClassId=normal_chair,  fixedAssetId=chair14,
> nrOfSpaces=1, number=1 //chair number 1 has one place(faId=chair14)
> AccommodationMap: accClassId=normal_chair,  fixedAssetId=chair15,
> nrOfSpaces=1, number=2 //chair number 2 has one place(faId=chair15)
>
> In similar fashion you can define theaters, planes etc.Also overbooking
> data could be kept in the AccommodationMap entity which could be used
> for hotel reservations. Hourly reservations could be enabled as well
> with the introduction of the AccommodationSpot entity. If you are
> interested I can provide a patch. Should I create issue and patch or
> just paste it here?
>
>

--
AntWebsystems.com: Quality OFBiz services for competitive rates.....

[Valentina Sirkova]

Hans and all,

In the next days I will prepare some text,patch/patches and
pictures(schemas) for this wiki page.
One of the pictures will show the book`s original ideas and the other
will show my personal vision of these entities and how they should be
enhanced to fit best into the OFBiz project.
I do not say that this(my) vision about the entities is the best way to
go. After posting in wiki, I will wait for the community`s feedback and
suggestions to make common decision.

Thanks: Valentina  

[hans_bakker]

Hi Valetina,

I appreciate you answer and wait for your contribution.

Regards,
Hans

On Thu, 2008-01-17 at 13:42 +0200, Valentina Sirkova wrote:

> Hans and all,
>
> In the next days I will prepare some text,patch/patches and
> pictures(schemas) for this wiki page.
> One of the pictures will show the book`s original ideas and the other
> will show my personal vision of these entities and how they should be
> enhanced to fit best into the OFBiz project.
> I do not say that this(my) vision about the entities is the best way to
> go. After posting in wiki, I will wait for the community`s feedback and
> suggestions to make common decision.
>
> Thanks: Valentina  
>
>

--
AntWebsystems.com: Quality OFBiz services for competitive rates.....

[Valentina Sirkova]

Hi David and all,

As you showed interest to reservation entities, I made issue for these
entities https://issues.apache.org/jira/browse/OFBIZ-1590 
Hans created wiki page here http://docs.ofbiz.org/display/OFBIZ/Proposal
+for+Plane%2C+Bus%2C+Restaurant+and+Cinema+Seats where we share ideas.

Valentina

[David E Jones]

Thanks Valentina, I'll try to take a look at this in the near future.

-David


On Jan 21, 2008, at 9:41 PM, Valentina Sirkova wrote:

> Hi David and all,
>
> As you showed interest to reservation entities, I made issue for these
> entities https://issues.apache.org/jira/browse/OFBIZ-1590
> Hans created wiki page here http://docs.ofbiz.org/display/OFBIZ/Proposal
> +for+Plane%2C+Bus%2C+Restaurant+and+Cinema+Seats where we share ideas.
>
> Valentina
>

[Shi Yusen]

+1

We use rental products for meeting rooms, Ad positions and labs.

Shi Yusen/Beijing Langhua Ltd.


在 2008-01-16三的 09:55 +0100，Jacopo Cappellato写道：

> Hi Hans,
>
> did you already consider to use rental products for this?
>
> Jacopo
>
> Hans Bakker wrote:
> > Good day to everybody.
> >
> > I need advice: in which entity would you store a "table with 4 seats" in
> > a certain restaurant which is reserved for a certain date and time?
> >
> > Would facility with facility location be a possibility?
> >
> > or should it be a fixed-asset (table for 4) for a date/time such as a
> > hotelroom?
> >
> > what is the best way to go?
> >
> > We need a seat numbering because a customer asks a table near the window
> > which we know is either table 3,4,5
> >
> > what about when we have plane-seats or bus-seats or cinema-seats with a
> > floorplan?
> >
> > Regards,
> > Hans
> >
> >
>