WO2024039523A1 - System and method of a group scheduler for managing attendance recommendations - Google Patents

System and method of a group scheduler for managing attendance recommendations Download PDF

Info

Publication number
WO2024039523A1
WO2024039523A1 PCT/US2023/029159 US2023029159W WO2024039523A1 WO 2024039523 A1 WO2024039523 A1 WO 2024039523A1 US 2023029159 W US2023029159 W US 2023029159W WO 2024039523 A1 WO2024039523 A1 WO 2024039523A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
preference
members
recommendation
remote
Prior art date
Application number
PCT/US2023/029159
Other languages
French (fr)
Inventor
Patrice BOULET
Sijia He
Original Assignee
Building Robotics, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Building Robotics, Inc. filed Critical Building Robotics, Inc.
Publication of WO2024039523A1 publication Critical patent/WO2024039523A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting

Definitions

  • This application relates to the field of workplace scheduling systems and, more particularly, to systems and methods for managing attendance of workplace occupants for one or more facilities.
  • an attendance management approach for facilitating in-person communications among personal and/or professional groups.
  • the approach facilitates positive and productive interaction among people, such as coworkers, by helping them to coordinate in-person contact.
  • the approach assists users to coordinate hybrid schedule preferences with schedules and preferences of other group members.
  • the approach also guides group members toward the best time periods to attend a certain facility, such as a workplace, when other members of the group also plan to be present at the facility. For example, a group member may have a need to be co-located with one or more other group members with whom he or she works most closely.
  • One aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor.
  • the memory component collects attendance schedules of group members, in which the group members include a first member, a second member, and a third member.
  • the processor generates a first group preference of the first member in response to collecting the attendance schedules.
  • the processor indexes the first group preference of the first member based on a second group preference of the second member.
  • the processor updates the first group preference of the first member to include the third member.
  • the first group preference includes one or more members of the group members followed by the first member, in which the first group preference includes the second member.
  • the second group preference includes one or more members of the group members followed by the second member, in which the second group preference includes the third member.
  • Another aspect is a method of a group scheduler for managing attendance recommendations.
  • Attendance schedules of group members are collected, in which the group members include a first member, a second member, and a third member.
  • a first group preference of the first member is generated in response to collecting the attendance schedules.
  • the first group preference includes one or more members of the group members followed by the first member, in which the first group preference includes the second member.
  • the first group preference of the first member is indexed based on a second group preference of the second member.
  • the second group preference includes one or more members of the group members followed by the second member, in which the second group preference includes the third member.
  • the first group preference of the first member is updated to include the third member.
  • Yet another aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor.
  • the memory component collects attendance schedules of group members, in which the group members include a first member and a second member.
  • the processor generates a group preference of the first member in response to collecting the attendance schedules.
  • the processor indexes the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member.
  • the processor updates the attendance schedule of the first member for the future time period by changing the first location status of the first member to correspond to the second location status of the second member.
  • the group preference includes one or more members of the group members followed by the first member, in which the group preference includes the second member.
  • the first location status is one of either a work location status or a nonwork location status
  • the second location status is the other of either the work location status or the non-work location status.
  • Still another aspect is a method of a group scheduler for managing attendance recommendations.
  • Attendance schedules of group members are collected, in which the group members include a first member and a second member.
  • a group preference of the first member is generated in response to collecting the attendance schedules.
  • the group preference includes one or more members of the group members followed by the first member, in which the group preference includes the second member.
  • the group preference of the first member is indexed based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member.
  • the first location status is one of either a work location status or a non-work location status
  • the second location status is the other of either the work location status or the non-work location status.
  • a further aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor.
  • the memory component collects multiple attendance schedules of multiple group members.
  • the group members include a first member and a second member. The second member is being followed by the first member.
  • the processor generates a weighted preference of the group members in response to collecting the attendance schedules.
  • the processor determines a schedule for a second time period based on the weighted preference of the group members.
  • the weighted preference is generated based on a first time period of work in office of the first and second members.
  • the second time period is greater than the first time period.
  • Another further aspect is a method of a group scheduler for managing attendance recommendations.
  • Multiple attendance schedules of multiple group members are collected.
  • the group members include a first member and a second member.
  • the second member is being followed by the first member.
  • a weighted preference of the group members is generated in response to collecting the attendance schedules.
  • the weighted preference is generated based on a first time period of work in office of the first and second members.
  • a schedule for a second time period is determined based on the weighted preference of the group members. The second time period is greater than the first time period.
  • Yet another aspect is a system of a group scheduler for managing attendance recommendations comprising an input component, a processor, and an output component.
  • the input component collects participant preferences, location preferences, and time preferences of group members at a management device from remote devices.
  • the group members are associated with a particular group entity, and each remote device is associated with one or more members of the group members.
  • the processor determines event participants based on the participant preferences, determines one or more event locations based on the location preferences, and determines one or more event times based on the time preferences.
  • the time preferences including calendar information for the event participants.
  • the output component provides a recommendation identifying the event participants, the event location(s), and the event time(s) to an acceptance device.
  • the acceptance device is associated with a particular member of the group members.
  • Still another aspect is a method of a group scheduler for managing attendance recommendations.
  • Participant preferences, location preferences, and time preferences of group members are collected at an input component from remote devices.
  • the group members are associated with a particular group entity.
  • Each remote device is associated with one or more members of the group members.
  • Event participants are determined at a processor based on the participant preferences.
  • One or more event locations are determined at the processor based on the location preferences.
  • One or more event times are determined at the processor based on the time preferences.
  • the time preferences include calendar information for the event participants.
  • a recommendation identifying the event participants, the event location(s), and the event time(s) are provided by an output component to an acceptance device.
  • the acceptance device is associated with a particular member of the group members.
  • Another aspect is a system of a group scheduler for managing attendance recommendations comprising an input component, a processor, and an output component.
  • the input component collects interest preference data of group members from remote devices.
  • the group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members.
  • the processor determines a meetup recommendation for member match based on the interest preference data of the group members. In determining the meetup recommendation, the processor generates a conversation starter based on the interest preference data.
  • the output component provides the meetup recommendation, including the conversation starter, to an acceptance device.
  • the acceptance device is associated with a particular member of the group members.
  • Another aspect is a method of a group scheduler for managing attendance recommendations.
  • Interest preference data of group members are collected at an input component from remote devices.
  • the group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members.
  • a meetup recommendation is determined at a processor for member match based on the interest preference data of the group members.
  • a conversation starter is generated based on the interest preference data.
  • the meetup recommendation including the conversation starter is provided by an output component to an acceptance device.
  • the acceptance device is associated with a particular member of the group members.
  • FIG. 1 is an illustration of a system of a group scheduler for managing attendance recommendations, in an example implementation, that is operable to employ techniques described herein.
  • FIG. 2 is a block diagram of various components of a management device, in an example implementation, of FIG. 1.
  • FIG. 3 is a flow diagram, in an example implementation, of an operation of the management device of FIGs. 1 and 2.
  • FIG. 4 is a flow diagram, in an example implementation, of another operation of the management device of FIGs. 1 and 2.
  • FIG. 5, including 5A and 5B, represents a first graphical view of a user interface of a remote device of FIG. 1, in an example implementation, that is operable to employ techniques described herein.
  • FIG. 6 represents a second graphical view of a user interface of a remote device of FIG. 1, in an example implementation, that is operable to employ techniques described herein.
  • FIGs. 7A through 7C illustrate a third graphical view of a user interface of a remote device of FIG. 1 representing, by example, followed coworker preferences.
  • FIGs. 8A through 8D illustrate a fourth graphical view of a user interface of the remote device of FIG. 1 representing, by example, space preferences.
  • FIGs. 9A through 9C illustrate fifth and sixth graphical views of a user interface of a remote device of FIG. 1 representing, by example, workday status preferences and weekly schedule recommendations.
  • FIG. 10 is an operational diagram representing an operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
  • FIG. 11 is a block diagram of various components of a management device, in another example implementation, of FIG. 1.
  • FIG. 12 is a flow diagram representing another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
  • FIG. 13 is a block diagram of various components of the management device, in still another example implementation, of FIG. 1.
  • FIG. 14 is a flow diagram representing yet another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
  • FIG. 15 illustrates a seventh graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information and feedback information.
  • FIG. 16 is a block diagram of various components of the management device, in yet another example implementation, of FIG. 1.
  • FIG. 17 illustrates an eighth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information and entry of user preference information.
  • FIG. 18 illustrates a ninth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information including secret tips and conversation starters.
  • FIG. 19 illustrates a tenth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information including interest preferences and conversation starters.
  • FIG. 20 is a flow diagram representing still another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
  • the attendance management system 100 includes a management device 140 located on-site at a facility 110 and/or remote from one or more facilities 120, 130.
  • the system 100 also includes devices 150, 160, 170 located remote from the management device 140, i.e., remote devices, positioned at more than one facility or remote location, such as facilities 120, 130.
  • the remote devices 150, 160, 170 may communicate with the management device and/or each other via a network connection 180.
  • facilities include, but are not limited to, a work location such as an office 120 or management location 110, or a non-work location such as home location 130 or remote location.
  • Examples of remote devices 150, 160, 170 include, but are not limited to, a workstation, a laptop, a tablet, or a mobile device.
  • Examples of the network connection 180 include, but are not limited to, a Cloud network or the Internet.
  • FIG. 1 is provided for illustrative purposes only to represent examples of the management device 140 and the remote devices 150, 160, 170, and is not intended to be a complete diagram of the various components that may be utilized by the system 100.
  • the management device 140 may include various other devices not shown in FIG. 1, such as presence or location sensors).
  • the management device 140 may include a combination of two or more devices, such as the management device 140 being co-located with one or more remote devices 150, 160, 170.
  • the management device 140 may include a division of a particular device into two or more separate devices (such as the management device 140 or its operation being distributed among more than one location or facility 110, 120, 130).
  • FIG. 2 represents example device components 200 of the management device 140.
  • the device components 200 comprise a communication bus 202 for interconnecting other device components directly or indirectly.
  • the other device components include one or more communication components 204 communicating with other entities via a wired or wireless network, one or more processors 206, and one or more memory components 208.
  • the communication component 204 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation.
  • the communication component 204 may utilize wired or wireless technology for communication.
  • the processor or processors 206 may execute code and process data received from other components of the device components 200, such as information received at the communication component 204 or stored at the memory component 208.
  • Each application includes executable code to provide specific functionality for the processor 206 and/or remaining components of the management device 140. Examples of applications executable by the processor 206 include, but are not limited to, an index & recommendation module 210 and an update module 212.
  • the index & recommendation module 210 processes the group preferences generated from the collected attendance schedules. For some embodiments, a group preference of one group member may be indexed based on a group preference of another, different group member.
  • a group preference may be indexed based on a difference between a first location status of one group member and a second location status of another, different group member for a future time period of an attendance schedule.
  • the index & recommendation module 210 also includes a recommendation engine of the group scheduler that generates a recommendation in response to indexing the group preference.
  • the update module 212 processes group preferences and/or attendance schedules.
  • a group preference may be updated to include or remove a group member.
  • an attendance schedule may be update for a future time period by changing a first location status of one group member to correspond to a second location status of another, different group member.
  • Data stored at the memory component 208 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140.
  • Examples of data associated with the management device 140 and stored by the memory component 208 may include, but are not limited to, schedule and status data 214 and group preference data 216.
  • the schedule and status data 214 may include attendance schedules of group members (such as a first member, a second member, etc.) and/or location statuses. Examples of location statuses include, but are not limited to, a work location status associated with a work location 110, 120; a non-work location status associated with a non-work location 130, and the like.
  • the group preference data 216 generates a group preference of a group member in response to collecting attendance schedules. Each group preference corresponds to a particular group member of a group, and the group preference includes one or more other members of the group followed by the particular group member.
  • the device components 200 may include one or more input components 218 and one or more output components 220.
  • the input components 218 and output components 220 of the device components 200 may include one or more visual, audio, mechanical, and/or other components.
  • the input and output components 218, 220 may include a user interface 222 for interaction with a user of the device.
  • the user interface 222 may include a combination of hardware and software to provide a user with a desired user experience.
  • FIG. 2 is provided for illustrative purposes only to represent examples of the management device 140 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device 140 may include various other components not shown in FIG. 2, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
  • FIG. 3 there is shown a flow diagram, in an example implementation, of an operation 300 of the management device.
  • the system 100 and the operation 300 assists the first member to find relevant group members to obtain updates for their hybrid schedule activity.
  • the relationship of group members who follow each other’s hybrid schedule activity may be indexed so that the first member may receive recommendations to follow some or all other group members.
  • a recommended group member may be, for example, a coworker who is followed by a coworker that the first member already follows, or a coworker who follows the first member.
  • the operation 300 represents a method of a group scheduler for managing attendance recommendations.
  • the attendance schedules of the group members are collected (302) from the system, such as the management device 140 and/or the remote devices 150, 160, 170.
  • the group members include a first member, a second member, and a third member.
  • the first member may explore in-office schedules of other group members to decide when to go to an office or facility.
  • the operation 300 generates (304-306) a first group preference of the first member.
  • the first group preference includes one or more members of the group members being followed by the first member.
  • the first group preference includes the second member but does necessarily require the inclusion of the first member.
  • the group members are provided (304) to a remote device associated with the first member and a user selection is received (306) from the remote device in response to the group members.
  • the system 100 may guide the first member to select other group members whom the first member may desire to follow in order to receive updates on the in-office schedule activity of one or more other group members.
  • the second member is added to the first group preference of the first member.
  • the operation 300 indexes (308) the first group preference of the first member based on a second group preference of the second member.
  • the second group preference includes one or more members of the group members followed by the second member, and the second group preference includes the third member. Accordingly, in order to index (308) the first group preference, the second group preference of the second member is generated (310) some time before indexing the first group preference of the first member.
  • the group preference may be updated automatically by the management device 140 or in response to interaction with a remote device 150, 160, 170.
  • a recommendation engine of the index & recommendation module 210 in response to indexing (308) the first group preference, a recommendation engine of the index & recommendation module 210 generates (312) a recommendation to adjust to the first group preference of the first member and the recommendation is provided (314) to one or more remote devices associated with the first member.
  • the system 100 provides recommendations on which group members might be relevant to add to the group preference followed by the first member as well as any previous response to historical recommendations. For example, a recommendation may indicate, "You might be interested to follow [member X] because [member Y] you follow also follows him/her. Do you want to follow his/her schedule?".
  • the remote device may be operated by a user to adjust the first group preference of the first member.
  • the operation 300 may receive (316) an acceptance of the recommendation from the remote device in response to providing (314) the recommendation. If an acceptance is received (316), then the first group preference of the first member is updated (318) to include the third member. Otherwise, the first group preference is not updated to include the third member.
  • the recommendation engine of the index & recommendation module 210 in response to indexing (308) the first group preference, the recommendation engine of the index & recommendation module 210 generates (312) a recommendation to adjust to the first group preference of the first member and the first group preference is updated (318) automatically by the management device 140.
  • the operation 300 continues with processing group preferences. For some embodiments, the operation 300 returns to indexing (308) the first group preference. For some embodiments, the operation 300 returns to generating (312) a recommendation by the recommendation engine. For some embodiments, the recommendation engine is updated (320) in response to receiving (316) a response to the recommendation from the remote device or updating (318) the first group preference. In this manner, the system 100 may determine whether a network recommendation for a group member was useful or not to improve future recommendations.
  • FIG. 4 there is shown a flow diagram, in an example implementation, of another operation 400 of the management device.
  • the system 100 and operation 400 may assist group members, such as employees or coworkers, to find the best days to go into the office based on which other group members are relevant to them.
  • a second coworkers may be relevant to a first coworker if the first coworker follows the second coworker in the first coworker's group preference.
  • the operation 400 may index the status (such as work in office, work remotely, or undecided) of each group member in the group scheduler of the system 100 for each time period (such as a workday) and the relationship of group members who follow each other's activity, recommending a change in their schedule when relevant.
  • a recommended day in office may be a workday in the future when the group member has not set his or her location status to be working in office, i.e., schedule to work remotely. Further, a recommended day in office may be a workday in the future when there are many people followed by the first member who have set their collective status to be working in office that workday.
  • the operation 400 represents another method of a group scheduler for managing attendance recommendations.
  • the attendance schedules of the group members are collected (402) from the system, such as the management device 140 and/or the remote devices 150, 160, 170.
  • the group members include a first member and a second member.
  • the first member may explore in-office schedules of individual coworkers to decide when to go to the office via the system 100.
  • the operation 400 generates (404-406) a group preference of the first member.
  • the group preference includes one or more members of the group members being followed by the first member.
  • the group preference includes the second member but does necessarily require the inclusion of the first member.
  • the group members are provided (404) to a remote device associated with the first member and a user selection is received (406) from the remote device in response to the group members.
  • a user selection is received (406) from the remote device in response to the group members.
  • the second member is added to the group preference of the first member.
  • the system 100 may guide the first member to select coworkers he or she would like to follow in order to get updates on their in-office schedule changes.
  • the operation 400 indexes (408) the group preference of the first member so that the system 100 may provide recommendations to, for example, adjust in-office work schedules for the first member.
  • the operation 400 may index (408) the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member.
  • the first location status is either one of a work location status or a nonwork location status
  • the second location status is the other one of either the work location status or the non-work location status.
  • the time period may be a particular day or some other period of time, such as an hour, a workday (as determined by employment), days excluding holidays/vacation days/sick days, a week, a weekday, a weekend, and the like.
  • the operation 400 may identify a day when the location status of the first member is a non-work location status (e.g., working from home) whereas the location status of the second member is a work location status (e.g., working at the office).
  • the operation 400 may also consider time periods that are not in the future, but the operation must consider at least future time periods for indexing (408) the group preference.
  • the attendance schedule may be updated automatically by the management device 140 or in response to interaction with a remote device 150, 160, 170.
  • the system 100 may provide a recommendation to the first member to change his or her location status to a work location status or non-work location status during a particular time period.
  • a recommendation engine of the index & recommendation module 210 in response to indexing (408) the group preference, generates (412) a recommendation to adjust to the attendance schedule of the first member and the recommendation is provided (414) to one or more remote devices associated with the first member.
  • the system 100 prompt the first member to change his or her schedule so the remote device may be operated by a device user to adjust the attendance schedule of the first member.
  • the operation 400 may receive (416) an acceptance of the recommendation from the remote device in response to providing (414) the recommendation. If an acceptance is received (416), then the attendance schedule of the first member is updated (418) for the future time period by changing the first location status of the first member to correspond to the second location status of the second member. Accordingly, the first and second members will be scheduled to be at the same location during the future time period. Otherwise, the attendance schedule is not updated for the future time period.
  • the recommendation engine of the index & recommendation module 210 in response to indexing (408) the group preference, the recommendation engine of the index & recommendation module 210 generates (412) a recommendation to adjust to the attendance schedule of the first member and the attendance schedule is updated (418) automatically by the management device 140.
  • the operation 400 continues with processing group preferences. For some embodiments, the operation 400 returns to indexing (408) the group preference. For some embodiments, the operation 400 returns to generating (412) a recommendation by the recommendation engine. For some embodiments, the recommendation engine is updated (420) in response to receiving (416) a response to the recommendation from the remote device or updating (418) the attendance schedule. In this manner, the system 100 may index the acceptance as feedback to improve the recommendation model of the recommendation engine.
  • the operation 400 may provide (422) a notification to a remote device associated with the first member.
  • the notification may indicate that the second location status of the second member is different from the first location status of the first member for the future time period.
  • the notification may be provided (422) in response to generating (412) the recommendation.
  • the first member may receive the notification or see a recommended insight at an output component (such as a web interface of a display) about other group members he or she follows. For example, the first member may receive a notification about other members going into a local office on a day when the first member is planning to work from home.
  • the first graphical view 500 includes a header 502, a time period range 504, and multiple time periods 506, 508, 510, 512, 514 (506-514).
  • the header 502 includes information associated with the group, such as a group identification and/or a group member identification.
  • the time period range includes information associated with the time period associated with the attendance management of the group scheduling system, such as a date range or date navigation.
  • the time periods 506-514 include information associated with each corresponding time period such as a date 516, a date status 518, a member attendance status 520 of the first member, and/or a group attendance status 522 of the group members.
  • the first graphical view 500 may further include a menu 524 to select among different features of the user interface, such as a status window and a profile window.
  • Each time period 506-514 provides insight to the attendance management of the group scheduler for the corresponding time period.
  • the date 516 provides a date identification for the particular time period.
  • the date status 518 provides status information associated with the particular time period.
  • a time period 506 may be in a disabled state when, for example, a day of the current week has passed. In the disabled state, the time period 506 may indicates the status as "passed”.
  • a time period 508 may indicates a current time period, such as a status of "today”, and/or other time periods 510-514 may indicate future time periods by providing a null or no date status indication.
  • the member attendance status 520 of the first member may be indicated by two or more location status, such as a work location status or a nonwork location status.
  • the member attendance status 520 may provide for a work status, a home status, and an undecided status.
  • the undecided status may be set by default.
  • the member attendance status 520 may be set or changed by a user selection of the user interface.
  • the member attendance status 520 may be set or changed automatically or semi-automatically by one or more sensors or databases of the device or system, such as a proximity sensor, a location sensor, a calendar application, or a communication application (such as monitoring emails, texts, calls, or online posts).
  • the group attendance status 522 of the group members may indicate a collective indicator or indicators of the status of the group members.
  • the group attendance status 522 may indicate a most common location status of the group members and/or the number of group members having the most common location status.
  • the first graphical view 500 may be explained.
  • "calendar weekday” may be in the current work week in which no weekend days are provided. If a user opens the app during a weekend, then the first graphical view may show the upcoming work week with the back button disabled 526. The user may use a caret button to navigate to future weeks and the disabled caret button for weeks in the past. If the user opens the app during the weekdays and navigates to future weeks, then a user selection on a calendar button 528 will take the user back to the current work week, in which "today" is within this particular week. If the user opens the app during the weekend and navigates to future weeks, then a user selection on the calendar button 528 will take user back to the upcoming work week.
  • the first graphical view 500 provides a scrollable screen 530, as represented by the middle section of FIG. 5.
  • calendar weekdays become part of the persistent header 532 on the top area.
  • the header separator 534 may also be provided by the scrollable screen 530.
  • the first graphical view 500 further provides a name list 536-548 that is accessible by selecting a particular time period 506-514.
  • Each name identification of the name list 536-548 may include a corresponding location status indicator 550, graphical and/or textual, providing the location status corresponding to the name identification.
  • the first graphical view 500 may include a name list header 552 when displaying the name list 536-548 that includes group information, such as a number of members of a most common location status 554 and a number of members of a location status other than the most common location status 556, 558.
  • the number of members of a location status other than the most common location status may include members working remotely 556 and/or member undecided 558.
  • any part of an area associated with the selected time period 506-514 may bring up the name list except for selection of the member attendance status 520.
  • the name list may include all group members.
  • the name list may be ordered and organized into subgroups based on the location status of the group members.
  • a first subgroup of members 536-542 may include members having a work location status
  • a second subgroup of members 544- 548 may include members having a non-work location status.
  • a first subgroup of members 536-542 may include members having a work location status
  • a second subgroup of members 544 may include members having a remote location status
  • third subgroup of member may include members who are undecided 546, 548.
  • the name list 536-548 may be provided in alphabetical order for the entire group or for each individual subgroup.
  • the name list 536-548 may include a sticky area 560 that allows a user to update a first member location status while viewing or scrolling through the name list.
  • FIG. 6 there is shown a second graphical view 600 of a user interface of another remote device of FIG. 1, in an example implementation, which is operable to employ techniques described herein.
  • the second graphical view 600 provides more information on less screens for remote devices having larger display areas.
  • the second graphical view 600 includes both a member status portion 670 for multiple time periods and a group status portion 680 for a particular time period on a single screen or view.
  • This second graphical view 600 may display a full list of group member location statuses based on selected and/or highlighted information in the middle portion of the screen. For some embodiments, when a user lands on this webpage or screen, the information for the current day may be selected and/or highlighted by default.
  • the second graphical view 600 includes a header 602, a time period range 604, and multiple time periods 606-614.
  • the various parts of the second graphical view 600 of FIG. 6 provides information and features similar to the corresponding parts of the first graphical view 500 of FIG. 5.
  • the time periods 606-614 include information associated with each corresponding time period such as a date 616, a date status 618, a member attendance status 620 of the first member, a group attendance status 622 of the group members, and/or a menu 624.
  • the second graphical view 600 further provides a name list 636-648 that is accessible by selecting a particular time period 606-614. Again, the various name list parts of the second graphical view 600 of FIG. 6 provides information and features similar to the corresponding name list parts of the first graphical view 500 of FIG. 5.
  • FIGs. 7A through 7C there are shown a third graphical view 700 of a user interface of a remote or management device 140, 150, 160, 170, in an example implementation.
  • the third graphical view 700 manages followed member preferences, similar to the first graphical view 500 of FIG. 5.
  • each screen 702, 704, 706 of the third graphical view 700 includes a header 708, a menu 710, and a set of content.
  • the third graphic view 700 includes followed member selections 712 for followed member preferences, such as followed member lists and followed member filters.
  • the third graphical view 700 includes a first screen 702 to identify followed members 714 and non-followed members 716.
  • a remote or management device 140, 150, 160, 170 may select a follow chip 718 associated with a member’s identification to follow non-followed members 716 to add the member to a list of followed members 714.
  • the remote or management device may deselect a following chip 720 associated with a member’s identification to remove the member from the list of followed members 714.
  • the remote or management device may filter schedules and receive recommendations when hybrid schedules of those selected members are updated.
  • the third graphical view 700 includes one or more other screens 704, 706 to filter followed member data.
  • the followed members 714 may be referenced to filter their hybrid schedules.
  • the device may filter member insights 722 of the hybrid schedules for a first time period (such as a week) at a second screen 704 subsequent to selecting one or more follow chips 718.
  • a third screen 706 associated with a second time period, shorter than the first time period (such as a day) may show a list 724 of members that the remote or management device follows, filtered to identify those members having their workday status for that day set to work in the office.
  • the remote or management device may identify which second time periods are the most popular at the office for the first time period by filtering the insights 722 and the list 724 for the members of interest.
  • the list of members 724 may be filtered to only display the members that the remote or management device has followed by selecting the followed members chip of the followed member selection 712. In response, the list 724 may be filtered to only display the status of the members followed by the remote or management device 150, 160, 170.
  • the remote or management device may determine whether a particular member of interest may be located at the office for a particular second time period of the first time period. Further, the list of members 724 that the followed by the remote or management device may be used as input to provide weekly schedule recommendations.
  • FIGs. 8A through 8D there are shown a fourth graphical view 800 of a user interface of the remote or management device 140, 150, 160, 170 representing, by example, space preferences.
  • each screen 802, 804, 806, 808 of the fourth graphical view 800 includes a header 810, a menu 812, and a set of content.
  • the fourth graphical view 800 include followed member selections 814 for followed member preferences, such as followed member lists, followed member filters, and followed member filters with space information.
  • the fourth graphical view 800 includes a fourth screen 802 to identify followed members 816 and non-followed members 818.
  • the fourth screen 802 further includes space preferences 820, 822, 824 for the followed member selections 814, followed members 816, and non-followed members 818.
  • the followed member selections 814 may allow for a selection 820 of a listing of member information for a particular location or space, such as an Oakland office.
  • each member of the followed members 816 may indicate a followed member location 822
  • each member of the non-followed members 818 may indicate a non-followed member location 824.
  • the remote or management device associates a location or space with a corresponding workday status.
  • the hybrid schedules coordinated with the spaces where members will be working and create in- person connections.
  • Each remote or management device may associate a space to a work in office status indicate its space preference, such as a company location.
  • Each remote or management device may associate a space to a non-work in office status, such as a working remotely status, to notify members about working outside the company offices, such as a cafe close to the office or a coworking space.
  • the remote or management device or system 100 may select a default space, which will be automatically applied to their work in office or working remotely statuses by defaults.
  • the remote or management device or system 100 may specify a default space preference.
  • the default space preference may be assigned automatically to a corresponding workday status in response to a remote or management device setting a work status.
  • the remote or management device may filter the hybrid schedules of their members by spaces in order to identify the members locations or spaces on any given day, and which days are popular for a given first time period at a space.
  • the system 100 and/or remote or management device may associate spaces to a workday status.
  • the remote or management device may select one of multiple status options of the member insights 826, for a particular second time period. Examples of status options include, but are not limited to, work in office 828, not work in office (i.e., working remotely) 830, or undecided 832.
  • the remote or management device or system 100 may select a particular location or space 834 associated with the work status.
  • the member insights 836 may be updated to indicate the selected space 838 in response to selection of the particular space.
  • the device may be prompted to select from the list of available spaces for the company to choose a location or space.
  • the list of spaces available for the work in office and working remotely statuses are separate and collectively managed by all members of a group account.
  • Default space preferences may be utilized for repetitive entries of the same space or spaces for work when setting hybrid schedules.
  • a remote or management device that is routinely located at particular office space when working in office may set that space as its default space preference. Thereafter, the remote or management device or system 100 may automatically set that space in the future when if the status option is set to working in office.
  • the remote or management device may include an Edit space list from the list of available spaces when changing a status designate a particular space as a default space.
  • the default space for the work in office status is different from the default space for working remotely.
  • Each remote or management device may remove existing spaces and select its default space for a particular status. When selecting a space, if the list of spaces available is empty or a space is missing, then the remote or management device may add a new space. The remote or management device may also edit the list of spaces collectively available for all users of the company from that list. In response to associating a space with a particular workday status, this information is made available within system 100 in the first time period view of hybrid schedules where the insights for each day can be filtered by a particular space. The first time period view may be filtered to show the number of members that have set their workday status to be working in office at a particular space for each second time period of the first time period.
  • the space information is available for remote or management devices to explore within the member list screen where the remote or management devices also have the ability to filter the list of members to only display members who will be working at a particular space.
  • the member list may be filtered to only display the workday status of members who have set their status to working in office at a particular location on a particular second time period.
  • the remote or management devices may coordinate a common location to be co-located at a particular space for the second time period.
  • FIG. 9 A represents second period status preferences 902, such as workday status preferences, to automate repetitive tasks with schedule recommendations.
  • the remote or management device may select one or more statuses commonly selected on a periodic basis for each second time period of a first time period (i.e., each day of the week). For example, a remote or management device may routinely be co-located at a work office on Thursdays 904 and Fridays 906 as well as at home on Tuesdays 908. The remote or management device may set its preferred status to be work in office for Thursday 904 and Fridays 906, working remotely for Tuesdays 908, and undecided for the rest of the week 910, 912.
  • a first period schedule recommendations 914 may provide a personalized experience to help remote or management devices determine when and where to work on a periodic basis.
  • a particular status 916, 918, 920, 922, 924 may be recommended for each second time period of each first time period (i.e., for each day of the week of the following week).
  • the recommendation may be updated in real-time, or substantially in real-time, as the hybrid schedule of other members changes and is communicate to the remote or management device as a better recommendation when available.
  • the remote or management device may accept the recommendation 926 in response to receiving the recommendation for next first time period within the remote or management device or system 100.
  • a collapsed state 928 of the web element which may be toggled using an upper right collapse/expand icon.
  • the collapsed state may be used when a user of the device does not want to update the schedules and desires to dismiss the recommendation. Dismissing it by collapsing the web element hides the recommendation with the time period (such as days of the week) and update schedule button while keeping the time period and title in view along with the expand icon. The entire recommendation web element disappears from the screen when the device accepts to update the schedule using the button. The web element may become visible again when a new or better recommendation is available, if any.
  • FIG. 10 there is shown an operational diagram 1000 representing an operation by a remote or management device 140, 150, 160, 170 for determining recommendations, in an example implementation, which is operable to employ techniques described herein.
  • a remote or management device 140, 150, 160, 170 for determining recommendations, in an example implementation, which is operable to employ techniques described herein.
  • the device 140, 150, 160, 170 may then decide whether to adjust the schedule or calendar of the first member in accordance with this recommendation. If many first time periods are popular, then the selection would be based on routine preferences, random selection, or a combination of both.
  • first and second time periods may be of any length so long as the second time period includes multiple, non-overlapping first time periods.
  • the first time period may be a day, a portion of day (such as hours), or multiple days (such as two or three days) in which two or more first time periods may be identified within that week.
  • the first time period may be an hour, a portion of an hours (such as minutes), or multiple hours (such as morning or afternoon hours) in which two or more first time periods may be identified within that day.
  • Other combinations of first and second time periods have also been contemplated without identifying them exhaustively herein.
  • the operational diagram 1000 includes user preferences 1002 and a recommended schedule 1004 based on the second time period.
  • the operational diagram 1000 also include multiple line items of first time periods 1006, 1008, 1010, 1012, 1014 across the user preferences 1002 and the recommended schedule 1004.
  • the user preferences 1002 of the operational diagram 1000 include routine preferences 1016 of the first member and planned preferences 1018 of other group members.
  • the individual recommendations 1020, 1022, 1024, 1026, 1028 of the recommended schedule 1004 are determined based on the routine preferences 1016 and the planned preferences 1018 for each of the first time periods 1006, 1008, 1010, 1012, 1014.
  • the routine preferences 1016 include an individual routine preference 1030, 1032, 1034, 1036, 1038 for each first time period
  • the planned preferences 1018 include an individual planned preference 1040, 1042, 1044, 1046, 1048 for each first time period.
  • the recommended schedule 1004 may be determined for a second time period based on a scoring of the weighted preference of the plurality of group members.
  • the operational diagram 1000 may include a scoring engine or module 1050 to sum the individual scores of the routine preferences 1016 and the planned preferences 1018 for each first time period 1006, 1008, 1010, 1012, 1014.
  • the scoring module 1050 may include individual scores 1052, 1054, 1056, 1058, 1060 corresponding to the first time periods 1006, 1008, 1010, 1012, 1014.
  • the scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member is planning to work in office.
  • the scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which a member followed by the first member is planning to “work in office”. On the other hand, the scoring module 1050 may allocate a negative or null value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a member followed by the first member is planning to work remotely.
  • the scoring process of the scoring module 1050 is not restricted to the process described above.
  • the scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is planning to work in office.
  • the scoring module 1050 may allocate a negative value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is planning to work remotely.
  • the scoring module 1050 may allocate a null value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is undecided about, or otherwise does not disclose, a location or space.
  • the scoring module 1050 determines the individual scores 1052, 1054, 1056, 1058, 1060 by summing of values for each first time period 1006, 1008, 1010, 1012, 1014 based on the routine preferences 1016 and the planned preferences 1018.
  • the highest individual scores 1052, 1054, 1056, 1058, 1060 will be recommended to the device 140, 150, 160, 170 of the first member as time periods for work in office. Where there are many first time periods having the high score, the first time period of work in office of the first member is given higher priority than the first time period of work in office of the other group members, including the second member.
  • the maximum number of work in office time periods may correspond to the first member’s routine preferences for first time periods having the highest score.
  • the maximum of work in office to periods recommended is the largest of either (1) the number of work in office days of the first member in its routine preference or (2) a predetermined threshold of days (such as three days).
  • the system 100 prioritizes recommending time periods when there are followed members of the first member going to the office on the first member’s routine days.
  • One objective of the system 100 is to assist the first member to facilitate in-person connections with other group members more often.
  • Other considerations by the system 100, including the remote and management devices 140, 150, 160, 170 include, but are not limited to, increasing scores based on multiple meetings for a particular day, collecting location information for each entry by other group members, and providing accessibility to spaces added by other group members.
  • the multiple meetings for a particular day may be with group members or with any member. The number of meetings per day are of particular interest for known participants (such as followed members).
  • the number of meetings per day do not imply much if the participants are not known and if those participants will be in office. If the device knows the number of meetings in a day with the group members and if the members will be in office, then they may be tied together to provide a recommendation to increase in-person connections.
  • FIG. 11 represents example device components 1100 of the remote or management device 140, 150, 160, 170
  • the device components 1100 comprise a communication bus 1102 for interconnecting other device components directly or indirectly.
  • the other device components include one or more communication components 1104 communicating with other entities via a wired or wireless network, one or more processors 1106, and one or more memory components 1108.
  • the communication component 1104 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation.
  • the communication component 1104 may utilize wired or wireless technology for communication.
  • the processor or processors 1106 may execute code and process data received from other components of the device components 1100, such as information received at the communication component 1104 or stored at the memory component 1108. Each application includes executable code to provide specific functionality for the processor 1106 and/or remaining components of the management device 140. Examples of applications executable by the processor 1106 include, but are not limited to, a weighted preference module 1110 and a determined schedule module 1112.
  • the weighted preference module 1110 generates a weighted preference of the group members in response to collecting the attendance schedules.
  • the determined schedule module 1112 determines a schedule for a second time period based on the weighted preference of the group members.
  • Data stored at the memory component 1108 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140.
  • Examples of data associated with the management device 140 and stored by the memory component 1108 may include, but are not limited to, collected schedules data 1114 and recommendation & update data 1116.
  • the collected schedules data 1114 includes attendance schedules collected from group members.
  • the recommendation & update data 1116 includes schedules determined for a second time period based on the weighted preference of the group members that may be used to create recommendations and update schedules and/or calendars.
  • the device components 1100 may include one or more input components 1118 and one or more output components 1120.
  • the input components 1118 and output components 1120 of the device components 1100 may include one or more visual, audio, mechanical, and/or other components.
  • the input and output components 1118, 1120 may include a user interface 1122 for interaction with a user of the device.
  • the user interface 1122 may include a combination of hardware and software to provide a user with a desired user experience.
  • FIG. 11 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 11, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
  • FIG. 12 there is shown a flow diagram, in another example implementation, of an operation 300 of the management device.
  • the system 100 and the operation 300 assists the first member to find relevant group members to obtain updates for their hybrid schedule activity.
  • the relationship of group members who follow each other's hybrid schedule activity may be indexed so that the first member may receive recommendations to follow some or all other group members.
  • a recommended group member may be, for example, a coworker who is followed by a coworker that the first member already follows, or a coworker who follows the first member.
  • the operation 300 represents a method of a group scheduler for managing attendance recommendations.
  • the attendance schedules of the group members are collected (1202) from the system, such as the management device 140 and/or the remote device 150, 160, 170.
  • the group members include a first member and a second member, in which the second member is being followed by the first member.
  • the attendance schedules are collected at a memory component 1108 of the device.
  • the input component 1118 may collect the attendance schedules of the group members and store the collected information at the memory component 1108.
  • the processor 1106 of the device generates (1204) a weighted preference of the group members in response to collecting the attendance schedules.
  • the weighted preference is generated based on a first time period of work in office of the first and second members.
  • the first time period may be a day of a week, a portion of a day, or multiple days.
  • the weighted preference of the group members may be generated (1204) by identifying (1206) a frequency of each first time period associated with work in office for the group members. For example, where the first time period is a day of the week and the second time period is the week, the processor 1106 may identify the number of group members, including the first and second members, planning to work at a particular office for a particular of the week.
  • the attendance schedules of the group members may include spaces, such as a particular office location among multiple possible office locations. Each first time period of work in office is associated with a particular space of the spaces.
  • the processor 1106 may generate (1204) the weighted preference based on the spaces. For example, the processor 1106 may generate the weighted preference based on a common space of multiple spaces common to the first and second members for a first time period of work in office.
  • the processor 1106 of the device determines (1208) a schedule for a second time period in response to generating (1204) the weighted preference of the group members.
  • the schedule may be determined (1208) based on the weighted preference of the group members, in which the second time period is greater than the first time period.
  • a second time period may be a week, day, hour, and the like, and the second time period may be a month, week, day, and the like, so long as the second time period may be subdivided into multiple first time periods.
  • the processor 1106 may identify (1210) the first time period or periods that correspond to the highest frequency of each first time period associated with work in office for the group members.
  • Wednesday may correspond to the highest frequency if there is no other day during that week in which more group members plan to come to a particular location or space. If there are multiple first time periods when group members plan to come to the space, then the first time period of work in office of the first member is given higher priority than the first time period of work in office of the second member.
  • the processor 1106 or an output component 1120 may provide (1212) a recommendation associated with the determined schedule to a remote or management device 140, 150, 160, 170 and await acceptance (1214) of the recommendation, in response to determining (1208) the schedule. If the recommendation is accepted (1214), then a schedule or calendar associated with the first member may be updated (1216).
  • a calendar application associated with a remote or management device of the first member for the second time period may be updated in accordance with the schedule and the processor 1106 or device may proceed to collect (1202) more data from the group members. If the recommendation is not accepted (1214), then the schedule or calendar associated with the first member is not updated and the processor 1106 or device may proceed to collect (1202) more data from the group members.
  • the device components 1300 comprise a communication bus 1302 for interconnecting other device components directly or indirectly.
  • the other device components include one or more communication components 1304 communicating with other entities via a wired or wireless network, one or more processors 1306, and one or more memory components 1308.
  • the communication component 1304 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation.
  • the comm uni cat on component 1304 may utilize wired or wireless technology for communication.
  • the processor or processors 1306 may execute code and process data received from other components of the device components 1300, such as information received at the communication component 1304 or stored at the memory component 1308. Each application includes executable code to provide specific functionality for the processor 1306 and/or remaining components of the management device 140. Examples of applications executable by the processor 1306 include, but are not limited to, a collection or update module 1310 and a recommendation module 1312.
  • the collection and/or update module 1310 operates in conjunction with one or more input components 1318 to collect participant preferences, location preferences, and time preferences of group members from remote devices.
  • the recommendation module 1312 of the processor 1306 determines event participants based on the participant preferences, event locations based on the location preferences, and event times based on the time preferences.
  • the time preferences include calendar information for the event participants.
  • Data stored at the memory component 1308 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140.
  • Examples of data associated with the management device 140 and stored by the memory component 1308 may include, but are not limited to, preference data 1314 and determined data 1316.
  • the preference data 1314 includes participant preferences, location preferences, and time preferences of group members.
  • the determined data 1316 includes event participants, event locations, and event times.
  • the device components 1300 may include one or more input components 1318 and one or more output components 1320.
  • the input components 1318 and output components 1320 of the device components 1300 may include one or more visual, audio, mechanical, and/or other components.
  • the input and output components 1318, 1320 may include a user interface 1322 for interaction with a user of the device.
  • the user interface 1322 may include a combination of hardware and software to provide a user with a desired user experience.
  • the communication component 1304 may receive input from a remote device and, in such case, may be considered as an input component 1318.
  • the communication component 1304 may provide output to a remote device and, thus, may be considered as an output component 1320.
  • the input component 1318 collects participant preferences, location preferences, and time preferences of group members at a management device 140 from remote devices.
  • the group members are associated with a particular group entity, and each remote device is associated with at least one member of the plurality of group members. Examples of remote devices include, but are not limited to, the remote devices 150, 160, 170 represented by FIG. 1.
  • the output component 1320 provides a recommendation identifying the event participants, the event locations, and the event times to acceptance devices. Each acceptance device is associated with a particular member of the group members.
  • FIG. 13 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 13, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
  • the operation 1400 is a method of a group scheduler for managing attendance recommendations.
  • the operation 1400 of the management device 140 may be activated by receiving (1402) an event activation, which may be a manual device activation or an automatic system activation.
  • the management device 140 may receive an activation signal from an acceptance device 150, 160, 170 in response to a user activation at a user interface of the device.
  • the activation signal may request a connection opportunity for a small group of members at a particular time period, such as a lunch buddy for next week.
  • the activation signal may request a connection opportunity for a group of members, such as identifying possible time periods for a large in-person meeting.
  • the management device 140 may create the activation signal automatically in response to a triggered event such as a periodic activation of the group scheduler or detection of a need for member connections.
  • the operation 1400 of the management device 140 may collect (1404) participant preferences (1406), location preferences (1408), and time preferences (1410) of group members at an input component 1318 from remote devices 150, 160, 170.
  • the participant preferences, location preferences, and time preferences may be collected (1404) in response to receiving (1402) an activation signal from the acceptance device 150, 160, 170 or the management device 140.
  • the group members may be associated with a particular group entity.
  • the group members may be concurrently employed by the particular group entity, i.e., the group members are co-workers or colleagues at a particular company.
  • Each remote device 150, 160, 170 may be associated with one or more members of the group members, such as laptops or mobile devices of the members.
  • the participant preferences include a conversation topic substantially common with the group members.
  • the conversation topic may not be associated with the particular group entity.
  • these non-entity topics include, for are not limited to, activities not associated with work or employment.
  • the conversation topic may be one or more of a media presentation, an entertainment entity, or a non-work activity.
  • Examples of a media presentation include, but are not limited to, movies, television, music, and other types of shows involving media.
  • Examples of an entertainment entity include, but are not limited to, performers, broadcasters, athletes, sports teams, celebrities, and other people involved in the entertainment industry.
  • Examples of a non-work activity include, but are not limited to, cooking, fitness, sports, travel, education, and other hobbies that people may have in common.
  • the participant preferences may include the activity types for potential meetings.
  • activity types includes, but are not limited to, physical activities (e.g., laser tag, mini golf, or tree top adventures), creative activities (e.g., cooking or painting), collaborative exercise (e.g., solving puzzles & riddles or escape rooms), or learning activities (e.g., joined training, speaker event, or site visit).
  • the location preferences may include a virtual meeting mode or an in-person meeting mode.
  • the location preferences may include resource preferences of the group members.
  • the location preferences may include one or more of available food, proximity to the particular group entity, location environment, or presentation equipment. Examples of food preference include, but are not limited to vegetarian, vegan, gluten free, cultural (Asian, Central American, European, etc.), seafood, steakhouse, and the like. Examples of proximity preference include, but are not limited to, location in proximity to a certain place of interest such as an office, a meeting place, or place of convenient transportation. Examples of location environment include, but are not limited to an outdoor area to experience a surrounding environment (e.g., a park) or an indoor area to shelter from the surrounding area.
  • a surrounding environment e.g., a park
  • presentation equipment examples include, but are not limited to audio equipment, video equipment, or multimedia equipment which may be associated with a conference room, a coworking space, office space, or other types of areas for productivity.
  • indirect participant information may help to identify one or more location preferences. Examples of the indirect participant information includes, but are not limited to, heads down work, happy hours, lunch with coworkers, walk and talk meetings, team meetings, and other reasons why participants come to the office.
  • the time preferences include calendar information for the availability of event participants.
  • the time preference includes information about group members with whom there is the most interaction and/or group members who are within the same organization of a particular group entity (for example, as identified by an org chart).
  • the time preference or time preferences include one or more categories of time. Examples of a category of time include, but are not limited to, days of the week, normal work hours, before work, after work (i.e., happy hours), lunch periods, and the like.
  • An additional example of a category of time includes hybrid work arrangements of group members, such as mostly remote days, mostly in-person days, mixture of in-person and remote days, or other indications of attendance at a work location.
  • the time preferences may include a frequency of in-person attendance at one or more locations, such as weekly, monthly, or quarterly.
  • the processor 1306 of the management device 140 determines (1412) event participants, event locations, and event times in response to collecting (1404) data of the potential participants. In particular, the processor 1306 determines (1416) the event participants based on the participant preferences. The processor 1306 also determines (1416) one or more event locations based on the location preferences. The processor 1306 further determines (1418) one or more event times based on the time preferences.
  • the output component 1320 of the management device 140 such as the communication component 1304, provides (1420) a recommendation identifying the event participants, the event location(s), and the event time(s) to an acceptance device 150, 160, 170 in response to determining (1416-1418) the event participants, locations, and times.
  • the acceptance device 150, 160, 170 is associated with a particular member of the group members. Examples of the acceptance device include, but are not limited to, one or more of the remote devices 150, 160, 170.
  • the input component 1318 of the management device 140 detects (1422) whether any feedback is received from an acceptance device, such as remote device 14, 150, 170.
  • the input component 1318 of the management device 140 may detect (1422) whether the provided recommendation (1420) has been accepted by an acceptance device 150, 160, 170.
  • Feedback (1422) may be received in response to a query provided to the acceptance device 150, 160, 170 relating to one or more preferences of the participant associated with the acceptance device or, in the alternative, feedback may be received without any type of query provided by the management device 140.
  • Feedback (1422) may be in the form of a user selection among multiple choices, a user submission of information (such as text, voice, motion, and the like), or a combination of selection and choice.
  • feedback (1422) includes lack of feedback which may indicate a non-positive (i.e., less than positive) reaction to the recommendation.
  • the processors updates (1424) the calendars of the group members in response to acceptance (1422) of the recommendation.
  • the processor updates (1424) the calendars by updating them at the management device 140 or sending update signals to one or more remote devices 150, 160, 170.
  • the operation 1400 may update (1426) the data of the participants.
  • the operation 1400 may update (1428) the participant preferences, update (1430) the location preferences, and/or update (1432) the time preferences of the acceptance device.
  • the operation 1400 may update (1428) the participant preferences to add or raise the rank one or more other participants identified by the recommendation in response to receiving (1422) positive feedback about recommendation.
  • the operation 1400 may update (1428) the participant preferences to delete or lower the rank of one or more other participants identified by the recommendation in response to receiving (1422) negative feedback about recommendation.
  • the management device 14 may associate a ranking or score with each preference that is updated (1426).
  • the operation may continue to perform operations of the management device 140, such as awaiting another event activation (1402) or some other operation of the device.
  • the graphical view 1500 may include one or more icons 1504, 1506, 1508, 1510 representing the system, the services, and/or the potential participants as well as highlighting or partitioning sections of the graphical view.
  • the graphical view 1500 may include group portions 1512 that are directed to multiple potential participants of a conversation and individual portions 1514 that are directed to an individual potential participant, such as the acceptance device. For each group portion 1512, the services 1516 and/or potential participants 1518, 1520, 1522, 1524 of the conversation may be identified.
  • the graphical view 1500 may include informative information 1526 to the acceptance device about notifications and other context of the conversation.
  • the graphical view 1500 may identify a recommendation 1528 for the potential participants.
  • the recommendation 1528 may identify an opportunity for multiple potential participants 1520, 1522 to meetup based on one or more similarities (i.e., match) of their preferences.
  • the recommendation 1528 may also include added information 1530 about how their preferences are considered to be similar, such as a match of location preferences of the potential participants.
  • the recommendation 1528 may include one or more suggestions 1532 for how, when, or where the potential participants may meet based on the data of the potential participants (i.e., participant, location, and/or time preferences).
  • the recommendation 1528 may provide the potential participants with information about the next step for the meetup.
  • the recommendation 1528 may suggest a particular potential participant to send a calendar invite to all potential participants in response to the recommendation.
  • the recommendation 1528 may provide suggested locations and/or times for the meetup based on the data of the potential participants and their calendar information.
  • the managing device 140 may send automatically one or more calendar invites to all potential participants based on the data of the potential participants and their calendar information.
  • the recommendation 1528 may further include background information 1536 about the conversation so that the potential participants may understand how and/or why they are receiving the recommendation.
  • the graphical view 1500 may include an individual portion 1514 that is directed to an individual potential participant, such as the acceptance device.
  • the graphical view 1500 may provide a query 1538 to a user of the acceptance device to solicit feedback relating to the recommendation 1528.
  • Feedback may be in the form of a user selection among multiple choices 1540, 1542, a user submission of information (such as text, voice, motion, and the like), or a combination of selection and choice.
  • lack of any feedback or response may be considered as feedback since it may indicate a non-positive (i.e., less than positive) reaction to the recommendation.
  • the feedback may be used to update the data of the participants, such as participant preferences, location preferences, and/or time preferences of the acceptance device, such as the remote devices 150, 160, 170.
  • the device components 1600 comprise a communication bus 1602 for interconnecting other device components directly or indirectly.
  • the other device components include one or more communication components 1604 communicating with other entities via a wired or wireless network, one or more processors 1606, and one or more memory components 1608.
  • the communication component 1604 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation.
  • the communication component 1604 may utilize wired or wireless technology for communication.
  • the processor or processors 1606 may execute code and process data received from other components of the device components 1600, such as information received at the communication component 1604 or stored at the memory component 1608. Each application includes executable code to provide specific functionality for the processor 1606 and/or remaining components of the management device 140. Examples of applications executable by the processor 1606 include, but are not limited to, a collection or update module 1610 and a recommendation module 1612. The collection and/or update module 1610 operates in conjunction with one or more input components 1618 to collect interest preference data of group members from remote devices. The recommendation module 1612 of the processor 1606 determines meetup recommendations, including the conversation starter, to provide to one or more acceptance devices.
  • Data stored at the memory component 1608 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140.
  • Examples of data associated with the management device 140 and stored by the memory component 1608 may include, but are not limited to, preference data 1614 and determined data 1616.
  • the preference data 1614 includes interest preference data of group members from remote devices.
  • the determined data 1616 includes meetup recommendations, including the conversation starter, to provide to one or more acceptance devices.
  • the device components 1600 may include one or more input components 1618 and one or more output components 1620.
  • the input components 1618 and output components 1620 of the device components 1600 may include one or more visual, audio, mechanical, and/or other components.
  • the input and output components 1618, 1620 may include a user interface 1622 for interaction with a user of the device.
  • the user interface 1622 may include a combination of hardware and software to provide a user with a desired user experience.
  • the communication component 1604 may receive input from a remote device and, in such case, may be considered as an input component 1618.
  • the communication component 1604 may provide output to a remote device and, thus, may be considered as an output component 1620.
  • FIG. 16 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 16, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
  • FIG. 17 there is shown an eighth graphical view of a user interface 1700 of a remote device representing, by example, management of recommendation information and entry of user preference information.
  • the system 100 generates meetup recommendations and performs related operations which provide personalized conversation starters for the meetup recommendations.
  • the user interface 1700 includes a messaging section 1720 for organizational communications.
  • the messaging section 1720 may include channel information 1722 relevant to multiple group members and meetup recommendation 1724 directed privately to a specific user, i.e., the primary member of the remote device or member account.
  • the meetup recommendation 1724 is only visible at a device associated with the member account shown by the messaging section 1720.
  • the meetup recommendation 1724 of the messaging section 1720 includes member location information 1726 and/or member interest information 1728, 1730 associated with the member account.
  • the user of the device is able to enter information in open text format about his or her location and/or interests in his or her preferences profile.
  • the entered information may be available at a home page, as well as at onboarding and in one or more engagement messages, of the user interface 1700.
  • the user may select one or more editing buttons 1732, 1734, 1736 to provide create or edit the member location information 1726 and/or the member interest information 1728, 1730.
  • the user may select an editing button 1734 corresponding to personal member interest information 1728 to view an editing window 1740 for the personal interests.
  • the user may enter or edit the personal member interest information 1728 in open text field 1742 using natural language.
  • the user may select an editing button 1736 corresponding to professional member interest information 1730 to view an editing window 1760 for the professional interests.
  • the user may enter or edit the professional member interest information 1730 in open text field 1762, 1764 using natural language.
  • the editing window 1760 for the professional interests may include a learning topic field 1762 and/or a teaching topic field 1764.
  • the member interest information may include personal interests 1728, professional interests 1730, or both.
  • Personal interests 1728 are associated with non-work activities preferred by the member. Examples of personal interests 1728 include, but are not limited to hobbies outside of work, favorite foods, favorite media shows, outdoor activities, and the like.
  • Professional interests 1730 are associated with work activities preferred by the member, such as career passions of the member. Examples of professional interests 1730 include, but are not limited to learning topics and teaching topics. Learning topics are topics that the member is interested in learning and enhancing his or her understanding, with a focus on professional topics. An example of a learning topic is, “I would like to learn more about political science or how to communicate better”.
  • Teaching topics are topics that the member may help others to learn, with a focus on professional topics. An example of a teaching topic is, “I can help coworkers that would like to learn about growth marketing as I am skilled in this area with many years of experience”.
  • FIG. 18 there is shown a ninth graphical view of a user interface 1800 of a remote device representing, by example, management of recommendation information including secret tips and conversation starters.
  • the user interface 1800 includes a messaging section 1820 for organizational communications.
  • the messaging section 1820 may include channel information 1822 relevant to multiple group members and meetup recommendation 1824 directed privately to a specific user.
  • the channel information 1822 may include match information about one or more other members who have matching interest preferences with the current member, i.e., the member associated with the remote device and/or member account associated with the remote device.
  • the meetup recommendation 1824 of the messaging section 1820 includes other member information 1826 and/or conversation starters 1828 associated with the member account.
  • a device associated with a member account may receive the other member information 1826 and/or the conversation starters 1828.
  • the other member information 1826 are one or more personalized “secret tips” 1830 highlighting interests of other members matched by the system 100 with the member associated with the device.
  • the other member information 1826 may be utilized to facilitate the initiation of conversations or communications during a meetup between these members.
  • the meetup recommendation 1824 of the messaging section 1820 of a first member may include one or more conversation starters 1832 for one or more second members.
  • the system 100 may contact a remote device or server to generate these conversation starters 1832.
  • the system 100 may contact a remote server to generate the conversation starters via a natural language processing tool of an artificial intelligence technology.
  • a natural language processing tool includes, but is not limited to, InstructGPT Large Language Model of OpenAI (in San Francisco, CA, USA) to generate the conversation starters related to the coworker match’s interest preferences.
  • the system 100 may indicate that Julia has a personal interest preference “I love movies and music”.
  • An output component of the system 100 displays the output at the remote device under the section for the conversation starters 1828 of the meetup recommendation messages.
  • FIG. 19 there is shown a tenth graphical view of a user interface 1900 of a remote device representing, by example, management of recommendation information including interest preferences and conversation starters.
  • the user interface 1900 includes a messaging section 1920 for organizational communications.
  • the messaging section 1920 may include meetup recommendation 1922 relevant to multiple group members or, in the alternative or in addition to, meetup recommendation directed privately to a specific user.
  • the meetup recommendation 1922 includes match information 1924 about one or more other members who have matching interest preferences with the current member, common member interest information 1926, and/or conversation starters 1928 associated with the member account.
  • Meetup recommendations may include a summary of personal and/or professional interests that other members, matched to the current member by the system 100, have provided in their preference profile. For example, in their preference profile, their match might have entered “I love to hike, listen to music, and watch movies.” for their personal interest preference.
  • the system 100 may summarize the interests into more concise phrases, extract generalized categories of interests, or both, based on the open text statements of members in the system 100.
  • the system 100 may extra a summarized statement (such as “outdoor activities, music, and movies”) and/or a list of generalized interest categories (such as outdoor activities, music, movies).
  • the system 100 may contact a remote server to generate the conversation starters via a natural language processing tool of an artificial intelligence technology.
  • the system may contact a processing tool in order to summarize those interests into more concise sentences as well as extract generalized categories of interests from the open text preference statement of one or more members. For example, if the enduser entered “I like to hike, listen to music, and watch movies”, the system 100 might be able to extract the summarized statement and/or list of generalized categories by sending this statement to the processing tool.
  • the Summarized Statement may be used to provide a better user experience in the conversation starters that the system 100 provides to members within meetup recommendations.
  • the list of generalized categories may be indexed by the system 100 for subsequent use in pairing algorithms, common interest conversation starters generation, and the like.
  • the system 100 may utilize the generalized interest categories, as indexed, for each member to include with meetup recommendations common interests between the members and his/her match and provide personalized conversation starters related to common interests shared by both or multiple members.
  • the system 100 generates a match compatibility rank between a particular member of the group members and other members of the group members.
  • the match compatibility rank is based on a quantity of common interests between the particular member and each other member. It is important to note that the match compatibility ranking isn’t based only on shared interests. Match compatibility ranking may also be based on work location preferences of the members. For instance, if members share a primary or secondary work location preference, they may be designated a higher match compatibility score and increase the chances that the system’s pairing algorithm matches them together for a meetup recommendation. Thus, the match compatibility rank may be based on a quantity of common interests and proximity of location preference between the particular member and each other member.
  • the meetup recommendations may also include features for rematching and/or diverse pairing.
  • a meetup member may be matched with another member of the group members having the highest match compatibility ranking between them for multiple consecutive pairing cycles.
  • the rematch feature allows members to receive a new pairing on-demand after receiving a member meetup match.
  • the rematch feature may also provide substantial information to the system 100 about the member preferences, which the system will infer from a rematch request.
  • a member requesting a rematch or a new match may be indicating that there is a negative sentiment towards the usefulness of the last member match received.
  • the system 100 may be able to infer some preferences for the member. For example, if a first member requests a rematch after receiving a match with a certain second member many times, the system 100 may infer that the first member has a preference not to meet with this particular second member. Another example may be that by not requesting a rematch after receiving a match with the second member, the system 100 may infer that the first member has positive compatibility with this particular second member. The system can then index all preferences for each member and other variables that went into generating the meetup recommendation and utilize it in vector-based compatibility ranking for its meetup pairing algorithm.
  • the system 100 may infer that the previous match was not what the first member desired.
  • the system 100 may, thus, index the variables and preferences that led to, and are part of, that match in order to further improve their compatibility rankings for every member.
  • the system 100 may also ensure diversity for pairing by indexing the history of pairings and inserting some randomness in pairings to ensure that, not only the most compatible coworkers meet, but also members meet a wide range of other members through meetups.
  • the meetup recommendations may also include features for mentorship and/or skip-level pairings.
  • the system 100 may determine the best mentor(s)/mentee(s) for their career passions and professional interests. Similar to the common interest pairings, the system 100 utilizes indexed generalized interest categories for learnings topics extracted from the preferences of members. Also, a natural language processing tool of artificial intelligence technology may be used to compute match compatibility ranking for each member in the group members. For some embodiments, the system 100 may simply target mentorship pairings specifically. For some embodiments, the system 100 may expand on the type of text inputs collected from members in their preferences in order to obtain more specific data on their professional interests. Then, using these professional preferences inputs and categorizing them in generalized categories for matching, the system 100 may make mentor-mentee pairings for meetup recommendations.
  • the system 100 may facilitate a search for a mentor from which the member may learn from within a topic of interest, or find someone that may be mentored on a topic the member could help others to learn.
  • Mentorship pairing for a member group may be based on preferences from the members to rank the highest compatibility mentors and mentees for matches.
  • the system 100 may generate skip-level meetup recommendations for similar connections within the member group, such as a company.
  • the meetup recommendations may further include features for inter-group and intra-group pairings.
  • an input component may collect member preferences relating to which other members they would like to meet.
  • the system 100 may increase the precision in making a quality meetup match for them, particularly within or between departments, teams, or any sort of groupings that could be used for such matches.
  • the system 100 may request members to input their preferences about meeting members in certain groups. It could be a preference, in general, to meet people outside their groups or a more specific preference about their interest to meet members in specific groups.
  • a product manager may like to meet with members in the marketing department group of a company.
  • the additional input received at an input component may be used to determine the match compatibility ranking for each second member for the first member and make the highest quality matches as part of the meetup recommendation.
  • the system 100 may collect preferences from a first member on whether or not he or she would like to meet with certain second members as opposed to meeting individuals that are part of certain groups. Similar to how the group preferences may be integrated into the pairing algorithm, individual member preferences may be integrated into a match compatibility ranking for each member in the organization, thus making optimized meetup matches of high quality for the member based on their preferences.
  • Interest preference data of group members is collected (2010) by an input component from remote devices.
  • the group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members.
  • the interest preference data that is collected may include personal interest information (2012), professional interest information (2014), or a combination of personal and professional interest information.
  • the interest preference data that is collected includes professional interest information about a learning topic, a teaching topic, or both.
  • a processor determines (2020) a meetup recommendation for member match based on the interest preference data of the group members.
  • a conversation starter is generated (2022) based on the interest preference data.
  • generating the conversation starter may include creating (2024) an interrogative phrase associated with a common interest shared by two or more members of the group members.
  • generating the conversation starter may include generating (2026) the conversation starter via a natural language processing tool of an artificial intelligence technology.
  • the determination (2020) of a meeting recommendation may include one or more features to enhance useful pairings of members.
  • common interest information may be identified (2028) from the interest preference data relating to common interests of two or more members of the group members.
  • the meetup recommendation may include a personal interest associated with a non-work activity and a professional interest associated with a work activity.
  • a match compatibility rank between a particular member of the group members and other members of the plurality of group members may be generated (2030).
  • the match compatibility rank may be based on a quantity of common interests between the particular member and each other member.
  • the match compatibility rank may be based on a quantity of common interests and proximity of location preference between the particular member and each other member.
  • the meetup recommendation may be determined (2020) by inferring (2032) a negative-compatibility preference for two or more particular members of the group members based on receiving a request for rematching the two or more particular members and/or inferring (2032) a positive-compatibility preference for the two or more particular members of the group members based on a lack of receiving any request for rematching the two or more particular members.
  • a mentorship pairing between two or more members of the group members may be generated (2034) based on the professional interest information.
  • the meetup recommendation for participant match may be determined (2036) based on an inter-group preference or an intra-group preference of the interest preference data of the group members.
  • the meetup recommendation including the conversation starter may be provided (2040) by an output component to an acceptance device.
  • the acceptance device is associated with a particular member of the group members.
  • machine usable/readable or computer usable/readable mediums include nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), and user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs).
  • ROMs read only memories
  • EEPROMs electrically programmable read only memories
  • user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs).

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Systems and methods of a group scheduler manage attendance recommendations comprising an input component (1618), a processor (1606), and an output component (1620). The input component (1618) collects interest preference data of group members from remote devices (150, 160, 170). The group members are associated with a particular group entity, and each remote device of the remote devices (150, 160, 170) is associated with one or more members of the group members. The processor (1606) determines a meetup recommendation for member match based on the interest preference data of the group members. In determining the meetup recommendation, the processor generates a conversation starter based on the interest preference data. The output component (1620) provides the meetup recommendation, including the conversation starter, to an acceptance device (150, 160, 170). The acceptance device (150, 160, 170) is associated with a particular member of the group members.

Description

SYSTEM AND METHOD OF A GROUP SCHEDULER
FOR MANAGING ATTENDANCE RECOMMENDATIONS
FIELD OF THE INVENTION
[01] This application relates to the field of workplace scheduling systems and, more particularly, to systems and methods for managing attendance of workplace occupants for one or more facilities.
BACKGROUND
[02] For many companies, employees may work at a company facility or work from home. An increasing number of employees have hybrid schedules where they may flexibly adjust their schedules week-to-week based on the needs of their employment. Although the flexibility of adjusting his or her scheduled location has many advantages for the company and employee, the lack of location consistency may cause difficulty for coworkers to meet and collaborate. Video conferencing and audio calls address this problem to some extent but, to many people, in-person discussions are more productive or otherwise conducive for a positive work environment. For these reasons, the hybrid schedules of the modem employee have caused certain negative impacts on employee communications and productivity.
SUMMARY
[03] In accordance with one embodiment of the disclosure, there is provided an attendance management approach for facilitating in-person communications among personal and/or professional groups. The approach facilitates positive and productive interaction among people, such as coworkers, by helping them to coordinate in-person contact. In particular, the approach assists users to coordinate hybrid schedule preferences with schedules and preferences of other group members. The approach also guides group members toward the best time periods to attend a certain facility, such as a workplace, when other members of the group also plan to be present at the facility. For example, a group member may have a need to be co-located with one or more other group members with whom he or she works most closely.
[04] One aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor. The memory component collects attendance schedules of group members, in which the group members include a first member, a second member, and a third member. The processor generates a first group preference of the first member in response to collecting the attendance schedules. The processor indexes the first group preference of the first member based on a second group preference of the second member. The processor updates the first group preference of the first member to include the third member. The first group preference includes one or more members of the group members followed by the first member, in which the first group preference includes the second member. The second group preference includes one or more members of the group members followed by the second member, in which the second group preference includes the third member.
[05] Another aspect is a method of a group scheduler for managing attendance recommendations. Attendance schedules of group members are collected, in which the group members include a first member, a second member, and a third member. A first group preference of the first member is generated in response to collecting the attendance schedules. The first group preference includes one or more members of the group members followed by the first member, in which the first group preference includes the second member. The first group preference of the first member is indexed based on a second group preference of the second member. The second group preference includes one or more members of the group members followed by the second member, in which the second group preference includes the third member. The first group preference of the first member is updated to include the third member. [06] Yet another aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor. The memory component collects attendance schedules of group members, in which the group members include a first member and a second member. The processor generates a group preference of the first member in response to collecting the attendance schedules. The processor indexes the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member. The processor updates the attendance schedule of the first member for the future time period by changing the first location status of the first member to correspond to the second location status of the second member. The group preference includes one or more members of the group members followed by the first member, in which the group preference includes the second member. The first location status is one of either a work location status or a nonwork location status, and the second location status is the other of either the work location status or the non-work location status.
[07] Still another aspect is a method of a group scheduler for managing attendance recommendations. Attendance schedules of group members are collected, in which the group members include a first member and a second member. A group preference of the first member is generated in response to collecting the attendance schedules. The group preference includes one or more members of the group members followed by the first member, in which the group preference includes the second member. The group preference of the first member is indexed based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member. The first location status is one of either a work location status or a non-work location status, and the second location status is the other of either the work location status or the non-work location status. The attendance schedule of the first member is updated for the future time period by changing the first location status of the first member to correspond to the second location status of the second member. [08] A further aspect is a system of a group scheduler for managing attendance recommendations comprising a memory component and a processor. The memory component collects multiple attendance schedules of multiple group members. The group members include a first member and a second member. The second member is being followed by the first member. The processor generates a weighted preference of the group members in response to collecting the attendance schedules. The processor determines a schedule for a second time period based on the weighted preference of the group members. The weighted preference is generated based on a first time period of work in office of the first and second members. The second time period is greater than the first time period.
[09] Another further aspect is a method of a group scheduler for managing attendance recommendations. Multiple attendance schedules of multiple group members are collected. The group members include a first member and a second member. The second member is being followed by the first member. A weighted preference of the group members is generated in response to collecting the attendance schedules. The weighted preference is generated based on a first time period of work in office of the first and second members. A schedule for a second time period is determined based on the weighted preference of the group members. The second time period is greater than the first time period.
[10] Yet another aspect is a system of a group scheduler for managing attendance recommendations comprising an input component, a processor, and an output component. The input component collects participant preferences, location preferences, and time preferences of group members at a management device from remote devices. The group members are associated with a particular group entity, and each remote device is associated with one or more members of the group members. The processor determines event participants based on the participant preferences, determines one or more event locations based on the location preferences, and determines one or more event times based on the time preferences. The time preferences including calendar information for the event participants. The output component provides a recommendation identifying the event participants, the event location(s), and the event time(s) to an acceptance device. The acceptance device is associated with a particular member of the group members.
[11] Still another aspect is a method of a group scheduler for managing attendance recommendations. Participant preferences, location preferences, and time preferences of group members are collected at an input component from remote devices. The group members are associated with a particular group entity. Each remote device is associated with one or more members of the group members. Event participants are determined at a processor based on the participant preferences. One or more event locations are determined at the processor based on the location preferences. One or more event times are determined at the processor based on the time preferences. The time preferences include calendar information for the event participants. A recommendation identifying the event participants, the event location(s), and the event time(s) are provided by an output component to an acceptance device. The acceptance device is associated with a particular member of the group members.
[12] Another aspect is a system of a group scheduler for managing attendance recommendations comprising an input component, a processor, and an output component. The input component collects interest preference data of group members from remote devices. The group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members. The processor determines a meetup recommendation for member match based on the interest preference data of the group members. In determining the meetup recommendation, the processor generates a conversation starter based on the interest preference data. The output component provides the meetup recommendation, including the conversation starter, to an acceptance device. The acceptance device is associated with a particular member of the group members. [13] Another aspect is a method of a group scheduler for managing attendance recommendations. Interest preference data of group members are collected at an input component from remote devices. The group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members. A meetup recommendation is determined at a processor for member match based on the interest preference data of the group members. In determining the meetup recommendation, a conversation starter is generated based on the interest preference data. The meetup recommendation including the conversation starter is provided by an output component to an acceptance device. The acceptance device is associated with a particular member of the group members.
[14] The above-described features and advantages, as well as others, will become more readily apparent to those of ordinary skill in the art by reference to the following detailed description and accompanying drawings. While it would be desirable to provide one or more of these or other advantageous features, the teachings disclosed herein extend to those embodiments which fall within the scope of the appended claims, regardless of whether they accomplish one or more of the above-mentioned advantages.
BRIEF DESCRIPTION OF THE DRAWINGS
[15] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, wherein like numbers designate like objects.
[16] FIG. 1 is an illustration of a system of a group scheduler for managing attendance recommendations, in an example implementation, that is operable to employ techniques described herein.
[17] FIG. 2 is a block diagram of various components of a management device, in an example implementation, of FIG. 1. [18] FIG. 3 is a flow diagram, in an example implementation, of an operation of the management device of FIGs. 1 and 2.
[19] FIG. 4 is a flow diagram, in an example implementation, of another operation of the management device of FIGs. 1 and 2.
[20] FIG. 5, including 5A and 5B, represents a first graphical view of a user interface of a remote device of FIG. 1, in an example implementation, that is operable to employ techniques described herein.
[21] FIG. 6 represents a second graphical view of a user interface of a remote device of FIG. 1, in an example implementation, that is operable to employ techniques described herein.
[22] FIGs. 7A through 7C illustrate a third graphical view of a user interface of a remote device of FIG. 1 representing, by example, followed coworker preferences.
[23] FIGs. 8A through 8D illustrate a fourth graphical view of a user interface of the remote device of FIG. 1 representing, by example, space preferences.
[24] FIGs. 9A through 9C illustrate fifth and sixth graphical views of a user interface of a remote device of FIG. 1 representing, by example, workday status preferences and weekly schedule recommendations.
[25] FIG. 10 is an operational diagram representing an operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
[26] FIG. 11 is a block diagram of various components of a management device, in another example implementation, of FIG. 1. [27] FIG. 12 is a flow diagram representing another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
[28] FIG. 13 is a block diagram of various components of the management device, in still another example implementation, of FIG. 1.
[29] FIG. 14 is a flow diagram representing yet another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein.
[30] FIG. 15 illustrates a seventh graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information and feedback information.
[31] FIG. 16 is a block diagram of various components of the management device, in yet another example implementation, of FIG. 1.
[32] FIG. 17 illustrates an eighth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information and entry of user preference information.
[33] FIG. 18 illustrates a ninth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information including secret tips and conversation starters.
[34] FIG. 19 illustrates a tenth graphical view of a user interface of a remote device of FIG. 1 representing, by example, management of recommendation information including interest preferences and conversation starters.
[35] FIG. 20 is a flow diagram representing still another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein. DETAILED DESCRIPTION
[36] Various technologies that pertain to systems and methods that facilitate attendance management of a group scheduling system will now be described with reference to the drawings, where like reference numerals represent like elements throughout. The drawings discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged apparatus. It is to be understood that functionality that is described as being carried out by certain system elements may be performed by multiple elements. Similarly, for instance, an element may be configured to perform functionality that is described as being carried out by multiple elements. The numerous innovative teachings of the present application will be described with reference to exemplary non-limiting embodiments.
[37] Referring to FIG. 1, there is shown a high-level representation of a system 100 for attendance management of a group scheduling system for one or more facilities 110, 120, 130. The attendance management system 100 includes a management device 140 located on-site at a facility 110 and/or remote from one or more facilities 120, 130. The system 100 also includes devices 150, 160, 170 located remote from the management device 140, i.e., remote devices, positioned at more than one facility or remote location, such as facilities 120, 130. The remote devices 150, 160, 170 may communicate with the management device and/or each other via a network connection 180. Examples of facilities include, but are not limited to, a work location such as an office 120 or management location 110, or a non-work location such as home location 130 or remote location. Examples of remote devices 150, 160, 170, include, but are not limited to, a workstation, a laptop, a tablet, or a mobile device. Examples of the network connection 180 include, but are not limited to, a Cloud network or the Internet. [38] It is to be understood that FIG. 1 is provided for illustrative purposes only to represent examples of the management device 140 and the remote devices 150, 160, 170, and is not intended to be a complete diagram of the various components that may be utilized by the system 100. The management device 140 may include various other devices not shown in FIG. 1, such as presence or location sensors). The management device 140 may include a combination of two or more devices, such as the management device 140 being co-located with one or more remote devices 150, 160, 170. The management device 140 may include a division of a particular device into two or more separate devices (such as the management device 140 or its operation being distributed among more than one location or facility 110, 120, 130).
[39] FIG. 2 represents example device components 200 of the management device 140. The device components 200 comprise a communication bus 202 for interconnecting other device components directly or indirectly. The other device components include one or more communication components 204 communicating with other entities via a wired or wireless network, one or more processors 206, and one or more memory components 208. The communication component 204 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation. The communication component 204 may utilize wired or wireless technology for communication.
[40] The processor or processors 206 may execute code and process data received from other components of the device components 200, such as information received at the communication component 204 or stored at the memory component 208. The code associated with the management device 140 and stored by the memory component
208 may include, but is not limited to, operating systems, applications, modules, drivers, and the like. An operating system includes executable code that controls basic functions, such as interactions among the various components of the device components 200, communication with external devices via the communication component 204, and storage and retrieval of code and data to and from the memory component 208. [41] Each application includes executable code to provide specific functionality for the processor 206 and/or remaining components of the management device 140. Examples of applications executable by the processor 206 include, but are not limited to, an index & recommendation module 210 and an update module 212. The index & recommendation module 210 processes the group preferences generated from the collected attendance schedules. For some embodiments, a group preference of one group member may be indexed based on a group preference of another, different group member. For some embodiments, a group preference may be indexed based on a difference between a first location status of one group member and a second location status of another, different group member for a future time period of an attendance schedule. The index & recommendation module 210 also includes a recommendation engine of the group scheduler that generates a recommendation in response to indexing the group preference. The update module 212 processes group preferences and/or attendance schedules. For some embodiments, a group preference may be updated to include or remove a group member. For some embodiments, an attendance schedule may be update for a future time period by changing a first location status of one group member to correspond to a second location status of another, different group member.
[42] Data stored at the memory component 208 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140. Examples of data associated with the management device 140 and stored by the memory component 208 may include, but are not limited to, schedule and status data 214 and group preference data 216. The schedule and status data 214 may include attendance schedules of group members (such as a first member, a second member, etc.) and/or location statuses. Examples of location statuses include, but are not limited to, a work location status associated with a work location 110, 120; a non-work location status associated with a non-work location 130, and the like. The group preference data 216 generates a group preference of a group member in response to collecting attendance schedules. Each group preference corresponds to a particular group member of a group, and the group preference includes one or more other members of the group followed by the particular group member.
[43] The device components 200 may include one or more input components 218 and one or more output components 220. The input components 218 and output components 220 of the device components 200 may include one or more visual, audio, mechanical, and/or other components. For some embodiments, the input and output components 218, 220 may include a user interface 222 for interaction with a user of the device. The user interface 222 may include a combination of hardware and software to provide a user with a desired user experience.
[44] It is to be understood that FIG. 2 is provided for illustrative purposes only to represent examples of the management device 140 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device 140 may include various other components not shown in FIG. 2, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
[45] Referring to FIG. 3, there is shown a flow diagram, in an example implementation, of an operation 300 of the management device. The system 100 and the operation 300 assists the first member to find relevant group members to obtain updates for their hybrid schedule activity. The relationship of group members who follow each other’s hybrid schedule activity may be indexed so that the first member may receive recommendations to follow some or all other group members. A recommended group member may be, for example, a coworker who is followed by a coworker that the first member already follows, or a coworker who follows the first member.
[46] The operation 300 represents a method of a group scheduler for managing attendance recommendations. The attendance schedules of the group members are collected (302) from the system, such as the management device 140 and/or the remote devices 150, 160, 170. The group members include a first member, a second member, and a third member. For example, the first member may explore in-office schedules of other group members to decide when to go to an office or facility. In response to collecting (302) the attendance schedules, the operation 300 generates (304-306) a first group preference of the first member. The first group preference includes one or more members of the group members being followed by the first member. In particular, the first group preference includes the second member but does necessarily require the inclusion of the first member. To generate of the first group preference of the first member, the group members are provided (304) to a remote device associated with the first member and a user selection is received (306) from the remote device in response to the group members. The system 100 may guide the first member to select other group members whom the first member may desire to follow in order to receive updates on the in-office schedule activity of one or more other group members. Upon receiving (306) the user selection, the second member is added to the first group preference of the first member.
[47] In response to generating (304-306) the first group preference, the operation 300 indexes (308) the first group preference of the first member based on a second group preference of the second member. The second group preference includes one or more members of the group members followed by the second member, and the second group preference includes the third member. Accordingly, in order to index (308) the first group preference, the second group preference of the second member is generated (310) some time before indexing the first group preference of the first member.
[48] The group preference may be updated automatically by the management device 140 or in response to interaction with a remote device 150, 160, 170. For some embodiments, in response to indexing (308) the first group preference, a recommendation engine of the index & recommendation module 210 generates (312) a recommendation to adjust to the first group preference of the first member and the recommendation is provided (314) to one or more remote devices associated with the first member. Thus, the system 100 provides recommendations on which group members might be relevant to add to the group preference followed by the first member as well as any previous response to historical recommendations. For example, a recommendation may indicate, "You might be interested to follow [member X] because [member Y] you follow also follows him/her. Do you want to follow his/her schedule?". By providing (314) the recommendation to the remote device(s), the remote device may be operated by a user to adjust the first group preference of the first member. In such case, the operation 300 may receive (316) an acceptance of the recommendation from the remote device in response to providing (314) the recommendation. If an acceptance is received (316), then the first group preference of the first member is updated (318) to include the third member. Otherwise, the first group preference is not updated to include the third member. For some embodiments, in response to indexing (308) the first group preference, the recommendation engine of the index & recommendation module 210 generates (312) a recommendation to adjust to the first group preference of the first member and the first group preference is updated (318) automatically by the management device 140.
[49] In response to updating (318) the first group preference, the operation 300 continues with processing group preferences. For some embodiments, the operation 300 returns to indexing (308) the first group preference. For some embodiments, the operation 300 returns to generating (312) a recommendation by the recommendation engine. For some embodiments, the recommendation engine is updated (320) in response to receiving (316) a response to the recommendation from the remote device or updating (318) the first group preference. In this manner, the system 100 may determine whether a network recommendation for a group member was useful or not to improve future recommendations.
[50] Referring to FIG. 4, there is shown a flow diagram, in an example implementation, of another operation 400 of the management device. The system 100 and operation 400 may assist group members, such as employees or coworkers, to find the best days to go into the office based on which other group members are relevant to them. A second coworkers may be relevant to a first coworker if the first coworker follows the second coworker in the first coworker's group preference. The operation 400 may index the status (such as work in office, work remotely, or undecided) of each group member in the group scheduler of the system 100 for each time period (such as a workday) and the relationship of group members who follow each other's activity, recommending a change in their schedule when relevant. In addition, a recommended day in office may be a workday in the future when the group member has not set his or her location status to be working in office, i.e., schedule to work remotely. Further, a recommended day in office may be a workday in the future when there are many people followed by the first member who have set their collective status to be working in office that workday.
[51] The operation 400 represents another method of a group scheduler for managing attendance recommendations. The attendance schedules of the group members are collected (402) from the system, such as the management device 140 and/or the remote devices 150, 160, 170. The group members include a first member and a second member. For example, the first member may explore in-office schedules of individual coworkers to decide when to go to the office via the system 100. In response to collecting (402) the attendance schedules, the operation 400 generates (404-406) a group preference of the first member. The group preference includes one or more members of the group members being followed by the first member. In particular, the group preference includes the second member but does necessarily require the inclusion of the first member. To generate of the group preference of the first member, the group members are provided (404) to a remote device associated with the first member and a user selection is received (406) from the remote device in response to the group members. Upon receiving (406) the user selection, the second member is added to the group preference of the first member. The system 100 may guide the first member to select coworkers he or she would like to follow in order to get updates on their in-office schedule changes.
[52] In response to generating (404-406) the group preference, the operation 400 indexes (408) the group preference of the first member so that the system 100 may provide recommendations to, for example, adjust in-office work schedules for the first member. The operation 400 may index (408) the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member. The first location status is either one of a work location status or a nonwork location status, and the second location status is the other one of either the work location status or the non-work location status. The time period may be a particular day or some other period of time, such as an hour, a workday (as determined by employment), days excluding holidays/vacation days/sick days, a week, a weekday, a weekend, and the like. For example, the operation 400 may identify a day when the location status of the first member is a non-work location status (e.g., working from home) whereas the location status of the second member is a work location status (e.g., working at the office). The operation 400 may also consider time periods that are not in the future, but the operation must consider at least future time periods for indexing (408) the group preference.
[53] The attendance schedule may be updated automatically by the management device 140 or in response to interaction with a remote device 150, 160, 170. The system 100 may provide a recommendation to the first member to change his or her location status to a work location status or non-work location status during a particular time period. For some embodiments, in response to indexing (408) the group preference, a recommendation engine of the index & recommendation module 210 generates (412) a recommendation to adjust to the attendance schedule of the first member and the recommendation is provided (414) to one or more remote devices associated with the first member. By providing (414) the recommendation to the remote device(s), the system 100 prompt the first member to change his or her schedule so the remote device may be operated by a device user to adjust the attendance schedule of the first member. In such case, the operation 400 may receive (416) an acceptance of the recommendation from the remote device in response to providing (414) the recommendation. If an acceptance is received (416), then the attendance schedule of the first member is updated (418) for the future time period by changing the first location status of the first member to correspond to the second location status of the second member. Accordingly, the first and second members will be scheduled to be at the same location during the future time period. Otherwise, the attendance schedule is not updated for the future time period. For some embodiments, in response to indexing (408) the group preference, the recommendation engine of the index & recommendation module 210 generates (412) a recommendation to adjust to the attendance schedule of the first member and the attendance schedule is updated (418) automatically by the management device 140.
[54] In response to updating (418) the attendance schedule, the operation 400 continues with processing group preferences. For some embodiments, the operation 400 returns to indexing (408) the group preference. For some embodiments, the operation 400 returns to generating (412) a recommendation by the recommendation engine. For some embodiments, the recommendation engine is updated (420) in response to receiving (416) a response to the recommendation from the remote device or updating (418) the attendance schedule. In this manner, the system 100 may index the acceptance as feedback to improve the recommendation model of the recommendation engine.
[55] For some embodiments, the operation 400 may provide (422) a notification to a remote device associated with the first member. The notification may indicate that the second location status of the second member is different from the first location status of the first member for the future time period. The notification may be provided (422) in response to generating (412) the recommendation. The first member may receive the notification or see a recommended insight at an output component (such as a web interface of a display) about other group members he or she follows. For example, the first member may receive a notification about other members going into a local office on a day when the first member is planning to work from home.
[56] Referring to FIG. 5, including 5A and 5B, there is shown a first graphical view 500 of a user interface of a remote device, in an example implementation, which is operable to employ techniques described herein. The first graphical view 500 includes a header 502, a time period range 504, and multiple time periods 506, 508, 510, 512, 514 (506-514). The header 502 includes information associated with the group, such as a group identification and/or a group member identification. The time period range includes information associated with the time period associated with the attendance management of the group scheduling system, such as a date range or date navigation. The time periods 506-514 include information associated with each corresponding time period such as a date 516, a date status 518, a member attendance status 520 of the first member, and/or a group attendance status 522 of the group members. The first graphical view 500 may further include a menu 524 to select among different features of the user interface, such as a status window and a profile window.
[57] Each time period 506-514 provides insight to the attendance management of the group scheduler for the corresponding time period. The date 516 provides a date identification for the particular time period. The date status 518 provides status information associated with the particular time period. For example, a time period 506 may be in a disabled state when, for example, a day of the current week has passed. In the disabled state, the time period 506 may indicates the status as "passed". As another example, a time period 508 may indicates a current time period, such as a status of "today", and/or other time periods 510-514 may indicate future time periods by providing a null or no date status indication. The member attendance status 520 of the first member may be indicated by two or more location status, such as a work location status or a nonwork location status. For example, the member attendance status 520 may provide for a work status, a home status, and an undecided status. For some embodiments, the undecided status may be set by default. For some embodiments, the member attendance status 520 may be set or changed by a user selection of the user interface. For some embodiments, the member attendance status 520 may be set or changed automatically or semi-automatically by one or more sensors or databases of the device or system, such as a proximity sensor, a location sensor, a calendar application, or a communication application (such as monitoring emails, texts, calls, or online posts). The group attendance status 522 of the group members may indicate a collective indicator or indicators of the status of the group members. For example, the group attendance status 522 may indicate a most common location status of the group members and/or the number of group members having the most common location status.
[58] An example operation of the first graphical view 500 may be explained. By default, "calendar weekday" may be in the current work week in which no weekend days are provided. If a user opens the app during a weekend, then the first graphical view may show the upcoming work week with the back button disabled 526. The user may use a caret button to navigate to future weeks and the disabled caret button for weeks in the past. If the user opens the app during the weekdays and navigates to future weeks, then a user selection on a calendar button 528 will take the user back to the current work week, in which "today" is within this particular week. If the user opens the app during the weekend and navigates to future weeks, then a user selection on the calendar button 528 will take user back to the upcoming work week.
[59] For some embodiments, the first graphical view 500 provides a scrollable screen 530, as represented by the middle section of FIG. 5. When a user scrolls the screen, calendar weekdays become part of the persistent header 532 on the top area. The header separator 534 may also be provided by the scrollable screen 530.
[60] The first graphical view 500 further provides a name list 536-548 that is accessible by selecting a particular time period 506-514. Each name identification of the name list 536-548 may include a corresponding location status indicator 550, graphical and/or textual, providing the location status corresponding to the name identification. The first graphical view 500 may include a name list header 552 when displaying the name list 536-548 that includes group information, such as a number of members of a most common location status 554 and a number of members of a location status other than the most common location status 556, 558. The number of members of a location status other than the most common location status may include members working remotely 556 and/or member undecided 558. For example, any part of an area associated with the selected time period 506-514 may bring up the name list except for selection of the member attendance status 520. The name list may include all group members. For some embodiments, the name list may be ordered and organized into subgroups based on the location status of the group members. For example, a first subgroup of members 536-542 may include members having a work location status, a second subgroup of members 544- 548 may include members having a non-work location status. As another example, a first subgroup of members 536-542 may include members having a work location status, a second subgroup of members 544 may include members having a remote location status, and third subgroup of member may include members who are undecided 546, 548. For some embodiments, the name list 536-548 may be provided in alphabetical order for the entire group or for each individual subgroup. The name list 536-548 may include a sticky area 560 that allows a user to update a first member location status while viewing or scrolling through the name list.
[61] Referring to FIG. 6, there is shown a second graphical view 600 of a user interface of another remote device of FIG. 1, in an example implementation, which is operable to employ techniques described herein. In contrast to the first graphical view 500 of FIG. 5, the second graphical view 600 provides more information on less screens for remote devices having larger display areas. In particular, the second graphical view 600 includes both a member status portion 670 for multiple time periods and a group status portion 680 for a particular time period on a single screen or view. This second graphical view 600 may display a full list of group member location statuses based on selected and/or highlighted information in the middle portion of the screen. For some embodiments, when a user lands on this webpage or screen, the information for the current day may be selected and/or highlighted by default.
[62] The second graphical view 600 includes a header 602, a time period range 604, and multiple time periods 606-614. The various parts of the second graphical view 600 of FIG. 6 provides information and features similar to the corresponding parts of the first graphical view 500 of FIG. 5. For example, the time periods 606-614 include information associated with each corresponding time period such as a date 616, a date status 618, a member attendance status 620 of the first member, a group attendance status 622 of the group members, and/or a menu 624.
[63] The second graphical view 600 further provides a name list 636-648 that is accessible by selecting a particular time period 606-614. Again, the various name list parts of the second graphical view 600 of FIG. 6 provides information and features similar to the corresponding name list parts of the first graphical view 500 of FIG. 5.
[64] Referring to FIGs. 7A through 7C, there are shown a third graphical view 700 of a user interface of a remote or management device 140, 150, 160, 170, in an example implementation. The third graphical view 700 manages followed member preferences, similar to the first graphical view 500 of FIG. 5. Specifically, each screen 702, 704, 706 of the third graphical view 700 includes a header 708, a menu 710, and a set of content. In addition to the features of the first graphical view 500, the third graphic view 700 includes followed member selections 712 for followed member preferences, such as followed member lists and followed member filters.
[65] Referring specifically to FIG. 7A, the third graphical view 700 includes a first screen 702 to identify followed members 714 and non-followed members 716. A remote or management device 140, 150, 160, 170 may select a follow chip 718 associated with a member’s identification to follow non-followed members 716 to add the member to a list of followed members 714. The remote or management device may deselect a following chip 720 associated with a member’s identification to remove the member from the list of followed members 714. In response to forming or configuring the list of followed members 714. The remote or management device may filter schedules and receive recommendations when hybrid schedules of those selected members are updated.
[66] Referring specifically to FIGs. 7B and 7C, the third graphical view 700 includes one or more other screens 704, 706 to filter followed member data. In particular, the followed members 714 may be referenced to filter their hybrid schedules. In response to a remote or management device following members, the device may filter member insights 722 of the hybrid schedules for a first time period (such as a week) at a second screen 704 subsequent to selecting one or more follow chips 718. Also, a third screen 706 associated with a second time period, shorter than the first time period (such as a day), may show a list 724 of members that the remote or management device follows, filtered to identify those members having their workday status for that day set to work in the office. The remote or management device may identify which second time periods are the most popular at the office for the first time period by filtering the insights 722 and the list 724 for the members of interest.
[67] The list of members 724 may be filtered to only display the members that the remote or management device has followed by selecting the followed members chip of the followed member selection 712. In response, the list 724 may be filtered to only display the status of the members followed by the remote or management device 150, 160, 170. The remote or management device may determine whether a particular member of interest may be located at the office for a particular second time period of the first time period. Further, the list of members 724 that the followed by the remote or management device may be used as input to provide weekly schedule recommendations.
[68] Referring to FIGs. 8A through 8D, there are shown a fourth graphical view 800 of a user interface of the remote or management device 140, 150, 160, 170 representing, by example, space preferences. For the fourth graphical view 800 manages space preferences, each screen 802, 804, 806, 808 of the fourth graphical view 800 includes a header 810, a menu 812, and a set of content. Similar to the third graphical view 700, the fourth graphical view 800 include followed member selections 814 for followed member preferences, such as followed member lists, followed member filters, and followed member filters with space information.
[69] Referring specifically to FIG. 8A, the fourth graphical view 800 includes a fourth screen 802 to identify followed members 816 and non-followed members 818. The fourth screen 802 further includes space preferences 820, 822, 824 for the followed member selections 814, followed members 816, and non-followed members 818. In particular, the followed member selections 814 may allow for a selection 820 of a listing of member information for a particular location or space, such as an Oakland office. Likewise, each member of the followed members 816 may indicate a followed member location 822, and each member of the non-followed members 818 may indicate a non-followed member location 824.
[70] For these embodiments of the space preferences, the remote or management device associates a location or space with a corresponding workday status. The hybrid schedules coordinated with the spaces where members will be working and create in- person connections. Each remote or management device may associate a space to a work in office status indicate its space preference, such as a company location. Each remote or management device may associate a space to a non-work in office status, such as a working remotely status, to notify members about working outside the company offices, such as a cafe close to the office or a coworking space. For some embodiments, the remote or management device or system 100 may select a default space, which will be automatically applied to their work in office or working remotely statuses by defaults.
[71] For some embodiments, the remote or management device or system 100 may specify a default space preference. The default space preference may be assigned automatically to a corresponding workday status in response to a remote or management device setting a work status. For some embodiments, the remote or management device may filter the hybrid schedules of their members by spaces in order to identify the members locations or spaces on any given day, and which days are popular for a given first time period at a space.
[72] Referring specifically to FIGs. 8B through 8D, the system 100 and/or remote or management device may associate spaces to a workday status. The remote or management device may select one of multiple status options of the member insights 826, for a particular second time period. Examples of status options include, but are not limited to, work in office 828, not work in office (i.e., working remotely) 830, or undecided 832. In response to selection of a status option for a particular second time period, the remote or management device or system 100 may select a particular location or space 834 associated with the work status. The member insights 836 may be updated to indicate the selected space 838 in response to selection of the particular space. If the member does not have a default space selected, the device may be prompted to select from the list of available spaces for the company to choose a location or space. The list of spaces available for the work in office and working remotely statuses are separate and collectively managed by all members of a group account.
[73] Default space preferences may be utilized for repetitive entries of the same space or spaces for work when setting hybrid schedules. For example, a remote or management device that is routinely located at particular office space when working in office may set that space as its default space preference. Thereafter, the remote or management device or system 100 may automatically set that space in the future when if the status option is set to working in office. For some embodiments, the remote or management device may include an Edit space list from the list of available spaces when changing a status designate a particular space as a default space. For some embodiments, the default space for the work in office status is different from the default space for working remotely.
[74] Each remote or management device may remove existing spaces and select its default space for a particular status. When selecting a space, if the list of spaces available is empty or a space is missing, then the remote or management device may add a new space. The remote or management device may also edit the list of spaces collectively available for all users of the company from that list. In response to associating a space with a particular workday status, this information is made available within system 100 in the first time period view of hybrid schedules where the insights for each day can be filtered by a particular space. The first time period view may be filtered to show the number of members that have set their workday status to be working in office at a particular space for each second time period of the first time period.
[75] Additionally, the space information is available for remote or management devices to explore within the member list screen where the remote or management devices also have the ability to filter the list of members to only display members who will be working at a particular space. For example, the member list may be filtered to only display the workday status of members who have set their status to working in office at a particular location on a particular second time period. Accordingly, the remote or management devices may coordinate a common location to be co-located at a particular space for the second time period.
[76] Referring to FIGs. 9A through 9C, there are shown fifth and sixth graphical views of a user interface of a remote or management device 140, 150, 160, 170 representing, by example, first period schedule recommendations and second period status preferences. FIG. 9 A represents second period status preferences 902, such as workday status preferences, to automate repetitive tasks with schedule recommendations. In order to set a preferred period status, the remote or management device may select one or more statuses commonly selected on a periodic basis for each second time period of a first time period (i.e., each day of the week). For example, a remote or management device may routinely be co-located at a work office on Thursdays 904 and Fridays 906 as well as at home on Tuesdays 908. The remote or management device may set its preferred status to be work in office for Thursday 904 and Fridays 906, working remotely for Tuesdays 908, and undecided for the rest of the week 910, 912.
[77] Referring specifically to FIG. 9B, a first period schedule recommendations 914, such as weekly schedule recommendations, may provide a personalized experience to help remote or management devices determine when and where to work on a periodic basis. By utilizing followed member and preferred workday status preferences collected from the remote or management device or system 100, a particular status 916, 918, 920, 922, 924 may be recommended for each second time period of each first time period (i.e., for each day of the week of the following week). The recommendation may be updated in real-time, or substantially in real-time, as the hybrid schedule of other members changes and is communicate to the remote or management device as a better recommendation when available. For some embodiments, the remote or management device may accept the recommendation 926 in response to receiving the recommendation for next first time period within the remote or management device or system 100.
[78] Referring to FIG. 9C, there is shown a collapsed state 928 of the web element, which may be toggled using an upper right collapse/expand icon. The collapsed state may be used when a user of the device does not want to update the schedules and desires to dismiss the recommendation. Dismissing it by collapsing the web element hides the recommendation with the time period (such as days of the week) and update schedule button while keeping the time period and title in view along with the expand icon. The entire recommendation web element disappears from the screen when the device accepts to update the schedule using the button. The web element may become visible again when a new or better recommendation is available, if any.
[79] Referring to FIG. 10, there is shown an operational diagram 1000 representing an operation by a remote or management device 140, 150, 160, 170 for determining recommendations, in an example implementation, which is operable to employ techniques described herein. In general, the most popular first time periods by the group members for working at a particular space will be recommended to the first member. The device 140, 150, 160, 170 may then decide whether to adjust the schedule or calendar of the first member in accordance with this recommendation. If many first time periods are popular, then the selection would be based on routine preferences, random selection, or a combination of both.
[80] It should be noted that the first and second time periods may be of any length so long as the second time period includes multiple, non-overlapping first time periods. For example, where the second time period is a week, the first time period may be a day, a portion of day (such as hours), or multiple days (such as two or three days) in which two or more first time periods may be identified within that week. As another example, where the second time period is a day, the first time period may be an hour, a portion of an hours (such as minutes), or multiple hours (such as morning or afternoon hours) in which two or more first time periods may be identified within that day. Other combinations of first and second time periods have also been contemplated without identifying them exhaustively herein.
[81] The operational diagram 1000 includes user preferences 1002 and a recommended schedule 1004 based on the second time period. The operational diagram 1000 also include multiple line items of first time periods 1006, 1008, 1010, 1012, 1014 across the user preferences 1002 and the recommended schedule 1004. The user preferences 1002 of the operational diagram 1000 include routine preferences 1016 of the first member and planned preferences 1018 of other group members. The individual recommendations 1020, 1022, 1024, 1026, 1028 of the recommended schedule 1004 are determined based on the routine preferences 1016 and the planned preferences 1018 for each of the first time periods 1006, 1008, 1010, 1012, 1014. The routine preferences 1016 include an individual routine preference 1030, 1032, 1034, 1036, 1038 for each first time period, and the planned preferences 1018 include an individual planned preference 1040, 1042, 1044, 1046, 1048 for each first time period.
[82] For some embodiments, the recommended schedule 1004 may be determined for a second time period based on a scoring of the weighted preference of the plurality of group members. Thus, the operational diagram 1000 may include a scoring engine or module 1050 to sum the individual scores of the routine preferences 1016 and the planned preferences 1018 for each first time period 1006, 1008, 1010, 1012, 1014. The scoring module 1050 may include individual scores 1052, 1054, 1056, 1058, 1060 corresponding to the first time periods 1006, 1008, 1010, 1012, 1014. [83] For some embodiments, the scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member is planning to work in office. The scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which a member followed by the first member is planning to “work in office”. On the other hand, the scoring module 1050 may allocate a negative or null value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a member followed by the first member is planning to work remotely.
[84] The scoring process of the scoring module 1050 is not restricted to the process described above. For some embodiments, as represented by FIG. 10, the scoring module 1050 may allocate a positive value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is planning to work in office. The scoring module 1050 may allocate a negative value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is planning to work remotely. The scoring module 1050 may allocate a null value for each first time period 1006, 1008, 1010, 1012, 1014 in which the first member and/or a followed member is undecided about, or otherwise does not disclose, a location or space.
[85] The scoring module 1050 determines the individual scores 1052, 1054, 1056, 1058, 1060 by summing of values for each first time period 1006, 1008, 1010, 1012, 1014 based on the routine preferences 1016 and the planned preferences 1018. The highest individual scores 1052, 1054, 1056, 1058, 1060 will be recommended to the device 140, 150, 160, 170 of the first member as time periods for work in office. Where there are many first time periods having the high score, the first time period of work in office of the first member is given higher priority than the first time period of work in office of the other group members, including the second member. For example, the maximum number of work in office time periods may correspond to the first member’s routine preferences for first time periods having the highest score. For another example, the maximum of work in office to periods recommended is the largest of either (1) the number of work in office days of the first member in its routine preference or (2) a predetermined threshold of days (such as three days).
[86] While the rule-based process described above takes into consideration the routine preferences of the first member, the system 100 prioritizes recommending time periods when there are followed members of the first member going to the office on the first member’s routine days. One objective of the system 100 is to assist the first member to facilitate in-person connections with other group members more often. Other considerations by the system 100, including the remote and management devices 140, 150, 160, 170, include, but are not limited to, increasing scores based on multiple meetings for a particular day, collecting location information for each entry by other group members, and providing accessibility to spaces added by other group members. For example, the multiple meetings for a particular day may be with group members or with any member. The number of meetings per day are of particular interest for known participants (such as followed members). The number of meetings per day do not imply much if the participants are not known and if those participants will be in office. If the device knows the number of meetings in a day with the group members and if the members will be in office, then they may be tied together to provide a recommendation to increase in-person connections.
[87] FIG. 11 represents example device components 1100 of the remote or management device 140, 150, 160, 170 The device components 1100 comprise a communication bus 1102 for interconnecting other device components directly or indirectly. The other device components include one or more communication components 1104 communicating with other entities via a wired or wireless network, one or more processors 1106, and one or more memory components 1108. The communication component 1104 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation. The communication component 1104 may utilize wired or wireless technology for communication. [88] The processor or processors 1106 may execute code and process data received from other components of the device components 1100, such as information received at the communication component 1104 or stored at the memory component 1108. Each application includes executable code to provide specific functionality for the processor 1106 and/or remaining components of the management device 140. Examples of applications executable by the processor 1106 include, but are not limited to, a weighted preference module 1110 and a determined schedule module 1112. The weighted preference module 1110 generates a weighted preference of the group members in response to collecting the attendance schedules. The determined schedule module 1112 determines a schedule for a second time period based on the weighted preference of the group members.
[89] Data stored at the memory component 1108 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140. Examples of data associated with the management device 140 and stored by the memory component 1108 may include, but are not limited to, collected schedules data 1114 and recommendation & update data 1116. The collected schedules data 1114 includes attendance schedules collected from group members. The recommendation & update data 1116 includes schedules determined for a second time period based on the weighted preference of the group members that may be used to create recommendations and update schedules and/or calendars.
[90] The device components 1100 may include one or more input components 1118 and one or more output components 1120. The input components 1118 and output components 1120 of the device components 1100 may include one or more visual, audio, mechanical, and/or other components. For some embodiments, the input and output components 1118, 1120 may include a user interface 1122 for interaction with a user of the device. The user interface 1122 may include a combination of hardware and software to provide a user with a desired user experience. [91] It is to be understood that FIG. 11 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 11, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
[92] Referring to FIG. 12, there is shown a flow diagram, in another example implementation, of an operation 300 of the management device. The system 100 and the operation 300 assists the first member to find relevant group members to obtain updates for their hybrid schedule activity. The relationship of group members who follow each other's hybrid schedule activity may be indexed so that the first member may receive recommendations to follow some or all other group members. A recommended group member may be, for example, a coworker who is followed by a coworker that the first member already follows, or a coworker who follows the first member.
[93] The operation 300 represents a method of a group scheduler for managing attendance recommendations. The attendance schedules of the group members are collected (1202) from the system, such as the management device 140 and/or the remote device 150, 160, 170. The group members include a first member and a second member, in which the second member is being followed by the first member. The attendance schedules are collected at a memory component 1108 of the device. For embodiments where the information is collected from other devices, the input component 1118 may collect the attendance schedules of the group members and store the collected information at the memory component 1108.
[94] The processor 1106 of the device generates (1204) a weighted preference of the group members in response to collecting the attendance schedules. The weighted preference is generated based on a first time period of work in office of the first and second members. For example, the first time period may be a day of a week, a portion of a day, or multiple days. For some embodiments, the weighted preference of the group members may be generated (1204) by identifying (1206) a frequency of each first time period associated with work in office for the group members. For example, where the first time period is a day of the week and the second time period is the week, the processor 1106 may identify the number of group members, including the first and second members, planning to work at a particular office for a particular of the week.
[95] For some embodiments, the attendance schedules of the group members may include spaces, such as a particular office location among multiple possible office locations. Each first time period of work in office is associated with a particular space of the spaces. Also, for some embodiments, the processor 1106 may generate (1204) the weighted preference based on the spaces. For example, the processor 1106 may generate the weighted preference based on a common space of multiple spaces common to the first and second members for a first time period of work in office.
[96] The processor 1106 of the device determines (1208) a schedule for a second time period in response to generating (1204) the weighted preference of the group members. The schedule may be determined (1208) based on the weighted preference of the group members, in which the second time period is greater than the first time period. For example, a second time period may be a week, day, hour, and the like, and the second time period may be a month, week, day, and the like, so long as the second time period may be subdivided into multiple first time periods. For some embodiments, the processor 1106 may identify (1210) the first time period or periods that correspond to the highest frequency of each first time period associated with work in office for the group members. For example, Wednesday may correspond to the highest frequency if there is no other day during that week in which more group members plan to come to a particular location or space. If there are multiple first time periods when group members plan to come to the space, then the first time period of work in office of the first member is given higher priority than the first time period of work in office of the second member. [97] For some embodiments, the processor 1106 or an output component 1120 may provide (1212) a recommendation associated with the determined schedule to a remote or management device 140, 150, 160, 170 and await acceptance (1214) of the recommendation, in response to determining (1208) the schedule. If the recommendation is accepted (1214), then a schedule or calendar associated with the first member may be updated (1216). For example, a calendar application associated with a remote or management device of the first member for the second time period may be updated in accordance with the schedule and the processor 1106 or device may proceed to collect (1202) more data from the group members. If the recommendation is not accepted (1214), then the schedule or calendar associated with the first member is not updated and the processor 1106 or device may proceed to collect (1202) more data from the group members.
[98] Referring to FIG. 13, there is shown a block diagram 1300 of various components of the remote or management device 140, 150, 160, 170 in still another example implementation. The device components 1300 comprise a communication bus 1302 for interconnecting other device components directly or indirectly. The other device components include one or more communication components 1304 communicating with other entities via a wired or wireless network, one or more processors 1306, and one or more memory components 1308. The communication component 1304 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation. The comm uni cat on component 1304 may utilize wired or wireless technology for communication.
[99] The processor or processors 1306 may execute code and process data received from other components of the device components 1300, such as information received at the communication component 1304 or stored at the memory component 1308. Each application includes executable code to provide specific functionality for the processor 1306 and/or remaining components of the management device 140. Examples of applications executable by the processor 1306 include, but are not limited to, a collection or update module 1310 and a recommendation module 1312. The collection and/or update module 1310 operates in conjunction with one or more input components 1318 to collect participant preferences, location preferences, and time preferences of group members from remote devices. The recommendation module 1312 of the processor 1306 determines event participants based on the participant preferences, event locations based on the location preferences, and event times based on the time preferences. The time preferences include calendar information for the event participants.
[100] Data stored at the memory component 1308 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140. Examples of data associated with the management device 140 and stored by the memory component 1308 may include, but are not limited to, preference data 1314 and determined data 1316. The preference data 1314 includes participant preferences, location preferences, and time preferences of group members. The determined data 1316 includes event participants, event locations, and event times.
[101] The device components 1300 may include one or more input components 1318 and one or more output components 1320. The input components 1318 and output components 1320 of the device components 1300 may include one or more visual, audio, mechanical, and/or other components. For some embodiments, the input and output components 1318, 1320 may include a user interface 1322 for interaction with a user of the device. The user interface 1322 may include a combination of hardware and software to provide a user with a desired user experience. It is to be understood that the communication component 1304 may receive input from a remote device and, in such case, may be considered as an input component 1318. Likewise, the communication component 1304 may provide output to a remote device and, thus, may be considered as an output component 1320.
[102] The input component 1318 collects participant preferences, location preferences, and time preferences of group members at a management device 140 from remote devices. The group members are associated with a particular group entity, and each remote device is associated with at least one member of the plurality of group members. Examples of remote devices include, but are not limited to, the remote devices 150, 160, 170 represented by FIG. 1. The output component 1320 provides a recommendation identifying the event participants, the event locations, and the event times to acceptance devices. Each acceptance device is associated with a particular member of the group members.
[103] It is to be understood that FIG. 13 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 13, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
[104] Referring to FIG. 14, there is shown a flow diagram representing yet another operation 1400 for determining recommendations, in an example implementation, which is operable to employ techniques described herein. The operation 1400 is a method of a group scheduler for managing attendance recommendations. The operation 1400 of the management device 140 may be activated by receiving (1402) an event activation, which may be a manual device activation or an automatic system activation. For some embodiments, the management device 140 may receive an activation signal from an acceptance device 150, 160, 170 in response to a user activation at a user interface of the device. For example, the activation signal may request a connection opportunity for a small group of members at a particular time period, such as a lunch buddy for next week. As another example, the activation signal may request a connection opportunity for a group of members, such as identifying possible time periods for a large in-person meeting. For some embodiments, the management device 140 may create the activation signal automatically in response to a triggered event such as a periodic activation of the group scheduler or detection of a need for member connections.
[105] The operation 1400 of the management device 140 may collect (1404) participant preferences (1406), location preferences (1408), and time preferences (1410) of group members at an input component 1318 from remote devices 150, 160, 170. For some embodiments, the participant preferences, location preferences, and time preferences may be collected (1404) in response to receiving (1402) an activation signal from the acceptance device 150, 160, 170 or the management device 140. The group members may be associated with a particular group entity. For some embodiments, the group members may be concurrently employed by the particular group entity, i.e., the group members are co-workers or colleagues at a particular company. Each remote device 150, 160, 170 may be associated with one or more members of the group members, such as laptops or mobile devices of the members.
[106] For some embodiments, the participant preferences include a conversation topic substantially common with the group members. For certain embodiments, the conversation topic may not be associated with the particular group entity. Examples of these non-entity topics include, for are not limited to, activities not associated with work or employment. For example, the conversation topic may be one or more of a media presentation, an entertainment entity, or a non-work activity. Examples of a media presentation include, but are not limited to, movies, television, music, and other types of shows involving media. Examples of an entertainment entity include, but are not limited to, performers, broadcasters, athletes, sports teams, celebrities, and other people involved in the entertainment industry. Examples of a non-work activity include, but are not limited to, cooking, fitness, sports, travel, education, and other hobbies that people may have in common.
[107] For some embodiments, the participant preferences may include the activity types for potential meetings. Examples of activity types includes, but are not limited to, physical activities (e.g., laser tag, mini golf, or tree top adventures), creative activities (e.g., cooking or painting), collaborative exercise (e.g., solving puzzles & riddles or escape rooms), or learning activities (e.g., joined training, speaker event, or site visit).
[108] For some embodiments, the location preferences may include a virtual meeting mode or an in-person meeting mode. For some embodiments, the location preferences may include resource preferences of the group members. For example, the location preferences may include one or more of available food, proximity to the particular group entity, location environment, or presentation equipment. Examples of food preference include, but are not limited to vegetarian, vegan, gluten free, cultural (Asian, Central American, European, etc.), seafood, steakhouse, and the like. Examples of proximity preference include, but are not limited to, location in proximity to a certain place of interest such as an office, a meeting place, or place of convenient transportation. Examples of location environment include, but are not limited to an outdoor area to experience a surrounding environment (e.g., a park) or an indoor area to shelter from the surrounding area. Examples of presentation equipment include, but are not limited to audio equipment, video equipment, or multimedia equipment which may be associated with a conference room, a coworking space, office space, or other types of areas for productivity. For other embodiments, indirect participant information may help to identify one or more location preferences. Examples of the indirect participant information includes, but are not limited to, heads down work, happy hours, lunch with coworkers, walk and talk meetings, team meetings, and other reasons why participants come to the office.
[109] As stated above, the time preferences include calendar information for the availability of event participants. For some embodiments, the time preference includes information about group members with whom there is the most interaction and/or group members who are within the same organization of a particular group entity (for example, as identified by an org chart). For some embodiments, the time preference or time preferences include one or more categories of time. Examples of a category of time include, but are not limited to, days of the week, normal work hours, before work, after work (i.e., happy hours), lunch periods, and the like. An additional example of a category of time includes hybrid work arrangements of group members, such as mostly remote days, mostly in-person days, mixture of in-person and remote days, or other indications of attendance at a work location. For some embodiments, the time preferences may include a frequency of in-person attendance at one or more locations, such as weekly, monthly, or quarterly.
[110] The processor 1306 of the management device 140 determines (1412) event participants, event locations, and event times in response to collecting (1404) data of the potential participants. In particular, the processor 1306 determines (1416) the event participants based on the participant preferences. The processor 1306 also determines (1416) one or more event locations based on the location preferences. The processor 1306 further determines (1418) one or more event times based on the time preferences.
[111] The output component 1320 of the management device 140, such as the communication component 1304, provides (1420) a recommendation identifying the event participants, the event location(s), and the event time(s) to an acceptance device 150, 160, 170 in response to determining (1416-1418) the event participants, locations, and times. The acceptance device 150, 160, 170 is associated with a particular member of the group members. Examples of the acceptance device include, but are not limited to, one or more of the remote devices 150, 160, 170.
[112] The input component 1318 of the management device 140, such as the communication component 1304, detects (1422) whether any feedback is received from an acceptance device, such as remote device 14, 150, 170. For example, the input component 1318 of the management device 140 may detect (1422) whether the provided recommendation (1420) has been accepted by an acceptance device 150, 160, 170. Feedback (1422) may be received in response to a query provided to the acceptance device 150, 160, 170 relating to one or more preferences of the participant associated with the acceptance device or, in the alternative, feedback may be received without any type of query provided by the management device 140. Feedback (1422) may be in the form of a user selection among multiple choices, a user submission of information (such as text, voice, motion, and the like), or a combination of selection and choice. In addition, feedback (1422) includes lack of feedback which may indicate a non-positive (i.e., less than positive) reaction to the recommendation.
[113] For some embodiments, the processors updates (1424) the calendars of the group members in response to acceptance (1422) of the recommendation. The processor updates (1424) the calendars by updating them at the management device 140 or sending update signals to one or more remote devices 150, 160, 170.
[114] Whether the operation 1400 receives (1422) feedback, does not receive (1422) feedback, and/or updates (1424) the calendars, the operation may update (1426) the data of the participants. In particular, the operation 1400 may update (1428) the participant preferences, update (1430) the location preferences, and/or update (1432) the time preferences of the acceptance device. For example, the operation 1400 may update (1428) the participant preferences to add or raise the rank one or more other participants identified by the recommendation in response to receiving (1422) positive feedback about recommendation. As another example, the operation 1400 may update (1428) the participant preferences to delete or lower the rank of one or more other participants identified by the recommendation in response to receiving (1422) negative feedback about recommendation. For some embodiments, the management device 14 may associate a ranking or score with each preference that is updated (1426).
[115] Thereafter or otherwise, the operation may continue to perform operations of the management device 140, such as awaiting another event activation (1402) or some other operation of the device.
[116] Referring to FIG. 15, there is shown a seventh graphical view 1500 of a user interface of a remote device representing, by example, management of recommendation information and feedback information. The graphical view 1500 may include one or more icons 1504, 1506, 1508, 1510 representing the system, the services, and/or the potential participants as well as highlighting or partitioning sections of the graphical view. The graphical view 1500 may include group portions 1512 that are directed to multiple potential participants of a conversation and individual portions 1514 that are directed to an individual potential participant, such as the acceptance device. For each group portion 1512, the services 1516 and/or potential participants 1518, 1520, 1522, 1524 of the conversation may be identified. The graphical view 1500 may include informative information 1526 to the acceptance device about notifications and other context of the conversation.
[117] Within a conversation of the group portion 1512, the graphical view 1500 may identify a recommendation 1528 for the potential participants. The recommendation 1528 may identify an opportunity for multiple potential participants 1520, 1522 to meetup based on one or more similarities (i.e., match) of their preferences. The recommendation 1528 may also include added information 1530 about how their preferences are considered to be similar, such as a match of location preferences of the potential participants. For some embodiments, the recommendation 1528 may include one or more suggestions 1532 for how, when, or where the potential participants may meet based on the data of the potential participants (i.e., participant, location, and/or time preferences). The recommendation 1528 may provide the potential participants with information about the next step for the meetup. For some embodiments, the recommendation 1528 may suggest a particular potential participant to send a calendar invite to all potential participants in response to the recommendation. For some embodiments, the recommendation 1528 may provide suggested locations and/or times for the meetup based on the data of the potential participants and their calendar information. For some embodiments, the managing device 140 may send automatically one or more calendar invites to all potential participants based on the data of the potential participants and their calendar information. The recommendation 1528 may further include background information 1536 about the conversation so that the potential participants may understand how and/or why they are receiving the recommendation.
[118] As described above, the graphical view 1500 may include an individual portion 1514 that is directed to an individual potential participant, such as the acceptance device. The graphical view 1500 may provide a query 1538 to a user of the acceptance device to solicit feedback relating to the recommendation 1528. Feedback may be in the form of a user selection among multiple choices 1540, 1542, a user submission of information (such as text, voice, motion, and the like), or a combination of selection and choice. In addition, lack of any feedback or response may be considered as feedback since it may indicate a non-positive (i.e., less than positive) reaction to the recommendation. The feedback may be used to update the data of the participants, such as participant preferences, location preferences, and/or time preferences of the acceptance device, such as the remote devices 150, 160, 170.
[119] Referring to FIG. 16, there is shown a block diagram 1600 of various components of the remote or management device 140, 150, 160, 170 in yet another example implementation. The device components 1600 comprise a communication bus 1602 for interconnecting other device components directly or indirectly. The other device components include one or more communication components 1604 communicating with other entities via a wired or wireless network, one or more processors 1606, and one or more memory components 1608. The communication component 1604 communicates (i.e., receives and/or transmits) data associated with one or more devices of the system 100, such as a mobile device or an external workstation. The communication component 1604 may utilize wired or wireless technology for communication.
[120] The processor or processors 1606 may execute code and process data received from other components of the device components 1600, such as information received at the communication component 1604 or stored at the memory component 1608. Each application includes executable code to provide specific functionality for the processor 1606 and/or remaining components of the management device 140. Examples of applications executable by the processor 1606 include, but are not limited to, a collection or update module 1610 and a recommendation module 1612. The collection and/or update module 1610 operates in conjunction with one or more input components 1618 to collect interest preference data of group members from remote devices. The recommendation module 1612 of the processor 1606 determines meetup recommendations, including the conversation starter, to provide to one or more acceptance devices.
[121] Data stored at the memory component 1608 is information that may be referenced and/or manipulated by an operating system or application for performing functions of the management device 140. Examples of data associated with the management device 140 and stored by the memory component 1608 may include, but are not limited to, preference data 1614 and determined data 1616. The preference data 1614 includes interest preference data of group members from remote devices. The determined data 1616 includes meetup recommendations, including the conversation starter, to provide to one or more acceptance devices.
[122] The device components 1600 may include one or more input components 1618 and one or more output components 1620. The input components 1618 and output components 1620 of the device components 1600 may include one or more visual, audio, mechanical, and/or other components. For some embodiments, the input and output components 1618, 1620 may include a user interface 1622 for interaction with a user of the device. The user interface 1622 may include a combination of hardware and software to provide a user with a desired user experience. It is to be understood that the communication component 1604 may receive input from a remote device and, in such case, may be considered as an input component 1618. Likewise, the communication component 1604 may provide output to a remote device and, thus, may be considered as an output component 1620. An example of a remote device is an acceptance device that receive and utilizes meetup recommendations. [123] It is to be understood that FIG. 16 is provided for illustrative purposes only to represent examples of the remote or management device 140, 150, 160, 170 and is not intended to be a complete diagram of the various components that may be utilized by the system 100. Therefore, the management device may include various other components not shown in FIG. 16, may include a combination of two or more components, or a division of a particular component into two or more separate components, and still be within the scope of the present invention.
[124] Referring to FIG. 17, there is shown an eighth graphical view of a user interface 1700 of a remote device representing, by example, management of recommendation information and entry of user preference information. The system 100 generates meetup recommendations and performs related operations which provide personalized conversation starters for the meetup recommendations. The user interface 1700 includes a messaging section 1720 for organizational communications. The messaging section 1720 may include channel information 1722 relevant to multiple group members and meetup recommendation 1724 directed privately to a specific user, i.e., the primary member of the remote device or member account. The meetup recommendation 1724 is only visible at a device associated with the member account shown by the messaging section 1720. The meetup recommendation 1724 of the messaging section 1720 includes member location information 1726 and/or member interest information 1728, 1730 associated with the member account. The user of the device is able to enter information in open text format about his or her location and/or interests in his or her preferences profile. The entered information may be available at a home page, as well as at onboarding and in one or more engagement messages, of the user interface 1700.
[125] The user may select one or more editing buttons 1732, 1734, 1736 to provide create or edit the member location information 1726 and/or the member interest information 1728, 1730. For example, the user may select an editing button 1734 corresponding to personal member interest information 1728 to view an editing window 1740 for the personal interests. The user may enter or edit the personal member interest information 1728 in open text field 1742 using natural language. Likewise, the user may select an editing button 1736 corresponding to professional member interest information 1730 to view an editing window 1760 for the professional interests. The user may enter or edit the professional member interest information 1730 in open text field 1762, 1764 using natural language. For some embodiments, the editing window 1760 for the professional interests may include a learning topic field 1762 and/or a teaching topic field 1764.
[126] The member interest information may include personal interests 1728, professional interests 1730, or both. Personal interests 1728 are associated with non-work activities preferred by the member. Examples of personal interests 1728 include, but are not limited to hobbies outside of work, favorite foods, favorite media shows, outdoor activities, and the like. Professional interests 1730 are associated with work activities preferred by the member, such as career passions of the member. Examples of professional interests 1730 include, but are not limited to learning topics and teaching topics. Learning topics are topics that the member is interested in learning and enhancing his or her understanding, with a focus on professional topics. An example of a learning topic is, “I would like to learn more about political science or how to communicate better”. Teaching topics are topics that the member may help others to learn, with a focus on professional topics. An example of a teaching topic is, “I can help coworkers that would like to learn about growth marketing as I am skilled in this area with many years of experience”.
[127] Referring to FIG. 18, there is shown a ninth graphical view of a user interface 1800 of a remote device representing, by example, management of recommendation information including secret tips and conversation starters. The user interface 1800 includes a messaging section 1820 for organizational communications. The messaging section 1820 may include channel information 1822 relevant to multiple group members and meetup recommendation 1824 directed privately to a specific user. The channel information 1822 may include match information about one or more other members who have matching interest preferences with the current member, i.e., the member associated with the remote device and/or member account associated with the remote device.
[128] The meetup recommendation 1824 of the messaging section 1820 includes other member information 1826 and/or conversation starters 1828 associated with the member account. When receiving meeting recommendations, a device associated with a member account may receive the other member information 1826 and/or the conversation starters 1828. The other member information 1826 are one or more personalized “secret tips” 1830 highlighting interests of other members matched by the system 100 with the member associated with the device. The other member information 1826 may be utilized to facilitate the initiation of conversations or communications during a meetup between these members.
[129] The meetup recommendation 1824 of the messaging section 1820 of a first member may include one or more conversation starters 1832 for one or more second members. The system 100, or a processor thereof, may contact a remote device or server to generate these conversation starters 1832. For some embodiments, the system 100 may contact a remote server to generate the conversation starters via a natural language processing tool of an artificial intelligence technology. An example of a natural language processing tool includes, but is not limited to, InstructGPT Large Language Model of OpenAI (in San Francisco, CA, USA) to generate the conversation starters related to the coworker match’s interest preferences. For example, the system 100 may indicate that Julia has a personal interest preference “I love movies and music”. When contacting the processing tool to get a conversation starter related to that preference, one of the processing tool outputs may be “What’s your favorite movie of all time?” An output component of the system 100 displays the output at the remote device under the section for the conversation starters 1828 of the meetup recommendation messages.
[130] Referring to FIG. 19, there is shown a tenth graphical view of a user interface 1900 of a remote device representing, by example, management of recommendation information including interest preferences and conversation starters. The user interface 1900 includes a messaging section 1920 for organizational communications. The messaging section 1920 may include meetup recommendation 1922 relevant to multiple group members or, in the alternative or in addition to, meetup recommendation directed privately to a specific user.
[131] The meetup recommendation 1922 includes match information 1924 about one or more other members who have matching interest preferences with the current member, common member interest information 1926, and/or conversation starters 1928 associated with the member account. Meetup recommendations may include a summary of personal and/or professional interests that other members, matched to the current member by the system 100, have provided in their preference profile. For example, in their preference profile, their match might have entered “I love to hike, listen to music, and watch movies.” for their personal interest preference. The system 100 may summarize the interests into more concise phrases, extract generalized categories of interests, or both, based on the open text statements of members in the system 100. For example, if a member enters “I like to hike, listen to music, and watch movies”, then the system 100 may extra a summarized statement (such as “outdoor activities, music, and movies”) and/or a list of generalized interest categories (such as outdoor activities, music, movies).
[132] For some embodiments, the system 100 may contact a remote server to generate the conversation starters via a natural language processing tool of an artificial intelligence technology. The system may contact a processing tool in order to summarize those interests into more concise sentences as well as extract generalized categories of interests from the open text preference statement of one or more members. For example, if the enduser entered “I like to hike, listen to music, and watch movies”, the system 100 might be able to extract the summarized statement and/or list of generalized categories by sending this statement to the processing tool. The Summarized Statement may be used to provide a better user experience in the conversation starters that the system 100 provides to members within meetup recommendations. The list of generalized categories may be indexed by the system 100 for subsequent use in pairing algorithms, common interest conversation starters generation, and the like. The system 100 may utilize the generalized interest categories, as indexed, for each member to include with meetup recommendations common interests between the members and his/her match and provide personalized conversation starters related to common interests shared by both or multiple members.
[133] In addition, the system 100 generates a match compatibility rank between a particular member of the group members and other members of the group members. The match compatibility rank is based on a quantity of common interests between the particular member and each other member. It is important to note that the match compatibility ranking isn’t based only on shared interests. Match compatibility ranking may also be based on work location preferences of the members. For instance, if members share a primary or secondary work location preference, they may be designated a higher match compatibility score and increase the chances that the system’s pairing algorithm matches them together for a meetup recommendation. Thus, the match compatibility rank may be based on a quantity of common interests and proximity of location preference between the particular member and each other member.
[134] The meetup recommendations may also include features for rematching and/or diverse pairing. A meetup member may be matched with another member of the group members having the highest match compatibility ranking between them for multiple consecutive pairing cycles. To connect with a greater number of members, the rematch feature allows members to receive a new pairing on-demand after receiving a member meetup match. In addition to facilitating matches that better suit member needs for meeting up, the rematch feature may also provide substantial information to the system 100 about the member preferences, which the system will infer from a rematch request. A member requesting a rematch or a new match may be indicating that there is a negative sentiment towards the usefulness of the last member match received. With this feedback and all of the information related to the match, the system 100 may be able to infer some preferences for the member. For example, if a first member requests a rematch after receiving a match with a certain second member many times, the system 100 may infer that the first member has a preference not to meet with this particular second member. Another example may be that by not requesting a rematch after receiving a match with the second member, the system 100 may infer that the first member has positive compatibility with this particular second member. The system can then index all preferences for each member and other variables that went into generating the meetup recommendation and utilize it in vector-based compatibility ranking for its meetup pairing algorithm.
[135] By requesting a rematch, the system 100 may infer that the previous match was not what the first member desired. The system 100 may, thus, index the variables and preferences that led to, and are part of, that match in order to further improve their compatibility rankings for every member. In addition, the system 100 may also ensure diversity for pairing by indexing the history of pairings and inserting some randomness in pairings to ensure that, not only the most compatible coworkers meet, but also members meet a wide range of other members through meetups.
[136] The meetup recommendations may also include features for mentorship and/or skip-level pairings. The system 100 may determine the best mentor(s)/mentee(s) for their career passions and professional interests. Similar to the common interest pairings, the system 100 utilizes indexed generalized interest categories for learnings topics extracted from the preferences of members. Also, a natural language processing tool of artificial intelligence technology may be used to compute match compatibility ranking for each member in the group members. For some embodiments, the system 100 may simply target mentorship pairings specifically. For some embodiments, the system 100 may expand on the type of text inputs collected from members in their preferences in order to obtain more specific data on their professional interests. Then, using these professional preferences inputs and categorizing them in generalized categories for matching, the system 100 may make mentor-mentee pairings for meetup recommendations.
Accordingly, the system 100 may facilitate a search for a mentor from which the member may learn from within a topic of interest, or find someone that may be mentored on a topic the member could help others to learn. Mentorship pairing for a member group may be based on preferences from the members to rank the highest compatibility mentors and mentees for matches. Similarly, the system 100 may generate skip-level meetup recommendations for similar connections within the member group, such as a company.
[137] The meetup recommendations may further include features for inter-group and intra-group pairings. In collecting interest preference data from remote devices, an input component may collect member preferences relating to which other members they would like to meet. The system 100 may increase the precision in making a quality meetup match for them, particularly within or between departments, teams, or any sort of groupings that could be used for such matches. For some embodiments, using these groupings, the system 100 may request members to input their preferences about meeting members in certain groups. It could be a preference, in general, to meet people outside their groups or a more specific preference about their interest to meet members in specific groups. For example, a product manager may like to meet with members in the marketing department group of a company. The additional input received at an input component may be used to determine the match compatibility ranking for each second member for the first member and make the highest quality matches as part of the meetup recommendation.
[138] The system 100 may collect preferences from a first member on whether or not he or she would like to meet with certain second members as opposed to meeting individuals that are part of certain groups. Similar to how the group preferences may be integrated into the pairing algorithm, individual member preferences may be integrated into a match compatibility ranking for each member in the organization, thus making optimized meetup matches of high quality for the member based on their preferences.
[139] Referring to FIG. 20, there is shown a flow diagram representing still another operation for determining recommendations, in an example implementation, that is operable to employ techniques described herein. Interest preference data of group members is collected (2010) by an input component from remote devices. The group members are associated with a particular group entity, and each remote device of the remote devices is associated with one or more members of the group members. The interest preference data that is collected may include personal interest information (2012), professional interest information (2014), or a combination of personal and professional interest information. For some embodiments, the interest preference data that is collected includes professional interest information about a learning topic, a teaching topic, or both.
[140] In response to collecting (2010) interest information, a processor determines (2020) a meetup recommendation for member match based on the interest preference data of the group members. In determining (2020) the meetup recommendation, a conversation starter is generated (2022) based on the interest preference data. For example, generating the conversation starter may include creating (2024) an interrogative phrase associated with a common interest shared by two or more members of the group members. As another example, generating the conversation starter may include generating (2026) the conversation starter via a natural language processing tool of an artificial intelligence technology.
[141] The determination (2020) of a meeting recommendation may include one or more features to enhance useful pairings of members. For some embodiments, common interest information may be identified (2028) from the interest preference data relating to common interests of two or more members of the group members. For some embodiments, the meetup recommendation may include a personal interest associated with a non-work activity and a professional interest associated with a work activity. For some embodiments, a match compatibility rank between a particular member of the group members and other members of the plurality of group members may be generated (2030). The match compatibility rank may be based on a quantity of common interests between the particular member and each other member. For some embodiments, the match compatibility rank may be based on a quantity of common interests and proximity of location preference between the particular member and each other member. For some embodiments, the meetup recommendation may be determined (2020) by inferring (2032) a negative-compatibility preference for two or more particular members of the group members based on receiving a request for rematching the two or more particular members and/or inferring (2032) a positive-compatibility preference for the two or more particular members of the group members based on a lack of receiving any request for rematching the two or more particular members. For some embodiments, a mentorship pairing between two or more members of the group members may be generated (2034) based on the professional interest information. For some embodiments, the meetup recommendation for participant match may be determined (2036) based on an inter-group preference or an intra-group preference of the interest preference data of the group members.
[142] In response to determining (2020) a meetup recommendation, the meetup recommendation including the conversation starter may be provided (2040) by an output component to an acceptance device. The acceptance device is associated with a particular member of the group members.
[143] Those skilled in the art will recognize that, for simplicity and clarity, the full structure and operation of all data processing systems suitable for use with the present disclosure are not being depicted or described herein. Also, none of the various features or processes described herein should be considered essential to any or all embodiments, except as described herein. Various features may be omitted or duplicated in various embodiments. Various processes described may be omitted, repeated, performed sequentially, concurrently, or in a different order. Various features and processes described herein can be combined in still other embodiments as may be described in the claims.
[144] It is important to note that while the disclosure includes a description in the context of a fully functional system, those skilled in the art will appreciate that at least portions of the mechanism of the present disclosure are capable of being distributed in the form of instructions contained within a machine-usable, computer-usable, or computer- readable medium in any of a variety of forms, and that the present disclosure applies equally regardless of the particular type of instruction or signal bearing medium or storage medium utilized to actually carry out the distribution. Examples of machine usable/readable or computer usable/readable mediums include nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), and user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs).
[145] Although an example embodiment of the present disclosure has been described in detail, those skilled in the art will understand that various changes, substitutions, variations, and improvements disclosed herein may be made without departing from the spirit and scope of the disclosure in its broadest form.

Claims

CLAIMS What is claimed is:
1. A system of a group scheduler for managing attendance recommendations comprising: a memory component configured to collect a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member, a second member, and a third member; and a processor configured to generate a first group preference of the first member in response to collecting the plurality of attendance schedules, index the first group preference of the first member based on a second group preference of the second member, and update the first group preference of the first member to include the third member, wherein the first group preference includes at least one member of the plurality of group members being followed by the first member, the first group preference including the second member, and wherein the second group preference includes at least one member of the plurality of group members being followed by the second member, the second group preference including the third member.
2. The system as described in claim 1, further comprising a communication component and a remote or management device associated with the first member, wherein the communication component provides the plurality of group members to the remote or management device and receives a user selection from the remote or management device to add the second member to the first group preference of the first member.
3. The system as described in claim 1, wherein the processor generates the second group preference of the second member before indexing the first group preference of the first member.
4. The system as described in claim 1, further comprising a communication component and a remote or management device associated with the first member, wherein the communication component provides a recommendation to the remote or management device to adjust to the first group preference of the first member in response to indexing the group preference and receives an acceptance of the recommendation from the remote or management device in response to providing the recommendation.
5. The system as described in claim 1, further comprising a recommendation engine of the group scheduler, a communication component, and a remote or management device associated with the first member, wherein: the recommendation engine generates a recommendation, in response to indexing the first group preference, to adjust to the first group preference of the first member; the communication component provides the recommendation to the remote or management device; and the processor updates the recommendation engine in response to the communication component receiving a response to the recommendation from the remote or management device.
6. A method of a group scheduler for managing attendance recommendations, the method comprising: collecting a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member, a second member, and a third member; generating a first group preference of the first member in response to collecting the plurality of attendance schedules, the first group preference including at least one member of the plurality of group members being followed by the first member, the first group preference including the second member; indexing the first group preference of the first member based on a second group preference of the second member, the second group preference including at least one member of the plurality of group members being followed by the second member, the second group preference including the third member; and updating the first group preference of the first member to include the third member.
7. The method as described in claim 6, wherein generating the first group preference of the first member comprises: providing the plurality of group members to a remote or management device associated with the first member; and receiving a user selection from the remote or management device to add the second member to the first group preference of the first member.
8. The method as described in claim 6, further comprising: generating the second group preference of the second member before indexing the first group preference of the first member.
9. The method as described in claim 6, further comprising: providing a recommendation to a remote or management device associated with the first member to adjust to the first group preference of the first member in response to indexing the group preference; and receiving an acceptance of the recommendation from the remote or management device in response to providing the recommendation.
10. The method as described in claim 6, further comprising: generating a recommendation by a recommendation engine of the group scheduler, in response to indexing the first group preference, to adjust to the first group preference of the first member; providing the recommendation to a remote or management device associated with the first member; and updating the recommendation engine in response to receiving a response to the recommendation from the remote or management device.
11. A system of a group scheduler for managing attendance recommendations comprising: a memory component configured to collect a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member and a second member; and a processor configured to generate a group preference of the first member in response to collecting the plurality of attendance schedules, index the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member, and update the attendance schedule of the first member for the future time period by changing the first location status of the first member to correspond to the second location status of the second member, wherein the group preference includes at least one member of the plurality of group members being followed by the first member, the group preference including the second member, and wherein the first location status is one of a work location status and a non-work location status and the second location status is the other of the work location status and the non-work location status.
12. The system as described in claim 11, further comprising a communication component and a remote or management device associated with the first member, wherein the communication component provides the plurality of group members to the remote or management device and receives a user selection from the remote or management device to add the second member to the group preference of the first member.
13. The system as described in claim 11, further comprising a remote or management device associated with the first member, wherein the system provides a notification to the remote or management device indicating that the second location status of the second member is different from the first location status of the first member for the future time period.
14. The system as described in claim 11, further comprising a communication component and a remote or management device associated with the first member, wherein the communication component provides a recommendation to the remote or management device to adjust to the attendance schedule of the first member for the future time period in response to indexing the group preference and receives an acceptance of the recommendation from the remote or management device in response to providing the recommendation.
15. The system as described in claim 11, further comprising a recommendation engine of the group scheduler, a communication component, and a remote or management device associated with the first member, wherein: the recommendation engine generates a recommendation, in response to indexing the group preference, to adjust to the attendance schedule of the first member for the future time period; the communication component provides the recommendation to the remote or management device; and the processor updates the recommendation engine in response to the communication component receiving a response to the recommendation from the remote or management device.
16. A method of a group scheduler for managing attendance recommendations, the method comprising: collecting a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member and a second member; generating a group preference of the first member in response to collecting the plurality of attendance schedules, the group preference including at least one member of the plurality of group members being followed by the first member, the group preference including the second member; indexing the group preference of the first member based on a difference between a first location status of the first member and a second location status of the second member for a future time period of an attendance schedule of the first member, wherein the first location status is one of a work location status and a non-work location status and the second location status is the other of the work location status and the non-work location status; and updating the attendance schedule of the first member for the future time period by changing the first location status of the first member to correspond to the second location status of the second member.
17. The method as described in claim 16, wherein generating the group preference of the first member comprises: providing the plurality of group members to a remote or management device associated with the first member; and receiving a user selection from the remote or management device to add the second member to the group preference of the first member.
18. The method as described in claim 16, further comprising: providing a notification to a remote or management device associated with the first member indicating that the second location status of the second member is different from the first location status of the first member for the future time period.
19. The method as described in claim 16, further comprising: providing a recommendation to a remote or management device associated with the first member to adjust to the attendance schedule of the first member for the future time period in response to indexing the group preference; and receiving an acceptance of the recommendation from the remote or management device in response to providing the recommendation.
20. The method as described in claim 16, further comprising: generating a recommendation by a recommendation engine of the group scheduler, in response to indexing the group preference, to adjust to the attendance schedule of the first member for the future time period; providing the recommendation to a remote or management device associated with the first member; and updating the recommendation engine in response to receiving a response to the recommendation from the remote or management device.
21. A system of a group scheduler for managing attendance recommendations comprising: a memory component configured to collect a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member and a second member, the second member being followed by the first member; and a processor configured to generate a weighted preference of the plurality of group members in response to collecting the plurality of attendance schedules and determine a schedule for a second time period based on the weighted preference of the plurality of group members, the weighted preference being generated based on a first time period of work in office of the first and second members, and the second time period being greater than the first time period.
22. The system as described in claim 21, wherein the second time period is a particular week, and the first time period is a day of the particular week.
23. The system as described in claim 21, wherein the processor identifies frequency of each first time period associated with work in office for the plurality of group members; and identifies one or more first time periods corresponding to a highest level of the frequency of the first time period associated with work in office for the plurality of group members.
24. The system as described in claim 21, wherein the first time period of work in office of the first member is given higher priority than the first time period of work in office of the second member.
25. The system as described in claim 21, wherein the processor updates a calendar application associated with a remote or management device of the first member for the second time period in accordance with the schedule.
26. The system as described in claim 21, wherein the plurality of attendance schedules of the plurality of group members includes a plurality of spaces, and each first time period of work in office is associated with a particular space of the plurality of spaces.
27. The system as described in claim 26, wherein the processor generates the weighted preference based on the plurality of spaces.
28. The system as described in claim 27, wherein the processor generates the weighted preference based on a common space of the plurality of spaces common to the first and second members for a first time period of work in office.
29. A method of a group scheduler for managing attendance recommendations, the method comprising: collecting a plurality of attendance schedules of a plurality of group members, the plurality of group members including a first member and a second member, the second member being followed by the first member; generating a weighted preference of the plurality of group members in response to collecting the plurality of attendance schedules, the weighted preference being generated based on a first time period of work in office of the first and second members; and determining a schedule for a second time period based on the weighted preference of the plurality of group members, the second time period being greater than the first time period.
30. The method as described in claim 29, wherein the second time period is a particular week, and the first time period is a day of the particular week.
31. The method as described in claim 29, wherein: generating the weighted preference of the plurality of group members includes identifying a frequency of each first time period associated with work in office for the plurality of group members; and determining the schedule for the second time period includes identifying one or more first time periods corresponding to a highest level of the frequency of the first time period associated with work in office for the plurality of group members.
32. The method as described in claim 29, wherein the first time period of work in office of the first member is given higher priority than the first time period of work in office of the second member.
33. The method as described in claim 29, further comprising updating a calendar application associated with a remote or management device of the first member for the second time period in accordance with the schedule.
34. The method as described in claim 29, wherein the plurality of attendance schedules of the plurality of group members includes a plurality of spaces, and each first time period of work in office is associated with a particular space of the plurality of spaces.
35. The method as described in claim 34, wherein generating the weighted preference of the plurality of group members includes generating the weighted preference based on the plurality of spaces.
36. The method as described in claim 35, wherein generating the weighted preference of the plurality of group members includes generating the weighted preference based on a common space of the plurality of spaces common to the first and second members for a first time period of work in office.
37. A system of a group scheduler for managing attendance recommendations comprising: an input component configured to collect participant preferences, location preferences, and time preferences of a plurality of group members at a management device from a plurality of remote devices, the plurality of group members being associated with a particular group entity, each remote device of the plurality of remote devices being associated with at least one member of the plurality of group members; a processor configured to determine a plurality of event participants based on the participant preferences, determine at least one event location based on the location preferences, and determine at least one event time based on the time preferences, the time preferences including calendar information for the plurality of event participants; and an output component configured to provide a recommendation identifying the plurality of event participants, the at least one event location, and the at least one event time to an acceptance device, the acceptance device being associated with a particular member of the plurality of group members.
38. The system as described in claim 37, wherein the input component collects the participant preferences, location preferences, and time preferences in response to receiving an activation signal from at least one of the acceptance device or the management device.
39. The system as described in claim 37, wherein the plurality of group members are concurrently employed by the particular group entity.
40. The system as described in claim 37, wherein the participant preferences include a conversation topic substantially similar among the plurality of group members and not associated with the particular group entity.
41. The system as described in claim 41, wherein the conversation topic is at least one of a group consisting of a media presentation, an entertainment entity, or a non-work activity.
42. The system as described in claim 37, wherein the location preferences include one of a virtual meeting mode or an in-person meeting mode.
43. The system as described in claim 37, wherein the location preferences include resource preferences of the plurality of group members.
44. The system as described in claim 44, wherein the location preferences include at least one of a group consisting of available food, proximity to the particular group entity, location environment, or presentation equipment.
45. The system as described in claim 37, wherein the at least one time preference includes at least one category of time.
46. The system as described in claim 37, wherein the processor updates at least one of the participant preferences, the location preferences, or the time preferences based on feedback received at the input component in response to providing the recommendation.
47. A method of a group scheduler for managing attendance recommendations, the method comprising: collecting participant preferences, location preferences, and time preferences of a plurality of group members at an input component from a plurality of remote devices, the plurality of group members being associated with a particular group entity, each remote device of the plurality of remote devices being associated with at least one member of the plurality of group members; determining, at a processor, a plurality of event participants based on the participant preferences; determining, at the processor, at least one event location based on the location preferences; and determining, at the processor, at least one event time based on the time preferences, the time preferences including calendar information for the plurality of event participants; and providing, by an output component, a recommendation identifying the plurality of event participants, the at least one event location, and the at least one event time to an acceptance device, the acceptance device being associated with a particular member of the plurality of group members.
48. The method as described in claim 47, wherein collecting the participant preferences, location preferences, and time preferences includes collecting the participant preferences, location preferences, and time preferences in response to receiving an activation signal from at least one of the acceptance device or the management device.
49. The method as described in claim 47, wherein the plurality of group members are concurrently employed by the particular group entity.
50. The method as described in claim 47, wherein the participant preferences include a conversation topic substantially similar among the plurality of group members and not associated with the particular group entity.
51. The method as described in claim 51, wherein the conversation topic is at least one of a group consisting of a media presentation, an entertainment entity, or a non-work activity.
52. The method as described in claim 47, wherein the location preferences include one of a virtual meeting mode or an in-person meeting mode.
53. The method as described in claim 47, wherein the location preferences include resource preferences of the plurality of group members.
54. The method as described in claim 54, wherein the location preferences include at least one of a group consisting of available food, proximity to the particular group entity, location environment, or presentation equipment.
55. The method as described in claim 47, wherein the at least one time preference includes at least one category of time.
56. The method as described in claim 47, further comprising updating at least one of the participant preferences, the location preferences, or the time preferences based on feedback received at the input component in response to providing the recommendation.
57. A system of a group scheduler for managing attendance recommendations comprising: an input component configured to collect interest preference data of a plurality of group members from a plurality of remote devices, the plurality of group members being associated with a particular group entity, each remote device of the plurality of remote devices being associated with at least one member of the plurality of group members; a processor configured to determine a meetup recommendation for member match based on the interest preference data of the plurality of group members, determining the meetup recommendation including generating a conversation starter based on the interest preference data; and an output component configured to provide the meetup recommendation including the conversation starter to an acceptance device, the acceptance device being associated with a particular member of the plurality of group members.
58. The system as described in claim 57, wherein the processor creates an interrogative phrase associated with a common interest shared by two or more members of the plurality of group members.
59. The system as described in claim 57, wherein the processor generates the conversation starter via a natural language processing tool of an artificial intelligence technology.
60. The system as described in claim 57, wherein the processor identifies common interest information from the interest preference data relating to common interests of two or more members of the plurality of group members.
61. The system as described in claim 57, wherein the meetup recommendation includes a personal interest associated with a non-work activity and a professional interest associated with a work activity.
62. The system as described in claim 57, wherein the processor generates a match compatibility rank between a particular member of the plurality of group members and other members of the plurality of group members, the match compatibility rank being based on a quantity of common interests between the particular member and each other member.
63. The system as described in claim 62, wherein the match compatibility rank is based on a quantity of common interests and proximity of location preference between the particular member and each other member.
64. The system as described in claim 57, wherein: the processor infers a negative-compatibility preference for two or more particular members of the plurality of group members based on receiving a request for rematching the two or more particular members; or the processor infers a positive-compatibility preference for the two or more particular members of the plurality of group members based on a lack of receiving any request for rematching the two or more particular members.
65. The system as described in claim 57, wherein: the input component collects professional interest information about at least one of a learning topic or a teaching topic; and the processor determines the meetup recommendation comprises generating a mentorship pairing between two or more members of the plurality of group members based on the professional interest information.
66. The system as described in claim 57, wherein the processor determines the meetup recommendation for participant match based on at least one of an inter-group preference or an intra-group preference of the interest preference data of the plurality of group members.
67. A method of a group scheduler for managing attendance recommendations, the method comprising: collecting, at an input component, interest preference data of a plurality of group members from a plurality of remote devices, the plurality of group members being associated with a particular group entity, each remote device of the plurality of remote devices being associated with at least one member of the plurality of group members; determining, at a processor, a meetup recommendation for member match based on the interest preference data of the plurality of group members, determining the meetup recommendation including generating a conversation starter based on the interest preference data; and providing, by an output component, the meetup recommendation including the conversation starter to an acceptance device, the acceptance device being associated with a particular member of the plurality of group members.
68. The method as described in claim 67, wherein generating the conversation starter includes creating an interrogative phrase associated with a common interest shared by two or more members of the plurality of group members.
69. The method as described in claim 67, wherein generating the conversation starter includes generating the conversation starter via a natural language processing tool of an artificial intelligence technology.
70. The method as described in claim 67, wherein determining the meetup recommendation includes identifying common interest information from the interest preference data relating to common interests of two or more members of the plurality of group members.
71. The method as described in claim 67, wherein the meetup recommendation includes a personal interest associated with a non-work activity and a professional interest associated with a work activity.
72. The method as described in claim 67, wherein determining the meetup recommendation includes generating a match compatibility rank between a particular member of the plurality of group members and other members of the plurality of group members, the match compatibility rank being based on a quantity of common interests between the particular member and each other member.
73. The method as described in claim *, wherein the match compatibility rank is based on a quantity of common interests and proximity of location preference between the particular member and each other member.
74. The method as described in claim 67, wherein determining the meetup recommendation comprises: inferring a negative-compatibility preference for two or more particular members of the plurality of group members based on receiving a request for rematching the two or more particular members; or inferring a positive-compatibility preference for the two or more particular members of the plurality of group members based on a lack of receiving any request for rematching the two or more particular members.
75. The method as described in claim 67, wherein: collecting the interest preference data includes collecting professional interest information about at least one of a learning topic or a teaching topic; and determining the meetup recommendation comprises generating a mentorship pairing between two or more members of the plurality of group members based on the professional interest information.
76. The method as described in claim 67, wherein determining the meetup recommendation includes determining the meetup recommendation for participant match based on at least one of an inter-group preference or an intra-group preference of the interest preference data of the plurality of group members.
PCT/US2023/029159 2022-08-19 2023-08-01 System and method of a group scheduler for managing attendance recommendations WO2024039523A1 (en)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US202263371897P 2022-08-19 2022-08-19
US63/371,897 2022-08-19
US202263383195P 2022-11-10 2022-11-10
US63/383,195 2022-11-10
US202363484053P 2023-02-09 2023-02-09
US63/484,053 2023-02-09
US202363491791P 2023-03-23 2023-03-23
US63/491,791 2023-03-23

Publications (1)

Publication Number Publication Date
WO2024039523A1 true WO2024039523A1 (en) 2024-02-22

Family

ID=87801004

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/029159 WO2024039523A1 (en) 2022-08-19 2023-08-01 System and method of a group scheduler for managing attendance recommendations

Country Status (1)

Country Link
WO (1) WO2024039523A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130219298A9 (en) * 2003-06-16 2013-08-22 Meetup, Inc. Web-Based Interactive Meeting Facility with Recommendations to Users
US20180174111A1 (en) * 2016-12-21 2018-06-21 International Business Machines Corporation Physical location scheduling management
US11157879B2 (en) * 2015-01-20 2021-10-26 NetSuite Inc. System and methods for facilitating scheduling of event or meeting
WO2021243565A1 (en) * 2020-06-02 2021-12-09 Citrix Systems, Inc. Dynamic recommendation engine

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130219298A9 (en) * 2003-06-16 2013-08-22 Meetup, Inc. Web-Based Interactive Meeting Facility with Recommendations to Users
US11157879B2 (en) * 2015-01-20 2021-10-26 NetSuite Inc. System and methods for facilitating scheduling of event or meeting
US20180174111A1 (en) * 2016-12-21 2018-06-21 International Business Machines Corporation Physical location scheduling management
WO2021243565A1 (en) * 2020-06-02 2021-12-09 Citrix Systems, Inc. Dynamic recommendation engine

Similar Documents

Publication Publication Date Title
US9965544B2 (en) Managing information about relationships in a social network via a social timeline
US20180129994A1 (en) Efficiency enhancements in task management applications
US20080301190A1 (en) Integrated system and method for implementing messaging, planning, and search functions in a mobile device
US8712820B2 (en) Mobile application for calendar sharing and scheduling
US9881281B2 (en) Collaborative event planning system
US20120259927A1 (en) System and Method for Processing Interactive Multimedia Messages
US20120259926A1 (en) System and Method for Generating and Transmitting Interactive Multimedia Messages
US20070094065A1 (en) Activity planning method and system
EP3724838A1 (en) Optimized scheduling of calendar events
US20220245520A1 (en) Systems and Methods for Generating and Providing Suggested Actions
US9424322B2 (en) Digital sticky note
CN108369695A (en) Determine the activity in response to profile
WO2024039523A1 (en) System and method of a group scheduler for managing attendance recommendations
JP2010191808A (en) Scheduling program, scheduling method, and scheduling device
WO2015195128A1 (en) Value-based organization
Ingvarsson Connecting and disconnecting: How digital nomads manage work in absence of a workplace
Friberg et al. Development of a Cooperation Framework for Cross-Functional Teams
US20130073278A1 (en) Methods and systems for compiling communication fragments and creating effective communication
Sandor Social Awareness Support for Cooperation-Design Experience and Theoretical Models
WO2013043897A1 (en) Methods and systems for compiling communication fragments and creating effective communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23761281

Country of ref document: EP

Kind code of ref document: A1