Orient EuroPharma deployed Traction® TeamPage in the year 2005 to address critical communication issues within the company. The deployment is supported by our partner, Applied Knowledge Company, in Japan. As of the date of this case study, March 2009, the focus on internal communications, market intelligence and document sharing has thrived and spread from the IT department throughout the organization. This interview with Orient Europharma discusses their background, the problems which led them to deploy Traction TeamPage, and the benefits they’ve experienced as a result.
OEP is a multinational pharmaceutical and nutritional company, headquarter located in Taipei, Taiwan. We also have branch offices in Hong Kong, Singapore, Malaysia, Philippines and China. Our operation has covered several Far-Eastern countries. Our company is founded in 1982 and has over 25 years of pharmaceutical marketing experience in these territories. Our company's annual turnover is over USD $100 million. We are a public company and our shares are traded in Taiwanese Over-the-Counter stock exchange market. You are more than welcome to visit our website: oep.com.tw
Problems before introducing Traction TeamPage 引進前的問題
Unexpected communication mistakes resulting from the use of email. Problems with email include (1) the pain and distraction of mass email messages (2) time delay in sending and receiving messages (3) mistakes in the shared information and (4) internet delays.
Expectations after introducing Traction TeamPage 引進後的結果
After initial Teampage application testing, we deployed it easily in 2005. We sought to centralize information, improve the process of capturing and timely distribution of information.
How the technology was identified and chosen? 此類的技術如何被認同且被選擇?
We chose Teampage for our blog solution not only because its features exactly match our enterprise’s operations functions, but also because it deployed easily and has good support for team work.
How many months did you evaluate before deciding to choose Traction TeamPage? 經過幾個月的測試你才決定引進TEAMPAGE?
In the year 2005 we searched blog application options as a means to strengthen our operation in communication of documents and other information. After testing TeamPage for one month, we found it fit our needs. First we started with a 50 user license. In the second year, we upgraded to 150 users.
What was done with Traction TeamPage to solve the problems faced by the company? 使用Traction TeamPage之後解決了什麼問題?
1. Faster communication (better than Email) 快速的溝通速度(比郵件好又相戶搭配)
2. User friendly search with any of three ways to find information; by date, by project, by label 易操作的資料找尋方式，僅需三步驟即可完成(依據日期，專案或是標籤)
3. No delay in message communication 沒有訊息溝通上的延遲
4. Centralization of Data 集中管理的資料庫
5. Good permission controls for administrators to allow or deny access to information 容易存取以及控制權限的方式讓管理員容易去做設定
What business benefits have been obtained? 何種商業上的優點已獲得認同
Teampage is now our internal communication tool. We use it to strength our relationships across each of our departments. It is easy to access data from Teampage.
Did you have any problems until introducing Traction TeamPage ? 引進Traction TeamPage後有沒有遇到任何問題?
We have not experienced any problems introducing and deploying Traction TeamPage. When needed, we ask Applied Knowledge Co (AKJ) to support or we consult the Traction TeamPage documentation.
到目前為止，我們只要遇到問題都會請AKJ來支援，或者透過Tractio溝通平臺的方式來解決問題
Training 訓練課程
Have you conducted Traction TeamPage training courses for your employees? 你有沒有甚麼針對Traction TeamPage的訓練課程?
No.無
Expansion of the Deployment 附加功能
How has the use of the technology evolved and branched out? 技術使用上是如何進步且拓展出去?
Yes, I trust TeamPage will be a good tool for many use cases, and king of solutions in Competitive Intelligence field.
