Electrical · Punch

Goodbye WeChat group, hello closed-loop Punch

Every Punch bound to an owner + due date, AgingDays color-graded, closure feeds back into MC live.

A-class blocks RFCC, B-class doesn't but is tracked to closure — defect grading matches class-society practice.

Defect closed-loop flow

1
Found in MC
Defect surfaced during MC inspection, raise Punch (must link to an existing MC row)
2
Register defect
PunchGrade (A/B), Description, Responsible, DueDate
3
Dispatch
Owner is notified, AgingDays calculated live, color-graded
4
Closed
Status marked Closed, closure date recorded
5
Feed back into MC
InspectionStatus on the parent MC row is recomputed
6
RFCC unblock
Only when all A-class items close does the subsystem RFCC go READY

Punch cannot be raised in a vacuum — it must hang off an existing MC row. No orphan defects.

TagNo + CheckSheetCategory stay consistent with the parent MC row.

Open 7/14/30 days steps the color up; closed items get their own palette. Risk visible at a glance.

A blocks RFCC, B is only tracked. Matches both class-society and owner habits.

Install-phase defects go to PAT; Punch is exclusively for the MC inspection process. Paths stay clean.

Batch close, batch re-assign — every action lands in the activity log.

Real product screenshot · from H588 NORSE WIND project (v4.3)

Punch records are tightly bound to MC records, forming the defect closed loop.

Field	Description	Note
PunchCode	Defect code (system-generated)	Unique
McRecordId	Linked MC inspection record	Required · immutable
TagNo	Inherited from MC row	Read-only
PunchGrade	A / B class	Drives RFCC blocking
Description	Defect description	Single-line truncate + tooltip
Responsible	Owner	Drives notification & KPI
DueDate	Due date	Drives AgingDays calculation
Status	Open / Closed	Closed feeds back into MC