Scope of Service Systems Engineering

From SEBoK
Jump to: navigation, search

Service systems engineering (SSE) involves all aspects of the enterprise. This topic discusses different aspects of the scope of SSE, from organizational strategy, to interoperability, to the life cycle of services, and then to their design.

SSE and the Enterprise

Enterprises plan, develop, and manage the enhancements of their infrastructure, products, and services, including marketing strategies for product and service offerings. These plans propose new products or service offerings based on new, unexplored, or unforeseen customer needs with clearly differentiated value propositions. Service strategies are the internal business processes required to design, operate, and deliver services. The mission of service strategies is to develop the capacity to achieve and maintain a strategic advantage (OGC 2009).

Taking the systems engineering (SE) approach to service systems, or (SSE), is imperative for the service-oriented, customer-centric holistic view to select and combine service system entities. The SSE approach can then define and discover relationships among service system entities to plan, design, adapt, or self-adapt to co-create value. The SSE approach should identify linkages, relationships, constraints, challenges/problems, new technologies, interoperability standards, interface agreements, or process development requirements among service entities required for the planned service or for potential future services (Lefever 2005).

SSE mandates participation not only from engineering, business operations, and customers, but also from various different domains, such as management science, behavioral science, social science, systems science, network science, computer science, decision informatics, etc.

Hipel et al. (2007) have presented a table for service science in terms of the domains and methods, including not only service systems, but also infrastructure and transportation systems, environmental and energy systems, and defense and space systems. The collaboration domains in Figure 1 below are a first approximation to the collaboration required from different disciplines for the SSE paradigm.

Table 1. Service Systems Engineering Domain Collaboration. (Hipel et al. 2007) Reprinted with permission of © Copyright IEEE - All rights reserved.
SEE Collaboration Domains
SSE Management
  • Management Science
  • Business Process Management
  • Cognitive Science
  • Decision Science
Service Realization Process (SRP)
  • All engineering fields
  • Business Operations
  • Infrastructure Operations
  • Social Science
  • Computer Science
  • Management Science
  • Behavioral Science
  • Network Science
  • Computational Science
  • Systems Science
  • Decision Science
Methodologies, Processes, and Tools (MPT)
  • Natural Science
  • Business Science (BPMN)
  • Mathematical
  • All engineering fields

Major challenges faced by SSE include the dynamic nature of service systems evolving and adapting to constantly changing operations and/or business environments, and the need to overcome silos of knowledge. Interoperability of service system entities through interface agreements must be at the forefront of the SSE design process for the harmonization of operations, administration, maintenance, and provisioning procedures of the individual service system entities (Pineda 2010).

In addition, service systems require open collaboration among all stakeholders, but recent research on mental models of multidisciplinary teams shows integration and collaboration into cohesive teams has proven to be a major challenge (Carpenter et al. 2010) (See also Team Dynamics). Thus, the emphasis on multidisciplinary (e.g., scientific, engineering, management, and social) education and training programs required to foster systems thinking helps bridge the gaps created by these silos of knowledge.

In the SSE approach, the social, governance, business, service, operations, and management activities are linked together through the service life cycle; service systems are by themselves a type of system of systems (SoS) where traditional systems engineering (TSE) practices need to be extended to include service systems entities' relationships (e.g., interface agreements among people, organizations, processes, and technologies) through information flows, technical interoperability, governance, and access rights within a system of systems.

Interoperability of Services

Interoperability among the different service system entities becomes highly relevant in SSE since the constituent entities are designed according to stakeholder needs; the entity is usually managed and operated to satisfy its own objectives independently of other system entities. The objectives of individual service system entities may not necessarily converge with the overall objectives of the service system. Thus, the need to include the following in the definition of a service system: analysis and design of the service system, governance frameworks to align political objectives, service strategies, business objectives, information and communications technologies (ICT) objectives, technology objectives and end-to-end operations, administration and maintenance procedures, and allocation of these procedures to individual entities (Luzeaux and Ruault 2010).

The previous discussion relates to a new service system development. There may be instances where a service is planned for delivery in phases of deployment (transition/deployment phase), or as presented earlier, if there is already a service system defined and deployed, then it's possible that the new request is for a service based application (SBA), in which case, the process is more focused on the adaptations needed to deploy the new application. For SBA, instances of advances in computer engineering, computer science, and software development already permit the adaptation and creation of SBA in a run-time environment for the discovery, development, and publishing of applications (Maglio et al. 2010).

The service design process (SDP) for new services is triggered by the market concept of the intended service and considers the stakeholder(s), service value chain(s), target market(s), target customer(s), proposed SLA, demand forecast, pricing strategy, and customer access privileges, which together comprise the service strategy. The SDP process then adapts the TSE as a life cycle approach (concept/definition, design/development, deployment/transition, operations, life cycle management/utilization/CSI, and retirement) as discussed in Life Cycle Models. A more detailed list of the SSE process activities is described in Value of Service Systems Engineering and Service Systems Engineering Stages.

Service Lifecycle Stages

The SDP stages and notation are depicted in Table 2 below; due to the complexity of service systems (see also Complexity) the documents generated are becoming more model-based electronic documents than written binders depending on the methodologies and tools used.

Table 2. Service Realization Process: Life Cycle Stages. (SEBoK Original)

<html>

Life Cycle Changes Purpose Decision Gates
Service Strategy/Concept New Service identification Elicit enterprise needs
Explore service concepts
Identify service system entities
Propose viable HL black box solutions
Output: Service Description

Decision Options
- Go, No-GO
- Continue this stage
- Go to preceding stage
- Hold project activity
- Terminate project
- Test
- Deploy

Feasibility Phase
HL Analysis
Service Design/Development Service Requirement Analysis and Engineering Refine service system requirements
Output: Service Requirement Document
Create solution description
Identify Interfaces among entities
Output: Preliminary Design
Develop service system detailed architecture and specs
Output: Service Specification Document
Verify and Validate system requirements
Output: service JV & V Plans
</br>
Service Development
Service Integration, Verification, and Validation
Service Transition/Deployment Service Insertion Plans
Deploy service system
Manage deployment activities
Inspect and test (verify)
Output: Service Operation Plans, Operations Technical Plans, Operational Readiness Plans
Service Operations and / Continuous Service Improvement Operate a reliable service system to satisfy customer needs
Monitor, Measure, & Assess
Provide sustained system capability
Troubleshoot potential issues
Store, archive, or dispose of the service system

</html>

All the life cycle stages are included for completeness, but very often during the concept analysis phase it may be determined that not all of the stages are needed. In these cases, a recommendation should be made regarding which stages are specifically required for the realization of the service in question.

Service Design Management

Another important role of SSE is the management of the service design process. SSE utilizes TSE practices to manage the resource and asset allocation to perform the activities required to realize the service through the value chain for both the customer and the service provider. The main focus of the service design process management is to provide for the planning, organizational structure, collaboration environment, and program controls to ensure that stakeholder's needs are met from an end-to-end customer perspective.

The service design process management process aligns business objectives and business operational plans with end-to-end service objectives, including customer management plans, service management and operations plans, and operations technical plans. The main SSE management activities are

  • planning;
  • assessment and control;
  • decision management;
  • risk management;
  • configuration management; and
  • information management.

SSE plays a critical role in describing the needs of the intended service in terms of the service's day-to-day operations, including customer care center requirements, interface among service system entities, such as: manufacturing plant, smart grid, hospital, network infrastructure provider(s), content provider(s) and service provider(s), service based application provider(s), applications providers, and the customer management process for the service.

Current research in computer engineering and software systems engineering is looking at the development of run-time platforms to allow real time or near real time customer service discovery and publishing (Spark 2009). The service-centric systems engineering (SeCSE) consortium has a well-defined service design process that is being applied to SBA. In this approach, there are design time and run-time sub-processes for the composition, provisioning, orchestration, and testing for service publishing (Lefever 2005). There is particular interest from the research community to include human-computer interactions (HCI) and behavioral science to address current social networking services (Facebook, Twitter, Linkedin, Google+, etc.) used to share unverified information via audio, messaging, video, chats, etc.

This research is gaining relevance because of the thin line between the customer (consumer, enterprise) and content providers in regards to security, privacy, information authentication, and possible misuse of the user-generated content. Even as the research progresses, these networking services are examples of business models organizing communities of interest for innovation. Hsu says, “If we understand this networking, then we may be able to see through the business strategies and systems design laws that optimize connected value co-creation” (2009).

References

Works Cited

Carpenter, S., H. Delugach, L. Etzkorn, J. Fortune, D. Utley, and S. Virani. 2010. "The Effect of Shared Mental Models on Team Performance." Presented at Industrial Engineering Research Conference, Institute of Industrial Engineers, 2010, Cancun, Mexico.

Hipel, K.W., M.M. Jamshidi, J.M. Tien, and C.C. White. 2007. "The Future of Systems, Man, and Cybernetics: Application Domains and research Methods." IEEE Transactions on Systems, Man, and Cybernetics-Part C: Applications and Reviews. 37 (5): 726-743.

Hsu, C. 2009. "Service Science and Network Science." Service Science, 1 (2): i-ii.

Lefever, B. 2005. SeSCE Methodology. Rome, Italy: SeCSE Service Centric Systems Engineering. SeCSE511680. Available: http://www.secse-project.eu/wp-content/uploads/2007/08/a5_d4-secse-methodology-v1_3.pdf.

Luzeaux, D., and J.R. Ruault (eds.). 2010. Systems of Systems. New York, NY, USA: John Wiley & Sons.

Maglio, P., M. Weske, J. Yang, and M. Fantinato (eds.). 2010. Proceedings of the 8th International Conference on Service Oriented Computing: ICSOC 2010. Berlin & Heidelberg, Germany: Springer-Verlag.

OGC (Office of Government Commerce). 2009. ITIL Lifecycle Publication Suite Books. London, UK: The Stationery Office.

Pineda, R. 2010. "Understanding Complex Systems of Systems Engineering." Presented at Fourth General Assembly Cartagena Network of Engineering, 2010, Metz, France.

Spark, D. 2009. "Real-Time Search and Discovery of the Social Web." Spark Media Solutions Report. Accessed September 2, 2011. Available: http://www.sparkminute.com/2009/12/07/free-report-real-time-search-and-discovery-of-the-social-web/.

Primary References

Lefever, B. 2005. SeSCE Methodology. Rome, Italy: SeCSE Service Centric Systems Engineering. SeCSE511680. Available: http://www.secse-project.eu/wp-content/uploads/2007/08/a5_d4-secse-methodology-v1_3.pdf.

Luzeaux, D., and J.R. Ruault (eds.). 2010. Systems of Systems. New York, NY, USA: John Wiley & Sons.

Additional References

None.


< Previous Article | Parent Article | Next Article >
SEBoK v. 1.7 released 27 October 2016

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus