# Implementation plan and responsibility record

DOE and NARUC DER Cybersecurity Baselines | Worked example with fictional data

Step: Implement through operations and vendor agreements
Owner: Engineering + procurement + operations change owner
When: Before changes and supplier renewals

## Gather first
- Priority crosswalk
- Support agreements
- Safety procedures
- Change windows
- Acceptance checks

## How to prepare it
1. Assign a lead, system owner, supplier contact and reviewer. Write who operates each shared control and who reports failures.
2. Set the planned change window and acceptance evidence. Define the condition for rolling back and who can make that decision.
3. Review dependencies and safety constraints with operations. Save approval and arrange for a safe follow-up check.

## Example

### Worked supplier handoff
The aggregator maintains the service configuration backup. The utility provides a scheduled test window and signs off on restoration evidence. Both name an escalation contact.

## Review
The implementation has approved roles, timing, acceptance criteria and a rollback decision owner.

## Handoff
Pass the approved work to the change owner and independent reviewer.

Use the current rules and any prescribed forms for your engagement.
