Comfy Implementation & Requirements

Implementation Summary:

1. You share the following documentation.
2. Comfy transforms the documentation and information outlined below into custom floor maps rich with points of interest and information.
3. Comfy provides you with early access to review maps and provide feedback prior to going live for all users.

Stakeholders:

Facilities Team, Landlord, Mechanical Contractor (if needed)

Implementation Requirements:

1. Floor Plans

The floor plans you provide become the map users see in the app— it's important for these to be as accurate as possible, since users will use it to navigate, make requests, find points of interest, etc.

Components: Walls, doors, primary furnishings, desk names, room & area names
Format: DWGs with all XREFs included. Vectorized PDFs are also acceptable if DWGs are unavailable. Please provide BOTH if possible.
Typical Owner: Workplace Services Team, Architect
Quantity: 1 per floor

2. Room and Desk Names

Comfy configures the app using the room and desk names you provide. These names appear within the Comfy UI and on the map as users search and pick their location. Ideally room and desk names are shared in the same file as floor plans (see above). If floor plans and room and desk names don’t exist in the same file, it is OK to share separate documents for each.

Components: Room names and desk names
Format: DWGs with all XREFs included. Vectorized PDFs are also acceptable if DWGs are unavailable. Please provide BOTH if possible.
Typical Owner: Workplace Services Team, Architect, Landlord
Quantity: 1 per floor

Implementation Summary:

1. Provide your brand logo with the following characteristics:
   1. In both white and black or dark gray
   2. Little to no margins
   3. While maintaining aspect ratio, must have either a width of 270px or height of 110px.
2. Provide a photo of your building with the following characteristics:
   1. Image should be in “landscape” orientation if possible
   2. Image will be cropped to fit the mobile and desktop experiences, so for best experience the building should fit roughly the center third of the image vertically
   3. No smaller than 800x360px
   4. No more than 5MB in size
   5. Image must be .jpg

Stakeholders:

Marketing Team, Facilities Team

Implementation Requirements:

Once you provide the appropriate brand logo and building photo, we will display them on your home screen.

Implementation Summary:

1. You select the sign-on method best suited for your organization.
2. You provide a list of all domains (ex: “@comfyapp.com”) that users can use to access Comfy. (Domains can be specific to individual tenants).
3. Comfy, with support from your IT department as needed, will implement and test your selection.

Stakeholders:

IT Team, Security Team

Implementation Requirements:

Choose a Sign-On Method

To enable users to log in and control their space, Comfy offers flexible authentication and authorization of users. Generally speaking, users log into Comfy using one of four methods (for more details on each method, see our Security Deep Dive):

• Email domain-based Login
• Login via Google Accounts
• Password Authentication
• SAML 2.0 (This method will require your IT department to add Comfy as an application to your single sign-on service. Comfy will share detailed instructions if this method is selected)

Comfy utilizes a variety of system integration models ranging from cloud-to-cloud to the installation of a physical gateway box. The Comfy Gateway can be used to connect to on-prem systems like your BMS, calendar system, and occupancy data warehouse. Your Comfy Sales Engineer will work with you to determine what, if any, integrations require a Comfy Gateway. For more information about the Comfy Gateway and Security, see our Trust Center.

Implementation Summary:

1. You complete the Comfy networking questionnaire (see details below). Your answers will help Comfy understand your BACnet network configuration and provide the necessary information for Comfy to configure Gateways for your site.

2. Comfy configures the Gateways and ships them to you along with the necessary power and ethernet cords. You will receive two Gateways, both of which should be online at all times (the second Gateway serves as a backup).

3. You install the Comfy Gateways. Installation is simple: Connect the Gateways to power with the provided power adapter, and use the ethernet cables to connect the Gateways to the BMS and outbound-internet connection.

Stakeholders:

Facilities Team, Landlord, IT Team

Implementation Requirements:

Comfy Network Questionnaire

Complete the Comfy Network Questionnaire (your Comfy Sales Engineer will provide you a link). The questionnaire is often best completed by your BMS operator, IT department, or combination of both.

Implementation Summary:

1. You share the following documentation. Your documentation will help our engineers get to know your building inside-and-out, designing the best Comfy controls sequence to complement your existing programming.

2. Comfy will meet with the owner of your HVAC system and BMS (often a combination of your Facilities Team and controls vendor) to learn about your systems and agree on the optimal Comfy controls sequence.

3. Comfy integrates with devices through the Comfy Gateways (see Comfy Gateway section above) and deploys the agreed upon Comfy controls sequence.

4. Comfy uploads your mechanical zoning to our user interface, which enables users to initiate a response from the terminal unit serving their location.

5. Testing and quality assurance commences; Comfy runs a building health report and tests remotely. Once Comfy’s remote testing is complete, Comfy grants you access to test on-site.

6. Once testing is complete, the feature is ready to roll out to all employees.

Stakeholders:

Facilities Team, Landlord, Controls Contractor, Mechanical Contractor

Implementation Requirements:

★ Documentation Tip: Compare your mechanical and controls drawings with your floor maps and any BMS graphics showing mechanical zoning. If there are discrepancies, that is a sign the mechanical and controls drawings are out-of-date. Confirm you have the most up-to-date drawings before sharing with Comfy.

1. Remote BMS Read-Only Access

Providing Comfy remote read-only access reduces implementation time and improves quality by providing direct access to up-to-date information such as mechanical zoning, available BACnet points, and other settings.

2. BMS Points List

Comfy refers to BACnet points at each site to devise an appropriate Comfy controls sequence.

Components: List of available BACnet points for each controller/application type
Format: PDF or CSV, exported directly from BMS
Typical Owner: Chief Engineer, Controls Contractor
Quantity: 1 per building

3. BACnet Device IP or IP Address List

Comfy uses this list to discover devices through the Comfy Gateway. Device IP address (for BACnet/IP controllers) can be submitted in lieu of BACnet Device ID.

Components: BACnet Device ID (or IP address), Device Name (Metadata/BACnet/Name), Name of terminal unit (VAV, FPB, etc.) that the device is associate with if not clear in Device Name, Control Program
Format: PDF or CSV, exported directly from BMS
Typical Owner: Controls Contractor
Quantity: 1 per building

4. Mechanical Drawings

Comfy uses mechanical drawings to get to know your mechanical system and design the optimal Comfy controls sequence.

Components: Terminal units, terminal unit names, diffusers, ducting, and room schedules, unless these are available in the controls drawing instead
Format: PDF. If PDFs are unavailable, we accept DWGs
Typical Owner: Property Manager, Chief Engineer, Mechanical Engineer
Quantity: 1 drawing per floor. Multiple foors can be combined into a single docment

5. HVAC Zoning Map

If available, Comfy will reference zoning maps alongside the mechanical drawings when defining the area served by each terminal unit in the Comfy UI. Users will select a zone when making Comfy Temperature requests.

Components: A map of each floor with zoning and terminal unit names (same names that are used in your BMS)
Format: Often these maps can be pulled from HVAC construction packages (PDF form) or BMS graphics (PEG, PNG format). Clear screenshots are acceptable. If Comfy has remote BMS access, no need to provide screenshots as we can view the BMS zoning graphics ourselves
Typical Owner: Chief Engineer, Mechanical Engineer, Controls Contractor
Quantity: 1 per floor. Multiple floors can be combined into a single document

6. Controls Drawings

Comfy engineers refer to controls drawings to understand the programming of each controller type and terminal unit and characteristics of each, such as which have heating. This information is used to design the optimal Comfy controls sequence.

Components: Each should contain sequence of operations, points lists to control each type of equipment, controller types, and room schedules including details on which termal units have heating available
Format: PDF
Typical Owner: Controls Contractor
Quantity: 1 per building

Implementation Summary:

1. You provide the following requirements.
2. Comfy uploads and configures rooms in our UI accordingly.

Stakeholders:

Facilities Team, IT Team, Workplace Services Team

Implementation Requirements:

1. Calendar Integration

Your Comfy Solutions Architect will work with you to select the best deployment model for integrating Comfy with your calendar service. Comfy supports several integration models ranging from cloud-to-cloud to the installation of a local agent within the corporate network.

Microsoft Office 365

1. IT will need to provide the Office 365 Tenant ID for the instance which will be integrated with Comfy. Find instructions on how to locate the Tenant ID here.
2. Once provided, Comfy will respond with a URL which will grant Comfy the appropriate access to be able to interact with user and room calendars in Office 365.
3. IT will need to provide Comfy with the appropriate permissions to book meetings (application or impersonation).

Microsoft Exchange

1. Create a service account for Comfy and:
   1. Set up permissions on that service account to give the service account access to room calendars
   2. Securely share service account username and password with Comfy
2. Whitelist Comfy if Exchange server isn't available publicly
3. Share the following metadata:
   1. Server url, by default the url is of the form "https://<server>/EWS/Exchange.asmx"
   2. Windows domain

Google Calendar

1. Create a booking user for Comfy
   1. In the GSuite admin console, create a new GSuite user, e.g. "Booking User" <booking@domain.com>.
      1. This user only needs access to Calendars; all other services (email, drive, etc.) can be disabled by placing the user in an "Organization" that only has access to Calendars
      2. You can call it whatever you want, like "Chewbacca" <chewbacca@domain.com>, but know that this is the name associated with the booking of a room, e.g. "room booked by Chewbacca", so it's advised to have the name make sense.
2. Give the booking user permission to make changes and manage sharing for each individual resource calendar (e.g. "domain_12345@resource.calendar.google.com")
   1. Click the ▼ button on the resource in the list > Share this Calendar
   2. "Share with specific people", enter booking user and set "Make changes AND manage sharing" as the Permission Settings, hit Save.
   3. In the main Calendar view > Other calendars > "Add a coworker's calendar" text input (may also be called "Subscribe to Calendar"), start typing the name of the room resource.
   4. Click the resource in the popup search results to add it to the calendars list.
3. Securely send Comfy the username and password of the booking user.

2. Room Data

Comfy uses the following data to configure rooms within the Comfy UI-- whether your selected solution includes room booking (without sensors), room availability (with sensors), or both.

Components: 

Comfy will provide you a form requesting the following information for each room:

• Floor #
• Room Name (Name that will be displayed to end users in the Comfy UI). Must match room names on floor map/room and desk name documents- see Floor Maps section above.
• Room description (any information about the room you would like displayed in Comfy, such as details on available equipment). (optional)
• Capacity (optional)
• If implementing room booking:
  • Indication which rooms should be bookable in Comfy (either on your existing calendar system or Comfy's internal calendar)
  • Room email address
• Sensor ID (if integrating wiht occupancy sensors)

Format: Comfy-provided form
Typical Owner: Workplace Services Team
Quantity: 1 per building

3. Room Images

If desired, share room images for Comfy to display in the app. Images help users select the best room for their meeting.

Format:

• Photo image no larger than 5MB (in file size)
• Landscape orientation
• Image size no smaller than 800x360
• JPEG format

Typical Owner: Workplace Services
Quantity: Max 1 per room

Implementation Summary:

1. You share the following documentation. Your documentation will help our engineers get to know your building inside-and-out.

2. Comfy works with you to determine how to integrate with your existing connected Lighting Management System (via BACnet or API integration), and the best Comfy controls sequence.

3. Comfy deploys and tests the agreed upon Comfy controls sequence. Once Comfy’s remote testing is complete, Comfy grants you access to test on-site.

4. Once testing is complete, the feature is ready to roll out to all employees.

Stakeholders:

Facilities Team, Landlord, Lighting Contractor

Implementation Requirements:

Background: Most Lighting Management Systems command lighting at the zone level with each zone comprised of multiple lighting fixtures. For consistency, Comfy refers to these groups as “zones,” but they are also commonly referred to as “groups” or “areas” across various lighting system vendors. Usually Comfy will copy the existing zoning to define lighting zones in the Comfy UI. Lighting requests in the Comfy app control lighting at the zone-level (a zone is usually comprised of a group of lighting fixtures and covers a single room or a group of desks).

1. Lighting Zoning Map & Reflected Ceiling Plan

See below for necessary components. Occasionally these components are found across multiple documents (such as a separate lighting zoning map and reflected ceiling plan) or combined into a single document. Comfy uses these documents to understand how lighting fixtures are grouped for control.

Components:

• Must have: Lighting zone outlines, lighting zone names (names must match names used in the Lighting Management System)
• Nice to have: Fixtures, fixture names, occupancy sensor IDs and attributed zones

Format: PDF or DWG
Typical Owner: Property Manager, Chief Engineer, Lighting Contractor
Quantity: 1 per floor. Multiple floors can be combined into a single document

2. Lighting Controller Data List

Comfy uses this data to discover and integrate with all lighting zones.

Components (for each lighting zone):

• Must have: Zone ID (usually a number or name of the space the group serves), BACnet device ID (if lighting controllers are BACnet devices), list of fixture IDs in the zone
• Nice to have: Control sequence associated with each zone (Scene, Dimming, or on/off)

Format: Spreadsheet
Typical Owner: Property Manager, Chief Engineer, Lighting Contractor
Quantity: 1 per floor. Multiple floors can be combined into a single document

3. Lighting Controls Drawings

Comfy refers to lighting controls drawings to understand the programming of each controller type and device. This information is used to design an appropriate Comfy controls sequence.

Components: Each drawing should contain sequence of operations, points lists, controller types, room schedules, available commands for each lighting zone (e.g. scene control, dimmable, or on/off), and method to release command
Format: PDF
Typical Owner: Property Manager, Chief Engineer, Lighting Contractor
Quantity: 1 per building

Implementation Summary:

1. You provide the following requirements.

2. Comfy uploads and configures desks in our UI accordingly.

Stakeholders:

Facilities Team, IT Team, Workplace Services Team

Implementation Requirements:

Desk Data

Comfy uses the following data to configure desks within the Comfy UI-- whether your selected solution includes desk booking (without sensors), desk availability (with sensors), or both.

Components: 

Comfy will provide you a form requesting the following information for each desk:

• Floor #
• Desk Name (Name that will be displayed to end users in the Comfy UI). Must match desk names on floor map/room and desk name documents- see Floor Maps section above.
• Desk description (any information about the room you would like displayed in Comfy, such as details on available equipment) (optional)
• If implementing desk booking:
  • Indication which desks should be bookable in Comfy
  • Desk booking hours (hours during which desk booking is available)
• Sensor ID (if integrating wiht occupancy sensors)

Format: Comfy-provided form
Typical Owner: Workplace Services Team
Quantity: 1 per building

Implementation Summary:

1. If you need help specifying or selecting sensors, Comfy can advise you during our Solution Design process, including vendor, power supply type (POE, battery), and sensor capabilities (occupancy, people count, motion).

2. Your Comfy Solutions Architect will work with you to determine the best method for Comfy to receive sensor data (over BACnet interface or API).

   1. If your sensor vendor works with BACnet and is accessible via the BACnet network, Comfy can integrate using the Comfy Gateway.

   2. If your sensor vendor is a Works With Comfy partner, we'll work with them directly to integrate with our API. We identify and work with the right counterparts, and keep you informed on the latest product offerings.

3. Comfy maps sensor data to spaces in the Comfy UI- both the app and Comfy Insights.

Stakeholders:

Facilities Team, IT Team, Sensor Vendor

Implementation Requirements:

Your Comfy Solutions Architect will share specific requirements based on your sensor vendor.

Implementation Summary:

1. You provide the following requirements.

2. Comfy adds the amenities to the floor maps and configures them accordingly.

Stakeholders:

Workplace Services Team, Facilities Team

Implementation Requirements:

1. Comfy Amenities Form

Comfy will provide you with a form requesting the following information for each amenity:

• Floor #
• Name
• Description
• Hours
• Link URL
• Link Button Text

Format: Comfy-provided form
Typical Owner: Workplace Services Team, Facilities Team
Quantity: 1 per building.

2. Map of Amenities Locations

Comfy will use this map to display amenity locations on the Comfy floor maps.

Components: Floor plan with amenities locations highlighted.
Format: DWG or PDF
Typical Owner: Workplace Services Team, Architect
Quantity: 1 per floor. Multiple floors can be combined into a single document.

3. Amenity Images

If desired, share amenity images for Comfy to display in the app. Images help users gain awareness of available amenities.

Format:

• Photo image no larger than 5MB (in file size)
• Landscape orientation
• Image size no smaller than 800x360
• JPEG format

Typical Owner: Workplace Services Team
Quantity: Max 1 per amenity

Implementation Summary:

1. You provide the following requirements.

2. Comfy adds the cards to the Comfy user Home Page and configures them accordingly.

Stakeholders:

Workplace Services Team, Facilities Team

Implementation Requirements:

1. Comfy Cards Form

Comfy will provide you with a form requesting the following information for each card:

• Headline/Title
• Body/Description
• Call to action (Link button text)
• Link URL
• Image

Format: Comfy-provided form
Typical Owner: Workplace Services Team, Facilities Team
Quantity: 5 per building; can be targeted to multiple buildings across campus if desired.

Implementation Summary:

1. You provide the following requirements.

2. Comfy configures Work Requests accordingly.

Stakeholders:

Facilities Team, IT Team

Implementation Requirements:

Comfy Work Requests Form

Comfy will provide you with a form requesting the following information:

• Work Request categories
• Email Tags (these tags are included in the work request email and can be used to facilitate automatic routing of tickets to the appropriate team)
• Email address of recipient(s)

Format: Comfy-provided form
Typical Owner: Facilities Team, IT Team
Quantity: 1 per building.

Implementation Summary:

1. You provide the following requirements.

2. Comfy shares credentials securely.

3. From the kiosk, go to https://my.comfyapp.com and log in using the credentials provided by Comfy. Each kiosk will have its own set of credentials.

4. Navigate through the onboarding slides and choose a building/floor/location and set your location to the area where the kiosk is located (that is where the "You Are Here" star will go).

5. Manually change the URL in the browser to (https://my.comfyapp.com/kiosk/) and refresh.

6. If required for better visibility, set the default zoom level between 0 to 3 in the URL (eg. https://my.comfyapp.com/kiosk/?zoom=1). Lower numbers are more zoomed out, higher numbers are more zoomed in. This is for the default zoom level, which the map will revert to after 30 seconds of no activity.

Our standard login session length is 180 days, after which you'll need to login again using the same steps above.

Stakeholders:

Facilities Team, IT Team

Implementation Requirements:

1. Kiosk Hardware

You are responsible for providing and maintaining kiosk hardware. Comfy supports a max. of 55" screen size and recommends touch screens so users can interact with the map (zoom in and out, click for more information, etc.)