Skip to content

Run Your System

This is the third step in Get Started with AI, once your system is onboarded.

Once the documentation foundation exists, the work that keeps a system certified is operational: vulnerabilities age against their timeframes, changes need notices, incidents need reports, recurring continuous-monitoring obligations fall due, and validations pass or fail. GRC-ITSM handles this with the Operations Meeting, a recurring, recorded review of the system from its own records, with every decision written back to the ticket it concerns.

The full policy and procedure is published as Operations Meetings, with a downloadable KB article you can import into your own instance like the other policy documents.

The shape of it:

Element What it is
One Project per period, one task per meeting Each period (a calendar quarter by default) has one Project per system; each meeting is a Project Task under it carrying the agenda, the meeting note, and the time spent
The status report The meeting's only input: an Excel workbook (.xlsx) rendered from current records before every meeting. An Overview sheet carries the period, headline numbers with their change since last time, a certification-risk block on compliance profiles, the actions for this period, and a Meeting Notes table for items raised in the meeting. One sheet follows per kind of open work: certification risks and obligations on compliance profiles; approvals, alerts, items past SLA, incidents, and remediation on every profile; and KSIs (FedRAMP 20x) or POA&M items (Rev5, CMMC). On each sheet the operations lead fills in three columns during the meeting (Notes, new owner, new due date); the debrief then fills Outcome and Posted.
Certification risks first For a system with a compliance program, open items are ranked by how directly they threaten certification -- Certification-Critical, At Risk, Watch -- from the strength of the FedRAMP rule, the system's class and track, and whether that rule family binds yet. Certification-Critical items leave the meeting with an owner and a date
A fixed nine-item agenda What changed, actions, tasks due across open projects, changes and approvals, register rows, obligations, incidents, and validation posture, decisions, items raised without a ticket, and the debrief assignment. A system with no compliance program runs the seven non-compliance items
Outcomes on the tickets Each discussed ticket receives one note with its decision, action, owner, and due date; the meeting task receives the meeting note; time is logged against the period budget. Decisions reached by email or chat between meetings are captured the same way with their source named

Where AI fits. You prepare and close the meeting with the plugin's guided commands, under the same approval discipline as everything else in Get Started with AI: the plugin drafts every note and change for your review, and nothing posts before you approve it.

  • /grcitsm-analyst:ops-setup -- sets up the operations folder for a system once: connects the tenant, picks the profile (General, FedRAMP 20x, FedRAMP Rev5, or CMMC), records the meeting cadence, and creates the period Project and the standing Remediation project after your approval.
  • /grcitsm-analyst:ops-prep -- before each meeting: pulls current records, builds the agenda, creates the meeting task, and renders the pre-meeting workbook the operations lead takes notes in.
  • /grcitsm-analyst:ops-report -- renders the report workbook for the period since the last report. It changes nothing on the platform.
  • /grcitsm-analyst:ops-debrief -- after the meeting: reads the lead's workbook columns and the transcript, updates the report, and drafts every ticket note for your approval. Approved changes apply as one reviewable change set.
  • /grcitsm-analyst:audit-prep -- on compliance profiles: indexes the period's evidence into an audit packet workbook and, on FedRAMP profiles, renders the Ongoing Certification Report.
  • Between meetings -- bring decisions reached by email or chat to the next debrief; ops-debrief records each on its ticket with the source named.

If you are new to the platform, /grcitsm-analyst:guide is a beginner guide that explains any step in plain words.