CONN-FIC-001 · fictional example
Life safety and emergency communications
Unverified
- Observed
- No related life-safety fault observed; emergency phone path not yet tested
- Customer effect
- Potential consequence is high if unavailable
- Approved fallback
- Use facility emergency procedure and approved emergency contact path
- Do not
- Do not substitute a personal contact path or ignore a physical hazard
- Owner
- site manager
- Reconcile
- Test approved emergency communication path
CONN-FIC-002 · fictional example
Existing gate access
Local Only
- Observed
- Approved local test accepts an existing fictional credential
- Customer effect
- Existing authorized access may continue; new changes remain unverified
- Approved fallback
- Continue only under approved local-operation procedure
- Do not
- Do not prop gate open, share master credentials or bypass controls
- Owner
- site manager and access-system owner
- Reconcile
- Verify synchronization and every queued access change after restoration
CONN-FIC-003 · fictional example
Business phone
Available
- Observed
- Approved business line completes a test call
- Customer effect
- Customer calls can continue
- Approved fallback
- Use the approved business line and outage wording
- Do not
- Do not publish or use a personal phone number as the business line
- Owner
- site manager
- Reconcile
- Retest at next review
CONN-FIC-004 · fictional example
Payment processing
Paused
- Observed
- Approved payment portal and terminal cannot reach processor
- Customer effect
- Payment cannot be represented as complete
- Approved fallback
- Use only a documented processor-approved alternative, if one exists
- Do not
- Do not write card data, email it, store it in notes or use an unapproved device
- Owner
- site manager and payment-process owner
- Reconcile
- Contact customer through approved channel after secure path returns
CONN-FIC-005 · fictional example
New rental and unit release
Paused
- Observed
- Online rental and authoritative customer record are unreachable
- Customer effect
- New rental cannot be verified or released
- Approved fallback
- Create a non-sensitive pending-item reference and use the approved follow-up process
- Do not
- Do not release a unit or promise completion without a verified rental and payment state
- Owner
- site manager
- Reconcile
- Complete or cancel once in authoritative system; check duplicates
CONN-FIC-006 · fictional example
Email and customer messaging
Degraded
- Observed
- Business email is unreachable from office workstation
- Customer effect
- Email responses are delayed
- Approved fallback
- Use approved business phone and truthful outage wording
- Do not
- Do not move customer correspondence to personal email or unapproved messaging
- Owner
- site manager
- Reconcile
- Reconcile messages and avoid duplicate replies after restoration
CONN-FIC-007 · fictional example
Camera visibility and remote alerts
Local Only
- Observed
- Local monitor displays video; cloud recording and remote alerts are not tested
- Customer effect
- Local visibility may continue while remote functions are unknown
- Approved fallback
- Apply approved local observation and escalation procedure
- Do not
- Do not claim recording or remote alerts are working based only on a local image
- Owner
- site manager and security-system owner
- Reconcile
- Verify recording, remote access and alert continuity after restoration
CONN-FIC-008 · fictional example
Work-order and facility records
Paused
- Observed
- Cloud work-order system is unreachable
- Customer effect
- Non-emergency updates are delayed
- Approved fallback
- Use approved outage record for minimal non-sensitive pending-item references
- Do not
- Do not mark work complete or create conflicting permanent records
- Owner
- site manager and maintenance owner
- Reconcile
- Reconcile once against authoritative work-order system