INFO6007 Chap.12 IT Service Management and ITIL 4 Foundations
IT Service Management and ITIL 4 Foundations
ITSM coordinates capabilities and practices to co-create value through services. ITIL 4 connects four dimensions, guiding principles, governance, the value chain and practices. This chapter develops ITSM purpose, Products and services, Service outcomes, Project vs service management, Service relationships, Four dimensions, Service Value System, Seven guiding principles, Automation and trends.
Each idea is framed as a management decision: what evidence is needed, who owns the decision, which baseline or service outcome changes, and how the result is communicated.
Begin with the user outcome and value relationship, then examine people, technology, suppliers and value streams together. The method is deliberately connective.
Scope choices affect dependencies and estimates; resource choices affect schedule and cost; governance choices affect escalation and benefit ownership; service choices affect operating value. A strong answer names those links rather than reproducing an isolated framework.
A tool is not automatically a service, one strong dimension cannot compensate for three weak ones, and guiding principles are not a mandatory sequence.
The chapter uses direction checks, boundary cases and original scenarios to make those errors visible. Where a supplied figure is reproduced third-party material, the guide rebuilds it on new dimensions.
Where an answer is independently computed from a published table, it is labelled AskSia-authored rather than attributed to the University.
For assessment, start with a one-sentence definition, apply it to the stated facts, explain the consequence for objectives or constraints, and finish with the controlled action. Quantitative work must show the formula, substituted values, result, direction and management meaning.
Qualitative work must identify the decision owner and the evidence that would change the recommendation.
Study this chapter through retrieval. Rebuild the central artefact from a blank page, test it against a changed assumption, then check it against one neighbouring plan or practice.
That routine prepares for explanations, comparisons, scenarios and calculations without inventing a past-paper format or per-question mark scheme.
What this chapter covers
- 01
ITSM purpose
- 02
Products and services
- 03
Service outcomes
- 04
Project vs service management
- 05
Service relationships
- 06
Four dimensions
- 07
Service Value System
- 08
Seven guiding principles
- 09
Automation and trends
Free worked application: IT Service Management and ITIL 4 Foundations
- FrameIdentify the objective, decision owner and evidence available at the decision point.
- MethodApply the chapter rule and keep assumptions, units and direction words explicit.
- IntegrateTrace effects into at least one connected plan, baseline, stakeholder or service outcome.
- ActState the recommendation and the change, control or communication action that follows.
- VerifyCheck the result against the chapter trap and explain why the conclusion is reproducible.
Key terms
- ITSM purpose
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Products and services
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Service outcomes
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Project vs service management
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Service relationships
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Four dimensions
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
IT Service Management and ITIL 4 Foundations FAQ
What are ITIL 4's four dimensions?
Organisations and people; information and technology; partners and suppliers; and value streams and processes. Consider them together when designing or improving a service.
What is the main decision rule for IT Service Management and ITIL 4 Foundations?
Begin with the user outcome and value relationship, then examine people, technology, suppliers and value streams together.
What is the most common trap in IT Service Management and ITIL 4 Foundations?
A tool is not automatically a service, one strong dimension cannot compensate for three weak ones, and guiding principles are not a mandatory sequence.
How should I structure a written answer on IT Service Management and ITIL 4 Foundations?
Define the concept, apply it to specific facts, explain the effect on an objective or constraint, identify the decision owner, and state the next controlled action.
Are the worked scenarios for IT Service Management and ITIL 4 Foundations official answers?
No. They are AskSia-authored learning examples derived independently from the concepts and stated inputs. They are not official questions, marking schemes or university solutions.
Exam move
Begin with the chapter map: ITSM purpose, Products and services, Service outcomes, Project vs service management, Service relationships, Four dimensions, Service Value System, Seven guiding principles, Automation and trends. Write the purpose of each item in your own words and connect it to a decision, an artefact and an owner. Then rebuild the worked application without looking at the answer.
Use this governing rule: Begin with the user outcome and value relationship, then examine people, technology, suppliers and value streams together. Create two variations by changing one assumption, dependency, rating, probability, duration or stakeholder priority. Explain what changes and what remains stable. Keep an error ledger headed direction, boundary, authority, precision and integration.
The chapter's highest-risk mistake is: A tool is not automatically a service, one strong dimension cannot compensate for three weak ones, and guiding principles are not a mandatory sequence. For quantitative work, write symbols and units before arithmetic, keep intermediate precision visible and translate the result into under/over, ahead/behind, faster/cheaper or selected/not selected as appropriate.
For qualitative work, write claim, scenario evidence, causal reasoning and controlled action. Finish by checking one neighbouring plan or practice. Review operational assessment details on Canvas; this learning chapter does not invent dates, a viva rubric, past-paper questions or a per-question university mark scheme.
Working through IT Service Management and ITIL 4 Foundations in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 IT Service Management and ITIL 4 Foundations question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
