Glossary

• Admin User: A user authenticated with the admin credentials configured in the environment. Admin users can review feedback logs and suggested pain-point logs.
• Affiliation: The required organization or institutional field entered at sign-in. Grid-ION stores it with session-based feedback and suggestion submissions.
• Ancestor Class: In the Data Object Schema workspace, a CIM class that the active class inherits from.
• Association: A class-to-class relationship shown in the Data Object Schema workspace alongside inheritance relationships.
• Business Spec Dashboard: The business-side summary tab that presents the current planning outputs after entering the Business workflow.
• Business User: The persona intended for users framing the why, what, and value of a grid program before technical design details are explored.
• Canonical Actor Order: The fixed actor precedence used in the interactive technical sequence canvas: Market Operator -> BPSO -> DSO -> Aggregator -> Resource Manufacturer -> Resource -> Customer.
• Chat Boundary Cleanup: The session-protection step that can run before logout or certain session transitions so chat and workspace state are handled cleanly.
• CIM: Common Information Model. Grid-ION uses CIM-oriented class, attribute, inheritance, and association data as the foundation for the Data Object Schema workspace.
• CIM101 Library: The class library panel in the Data Object Schema workspace from which users drag classes into the schema canvas.
• Class Tree View: The center column of the Data Object Schema workspace where canvas classes are shown, configured, and exported.
• Common Login: The shared sign-in experience used by both standard users and admin users.
• Data Object Schema: The technical workspace used to explore CIM classes, choose attributes and related classes, and generate/export schema previews.
• Descendant Class: In the Data Object Schema workspace, a CIM class that inherits from the active class.
• Dual User: The persona intended for users who need business framing and technical design in the same session.
• Feedback Log: The repository-backed file created when a signed-in user submits the Provide Feedback form.
• Glossary Resources: The Resources page in the Options menu that summarizes internal source touchpoints and external standards references used by the app.
• Home Button: The tab-style navigation button shown only after entering a workspace. It returns the user to the persona-selection home page.
• Logout: The authenticated session action in the header that ends the current signed-in session and returns the user to the sign-in screen.
• Pain-Point Suggestion Log: The repository-backed file created when a signed-in user submits the Suggest a Pain-Point form.
• Persona Home Page: The post-login landing page that presents the Business User, Technical User, and Dual User cards.
• Provide Feedback: The structured survey form available from the Options menu after a persona session is active.
• Relationship Graph: The graphical portion of the active CIM class view that shows ancestors, descendants, and associations around the center class.
• Review Feedback: The admin-only Options entry used to inspect, copy, and delete saved feedback logs.
• Review Suggested Pain-Point: The admin-only Options entry used to inspect, copy, and delete saved pain-point suggestion logs.
• Schema Preview: The right-side preview area in the Data Object Schema workspace that reflects the currently included classes and attributes, with collapsible LinkML and raw export-format views.
• Semantic Dependency: The technical dependency view that explains how actors, functions, and information exchanges relate in the technical workflow.
• Session Identity: The authenticated username, affiliation, and auth kind currently associated with the running session.
• Suggest a Pain-Point: The structured overlay form used to capture an additional business pain-point suggestion for later admin review.
• Technical User: The persona intended for users translating program specifications into functions, exchanges, UML sequences, and schema artifacts.
• Top-Level Class: A root class currently included on the schema canvas rather than a class pulled in only through relationship selections.
• UML Sequence Diagram: The technical diagram showing the order of interactions and message exchanges between participating actors.
• User Guide: The in-app operational guide available from the Options menu.