Templates & Checklists

Data Contract Template • Policy Definition • Data Quality Rules • Integration Runbook #

---

1 Purpose #

Architectures fail from inconsistency, not ignorance.
EA 2.0 enforces repeatability through structured templates — short, reusable blueprints that every steward, architect, and policy owner can fill without ambiguity.

---

2 Template Categories #

Template Type	Used By	Purpose
Data Contract	Architect + Steward	Define how data moves & what’s guaranteed.
Policy Definition	Governance Lead	Specify rules, triggers, and remediation.
Data Quality Rules	Steward	Quantify “trustworthiness.”
Integration Runbook	Service Mgr	Step-by-step connection and monitoring guide.

---

3 Data Contract Template (Excerpt) #

Field	Example	Guidance
Source System ID	CMDB-SRV-123	Unique identifier.
Target System ID	EA2-Graph	Destination of feed.
Data Owner	john.doe@org	One accountable person.
Update Frequency	Daily 00:00 UTC	Define freshness expectation.
Schema Version	v3.2	Tracked for change control.
Transformation Logic	JSON mapping rules URI	Stored in Git.
DQ Checks Applied	Freshness, Completeness	Reference Rule IDs.
Exception Handling	Retry ×3, log to Event Hub	Must be testable.

Checklist Before Activation:
☑ Owner approved  ☑ Versioned  ☑ Validated schema  ☑ Monitored in dashboard

---

4 Policy Definition Template (Excerpt) #

Field	Example	Description
Policy Name	Tagging Compliance	Unique rule title.
Objective	Ensure all Azure resources have CostCenter tag.	Purpose statement.
Trigger	Resource Created/Updated Event	Event source.
Condition	tags.CostCenter IS NULL	Logical rule.
Action	Auto-add default tag / raise GRC task	Remediation.
Owner	Policy Admin	Single custodian.
Evidence Type	Policy Evaluation Log	Stored for audit.
Review Cycle	Quarterly	Continuous validation.

Checklist Before Publish:
☑ Legal review  ☑ Security sign-off  ☑ Tested in sandbox  ☑ Automated evidence configured

---

5 Data Quality Rules Template (Excerpt) #

Rule ID	Dimension	Metric	Threshold	Action on Fail
DQ-01	Freshness	NOW − last_seen < 7 days	≥ 0.9	Notify Steward
DQ-02	Completeness	Required fields not NULL	≥ 95 %	Reject record
DQ-03	Validity	Regex match on ID format	100 %	Flag DQ error
DQ-04	Uniqueness	No duplicate key	100 %	Auto-merge

Checklist:
☑ Mapped to Data Contract ☑ Logged in DQ Catalog ☑ Alert configured

---

6 Integration Runbook (Excerpt) #

Section	Example	Purpose
Connector Name	ServiceNow CMDB → EA2 Graph	Identification
Auth Method	OAuth 2.0 Client Creds	Security setup
API Endpoint	/api/now/table/cmdb_ci_app	Source data path
Transform Script	cmdb_to_graph.py	ETL logic file
Schedule	Daily 02:00 UTC	Frequency
Error Handling	Retries × 3 → DLQ Event Hub	Resilience
Testing Steps	Run test API → Validate 5 records → Check Graph	Validation
Rollback Plan	Restore last snapshot	Safety

Checklist Before Production:
☑ Credentials vaulted ☑ Runbook tested ☑ Monitoring enabled ☑ Backout plan ready

---

7 Unified Checklist for All Templates #

Area	Validation
Ownership	Each artifact has an Entra ID owner.
Versioning	Semantic version in header (vX.Y.Z).
Storage	Saved in Git/SharePoint with retention policy.
Review Cycle	Quarterly review automated reminder.
Audit Trace	Signed commit or timestamped upload.

---

8 Embedding in EA 2.0 Platform #

• Templates stored in SharePoint “Playbook Assets.”
• Reasoning API can generate draft Data Contracts from existing feeds.
• Power BI dashboard shows completion status (% templates filled).

---

9 Benefits #

✅ Standardizes execution across teams.
✅ Reduces setup time for new integrations.
✅ Improves audit readiness.
✅ Links governance policy to operational reality.

---

10 Takeaway #

Templates don’t slow you down — they keep you aligned.
In EA 2.0, consistency is the currency of trust, and these templates are its ledger.