CyrusOne

DFW4 · Vendor Sign-In / Out
Prototype · sample data

What this shows: a vendor checks in on their own phone by scanning a QR code at the entrance. Their answers land directly in the Operations log with a unique Visit ID — so CyrusOne never re-types vendor data. Switch to CyrusOne Operations to review a submission, see what the vendor declared for safety, fill the internal-only fields, and sign the vendor in.

▣ Scanned at DFW4 entrance

Vendor Check-In

Tell us who you are and what you're here to do. CyrusOne will confirm on site.

Your details
Visit details
Equipment
Safety pre-check
This is what you expect your work to require. CyrusOne confirms and authorizes every item on site before work begins.

Check-in received

Show this Visit ID to CyrusOne Operations.


Status: Awaiting CyrusOne Sign-In

A CyrusOne engineer will verify your scope and walk you to the equipment.

Why this matters

  • No duplicate entry. Everything on this screen flows straight into the Operations log — staff stop re-typing the logbook.
  • Vendors use their own phone. Company or personal — just scan and submit at the entrance.
  • Safety stays with CyrusOne. Vendors declare hot work / LOTO / PPE; CyrusOne verifies and authorizes. The two are never confused.
  • The review process is unchanged. Every submission lands as Awaiting CyrusOne Sign-In — nothing is auto-approved.

Try it: fill a few fields, hit submit, then open CyrusOne Operations.

CyrusOne Operations — Vendor Log

0Awaiting sign-in
0On site
0Total today
Submissions (newest first)
Visit IDCompany / TechTypeStatusTime In
Record detail
Select a row to review the submission, fill internal fields, and sign the vendor in.
Interactive prototype for proposal use only. Sample data lives in the browser and resets on reload; no Microsoft 365 connection. Production build maps to Microsoft Forms → Power Automate → SharePoint List. Column names JLL Work Order #, JLL Employee Name, JLL Work Complete Verification are retained internally; all vendor-facing text reads CyrusOne.