Every new Innomesh tenancy is provisioned with a default set of room information fields. This set covers the metadata most organisations need on day one (location, capability, support contacts, documentation, and management links) and is intended as a starting point rather than a fixed schema. This article lists each default field, its type, its validation, and what it drives in Innomesh Portal.
How the Default Set Is Applied
Default fields are defined in an information template, which is linked to a deployment template in Innomesh Room Manager. When a room is created, it inherits every field in the information template attached to its deployment template. See Room Information Onboarding for the creation workflow.
The default set is a recommendation, not a constraint. During onboarding you can:
- Rename fields to match your internal terminology.
- Remove fields that do not apply to your estate.
- Add organisation-specific fields.
- Convert a Text field into an Enum once the list of valid values is known.
Field Types
Each field is configured with a type that determines how it is captured in Room Manager and rendered in Portal.
| Type | Behaviour |
|---|---|
| Text | Free text entry. Can be constrained with a regular expression and help text. |
| Number | Numeric entry only. Can be constrained with a regular expression. |
| Enum | Dropdown selection from a fixed list of values defined during onboarding. |
| Hyperlink | URL entry, validated against a URL pattern. Rendered as a clickable link in Portal. |
| File | File upload. Images, PDFs, and configuration files are supported depending on the field. |
Several defaults are listed as “Text or Enum”. Most of these ship as Text so rooms can be onboarded before the value list is finalised, then convert to Enum once your organisation has agreed on the permitted values. Primary Usage is the exception: it ships as Enum with a starter value list.
Platform-Managed Fields
These fields are populated automatically by Innomesh and are mandatory on every room. They exist so that room information can be reliably matched back to the room record, and so that changes are attributable.
| Field | Type | Description |
|---|---|---|
| Room ID | Text | Unique room identifier assigned by the platform. |
| System ID | Text | Unique system identifier assigned by the platform. |
| System Name | Text | System name assigned by the platform. |
| User Group | Text | User group the room belongs to, used for access control. |
| Last Updated By | Text | Name of the user who last changed the room information. |
| Last Updated Date | Text | Date the room information was last changed. |
Location and Ownership Fields
These fields describe where a room is and who is responsible for it. They are the fields most commonly used for filtering, grouping, and access control in Portal.
| Field | Type | Required | Example / Values | Notes |
|---|---|---|---|---|
| Site | Enum | Yes | City Campus | Required to enable site-based access control. Often used synonymously with “campus” in education deployments. |
| Building | Text or Enum (Text by default) | No | Client-supplied list | Building name. Convert to Enum once the building list is confirmed. |
| Faculty | Text or Enum (Text by default) | No | Client-supplied list | Owning faculty, school, or business unit. |
| Ownership | Enum | No | Centrally Owned, Departmentally Owned | Who funds and owns the room. |
| Support Level | Enum | No | Yes, No, VIP | Support tier applied to the room. |
| Location | Hyperlink | No | https://maps.example.com/room-101 | Populates the Location tab on the Room Information View in Portal. |
Room Characteristic Fields
These fields describe what the room is and what it can do. They drive most of the comparison and reporting use cases on the Information page.
| Field | Type | Required | Example / Values | Notes |
|---|---|---|---|---|
| Facility Type | Text or Enum (Text by default) | Yes | Digital Signage, Huddle Space, Meeting Room Large, Meeting Room Small, Recording Room, Teaching Collaborative, Teaching Single Display, Teaching Dual Display, Teaching Multi-Display, Tutorial Space | Shipped as Text with a recommended value list. Convert to Enum once your room taxonomy is agreed. |
| Primary Usage | Text or Enum (Enum by default) | No | Meeting, Teaching, Conference, Other | Main purpose of the room. |
| Seating Capacity | Number | No | 100 | Maximum number of occupants. |
| Control | Enum | No | Cloud, Local | Where room control is hosted. |
| Video Conferencing | Enum | No | Yes (Teams), Yes (Zoom), Yes (Google), Yes (Cisco), No | Video conferencing platform available in the room. |
| Lecture Recording | Enum | No | Yes, No | Whether the room supports lecture capture. |
| Commission Date | Text | Yes | 30/11/2022 | Validated as DD/MM/YYYY. Prefilled with today’s date when the room is created. |
| Installation Year | Number | Yes | 2000 | Validated as a four-digit year (19XX or 20XX). Prefilled with the current year when the room is created. |
| Notes | Text | No | Free text | General notes about the room. |
Contact Fields
| Field | Type | Required | Example | Notes |
|---|---|---|---|---|
| Phone Number | Text | No | 123456789 | Phone number of the handset in the room. Numbers only. |
| Helpdesk Number | Text | No | 123456789 | Support number displayed to room users. Numbers only. |
Documentation and Media Fields
These fields feed the media tabs on the Portal Room Information View. Image files (JPG, PNG, GIF) uploaded to a File field appear in the Image Gallery.
| Field | Type | Required | Notes |
|---|---|---|---|
| Room Profile Photo | File | Yes | Used as the room’s profile photo in the Room Information View. |
| Room Photo | File | No | Appears in the Image Gallery. |
| Lectern (Image) | File | No | Appears in the Image Gallery. |
| User Interface (Image) | File | No | Appears in the Image Gallery. |
| Room 360 View | File | No | Populates the 360 View tab on the Room Information View. |
| Floorplan | File | No | Adds a Floorplan link to the Room Information View. |
| Schematics | File | No | Populates the Schematics tab on the Room Information View. |
| Cable Schedule | File | No | Cable schedule document for the room. |
| DSP Profile | File | No | DSP design file. |
| Switcher Profile | File | No | Switcher configuration file. |
| Video Guide | Hyperlink | No | Link to an instructional or overview video for the room. |
Link Fields
Hyperlink fields hold URLs to systems outside Innomesh. All of them use the same URL validation pattern (see Appendix: Validation Patterns).
| Field | Type | Notes |
|---|---|---|
| Schedule | Hyperlink | Adds a View Room Schedule link to the Launchpad pane in the Room Support View. |
| Camera URL | Hyperlink | Adds a View Room Camera link to the Launchpad pane in the Room Support View. |
| Recorder URL | Hyperlink | Adds a View Recorders link to the Launchpad pane in the Room Support View. |
| Controller URL | Hyperlink | Management interface of the room controller. |
| Touch Panel URL | Hyperlink | Management interface of the touch panel, not the web panel used for room control. |
| Display URL | Hyperlink | Management interface of the room display. |
| DSP URL | Hyperlink | Management interface of the DSP. |
| Switcher URL | Hyperlink | Management interface of the switcher. |
| Video Conference Device URL | Hyperlink | Management interface of the video conferencing endpoint. |
Recommended Onboarding Approach
- Start with the full default set rather than trimming it up front. Unused fields are easier to remove later than missing fields are to backfill.
- Confirm the value lists for Site, Building, and Faculty with the customer before creating rooms, since these drive access control and filtering.
- Populate Site, Facility Type, Commission Date, Installation Year, and Room Profile Photo for every room. These are required and appear throughout Portal.
- Convert Text fields to Enum once value lists stabilise. This prevents inconsistent spelling from fragmenting your filters.
- Add media and link fields last. They improve the support experience but are not needed for a room to go live.
Related Articles
Appendix: Validation Patterns
Text and Number fields can be constrained with a regular expression. The default set uses three patterns.
URL
Applied to every Hyperlink field.
^(http:\/\/www\.|https:\/\/www\.|http:\/\/|https:\/\/)?[a-zA-Z0-9]+([\-\.]{1}[a-zA-Z0-9]+)*\.[a-z]{2,5}(:[0-9]{1,5})?(\/.*)?$Help text: “Enter hyperlink in the format http://… or https://…”
Date (DD/MM/YYYY)
Applied to Commission Date.
^(0?[1-9]|[12][0-9]|3[01])/(0?[1-9]|1[012])/\d{4}$Help text: “Enter date in the format DD/MM/YYYY”
Year
Applied to Installation Year.
^(19|20)\d{2}$Help text: “Enter year in the format 19XX / 20XX”
Appendix: Complete Default Field List
The full default set in alphabetical order, as shipped in a new tenancy.
| Field | Type | Required | Help Text |
|---|---|---|---|
| Building | Text or Enum (Text by default) | No | Enter building name |
| Cable Schedule | File | No | Upload cable schedule file |
| Camera URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Commission Date | Text | Yes | Enter date in the format DD/MM/YYYY |
| Control | Enum | No | Select type of control |
| Controller URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Display URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| DSP Profile | File | No | Upload DSP design file |
| DSP URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Facility Type | Text or Enum (Text by default) | Yes | Select facility type of this room |
| Faculty | Text or Enum (Text by default) | No | Enter faculty |
| Floorplan | File | No | Upload floorplan file |
| Helpdesk Number | Text | No | Enter helpdesk phone number (numbers only) |
| Installation Year | Number | Yes | Enter year in the format 19XX / 20XX |
| Last Updated By | Text | Yes | Autopopulated by the platform |
| Last Updated Date | Text | Yes | Autopopulated by the platform |
| Lectern (Image) | File | No | Upload image file |
| Lecture Recording | Enum | No | Select recording capabilities |
| Location | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Notes | Text | No | (none) |
| Ownership | Enum | No | Select room ownership status for this room |
| Phone Number | Text | No | Enter room phone number (numbers only) |
| Primary Usage | Text or Enum (Enum by default) | No | Select primary usage type |
| Recorder URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Room 360 View | File | No | Upload image file |
| Room ID | Text | Yes | Autopopulated by the platform |
| Room Photo | File | No | Upload image file |
| Room Profile Photo | File | Yes | Upload image file |
| Schedule | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Schematics | File | No | Upload schematics file |
| Seating Capacity | Number | No | Enter maximum number of occupants |
| Site | Enum | Yes | Select site where this room is located |
| Support Level | Enum | No | Select type of support |
| Switcher Profile | File | No | Upload switcher configuration file |
| Switcher URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| System ID | Text | Yes | Autopopulated by the platform |
| System Name | Text | Yes | Autopopulated by the platform |
| Touch Panel URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| User Group | Text | Yes | Autopopulated by the platform |
| User Interface (Image) | File | No | Upload image file |
| Video Conference Device URL | Hyperlink | No | Enter hyperlink in the format http://… or https://… |
| Video Conferencing | Enum | No | Select type of video conferencing available |
| Video Guide | Hyperlink | No | Enter hyperlink in the format http://… or https://… |