LEARN. PRACTICE. GROW.Concept and mechanism
An SLA makes expectations discussable and observable when it defines the service, period, method, and measurement conditions. “99.9%” without these elements may mean different things to each participant. Connect indicators to intended use: a correct report after the deadline may not enable the necessary decision. Functionality and the conditions under which it is available should be evaluated together. Also define customer contributions. A delivered tool does not produce the outcome if necessary data or the people using it are unavailable. Useful agreements make these dependencies explicit and define their follow-up.
Guided application
In the 24/7 coverage case, completed functional tests do not create a night roster. Compare prepared coverage, limited initial scope, and a date change, identifying costs, risks, and owners. A daytime pilot may work if compatible with the objective and agreed by authorized people. Do not change the commitment only in an internal report. Negotiation seeks an option both sides can execute; it requires neither accepting every request nor rejecting every change. Confirm the decision, prepare resources, and check experience after service entry. Percentages used in examples are fictional and do not represent BNP Paribas contracts or policies.
A person spending 75% on L3 work cannot simultaneously be counted as full project capacity and informal night coverage.
Common pitfalls
Percentage without definition; tests as a roster; license delivery as benefit; unilateral changes to expectations.
Related topics: Onboarding, offboarding, and channels · Co-creation, support, and feedback
Promise conditions that are understood, agreed, and operationally prepared.
Reference: PeopleCert Service Level Management practice overview · ITIL 4 DSV; observed JA v1.0.1 (2025 copyright), current EN revision comparison pending