Group items tagged

daviding says: I was sitting in a demonstration of IBM Rhapsody, where the simulation called out to some algorithms coded in Maxima.

OStatic: What products are your closest competitors? Viktor Toth: Maxima is in the same league as Mathematica or Maple. Perhaps a little less polished but in some ways, more powerful (I think for instance that the tensor algebra packages in Maxima can do things that cannot be done, at least not trivially, in other computer algebra systems.) Of course, it's also a LOT cheaper!

SERVICE SCIENCE: RESEARCH AND INNOVATIONS IN THE SERVICE ECONOMY 2011, DOI: 10.1007/978-1-4419-8270-4

Print ISBN: 9780470382417 Online ISBN: 9780470569627 DOI: 10.1002/9780470569627 Industrial Engineering What you need to know to engineer the global service economy. As customers and service providers create new value through globally interconnected service enterprises, service engineers are finding new opportunities to innovate, design, and manage the service operations and processes of the new service-based economy. Introduction to Service Engineering provides the tools and information a service engineer needs to fulfill this critical new role. The book introduces engineers as well as students to the fundamentals of the theory and practice of service engineering, covering the characteristics of service enterprises, service design and operations, customer service and service quality, web-based services, and innovations in service systems.

The basic idea: A method to select the appropriate management actions in a complex adaptive system based on the degree of certainty and level of agreement on the issue in question.

daviding says: I came to this 2001 page by Brenda Zimmerman, interpreting Ralph Stacey's work, via the presentation on the Constellation Model by Tonya Surman (at the Centre for Social Innovation, Toronto).

SERVICE SCIENCE: RESEARCH AND INNOVATIONS IN THE SERVICE ECONOMY 2011, DOI: 10.1007/978-1-4419-7904-9

At one time, the belief was that services-ranging from healthcare to retail, from banking to education-were the exclusive domain of local providers and were therefore impervious to foreign competition. Because they required direct interaction with customers, service providers needed to be located where their customers were (Bryson et al. 2004). This belief-along with many others associated with service activities requiring direct customer interactions-is no longer true because information technology has fundamentally changed the way many services are now designed and delivered (Karmarkar 2004). In this editorial, we introduce a framework for service managers that shows how advances in technology are continuing to change the way service providers and their customers interact; how both providers and customers access resources and unlock their capabilities in the co-creation of value. We also identify some major challenges confronting today's service managers who are competing in a rapidly changing global knowledge economy. Their success in addressing these challenges requires increasingly sophisticated management techniques that continue to focus on creating value for both direct and indirect customer-provider interactions.

11. How is ontology different from object-oriented modeling? An ontology is different from object-oriented modeling (represented in UML) in several ways. First, the most profound difference is that the ontology technology is theoretically found on logic. While ontology allows automated reasoning or infer ence, object-oriented modeling does not. Another difference is the treatment of properties; while the ontology technology treats properties as the first-class citizen, the object-oriented modeling does not. That is, while the ontology technology allows inheritance of properties, the object-oriented modeling does not. While the ontology technology allows arbitrary user-defined relationships among classes (a type property), the object-oriented modeling limits the relationship types to the subclass-superclass hierarchical relationship. While the ontology technology allows adding properties to relationships such as symmetry, transitivity, and inversion so that they are used in reasoning, the object-oriented modeling does not. While the ontology technology allows multiple inheritances among classes and also among properties, the object-oriented modeling allows only single inheritances. Despite theses differences, object-oriented modeling and UML are accepted as a practical ontology specification, mostly because of their wide-spread use in industry and the multitude of existing models in UML. There is an on-going effort to add logic capability to object-oriented modeling, represented by OCL (Object Constraint Language).

daviding says: To improve our understanding of the science of service systems, I think that we need to get to the level of ontology vocabulary ... and probably no higher. SysML has features that UML doesn't ... which doesn't mean good or bad, just different.

daviding says: I was thinking about (output) coproduction and (value) cocreation, and came across these proceedings, which includes a short article by Rafael Ramirez and Ulf Mannervick on "Designing value-creating systems".

Essay Archive Edited by Lucy Kimbell and Victor P. Seidel, collected in this innovative and highly illustrated volume are findings from the designing for services project. Particular focus is on the practices of an emerging discipline of service design grounded in the arts and humanities. Three case studies in which service design companies worked with science and technology-based enterprises are discussed, from a range of academic perspectives.