OpenSource for Enterprise Business Presentation 010
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,719
On Slideshare
1,656
From Embeds
63
Number of Embeds
2

Actions

Shares
Downloads
30
Comments
0
Likes
0

Embeds 63

http://champillon.wordpress.com 62
http://www.slideshare.net 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. OpenSource for Enterprise Business On 4 February 2010, KMITL By Passapong Thaithatgoon Software Architect, Somewhere Commercial Bank. E-mail: [email_address] Twitter: @champillon
  • 2. Agenda
    • Enterprise Business?
    • 3. OpenSource?
    • 4. Case Study
    • 5. OpenSouce Community in Thailand
  • 6. Enterprise Business?
    • Need of Enterprise Business
      • Correctness
      • 7. Stability
      • 8. Long-Term Support
      • 9. Scalability
    “ Proven Software” “ Site References”
  • 10. Enterprise Business?
  • 11. Enterprise Business?
  • 12. Enterprise Business?
  • 13. Enterprise Business? Prove?
  • 14. OpenSource?
  • 15. OpenSource?
      Definition “ Practices in product and development that promote access to the end of product's source materials.” (Wikipedia)
    Never Die? Source Code Share to the World Source Code Update Source Code
  • 16. OpenSource?
      OpenSoure in Vertical view?
    Cover in all Software Stacks Hardware Hypervisor (Virtualization Platform) Operating System Application Environment Desktop Environment Applications User Interface Program
  • 17. OpenSource?
      OpenSource in Horizontal view?
    wide Range for Enterprise Architecture
  • 18. OpenSource?
    • Why OpenSource?
      • Correctness: Choose only proven OpenSouce
      • 19. Stability: Proven OpenSouce have many Site References which show it's stability
      • 20. Long-Term Support: Proven OpenSouce have a big community who always share their experiences and support each others.
      • 21. Scalability: Proven OpenSouce is software that handle high-volume transaction.
    so use only Proven OpenSources
  • 22. Case Study
    • Knowledge Tree
      • Problem: want to have the document management system which can
        • Control Authorization by Group and Role
        • 23. Full-text Search
        • 24. Approval Workflow with e-Mail notification
        • 25. Integrated authentication with Microsoft Active Directories
        • 26. Web-based Application
        • 27. Easy to use!!
      • We are looking for the commercial product !!
    Documentum
  • 28. Case Study
    • Knowledge Tree (Cont.)
      • Documentum cost x,xxx,xxx bahts!!
      • 29. So we make a decision:
        • Document management system is nice to have but not need
        • 30. Is documentum cost effective?
        • 31. There is a procurement process about 3 months!!
      • With this reason, we change from commercial to OpenSource with this candidates:
        • Alfresco
        • 32. Knowledge Tree
  • 33. Case Study
    • Knowledge Tree (Cont.)
      • We compare Alfresco and Knowledge Tree
    Criteria Alfresco Knowledge Tree 1. Group and Role Authorization T T 2. Full-text search T T 3. Approval Workflow T T 4. Integrated Authentication with AD T T 5. Web-based Application T T 6. Easy to use T T 7. Programming Language Java PHP 8. Interoperability Good Normal We choose PHP because easy to find staff
  • 34. Case Study
    • Knowledge Tree (Cont.)
      • Present Status:
        • Production with Real-time backup
        • 35. Implementing Load-Sharing
        • 36. Planning for DR
        • 37. Show this case study to Group
        • 38. Group want us to pilot this in other country
  • 39. Case Study
    • SugarCRM
      • Problem: want to have consolidate data for each customer from every system in Bank to generate the customer portal for our branch staffs.
      • 40. We think about Sale-forced automation
      • 41. We let them explore on www.salesforce.com
      • 42. They like www.salesforce.com but don't have money LoL......
      • 43. We show SugarCRM to them.
  • 44. Case Study
    • SugarCRM (Cont.)
      • We have to make the customer portfolio in SugarCRM with in 3 months.
      • 45. We can do it with Module Builder in SugarCRM which is drag-and-drop e-Forms generator.
  • 46. Case Study
    • SugarCRM (Cont.)
      • Present Status:
        • Now we have a customer portfolio system to support our sales at branch.
        • 47. Other countries in Group spend about x,xxx,xxx bahts for this system but we make it with no software cost.
        • 48. We have daily back up and can restore in 1hour.
        • 49. We use only 2 staffs for this project
  • 50. Case Study
    • Approval Workflow
      • As we have learnt e-Forms tool from SugarCRM, we apply this concept to other system which need approval workflow.
      • 51. Problem: need a e-Form to send a approved data from branch to head quarter to replace the manual process.
      • 52. We use configed SugarCRM e-Forms tool to make a simple approval workflow then interface this data to our Lotus Notes.
  • 53. Case Study
    • Approval Workflow (Cont.)
      • We reduce the approval time from 7 days to 2 hours.
      • 54. We use only 1 staff (me) to implement this system in 1 month.
      • 55. We have daily back up and can restore in 1 hour.
  • 56. Q&A Question & Answer Thank you.