bu1 ad email config
This commit is contained in:
phaichayon
617
plans/task-bu-r.1.md
Normal file
617
plans/task-bu-r.1.md
Normal file
@@ -0,0 +1,617 @@
|
||||
# Task BU-R.1 – Business Capability Audit
|
||||
|
||||
Status: Planning
|
||||
|
||||
Priority: Critical
|
||||
|
||||
Type: Business Discovery / Capability Audit
|
||||
|
||||
Depends On
|
||||
|
||||
- BU-R.0 Business Blueprint Freeze
|
||||
- BU-R.0.1 Workspace & Activity Business Blueprint Completion
|
||||
|
||||
---
|
||||
|
||||
# Objective
|
||||
|
||||
Audit the current ALLA OS implementation against the frozen Business Blueprint.
|
||||
|
||||
This phase must identify which business capabilities already exist, which are partially implemented, which require enhancement, and which should be introduced as new capabilities.
|
||||
|
||||
The purpose is to minimize disruption to the existing architecture while ensuring future implementation aligns with the approved business blueprint.
|
||||
|
||||
This is a documentation and analysis phase only.
|
||||
|
||||
No implementation work is allowed.
|
||||
|
||||
---
|
||||
|
||||
# Background
|
||||
|
||||
BU-R.0 and BU-R.0.1 established the official Business Constitution of ALLA OS.
|
||||
|
||||
The current repository already contains a mature CRM foundation including:
|
||||
|
||||
- Customer
|
||||
- Contact
|
||||
- Lead
|
||||
- Opportunity
|
||||
- Quotation
|
||||
- Approval
|
||||
- Document
|
||||
- Organization
|
||||
- RBAC
|
||||
- PDF
|
||||
- Dashboard
|
||||
|
||||
The next step is to determine how closely the current implementation aligns with the frozen business architecture.
|
||||
|
||||
---
|
||||
|
||||
# Review Required
|
||||
|
||||
Review all relevant documentation before auditing.
|
||||
|
||||
Minimum review
|
||||
|
||||
- AGENTS.md
|
||||
- Project Standards
|
||||
- Architecture Rules
|
||||
- UI/UX Rules
|
||||
- Task Catalog
|
||||
- CRM Terminology
|
||||
- Relationship & Sales Workspace Blueprint
|
||||
- Existing ADRs
|
||||
- Current Schema
|
||||
- Current CRM APIs
|
||||
- Existing Dashboard
|
||||
- Existing Customer Workspace
|
||||
- Existing Lead Workspace
|
||||
- Existing Opportunity Workspace
|
||||
- Existing Quotation Workspace
|
||||
- Existing Approval Module
|
||||
- Existing Notification Module
|
||||
|
||||
Review source code only for capability verification.
|
||||
|
||||
Do not redesign.
|
||||
|
||||
Do not implement.
|
||||
|
||||
---
|
||||
|
||||
# Audit Scope
|
||||
|
||||
---
|
||||
|
||||
## Part 1 — Relationship Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Customer
|
||||
|
||||
Contact
|
||||
|
||||
Customer Account Type
|
||||
|
||||
Customer Ownership
|
||||
|
||||
Contact Sharing
|
||||
|
||||
Relationship Health
|
||||
|
||||
Customer Timeline
|
||||
|
||||
Customer Workspace
|
||||
|
||||
Determine
|
||||
|
||||
Existing capability
|
||||
|
||||
Missing capability
|
||||
|
||||
Refactor candidates
|
||||
|
||||
Future enhancements
|
||||
|
||||
---
|
||||
|
||||
## Part 2 — Activity Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Follow-up
|
||||
|
||||
Meeting
|
||||
|
||||
Visit
|
||||
|
||||
Phone Call
|
||||
|
||||
Reminder
|
||||
|
||||
Task
|
||||
|
||||
Notification
|
||||
|
||||
Internal Task
|
||||
|
||||
Determine
|
||||
|
||||
Current activity implementation
|
||||
|
||||
Duplicate activity concepts
|
||||
|
||||
Reusable components
|
||||
|
||||
Potential shared Activity model
|
||||
|
||||
Activity ownership
|
||||
|
||||
Activity lifecycle support
|
||||
|
||||
Calendar readiness
|
||||
|
||||
Timeline readiness
|
||||
|
||||
---
|
||||
|
||||
## Part 3 — Lead Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Lead lifecycle
|
||||
|
||||
Lead ownership
|
||||
|
||||
Lead assignment
|
||||
|
||||
Lead qualification
|
||||
|
||||
Lead conversion
|
||||
|
||||
Lead follow-up
|
||||
|
||||
Lead dashboard
|
||||
|
||||
Determine
|
||||
|
||||
Blueprint compliance
|
||||
|
||||
Missing capabilities
|
||||
|
||||
Legacy behaviour
|
||||
|
||||
---
|
||||
|
||||
## Part 4 — Opportunity Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Opportunity ownership
|
||||
|
||||
Forecast
|
||||
|
||||
Expected Award Date
|
||||
|
||||
Expected Delivery Date
|
||||
|
||||
Probability
|
||||
|
||||
Hot Project
|
||||
|
||||
Pipeline
|
||||
|
||||
Outcome
|
||||
|
||||
Process Status
|
||||
|
||||
Status
|
||||
|
||||
Determine
|
||||
|
||||
Business alignment
|
||||
|
||||
Schema readiness
|
||||
|
||||
Service readiness
|
||||
|
||||
UI readiness
|
||||
|
||||
---
|
||||
|
||||
## Part 5 — Commercial Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Quotation
|
||||
|
||||
Revision
|
||||
|
||||
Approval
|
||||
|
||||
Pricing
|
||||
|
||||
PDF
|
||||
|
||||
Customer Package
|
||||
|
||||
PO integration
|
||||
|
||||
Determine
|
||||
|
||||
Blueprint compliance
|
||||
|
||||
Missing capabilities
|
||||
|
||||
---
|
||||
|
||||
## Part 6 — Workspace Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Customer Workspace
|
||||
|
||||
Sales Workspace
|
||||
|
||||
Manager Workspace
|
||||
|
||||
Executive Workspace
|
||||
|
||||
Calendar
|
||||
|
||||
Timeline
|
||||
|
||||
My Day
|
||||
|
||||
Notification
|
||||
|
||||
Dashboard
|
||||
|
||||
Determine
|
||||
|
||||
Existing workspaces
|
||||
|
||||
Navigation gaps
|
||||
|
||||
Role support
|
||||
|
||||
Operational readiness
|
||||
|
||||
---
|
||||
|
||||
## Part 7 — Dashboard Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Pipeline
|
||||
|
||||
Forecast
|
||||
|
||||
Hot Project
|
||||
|
||||
Follow-up
|
||||
|
||||
Overdue Work
|
||||
|
||||
Sales KPI
|
||||
|
||||
Manager KPI
|
||||
|
||||
Executive KPI
|
||||
|
||||
Determine
|
||||
|
||||
Current implementation
|
||||
|
||||
Metric ownership
|
||||
|
||||
Business alignment
|
||||
|
||||
---
|
||||
|
||||
## Part 8 — Notification Capability Audit
|
||||
|
||||
Review
|
||||
|
||||
Approval Notification
|
||||
|
||||
Reminder
|
||||
|
||||
Follow-up Notification
|
||||
|
||||
Manager Escalation
|
||||
|
||||
Assignment Notification
|
||||
|
||||
Determine
|
||||
|
||||
Current notification model
|
||||
|
||||
Missing business events
|
||||
|
||||
Automation opportunities
|
||||
|
||||
---
|
||||
|
||||
## Part 9 — Business Event Audit
|
||||
|
||||
Review
|
||||
|
||||
Lead Events
|
||||
|
||||
Opportunity Events
|
||||
|
||||
Quotation Events
|
||||
|
||||
Approval Events
|
||||
|
||||
Customer Events
|
||||
|
||||
Determine
|
||||
|
||||
Existing events
|
||||
|
||||
Missing events
|
||||
|
||||
Timeline support
|
||||
|
||||
Calendar support
|
||||
|
||||
Automation readiness
|
||||
|
||||
---
|
||||
|
||||
# Deliverables
|
||||
|
||||
Produce
|
||||
|
||||
## 1
|
||||
|
||||
Business Capability Matrix
|
||||
|
||||
For every capability identify
|
||||
|
||||
- Existing
|
||||
- Partial
|
||||
- Missing
|
||||
- Legacy
|
||||
- Refactor Candidate
|
||||
|
||||
---
|
||||
|
||||
## 2
|
||||
|
||||
Capability Coverage Report
|
||||
|
||||
Percentage coverage
|
||||
|
||||
Customer
|
||||
|
||||
Activity
|
||||
|
||||
Lead
|
||||
|
||||
Opportunity
|
||||
|
||||
Quotation
|
||||
|
||||
Approval
|
||||
|
||||
Dashboard
|
||||
|
||||
Calendar
|
||||
|
||||
Timeline
|
||||
|
||||
Notification
|
||||
|
||||
Workspace
|
||||
|
||||
---
|
||||
|
||||
## 3
|
||||
|
||||
Gap Analysis
|
||||
|
||||
Current System
|
||||
|
||||
vs
|
||||
|
||||
Business Blueprint
|
||||
|
||||
Categorize
|
||||
|
||||
No Change
|
||||
|
||||
Enhancement
|
||||
|
||||
Refactor
|
||||
|
||||
New Capability
|
||||
|
||||
---
|
||||
|
||||
## 4
|
||||
|
||||
Architecture Preservation Report
|
||||
|
||||
Identify
|
||||
|
||||
Core components that should remain unchanged
|
||||
|
||||
Core components requiring extension only
|
||||
|
||||
Components requiring controlled refactoring
|
||||
|
||||
Potential breaking changes
|
||||
|
||||
Backward compatibility concerns
|
||||
|
||||
---
|
||||
|
||||
## 5
|
||||
|
||||
Business Capability Dependency Map
|
||||
|
||||
Show dependency between
|
||||
|
||||
Customer
|
||||
|
||||
Activity
|
||||
|
||||
Lead
|
||||
|
||||
Opportunity
|
||||
|
||||
Quotation
|
||||
|
||||
Approval
|
||||
|
||||
Dashboard
|
||||
|
||||
Calendar
|
||||
|
||||
Timeline
|
||||
|
||||
Notification
|
||||
|
||||
---
|
||||
|
||||
## 6
|
||||
|
||||
Capability Priority Matrix
|
||||
|
||||
Prioritize
|
||||
|
||||
Critical
|
||||
|
||||
High
|
||||
|
||||
Medium
|
||||
|
||||
Low
|
||||
|
||||
based on business value and implementation impact.
|
||||
|
||||
---
|
||||
|
||||
## 7
|
||||
|
||||
Implementation Readiness Report
|
||||
|
||||
Identify
|
||||
|
||||
Ready immediately
|
||||
|
||||
Requires schema enhancement
|
||||
|
||||
Requires service enhancement
|
||||
|
||||
Requires UI enhancement
|
||||
|
||||
Requires future phase
|
||||
|
||||
---
|
||||
|
||||
## 8
|
||||
|
||||
Recommended Epic Breakdown
|
||||
|
||||
Group future implementation into epics.
|
||||
|
||||
Example
|
||||
|
||||
Epic
|
||||
|
||||
Customer Workspace
|
||||
|
||||
Epic
|
||||
|
||||
Activity Platform
|
||||
|
||||
Epic
|
||||
|
||||
Calendar Workspace
|
||||
|
||||
Epic
|
||||
|
||||
Timeline
|
||||
|
||||
Epic
|
||||
|
||||
Manager Workspace
|
||||
|
||||
Epic
|
||||
|
||||
My Day
|
||||
|
||||
Epic
|
||||
|
||||
Notification
|
||||
|
||||
Epic
|
||||
|
||||
Dashboard
|
||||
|
||||
---
|
||||
|
||||
# Constraints
|
||||
|
||||
This phase is documentation only.
|
||||
|
||||
DO NOT
|
||||
|
||||
- modify schema
|
||||
- modify database
|
||||
- modify migrations
|
||||
- modify APIs
|
||||
- modify services
|
||||
- modify UI
|
||||
- modify permissions
|
||||
- modify business logic
|
||||
|
||||
No code changes are permitted.
|
||||
|
||||
---
|
||||
|
||||
# Success Criteria
|
||||
|
||||
Every business capability has been audited.
|
||||
|
||||
Current implementation is mapped to the approved Business Blueprint.
|
||||
|
||||
No duplicate business capability remains unidentified.
|
||||
|
||||
The impact of every future feature is understood.
|
||||
|
||||
Core architecture preservation strategy is documented.
|
||||
|
||||
A prioritized implementation roadmap can be produced without re-discovering business requirements.
|
||||
|
||||
Ready for
|
||||
|
||||
BU-R.2 Domain & Schema Audit.
|
||||
# Implementation Result - 2026-07-07
|
||||
Status: Completed
|
||||
|
||||
Completed:
|
||||
- audited current customer, lead, opportunity, quotation, approval, dashboard, notification, workspace, and security capabilities against the frozen BU-R.0 and BU-R.0.1 blueprint
|
||||
- classified current implementation into `Existing`, `Partial`, `Missing`, `Legacy`, and `Refactor Candidate` capability states
|
||||
- documented preservation-safe direction for later phases without changing code or schema
|
||||
|
||||
Primary findings:
|
||||
- customer ownership, contact sharing, opportunity lifecycle, quotation lifecycle, approval runtime, PDF/document delivery, dashboard KPIs, and CRM security are already strong foundations and should be preserved
|
||||
- follow-up capability is real across lead, opportunity, quotation, and dashboard analytics, but a shared production Activity platform does not yet exist
|
||||
- customer detail is a strong partial Customer Workspace, but generated timeline, relationship health, and activity-centered workspace sections are still missing
|
||||
- calendar, My Day, manager workspace, executive workspace, and generated timeline remain mostly future capability rather than current implementation
|
||||
- notification foundation exists and is production-ready, but business-event coverage is still mostly approval-centric
|
||||
|
||||
Recorded outputs:
|
||||
- [task-bu-r.1-business-capability-audit-2026-07-07.md](/C:/Users/mtpphtaps/Documents/gitea/alla-allaos-fullstack/docs/implementation/task-bu-r.1-business-capability-audit-2026-07-07.md)
|
||||
|
||||
Verification:
|
||||
- documentation-only phase
|
||||
- no schema, API, service, UI, permission, or business-logic changes made
|
||||
- no build or test command required
|
||||
Reference in New Issue
Block a user