Difference between pages "ERP On Demand" and "E-ticketing"

From ADempiere
(Difference between pages)
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(just some essay.. for fun..)
 
(Team Members)
 
Line 1: Line 1:
=Disclaimer=
+
== Introduction ==
*This is a self authored essay and reflects only the limited experience of the signed author, and thus in no way authorised by the Bazaar nor indicative of any sales pitch to sway any member thereof from anything they are doing. Unless of course they are wasting their time reading. - [[User:Red1|Red1]] 22:21, 19 January 2008 (EST)
+
* This page is for the proposal of e-Ticketing system built-in inside ADempiere.
=Did It Heat Up?=
+
* Sponsored by Energetic Point Sdn Bhd
*As the saying goes, "A rose is a rose by any other name" or is it?[http://www.tash.org/pdf/turnbullpdfexch.pdf]
+
* Will be based on e-Ticketing for Express Bus service between cities
*This [[ASP]] or ''Application Service Provider'' concept is now reincarnated from its fallen past [http://en.wikipedia.org/wiki/Application_service_provider] as something sexy sounding such as [http://en.wikipedia.org/wiki/Software_as_a_service SaaS] (''Software As A Service'') which is more technically true, and even Application ''On Demand'' which seems to be more poetic sounding and impressive enough to shout out in a brainstorm meeting.
+
*There is a another ''concept phrase'' floated by ISPs (Internet Service Providers) a long time ago, which seems to ring well the ASP rhythm, is ''Apps On Taps'' that you do not hear often anymore. Hope you get the idea of what is going ''ON''.
+
  
*So, question is how hot is in our case, ''ERP On Demand'' getting? A simple [http://search.yahoo.com/search?p=ERP+On+Demand&ei=utf-8&fr=b1ie7 yahoo check] says it is.
+
== Team Members ==
 +
* Red1
 +
* [[User:Selpiso|Selpiso]]
 +
* [[User:Wariola|Wariola]]
 +
* Samsudin
 +
* Hafiz
 +
* Hafiz Zazlin
  
=So Will It Go Down?=
+
== Product Modeling ==
*But as these concepts stem from the disastrous need of throwing out the bathwater every time a baby is washed, they fall under a broader category called [http://en.wikipedia.org/wiki/Outsourcing Outsourcing].
+
* How many bus?
*We then can have a cursory examination of what can particularly in this area of ERP happens to pose an even higher risk than in-sourcing. [http://www.outsourcing-journal.com/aug2004-failure.html]
+
-- Model it on number of bus
*ERP as we know it is not something you can outsource or give away. It is not non-core IT activity. It is core business subject matter and that is core.
+
-- What is inside to measure? the seat.  
*The expectations of customers of ERP to think they can remove the pain away probably will give On Demand solutions an intial boost, but as the example of SAP associated CRM On Demand solution [http://www.salesforce.com SalesForce.com] has shown dramatic flight patterns when its profits plunge [http://www.theregister.co.uk/2007/02/22/salesforce_fourth_quarter/]. What more inadvertently giving away its customers' list. [http://www.eweek.com/c/a/Security/Salesforcecom-Employee-Hands-Customer-List-to-Phisher/]
+
-- ie; 1 bus = 20 seats = 20 ticket
  
=It is a Channel, Stupid=
+
* Route
*That is what Howard Smith seems to say in his blog. [http://salesforcedotbomb.blogspot.com/] It is still not a service. And service takes a different drawing board. It takes business concerns, which takes content, which takes expertise, which takes attention, which takes another business all together.
+
-- Location bus from Point A to Point B
*It is like what i often tell OS pundits that ''Free doesn't mean Free''. So now i have to introduce anoher phrase, ''Outsourcing your TCO doesn't mean you do not have another bigger TCO''.
+
-- ie: Kuala Lumpur to Skudai
*Don't take my word for it. Try SalesForce.com today. Then come back and sign below here.
+
* Trips
 +
-- How many trips in 1 day? 1 months?
 +
* Resource
 +
-- Petrol
 +
-- Driver
 +
-- Maintenance
 +
-- Insurance
  
=More Last Words=
+
== Conditional Rules Model ==
*Silence is not golden during outages. [http://blogs.zdnet.com/SAAS/?p=104][http://www.techworld.com/applications/news/index.cfm?NewsID=5390]
+
 
*Winning suits is one thing. But getting sued in the first place? [http://www.infoworld.com/article/05/12/23/HNsalesforcelawsuit_1.html]
+
 
*The paradox of been everything to everyone. [http://www.eweek.com/c/a/CRM/Salesforcecom-Needs-to-Focus-on-Fundamentals/]
+
== e-Ticketing System Flow ==
 +
 
 +
 
 +
== Customer View ==
 +
 
 +
 
 +
== Implementation ==
 +
 
 +
 
 +
== Future Roadmap ==
 +
 
 +
 
 +
== Interested? ==

Revision as of 23:54, 18 May 2009

Introduction

  • This page is for the proposal of e-Ticketing system built-in inside ADempiere.
  • Sponsored by Energetic Point Sdn Bhd
  • Will be based on e-Ticketing for Express Bus service between cities

Team Members

Product Modeling

  • How many bus?
-- Model it on number of bus
-- What is inside to measure? the seat. 
-- ie; 1 bus = 20 seats = 20 ticket
  • Route
-- Location bus from Point A to Point B
-- ie: Kuala Lumpur to Skudai
  • Trips
-- How many trips in 1 day? 1 months?
  • Resource
-- Petrol
-- Driver
-- Maintenance
-- Insurance

Conditional Rules Model

e-Ticketing System Flow

Customer View

Implementation

Future Roadmap

Interested?