You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

casestudies.xml 12KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. ====================================================================
  4. Licensed to the Apache Software Foundation (ASF) under one or more
  5. contributor license agreements. See the NOTICE file distributed with
  6. this work for additional information regarding copyright ownership.
  7. The ASF licenses this file to You under the Apache License, Version 2.0
  8. (the "License"); you may not use this file except in compliance with
  9. the License. You may obtain a copy of the License at
  10. http://www.apache.org/licenses/LICENSE-2.0
  11. Unless required by applicable law or agreed to in writing, software
  12. distributed under the License is distributed on an "AS IS" BASIS,
  13. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  14. See the License for the specific language governing permissions and
  15. limitations under the License.
  16. ====================================================================
  17. -->
  18. <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "./dtd/document-v13.dtd">
  19. <document>
  20. <header>
  21. <title>Apache POI - Case Studies</title>
  22. <authors>
  23. <person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
  24. <person id="CR" name="Cameron Riley" email="crileyNO@SPAMekmail.com"/>
  25. <person id="DF" name="David Fisher" email="dfisher@jmlafferty.com"/>
  26. </authors>
  27. </header>
  28. <body>
  29. <section>
  30. <title>Introduction</title>
  31. <p>
  32. A number of people are using POI for a variety of purposes. As with
  33. any new API or technology, the first question people generally ask
  34. is not "how can I" but rather "Who else is doing what I'm about to
  35. do?" This is understandable with the abysmal success rate in the
  36. software business. These case statements are meant to help create
  37. confidence and understanding.
  38. </p>
  39. </section>
  40. <section>
  41. <title>Submitting a Case Study</title>
  42. <p>
  43. We are actively seeking case studies for this page (after all it
  44. just started). To submit a case study, either
  45. <link href="getinvolved/index.html">
  46. submit a patch for this page</link> or email it to the
  47. <link href="mailinglists.html">mailing list
  48. </link> (with [PATCH] prefixed subject, please).
  49. </p>
  50. </section>
  51. <section>
  52. <title>Case Studies</title>
  53. <section><title>QuestionPro</title>
  54. <p>
  55. <link href="http://www.questionpro.com">QuestionPro</link> is an online service allowing businesses and individuals to create, deploy and do in-depth analysis of Online Surveys. The technology is build on open-source frameworks like Struts, Velocity, POI, Lucene ... the List goes on. The application deployment is on a Linux Application Cluster farm with a Mysql database.
  56. </p>
  57. <p>
  58. There are quite a few competitors delivering similar solutions using Microsoft Technologies like asp and .net. One of the distinct advantages our competitors had over us was the ability to generate Excel Spreadsheets, Access Databases (MDB) etc. on the fly using the Component Object Model (COM) - since their servers were running IIS and they had access to the COM registry and such.
  59. </p>
  60. <p>
  61. QuestionPro's initial solution was to generate CSV files. This was easy however it was a cumbersome process for our clients to download the CSV files and then import them into Excel. Moreover, formatting information could not be preserved or captured using the CSV format. This is where POI came to our rescue. With a POI based solution, we could generate a full report with multiple sheets and all the analytical reports. To keep the solution scalable, we had a dedicated cluster for generating out the reports.
  62. </p>
  63. <p>
  64. The Apache-POI project has helped QuestionPro compete with the other players in the marketplace with proprietary technology. It leveled the playing field with respect to reporting and data analysis solutions. It helped in opening doors into closed solutions like Microsoft's CDF. Today about 100 excel reports are generated daily, each with about 10-30 sheets in them.
  65. </p>
  66. <p>
  67. Vivek Bhaskaran
  68. </p>
  69. <p>
  70. <link href="http://www.questionpro.com">QuestionPro, Inc</link>
  71. </p>
  72. <p>
  73. POI In Action - <link href="http://www.questionpro.com/marketing/SurveyReport-289.xls">http://www.questionpro.com/marketing/SurveyReport-289.xls</link>
  74. </p>
  75. </section>
  76. <section><title>Sunshine Systems</title>
  77. <p>
  78. <link href="http://www.sunshinesys.com/">Sunshine Systems</link> deveveloped a
  79. POI based reporting solution for a price optimization software package which
  80. is used by major retail chains.
  81. </p>
  82. <p>The solution allowed the retailer's merchandise planners and managers to request a
  83. markdown decision support reports and price change reports using a standard browser
  84. The users could specify report type, report options, as well as company,
  85. division,
  86. and department filter criteria. Report generation took place in the
  87. multi-threaded
  88. application server and was capable of supporting many simultaneous report requests.
  89. </p>
  90. <p>The reporting application collected business information from the price
  91. optimization
  92. application's Oracle database. The data was aggregated and summarized
  93. based upon the
  94. specific report type and filter criteria requested by the user. The
  95. final report was
  96. rendered as a Microsoft Excel spreadsheet using the POI HSSF API and
  97. was stored on
  98. the report database server for that specific user as a BLOB. Reports
  99. could be
  100. seamlessly and easily viewed using the same browser.
  101. </p>
  102. <p>The retailers liked the solution because they had instantaneous access
  103. to critical
  104. business data through an extremely easy to use browser interface. They
  105. did not need
  106. to train the broader user community on all the complexities of the optimization
  107. application. Furthermore, the reports were generated in an Excel spreadsheet
  108. format,
  109. which everyone was familiar with and which also allowed further data
  110. analysis using
  111. standard Excel features.
  112. </p>
  113. <p>Rob Stevenson (rstevenson at sunshinesys dot com)
  114. </p>
  115. </section>
  116. <section>
  117. <title>Bank of Lithuania</title>
  118. <p>
  119. The
  120. <link href="http://www.lbank.lt/">Bank of Lithuania</link>
  121. reports financial statistical data to Excel format using the
  122. <link href="http://poi.apache.org/">Apache POI</link>
  123. project's
  124. <link href="spreadsheet/">
  125. HSSF</link> API. The system is based on Oracle JServer and
  126. utilizes a Java stored procedure that outputs to XLS format
  127. using the HSSF API. - Arian Lashkov (alaskov at lbank.lt)
  128. </p>
  129. </section>
  130. <!-- <section>-->
  131. <!-- <title>Bit Tracker by Tracker Inc., and ThinkVirtual</title>-->
  132. <!-- <p>-->
  133. <!-- Bit Tracker (http://www.bittracker.com/) is the world's first and only web-based drill bit tracking system to manage your company's critical bit information and use that data to its full potential. It manages all bit related data, including their usage, locations, how they were used, and results such as rate of penetration and dull grade after use. This data needs to be available in Excel format for backwards compatibility and other uses in the industry. After using CSV and HTML formats, we needed something better for creating the spreadsheets and POI is the answer. It works great and was easy to implement. Kudos to the POI team.-->
  134. <!-- </p>-->
  135. <!-- <p>-->
  136. <!-- Travis Reeder (travis at thinkvirtual dot com)-->
  137. <!-- </p>-->
  138. <!-- </section>-->
  139. <section>
  140. <title>Edwards And Kelcey Technology</title>
  141. <p>
  142. Edwards and Kelcey Technology (http://www.ekcorp.com/) developed a
  143. Facility
  144. Managament and Maintenance System for the Telecommunications industry
  145. based
  146. on Turbine and Velocity. Originally the invoicing was done with a simple
  147. CSV
  148. sheet which was then marked up by accounts and customized for each client.
  149. As growth has been consistent with the application, the requirement for
  150. invoices that need not be touched by hand increased. POI provided the
  151. solution to this issue, integrating easily and transparently into the
  152. system. POI HSSF was used to create the invoices directly from the server
  153. in
  154. Excel 97 format and now services over 150 unique invoices per month.
  155. </p>
  156. <p>
  157. Cameron Riley (crileyNO@ SPAMekmail.com)
  158. </p>
  159. </section>
  160. <section>
  161. <title>ClickFind</title>
  162. <p>
  163. <link href="http://www.clickfind.com/">ClickFind Inc.</link> used the POI
  164. projects HSSF API to provide their medical
  165. research clients with an Excel export from their electronic data
  166. collection web service Data Collector 3.0. The POI team's assistance
  167. allowed ClickFind to give their clients a data format that requires less
  168. technical expertise than the XML format used by the Data Collector
  169. application. This was important to ClickFind as many of their current
  170. and potential clients are already using Excel in their day-to-day
  171. operations and in established procedures for handling their generated
  172. clinical data. - Jared Walker (jared.walker at clickfind.com)
  173. </p>
  174. </section>
  175. <section>
  176. <title>IKAN Software NV</title>
  177. <p>In addition to Change Management and Database Modelling, IKAN Software NV
  178. (http://www.ikan.be/) develops and supports its own ETL
  179. (Extract/Transform/Load) tools.</p>
  180. <p>IKAN's latest product is this domain is called ETL4ALL
  181. (http://www.ikan.be/etl4all/). ETL4ALL is an open source tool
  182. allowing data transfer from and to virtually any data source. Users can
  183. combine and examine data stored in relational databases, XML databases, PDF
  184. files, EDI, CSV files, etc.
  185. </p>
  186. <p>It is obvious that Microsoft Excel files are also supported.
  187. POI has been used to successfully implement this support in ETL4ALL.</p>
  188. </section>
  189. <section>
  190. <title>JM Lafferty Associates, Inc.</title>
  191. <p>
  192. On its <link href="http://www.forecastworks.com/public/">ForecastWorks</link> website
  193. <link href="http://www.jmlafferty.com/">JM Lafferty Associates, Inc.</link> produces dynamic on demand
  194. financial analyses of companies and institutional funds. The pages produced are selected and exported
  195. in several file formats including PPT and XLS.
  196. </p>
  197. <ul>
  198. <li>The PPT files produced are of high quality which is on a par with similar PDF files.</li>
  199. <li>The XLS files produced contain a complex forecasting model built from a template with a VBA Macro.</li>
  200. </ul>
  201. <p>
  202. David Fisher (dfisher@jmlafferty.com)
  203. </p>
  204. </section>
  205. </section>
  206. </body>
  207. <footer>
  208. <legal>
  209. Copyright (c) @year@ The Apache Software Foundation All rights reserved.
  210. </legal>
  211. </footer>
  212. </document>