vespolina-bus service product

[liuggio]

Hi all
sorry for this HUGE email,
but i'd love to merge our project with vespolina,
we have a mutual goal :)
we are an opensource team and we are really motivated,
i think we'll be the first that 'll publish a vespolina in a
production site.

Tomorrow I'll be in chat as said to "inspiran",
but i thought is better to give u some additional information,

Now the main problem is to figure out how to join our technical
specifications with vespolina

------------------------------

a "Journey" is a trip of a bus,
has a Departure stop
and an Arrival stop,
and has some "Ride" for each day,
and has some properties: kilometers

a "Ride" is bus ride,
is identified by:
1-a departure time eg. 18.00 (o2o)
2-a departure day eg. 10/12/2012 (o2o)
3-a journey (o2o)
Has a different prices for each customer type: Adult, infant,
children ...
has a preferred currency (eg london->manchester has £ as preferred
currency)

eg. Journey: 01, London->Manchester
Ride:
Day-> 1/1/2012
Time: 8:00,
Journey-> 01
prices: Adult:10£, Adult 13€, Children 8£, Children 10€ ...

Day-> 1/1/2012
Time: 9:15,
Journey-> 01
prices: Adult:10£, Adult 13€, Children 8£, Children 10€ ...

Day-> 1/1/2012
Time: 10:15,
Journey-> 01
prices: [Adult:10£, Adult 13€, Children 8£, Children 10€ ... ]

Use Case:
When a customer wants to book a Ride
A- he needs to pre-fill some information:
1- the number of passengers for each passengers type (adult
infant children etc)
2- when he want to use the bus-service (day)
3- departure and stop
(A4- there'are a heap of more information but i'll not write
here :) )
B- he has to choose a Ride from a timetable for that day
C- when he choose the Ride
he has to fill some information if the Ride needs some
additional information
eg some "Ride"s needs identity cart number
or hotel information
or Flight number
--------------
We need some great idea how to integrate our product and our cart item
with vespolina.

Thanks a lot

liuggio

[IamPersistent]

Off hand, I see a ride as a product (service might be a better name) and the journey, timetable and customer type as options.

I have the concept of option combinations that I'm ironing out the last of the details on right now (the code is in the ProductBundle). By using upcharges for the various combinations you can set different prices, however, if the price is only dependent on one option (customer type) then use the upcharge in the option. If you have other pricing requirement, let me know I'll bounce some more ideas.

Of course if you want to get into fulfillment then your fulfillment would be a ticket and you could have the options of a printed or electronic ticket, with the confirmation number being generated at the close of the sale.

[IamPersistent]

And you'll need an inventory type/manager that can handle a finite number of seats for each of the rides.

[liuggio]

Thanks a lot i'm starting studing this solution i'll let you know

thanks again

liuggio