1. CCT 355: E-Business Technologies Class 3: Core E-business Technologies

2. Administration Sign up for presentations – and not late ones! Time to discuss proposals today Reading for today discussed next week – and a new quick but very foundational reading as well http://sloanreview.mit.edu/the- magazine/articles/2006/spring/47306/enterpr ise-the-dawn-of-emergent-collaboration/

3. Types of Information Systems Transaction processing (TPS) Management and Decision Support (MIS/DSS) Enterprise Resource Planning (ERP) Customer Relationship Management (CRM) Knowledge Management (KM) Communication and social networking systems (Enterprise 2.0)

4. Transaction Processing Systems Facilitate processing of transfer of goods and services Non-internet – electronic data interchange (EDI) systems Internet – e-commerce sites Key concerns?

5. Management and Decision Support Culling and representing key data to support human decisions “expert” systems – e.g., diagnosis software in medicine, IT support “dashboards” – key information about a given information system presented for quick analysis Key concerns?

6. Enterprise Resource Planning Systems to manage key inputs and outputs of organization Can be human, physical or more abstract resources - HR systems to inventory control Key concerns?

7. Customer Relationship Management Representing key information of customer base and history of interaction Sales support systems Data mining for key customer habits Affiliate and loyalty systems Key concerns?

8. Knowledge Management Representation and sharing of information within organization Supports knowledge building – but isn’t knowledge! Groupware systems Content Management Systems Key concerns?

9. Communication/Social Networking Enterprise 2.0 – integration of social media style communication Intranet setting – 37Signals (e.g., Basecamp), other tools (e.g., Socius, Yammer, Doodle) Internal IM – why? Use of 2.0 technologies for business outreach (e.g., Linkedin) Key concerns?

10. Systems Integration Integration of systems can be key points of success – or failure. Examples? Integrated suites as solution – but an expensive and constraining one Open APIs as an alternative – many Enterprise 2.0 solutions can be linked to each other relatively simply (the E in SLATES)

11. Tailoring Full scale systems engineering is complex and costly – e.g., INCOSE standard is thorough but massive and only applicable in full in massive projects Tailored solutions for more minor contexts – not perfect but effective for needs, and much more reasonable

15. Historical challenges at Cornell… Solid base of explicit information represented in reports – but significant tacit knowledge required to understand reports Not yet professional engineers – still learning Many learning styles among members – some are more comfortable with some mechanisms Learning ecology vs. knowledge management Continued research with U of T team

16. Use of information systems in Cornell/U of T Transaction processing? Decision support? Enterprise Resource Planning? Customer Relationship Management? Knowledge Management? Enterprise 2.0?

17. Next Week Look at three articles around challenges and promises of e-business technologies in social media world More presentations as we go along.