What has Kelly been up to lately?

Two people I respect a lot told me they were disappointed to see nothing from me blog-wise lately. Well, not as disappointed as I am in myself! So, here goes ...

I have been having a great term so far! I’m having fun in my class (Project Management). Hopefully the students are, too. I’m working on some papers (aka writing), taking the odd “how to” course at UofT, applying for things, submitting stuff, conducting research interviews, co-chairing workshops at CASCON, updating my webpage ... the usual professor stuff (I think). I need more students ... hint, hint.

One of my more exciting accomplishments of the term is coming up with a distinct statement about my research. Seems this should have been obvious to me but it wasn’t and it took some time for me to feel good about it. Here it is:

My current research interests include services science, social computing, data management, and business intelligence. In general, I am interested the application of technology in order to positively impact specific domains while taking into consideration the cultural and social implications of applying technology in those domains. Service science is an emerging discipline that looks broadly at the application of technology to positively impact services and the social and cultural impacts of doing so. Specifically, I am focusing on the technology and work practices that facilitate human-to-human exchanges and value creation in services which has led me to work in social computing technologies and virtual worlds.

More details are on my webpage in the “Research” section.

Something else exciting I accomplished since my last post was articulating my teaching philosophy.

To me, these are just a few of the wonderful aspects of being a professor (you can tell I'm still in the naive, honeymoon stage of this job)!

Proposed Service Science Research Landscape

Many individuals and groups are working to establish a research program and research projects in Service Science, Management, and Engineering or Service Science. These individuals and groups come from different research backgrounds and bring different perspectives and points of view to this emerging field.

The purpose of this blog post is to propose a research landscape which can help us situate service science research from across our varied disciplines. My hope is that, through this blog medium, we can collaborate to enhance and evolve the landscape so that it can serve several roles, including:

1. Help researchers understand how their research relates to existing service science research activities and that of specific researchers so that they may define effective collaborations;

2. Help researchers and project leaders determine which aspects of service science research are not addressed within a large research project or program; and

3. Help educators define service science curriculum and courses that cover specific aspects that are being addressed in service science research.

First I will provide some definitions, a practice which is extremely important when discussing topics that cross disciplines. For the context the proposed research landscape, “service” is defined independently of the notion of technology. In [1], a service is defined as “the application of competences for the benefit of another”. More broadly in [2], a service is defined as “the application of resources (including competences, skills and knowledge) to make changes that have value for another”.

A “service system” is defined as “a configuration of people, technologies, and other resources that interact with other service systems to create mutual value” [2].

By contrast, a “web service” is more narrowly defined as “a software system designed to support interoperable machine to machine interaction over a network” [3]. In the context of service oriented architectures (SOA), “services” are described as network-accessible software components that are aligned with business processes [4].

“Service Science” then is the study of the application of resources in one or more service systems to the benefit of another service system. Service Science is trying to develop a science of service systems and their interactions [2].

“Service Science, Management, and Engineering” (SSME) is sometimes used interchangeably with the term “service science” but it involves more than “service science” does. It includes applying management and engineering principles to services and has been defined as, “ the application of scientific, management, and engineering disciplines to tasks that one organization (service provider) beneficially performs for and with another (service client) [1].

Note that the definition of “services” has changed over time from meaning tasks that one performs for and with another in [1] to the application of resources for mutual benefit in [2]. This is evidence that the field is emerging and changing in such a way that it will benefit from having a landscape on which to ground various research activities.

The vision of service science remains boldly or ambitiously to be to create a coherent integrated body of knowledge to support ongoing innovation in service systems design, operation, and improvement [5]. A picture that has been used by IBM researchers to show the breadth of service science activities shows three layers:

The lowest level of this diagram represents the technical architecture, the middle layer defines work practices and on the top layer sits the services business. Research in service science or SSME spans these three different layers; thus, these three layers define one of the dimensions of the proposed landscape.

To articulate the other dimension of the proposed research landscape, we first look at the definition of a service system since research in service science requires researching service systems. A service system is defined as “a dynamic value co-creation configuration of resources, including people, organizations, shared information (language, laws, measures, methods), and technology, all connected internally and externally to other service systems by value propositions” [6].

Because organizations contain people and technology and information is shared through people and technology, the second dimension of the research landscape focuses on the people and technology resources in service systems.

Recall that a service is defined as the application of competence for the benefit of another entity. Services, therefore, involve at least two entities, one applying competence and another integrating the applied competences with other resources and determining benefit [6].

For benefit to be realized and competences to be applied, these two entities must interact in some way. The interaction could take place between two technological systems and be performed through web services. It could be that people in one entity are interacting with technology in another as in business to consumer e-commerce. Finally, it could be that technology is mediating people to people interactions such as when a researcher interacts through chat or email with a reference librarian to find information.

The second dimension of the proposed landscape, therefore, differentiates research as to whether it studies connections and interactions between people, between people and technology, or between technology and technology.

There are a couple of points to note about research that is situated within this landscape. First, the research may study interactions and sharing between two entities that are within the same organization or in different organizations. That aspect of the research is not differentiated on the landscape.

Second, the underlying goal of research that gets situated within this landscape has to explicitly address services as defined in [1] or [2]. In this way, we would not include research on the bottom level of this landscape picture that advances technology in a way that could simply be applied to service paradigms as well as being applied to several other paradigms. Rather, the research we situate on this landscape must study an effective and novel application of technology in new ways to enhance services or advances in technology that are motivated by specific kinds of services.

So for some examples of where research would fit within this proposed landscape, consider SOA and Web Services research which fits in the bottom to middle left side of the landscape. Two pieces of work I’ve collaborated on in virtual worlds fits in the upper right. And work I’ve collaborated on in understanding the structure of the social network in corporate blogs (technology mediated person to person interaction and sharing) fits in the middle right side of the landscape.

I think it’s important to realize that different kinds of business services may drive the research differently so I explicitly list 4 kinds on the landscape (large enterprise, small enterprise – although I’m not 100% sure there is a difference between them for the purposes of services research – government services, and non-profit services). Most of the work on theories of service science assume for-profit services and, while I haven’t looked at it very closely yet, I think it’s worthwhile to consider that some of the theories and definitions may not apply as well in non-profit services.

In a future blog post, I will describe how my current research activities fit within this landscape.

References:

[1] J. Spohrer, P. P. Maglio, J. Bailey, D. Gruhl, “Steps Toward a Science of Service Systems,” IEEE Computer, Jan. 2007

[2] J. Spohrer, S. L. Vargo, N. Caswell, and P. P. Maglio, “The Service System is the Basic Abstraction of Service Science”, Proceedings of the 41st HICSS, Jan. 2008

[3] W3C, http://www.w3.org/TR/ws-gloss/

[4] Wikipedia, SOAhttp://en.wikipedia.org/wiki/Service-oriented_architecture

[5] Kieliszewski, C., From a presentation at a meeting of the Alberta CAS (Center for Advanced Studies) Research Board Meeting, December 2007.

[6] Maglio, P., From a presentation at a CAS Alberta Workshop on Service Science, Management, and Engineering, March 2008.

ACM, ACM-W, and Great Advice

I was recently elected to the Council of the ACM for a 4 year term as one of 5 members-at-large. My initial decision to run is thanks to much encouragement from my colleague and mentor, Gabby Silberman. I’m extremely honoured to be serving with the tremendous talented people who were also elected and to be counted among those who have served on ACM Council in the past.

Some time ago, I joined the listserv for ACM-W (the ACM committee on Women in Computing). From the website, ACM-W “celebrates, informs and supports women in computing, and works with the ACM-W community of computer scientists, educators, employers and policy makers to improve working and learning environments for women”. I have benefited from being part of that community by reading with pleasure and pride the posts which share information, encouragement, and suggestions.

The first ACM-W newsletter was recently published and it is full of interesting profiles and articles. There is an interview with Fran Allen (first woman to win the ACM Turing Award) that I thought was terrific. I knew Fran when I was at IBM and have been a long time admirer of hers. She is an amazing mentor to so many people. I really like the advice Fran gives in her interview so wanted to point to it here: "Focus on your work, not your career – that will happen later; build professional networks; get multiple mentors and be a mentor; nearly all projects involve teams and there is evidence that diverse teams produce the best results, also they are the most interesting; have fun."

I think it’s great advice whether you are working in industry or in academia or going to school.

My Decision to Leave IBM

I was at IBM for 22 years ... I started on June 10, 1985 and my last day was November 30, 2007. I joined the University of Toronto Faculty of Information Studies in January 2008. I took Dec. "off" to regroup and get prepared emotionally.

I must say it was a big decision ... something I tried not to think too much about but instead went with my gut. I don't have tenure and came in at the Associate level so only have 3 years to get tenure. I try not to worry about this too much but it lurks in the back of my mind!

I joined IBM right after my undergrad but I knew I wanted to be an academic. I had also applied for scholarships and grad school. I received a Canadian gov't scholarship (NSERC Postgraduate Scholarship) that was deferrable for 2 years to go into industry so I took the job at IBM to get some experience (it was in the area of compiler development). I left after 2 years to pursue grad studies (my masters) and my (wise) manager at the time convinced me to take an educational leave of absence. I remember his reaction, “Never say never, Kelly. Things change. You’ll change,” when I told him I was never coming back. When I finished my masters and started my PhD, I went into IBM to resign but they extended my leave (that was almost 20 years ago -- I don't think it would be possible today). After my PhD, I wanted to have children and at the time looking for a faculty job seemed like a stressful process. I was offered and accepted a great job at IBM, had 2 wonderful children, and worked for 13 more years taking advantage of excellent opportunities and jobs I was given at IBM. Then (all of a sudden), I realized I had spent half my life with IBM (!) and I decided academia was now or never so I applied for academic jobs (I had built a lot of contacts in academia in Canada through my work at IBM so that helped).

And, here I am! It's pretty exciting and scarey all at once! People ask me what I miss the most about IBM and the answer is always, "the people" but fortunately, as an IBM CAS Faculty Fellow, I have the opportunity to stay in touch with and continue to interact with many of those tremendous people.

CASCON 2008 -- A Great Opportunity

Each year, IBM Toronto Centre for Advanced Studies and National Research Council Canada host a conference (CASCON) in Markham, Ontario. The conference is in the broad area of computer science and is considered to be the premier general international computer science conference held in Canada. It attracts international participation and over 1500 people usually attend over the course of 4 days. The first was held in 1991 and I have attended every one since. I started attending when I was a PhD student and I used the opportunity to “demo” my PhD research. The feedback I received from attendees was invaluable in the shaping of my thesis and results. I have also organized workshops and been a member of the Program Committee in the past (I’m on the Program Committee this year). In the last few years I was General Co-Chair so I’ll admit I am quite biased! But it really is a great opportunity for people whose work fits into one of the broad theme areas. Plus, it is free to attend and the lunches are delicious!

There are three main parts of the program: Academic papers (reviewed and selected by an international program committee with ~25% acceptance rate – papers are published in the ACM Digital Library); workshops and tutorials (my personal favourite part of the conference); and demos (another highlight). There are also very interesting and thought-provoking keynote speakers.

CASCON is called a “Meeting of Minds” because it aims to bring together academic researchers with practitioners and government researchers to meet and build collaborations. I highly encourage people (especially students) to take advantage of this local, free conference to showcase your work, engage in discussions, and meet new people.

You can participate as a contributor to CASCON by submitting a paper, organizing a workshop, or submitting a demo or poster. Or, you can participate as an attendee and attend any the workshops, demos, and paper presentations you wish. However, I highly recommend taking the opportunity to participate as a contributor – at least to put a poster or demo on display.

See the CASCON 2008 website for important dates, actual location, link to the call for papers, and description of topics of interest.

Great Pre-tenure Advice

I missed March!! I didn’t post anything to my blog in March. Well, technically, I did create a blog post because I set up a blog for my Service Science class where students could blog about an interesting service innovation that uses social computing technology. It was a huge success, each student blogging on something completely different. We all learned something new. So, I didn’t blog here but I blogged elsewhere.

I also missed posting something I really wanted to post about in February. On February 12, I attended an informal presentation by Professor and Vice Provost, Academic, Edith Hillan for women faculty who are pre-tenure which was hosted by her office and the Status of Women Office. It was a wicked cold day and there were fewer people there than expected but Professor Hillan delivered a great presentation, providing key tips for women faculty who are pre-tenure. She gave advice and suggestions based on her own experience and on the fact that she reviews between 100 and 150 tenure files per year. Here is what I took away from this very informative and useful event (the numbering and text are my own based on the notes I took during Dr. Hillan’s presentation):

1. Time and Task Management: she asked us to think about what we are doing to save time and provided suggestions:

a. Arrange your teaching so all classes meet on the same 2-3 days per week. You are only required to teach in 2 academic terms per year so don’t volunteer to teach in your “off” time. Make it very clear to students in your class which times you are available and set clear expectations about when they can expect a response from you (eg, within 48 hours). Don’t put off doing things that look too overwhelming (eg, the exams or papers you have to mark) – get started and make progress.

b. Set limits on the amount of time you spend on each thing. Set boundaries, stick to them, and say, “NO!” if necessary. Closely organize your work week. Work in brief, regular sessions instead of binges.

c. Don’t go for perfection!! This is a tough one for me because I’ve been practising being a perfectionist for over 45 years now!

d. Don’t always answer the phone or emails – let them go to the next day, or set up specific regular time when you deal with email and at other times, don’t. I tried this when I was at IBM for a while and it really does work but it is extremely hard for me to be disciplined about this (I, by habit, check email every few minutes).

e. Do double duty (also known as “leverage”). Find opportunities where your teaching links to research and where engagements with students (both undergrad and grad) link to your research. For example, co-author papers with students, and participate in service that gives you leverage somewhere else.

f. Take your holidays. This is an important one!

2. We talked about classes and teaching and she said that student responses to teaching are important so offered the following advice:

a. Make sure you are well prepared for classes. Provide good course outlines and bibliography. Present what will be covered at the start of the class.

b. Be very clear about what is expected from students (assignments, when they will be due, how they will be marked, how to contact you, etc.). She said the biggest complaint from students is that it wasn’t clear what was expected from them.

c. Leave time each lecture for student interaction and questions.

d. Take the pulse of student opinion mid-term and make adjustments. Show the students are you are interested in what they have to say. Clearly explain to students why they are completing final course evaluations and how it will affect your future.

e. Be open about your course being a “course in development” if it is one. But make sure you are able to teach courses again in the future (prepare once, reuse). Beg for and borrow course syllabi, exams, etc. from those who have taught the courses before.

3. We talked about service to the department through committees:

a. Try not to do too much committee work but you have to balance being a collaborative colleague with being a productive scholar and an effective teacher. Be a good department citizen.

b. Volunteer for the things you want to do then say “No!” to the others. Don’t wait to be invited if there is a committee you want to be on – ask for it.

c. Don’t try to “run the department” until after you have tenure! Similarly, don’t get involved in outside consulting until after tenure

d. She said a good committee to be on is the “PTR” committee (Thanks to Steve, I now know that stands for "Progress Through the Ranks"). The reason this committee was considered a good one was the fact that serving on it would help you understand what is needed to progress.

4. Research:

a. Make statements now to put in your dossier – your “story” – where you came from, where you are now, where you are going to go, research-wise. In your research statements, explain how you are building your program and where you are going next.

b. Publish, publish, publish (I think we all knew that one!)

c. Present at department seminars and organize seminars for your department, bringing in well-known researchers.

d. Manage your professional image. Develop a “marketable” record. View tenure as a political process: meet the candidates, the voters, ensure they know and understand your message.

e. Have regular conversations with your department chair or dean. Set objectives for the year and use these discussions to get feedback on those objectives.

f. Add something to your resume / CV every month (I love this one –it’s great advice).

5. Be assertive. This is an important piece of advice for many women I know. It applies in several of the points above with respect to committees, teaching, etc. In general, ask for things – don’t wait for things to be offered to you.

Multi-tasking and Context-Switching

Just a quick post as I haven't posted in a while and I have been thinking a lot about a lot of things but haven't had time to write anything down.

I have so many colleagues, friends, and mentors who have been in academia for years and years. They provide me with a lot of advice (almost all of it welcome) and suggestions. Just before I left IBM, one of my university colleagues told me that in academia I would find I was switching a lot between several different things -- more so than I did in industry. I remember thinking that could not be possible! At IBM, I switched between issues and topics every 30 minutes or so (back to back 30-60 min. meetings for 8 hours straight) with "sametime" (instant messages) and emails interrupting those 30-60 min. sessions for additional completely unrelated questions.

It's true that I switched more in IBM but it's also true that most of those switches were externally triggered (go to the next meeting now, respond to the urgent email request now, etc.). They were also easy to check of a list: that's done; that's done; next?

Now, I am switching between many different topics and activities (more so than I thought I would). In most cases, I have to schedule and initiate those switches. And because everything is so new, it takes me much longer to do some things than it should (or I tend to spend way too much time on some things than I should). And many of these activities are longer in duration and harder to declare as "done". Recently, in a faculty meeting, it was declared that we would meet weekly on the specific topic until we were done. A colleague remarked, "I just wish I knew what 'done' looked like!"

I actually enjoy switching between things. I have to get better at figuring out when to switch and when to keep going and, of course, when I'm "done" with something.

What is Service Science?

So, I’ve arrived here (at the University of Toronto) to embark on my scholarly and academic career. “So, what area are you in?” I’m asked. My first thought is, “I’m a computer scientist. I came from IBM. I’m interested in Service Science.” So, the next question is, “What’s Service Science?” Below I summarize what I think it is, why I’m interested, and briefly what (I think) I’m going to do next.

Service science (I am using this term – others may say “service science, management and engineering (SSME)” or simply “services”) is being called an emerging discipline. There is a big push in IBM and other companies to address this area and engage with academia to do so because the services sector (vs. manufacturing and agriculture) is the fastest growing segment of the economy in most if not all nations. Because of this significant economic shift and human labour migration, there is a claim that there is a need for organizations to be more systematic about services and services delivery; therefore, there is a need for research and innovation in services and for service science research and teaching programs to emerge (See Communications of the ACM July 2006 and IBM Systems Journal January 2008.

Programs are emerging in business schools, computer science and engineering schools, and through new multidisciplinary institutions. There are a host of others.

Establishing a research and teaching program in service science requires a multidisciplinary approach. It must combine knowledge about computing and technology with the social and cultural implications of how technology will be used in a specific business or societal service domain (or service system). I’m a computer scientist at heart and a proud member of the computer science community. I am very interested in how research advances in computer science can be made in order to impact something of importance (perhaps even change the world). I am fascinated by how these advances require understanding of and participation by people and society. Therefore, service science (as I understand it) is a very exciting area for me.

Most research to date has focused on service science with an underlying assumption that the service system or service is a business / profit service. Very broadly, I’m interested in service science in which the “business” domains are not-for-profit or community organizations. Most literature today assumes the services business is a profit-making entity. I will focus on the not-for-profit and community services organizations such as libraries, museums, healthcare facilities, etc. My initial investigations show that there are many interesting problems that come up in these contexts that are not prevalent in business environments.

So, that’s a start … within this framework, I’ve identified several interesting problems that I will blog about in future posts.

Why Blog?

When I started this new career, I decided I was going to blog ... about the transition, about my work, about my experiences. I wasn't sure why I was blogging. I just knew I was going to do it.

My first post was easy. I wanted students to know about the course I was teaching on "service science". I had already prepared a document to help me organize what I was going to say at a meeting organized by Eric Yu for FIS students to learn about Winter 08 elective courses. The document I prepared had a bit about my background, service science, and the course. When only a few students attended the session, I decided to post the course information from that document on a blog so I could point students to the post if they wanted more information.

Since then, I've had a few ideas about what I might blog about but I've hesitated. I was still not sure why I was blogging.

My second post was about the blogging seminar I attended at the FIS Inforum (the Inforum a tremendous jewel of a resource in FIS). In that blog post, I linked to the author of a book that related to a Book Chapter I'm contributing to with colleagues at the University of Alberta. In a phone conference with them, I mentioned the book and they asked me to send the link. Instead, I sent the link to my blog post! In return, I received a thoughtful comment from my colleague and one of my academic mentors, Eleni Stroulia, to my third post in which I attempted to compare my IBM (industry) career with my (new) academic one.

Today, I had a stimulating (but too short) conversation with FIS PhD Candidate, Rhonda McEwen, about Service Science. I shared with her some of my thoughts and ideas and told her about some papers she might be interested in reading. I said I'd send the links. Then I thought, if I had just blogged about my thoughts and included the links there, I could just point her to my blog. It dawned on me that having a public repository I can point people to will help save email generation but also will make sure I don't forget to send something in the list.

Also, as I talked with Rhonda, I remembered how helpful it is (for me) to articulate my thoughts and ideas out loud. Talking out loud is a necessary step for me to know what I think (someone once told me that extroverts don't know what they think until they've said it out loud). Well, blogging is like "saying it out loud". I have just realized (although it seems so obvious) that blogging will help me know what I think.

So, two reasons to blog. Now I know "why". So, I'll start working on "how". Until next time ...

Comparing my Industry Job to my Academic Job

In this blog post, I attempt to compare my old industry job with my new academic job. It's a bit early to do this (less than one month into it) and it seems that all things are on a spectrum, nothing being black and white, but I'm going to give it a try anyway. Since I'm just starting a new job, there is a lot of "start-up" activities that I need to do that have nothing to do with academia vs. industry (get health benefits, unpack my office, figure out how to print and photocopy for free, figure out the email system, determine the fastest commute route from A to B, meet new people, determine who does what, etc.) I won't add those to the comparison.

My first attempt at a comparison:

In my industry job, I was accountable to a large number of people and groups. I had to ensure that I was doing the things they needed: my employees, my bosses, collaborating university students, collaborating university professors, others in IBM and external to IBM, etc. A great deal of my time was spent responding to their needs or pro-actively setting up processes or systems to enable me and the rest of the organization to respond to others' needs.

In my academic job, I am accountable to less people and groups. I expect this to change as I become more active on committees, with students, collaborative research, and teach more courses but I think it will still be less than in my old job. Now, a great deal of my time is spent deciding where I should focus my effort and responding to my needs. Of course, I have high standards and needs so I push myself hard but this is definitely one difference I've noticed so far ... one that I like!

Getting into Blogging

Thanks to my blogger-mentors for encouraging me to keep blogging (you know who you are). And thanks to the instructor of my blogging and rss feed workshop for giving me even more reasons and suggestions for my blog (you know who you are!). I'm sitting in your class right now! In this class I also learned about a book (from an example blog of the author (Meredith Farkas) called, "Social Software in Libraries" which interests me and will help me contribute to a book chapter I'm currently working on with some colleagues.

Introduction to Service Science: Winter Course

As I embark on my new career in academia, I have decided it is time to make use of the technologies I became familiar with in my old job (in the IBM Toronto Centre for Advanced Studies) to enhance my new job (in the University of Toronto Faculty of Information Studies -- FIS). Hence, this blog.

This first blog gives some details about the Information Systems Elective course I'm teaching this term. I hope a lot of students from different backgrounds sign up. Hopefully, this post will help excite them about what we'll be learning.

First some background about me: My name is Kelly Lyons; I am joining FIS as a new faculty member in January 2008. Until recently, I was the Program Director of the Centre for Advanced Studies (CAS) at the IBM Toronto Lab. CAS works with university researchers on collaborative research project with IBM. So, I am coming from an industry background but with experience working with graduate students and faculty members on research projects.

Services Science: The last few years in CAS, I’ve been involved in some research in services science (which I’ll attempt to define in a bit). I also taught a grad course at York University Computer Science in this area (I’m an adjunct professor there) with my IBM colleague and really smart guy, Ross McKegney. Here is a link to the wiki we used: http://cosc6002r.wikispaces.com/ There were mostly CS grad students in the class but one PhD student from the Schulich School of Business. The course I'm teaching at FIS is different but is based on that one.

Services Science is an area of increasing focus in academia from the perspective of both research and teaching. The main motivation for this increasing focus is the fact that services are a growing part of the world’s economies: not just in the for-profit arena but for government services, social services, etc. Access to information sources and on-line spaces have enabled the creation of new ways of providing services.

So, there is a strong desire among many academics to work in this new, emerging, barely-defined field of study, or actually a somewhat loosely coupled combination of fields of study.

One of the things that attracted me to Service Science is the fact that it brings different areas together: social and cultural issues, computer science / information technology, management, operations, and so on. There is a unique opportunity in FIS to make progress and contributions that will bring these together into a more multidisciplinary area of study. That’s one of the goals of the course and my research program.

So, what is service science: the application of scientific, management, and engineering principles to services. A “service” is something that an organization or individual beneficially performs for and with another. In fact, researchers can’t 100% agree on how to define services. One of the things we’ll do is apply different theories of services to various service activities students are involved in.

One thing that is common among definitions is that services depend critically on people, and co-creation of value … and in this course we will focus on those services that also depend on technology and information. In order to deliver services, people work together and with technology to provide value.

Another way to look at services is through service systems. Service systems involve the interaction of people, technology, information within and external to organizations. Building services systems requires being able to model the many interactions and relationships. The paper here by Jim Spohrer, Paul Maglio, John Bailey, and Daniel Gruhl titled "Steps Toward a Science of Service Systems" does a nice job of describing different kinds of service systems and their complexities.

The Course: There are many aspects of service science and it’s not yet clear if it will become a discipline in and of itself or if it will augment existing disciplines. In some universities, programs are based in the business school so have a management focus. In other cases, the programs are based in the computer science department so focus mostly on service oriented architectures and the IT component of service systems. In some cases, courses are taught in Information Schools.

In my opinion and that of many of my colleagues, it’s important to look at service science from different perspectives and to agree on a common “language” or frame of reference. For example, in a recent workshop I helped organize, we talked about possibly having researchers from different backgrounds read the same papers in the area and annotate them from their perspective and use the different annotations to help come up with a common frame of reference. This is one of the things we will try to do in this course.

Since I come from a Computer Science background, I’ll present the course from that perspective but I’m very excited to have other points of view and perspectives from individuals participating in the course. I’m especially interested in understanding how to exploit social computing technologies and tools to better provide communication, collaboration, and innovation (unique, new ways of doing things) in service systems.

So, the course is broken into 4 topic sections, each with readings and assignments, plus a final paper and presentation:

1. Introduction to Service Science: Defining services, service systems, applying theories of services to student-selected service activities.
   
2. Modeling, analyzing, and optimizing service systems (of students' choice – hopefully related to their specialty) using software modeling tools (specifically WebSphere Business Process Modeler)
3. Innovation in services: What new ways of doing things or new models could be used to enhance the chosen service system? We will look at some case studies as examples.
4. Service Oriented Architectures: How are SOA technologies and associated tools helping organizations modify the software that implements their service system
   

Because of the uniqueness of the topic, we need to look at innovative delivery methods for the material and ideas presented. Guest lecturers will provide practical perspectives that we can compare with and augment what’s being learned through review of academic papers. We will also explore different social computing environments for sharing knowledge, information, and expressing our ideas: wiki’s, blogs, and through virtual world avatars.

Ultimately, more understanding of services and better service innovations will mean people who are “adaptive innovators” in business and society.

I’ve been familiar with and involved in research in services science with the goal of making companies (like IBM where I come from) more profitable in their services business (or for IBM to help make their customers more profitable), BUT it is clear to me that service science research can benefit social services and non-profit entities as well … and we have a real opportunity through this course and within FIS to be quite unique in our approach to studying service systems such as libraries, public institutions, social services, hospitals, high schools, universities, etc. That is one thing I hope we can bring to this topic and through each of the different perspectives in FIS and some of the other topics each of you are studying.