OMNIFacilities
Sign in

KEEP OMNI ONE TAP AWAY

Install OMNI Facilities

OMNI FacilitiesYour facility workspace, in its own app

    Use your existing account. Internet access is required.

    View the full setup guide

    Project

    General

    Profile

    OMNI FACILITIES / HELP CENTRE

    A guide for every role.

    From the first request to the final approved report.

    Version 0.8.2 · Updated 7 November 2026

    01 / Your account and project workspace

    Get started

    Open your dashboard

    Sign in at your organisation's OMNI Facilities address. The homepage can open a project dashboard directly. Use the project name in the top bar to switch facilities. Only projects available to your account appear.

    Register as a normal user

    Open the project registration link supplied by your hospital, or choose Join a project on the sign-in page. Verify your email, then enter your name, username and password. A new account remains inactive until a Project Admin approves access and assigns a role. Existing users sign in with the same account.

    Public and private facilities

    Private facilities and projects with approved-membership admission require project membership. An account active elsewhere does not bypass approval. Existing public portal access remains only where ADF retains that policy. Requesters see their own requests and progress, never other users’ reports.

    Your dashboard

    Requesters see their own request progress. Coordinators see assignments and exceptions. Technicians see assigned work. Managers see approvals and SLA attention. Sidebar badges count open records available to your role, excluding removed work orders and requests whose linked work is closed.

    Before your first request

    If no project is available, ask your project administrator or ADF to confirm activation, project membership and role. Do not create a second account to work around missing access.

    02 / The right access in each facility

    Roles and responsibilities

    Requester

    Submit a service request with a problem title, description and optional files. View your own requests and their progress. No staff settings, other users' requests or bulk reporting access.

    FM Coordinator

    Review all project requests and work orders, fill operational details, choose Low / Normal / High priority and assign a technician. Maintain registers and PPM plans. Remove inappropriate work orders from the active queue with an audited reason; the history is retained.

    Technician / engineer

    See assigned work orders and related requests. Start Work, optionally put work On Hold with a reason, Resume and submit completion. Record permitted material issues and returns. Technicians cannot delete work orders or approve their own completion.

    Manager and storekeeper

    Managers review submitted completion and approve or return it for revision. Managers can see project reporting. Storekeepers maintain inventory movements and related work-order references. Combining roles combines their permissions within that project.

    Project Administrator and ADF Administrator

    ADF creates projects and invites the first Project Admin. Project Admins manage profile details, verified registrations and project roles. ADF alone controls internal Redmine settings, global accounts and administrator-delegation policy. A Project Admin can appoint another Project Admin only where ADF enables delegation.

    03 / Report a problem in a few steps

    Service requests

    1. Open Service Requests

    Check that the correct facility is selected, then choose Submit Service Request. A requester does not need to complete the detailed maintenance form.

    2. Explain the problem

    Enter a clear title and a useful description: what happened, where it happened and any access details. Add photos or documents when helpful. Check the file-size limit shown by the application.

    3. Submit once

    A successful request automatically creates a linked work order in Pending Technician Assignment. The coordinator receives an email when workflow email is enabled and delivery is configured. The requester does not manually create or convert the work order.

    4. Follow progress

    Open your request to see its linked work status. The request number and work-order number are different references for the same service journey. If creation is pending, the coordinator can retry conversion after checking the automation error; avoid duplicate manual jobs.

    Use filters and sorting

    Search the request list, narrow status or dates and select a column heading to sort. Select again to reverse direction. Main registers sort all matching results before pagination. Dashboard summaries sort only their displayed rows.

    04 / Review, plan and assign the work

    Coordinator workflow

    1. Open the linked work order

    From the request list choose Review & assign, or open the assignment queue. The request is already linked to a work order. Review the original description and attachments before planning the job.

    2. Keep the original operational fields

    The work-order form keeps the original record fields while grouping the important entries. Confirm location, asset or service category where applicable, describe the work and choose priority: Low, Normal or High. Complete the fields required by your organisation.

    3. Assign a technician

    Choose an active eligible project technician and set a due date where required. Save the assignment. A notification is queued for the assigned account when workflow email is enabled; changing assignment does not bypass project access.

    4. Handle inappropriate requests

    Use the work-order removal action and provide a reason. This removes the job from active queues with an audit trail. Do not destroy the request or bypass the audit through native record tools.

    5. Watch exceptions

    Use filters for unassigned, due, approval and SLA attention. A missing technician often means the account is inactive, lacks membership or has not received the Technician role in this project.

    05 / Start, hold, resume and complete

    Technician workflow

    Start Work

    Open an assigned work order and select Start Work when work begins. OMNI records the server timestamp and actor. Starting work is required before submitting completion in this release.

    Optional On Hold

    Use On Hold only when work must stop. Enter a useful reason such as waiting for a part or access. The hold is timestamped. Choose Resume when work continues; another hold can be recorded later if needed.

    Complete Work

    After work is running, enter completion notes, attach evidence where available and choose an internal manager or an external email reviewer. Submit completion. The completion timestamp stops the work timer and moves the job to Awaiting Approval.

    Understand the time figures

    Elapsed work time adds the recorded start/resume-to-completion cycles, including holds and excluding time waiting for approval. On-hold time is the total recorded pause duration. Working time excludes holds and waiting for approval. Returned work requires Resume; its previous events stay in the history.

    Read the report correctly

    The work order and completion report show timestamps, holds and elapsed / working time. Approved reports keep a snapshot of the approved submission. Older jobs without timing events show no recorded timing; the app does not invent historical start times. Report timestamps use Asia/Kuala_Lumpur in this release.

    06 / Close the job with a recorded decision

    Completion and approval

    Internal approval

    The technician selects an eligible internal manager when submitting completion. The manager opens the approval notification or approval queue, reviews notes and evidence, then approves or returns the work with comments. A technician cannot approve their own completion.

    External approval

    Choose external approval and enter the reviewer's email during completion. The system emails a signed, expiring review link when email delivery is enabled. The external reviewer can inspect that submission and approve or return it without a Facilities account.

    Protect the review link

    Treat an external review link as confidential. It grants access to that job's review. It is not a login or access to the project. Expiry, resubmission and an already-recorded decision prevent reusing the link for a different decision.

    Returned work

    Read the reviewer's comments, resume work, update the completion notes and submit again. A new submission needs a new approval. Repeatedly refreshing an old external link cannot approve a new version.

    Approved reports and email

    After approval the completed report is available for download and can be sent to the requester, assigned technician, coordinator and nominated reviewer as configured by the workflow. Sender: notification@adftech.com.my via Mailgun. Email requires configured credentials, enabled workflow delivery and a running notification scheduler.

    07 / Keep facility records and stock reliable

    Assets, inventory and vendors

    Assets and vendors

    Use the dedicated register to create and maintain each record. Keep asset identifiers, location and vendor details consistent. Apply the register filters and sort headings to find records. Field availability follows the project's configured trackers and custom fields.

    Issue materials to a work order

    Use the inventory stock-movement form, select an item and work-order reference, enter the quantity and reason, then save. Issuing stock deducts the balance with an audit record. Do not edit the balance field to bypass movements.

    Return unused materials

    Record a return against the relevant work order. A return increases stock and remains linked to the original work. Check the item, quantity and work order before saving to avoid overstating available stock.

    Stock receipts and low stock

    Opening stock is entered on creation; later deliveries use Receive stock with a reference. Low-stock highlighting compares balance with the reorder level. Posted movements cannot be edited. Ask the coordinator to reconcile a posting error using the ledger; this release has no general stock-adjustment screen.

    Who can do what

    Coordinators and authorised storekeepers manage stock. Staff see registers allowed by their role. Requesters do not get access to the asset, inventory or vendor database. Bulk CSV/PDF exports are limited to coordinators and managers.

    08 / Schedule repeating work and checklists

    Planned maintenance

    Create a plan

    Open Planned Maintenance and choose New plan. Enter a title, active asset, service category and priority. Choose a repeat interval in days, weeks, months or years, the first visit date and how many days in advance to create the work order.

    Attach the checklist

    Enter the checklist / instructions and optionally upload PDFs, documents or photos. Each plan accepts up to 10 files subject to the configured file-size limit. Existing plans also offer Add checklist files.

    Automatic work-order creation

    The scheduler creates one work order when the advance date is reached, pending technician assignment. The job follows the same start, completion and approval process as corrective work. A new job waits until the previous one is closed.

    Checklist copies and missed visits

    The generated job receives a copy of the plan's checklist files. Later plan changes apply to future jobs; existing jobs retain their copies. Missed historical periods are consolidated to avoid a backlog of duplicate jobs.

    Pause, filter and sort

    Pause a plan when servicing should stop, then Resume when ready. Filter by asset, activity, interval or due period. Sort by plan, asset, repeat interval, next visit or status. If a due plan never creates work, ask the administrator to check scheduler health and the plan error.

    09 / Use a filtered, shareable record

    Reporting and CSV transfer

    Register exports

    Coordinators and managers can export the filtered request, work-order, asset, inventory and vendor register as CSV or branded PDF. Exports include all matching records, not only the current page. The selected register sort is retained.

    Workload and completion

    Open Reports, choose the reporting period and inspect status, workload, materials and timing figures. Use the page's CSV or PDF export for a shareable report. The screen may show only the stated preview rows; exports cover the matching scope.

    Completion reports

    Open the work order's report for the completion / approval record, materials and recorded work timing. The PDF uses the OMNI and ADF logos. An approved snapshot reflects the submitted work at approval, rather than later unrelated register edits.

    Import assets, inventory and vendors

    An authorised coordinator with import permission opens the register's CSV import guide. Prepare UTF-8 CSV, choose the correct tracker and project in the native import wizard, map headers and test a small batch. Keep sample imports out of production until checked. Required fields and custom-field mappings follow the project configuration.

    Import safety

    Do not assume import is an automatic upsert or stock ledger. Check duplicates and unique identifiers before import. Use opening stock only for the initial migration, then stock movements. Protect spreadsheets containing personal or sensitive data; exported cells starting with formula characters are escaped.

    10 / A foundation for OMNI Workspace

    Project administration

    One account, several projects

    Use the project dropdown in the top bar to switch dashboards. Select Browse all projects for the project directory. An account may be a Project Admin in one facility and a technician or manager in another.

    ADF invites the first administrator

    ADF creates a private workspace, chooses its configuration template and optionally enters the first Project Admin email. The recipient accepts an expiring invitation and sets their own password. Existing active users sign in to accept. No password is emailed; opening the link alone grants nothing.

    Approve verified registrations

    Enable project registration under Project profile & team and share its link. Other users verify their email and complete registration. Review Pending access, select roles and approve or reject. Only new accounts created by this verified flow can be activated through project approval; ADF handles other inactive or locked accounts.

    Delegate and maintain the team

    ADF can enable appointment of additional Project Admins for a project. Select that role during invitation or team assignment. Your own membership needs another administrator, and the last active project administrator cannot be removed through Facilities controls. Team and access changes are audited.

    Edit roles within the project

    Four staff defaults are Project Admin, Coordinator, Tech / Engineer and Manager; Requester is basic access. Enable independent project role controls, edit operational capabilities or create a custom role such as Storekeeper. Restore defaults when needed. Existing shared roles remain unchanged until reassigned. ADF retains global and inherited grants; self-approval restrictions remain enforced.

    11 / Use the same account on each device

    Install and troubleshoot

    iPhone and iPad - Safari

    Open the site in Safari. Use Share, choose Add to Home Screen and keep Open as Web App on if shown. Tap Add. Open the app icon and sign in with your existing account.

    Android - Chrome

    Open the site in Chrome. Use More, then Install app, Install and create shortcut, or Add to home screen as offered by the browser. Confirm and open the installed icon.

    Desktop - Edge, Chrome or Safari

    On Windows or desktop Chrome / Edge, use the address-bar install icon or Install this site as an app. On a supported Mac Safari version, use File > Add to Dock. Installing gives a dedicated window and icon; it does not change your permissions.

    Connection and sign-in problems

    Live data and submissions require an internet connection. An installed app may use its own sign-in session. If a submit fails, reconnect and check whether the record was saved before sending again. Unsent forms are not saved offline.

    Support and release details

    Use Help & FAQ and quote the version shown in the sidebar. Include the project, record number, time and steps to reproduce; do not share passwords or signed approval links. OMNI AI is a placeholder panel in this release; the Qwen model is not connected. Device push notifications and offline submissions are not available.

    About OMNI Facilities

    By ADF Technology, built on Redmine. Redmine © 2006–2026 Jean-Philippe Lang, GNU GPL v2 or later. Upstream source notices and licences are retained.

    Open-source licences and credits · Return to OMNI Facilities