iShield Solutions Series, Employee Experience · Workplace
Workplace & Facilities Experience
One Room, Three Records, No Swivel Chair
Workplace & Facilities Experience treats a room as what it really is: a booking in iShield Connect, a maintained asset in iShield One and a set of technology items in iShield Nexus. Each record is meant to stay with its owner and each request to reach the right one.
Desks, rooms, visitors and maintenance on one platform with the asset and contract ledger.
Who leads, who contributes
- LeadiShield Connect
- ContributoriShield One
- ContributoriShield Nexus
Workplace service delivery, room and desk booking and visitor management — the employee and visitor experience.
The enterprise challenge
Employees experience one workplace. Systems see three.
Booking a room, reporting a broken display and requesting a new desk feel like one experience to an employee. Behind the scenes they touch the booking system, the facilities work-order system and the IT asset record, and the request is retyped at every step.
A connected workplace keeps each record where it belongs — bookings in the experience platform, the building and its maintenance in the estate platform, devices in the technology platform — and links them through the space they share.
Where iShield Nexus contributes
iShield Nexus contributes service fulfillment and operational workflows: the workplace service catalog and the technology assets tied to people and rooms (Service Catalog, Asset Management). iShield Connect leads the workplace service experience; iShield One contributes estate, maintenance and finance transactions.
The Nexus angle
Workplace services and facility assets need one request and record model.
- Technology services and controls are managed apart from the business process
- Evidence and ownership are fragmented
Solution overview. Workplace Service Delivery handles bookings, visitors and service requests; iShield One Property & Maintenance tracks the physical estate and work orders; Nexus Asset Management ties devices to people and rooms.
Buyer challenges
Requests in the wrong queue
A broken screen in a meeting room goes to facilities, then IT, then back, because nobody knows which record owns it.
Utilisation guessed
Space decisions rely on badge swipes and surveys rather than on bookings and actual use.
Maintenance without context
Work orders lack the booking schedule, so repairs disrupt meetings that could have been moved.
Visitors as paperwork
Pre-registration, badges and safety lists are kept apart, so an evacuation list is incomplete.
Decision owners
- Head of workplace experience
- Booking rules, neighbourhoods and the visitor experience.
- Facilities manager
- Maintenance plans, work-order priorities and contractor assignment.
- IT asset manager
- Which devices are assigned to which people and rooms.
- Sustainability lead
- Which energy and occupancy signals feed sustainability reporting.
Cross-platform journey
One room, followed through a working week
Follow a meeting room. Its three layers — the booking, the building asset and the technology inside it — are shown together; each step lights the layer that owns it.
- Book · Room & Desk Booking iShield Connect
- Welcome a visitor · Visitor Management iShield Connect
- Ask for help · Service Catalog iShield Nexus
- Identify the asset · Asset Management iShield Nexus
- Coordinate the fix · Workplace Service Delivery iShield Connect
- Maintain the room · Facility & Maintenance Work Orders iShield One
- Report energy and use · Energy & Sustainability iShield One
Stage 1 of 7 · iShield Connect Book
An employee books the room under the team's rules.
- Decision
- Workplace experience sets the rules.
- Exception path
- A conflict offers the nearest suitable alternative.
- Recorded as
- Booking record
Next: Welcome a visitor in Visitor Management (iShield Connect)
This journey shows how responsibilities are intended to divide between the platforms. It describes an operating model, not a pre-built integration between them.
Who leads, who contributes, and where each stops
This is a cross-product solution. Each platform keeps its own responsibility and boundary; none is presented as a module of another.
- iShield ConnectLead
Owns
Workplace service delivery, room and desk booking and visitor management — the employee and visitor experience.
Boundary
Does not maintain the building or own IT asset records.
- iShield OneContributor
Owns
Estate, finance and business transactions: property and real estate, facility and maintenance work orders, energy and sustainability.
Boundary
Does not run bookings or IT asset records.
- iShield NexusContributor
Owns
Service fulfillment and operational workflows: the workplace services offered in the service catalog and the technology assets assigned to people and rooms.
Boundary
Does not book spaces, manage visitors or maintain the building.
Module responsibilities
| Module | Platform | Responsibility in this solution | Hands on |
|---|---|---|---|
| Service Catalog | iShield Nexus | Presents workplace services with their request forms and approvals. | Requests to the owning team |
| Asset Management | iShield Nexus | Records devices and their assignment to people and rooms. | Asset and assignment records |
Published composition, by owning platform
The modules in the solution's published composition, grouped by the platform that owns them.
iShield Nexus
Why this composition
A room is a Connect booking, a One maintenance asset and a Nexus IT-equipment record at the same time. Joining all three is intended to support accurate utilisation, condition-based maintenance and sustainability reporting without re-keying the same request in three places.
Intelligence in explicit modes, by platform
Nexus AI capabilities assist the people involved; decisions remain with accountable owners.
- Assistance drafts, answers or summarizes
- Recommendation proposes for a person to accept
- Predictive anticipates or flags
- Workflow-triggered runs only as configured and approved
Conversational search
RecommendationSuggests the right workplace service from a natural-language query.
Service Catalog — Conversational searchRelationship suggestions
RecommendationProposes likely device-to-room relationships for the asset owner to confirm.
Asset Management — Relationship suggestions
Decisions, exceptions and who owns them
Approvals and asset history are recorded.
| Decision | Accountable owner | Evidence recorded | Exception path |
|---|---|---|---|
| Set booking rules | Head of workplace experience | Rules per space and team | Exceptions for accessibility needs are recorded with the person's consent. |
| Prioritize a work order | Facilities manager | Work order with booking impact | Emergency work notifies affected bookings. |
| Assign a device to a room or person | IT asset manager | Assignment on the asset record | Unassigned devices open an asset-data task. |
| Report sustainability signals | Sustainability lead | Selected signals and their sources | Missing telemetry is disclosed as a gap. |
How workplace obligations are handled
Visitor safety, privacy of occupancy data and labour rules are set by the organization's workplace, privacy and HR owners. The platforms record bookings, visits, requests and work orders against those rules; no regulatory mapping is pre-built.
- Occupancy data is reported at the level the privacy owner approves.
- Visitor safety lists are kept by iShield Connect for the duration the policy sets.
- Request approvals and asset history are recorded on the Nexus service request and asset record.
Regulatory context
Regulations and frameworks organizations in this domain commonly work with. Listed as context for planning, not as a certification, attestation or pre-built mapping.
Recognized practice behind the operating model
Mappings describe how the operating model aligns with recognized practice. They are not attestations or certifications.
Workplace requests in Nexus follow the ITIL 4 service catalog and request practices mapped on the accepted Service Catalog page, and device records follow the IT asset management practices mapped on Asset Management.
| Framework | Practice | How the solution operates | Relationship |
|---|---|---|---|
| ITIL 4 | Service Catalog Management | Workplace services are offered through one catalog with consistent request and approval discipline.Mapped on the accepted Service Catalog page. | Aligned practice |
| ISO/IEC 19770-1:2017 | IT asset management system | Devices in workplace spaces are recorded with assignment and lifecycle.Mapped on the accepted Asset Management page. | Aligned practice |
What changes for the organization
Outcomes are described qualitatively. Figures are published only once evidenced.
Requests reach the right owner
Once the room's three records are linked, a request can start with the right one.
Maintenance around meetings
Work is planned with the booking schedule in view.
Space decisions from real use
Bookings and occupancy inform how space is planned.
Complete safety lists
Visitors are registered before they arrive.
What sets this solution apart
Requests with the room attached
Workplace requests arrive with the space and its assets already identified.
Nexus as contributor
Nexus supplies the catalog and the device record; it never presents itself as the workplace or facilities platform.
Delivery and industry context
Planning information carried over from the solution record.
30 / 60 / 90-day value plan
Days 0–30 — Foundation
Stand up the iShield workspace, integrate sources of truth, ingest baseline data.
- Tenant provisioned in chosen region (KSA / UAE / EU / US)
- SSO + RBAC mapped to enterprise identity (Entra ID / Okta)
- Top 5 integrations connected and reconciled
- Baseline KPIs measured before any change
Days 31–60 — Activation
Turn on automation, AI agents and guardrails for the priority value stream.
- Workflows live for the top 3 use cases
- Link AI agents enabled with explicit guardrails and approvals
- Power-user enablement and admin training complete
- First measurable KPI improvement vs baseline
Days 61–90 — Scale
Industrialize, roll out to additional teams, prove ROI to the steering committee.
- Solution rolled out to additional business units / geos
- Executive dashboard with target vs actual outcomes
- Continuous improvement backlog established
- Signed ROI memo and renewal / expansion plan
Personas served
Illustrative industry scenarios
Representative situations by industry. Regulations named here are context, not certifications or commitments.
Energy, Oil & Gas
Workplace & Facilities Experience extended to OT estates via iShield Link OT bridge.
Public Sector (KSA Vision 2030 / UAE Digital Government)
Workplace & Facilities Experience delivered on sovereign cloud with NCA / TDRA alignment.
Healthcare
Workplace & Facilities Experience with HIPAA / NPHIES-aware data flows and PHI guardrails.
