You are tasked with extracting a business case from the provided document.
- Carefully read the provided document to identify and extract the key components of the business case.
- Identify the core WHY (business purpose or impact), HOW (process or approach), and WHAT (technical product or service) elements.
- Focus on capturing the following elements where available:
- Problem Statement: The issue or opportunity the business case addresses. Begin with an infinitive verb to Clearly convey the business's fundamental reason for existence (the WHY), then integrate HOW and WHAT naturally within the sentence in that order.
- Objectives: Goals the business case aims to achieve.
- Proposed Solution: Description of the recommended approach or project.
- Benefits: Quantified expected advantages or value from the solution, Quantified expected impact of NOT implementing the solution. Mention relevant KPIs.
- Costs and Resources: Estimated expenses and resources required.
- Risks and Mitigations: Potential challenges and how they will be managed. List all identified risks using a factual, bullet-point format, quantifying likelihood and impact where possible. You will sort them under quality, costs and schedule, then highest likelihood x Impact.For any risks where information is missing or ambiguous, clearly highlight these as “unclear topics” that require further definition.
- Timeline: Key milestones and mitigation gates associated with identified risks. suggest relevant implementation steps from design to operation handover.
- If proposed solution is scalable at group level, highlight it as a benefit, but if proposed solution is specific to current situation or does not rely on best practices and reference architecture, highlight it as a risk and suggest a scalable solution as a mitigation
- Summarize these components clearly and concisely, ensuring the extracted business case is coherent and comprehensive.
The issue or opportunity the business case addresses:
- WHY: business purpose, fundamental reason for existence or impact ( infinive ...)
- HOW: process or approach (by + continuous tense ...)
- WHAT: technical product or service to be delivered (with + nouns/details ...)
Formalise as a sentence beginning with the WHY, then integrating HOW and WHAT naturally in that order.
- little or no evidence of occurence
- people will be surprised uppon occurence, they thought previous occurence were managed
- people will not be surprised uppon occurence,several occurences are known
- always happens
- No noticeable effect,operations undisturbed
- Localized,quickly fixable disruption
- Department-wide interruption; impacts timelines or budget
- Organization-wide breakdown; halts core activities or causes major losses
Provide the full business case in a structured basic html format with clearly labeled sections as follows:
Problem Statement:
[Extracted text]
Objectives:
[Extracted text]
Proposed Solution:
[Extracted text]
Benefits:
[Extracted text as bullet points with KPIs]
Costs and Resources:
[Extracted text as bullet points]
Risks and Mitigations:
[Extracted text as bullet points]
Timeline:
[Extracted timeline as table with Who What How When]
Clarification:
[Prioritized clarification questions with owner]
If any section is not present in the document, or If a number/KPI is missing or not clear, indicate it as "Not specified" and add a relevant clarification question assigned to relevant department. Infer original language. Make sure all extracted value are in the same language.
Output will be a json as follows: {"text_lang": "lang", "short_problem_statement": "...", "full_problem_statement": "...", "full_business_case": "..."}. If no business case found, output {}. All values will be in same language as input.
Provide the short_problem_statement as a single sentence that:
- must begin with an infinitive verb to clearly convey the WHY along with a relevant element of context (site name, location, system name)
- must mention neither HOW nor WHAT