bu1 ad email config
This commit is contained in:
@@ -448,3 +448,572 @@ Phase R.1 may begin when:
|
||||
1. this blueprint is accepted as the business baseline
|
||||
2. terminology conflicts are treated as governance backlog instead of hidden assumptions
|
||||
3. capability audit work references this document explicitly
|
||||
## 20. Activity Blueprint Freeze
|
||||
|
||||
### Purpose
|
||||
Activity is the governed operational work record for business execution across marketing, sales, customer relationship work, quotation chasing, manager follow-through, and future service coordination.
|
||||
|
||||
Frozen rule:
|
||||
- `Activity` is the source-of-truth work record.
|
||||
- `Audit Log` is immutable system history.
|
||||
- `Notification`, `Reminder`, `Calendar`, and `Timeline` are projections from activity state and business events, not parallel activity records.
|
||||
|
||||
### Activity Definition
|
||||
An Activity represents one planned, in-progress, completed, rescheduled, or cancelled unit of work performed by or assigned to a user.
|
||||
|
||||
Examples:
|
||||
- follow-up call
|
||||
- customer meeting
|
||||
- site visit
|
||||
- site survey
|
||||
- presentation
|
||||
- internal task
|
||||
- document chase
|
||||
- reminder-backed action item
|
||||
|
||||
### Activity Ownership
|
||||
- One activity has one accountable owner.
|
||||
- One activity may also have one assignee when work is delegated.
|
||||
- Owner is responsible for ensuring the activity reaches a terminal outcome.
|
||||
- Assignee is responsible for execution when assigned.
|
||||
- Customer owner, lead owner, opportunity owner, quotation salesman, or manager may create activities, but activity ownership must still resolve to one user.
|
||||
|
||||
### Activity Entity Relationships
|
||||
Every activity must support:
|
||||
- one required primary reference
|
||||
- zero or more related references
|
||||
|
||||
Allowed primary reference targets:
|
||||
- Customer
|
||||
- Contact
|
||||
- Lead
|
||||
- Opportunity
|
||||
- Quotation
|
||||
- PO / Won Project
|
||||
- Internal Only
|
||||
|
||||
Allowed related references:
|
||||
- Customer + Contact
|
||||
- Customer + Opportunity
|
||||
- Opportunity + Quotation
|
||||
- Lead + Customer
|
||||
- Quotation + Opportunity + Customer
|
||||
|
||||
Frozen rule:
|
||||
- Activity may span business context, but only one primary reference governs default visibility, ownership inheritance, and calendar placement.
|
||||
|
||||
### Activity Families
|
||||
Shared activity families are:
|
||||
- Follow-up
|
||||
- Meeting
|
||||
- Visit
|
||||
- Phone Call
|
||||
- Email Follow-up
|
||||
- Site Survey
|
||||
- Presentation
|
||||
- Internal Task
|
||||
- Reminder-Driven Action
|
||||
- Other
|
||||
|
||||
### Activity Priority Freeze
|
||||
Priority levels are:
|
||||
- Critical
|
||||
- High
|
||||
- Normal
|
||||
- Low
|
||||
|
||||
Priority is determined from:
|
||||
- business deadline
|
||||
- customer commitment date
|
||||
- forecast sensitivity
|
||||
- approval dependency
|
||||
- manager escalation
|
||||
|
||||
Frozen rule:
|
||||
- `Hot Project` is not the same thing as `Critical Activity`.
|
||||
- Hot Project may increase suggested activity priority, but does not force it automatically.
|
||||
|
||||
### Activity Status Freeze
|
||||
Primary status set:
|
||||
- Planned
|
||||
- In Progress
|
||||
- Completed
|
||||
- Cancelled
|
||||
|
||||
Derived operational views:
|
||||
- Due Today
|
||||
- Upcoming
|
||||
- Overdue
|
||||
- Completed Today
|
||||
|
||||
Frozen rules:
|
||||
- `Overdue` is a derived operational condition, not a separate lifecycle state.
|
||||
- `Rescheduled` is an activity event and timeline event, not a standalone terminal status.
|
||||
|
||||
### Activity State Machine Freeze
|
||||
|
||||
```text
|
||||
Planned -> In Progress -> Completed
|
||||
Planned -> Cancelled
|
||||
Planned -> Overdue (derived view only, returns to Planned after reschedule)
|
||||
In Progress -> Completed
|
||||
In Progress -> Cancelled
|
||||
```
|
||||
|
||||
### Activity Completion Rules
|
||||
- Completion requires an outcome summary.
|
||||
- Completion may optionally create a next activity suggestion.
|
||||
- Follow-up completion should encourage explicit next action when the related lead, opportunity, or quotation remains open.
|
||||
- Cancelled activities must capture cancellation reason when the activity was already scheduled with customer-facing commitment.
|
||||
- Activities linked to lost or closed records may still be completed for documentation, but no new forward-driving activity should be auto-created from a terminal-lost record without user intent.
|
||||
|
||||
### Activity Visibility Freeze
|
||||
Activity visibility inherits from the primary related record plus assignment.
|
||||
|
||||
Rules:
|
||||
- Owner and assignee can always view the activity.
|
||||
- Users who can access the primary record may view the activity unless the activity is marked internal-only.
|
||||
- Internal-only activities are visible only to creator, owner, assignee, managers, and authorized admins.
|
||||
- Contact-level sensitivity follows parent customer/contact access rules.
|
||||
- Pricing-sensitive notes remain subject to quotation pricing visibility when activity content exposes commercial amounts.
|
||||
|
||||
### Activity Permission Freeze
|
||||
Minimum governed permissions:
|
||||
- Activity Read
|
||||
- Activity Create
|
||||
- Activity Update
|
||||
- Activity Complete
|
||||
- Activity Cancel
|
||||
- Activity Delete
|
||||
- Activity Reassign
|
||||
|
||||
Frozen rule:
|
||||
- Activity authorization must follow resolved CRM access patterns and never bypass record scope rules.
|
||||
|
||||
### Follow-up Strategy Freeze
|
||||
- Follow-up remains the first operational activity subtype.
|
||||
- Existing lead, opportunity, and quotation follow-up records are the current implementation seam.
|
||||
- Future unification should map those records into the shared activity model without changing business meaning.
|
||||
- A follow-up should always answer: what happened, what is next, and when the next touch should happen.
|
||||
|
||||
### Reminder Strategy Freeze
|
||||
- Reminder is not a separate business master entity from activity in the future target model.
|
||||
- Reminder is a time-based prompt attached to an activity or milestone event.
|
||||
- Users may receive multiple reminders for one activity without creating duplicate work records.
|
||||
|
||||
### Automation Strategy Freeze
|
||||
Future automation may:
|
||||
- suggest follow-up creation
|
||||
- suggest priority increases
|
||||
- suggest Hot Project activity escalation
|
||||
- generate reminder prompts
|
||||
- escalate manager visibility for overdue work
|
||||
|
||||
Frozen rule:
|
||||
- Automation may propose or publish derived signals, but must not silently fabricate completed business work.
|
||||
|
||||
### Calendar Synchronization Freeze
|
||||
- Scheduled activities appear in calendar.
|
||||
- Reminder prompts appear in calendar only when configured as visible reminder events.
|
||||
- Opportunity milestone dates and quotation milestone dates appear as milestone events, not as activity rows.
|
||||
- Reschedule, cancel, and complete actions must update the calendar projection.
|
||||
|
||||
### Timeline Synchronization Freeze
|
||||
- Activity created
|
||||
- activity assigned
|
||||
- activity rescheduled
|
||||
- activity completed
|
||||
- activity cancelled
|
||||
- outcome summary captured
|
||||
|
||||
All create timeline entries on the related records.
|
||||
|
||||
### Notification Synchronization Freeze
|
||||
Notifications may be created for:
|
||||
- assignment
|
||||
- due soon
|
||||
- overdue
|
||||
- manager escalation
|
||||
- reminder prompt
|
||||
- linked approval dependency
|
||||
|
||||
Frozen rule:
|
||||
- Notification inbox is a delivery surface, not the system-of-record for work.
|
||||
|
||||
## 21. Workspace Interaction Blueprint Freeze
|
||||
|
||||
### Workspace Philosophy
|
||||
Workspace means a role-oriented working surface over shared governed records.
|
||||
|
||||
Frozen rule:
|
||||
- navigation should move users by decision context, not by raw table ownership alone.
|
||||
|
||||
### Daily Operating Pattern
|
||||
The standard operating day is:
|
||||
|
||||
```text
|
||||
My Day -> Customer / Lead / Opportunity / Quotation Workspace -> Calendar / Timeline check -> Follow-up completion -> Manager / Executive review
|
||||
```
|
||||
|
||||
### Marketing Workflow
|
||||
1. Review My Day for overdue and due-today lead activities.
|
||||
2. Open Lead workspace to qualify new demand and capture follow-up outcome.
|
||||
3. Escalate or convert demand into sales-ready handoff.
|
||||
4. Confirm next touch date before leaving the record.
|
||||
|
||||
### Sales Workflow
|
||||
1. Start in My Day for urgent follow-up, meetings, and quotation chases.
|
||||
2. Move into Opportunity workspace for qualification, forecast, and customer coordination.
|
||||
3. Enter Quotation workspace when pricing, revision, or approval work is required.
|
||||
4. Return to Customer workspace when relationship context or cross-project view is needed.
|
||||
5. End the day by closing completed work and scheduling next actions.
|
||||
|
||||
### Manager Workflow
|
||||
1. Review Manager workspace for team overdue work, idle opportunities, approvals, and Hot Projects.
|
||||
2. Jump into Team Calendar for schedule conflicts and near-term commitments.
|
||||
3. Intervene on stalled records through assignment, escalation, and forecast review.
|
||||
4. Finish with tomorrow-risk review rather than only historical KPI review.
|
||||
|
||||
### Executive Workflow
|
||||
1. Review pipeline, revenue outlook, and strategic account movement.
|
||||
2. Use customer relationship and manager signals for exception review.
|
||||
3. Drill into customer, opportunity, or quotation only when escalation or business risk requires it.
|
||||
|
||||
## 22. Customer Workspace Blueprint Freeze
|
||||
|
||||
### Customer Workspace Philosophy
|
||||
Customer is the relationship anchor and must become the main relationship workspace, not only a master-data form.
|
||||
|
||||
### Required Sections
|
||||
- Overview
|
||||
- Contacts
|
||||
- Activities
|
||||
- Timeline
|
||||
- Leads
|
||||
- Opportunities
|
||||
- Quotations
|
||||
- PO / Won History
|
||||
- Files
|
||||
- Notes / Relationship Summary
|
||||
- Upcoming Activities
|
||||
- Recent Visits / Meetings
|
||||
|
||||
### Customer 360 View Freeze
|
||||
Customer 360 must answer:
|
||||
- who owns the relationship
|
||||
- who the active contacts are
|
||||
- what work is next
|
||||
- what open demand exists
|
||||
- what quotation and revenue motion is active
|
||||
- what history and risk the team should know before contacting the customer
|
||||
|
||||
### Relationship Health Freeze
|
||||
Relationship health is a business assessment derived from:
|
||||
- recency of meaningful contact
|
||||
- number of overdue activities
|
||||
- open opportunities without next action
|
||||
- strategic account importance
|
||||
- ownership clarity
|
||||
|
||||
Status bands:
|
||||
- Healthy
|
||||
- Watch
|
||||
- At Risk
|
||||
|
||||
### Follow-up Health Freeze
|
||||
Follow-up health is derived from:
|
||||
- next scheduled activity exists
|
||||
- overdue work count
|
||||
- activity completion discipline
|
||||
- follow-up gap age
|
||||
|
||||
### Customer Timeline Freeze
|
||||
Customer timeline is generated from:
|
||||
- customer updates
|
||||
- contact updates
|
||||
- lead events
|
||||
- opportunity events
|
||||
- quotation events
|
||||
- activity events
|
||||
- PO / outcome events
|
||||
- file / document events
|
||||
|
||||
Frozen rule:
|
||||
- Customer timeline is the relationship history view across all related work, not a separate manually maintained log.
|
||||
|
||||
## 23. Calendar Workspace Blueprint Freeze
|
||||
|
||||
### Calendar Philosophy
|
||||
Calendar is the time-based operational workspace across roles.
|
||||
|
||||
### Calendar Lenses
|
||||
- Personal Calendar
|
||||
- Team Calendar
|
||||
- Manager Calendar
|
||||
- Executive Calendar
|
||||
|
||||
### Calendar Sources
|
||||
- Activities
|
||||
- Meetings
|
||||
- Visits
|
||||
- Site Surveys
|
||||
- Follow-up commitments
|
||||
- Reminder prompts
|
||||
- Expected Award Date milestone
|
||||
- Expected Delivery Date milestone
|
||||
- Approval due / escalation events
|
||||
- Quotation expiration / validity milestone
|
||||
|
||||
Frozen rules:
|
||||
- milestone dates can appear in calendar without becoming standalone activities
|
||||
- milestone events must be visually distinct from owned work
|
||||
|
||||
### Calendar Filters
|
||||
- user
|
||||
- team
|
||||
- branch
|
||||
- customer
|
||||
- lead
|
||||
- opportunity
|
||||
- quotation
|
||||
- activity type
|
||||
- priority
|
||||
- status
|
||||
- Hot Project only
|
||||
|
||||
### Calendar Color Strategy
|
||||
- Follow-up / task work
|
||||
- Meeting / visit work
|
||||
- Reminder prompts
|
||||
- Opportunity milestone
|
||||
- Quotation milestone
|
||||
- Approval due event
|
||||
|
||||
Frozen rule:
|
||||
- colors communicate event family, not authorization level.
|
||||
|
||||
### Calendar Views
|
||||
- Day
|
||||
- Week
|
||||
- Month
|
||||
- Agenda
|
||||
|
||||
Agenda view is the default manager-friendly review surface for operational workload.
|
||||
|
||||
## 24. My Day Blueprint Freeze
|
||||
|
||||
### Purpose
|
||||
My Day is the personalized operational home screen for action-taking users.
|
||||
|
||||
### Required Modules
|
||||
- Today's Activities
|
||||
- Overdue Activities
|
||||
- Upcoming Meetings
|
||||
- Pending Approvals
|
||||
- Hot Projects Requiring Action
|
||||
- Today's Follow-up
|
||||
- Urgent Quotations
|
||||
- Relationship Alerts
|
||||
|
||||
### Priority Ordering Freeze
|
||||
My Day orders work by:
|
||||
1. overdue customer-facing commitments
|
||||
2. due-today committed meetings / visits
|
||||
3. urgent quotation and approval blockers
|
||||
4. Hot Project follow-up gaps
|
||||
5. scheduled upcoming work
|
||||
|
||||
### Urgency Rules
|
||||
Urgency increases when:
|
||||
- customer commitment date is today or missed
|
||||
- expected award date is near
|
||||
- quotation validity is near expiry
|
||||
- manager escalated the record
|
||||
- no next action exists on an open record
|
||||
|
||||
Frozen rule:
|
||||
- My Day should guide the next best operational action, not become a passive report dashboard.
|
||||
|
||||
## 25. Manager Workspace Blueprint Freeze
|
||||
|
||||
### Purpose
|
||||
Manager Workspace is the operational control tower for team execution quality.
|
||||
|
||||
### Required Sections
|
||||
- Team Calendar
|
||||
- Team Activities
|
||||
- Overdue Activities
|
||||
- Idle Opportunities
|
||||
- Forecast Review
|
||||
- Hot Projects
|
||||
- Approval Queue
|
||||
- Workload Balance
|
||||
- Relationship Risk Alerts
|
||||
|
||||
### Daily Management Workflow
|
||||
1. Review overdue and unowned work.
|
||||
2. Review Hot Projects without recent activity.
|
||||
3. Review expected-award opportunities with no next step.
|
||||
4. Review approval queue and quotation blockers.
|
||||
5. Rebalance assignments and escalate risks.
|
||||
6. Review tomorrow's team calendar load.
|
||||
|
||||
### Manager Output Freeze
|
||||
Manager workspace should enable:
|
||||
- coaching
|
||||
- escalation
|
||||
- reassignment
|
||||
- forecast challenge
|
||||
- workload balancing
|
||||
|
||||
It is not only a KPI readout surface.
|
||||
|
||||
## 26. Business Event Blueprint Freeze
|
||||
|
||||
### Event Philosophy
|
||||
Business events are immutable facts emitted from operational changes. One event may fan out to timeline, notification, dashboard, audit, and future automation.
|
||||
|
||||
### Business Event Matrix
|
||||
| Event | Timeline | Notification | Reminder | Dashboard / Workspace | Audit Log | Future Automation |
|
||||
| --- | --- | --- | --- | --- | --- | --- |
|
||||
| Activity Created | Yes | Optional assignment notice | Optional | Yes | Yes | Yes |
|
||||
| Activity Reassigned | Yes | Yes | Optional | Yes | Yes | Yes |
|
||||
| Activity Completed | Yes | Optional | Close outstanding reminders | Yes | Yes | Yes |
|
||||
| Activity Cancelled | Yes | Optional | Close reminders | Yes | Yes | Yes |
|
||||
| Activity Overdue | Optional derived marker | Yes | Yes | Yes | No | Yes |
|
||||
| Lead Created | Yes | Optional | Optional | Yes | Yes | Yes |
|
||||
| Lead Assigned / Handoff Ready | Yes | Yes | Optional | Yes | Yes | Yes |
|
||||
| Opportunity Created | Yes | Optional | Optional | Yes | Yes | Yes |
|
||||
| Opportunity Reassigned | Yes | Yes | Optional | Yes | Yes | Yes |
|
||||
| Expected Award Date Changed | Yes | Optional | Yes | Yes | Yes | Yes |
|
||||
| Hot Project Flagged | Yes | Yes | Optional | Yes | Yes | Yes |
|
||||
| Quotation Created | Yes | Optional | Optional | Yes | Yes | Yes |
|
||||
| Quotation Sent | Yes | Optional | Optional | Yes | Yes | Yes |
|
||||
| Quotation Pending Approval | Yes | Yes | Yes | Yes | Yes | Yes |
|
||||
| Quotation Approved / Rejected / Returned | Yes | Yes | Close or move reminders | Yes | Yes | Yes |
|
||||
| Quotation Expiring Soon | Optional | Yes | Yes | Yes | No | Yes |
|
||||
| Opportunity Marked Won | Yes | Optional | Close forward-chasing reminders | Yes | Yes | Yes |
|
||||
| Opportunity Marked Lost | Yes | Optional | Close forward-chasing reminders | Yes | Yes | Yes |
|
||||
| PO Received | Yes | Optional | Optional | Yes | Yes | Yes |
|
||||
|
||||
Frozen rules:
|
||||
- Audit log records mutation truth.
|
||||
- Timeline records business-readable chronology.
|
||||
- Dashboard / workspace metrics consume aggregated event effects, not raw notification counts.
|
||||
|
||||
## 27. Workspace Navigation Diagram Freeze
|
||||
|
||||
```text
|
||||
My Day
|
||||
|- Customer Workspace
|
||||
| |- Contacts
|
||||
| |- Activities
|
||||
| |- Timeline
|
||||
| |- Leads
|
||||
| |- Opportunities
|
||||
| |- Quotations
|
||||
|
|
||||
|- Lead Workspace
|
||||
| |- Qualification
|
||||
| |- Follow-up
|
||||
| |- Handoff
|
||||
|
|
||||
|- Opportunity Workspace
|
||||
| |- Execution
|
||||
| |- Follow-up
|
||||
| |- Forecast
|
||||
| |- Outcome
|
||||
|
|
||||
|- Quotation Workspace
|
||||
| |- Pricing
|
||||
| |- Revision
|
||||
| |- Approval
|
||||
| |- Customer Package
|
||||
|
|
||||
|- Calendar Workspace
|
||||
| |- Personal
|
||||
| |- Team
|
||||
| |- Manager
|
||||
| |- Executive
|
||||
|
|
||||
|- Manager Workspace
|
||||
| |- Team Activities
|
||||
| |- Forecast
|
||||
| |- Hot Projects
|
||||
| |- Approval Queue
|
||||
|
|
||||
`- Executive Workspace
|
||||
|- Pipeline
|
||||
|- Revenue Outlook
|
||||
`- Strategic Accounts
|
||||
```
|
||||
|
||||
## 28. Customer 360 Diagram Freeze
|
||||
|
||||
```text
|
||||
Customer
|
||||
|- Ownership
|
||||
|- Contacts
|
||||
|- Relationship Health
|
||||
|- Activities / Upcoming Work
|
||||
|- Timeline
|
||||
|- Leads
|
||||
|- Opportunities
|
||||
|- Quotations
|
||||
|- PO / Won History
|
||||
|- Files / Documents
|
||||
`- Notes / Relationship Summary
|
||||
```
|
||||
|
||||
## 29. Daily User Journey Freeze
|
||||
|
||||
### Marketing
|
||||
|
||||
```text
|
||||
My Day -> Lead Queue -> Lead Detail -> Follow-up -> Handoff Ready -> Next Scheduled Action
|
||||
```
|
||||
|
||||
### Sales
|
||||
|
||||
```text
|
||||
My Day -> Opportunity Workspace -> Customer Context -> Quotation Workspace -> Next Activity -> Calendar Check
|
||||
```
|
||||
|
||||
### Manager
|
||||
|
||||
```text
|
||||
Manager Workspace -> Team Calendar -> Overdue / Idle Review -> Forecast Challenge -> Reassignment / Escalation
|
||||
```
|
||||
|
||||
### Executive
|
||||
|
||||
```text
|
||||
Executive Workspace -> Strategic Customer Review -> Pipeline / Revenue Review -> Exception Drill-down
|
||||
```
|
||||
|
||||
## 30. Current-System Alignment Notes
|
||||
|
||||
Current implementation signals already supporting this blueprint:
|
||||
- customer detail already behaves as relationship context plus related opportunity / quotation bridge
|
||||
- opportunity and quotation already contain follow-up, Hot Project, forecast-related date fields
|
||||
- dashboard already aggregates follow-up and Hot Project signals
|
||||
- notification foundation already exists, but current production rules focus mainly on approval events
|
||||
|
||||
Current gaps still intentionally unresolved:
|
||||
- no shared production `Activity` entity yet
|
||||
- no dedicated calendar workspace yet
|
||||
- no My Day workspace yet
|
||||
- manager workspace is not yet implemented as a first-class operational surface
|
||||
- current `workspaces` navigation still refers to organization / team administration, not business role workspaces
|
||||
|
||||
## 31. Freeze Outcome For BU-R.0.1
|
||||
|
||||
This pass extends the original blueprint without changing previously frozen principles.
|
||||
|
||||
Newly frozen business architecture in this pass:
|
||||
- Activity as governed shared work model
|
||||
- Customer Workspace as the relationship execution hub
|
||||
- Calendar Workspace as cross-role time-based operating surface
|
||||
- My Day as user action home screen
|
||||
- Manager Workspace as execution control tower
|
||||
- Business Event Matrix as the fan-out rule for timeline, notification, dashboard, reminder, and audit behavior
|
||||
|
||||
Reference in New Issue
Block a user