CHAPTER 4. INTERACTION PATTERN BASED INNOVATION
4.7 Annotation Module
國
立 政 治 大 學
‧
N a tio na
l C h engchi U ni ve rs it y
72
examination, Figure 4.14 provides an algorithm of the adjustment direction dividing and proper case selection.
After SME users choose its most favorite case example regarding to its service innovation direction, SME users are supposed to be able to reference the company in the case example to do their service innovation by changing its interaction pattern with other entities within the SME user’s current service system.
4.7 Annotation Module
During the adjusting module, most of the adjustments are made by the SME users, and the system provides limited guidance. But for some situation, the system has to do more; for example, if the SME users are not able to provide the information of the entities within the service system, the SME users will need the system to help them with. The existing modules in this information system are not designed to provide this service to the SME users, so another module is required to fulfill this requirement.
Annotation module is designed to meet this need; explanation of implementation will be present in afterwards paragraphs, and the purpose of the module is as following:
Provide on-time support of what kind of entity might be related to the SME users and the name and information of the entity, upon SME users inputting data into the data collection module to provide more support to the SME users.
To provide SME users with the information they need, the information system need a database with required data firstly. Information needed here is the association of each entity within each industry, the connection of the entities and the detail of the entities (see table 4.5 for example). However, since each industry has their own features; to collect information by us only is not feasible and another method must be chosen. There are two methods that might be appropriate: the first one is to use the
‧
國立 政 治 大 學
‧
N a tio na
l C h engchi U ni ve rs it y
73
search engine to collect the information automatically, and the second one is by collecting data through other SME user’s input.
The search engine approach advantages include: it collects the data automatically and has massive data, and it is adequate for the information system design. However, the information needs to be examined and checked before providing to the SME users, and some detail information like the connection between two entities might not be able to be found on the internet. Also, since everyone can access to a good search engine, these information might not be able to provide too much uniqueness. So the search engine approach shall be considered later.
Table 4.5 Information required for the system to provide support for the SME users Entity’s Name
Entity role it might play in SME user’s service system for SME
Entity Providing Service (ex: Logistics) Entity’s Region
Company’s Detail
The approach to collect data through other SME users is to record each SME users’
input data. For example, another SME users might input 10 entities information during the input process, and these 10 entities and the relation with the SME users will be recorded in the system and these information can provide other SME users as a hint and support during their data input process. This can be considered as another case base methodology, in which the case used here is to collect through other users.
The advantages of using this approach are just counter to the disadvantages of using the search engine approach, with which these information are only accessible through
‧
國立 政 治 大 學
‧
N a tio na
l C h engchi U ni ve rs it y
74
this information system and the information is trustable since it is another SME users condition and these features makes these information more valuable and convincible.
For connecting to the entire project design, the SME users will come out a story of an image at the end, and the image will pass down to the uVoyage system, which we can refer as the implementation work of the story. After implementation, the uVoyage system will record the implementation detail, which we can see as another case of SME doing service innovation; this information can be provided to this information system to give the coming SME users more support and hints throughout the information system using. Concluding the comparison, it will be better to use the information inputted by other SME users because it can provide more precise and convincible unique data to the SME users.
Examples of how the annotation module help the SME users during the data collection module is presented in Figure 4.15, in which dotted broader and black background entity is the suggestion from the annotation module based on other SME users input.
After the data is collected, the system will be able to provide support to the SME users during the adjusting module, the annotation module will function while the SME users are doing the adjustment of interaction patterns, and it will suggest what kind of companies that shall put in a specific role of entities and it will give the detail information of the companies. Another function is if the sample SME users have go through the entire projects process, the details will also be presented to the current SME users as another business case. The last function is the data collection work, it will access to other systems that are within this project’s database. Through these functions, the SME users will be guided and supported throughout all the process within this information, which will leads to a better using performance of this information system.
‧
國立 政 治 大 學
‧
N a tio na
l C h engchi U ni ve rs it y
75
Concluding, this chapter corresponds to the Build/Develop part of the IS research framework, and expatiated how we intend to solve the business needs we observed in current SMEs service innovation problems by combing different theories and information technologies. In this chapter, we had illustrated the concept model of this research, and the system architecture which contains five modules for providing service innovation based on interaction pattern, and the implementation detail of the information system in this chapter. In next chapter, we will demonstrate the details of our evaluation of our theory.
Figure 4.15 Example of annotation module support during data input process (Annotation module gets information from another user’s input
to support User 1 during the it’s data input process)
‧
國立 政 治 大 學
‧
N a tio na
l C h engchi U ni ve rs it y
76