Introduction¶
IMS helps implementation teams manage the complete path from a product requirement to a client-specific implementation. Teams can review what data is required, understand how entities and fields are used downstream, record contextual notes, evaluate measure impact, and export information for onboarding and implementation work.
Core IMS Concepts¶
IMS follows this hierarchy:
Product
→
Specification Version
→
Implementation
→
Module
→
Entity/Table
→
Field
| Concept | Description |
|---|---|
| Product | A business solution, such as Crimson AI. |
| Specification | The complete set of product requirements. |
| Specification Version | A point-in-time version of a specification. |
| Implementation | A client-specific workspace linked to a specification version. |
| Module | A logical business grouping of requirements. |
| Entity/Table | A data object required by an implementation. |
| Field | An individual attribute within an entity. |
Specifications vs. implementations
A specification defines standard product requirements. An implementation applies those requirements to a specific client and adds client-specific context.