COMM391 Section 203 Phase 5

Get Started. It's Free
or sign up with your email address
COMM391 Section 203 Phase 5 by Mind Map: COMM391 Section 203 Phase 5

1. Security concerns over how functional our database are is another cause for concern.

1.1. New node

2. DataMed: Our company looks toward quick and efficient throughput, and knowledge management systems aid that because they are a document based technology that allows creation, management and sharing of documents.

2.1. Strengths

2.1.1. Increased Efficiency: KMS allows users to actively collect and distribute knowledge. This can help our doctors to apply live updates to patients’ files, and create an easier method of communication when a patient visits a second time. KMS provides a network of documents, so if a patient visits for a variety of reasons, we are able to use the system to match different reports.

2.1.2. Decreases costs: Provides a mapping network of the organization, increasing flow of communication, and allowing our professionals ease of access--> we will need fewer go-betweens

2.1.3. KMS can be used as an expertise locator, allowing easier location of details about a patient's history --> we can match specialists with a patient's core requirements

2.2. Weaknesses

3. ERP could be useful to DataMed since we are planning on taking personal information from our clients and integrate that information with their health data. By creating a single IT system, this will decrease redundancy as employees as well as clients do not have to enter in the same information each visit. Moreover, with all the information intertwined, our doctors can start to realize trends from the data and better help our clients overtime. Another way ERP is useful is that when it comes to our partnerships with other firms (nutritionists, physiotherapists, etc.) we can extract their data on the client and create a single system from there. It will be easier to discover solutions to potential health issues having extracted as much information as possible about our client. However, some limitations include if a client goes to another doctor and gains opposing information, then the data created by the ERP will not be accurate. Also, if the customer information changes slightly (weight, height, blood pressure, etc.) it can delay the process. To address these issues, we would allow the client to input some of their own information whenever it changes so the database could update more quickly. With the differing information of doctors, we would verify the correct information before inputting anything in the system.

3.1. One of the major problems or limitations of using ERP is the fact that we want the patient to have constant access to the information as well as us. The problem lies in that we wish to use a web-based interface that allows patients to constantly update their own information to give us a more holistic picture of their health, but how do we link a web-based system to our ERP? One way to to combat this problem is ensure the medical information on the web-based platform is exportable and can be recognized by an algorithm in our ERP, so that the information could be updated periodically by an automated process to save time and money. Obviously, this is a big task that we must research with great vigor understand it's implementation possibility.

4. Choose a technology, e.g. mobile computing. Highlight the strengths and limitations of the technology for your company. Identify some ways you can mitigate these limitations.

5. Group 314

5.1. Social Knowledge Management (KM)

5.1.1. We will use this technology with our Good Foods website which acts as a social networking community where individuals share knowledge, goals, and interests relating to health and organic foods

5.1.1.1. Strengths:

5.1.1.1.1. Users will communicate through message boards and blogs and we will be able to monitor their conversational trends to personalize our offers and develop CRM

5.1.1.1.2. Provides personalization to fulfill business model and provide competitive advantage

5.1.1.2. Limitations

5.1.1.2.1. A lot of information will be present

5.1.1.2.2. Mitigation

6. Group 311

6.1. Mobile Computing

6.1.1. Create a smartphone app. to schedule appointment by simply using the app. anytime from anywhere. For strength, it may attract more patients for the clinic since they can make quick convenient appointments. The limitations include: development costs, privacy issues, potentially small user base since we just have one clinic.

6.1.2. Mitigate the limitation: Hire a cheap third party ( small Computer science entity to help us develop the app. Mention the privacy issues before the registraition process. Encourage our patients to use this smartphone app to get quick response

7. Group 313

8. Group 312

8.1. Good Foods (312): Online Recommendation Agents

8.1.1. With the data we collect through our Customer Loyalty CRM system, we are able to determine the buying habits of different customers. When the customer logs into the online website with their loyalty card through our standard OR our mobile website, products/deals/coupons are automatically recommended for them based on their historical buying habits. Our in-store kiosks also have access to this customer database, so customers accessing their account through our in-store kiosks can view deals offered for them.

8.1.2. Strengths: Highly targeted marketing effort, relevance to consumer (which will ensure that they are interested), gives customer an incentive to return to our store; Weaknesses: Costly, not always correct or relevant, not all customer accounted for (those that are not part of our loyalty card)

8.1.2.1. Mitigation of weaknesses: When customers make online grocery lists, complements to items they've added to their list will be recommended. (For example: when a customer adds pasta to their list, we will also recommend pasta sauce). So even though some customers don't have a loyalty card, we can still upsell by using this method.

9. Group 319

9.1. MoveIt - Mobile Computing

9.1.1. Strengths

9.1.1.1. Allows people in the field to communicate with people in the office. The movers may need extra information during the move, and we can provide real time updates of information to our employees regarding the move. We imagine that phone calls are inefficient and that these instant notifications will make the moving process more fluid

9.1.1.2. Mobile computing is useful for our company because people are always on move. They are not stuck in the office where they can communicate with each other in person. With mobile computing, our employees will always be in contact with each other without being with close proximity of one another.

9.1.1.3. Reduces the likelihood of mistakes in managing, communicating, and entering, data. Less paperwork in the field, plus easier to organize and absorb needed information. Quality of data/information will be higher.

9.1.1.4. Should ultimately (after learning how to use it) lead to increased efficiency and productivity.

9.1.2. Weaknesses

9.1.2.1. For our company, we are dependent on the interactions with our customers in person. Mobile computing may allow us to get information with greater speed, but the quality of the move is not dependent on this technology

9.1.2.2. It does not add any visible value to the customers. Thus this would not be an advantage that we can advertise. Though, it will increase efficiency.

9.1.2.3. Since employees are busying communicating using mobile computing, the real interactions with customers may be reduced, which is not what we want since one of the company's strategy is to provide exceptional customer service

9.1.2.3.1. mitigation: explain the benefits to the customer of using mobile computing and gain their understanding of it. Provide good customer service as much as possible.

9.1.2.4. Carrying mobile devices around may be inconvenient (if it is a big one) and for the movers, guarding the device while moving might have a potential property security problem.

9.1.2.4.1. Incorporate the system in the work phone that the workers have. Or, simply keep an eye on the device while moving (since the movers must ensure property safety for the customers already).

9.1.2.5. Startup costs for implementing a strong (quality) mobile computing system will be high (relatively), but significant long term benefits.

10. Group 320

10.1. Van Realty - Recommendation Agents

10.1.1. Limitations

10.1.1.1. May not be ideal when it comes to personalizing a client's experience. Choices offered may be premature if based off of insufficient data.

10.1.1.2. Choices served may decrease client satisfaction.

10.1.1.2.1. MITIGATION: Live agents will be available to address customer concerns. Clients are not fully reliant on online recommendation agents as they are only used to form early decision sets.

10.1.2. Strengths

10.1.2.1. Takes out the complexity of choice when it comes to property purchases.

10.1.2.2. Quick/easy way for customers to form early decision sets.

10.1.2.3. The underlying data needed to create recommendations is not that extensive

10.1.2.3.1. Most recommendations will be based off property size, bedrooms, bathrooms, and neighbourhood preferences. Relatively few inputs compared to other recommendation services such as last.fm

11. Group 315

11.1. VanRealty - Cloud Computing

11.1.1. STRENGTHS

11.1.1.1. Convenience - Data warehouses can be easily accessed and input from anywhere as long as you have internet and the proper device (i.e. smartphones, tablets, etc.). A better system of organization is created and searching for data to use can be found quickly and when it is needed.

11.1.1.1.1. Useful for house showings when data on available listings, putting in data for offers, etc. may be needed on the spot)

11.1.1.2. Lower Costs - Less software updates needed, since any application that may be needed can be found online and run instantly from phone

11.1.1.2.1. By lowering costs there could be more money available to put towards marketing for the firm (creating ads/promotions that lhelps increase awareness of our firm with customers/potential clients), finding and hiring skilled real estate agents

11.1.2. LIMITATIONS

11.1.2.1. Possible security issues - Could be easily hacked , and then data could be accessed by anyone who shouldn't see it

11.1.2.1.1. Mitigation: By researching various cloud service providers credibility and their history with possible security issues and security measures, we may be able to reduce this risk.

11.1.2.2. Loss of control - A large portion of the control is put in the hands of the cloud service provider, so if anything goes wrong with the service/system it is hard to say who is responsible for it.

12. Group 318

12.1. Our choice of technology:

12.1.1. RFID: Using communication via radiowaves to exchange data between a reader (healthcare staff) and an electronic tag attached to the patient, for the purpose of identification and tracking. This will make it easier to keep track of patients. Tags will be read from several meters away and beyond the line of sight of the patient, will will enable an almost parallel reading of the

12.1.1.1. Weaknesses

12.1.1.1.1. Problems with data flooding as there might be too much information contained in our database system, especially since we are compiling comprehensive patient information.

12.1.1.1.2. There is a risk that patients might accuse our healthcare clinic of violating information privacy, by exploiting their personal healthcare data. To resolve this, contracts and regulations must be held and signed.

12.1.1.1.3. Security concerns about how secure our network is and whether there might be privacy issues is another cause for concern.

12.1.1.2. Strengths

12.1.1.2.1. It is extremely versatile in the sense that it can be used to track patients, which makes it easier for healthcare staff to track the movements of patients who might be more mobile even post-surgery.

13. Group 317

13.1. MoveIT - RFID tags

13.1.1. Strengths

13.1.1.1. can easily track location of each individual truck to guarantee on time scheduling, update available times faster

13.1.1.1.1. use to plan out best possible route in the future based on time of day. will be able to consider traffic conditions, obstacles on the road, etc based on observations made from previous routes taken

13.1.1.1.2. will help us collect future data: regional trends (where customers move to/from), how long it takes to get to certain areas

13.1.1.2. use to track important items of customers. for example, tags on special care items customers have specified. for example an expensive painting

13.1.1.2.1. helps increase customer satisfaction, maintaining loyal customers in the long run

13.1.2. Limitations

13.1.2.1. Can be hacked so that anyone can view where the truck/item is currently. Can midagate by having trackings which are not in words reabale by other parties but are encoded

13.1.2.2. Costly to first implement as we are a small company

13.1.2.2.1. Can be used for a very long time, increase profits by increasing efficiency in scheduling

13.1.2.3. tags can have errors/glitches. will think truck or item is somewhere it's actually not. or will lose track of truck/item if tag stops working, customers will expect to know where truck/item is but we wont be able to tell them. Can mitigate this by constantly inspecting and doing maintenance checks on all tags and tag system

14. Group 316

14.1. Moved here by TA

14.1.1. Intelligent Agents (Recommendation Agents) Strengths: Increases productivity because it provides fast matching recommendations without much labour input. Cheap – less human labour Provides matches that take into account a variety of factors Fast Limitations: More work has to be done on context related matching (AI not optimal) – Keywords matching is not perfect Security – glitches in the system can alter the data Mitigate Limitations: Refinements of input texts provided by job seekers and employers – standardised rewording so AI can evaluate the text better and match. Regular backups can help prevent Data Loss Operators always have to check recommendations provided by Agents before releasing it to the clients to make sure the recommendation is reasonable. This is OK though since there are not too many clients

15. New node

16. However, we also acknowledge some of the weaknesses to this solution. Such as the loss of control that the company has over its own information and data during the offload processing as well as possible ownership issues. Ownership issues can occur when it is unclear if the responsibility for the data should lie with the organization holding it or that created it.

17. More expensive than alternatives: the tags are easy to break which could easily happen during the process of moving

18. Group 301

18.1. City Workforce- Recommendation Agents

18.1.1. CityWorkforce would use recommendation agents to store preferences of clients and candidates to make future matching recommendations accordingly.Store reports on economic situation to consider the environment in the recommendations.

18.1.1.1. Strengths

18.1.1.1.1. Uses data mining so it's faster, more efficient to search for qualiied candidates. By reducing operating time and tasks it can reduce costs

18.1.1.1.2. It can be used to do the first steps in matching, creating a short list of recommendations, leading to less work load for each City Workforce agent

18.1.1.2. Limitation

18.1.1.2.1. -It doesn't consider intrinsic factors such as company culture and organizational value, which are crucial to the succees of the pairing.

18.1.1.2.2. They are not able to take into consideration aspects that clients and candidates value more than others.

18.1.1.2.3. -Misses the affective factor, some characteristics cannot be accurately described in key words.

18.1.1.2.4. -It can only use certain aspects or characteristics of each clients and candidates.

19. Group 302

19.1. VanRealty - Cloud computing

19.1.1. Benefits:

19.1.1.1. Sustainable for our small firm in terms of cost.

19.1.1.2. Our agents can get information that we need to provide clients very conviently as long as there is connection to an internet source which can be attained almost anywhere via wifi, 3g, and mobile data plans

19.1.1.2.1. useful for providing on demand information ie. pictures, state, condition and history of our listings to clients to enhance the buying aspect and reduction in lag times of data processing and attaining

19.1.1.3. Good complement to our OLAP system that were using to manage our CRM to provide quick decisions regarding consumer preferences and relations.

19.1.1.4. Can provide a central data source and key communication between firm and agents to sync new information in order to provide our clients the latest info and firm assessments

19.1.1.5. cheap to implement

19.1.2. Limitations

19.1.2.1. Lose control of who's adding or taking away information on the cloud server's. It becomes a security issue for privacy information if people can access this private information of our company and clients without our permission.

19.1.2.2. Overcoming Limitation: record a log of who is accessing the server. Dates, time, size of information, input/output, frequency, and location. Put security measures ie.coding, password check, AGENT ID check, and etc to improve security and identify users.

19.1.2.3. New node

20. Group 304

20.1. City Workforce

20.1.1. Enterprise Resource Planning (ERP)

20.1.1.1. Strengths

20.1.1.1.1. • An integrated and working system==> all departments and functions throughout City Workforce are integrated into a single IT system so that employees can make enterprise-wide decisions by viewing enterprise-wide information on all business operations ==>eg. data sharing between the Accounting, Marketing & Sales, and HR departments Once an employee signs (a contract) with City Workforce, their information (ie skills, attributes, experience level, etc.) is entered into our database system. With ERP, it allows for joint execution among the different systems/departments and by inputting data in one module, it triggers the execution of all related modules such as payroll, client match, fulfillment, etc.

20.1.1.1.2. • ERP system contains best practices in the business.

20.1.1.1.3. • Implementing it will force your organization to be more structured.

20.1.1.1.4. • Although implementation time is lengthy, it is still a lot faster and more efficient compared to doing everything from scratch.

20.1.1.2. Limitations

20.1.1.2.1. • Each time data re-entered, possibly with reformatting: ==>Reformat: e.g., date format (month/date/year, date/month/year, year/month/date)

20.1.1.2.2. • Small changes can delay the process: ==>What if the project or work term required by the client takes longer than expected to complete? Payroll person may need to go back to client for more information/revise work contract

20.1.1.2.3. • Systems and strategy clash ==>Only some degree of customization possible, but the complexity of the system makes major modifications impracticable ==>Prior to ERP, City Workforce would first decide how they wanted to do business and then choose a software package that would support their proprietary processes. They often rewrote large portions of software code to ensure a tight fit. With ERP, the business must be modified to fit the system.

20.1.1.2.4. • Resistance from employees

20.1.1.2.5. • High initial investment ==>$100M~200M for large companies is not uncommon; even small firms may need to spend more than $1 million. ==>Consulting (30%); HW/Infrastructure (25%); Implementation Team (15%); Training (15%); Software (15%)

20.1.1.3. Ways to mitigate these limitations

20.1.1.3.1. • Stress the enterprise, not the system ==>think of ERP as a business project rather than as a technology

20.1.1.3.2. • Bounded reengineering, not blank-sheet ==>Redefine/rework processes so that they can be aligned with the requirements built into an ERP system to be implemented

20.1.1.3.3. • Train the end users in the new business, not just the software

20.1.2. Other technologies we think are helpful:

20.1.3. Grid Computing

20.1.3.1. Strengths

20.1.3.1.1. → can be used to store our employee’s information and resume etc. all in one very accessible and organized database. When a potential customer needs employees we can just enter our database search for example “painter” and then send the employer all the employees resume’s that fit the right categories. These can be inputted in the Grid Computing program.

20.1.3.1.2. Grid Computing can take information from multiple computers and form a grid. So if our client decides to edit our employees profile (example: the feedback section, or ranking) all the computers will have this updated information.

20.1.3.2. Limitations

20.1.3.2.1. With many languages, there is a trade off between investment in software development and the number of platforms that can be supported (and thus the size of the resulting network) Therefore the size of our grid could be affected if we have the service in multiple languages (temporary workers).

20.1.3.2.2. Second limitation is cost. This software can be very expensive.

20.1.3.3. Ways to mitigate these limitations

20.1.3.3.1. We would have to only offer the service in one language to keep the number of problems and cost down.

20.1.4. Wireless Technologies (e.g., Blue Tooth, Wi-Bro Technology, WiMAX, 4G Wireless)

20.1.4.1. Strengths

20.1.4.1.1. → because we are a fast paced business we constantly need to know when there is a demand for employees and the supply that our business currently has available to fulfil that supply. Wireless Technologies can help us support this and make this more more efficient because employees and employers can contract us directly and more efficiently.

20.1.4.2. Limitations

20.1.4.2.1. Blackout locations. There are still some areas where you cannot receive service (3G or 4G). Also, if you are too far away from the wireless service you will not receive a signal.

20.1.4.3. Ways to mitigate these limitations

20.1.4.3.1. Create a digital map of where there blackout locations are. From there we can make sure that our employees can be contacted through different communication channels (example – landlines, Ethernet cables, internet)

21. Group 303

21.1. Mobile E-Commerce

21.1.1. Strengths

21.1.1.1. By using the mobile browsing system,customers are able to check whether or not an item that they want to purchase is in stock or not

21.1.1.2. By implementing a mobile payment system, customers could shop online or on mobile phones and pay on their phones. This way, they can just show the receipt on their phone to the cashier (cashier scans barcode/QR code or input receipt number on receipt . This will be convenient and time saving for those customers who don't want to wait in line

21.1.1.3. Allows us to increase personalization for customers. Because we know what they have purchased, we can provide updates or messages to their Good Foods App to provide information such as recipes that they could use with the food they purchased

21.1.1.3.1. Can also use prediction tools to suggest other products that the customer may enjoy or complement the foods they have purcashed

21.1.1.4. In store

21.1.1.4.1. Can provide a map or search bar in the mobile app so that customers are able to easily find items that they are looking for in the store

21.1.1.4.2. Customers can scan food items or price/food tags that show a QR code so that customers are able to find out nutritional information about the products

21.1.2. Limitations

21.1.2.1. Security: There may be hackers who threaten the security of the system causing interruptions in the business. This can cause a breach in security.

21.1.2.1.1. This can be fixed by having a better firewall and stronger security system.

21.1.2.2. In order to apply the mobile payment system to make it work for customers who have a different telecommunications network (Rogers, Bell, Telus etc.) It is necessary to cooperate with different telecommunications companies.This way, customers will be able to pay for items on their telephone bills. To cooperate with many companies, it may be costly and time consuming.

21.1.2.2.1. This limitation is related the the cost of implementation. In order to mitigate such we can use other methods of of payment. This includes credit card payment

21.1.2.3. People may not own a smart phone or are not tech saavy.

21.1.2.4. Having people sign up for the mobile app during the beginning may be difficult.

21.1.2.4.1. This can be mitigated by having promotions or incentives to increase the number of people signing up and downloading the app.

21.1.2.5. Trust: customers may not trust the online applications especially regarding online payments as they have security and privacy concerns.

21.1.2.5.1. This can be mitageted by educating consumers on online security to help build consumer confidence

22. Group 307

22.1. We are choosing Cloud Computing for VAnalyst - Some of the advantages would include a better utilization of company resources, as well as providing a more sustainable service by allowing offload processing and storage to remote computers.

22.1.1. To mitigate some of the weaknesses mentioned above there are some solutions we may consider. One of these solutions may include a historic log when when the data is accessed, developed, or used. Additionally simple security measures such as limiting access to certain level employees or password access.

23. Group 306

23.1. ERP

23.1.1. Strengths

23.1.1.1. Central system for all of our inventory and sales data that will streamline our value chain with our warehouse, suppliers and retail locations. Paired with RIFD technology for perishable goods we can use a ERP system to improve inventory management in all three of our locations, making our stores more cost efficient by reducing waste in perishable goods.

23.1.2. Weakness

23.1.2.1. : The ERP system will be very costly to implement and it can be copied by our competitors.

23.1.3. Mitigations

23.1.3.1. The ERP system is costly to implement, but offers significant gains in the long run. The ERP will make inventory management more efficient (by reducing the number of spoiled goods) which will create substantial savings for the company.

23.2. Because the moving industry is all about being coordinated and fast, an ERP system would potentially be very beneficial. Integrate departments: staffing, equipment/maintenance, jobs/scheduling, accounting. This way- when a customer contacts us and the scheduler can look directly at if a truck is available/maintenance and if staff are available. The individual in charge of truck maintenance can then make sure its ready in time for the booking and the staff can see the customer profile immediately to prepare to make it a tailored moving experience, accounting department and look themselves to see any bookings and their costs/revenues. Pros: because MoveIt has no current info system it will be an improvement, staff may resist less because they don’t have to move from one it system to another- just from paper to ERP. Cons: take a while to implement- must train.

24. Group 310

24.1. VAnalyst - Knowledge Management System:

24.1.1. Benefits

24.1.1.1. Knowledge information sytems can be used to identify which analysts know what, and this can be useful when assesing different stocks for potential clients. For example, some analysts may specialize in growth stocks, whilst other "value" investors may have more extensive knowledge on stocks which are undervalued by the market.

24.1.1.1.1. The knowledge information system could act as supplementary support to decision making rather than a database. For example:

24.1.1.2. This is strongly aligned with VAnalyst's desire to cater very closely to customers. By clearly understanding and being able to assess the different areas of strength of their analysts through an integrated system, VAnalyst would easily be able to assign the most suitable and experienced analysts in the clients' respective areas of interest.

24.1.1.2.1. For example, VAnalyst receives a client who is particularly interested in a very specific industry. Through a Knowledge Management System, the information regarding which analyst holds the most experience and has the best results in this industry would be easily accessible and available. This way, VAnalyst can provide the best possible service that is catered to the client's needs to the best of VAnalyst's ability.

24.1.2. Limitations

24.1.2.1. It may be quite difficult to identify who within the company knows what considering that most of the agents within the financial industry hold similar knowledge. Most of the agents are some what complimentary to each other within this industry.

24.1.2.1.1. Mitigate the limitation: Most investors tend to have a preference on what type of stocks they prefer, and prior to the information system, a survey can be conducted to identify each analyst/proffesionals "speciality".

24.1.2.2. Though there are strong benefits to implementing a Knowledge Information System, whether the benefits outweigh the costs depend on the size of the company, as well as its complexity. A large and complicated company would derive much more benefit from KMS implementation than a small, straightforward company.

24.1.2.2.1. In terms of VAnalyst, though the size of the company is not large, we feel that the complexity of the environment in which it operates would mean that it would still be able to benefit greatly from the implementation of this technology.

24.1.2.2.2. The dynamic nature of the stock market demands adaptability and an array of different skills, experience, and knowledge on the part of the analysts. By organizing this information through KMS, it becomes readily available and accessible, and increases the flexibility and effectiveness of the company.

25. Group 309

25.1. VanRealty

25.1.1. Personalization

25.1.1.1. The strengths with this technology is that we can observe what individuals are searching online and offer housing suggestions for them. This matching can factor in past house locations, house types, etc. The disadvantange

26. Group 308

27. Group 305

27.1. MoveIT

27.1.1. RFID Tags

27.1.1.1. Strengths:

27.1.1.1.1. Easy to organise packages, track their locations, identify packages

27.1.1.1.2. Potential to save time by allowing that data to be connected electronically between databases

27.1.1.1.3. RFID tags can track people, items, and equipment in realtime and away from the office / on the go.

27.1.1.2. Limitations

27.1.1.2.1. Dependence upon th esystem: what if the tags stop working?

27.1.1.2.2. Safety issues: Since RFID systems make use of the electromagnetic spectrum (like WiFi networks or cellphones), they are relatively easy to jam using energy at the right frequency.

27.1.1.2.3. RFID Tags are more expensive than other options (such as marking each box with a marker) and break more easily

28. New node

29. New node

30. New node

31. New node