<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.3" xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Phys.</journal-id>
<journal-title>Frontiers in Physics</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Phys.</abbrev-journal-title>
<issn pub-type="epub">2296-424X</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">1129594</article-id>
<article-id pub-id-type="doi">10.3389/fphy.2023.1129594</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Physics</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Quantum annealing for the adjuster routing problem</article-title>
<alt-title alt-title-type="left-running-head">Mori and Furukawa</alt-title>
<alt-title alt-title-type="right-running-head">
<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3389/fphy.2023.1129594">10.3389/fphy.2023.1129594</ext-link>
</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Mori</surname>
<given-names>Naoya</given-names>
</name>
<xref ref-type="fn" rid="fn1">
<sup>&#x2020;</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/2068362/overview"/>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Furukawa</surname>
<given-names>Satoshi</given-names>
</name>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<xref ref-type="fn" rid="fn1">
<sup>&#x2020;</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/2078364/overview"/>
</contrib>
</contrib-group>
<aff>
<institution>Digital Promotion Department</institution>, <institution>Cognivision Inc.</institution>, <addr-line>Tokyo</addr-line>, <country>Japan</country>
</aff>
<author-notes>
<fn fn-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/716436/overview">Olaniyi Samuel Iyiola</ext-link>, Clarkson University, United States</p>
</fn>
<fn fn-type="edited-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1718900/overview">Vladimir Palyulin</ext-link>, Skolkovo Institute of Science and Technology, Russia</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/153032/overview">Saravana Prakash Thirumuruganandham</ext-link>, Universidad Technologica de Indoamerica, Ecuador</p>
</fn>
<corresp id="c001">&#x2a;Correspondence: Satoshi Furukawa, <email>satoshi_furukawa@cognivision.jp</email>
</corresp>
<fn fn-type="equal" id="fn1">
<label>
<sup>&#x2020;</sup>
</label>
<p>These authors have contributed equally to this work</p>
</fn>
<fn fn-type="other">
<p>This article was submitted to Statistical and Computational Physics, a section of the journal Frontiers in Physics</p>
</fn>
</author-notes>
<pub-date pub-type="epub">
<day>16</day>
<month>03</month>
<year>2023</year>
</pub-date>
<pub-date pub-type="collection">
<year>2023</year>
</pub-date>
<volume>11</volume>
<elocation-id>1129594</elocation-id>
<history>
<date date-type="received">
<day>23</day>
<month>12</month>
<year>2022</year>
</date>
<date date-type="accepted">
<day>23</day>
<month>02</month>
<year>2023</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2023 Mori and Furukawa.</copyright-statement>
<copyright-year>2023</copyright-year>
<copyright-holder>Mori and Furukawa</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p>
</license>
</permissions>
<abstract>
<p>In the event of a disaster such as an earthquake, insurance companies basically conduct on-site witnessing. Depending on the scale of the disaster, hundreds of adjusters are dispatched from each office to the affected buildings per day. In such cases, which adjusters will witness which buildings and in what order must be determined, and the route must be optimized to conduct efficient witnessing. In this study, we define this witnessing route decision as an optimization problem and propose the adjuster routing problem (ARP). The ARP can be viewed as an extension of the vehicle routing problem (VRP). We introduce constraints not to be considered in the usual VRP, such as adjuster-building matching and satisfying the desired time. The VRP is an NP-hard optimization problem and is considered difficult to solve on a classical computer. Therefore, we formulated various constraints in QUBO so that quantum annealing can be applied to the ARP. In addition, we conducted numerical experiments with D-Wave. The ARP is a real problem, and our research provides a new example of applications of quantum annealing to real-world problems.</p>
</abstract>
<kwd-group>
<kwd>quantum annealing</kwd>
<kwd>vehicle routing problem</kwd>
<kwd>clustering</kwd>
<kwd>traveling salesman problem</kwd>
<kwd>insurance company</kwd>
<kwd>disaster</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<title>1 Introduction</title>
<p>Discrete optimization problems appear in various fields. However, they are usually hard to solve. Many of these problems are in NP<xref ref-type="fn" rid="fn2">
<sup>1</sup>
</xref> [<xref ref-type="bibr" rid="B1">1</xref>], which is the class that classical computers may not solve them in polynomial time. In recent years, quantum annealing has been expected to solve these problems efficiently. Quantum annealing is a metaheuristic algorithm for solving discrete optimization problems, and its research has been initiated by Kadowaki and Nishimori [<xref ref-type="bibr" rid="B2">2</xref>]. In 2011, D-Wave Systems announced D-Wave [<xref ref-type="bibr" rid="B3">3</xref>], a machine that implements quantum annealing. Since then, many studies using quantum annealing have been published. When solving optimization problems by D-Wave, we first formulate problems in quadratic unconstrained binary optimization (QUBO) or Ising form. Then, quantum annealing is performed to search for the minimal value of QUBO. As the QUBO problems are NP-hard, almost all optimization problems can be formulated in QUBO. Therefore, quantum annealing applies to a very wide range of optimization problems, for example, scheduling [<xref ref-type="bibr" rid="B4">4</xref>,<xref ref-type="bibr" rid="B5">5</xref>], economics [<xref ref-type="bibr" rid="B6">6</xref>], machine learning [<xref ref-type="bibr" rid="B7">7</xref>&#x2013;<xref ref-type="bibr" rid="B9">9</xref>], computer vision [<xref ref-type="bibr" rid="B10">10</xref>,<xref ref-type="bibr" rid="B11">11</xref>], and quantum chemistry [<xref ref-type="bibr" rid="B12">12</xref>,<xref ref-type="bibr" rid="B13">13</xref>]. Moreover, it can be applied to real-world problems, such as control of automated guided vehicles in the factory without collision [<xref ref-type="bibr" rid="B14">14</xref>], traffic flow optimization to reduce traffic jam in Beijing [<xref ref-type="bibr" rid="B15">15</xref>], and item listing optimization in e-commerce websites [<xref ref-type="bibr" rid="B16">16</xref>].In this study, we propose an optimization problem called the adjuster routing problem (ARP) and propose a method to solve it using quantum annealing. The purpose of the ARP is to optimize the on-site witnessing route for insurers&#x2019; adjusters in the event of a disaster. Therefore, our research provides a new example of the application of quantum annealing to real-world problems.</p>
<sec id="s1-1">
<title>1.1 The adjuster routing problem</title>
<p>Here, we explain the details of the ARP. In the event of a disaster, such as an earthquake, an on-site witnessing will be conducted by adjusters dispatched by the insurance company to damaged buildings to confirm the damage. Particularly, in the case of large-scale disasters, a single insurance company has to assess tens of thousands of cases, requiring the dispatch of hundreds of personnel from the office each day. Therefore, an optimization of the route (i.e., minimizing the time required for witnessing, including travel time) is an extremely important problem from both a time and cost perspective. This problem can be regarded as the vehicle routing problem (VRP) [<xref ref-type="bibr" rid="B17">17</xref>] because multiple persons visit multiple locations and optimize their routes. In the setting where multiple vehicles visit multiple customers, VRP is the problem of finding a route that minimizes the sum of costs among the routes that satisfy the following constraints:<list list-type="simple">
<list-item>
<p>&#x2022; Each customer is visited exactly once by exactly one vehicle.</p>
</list-item>
<list-item>
<p>&#x2022; Every vehicle starts from the depot and back there.</p>
</list-item>
</list>
</p>
<p>Here, the interpretation of the cost as the time required for witnessing, the customer as the building to be witnessed, the vehicle as the adjuster, and depot as the dispatcher&#x2019;s office, respectively, VRP is basically consistent with the problem considered. However, there are some additional constraints in the ARP. First, the adjuster who can witness the building is determined according to the type of the building. The level of difficulty of witnessing a building depends on the type of building materials. Basically, three types of building materials (wood, steel, and reinforced concrete) are considered. Therefore, there are three types of buildings with three levels of difficulty: &#x201c;hard,&#x201d; &#x201c;normal,&#x201d; and &#x201c;easy.&#x201d; Adjusters cannot witness all of these types of buildings, and the buildings that can be witnessed are determined according to their capabilities. We refer to this capability as the adjuster&#x2019;s spec. Three types of specs are defined, &#x201c;high,&#x201d; &#x201c;middle,&#x201d; and &#x201c;low,&#x201d; from the highest to lowest. Buildings with a hard difficulty level can be witnessed by an adjuster with a high spec, and buildings with a normal difficulty level can be witnessed by an adjuster with a high or middle spec. In optimizing the route, we should consider the matching of the adjuster&#x2019;s spec and the difficulty level of witnessing the building. In addition, it is necessary to be able to start witnessing at the desired time submitted in advance by each building. This desired time is specified by time zone, for example, AM, PM1, and PM2, and each adjuster must be able to witness to satisfy the desired time. We also consider the time required for witnessing, which is determined according to the total area of the building (i.e., it increases in proportion to the area), and the total operating time includes the total travel time and the time required for witnessing at each building. Furthermore, even when all the aforementioned constraints are satisfied, if the number of buildings witnessed by one adjuster is large, the witnessing cannot be completed in time. Therefore, it is necessary to limit the number of buildings one adjuster can witness.</p>
<p>In summary, the ARP is the problem of finding a route that minimizes the total operating time among routes that satisfy the following constraints:<list list-type="simple">
<list-item>
<p>1. Every adjuster leaves from certain office and must return to the same office at the end of the last witnessing.</p>
</list-item>
<list-item>
<p>2. Each building must be witnessed once by only one adjuster.</p>
</list-item>
<list-item>
<p>3. The desired times for witnessing are satisfied.</p>
</list-item>
<list-item>
<p>4. Matchings of adjuster&#x2019;s specs and types of buildings are satisfied.</p>
</list-item>
<list-item>
<p>5. The total number of buildings witnessed by any adjuster does not exceed the limit.</p>
</list-item>
</list>
</p>
<p>As mentioned previously, the usual VRP does not satisfy constraints 3, 4, and 5. Therefore, the ARP is an extension of the VRP. Other VRP extensions include the vehicle routing problem with time windows (VRPTW) satisfying constraint 3 [<xref ref-type="bibr" rid="B18">18</xref>,<xref ref-type="bibr" rid="B19">19</xref>] and the capacitated vehicle routing problem (CVRP) satisfying constraint 5 [<xref ref-type="bibr" rid="B20">20</xref>].</p>
<p>As the VRP is in the class NP, we consider solving the ARP using a quantum computer (quantum annealing).</p>
</sec>
<sec id="s1-2">
<title>1.2 Our contributions</title>
<p>In this study, we propose a method for solving the ARP using quantum annealing. The following decision variables are needed for route optimization:<disp-formula id="e1">
<mml:math id="m1">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="{" close="">
<mml:mrow>
<mml:mtable class="cases">
<mml:mtr>
<mml:mtd columnalign="left">
<mml:mn>1</mml:mn>
<mml:mspace width="1em"/>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>when&#x2009;adjuster</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>k</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mtext>witness&#x2009;building</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>n</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>for&#x2009;the</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>i</mml:mi>
<mml:mo>-</mml:mo>
<mml:mtext>th&#x2009;time</mml:mtext>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="left">
<mml:mn>0</mml:mn>
<mml:mspace width="1em"/>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>otherwise</mml:mtext>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(1)</label>
</disp-formula>
</p>
<p>Let <italic>K</italic> be the number of adjusters, <italic>N</italic> the number of buildings, and <italic>I</italic> the number of buildings witnessed by one adjuster. The size of the optimization problem is <italic>K</italic> &#xd7; <italic>N</italic> &#xd7; <italic>I</italic>. Quantum annealing can only solve problems of small size when three parameters (<italic>k</italic>, <italic>n</italic>, <italic>i</italic>) are introduced because the size of the problem is limited by hardware constraints, such as the number of qubits and connectivity [<xref ref-type="bibr" rid="B21">21</xref>]. Further information about these constraints is presented in the following paragraph. We divided the ARP into two subproblems to reduce the number of decision variables: clustering and routing phases. The clustering phase determines which building each adjuster will witness, and the routing phase determines the order each adjuster will witness. A method for dividing the VRP into clustering and routing phases has already been proposed [<xref ref-type="bibr" rid="B22">22</xref>,<xref ref-type="bibr" rid="B23">23</xref>], and we adopt a similar approach for the ARP. To apply quantum annealing, we formulate each phase in QUBO.</p>
<p>Constraints 4 and 5 are considered in the clustering phase because the building to be witnessed by the adjuster is determined in this phase. Specifically, for constraint 4, we interpret the adjuster and building matching as bipartite graph matching and introduce constraints into the clustering phase. For constraint 5, we introduce an element count constraint into the clustering. Constraint 3 is considered in the routing phase because it affects the order of witnessing by the adjuster. Although the routing phase optimizes the route of a single adjuster to witness multiple buildings, and thus can be regarded the same as the traveling salesman problem (TSP) as an optimization problem, we introduce the concept of time into the TSP and introduce constraints to realize routing that satisfies the desired time. When the problem is divided into two phases, the probability that no feasible solution exists in the routing phase increases if the desired time zones of the buildings are concentrated in the same cluster in the clustering phase or if only buildings with large areas are clustered together. Therefore, we introduce constraints in the clustering phase such that they are properly distributed to ensure the diversity of cluster elements. Furthermore, we conducted numerical experiments using D-Wave to confirm the correctness of our formulation.</p>
<p>Our contributions can be summarized as follows:<list list-type="simple">
<list-item>
<p>&#x2022; <bold>Applications of quantum annealing to the real-world problem</bold>: Our ARP is based on the VRP and extended to a realistic setting. We formulated the problem in a form amenable to quantum annealing and confirmed correctness through numerical experiments.</p>
</list-item>
<list-item>
<p>&#x2022; <bold>Proposal of various constraints</bold>: In the clustering and routing phases, we introduced constraints for matching, satisfying the desired time, and variance. We believe that these constraints are applicable not only to our problem but also to other optimization problems related to the VRP.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s1-3">
<title>1.3 Quantum annealing and D-Wave</title>
<p>We review the theoretical backgrounds of quantum annealing and D-Wave machines that implement quantum annealing. Several solvers can perform QUBO, such as Digital Annealer [<xref ref-type="bibr" rid="B25">25</xref>] and CMOS annealer [<xref ref-type="bibr" rid="B26">26</xref>]. In particular, quantum annealing machines have been increasingly applied in recent years, and there are high expectations that both the speed of solution seeking and the quality of the solution will exceed those of classical computers.</p>
<p>Quantum annealing is a meta-heuristic algorithm for optimization problems introducing quantum effects, proposed by Kadowaki and Nishimori [<xref ref-type="bibr" rid="B2">2</xref>]. It can solve optimization problems in QUBO or Ising form. Because QUBO belongs to the NP-hard, quantum annealing can be applied to an extremely wide range of optimization problems.</p>
<p>In quantum annealing, the objective function of the optimization problem under consideration is represented by a quantum system Hamiltonian <inline-formula id="inf1">
<mml:math id="m2">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>. Then, a quantum fluctuation <inline-formula id="inf2">
<mml:math id="m3">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>q</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is introduced, and the ground state of <inline-formula id="inf3">
<mml:math id="m4">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is searched. Thus, quantum annealing deals with the following Hamiltonian <inline-formula id="inf4">
<mml:math id="m5">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>:<disp-formula id="e2">
<mml:math id="m6">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>A</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>B</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>q</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
</mml:math>
<label>(2)</label>
</disp-formula>where <italic>A</italic>(<italic>t</italic>)&#x2a7e;0, <italic>B</italic>(<italic>t</italic>)&#x2a7e;0 and the control shall be performed as in <italic>A</italic>(0) &#x3d; 0, <italic>B</italic>(<italic>&#x3c4;</italic>) &#x3d; 0 with the annealing start time of <italic>t</italic> &#x3d; 0 and end time of <italic>t</italic> &#x3d; <italic>&#x3c4;</italic>. Let <italic>&#x210f;</italic> be the reduced Planck constant, <inline-formula id="inf5">
<mml:math id="m7">
<mml:mfenced open="|" close="&#x27e9;">
<mml:mrow>
<mml:mi>&#x3c8;</mml:mi>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> the spin wavefunction (<inline-formula id="inf6">
<mml:math id="m8">
<mml:mfenced open="|" close="&#x27e9;">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> means the <italic>k</italic>th excited state), &#x394;<sub>
<italic>k</italic>
</sub>(<italic>t</italic>) the energy gap between the state <italic>k</italic> and ground state, and <italic>s</italic> &#x3d; <italic>t</italic>/<italic>&#x3c4;</italic>. By time-evolving <inline-formula id="inf7">
<mml:math id="m9">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> with the Schr&#xf6;dinger equation,<disp-formula id="e3">
<mml:math id="m10">
<mml:mi>i</mml:mi>
<mml:mi>&#x210f;</mml:mi>
<mml:mfrac>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>d</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="|" close="&#x27e9;">
<mml:mrow>
<mml:mi>&#x3c8;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mfenced open="|" close="&#x27e9;">
<mml:mrow>
<mml:mi>&#x3c8;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:math>
<label>(3)</label>
</disp-formula>and with the asymptotic expansion of adiabatic condition<xref ref-type="fn" rid="fn3">
<sup>2</sup>
</xref>,<disp-formula id="e4">
<mml:math id="m11">
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x226b;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mfenced open="&#x27e8;" close="&#x27e9;">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo stretchy="false">&#x7c;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mo>&#x307;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">&#x7c;</mml:mo>
<mml:mn>0</mml:mn>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="normal">&#x394;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:mfrac>
<mml:mo>,</mml:mo>
</mml:math>
<label>(4)</label>
</disp-formula>
<inline-formula id="inf8">
<mml:math id="m12">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>qa</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> follows the ground state at each moment, and finally, the ground state of <inline-formula id="inf9">
<mml:math id="m13">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is obtained. As the ground state of <inline-formula id="inf10">
<mml:math id="m14">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is the solution to the original optimization problem, it can be solved using quantum annealing. This is an outline of the algorithm.</p>
<p>Physical devices that enable quantum annealing have been developed by D-Wave Systems [<xref ref-type="bibr" rid="B3">3</xref>], which recently launched a quantum cloud computing service called D-Wave Leap. In the D-Wave machine, the target quantum system is a spin system, and the Ising model and transverse magnetic field are used as <inline-formula id="inf11">
<mml:math id="m15">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>obj</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> and <inline-formula id="inf12">
<mml:math id="m16">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mtext>q</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>, respectively. Quantum annealing machines are more stable than quantum gate-based machines in controlling quantum devices such as noise, and the machine at the first time of the implementation announcement had only 128 qubits (D-Wave One), increasing to 2,048 qubits in 2017 (D-Wave 2000Q) and 5,436 qubits in September 2020 (Advantage).</p>
<p>As the computational principle of quantum annealing is the transverse-field Ising model, if the combinatorial optimization problem we wish to solve can be formulated in the Ising model, the solution can be obtained by providing information on its coefficients as input. Conversely, when we design a combinatorial optimization problem for a real-world problem, decision variables such as <inline-formula id="inf13">
<mml:math id="m17">
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2208;</mml:mo>
<mml:mfenced open="{" close="}">
<mml:mrow>
<mml:mn>0,1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> are often used, and the input forms of the objective function that D-Wave can optimize correspond to both of these, called the Ising and QUBO forms, respectively, and they are equivalent by variable transformation.</p>
<p>The spin&#x2013;spin interaction in the transverse-field Ising model assumes a fully connected state. Therefore, realizing the fully connected state between spins as a physical device must construct a complete graph with all spins as nodes on the hardware. Because it is currently difficult to construct such a graph, D-Wave introduces a special graph for the connection of spins, called a chimera graph in D-Wave 2000Q and a Pegasus graph in Advantage [<xref ref-type="bibr" rid="B21">21</xref>]. Whatever optimization problem we design, embedding operations are essentially required when performing optimization computations with D-Wave, and the number of installed qubits and the size of the problem to be solved do not generally match.</p>
<p>Optimal annealing time <italic>&#x3c4;</italic> should be long enough to give a sufficiently high probability of finding the ground state (Eq. <xref ref-type="disp-formula" rid="e4">4</xref>). At the same time, it should be as short as possible for practical purposes. Therefore, <italic>&#x3c4;</italic> is a trade-off value. Since the optimal <italic>&#x3c4;</italic> depends on the structure of the problem we wish to solve [<xref ref-type="bibr" rid="B27">27</xref>], a parameter study should essentially be performed. However, as discussed in <xref ref-type="sec" rid="s3">Section 3</xref>, we used D-Wave&#x2019;s hybrid solver system (HSS) for the solver, where <italic>&#x3c4;</italic> cannot be treated as a variable parameter, so we experimented numerically using <italic>&#x3c4;</italic> as a fixed value of 20&#xa0;&#xb5;s.</p>
</sec>
</sec>
<sec sec-type="materials|methods" id="s2">
<title>2 Materials and methods</title>
<p>In this section, we present the formulation of the ARP. First, we recheck the ARP setup. The objective is to optimize the total travel time (not distance) and total time required for the adjuster&#x2019;s witnessing when the adjuster from the insurance company visits each damaged building one by one after a disaster to assess the amount of damage insurance. In addition, as noted in <xref ref-type="sec" rid="s1">Section 1</xref>, we assume the following for the buildings and adjusters:<list list-type="simple">
<list-item>
<p>&#x2022; For buildings,</p>
<list list-type="simple">
<list-item>
<p>- Each desired time for witnessing is set,</p>
</list-item>
<list-item>
<p>- Each time required for witnessing is set (proportional to the total area of the building),</p>
</list-item>
<list-item>
<p>- Each difficulty level for assessment is set.</p>
</list-item>
</list>
</list-item>
<list-item>
<p>&#x2022; For adjusters,</p>
<list list-type="simple">
<list-item>
<p>- Each spec for assessment is set,</p>
</list-item>
<list-item>
<p>- A limit is set on the number of buildings that an adjuster can witness in a day.</p>
</list-item>
</list>
</list-item>
</list>
</p>
<p>Furthermore, constraints 1&#x2013;5 in <xref ref-type="sec" rid="s1">Section 1</xref> are introduced into the optimization. Among the routes that satisfy these constraints, ARP searches for the one that minimizes the total operating time, the sum of total travel time, and the total time required for witnessing.</p>
<p>In this study, we formulate this problem in a QUBO form to solve it using quantum annealing. Because of the limited number of qubits that can be handled, we use 2-Phase-Heuristics [<xref ref-type="bibr" rid="B28">28</xref>] to split the problem into a clustering phase, which determines which buildings the adjuster will witness, and a routing phase, which determines in which order the adjuster will witness the buildings. We formulate the clustering and routing in a QUBO form, respectively, and use the Q2Q approach proposed by Feld et al. [<xref ref-type="bibr" rid="B23">23</xref>], which allows for seeking solutions using quantum annealing in both phases.</p>
<p>For constraints 1&#x2013;5, we consider 1&#x2013;3 for routing and 4 and 5 for clustering. Even if constraints 4 and 5 are satisfied in clustering, if the desired time for witnessing and the time required for witnessing are concentrated in the same group of buildings to be witnessed by an adjuster, it is highly likely that the routing will not yield a solution that satisfies the constraints. Therefore, we introduce an additional constraint to distribute the desired time of witnessing and the time required for witnessing. First, we perform a QUBO formulation of clustering in <xref ref-type="sec" rid="s2-1">Section 2.1</xref>, introducing these additional constraints. In <xref ref-type="sec" rid="s2-2">Section 2.2</xref>, we also present QUBO formulation of route optimization for each cluster, which satisfies the constraint of the desired time for witnessing.</p>
<sec id="s2-1">
<title>2.1 Clustering phase</title>
<p>If the clustering target is a building and each cluster is applied to each adjuster, clustering is synonymous with determining the group of buildings to be witnessed by each adjuster. Thus, defining <inline-formula id="inf14">
<mml:math id="m18">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">{</mml:mo>
<mml:mrow>
<mml:mn>0,1</mml:mn>
</mml:mrow>
<mml:mo stretchy="false">}</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> is a decision variable, 1 if a building <italic>n</italic> belongs to a certain cluster <italic>k</italic> and 0 if it does not. The simplest Hamiltonian that classifies buildings close to each other into the same cluster can be described as follows:<disp-formula id="e5">
<mml:math id="m19">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>vanilla</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>v</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>,</mml:mo>
</mml:math>
<label>(5)</label>
</disp-formula>where <italic>N</italic> is the total number of buildings, <italic>K</italic> is the total number of clusters, and <italic>D</italic>
<sub>
<italic>uv</italic>
</sub> is the weight (distance) between <italic>u</italic> and <italic>v</italic> connected by an edge <italic>E</italic>. The first term is the distance cost term, and the second term is the constraint term for any building to always belong to one of the clusters.</p>
<p>In ARP clustering, it is necessary to add a cost term that accounts for variance (<italic>H</italic>
<sub>div</sub>), a difficulty-matching constraint term between adjuster and building (<italic>H</italic>
<sub>matching</sub>), and a constraint term on the number of elements in the cluster (<italic>H</italic>
<sub>num</sub>). Thus, the Hamiltonian of our clustering takes the following form:<disp-formula id="e6">
<mml:math id="m20">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>clustering</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>vanilla</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>div</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>matching</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>num</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
<label>(6)</label>
</disp-formula>In the following sections, we show how these three conditions can be formulated.</p>
<sec id="s2-1-1">
<title>2.1.1 <italic>H</italic>
<sub>div</sub>: Consideration of the dispersion of elements in clusters</title>
<p>As mentioned previously, buildings in the ARP are given a &#x201c;desired time for witnessing&#x201d; and a &#x201c;time required for witnessing&#x201d; that is proportional to the total area of the building. Therefore, if they have extremely skewed distribution within a given cluster (e.g., all buildings wish to be witnessed in the morning and all buildings have a large total area), then a routing solution that satisfies the desired time for witnessing will not be available. In other words, constraints are needed to ensure that the desired and required times for witnessing are reasonably spread out among the clusters (i.e., there is diversity in the elements). Such a constraint is <italic>H</italic>
<sub>div</sub>, and specific terms are designed according to the objective. Now, the time required for witnessing building <italic>n</italic> is <italic>e</italic>
<sub>
<italic>n</italic>
</sub>, and the set of possible time periods is <inline-formula id="inf15">
<mml:math id="m21">
<mml:mtext>TG</mml:mtext>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="{" close="}">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mo>&#x2026;</mml:mo>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>L</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> as the desired time for witnessing. In this study, we introduce a cost term that simultaneously considers the dispersion of desired and required time for witnessing. The cost term is defined as follows:<disp-formula id="e7">
<mml:math id="m22">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>div</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x2113;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>L</mml:mi>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x2113;</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(7)</label>
</disp-formula>Thus, if the total time required for witnessing for each desired time zone is given as a cost, the bias in the total time required for witnessing can be reduced, as well as the bias in the time desired for witnessing within each cluster.</p>
</sec>
<sec id="s2-1-2">
<title>2.1.2 <italic>H</italic>
<sub>matching</sub>: Consideration of adjuster and building matching</title>
<p>In ARP, we set the specs of adjusters who can witness each building according to its assessment difficulty, and the buildings and adjusters (clusters) must be matched during clustering. This is introduced as a constraint term in the Hamiltonian. We will make it more general to describe relationships other than difficulty and spec. First, we define <italic>k</italic> and <italic>n</italic> to be &#x201c;consistent&#x201d; if adjuster <italic>k</italic> can conduct the witnessing of building <italic>n</italic>. When the spec of adjuster <italic>k</italic> is &#x201c;high&#x201d; and the difficulty level of building <italic>n</italic> is &#x201c;normal,&#x201d; <italic>k</italic> and <italic>n</italic> are consistent. When the spec of <italic>k</italic> is &#x201c;low&#x201d; and the difficulty of <italic>n</italic> is &#x201c;middle,&#x201d; <italic>k</italic> and <italic>n</italic> are not consistent. In addition to specs, a specialized adjuster may be assigned to buildings constructed using special construction methods (such as the two-by-four method). Therefore, a special construction method building and a specialized adjuster are consistent, and other adjusters are not consistent. We can describe mathematically in terms of graph theory that the adjuster and the building are consistent. Let <inline-formula id="inf16">
<mml:math id="m23">
<mml:mi mathvariant="script">K</mml:mi>
</mml:math>
</inline-formula> be the set of adjusters and <inline-formula id="inf17">
<mml:math id="m24">
<mml:mi mathvariant="script">N</mml:mi>
</mml:math>
</inline-formula> the set of buildings. Then, for a bipartite graph <inline-formula id="inf18">
<mml:math id="m25">
<mml:mi mathvariant="script">G</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi mathvariant="script">K</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> with independent <inline-formula id="inf19">
<mml:math id="m26">
<mml:mi mathvariant="script">K</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
</mml:math>
</inline-formula> as vertices and <inline-formula id="inf20">
<mml:math id="m27">
<mml:mi mathvariant="script">E</mml:mi>
</mml:math>
</inline-formula> as an edge set, we define<disp-formula id="e8">
<mml:math id="m28">
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">K</mml:mi>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
<mml:mo>,</mml:mo>
<mml:mspace width="0.01em"/>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
<mml:mo>&#x21d4;</mml:mo>
<mml:mtext>adjuster</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>k</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>and&#x2009;building</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>n</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>are&#x2009;consistent</mml:mtext>
<mml:mo>.</mml:mo>
</mml:math>
<label>(8)</label>
</disp-formula>To match the adjuster and the building, we need to make sure that <inline-formula id="inf21">
<mml:math id="m29">
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
</mml:math>
</inline-formula> is witnessed by one <inline-formula id="inf22">
<mml:math id="m30">
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">K</mml:mi>
</mml:math>
</inline-formula> who satisfies <inline-formula id="inf23">
<mml:math id="m31">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
</mml:math>
</inline-formula>, so the constraints are as follows:<disp-formula id="e9">
<mml:math id="m32">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>matching</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(9)</label>
</disp-formula>We formulate a matching between adjuster specs and building difficulties. Let the set of adjusters with spec &#x201c;high&#x201d; (&#x201c;middle&#x201d; and &#x201c;low,&#x201d; respectively) be High (Middle and Low, respectively) and the set of buildings with difficulty &#x201c;hard&#x201d; (&#x201c;normal&#x201d; and &#x201c;easy,&#x201d; respectively) be Hard (Normal and Easy, respectively). The matching is as follows, respectively:<list list-type="simple">
<list-item>
<p>&#x2022; When <italic>n</italic> &#x2208; Hard, <inline-formula id="inf24">
<mml:math id="m33">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
<mml:mo>&#x21d4;</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
</mml:math>
</inline-formula>.</p>
</list-item>
<list-item>
<p>&#x2022; When <italic>n</italic> &#x2208; Normal, <inline-formula id="inf25">
<mml:math id="m34">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
<mml:mo>&#x21d4;</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
<mml:mo>&#x222a;</mml:mo>
<mml:mtext>Middle</mml:mtext>
</mml:math>
</inline-formula>.</p>
</list-item>
<list-item>
<p>&#x2022; When <italic>n</italic> &#x2208; Easy, <inline-formula id="inf26">
<mml:math id="m35">
<mml:mo>&#x2200;</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">K</mml:mi>
<mml:mo>&#x21d2;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
</mml:math>
</inline-formula>.</p>
</list-item>
</list>
</p>
<p>Substituting this relationship for Eq. <xref ref-type="disp-formula" rid="e9">9</xref>, the constraint terms for matching with respect to specs and difficulties are as follows:<disp-formula id="e10">
<mml:math id="m36">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>matching</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>Hard</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>Normal</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
<mml:mo>&#x222a;</mml:mo>
<mml:mtext>Middle</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(10)</label>
</disp-formula>When <italic>n</italic> &#x2208; Easy, there is no constraint on specs, so it is equivalent to the constraint that &#x201c;each building must be witnessed once by only one adjuster.&#x201d;</p>
</sec>
<sec id="s2-1-3">
<title>2.1.3 <italic>H</italic>
<sub>num</sub>: Constraint term on the number of cluster elements</title>
<p>Even if the dispersion of desired and required time for witnessing and matching adjusters and buildings could be considered, if there are too many buildings to be witnessed by one adjuster, the routing may not fit within the set time frame. Therefore, we consider here a formulation to impose a constraint on the number of elements in a cluster, the total number of buildings witnessed by one adjuster. If the maximum number of elements per cluster is <italic>M</italic> and the number of elements in each cluster is limited to <italic>M</italic> or less, clustering is optimized under the following inequality constraints:<disp-formula id="e11">
<mml:math id="m37">
<mml:munder>
<mml:mrow>
<mml:mi>min</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:munder>
<mml:mspace width="1em"/>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>clustering</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mspace width="1em"/>
<mml:mtext>s.t.</mml:mtext>
<mml:mspace width="1em"/>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>M</mml:mi>
<mml:mspace width="1em"/>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mo>&#x2200;</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mi>K</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(11)</label>
</disp-formula>The aforementioned inequality constraints cannot be formulated as QUBO in their original form and must be rewritten as equality constraints. There are several ways to convert inequality constraints into equality constraints. The first is to introduce a slack variable and attribute it to the multiple knapsack problem (MKSP). Lucas [<xref ref-type="bibr" rid="B28">28</xref>] introduced auxiliary decision variables (slack variables) and used one-hot encoding to express the total number of elements in the cluster and rewrite inequality constraints as equality constraints (Feld et al. [<xref ref-type="bibr" rid="B23">23</xref>] had a similar formulation in the Q2Q approach). The disadvantage is that the number of qubits available to solve a problem is more limited owing to slack variables. The second is to optimize using the augmented Lagrangian method and alternating direction method of multipliers (ADMM) without introducing slack variables. Yonaga et al. [<xref ref-type="bibr" rid="B29">29</xref>] defined an extended Lagrangian by introducing an auxiliary variable in the objective function and proposed a method to obtain a feasible solution while updating the auxiliary variable by applying quantum annealing to QUBO within the ADMM algorithm. This is effective when using quantum annealing because it does not use slack variables, but the computation time increases owing to iterative calculations. The third is to consider only equality constraints in inequality constraints. The number of elements in each cluster can be limited to <italic>M</italic> by imposing the following equality constraints:<disp-formula id="e12">
<mml:math id="m38">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>num</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>M</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(12)</label>
</disp-formula>It is not a constraint like MKSP or ADMM that limits the number of elements to <italic>M</italic> or less, but it can be written in a very simple form. In this paper, we took an equality constraint term for simplicity.</p>
<p>From the aforementioned paragraphs, our clustering Hamiltonian, specifically describing Eq. <xref ref-type="disp-formula" rid="e6">6</xref>, is as follows:<disp-formula id="e13">
<mml:math id="m39">
<mml:mtable class="align" columnalign="left">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>clustering</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:munder>
<mml:munder accentunder="false">
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>v</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>B</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2212;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="true">&#x23df;</mml:mo>
</mml:munder>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>vanilla</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
<mml:mo>&#x2b;</mml:mo>
<mml:munder>
<mml:mrow>
<mml:munder accentunder="false">
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x2113;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>L</mml:mi>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x2113;</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="true">&#x23df;</mml:mo>
</mml:munder>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>div</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:munder>
<mml:mrow>
<mml:munder accentunder="false">
<mml:mrow>
<mml:mi>D</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="true">&#x23df;</mml:mo>
</mml:munder>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>num</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
<mml:mo>&#x2b;</mml:mo>
<mml:munder>
<mml:mrow>
<mml:munder accentunder="false">
<mml:mrow>
<mml:mi>E</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">N</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="script">E</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="true">&#x23df;</mml:mo>
</mml:munder>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>matching</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(13)</label>
</disp-formula>where <italic>A</italic>, <italic>B</italic>, <italic>C</italic>, <italic>D</italic>, and <italic>E</italic> are positive coefficients representing the weight of each cost or constraint term. The problem size for this optimization is <italic>K</italic> &#xd7; <italic>N</italic>.</p>
</sec>
</sec>
<sec id="s2-2">
<title>2.2 Routing phase</title>
<p>After the clustering phase is completed, the goal is to find the optimal route in each cluster. Following Feld et al. [<xref ref-type="bibr" rid="B23">23</xref>], we solve the TSP for every generated cluster. However, we need to find the shortest time route that satisfies the desired time for each building. Therefore, we should introduce time into TSP. Several studies have introduced time to the TSP [<xref ref-type="bibr" rid="B30">30</xref>,<xref ref-type="bibr" rid="B31">31</xref>]. We adopt the time-scheduled traveling salesman problem (TS-TSP<italic>)</italic> proposed by Irie et al. [<xref ref-type="bibr" rid="B32">32</xref>] as a route optimization model. In addition, we introduce the constraint for the desired time in the TS-TSP. We begin with a brief review of the TS-TSP in the following section and describe the Hamiltonian formulation of our routing phase.</p>
<sec id="s2-2-1">
<title>2.2.1 Time-scheduled traveling salesman problem</title>
<p>To introduce the concept of time into TSP, we first divide the time zone into time intervals based on the unit time &#x394;<italic>t</italic>. Then, the variable <inline-formula id="inf27">
<mml:math id="m40">
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="double-struck">Z</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x3e;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is used to represent a certain time interval. In other words, we identify the time interval with <italic>&#x3c4;</italic> in the following correspondence:<disp-formula id="e14">
<mml:math id="m41">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x21a6;</mml:mo>
<mml:mfenced open="[" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:mspace width="0.3333em"/>
<mml:mspace width="0.3333em"/>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
<mml:mspace width="0.3333em"/>
<mml:mspace width="0.3333em"/>
<mml:mspace width="0.3333em"/>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mi mathvariant="normal">&#x394;</mml:mi>
<mml:mi>t</mml:mi>
<mml:mo>,</mml:mo>
</mml:math>
<label>(14)</label>
</disp-formula>where <italic>T</italic> is the length of time considered.</p>
<p>Let <italic>N</italic> be the total number of buildings. We define the variable <italic>x</italic>
<sub>
<italic>&#x3c4;</italic>,<italic>a</italic>
</sub>(1&#x2a7d;<italic>&#x3c4;</italic>&#x2a7d;<italic>T</italic>, 1&#x2a7d;<italic>a</italic>&#x2a7d;<italic>N</italic>) as<disp-formula id="equ1">
<mml:math id="m42">
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="{" close="">
<mml:mrow>
<mml:mtable class="cases">
<mml:mtr>
<mml:mtd columnalign="left">
<mml:mn>1</mml:mn>
<mml:mspace width="1em"/>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>when&#x2009;an&#x2009;adjuster&#x2009;visits&#x2009;building</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>a</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>at&#x2009;time</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="left">
<mml:mn>0</mml:mn>
<mml:mspace width="1em"/>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>otherwise</mml:mtext>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
</disp-formula>For each time interval <italic>&#x3c4;</italic>, we also define the time-duration matrix <inline-formula id="inf28">
<mml:math id="m43">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> and cost-matrix <inline-formula id="inf29">
<mml:math id="m44">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> as<disp-formula id="e15">
<mml:math id="m45">
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="&#x2308;" close="&#x2309;">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>the&#x2009;time&#x2009;required&#x2009;to&#x2009;move</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>b</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>to</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>a</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>at&#x2009;time</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="normal">&#x394;</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msubsup>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtext>the&#x2009;cost&#x2009;to&#x2009;move</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>b</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>to</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>a</mml:mi>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mtext>at&#x2009;time</mml:mtext>
<mml:mspace width="0.17em"/>
<mml:mspace width="0.17em"/>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(15)</label>
</disp-formula>Now, the Hamiltonian of TS-TSP is formulated as follows:<disp-formula id="e16">
<mml:math id="m46">
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>route</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c1;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#xd7;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(16)</label>
</disp-formula>where <bold>
<italic>x</italic>
</bold> &#x3d; (<italic>x</italic>
<sub>
<italic>&#x3c4;</italic>,<italic>a</italic>
</sub>) &#x2208; {0,1}<sup>
<italic>T</italic>&#xd7;<italic>N</italic>
</sup> and<disp-formula id="equ2">
<mml:math id="m47">
<mml:mi>&#x3bb;</mml:mi>
<mml:mo>&#x3e;</mml:mo>
<mml:mn>0</mml:mn>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:mi>&#x3bc;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>max</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:mi>&#x3c1;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>max</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>min</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bb;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mo>.</mml:mo>
</mml:math>
</disp-formula>The first term is the total cost to be minimized, and the second term is the constraint prohibiting any early arrivals.</p>
</sec>
<sec id="s2-2-2">
<title>2.2.2 Formulation of route optimization</title>
<p>We give the Hamiltonian formulation of the routing phase. First, we prepare some notations. Let <italic>p</italic>
<sub>
<italic>a</italic>
</sub> be the time required for witnessing building <italic>a</italic> and TG &#x3d; {<italic>T</italic>
<sub>1</sub>, <italic>&#x2026;</italic>, <italic>T</italic>
<sub>
<italic>M</italic>
</sub>} a set of desired time zones. If <italic>&#x2113;</italic> &#x2260; <italic>m</italic>, <italic>T</italic>
<sub>
<italic>&#x2113;</italic>
</sub> &#x2229; <italic>T</italic>
<sub>
<italic>m</italic>
</sub> &#x3d; <italic>&#x2205;</italic>. Furthermore, let <italic>N</italic>
<sub>
<italic>m</italic>
</sub> be a set of buildings, where the desired time is <italic>T</italic>
<sub>
<italic>m</italic>
</sub> &#x2208; TG. Here, we assume the following:<list list-type="simple">
<list-item>
<p>&#x2022; The time required to travel between two buildings does not depend on <italic>&#x3c4;</italic>:</p>
</list-item>
</list>
<disp-formula id="equ3">
<mml:math id="m48">
<mml:mo>&#x2200;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>&#x21d2;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x3d;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:msubsup>
<mml:mo>.</mml:mo>
</mml:math>
</disp-formula>
<list list-type="simple">
<list-item>
<p>&#x2022; The cost to travel between two buildings is travel time:</p>
</list-item>
</list>
<disp-formula id="equ4">
<mml:math id="m49">
<mml:msubsup>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
</disp-formula>
<list list-type="simple">
<list-item>
<p>&#x2022; The time required for witnessing is included in travel time, namely, rewriting travel time from building <italic>b</italic> to <italic>a</italic> by <italic>e</italic>
<sub>
<italic>ab</italic>
</sub>:</p>
</list-item>
</list>
<disp-formula id="equ5">
<mml:math id="m50">
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
</disp-formula>
<list list-type="simple">
<list-item>
<p>&#x2022; Every adjuster starts from a certain office (depot) and backs there. Depot is not included in the number of buildings to witness.</p>
</list-item>
</list>
</p>
<p>Under these assumptions, we introduce constraints for the routing phase. Every adjuster starts from the depot and backs there, so the route prohibits early arrivals from the depot (at <italic>&#x3c4;</italic> &#x3d; 1) and ensures that the adjuster arrives at the depot within time <italic>T</italic>. The adjuster must also conduct a witnessing that satisfies the desired time for each building.</p>
<p>These constraints can be formulated as follows:<list list-type="simple">
<list-item>
<p>&#x2022; The constraint that forbids early arrivals from the depot is as follows (as Eq. <xref ref-type="disp-formula" rid="e16">16</xref>):</p>
</list-item>
</list>
<disp-formula id="e17">
<mml:math id="m51">
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="normal">d</mml:mi>
<mml:mi mathvariant="normal">e</mml:mi>
<mml:mi mathvariant="normal">p</mml:mi>
<mml:mi mathvariant="normal">o</mml:mi>
<mml:mi mathvariant="normal">t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
<mml:mtext>depot</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="normal">d</mml:mi>
<mml:mi mathvariant="normal">e</mml:mi>
<mml:mi mathvariant="normal">p</mml:mi>
<mml:mi mathvariant="normal">o</mml:mi>
<mml:mi mathvariant="normal">t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
<label>(17)</label>
</disp-formula>
<list list-type="simple">
<list-item>
<p>&#x2022; The constraint that arrives at the depot within time <italic>T</italic> is</p>
</list-item>
</list>
<disp-formula id="e18">
<mml:math id="m52">
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>depot</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
<label>(18)</label>
</disp-formula>
<list list-type="simple">
<list-item>
<p>&#x2022; For a building with desired time <italic>T</italic>
<sub>
<italic>m</italic>
</sub>, it is sufficient to satisfy <italic>x</italic>
<sub>
<italic>&#x3c4;</italic>,<italic>a</italic>
</sub> &#x3d; 1 for some <italic>&#x3c4;</italic> &#x2208; <italic>T</italic>
<sub>
<italic>m</italic>
</sub>, so the constraint for the desired time is</p>
</list-item>
</list>
<disp-formula id="e19">
<mml:math id="m53">
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="normal">T</mml:mi>
<mml:mi mathvariant="normal">G</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>N</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(19)</label>
</disp-formula>Finally, the Hamiltonian of the routing phase is<disp-formula id="e20">
<mml:math id="m54">
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>route</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c1;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#xd7;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="normal">d</mml:mi>
<mml:mi mathvariant="normal">e</mml:mi>
<mml:mi mathvariant="normal">p</mml:mi>
<mml:mi mathvariant="normal">o</mml:mi>
<mml:mi mathvariant="normal">t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>depot</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="normal">T</mml:mi>
<mml:mi mathvariant="normal">G</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>N</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(20)</label>
</disp-formula>
</p>
<p>This is based on the negatively shifted energy method [<xref ref-type="bibr" rid="B32">32</xref>]. However, the constraint for desired time is formulated in squared penalty. In our experiments, we confirmed that one can obtain feasible solutions even with a squared penalty. The problem size for this optimization is <italic>N</italic> &#xd7; <italic>T</italic>.</p>
</sec>
</sec>
</sec>
<sec sec-type="results" id="s3">
<title>3 Results</title>
<p>In this section, we present the results of numerical experiments on ARP using the D-Wave machine and the Hamiltonian constructed in the previous section. To evaluate the impact on the solution of differences in each input parameter of the problem (number of buildings, difficulty level for assessment, distribution of time required for witnessing, etc.), we defined a base case for the ARP and a derived case in which each input parameter of the base case was partially modified. In <xref ref-type="sec" rid="s3-1">Section 3.1</xref>, we describe the specific Hamiltonian and various input parameters of the base case used in the numerical experiments. For the base case, we compare the solutions obtained in the clustering phase in <xref ref-type="sec" rid="s3-2">Section 3.2</xref> and the routing phase in <xref ref-type="sec" rid="s3-3">Section 3.3</xref>, respectively, and describe whether there are solutions that do not satisfy the constraints depending on whether they are in a sparsely populated or urban area.</p>
<p>Here, we used the following two QUBO solvers for numerical experiments available <italic>via</italic> D-Wave Ocean SDK<xref ref-type="fn" rid="fn4">
<sup>3</sup>
</xref>. The first is called Neal, a solver using the classical method based on simulated annealing (SA) [<xref ref-type="bibr" rid="B33">33</xref>]. The second, called hybrid_v2, is a hybrid of classical and quantum methods and is one of the solvers in D-Wave&#x2019;s HSS that can solve larger sizes at faster speeds by appropriately decomposing the size of the input QUBO and performing parallel processing. The latest solver as of 2022 is hybrid_v2, which can handle as input a fully connected graph of up to 20,000 nodes. In this study, we used the HSS solution for comparison with the Neal (SA) solution.</p>
<p>The comparison of the SA and HSS solutions obtained with the aforementioned solver in terms of processing time is given in <xref ref-type="sec" rid="s3-4">Section 3.4</xref>. Finally, in <xref ref-type="sec" rid="s3-5">Section 3.5</xref>, we describe the overall numerical experiments obtained in the base case and its derivatives. As a summary of the results, the solution in the clustering phase is feasible in all cases, and some break solutions occur in the routing phase. The HSS solution in the clustering phase has a solution time advantage over the SA solution in all cases.</p>
<sec id="s3-1">
<title>3.1 Settings</title>
<p>In the numerical experiments, multiple cases were set up and verified for the ARP. The details of the settings are described as follows. The target area was chosen to be near Kawajiri Station in Kumamoto Prefecture, Japan, as an example of major earthquake damage in the past (<xref ref-type="fig" rid="F1">Figure 1</xref>). First, we defined the size of the problem in the clustering phase as one instance such that 100 visits are divided into 20 clusters. The instances were configured with information on the buildings to be visited (location, distance between buildings, difficulty level for assessment, required time, and desired time for witnessing) and the percentage of corresponding adjuster specs for each instance. To account for the effect of the different geographic distributions of instances, we prepared 10 instances, as shown in <xref ref-type="fig" rid="F2">Figure 2</xref>. As a practical matter, the numbers of adjusters and their specs are limited, and considering the matching constraints between specs and difficulty, it becomes obvious that if there is a bias in the difficulty levels, a feasible solution in the routing will not be obtained. Therefore, the adjuster&#x2019;s spec ratio and the assessment difficulty ratio were set to be completely common (fixed) in each instance. In contrast, the time required for witnessing and the desired time for witnessing were set to change from case to case. The common settings for case-independent instances are as in <xref ref-type="table" rid="T1">Table 1</xref>. Furthermore, we defined the base case as shown in <xref ref-type="table" rid="T2">Table 2</xref> for the ratio of time desired for witnessing. For each of the settings in <xref ref-type="table" rid="T2">Table 2</xref>, we defined cases as a derivation of the base case with each of the parameters changed except the depot location. Numerical experiments were also conducted for these cases (details are given in <xref ref-type="sec" rid="s3-5">Section 3.5</xref>).</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Map of 16&#xa0;km radius around Kawajiri Station (the red dot in the center).</p>
</caption>
<graphic xlink:href="fphy-11-1129594-g001.tif"/>
</fig>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Ten instances with different geographic distributions in the base case.</p>
</caption>
<graphic xlink:href="fphy-11-1129594-g002.tif"/>
</fig>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Common settings for each instance.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Item</th>
<th align="center">Detail</th>
<th align="center">Note</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Depot</td>
<td align="center">Kawajiri Station</td>
<td align="center">Examples of past disasters</td>
</tr>
<tr>
<td align="center">Operating hours</td>
<td align="center">9:00&#x2013;17:00</td>
<td align="center">Not considering lunch break</td>
</tr>
<tr>
<td align="center">Number of cases per adjuster</td>
<td align="center">5</td>
<td align="center">Synonymous with the number of elements per cluster</td>
</tr>
<tr>
<td align="center">Difficulty levels</td>
<td align="center">Hard/normal/easy</td>
<td align="center">Assuming three levels</td>
</tr>
<tr>
<td align="center">Adjuster&#x2019;s specs</td>
<td align="center">High/middle/low</td>
<td align="center">Assuming three types<xref ref-type="table-fn" rid="Tfn1">
<sup>a</sup>
</xref>
</td>
</tr>
<tr>
<td align="center">Desired time for witnessing</td>
<td align="center">AM/PM1/PM2</td>
<td align="center">Assuming three zones<xref ref-type="table-fn" rid="Tfn2">
<sup>b</sup>
</xref>
</td>
</tr>
<tr>
<td align="center">Adjuster spec ratio</td>
<td align="center">2:3:15</td>
<td align="center">high:middle:low in this order</td>
</tr>
<tr>
<td align="center">Difficulty level ratio</td>
<td align="center">6:16:78</td>
<td align="center">hard:normal:easy in this order</td>
</tr>
<tr>
<td align="center">Average travel speed of adjuster</td>
<td align="center">40&#xa0;km/h</td>
<td align="center">Assuming general road travel by vehicle</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn1">
<label>
<sup>a</sup>
</label>
<p>High can assess all three difficulty levels mentioned previously, middle can assess normal and easy, and low can assess only easy.</p>
</fn>
<fn id="Tfn2">
<label>
<sup>b</sup>
</label>
<p>We define AM &#x3d; 9:00&#x2013;11:30, PM1 &#x3d; 12:00&#x2013;14:00, and PM2 &#x3d; 14:30&#x2013;16:30 and assume that all visits have one desired time for witnessing each.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Settings for each instance in the base case.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Item</th>
<th align="center">Detail</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Depot location</td>
<td align="center">Center of distribution</td>
</tr>
<tr>
<td align="center">Distribution radius of buildings</td>
<td align="center">16.0&#xa0;km</td>
</tr>
<tr>
<td align="center">Number of buildings</td>
<td align="center">100</td>
</tr>
<tr>
<td align="center">Number of adjusters (clusters)</td>
<td align="center">20</td>
</tr>
<tr>
<td align="center">Ratio of desired time for witnessing</td>
<td align="center">AM:PM1:PM2 &#x3d; 40:30:30</td>
</tr>
<tr>
<td align="center">Ratio of required time for witnessing<xref ref-type="table-fn" rid="Tfn3">
<sup>a</sup>
</xref>
</td>
<td align="center">0.5&#xa0;h:1.0&#xa0;h:1.5&#xa0;h &#x3d; 75:23:2</td>
</tr>
<tr>
<td align="center">Unit time in TS-TSP</td>
<td align="center">&#x394;<italic>t</italic> &#x3d; 0.25 (<italic>&#x23;&#x3c4;</italic> &#x3d; 32)</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn3">
<label>
<sup>a</sup>
</label>
<p>The time required for witnessing is assumed to be proportional to the total area of the building, with 0.5&#xa0;h being less than 100&#xa0;m<sup>2</sup>, 1.0&#xa0;h being between 100&#xa0;m<sup>2</sup> and 200&#xa0;m<sup>2</sup>, and 1.5&#xa0;h being between 200&#xa0;m<sup>2</sup> and 300&#xa0;m<sup>2</sup> (h represents hours).</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Furthermore, by setting up numerical experiments as described previously, <italic>H</italic>
<sub>div</sub> and <italic>H</italic>
<sub>matching</sub> in Eq. <xref ref-type="disp-formula" rid="e13">13</xref> can be written down specifically, respectively. Thus, the Hamiltonian <inline-formula id="inf30">
<mml:math id="m55">
<mml:msubsup>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>clustering</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>sim</mml:mtext>
</mml:mrow>
</mml:msubsup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> of the clustering phase in the numerical experiment is as follows:<disp-formula id="e21">
<mml:math id="m56">
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msubsup>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>clustering</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>sim</mml:mtext>
</mml:mrow>
</mml:msubsup>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x2009;</mml:mo>
<mml:mo>&#x2009;</mml:mo>
<mml:mo>&#x2009;</mml:mo>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>A</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mi>v</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>v</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>B</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2212;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>D</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>C</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munderover accentunder="false" accent="false">
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>K</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mfenced open="{" close="}">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>AM</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>E</mml:mi>
<mml:mfenced open="{" close="}">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>Hard</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>n</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>Normal</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>High</mml:mtext>
<mml:mo>&#x222a;</mml:mo>
<mml:mtext>Middle</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(21)</label>
</disp-formula>where <italic>N</italic> &#x3d; 100, <italic>K</italic> &#x3d; 20, and <italic>M</italic> &#x3d; 5 correspond to the total number of visits, the total number of clusters, and the number of elements per cluster, respectively, and <italic>D</italic>
<sub>
<italic>&#x3bc;&#x3bd;</italic>
</sub> represent the distance matrix between visits <italic>&#x3bc;</italic> and <italic>&#x3bd;</italic>. We used <italic>A</italic> &#x3d; 1, <italic>B</italic> &#x3d; <italic>D</italic> &#x3d; <italic>E</italic> &#x3d; max(<italic>D</italic>
<sub>
<italic>uv</italic>
</sub>) &#xd7; <italic>K</italic> &#xd7; 2, <italic>C</italic> &#x3d; 60 for each coefficient.</p>
<p>Similarly, the desired time constraint in Eq. <xref ref-type="disp-formula" rid="e20">20</xref> can be specifically written down, and the Hamiltonian <inline-formula id="inf31">
<mml:math id="m57">
<mml:msubsup>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>route</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>sim</mml:mtext>
</mml:mrow>
</mml:msubsup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> for the routing phase in the numerical experiment becomes<disp-formula id="e22">
<mml:math id="m58">
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msubsup>
<mml:mrow>
<mml:mi>H</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>route</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>sim</mml:mtext>
</mml:mrow>
</mml:msubsup>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="bold-italic">x</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c1;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#xd7;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3b4;</mml:mi>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>b</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2032;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x3c;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="normal">d</mml:mi>
<mml:mi mathvariant="normal">e</mml:mi>
<mml:mi mathvariant="normal">p</mml:mi>
<mml:mi mathvariant="normal">o</mml:mi>
<mml:mi mathvariant="normal">t</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mtable class="subarray-c" columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mn>1</mml:mn>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mi>T</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>depot</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2a7d;</mml:mo>
<mml:mi>T</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right"/>
<mml:mtd columnalign="left">
<mml:mo>&#x2b;</mml:mo>
<mml:mi>&#x3bb;</mml:mi>
<mml:mo>{</mml:mo>
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>AM</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mtext>AM</mml:mtext>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>a</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>b</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mrow>
<mml:mtext>PM</mml:mtext>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>c</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo>}</mml:mo>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(22)</label>
</disp-formula>where <italic>N</italic> &#x3d; 5 and <italic>T</italic> &#x3d; 32<xref ref-type="fn" rid="fn5">
<sup>4</sup>
</xref> correspond to the number of buildings per cluster and the number of time intervals, respectively, and <italic>&#x2211;</italic>
<sub>
<italic>a</italic>&#x2208;AM</sub> means taking the sum for building <italic>a</italic> such that the desired time for witnessing is the AM zone (the same for PM1 and PM2). <italic>n</italic>
<sub>
<italic>ab</italic>
</sub> in the first term can be obtained using the distance matrix <italic>D</italic>
<sub>
<italic>ab</italic>
</sub> and Eq. <xref ref-type="disp-formula" rid="e15">15</xref>. We took <italic>&#x3bb;</italic> &#x3d; 40 for the coefficient.</p>
</sec>
<sec id="s3-2">
<title>3.2 Clustering</title>
<p>Here are some of the clustering results for each instance in the base case using the Hamiltonian in Eq. <xref ref-type="disp-formula" rid="e21">21</xref>, accounting for the matchings of adjusters and buildings and dispersion in the required and desired time for witnessing.</p>
<p>
<xref ref-type="fig" rid="F3">Figure 3</xref> shows<xref ref-type="fn" rid="fn6">
<sup>5</sup>
</xref> a portion of the clustering results for instance No. 1 of the base case. The red point cloud in <xref ref-type="fig" rid="F2">Figure 2</xref>, an example of an urban area, color-coded by clusters to visualize the location relationships and the data for each of the same clusters, is shown in <xref ref-type="table" rid="T3">Table 3</xref>. The distances between buildings in the cluster are short because of the high density near the depot, but the buildings closest to each other are necessarily not in the same cluster, which means the difficulty and spec correspondence and dispersion of desired and required time for witnessing are considered. For clusters other than those shown in <xref ref-type="fig" rid="F3">Figure 3</xref> and <xref ref-type="table" rid="T3">Table 3</xref>, the matching conditions for adjusters (clusters) and buildings were satisfied, and the required time and desired time for witnessing were appropriately distributed. There was no solution that did not satisfy the constraints (we call such a solution &#x201c;break solution&#x201d;) for either the SA or HSS solutions. No break solution occurred in all other instances, including sparsely populated areas, confirming that a feasible solution was obtained during the entire clustering phase.</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>Location of the three clusters in instance No. 1 of the base case.</p>
</caption>
<graphic xlink:href="fphy-11-1129594-g003.tif"/>
</fig>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Data for each of the three clusters in instance No. 1 of the base case: the top five, middle five, and bottom five points belong to different clusters (corresponding to red, blue, and green in <xref ref-type="fig" rid="F3">Figure 3</xref>).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Desired time</th>
<th align="center">Difficulty</th>
<th align="center">Required time (h)</th>
<th align="center">Adjuster&#x2019;s spec</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">AM</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM2</td>
<td align="center">Easy</td>
<td align="center">1.0</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM1</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">AM</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM1</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">AM</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM2</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">AM</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM1</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">PM1</td>
<td align="center">Hard</td>
<td align="center">0.5</td>
<td align="center">High</td>
</tr>
<tr>
<td align="center">AM</td>
<td align="center">Normal</td>
<td align="center">1.0</td>
<td align="center">Middle</td>
</tr>
<tr>
<td align="center">AM</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">Middle</td>
</tr>
<tr>
<td align="center">PM2</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">Middle</td>
</tr>
<tr>
<td align="center">PM2</td>
<td align="center">Normal</td>
<td align="center">0.5</td>
<td align="center">Middle</td>
</tr>
<tr>
<td align="center">PM1</td>
<td align="center">Normal</td>
<td align="center">1.0</td>
<td align="center">Middle</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s3-3">
<title>3.3 Routing</title>
<p>Here are some of the results of route optimization using Eq. <xref ref-type="disp-formula" rid="e22">22</xref> for the results of the clustering described in <xref ref-type="sec" rid="s3-2">Section 3.2</xref>. In the routing phase, unlike the clustering phase, some cases occurred where feasible solutions were not obtained, so we also addressed such solutions.</p>
<p>
<xref ref-type="fig" rid="F4">Figure 4</xref> visualizes the solution of route optimization for one cluster belonging to instance No. 1, corresponding to the top five clusters in <xref ref-type="table" rid="T3">Tables 3</xref>, <xref ref-type="table" rid="T4">4</xref> summarizes the travel time in the travel order for each visit. As shown in the chart, the route departs from the depot and returns to the depot within 8&#xa0;h and is such that the desired time for witnessing each visit is satisfied. In addition, it was confirmed that all the route optimization solutions for the other clusters in instance No. 1 are also feasible.</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>Route visualization for cluster No. 1 in instance No. 1 of the base case (paths are represented by red, green, blue, light blue, purple, and yellow in that order).</p>
</caption>
<graphic xlink:href="fphy-11-1129594-g004.tif"/>
</fig>
<table-wrap id="T4" position="float">
<label>TABLE 4</label>
<caption>
<p>Route optimization results for cluster No. 1 at instance No. 1 in the base case.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Itinerary<xref ref-type="table-fn" rid="Tfn4">
<sup>a</sup>
</xref>
</th>
<th align="center">Travel time (h)</th>
<th align="center">Arrival time (h)</th>
<th align="center">Arrival time zone</th>
<th align="center">Desired time zone</th>
<th align="center">Required time (h)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Depot</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0.25</td>
<td align="center">1.5</td>
<td align="center">AM</td>
<td align="center">AM</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">0.25</td>
<td align="center">2.25</td>
<td align="center">AM</td>
<td align="center">AM</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">0.25</td>
<td align="center">4.25</td>
<td align="center">PM1</td>
<td align="center">PM1</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">0.25</td>
<td align="center">5.0</td>
<td align="center">PM1</td>
<td align="center">PM1</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">5</td>
<td align="center">0.25</td>
<td align="center">6.5</td>
<td align="center">PM2</td>
<td align="center">PM2</td>
<td align="center">1.0</td>
</tr>
<tr>
<td align="center">Depot</td>
<td align="center">0.25</td>
<td align="center">6.75</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn4">
<label>
<sup>a</sup>
</label>
<p>The number (1, 2, 3, &#x2026;) in the itinerary column is the ID of the building, not the order of the visits. The order of visits is from the top to the bottom of the column.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Conversely, only in instance No. 9, the brown point cloud in <xref ref-type="fig" rid="F2">Figure 2</xref>, break solutions occurred in 2 out of 20 clusters. <xref ref-type="fig" rid="F5">Figure 5</xref> visualizes one of the clusters in instance No. 9, which is one of the solutions for which the constraint was broken. <xref ref-type="table" rid="T5">Table 5</xref> summarizes the travel time for each building in order of travel; the desired time zone for witnessing the fourth visit is AM, but as a solution, it arrives at PM1, which breaks the desired time constraint. Similarly, for the other break solution, the break of the desired time constraint occurred in a cluster in a sparsely populated area far from the depot, resulting in a solution with a relatively long total travel distance. For these solutions, optimization with only the constraint term after excluding the cost term, the first term in Eq. <xref ref-type="disp-formula" rid="e22">22</xref>, did not break, suggesting that the trade-off between travel time minimization and desired time constraints is more pronounced in the case of long total travel distances.</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>Route visualization for the break solution in instance No. 9 of the base case (paths are represented by red, green, blue, light blue, purple, and yellow in that order).</p>
</caption>
<graphic xlink:href="fphy-11-1129594-g005.tif"/>
</fig>
<table-wrap id="T5" position="float">
<label>TABLE 5</label>
<caption>
<p>Example of break solutions for route optimization results at instance No. 9 in the base case. The meaning of the &#x201c;Itinerary&#x201d; column is the same as in <xref ref-type="table" rid="T4">Table 4</xref>. A fourth visit breaks the desired time constraint.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Itinerary</th>
<th align="center">Travel time (h)</th>
<th align="center">Arrival time (h)</th>
<th align="center">Arrival time zone</th>
<th align="center">Desired time zone</th>
<th align="center">Required time (h)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Depot</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">0.75</td>
<td align="center">2.5</td>
<td align="center">AM</td>
<td align="center">AM</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">0.5</td>
<td align="center">3.5</td>
<td align="center">PM1</td>
<td align="center">PM1</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0.25</td>
<td align="center">4.25</td>
<td align="center">PM1</td>
<td align="center">PM1</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">5</td>
<td align="center">0.25</td>
<td align="center">5.0</td>
<td align="center">PM1</td>
<td align="center">AM</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">0.25</td>
<td align="center">5.75</td>
<td align="center">PM2</td>
<td align="center">PM2</td>
<td align="center">1.0</td>
</tr>
<tr>
<td align="center">Depot</td>
<td align="center">0.25</td>
<td align="center">7.0</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s3-4">
<title>3.4 Processing time</title>
<p>In the base case, we measured processing times in the two phases of the numerical experiment, the clustering and routing phases, and compared the differences between the solvers. The processing time was defined as the QUBO computation and solving time for both clustering and routing, both for one instance (for clustering, the process of dividing 100 buildings into 20 clusters of 5 elements each; for routing, the routing process for 20 clusters). The results are shown in <xref ref-type="table" rid="T6">Table 6</xref>. The processing time variation in clustering is small for HSS but large for routing. HSS, including quantum annealing, is superior in clustering, whereas SA is superior in the routing phase. The reason for these differences is that HSS performs quantum annealing while dividing QUBO according to the problem size, which is effective for large problems. However, extra processing time is presumably required for too small problems. The advantages of HSS will become even more effective when the problem size per processing unit increases during the routing phase.</p>
<table-wrap id="T6" position="float">
<label>TABLE 6</label>
<caption>
<p>Processing time for each solver in each phase.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="center">Phase</th>
<th rowspan="2" align="center">Problem size</th>
<th rowspan="2" align="center">Number of problems</th>
<th colspan="2" align="center">Processing time<xref ref-type="table-fn" rid="Tfn5">
<sup>a</sup>
</xref> (min)</th>
</tr>
<tr>
<th align="center">Neal (SA)</th>
<th align="center">HSS</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Clustering</td>
<td align="center">20 &#xd7; 100</td>
<td align="center">1</td>
<td align="center">0.6 &#xb1; 0.1</td>
<td align="center">
<bold>0.4 &#xb1; 0.0</bold>
</td>
</tr>
<tr>
<td align="center">Routing</td>
<td align="center">32 &#xd7; 5</td>
<td align="center">20 (sequential)</td>
<td align="center">
<bold>3.1 &#xb1; 0.0</bold>
</td>
<td align="center">5.8 &#xb1; 1.0</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn5">
<label>
<sup>a</sup>
</label>
<p>The numerical experiments were run five times to measure the time.</p>
</fn>
</table-wrap-foot>
<table-wrap-foot>
<fn>
<p>Bold is used to mean the better value.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>For the break solution in the routing described previously, no feasible solution was obtained by HSS instead of SA. The break solution occurred even when the entire routing phase was solved with HSS from the beginning, and the same was true when both clustering and routing phases were solved consistently with HSS. Focusing especially on the clustering phase, where the superiority of the HSS solution was confirmed in terms of processing time, the percentage of solutions with the smaller energy value is shown in <xref ref-type="table" rid="T7">Table 7</xref>. The largest energy difference occurred at instance No. 6, yellow dots in <xref ref-type="fig" rid="F2">Figure 2</xref>, where the HSS solution was 4.6% smaller than the SA solution in terms of magnitude. However, this level of energy difference is considered to have a small impact on the routing phase solution because there are cases where the break solution occurs in the routing phase, regardless of whether the HSS or SA solution is used in the clustering phase.</p>
<table-wrap id="T7" position="float">
<label>TABLE 7</label>
<caption>
<p>Energetic advantage of each solver in the clustering phase.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="center">Phase</th>
<th rowspan="2" align="center">Problem size</th>
<th rowspan="2" align="center">Number of problems</th>
<th rowspan="2" align="center">Maximum energy difference (%)</th>
<th colspan="2" align="center">Percentage of solutions with low energy (%)</th>
</tr>
<tr>
<th align="center">Neal</th>
<th align="center">HSS</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Clustering</td>
<td align="center">20 &#xd7; 100</td>
<td align="center">10</td>
<td align="center">4.6</td>
<td align="center">30</td>
<td align="center">
<bold>70</bold>
</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn>
<p>Bold is used to mean the better value.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>In this paper, clustering is performed in the form of assigning a building to each adjuster, so even if a feasible solution is obtained in the clustering phase, the impact of the solution will strongly affect the next routing phase. To reduce this effect, for example, let us consider the case where the number of elements in one cluster increased. In this form of TS-VRP, a route optimization in which several people visit dozens of buildings, it may be possible to reduce the number of break solutions in the HSS solver and reduce the processing time. Mitigating the constraints that the solution of the clustering phase imposes on the next routing phase is a topic for future work.</p>
</sec>
<sec id="s3-5">
<title>3.5 Results of other cases</title>
<p>A list of changes from the base case for each case is shown in <xref ref-type="table" rid="T8">Table 8</xref>. The application of the results of five numerical experiments, each with SA for all cases, is shown in <xref ref-type="table" rid="T9">Table 9</xref>. Here, the processing time is calculated by the total processing time of the clustering and routing phases according to <xref ref-type="table" rid="T6">Table 6</xref>. The percentage of break solutions means the percentage of the total 200 route optimization solutions. In all cases, the changes in each setting value affected the processing time and solution quality. However, especially for case &#x23;4, although the processing time was reduced, the quality dropped significantly due to many broken solutions in the final routing phase caused by the increase in unit time in route optimization. There are instances of urban and sparsely populated areas in the numerical experiments. Particularly, in the former, where buildings to visit are relatively close to each other, a too large unit time would have a negative impact on the routing optimization. Therefore, an appropriate value for the problem setting should be set like the unit time of route optimization. It was also found that when there is no significant bias in the desired time zone, as in &#x23;1 and &#x23;2, a feasible solution is sufficient in the area within a radius of 16&#xa0;km. For cases such as &#x23;5&#x2013;&#x23;7, where there is a significant bias in the desired time zone, the Q2Q approach requires measures to ease the constraints on the routing solution by adjusting the size of the solution passed between the two phases, as described in <xref ref-type="sec" rid="s3-4">Section 3.4</xref>. As also discussed in <xref ref-type="sec" rid="s3-4">Section 3.4</xref>, the HSS has advantages, at least in clustering. Therefore, when HSS is used for severe cases such as &#x23;2, &#x23;7, and &#x23;8, it may be possible to suppress break solutions.</p>
<table-wrap id="T8" position="float">
<label>TABLE 8</label>
<caption>
<p>Differences between the base case and other cases.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">&#x23;</th>
<th align="center">Difference</th>
<th align="center">Base value</th>
<th align="center">Modified value</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">1 (base)</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
<td align="center">&#x2014;</td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">Large distribution radius</td>
<td align="center">16.0&#xa0;km</td>
<td align="center">32.0&#xa0;km</td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">Fewer buildings and adjusters</td>
<td align="center">(&#x23; of buildings, &#x23; of adjusters) &#x3d; (100, 20)</td>
<td align="center">(50, 10)</td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">Large unit time</td>
<td align="center">&#x394;<italic>t</italic> &#x3d; 0.25</td>
<td align="center">0.5</td>
</tr>
<tr>
<td align="center">5</td>
<td align="center">Busy in AM</td>
<td align="center">AM:PM1:PM2 &#x3d; 40:30:30</td>
<td align="center">60:20:20</td>
</tr>
<tr>
<td align="center">6</td>
<td align="center">Busy in PM1</td>
<td align="center">AM:PM1:PM2 &#x3d; 40:30:30</td>
<td align="center">30:50:20</td>
</tr>
<tr>
<td align="center">7</td>
<td align="center">Busy in PM2</td>
<td align="center">AM:PM1:PM2 &#x3d; 40:30:30</td>
<td align="center">30:20:50</td>
</tr>
<tr>
<td align="center">8</td>
<td align="center">Visits with large areas</td>
<td align="center">0.5&#xa0;h:1.0&#xa0;h:1.5&#xa0;h &#x3d; 75:23:2</td>
<td align="center">35:62:3</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="T9" position="float">
<label>TABLE 9</label>
<caption>
<p>Summary of numerical experimental results in each case.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">&#x23;</th>
<th align="center">Difference</th>
<th align="center">
<inline-formula id="inf32">
<mml:math id="m59">
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mo>&#x304;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula>
<xref ref-type="table-fn" rid="Tfn6">
<sup>a</sup>
</xref> (min)</th>
<th align="center">Presence of break sol.</th>
<th align="center">&#x23; of sol.</th>
<th align="center">
<inline-formula id="inf33">
<mml:math id="m60">
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>V</mml:mi>
</mml:mrow>
<mml:mo>&#x304;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula>
<xref ref-type="table-fn" rid="Tfn7">
<sup>b</sup>
</xref>
</th>
<th align="center">Summary</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">1 (base)</td>
<td align="center">&#x2014;</td>
<td align="center">3.7 &#xb1; 0.1</td>
<td align="center">1 out of 5</td>
<td align="center">2 (1%)</td>
<td align="center">0.33</td>
<td align="center">&#x2014;</td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">Large radius</td>
<td align="center">3.8 &#xb1; 0.2</td>
<td align="center">5 out of 5</td>
<td align="center">9 &#x223c;18 (4.5% &#x223c;9%)</td>
<td align="center">0.36</td>
<td align="center">Break sol. increased</td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">Fewer buildings</td>
<td align="center">1.7 &#xb1; 0.0</td>
<td align="center">1 out of 5</td>
<td align="center">2 (1%)</td>
<td align="center">0.34</td>
<td align="center">Computation time reduced</td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">Large unit time</td>
<td align="center">1.9 &#xb1; 0.2</td>
<td align="center">5 out of 5</td>
<td align="center">17 &#x223c;42 (8.5% &#x223c;21%)</td>
<td align="center">0.34</td>
<td align="center">Computation time for route optimization reduced</td>
</tr>
<tr>
<td align="center">5</td>
<td align="center">Busy in AM</td>
<td align="center">3.8 &#xb1; 0.2</td>
<td align="center">5 out of 5</td>
<td align="center">7 &#x223c;17 (3.5% &#x223c;8.5%)</td>
<td align="center">1.05</td>
<td align="center">AM break sol. increased</td>
</tr>
<tr>
<td align="center">6</td>
<td align="center">Busy in PM1</td>
<td align="center">3.9 &#xb1; 0.2</td>
<td align="center">1 out of 5</td>
<td align="center">1 (0.5%)</td>
<td align="center">0.63</td>
<td align="center">Very few break sol.</td>
</tr>
<tr>
<td align="center">7</td>
<td align="center">Busy in PM2</td>
<td align="center">3.9 &#xb1; 0.2</td>
<td align="center">5 out of 5</td>
<td align="center">26 &#x223c;45 (13% &#x223c;22.5%)</td>
<td align="center">0.64</td>
<td align="center">PM2 break sol. increased</td>
</tr>
<tr>
<td align="center">8</td>
<td align="center">With large areas</td>
<td align="center">4.0 &#xb1; 0.1</td>
<td align="center">5 out of 5</td>
<td align="center">6 &#x223c;18 (3% &#x223c;9%)</td>
<td align="center">0.28</td>
<td align="center">PM2 break sol. increased</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn6">
<label>
<sup>a</sup>
</label>
<p>
<inline-formula id="inf34">
<mml:math id="m61">
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mo>&#x304;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula> means average processing time.</p>
</fn>
<fn id="Tfn7">
<label>
<sup>b</sup>
</label>
<p>
<inline-formula id="inf35">
<mml:math id="m62">
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>V</mml:mi>
</mml:mrow>
<mml:mo>&#x304;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula> means average variance of desired time.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Conversely, it is also important in real-world problems to consider multiple targets for optimization. In this paper, we aimed to optimize total travel time and total witnessing time, but various optimization targets depend on the needs, such as optimization to minimize the number of adjusters to be dispatched or optimization to complete all witnessing in a minimum number of operating days at the expense of operating time. These will be discussed in future prospects.</p>
</sec>
</sec>
<sec sec-type="conclusion" id="s4">
<title>4 Conclusion</title>
<p>We formulate a real-world problem, the adjuster route optimization problem (ARP) in a QUBO form, and propose a method to solve it using quantum annealing. ARP is an optimization problem that extends VRP and can be solved using a 2-phase-heuristics approach, as in [<xref ref-type="bibr" rid="B23">23</xref>]. In the clustering phase, to determine the buildings to be witnessed by the adjuster, constraints were introduced to achieve adjuster/building matching and distribute the required and desired time for witnessing without bias for the next routing phase. In the routing phase, to determine the order of witnessing by the adjuster, the constraint was introduced to satisfy the desired time for witnessing that each building has. These constraints may be applicable not only to ARP but also to other real-world problems related to VRP.</p>
<p>Furthermore, we confirmed that our formulation works correctly by conducting numerical experiments using the actual quantum annealing machine D-Wave. We also confirmed the superiority of D-Wave Leap&#x2019;s Hybrid Solver Service over classical algorithms. We hope that our research will help speed up witnessing operations during disasters using quantum computers.</p>
<p>While the constraints introduced in this paper alone are sufficient to make the model practical, additional conditions will likely need to be considered to actually implement the model in witnessing operations. For example, it may be necessary to consider break times, such as lunch (this can be realized by &#x201c;state&#x201d; in [<xref ref-type="bibr" rid="B32">32</xref>]), or routes that cannot be taken in the event of a disaster in the distance matrix. It is also a challenge to add and validate constraints to the model that may be necessary in the future.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s5">
<title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/supplementary material. Further inquiries can be directed to the corresponding author.</p>
</sec>
<sec id="s6">
<title>Author contributions</title>
<p>NM mainly contributed to the construction and verification of the clustering Hamiltonian and performed all the numerical experiments through the clustering and routing phases. SF mainly contributed to routing Hamiltonian, especially the constraint term newly introduced, and conducted the numerical experiment of routing for verification. All authors contributed to the article and approved the submitted version.</p>
</sec>
<ack>
<p>The authors would like to thank Jun Mino for helpful discussions about ARP. The authors also want to thank the member of the Digital Promotion Department at Cognivision Inc., especially Masakazu Sato, Kazutaka Murakami, and Mitsuaki Nozawa for the careful reading of the article and the suggestions for improvements.</p>
</ack>
<sec sec-type="COI-statement" id="s7">
<title>Conflict of interest</title>
<p>NM and SF were employed by Cognivision Inc.</p>
</sec>
<sec sec-type="disclaimer" id="s8">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors, and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<fn-group>
<fn id="fn2">
<label>1</label>
<p>Non-deterministic polynomial time.</p>
</fn>
<fn id="fn3">
<label>2</label>
<p>Equation <xref ref-type="disp-formula" rid="e4">4</xref> contains only the leading-order term. More rigorous discussion is given by Kimura and Nishimori [<xref ref-type="bibr" rid="B34">34</xref>].</p>
</fn>
<fn id="fn4">
<label>3</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://docs.ocean.dwavesys.com/en/stable/">https://docs.ocean.dwavesys.com/en/stable/</ext-link>.</p>
</fn>
<fn id="fn5">
<label>4</label>
<p>As the total operating hours is 8&#xa0;h (<xref ref-type="table" rid="T1">Table 1</xref>) and the unit time is &#x394;<italic>t</italic> &#x3d; 0.25 (<xref ref-type="table" rid="T2">Table 2</xref>), the number of time intervals is 8/0.25 &#x3d; 32, according to the correspondence Eq. <xref ref-type="disp-formula" rid="e14">14</xref>.</p>
</fn>
<fn id="fn6">
<label>5</label>
<p>For ease of viewing, the figure shows only three of the 20 clusters contained in each instance.</p>
</fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="B1">
<label>1.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Karp</surname>
<given-names>RM</given-names>
</name>
</person-group>. <article-title>Reducibility among combinatorial problems</article-title>. <source>Complexity Comput Computations</source> (<year>1972</year>) <volume>85</volume>:<fpage>85</fpage>&#x2013;<lpage>103</lpage>. <pub-id pub-id-type="doi">10.1007/978-1-4684-2001-2_9</pub-id>
</citation>
</ref>
<ref id="B2">
<label>2.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kadowaki</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Nishimori</surname>
<given-names>H</given-names>
</name>
</person-group>. <article-title>Quantum annealing in the transverse Ising model</article-title>. <source>Phys Rev E</source> (<year>1998</year>) <volume>58</volume>:<fpage>5355</fpage>&#x2013;<lpage>63</lpage>. <pub-id pub-id-type="doi">10.1103/PhysRevE.58.5355</pub-id>
</citation>
</ref>
<ref id="B3">
<label>3.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Johnson</surname>
<given-names>MW</given-names>
</name>
<name>
<surname>Amin</surname>
<given-names>MHS</given-names>
</name>
<name>
<surname>Gildert</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Lanting</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Hamze</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Dickson</surname>
<given-names>N</given-names>
</name>
<etal/>
</person-group> <article-title>Quantum annealing with manufactured spins</article-title>. <source>Nature</source> (<year>2011</year>) <volume>473</volume>:<fpage>194</fpage>&#x2013;<lpage>8</lpage>. <pub-id pub-id-type="doi">10.1038/nature10012</pub-id>
</citation>
</ref>
<ref id="B4">
<label>4.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Venturelli</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Marchand</surname>
<given-names>DJJ</given-names>
</name>
<name>
<surname>Rojo</surname>
<given-names>G</given-names>
</name>
</person-group>. <article-title>Quantum annealing implementation of job-shop scheduling</article-title>. <source>COPLAS</source> (<year>2016</year>). <pub-id pub-id-type="doi">10.48550/arXiv.1506.08479</pub-id>
</citation>
</ref>
<ref id="B5">
<label>5.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ikeda</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Nakamura</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Humble</surname>
<given-names>TS</given-names>
</name>
</person-group>. <article-title>Application of quantum annealing to nurse scheduling problem</article-title>. <source>Scientific Rep</source> (<year>2019</year>) <volume>9</volume>:<fpage>12837</fpage>. <pub-id pub-id-type="doi">10.1038/s41598-019-49172-3</pub-id>
</citation>
</ref>
<ref id="B6">
<label>6.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Venturelli</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Kondratyev</surname>
<given-names>A</given-names>
</name>
</person-group>. <article-title>Reverse quantum annealing approach to portfolio optimization problems</article-title>. <source>Quan Machine Intelligence</source> (<year>2019</year>) <volume>1</volume>:<fpage>17</fpage>&#x2013;<lpage>30</lpage>. <pub-id pub-id-type="doi">10.1007/s42484-019-00001-w</pub-id>
</citation>
</ref>
<ref id="B7">
<label>7.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Neven</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Denchev</surname>
<given-names>VS</given-names>
</name>
<name>
<surname>Rose</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Macready</surname>
<given-names>WG</given-names>
</name>
</person-group>. <article-title>QBoost: Large scale classifier training with adiabatic quantum optimization</article-title>. <source>JMLR: Workshop Conf Proc</source> (<year>2012</year>) <volume>25</volume>:<fpage>333</fpage>&#x2013;<lpage>48</lpage>.</citation>
</ref>
<ref id="B8">
<label>8.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>O&#x2019;Malley</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Vesselinov</surname>
<given-names>VV</given-names>
</name>
<name>
<surname>Alexandrov</surname>
<given-names>BS</given-names>
</name>
<name>
<surname>Alexandrov</surname>
<given-names>L</given-names>
</name>
</person-group>. <source>Nonnegative/binary matrix factorization with a D-Wave quantum annealer</source> (<year>2017</year>). <comment>
<italic>arXiv:1704</italic>.<italic>01605</italic>
</comment>. <pub-id pub-id-type="doi">10.1371/journal.pone.0206653</pub-id>
</citation>
</ref>
<ref id="B9">
<label>9.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>von Dollen</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Neukart</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Weimer</surname>
<given-names>D</given-names>
</name>
<name>
<surname>B&#xe4;ck</surname>
<given-names>T</given-names>
</name>
</person-group>. <source>Quantum-assisted feature selection for vehicle price prediction modeling</source> (<year>2021</year>). <comment>
<italic>arXiv:2104</italic>.<italic>04049</italic>
</comment>. <pub-id pub-id-type="doi">10.48550/arXiv.2104.04049</pub-id>
</citation>
</ref>
<ref id="B10">
<label>10.</label>
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Benkner</surname>
<given-names>MS</given-names>
</name>
<name>
<surname>Golyanik</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Theobalt</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Moeller</surname>
<given-names>M</given-names>
</name>
</person-group>. <article-title>Adiabatic quantum graph matching with permutation matrix constraints</article-title>. In: <conf-name>2020 International Conference on 3D Vision (3DV)</conf-name>. <publisher-loc>Fukuoka, Japan</publisher-loc>: <publisher-name>IEEE</publisher-name> (<year>2020</year>). <pub-id pub-id-type="doi">10.1109/3DV50981.2020.00068</pub-id>
</citation>
</ref>
<ref id="B11">
<label>11.</label>
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Birdal</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Golyanik</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Theobalt</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Guibas</surname>
<given-names>L</given-names>
</name>
</person-group>. <article-title>Quantum permutation synchronization</article-title>. In: <conf-name>2021 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>. <publisher-loc>Nashville, TN, USA</publisher-loc>: <publisher-name>IEEE</publisher-name> (<year>2021</year>). <pub-id pub-id-type="doi">10.1109/CVPR46437.2021.01292</pub-id>
</citation>
</ref>
<ref id="B12">
<label>12.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xia</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Bian</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Kais</surname>
<given-names>S</given-names>
</name>
</person-group>. <article-title>Electronic structure calculations and the Ising Hamiltonian</article-title>. <source>The J Phys Chem B</source> (<year>2017</year>) <volume>122</volume>:<fpage>3384</fpage>&#x2013;<lpage>95</lpage>. <pub-id pub-id-type="doi">10.1021/acs.jpcb.7b10371</pub-id>
</citation>
</ref>
<ref id="B13">
<label>13.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Streif</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Neukart</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Leib</surname>
<given-names>M</given-names>
</name>
</person-group>. <article-title>Solving quantum chemistry problems with a D-wave quantum annealer: First international workshop, QTOP 2019, Munich, Germany, March 18, 2019, proceedings</article-title>. In: <source>Quantum Technology and optimization problems</source> (<year>2017</year>). p. <fpage>111</fpage>&#x2013;<lpage>22</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-030-14082-3_10</pub-id>
</citation>
</ref>
<ref id="B14">
<label>14.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ohzeki</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Miki</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Miyama</surname>
<given-names>MJ</given-names>
</name>
<name>
<surname>Terabe</surname>
<given-names>M</given-names>
</name>
</person-group>. <article-title>Control of automated guided vehicles without collision by quantum annealer and digital devices</article-title>. <source>Front Comput Sci</source> (<year>2019</year>) <volume>1</volume>. <pub-id pub-id-type="doi">10.3389/fcomp.2019.00009</pub-id>
</citation>
</ref>
<ref id="B15">
<label>15.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Neukart</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Compostella</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Seidel</surname>
<given-names>C</given-names>
</name>
<name>
<surname>von Dollen</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Yarkoni</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Parney</surname>
<given-names>B</given-names>
</name>
</person-group>. <article-title>Traffic flow optimization using a quantum annealer</article-title>. <source>Front ICT</source> (<year>2017</year>) <volume>4</volume>. <pub-id pub-id-type="doi">10.3389/fict.2017.00029</pub-id>
</citation>
</ref>
<ref id="B16">
<label>16.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Nishimura</surname>
<given-names>N</given-names>
</name>
<name>
<surname>Tanahashi</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Suganuma</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Miyama</surname>
<given-names>MJ</given-names>
</name>
<name>
<surname>Ohzeki</surname>
<given-names>M</given-names>
</name>
</person-group>. <article-title>Item listing optimization for E-commerce websites based on diversity</article-title>. <source>Front Comput Sci</source> (<year>2019</year>) <volume>1</volume>. <pub-id pub-id-type="doi">10.3389/fcomp.2019.00002</pub-id>
</citation>
</ref>
<ref id="B17">
<label>17.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Dantzig</surname>
<given-names>GB</given-names>
</name>
<name>
<surname>Ramser</surname>
<given-names>JH</given-names>
</name>
</person-group>. <article-title>The truck dispatching problem</article-title>. <source>Manage Sci</source> (<year>1959</year>) <volume>6</volume>:<fpage>80</fpage>&#x2013;<lpage>91</lpage>. <pub-id pub-id-type="doi">10.1287/mnsc.6.1.80</pub-id>
</citation>
</ref>
<ref id="B18">
<label>18.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Braysy</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Gendreau</surname>
<given-names>M</given-names>
</name>
</person-group>. <article-title>Vehicle routing problem with time windows, part I: Route construction and local search algorithms</article-title>. <source>Transportation Sci</source> (<year>2005</year>) <volume>39</volume>:<fpage>104</fpage>&#x2013;<lpage>18</lpage>. <pub-id pub-id-type="doi">10.1287/trsc.1030.0056</pub-id>
</citation>
</ref>
<ref id="B19">
<label>19.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>de Oliveira</surname>
<given-names>HCB</given-names>
</name>
<name>
<surname>Vasconcelos</surname>
<given-names>GC</given-names>
</name>
</person-group>. <article-title>A hybrid search method for the vehicle routing problem with time windows</article-title>. <source>Ann Operations Res</source> (<year>2010</year>) <volume>180</volume>:<fpage>125</fpage>&#x2013;<lpage>44</lpage>. <pub-id pub-id-type="doi">10.1007/s10479-008-0487-y</pub-id>
</citation>
</ref>
<ref id="B20">
<label>20.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ralphs</surname>
<given-names>TK</given-names>
</name>
<name>
<surname>Kopman</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Pulleyblank</surname>
<given-names>WR</given-names>
</name>
<name>
<surname>Trotter</surname>
<given-names>LE</given-names>
</name>
</person-group>. <article-title>On the capacitated vehicle routing problem</article-title>. <source>Math Programming</source> (<year>2003</year>) <volume>94</volume>:<fpage>343</fpage>&#x2013;<lpage>59</lpage>. <pub-id pub-id-type="doi">10.1007/s10107-002-0323-0</pub-id>
</citation>
</ref>
<ref id="B21">
<label>21.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Boothby</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Bunyk</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Raymond</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Roy</surname>
<given-names>A</given-names>
</name>
</person-group>. <source>Next-generation topology of D-Wave quantum processors</source> (<year>2020</year>). <comment>
<italic>arXiv:2003</italic>.<italic>00133</italic>
</comment>. <pub-id pub-id-type="doi">10.48550/arXiv.2003.00133</pub-id>
</citation>
</ref>
<ref id="B22">
<label>22.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Laporte</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Semet</surname>
<given-names>F</given-names>
</name>
</person-group>. <article-title>Classical heuristics for the capacitated VRP</article-title>. In: <source>The vehicle routing problem</source>. <publisher-loc>Philadelphia, Pennsylvania, USA</publisher-loc>: <publisher-name>Society for Industrial and Applied Mathematics</publisher-name> (<year>2002</year>). <comment>chap. 5</comment>.</citation>
</ref>
<ref id="B23">
<label>23.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Feld</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Roch</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Gabor</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Seidel</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Neukart</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Galter</surname>
<given-names>I</given-names>
</name>
<etal/>
</person-group> <article-title>A hybrid solution method for the capacitated vehicle routing problem using a quantum annealer</article-title>. <source>Front ICT</source> (<year>2019</year>) <volume>6</volume>:<fpage>1</fpage>&#x2013;<lpage>13</lpage>. <pub-id pub-id-type="doi">10.3389/fict.2019.00013</pub-id>
</citation>
</ref>
<ref id="B24">
<label>24.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Laporte</surname>
<given-names>G</given-names>
</name>
</person-group>. <article-title>The traveling salesman problem: An overview of exact and approximate algorithms</article-title>. <source>Eur J Oper Res</source> (<year>1992</year>) <volume>59</volume>:<fpage>231</fpage>&#x2013;<lpage>47</lpage>. <pub-id pub-id-type="doi">10.1016/0377-2217(92)90138-Y</pub-id>
</citation>
</ref>
<ref id="B25">
<label>25.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tsukamoto</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Takatsu</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Matsubara</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Tamura</surname>
<given-names>H</given-names>
</name>
</person-group>. <article-title>An accelerator architecture for combinatorial optimization problems</article-title>. <source>Fujitsu Sci</source> (<year>2017</year>) <volume>53</volume>.</citation>
</ref>
<ref id="B26">
<label>26.</label>
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Yoshimura</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Yamaoka</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Aoki</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Mizuno</surname>
<given-names>H</given-names>
</name>
</person-group>. <article-title>Spatial computing architecture using randomness of memory cell stability under voltage control</article-title>. In: <conf-name>2013 European Conference on Circuit Theory and Design (ECCTD)</conf-name>. <publisher-loc>Dresden, Germany</publisher-loc>: <publisher-name>IEEE</publisher-name> (<year>2013</year>). <pub-id pub-id-type="doi">10.1109/ECCTD.2013.6662276</pub-id>
</citation>
</ref>
<ref id="B27">
<label>27.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yarkoni</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Raponi</surname>
<given-names>E</given-names>
</name>
<name>
<surname>B&#xe4;ck</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Schmitt</surname>
<given-names>S</given-names>
</name>
</person-group>. <article-title>Quantum annealing for industry applications: Introduction and review</article-title>. <source>Rep Prog Phys</source> (<year>2022</year>) <volume>85</volume>:<fpage>104001</fpage>. <pub-id pub-id-type="doi">10.1088/1361-6633/ac8c54</pub-id>
</citation>
</ref>
<ref id="B28">
<label>28.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lucas</surname>
<given-names>A</given-names>
</name>
</person-group>. <article-title>Ising formulations of many NP problems</article-title>. <source>Front Phys</source> (<year>2014</year>) <volume>2</volume>. <pub-id pub-id-type="doi">10.3389/fphy.2014.00005</pub-id>
</citation>
</ref>
<ref id="B29">
<label>29.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Yonaga</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Miyama</surname>
<given-names>MJ</given-names>
</name>
<name>
<surname>Ohzeki</surname>
<given-names>M</given-names>
</name>
</person-group>. <source>Solving inequality-constrained binary optimization problems on quantum annealer</source> (<year>2020</year>). <comment>
<italic>arXiv:2012</italic>.<italic>06119</italic>
</comment>. <pub-id pub-id-type="doi">10.48550/arXiv.2012.06119</pub-id>
</citation>
</ref>
<ref id="B30">
<label>30.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Dash</surname>
<given-names>S</given-names>
</name>
<name>
<surname>G&#xfc;nl&#xfc;k</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Lodi</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Tramontani</surname>
<given-names>A</given-names>
</name>
</person-group>. <article-title>A time bucket formulation for the traveling salesman problem with time windows</article-title>. <source>Informs J Comput</source> (<year>2010</year>) <volume>24</volume>:<fpage>132</fpage>&#x2013;<lpage>47</lpage>. <pub-id pub-id-type="doi">10.1287/ijoc.1100.0432</pub-id>
</citation>
</ref>
<ref id="B31">
<label>31.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kara</surname>
<given-names>I</given-names>
</name>
<name>
<surname>Derya</surname>
<given-names>T</given-names>
</name>
</person-group>. <article-title>Formulations for minimizing tour duration of the traveling salesman problem with time windows</article-title>. <source>Proced Econ Finance</source> (<year>2015</year>) <volume>26</volume>:<fpage>1026</fpage>&#x2013;<lpage>34</lpage>. <pub-id pub-id-type="doi">10.1016/S2212-5671(15)00926-0</pub-id>
</citation>
</ref>
<ref id="B32">
<label>32.</label>
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Irie</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Wongpaisarnsin</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Terabe</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Miki</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Taguchi</surname>
<given-names>S</given-names>
</name>
</person-group>. <article-title>Quantum annealing of vehicle routing problem with time, state and capacity</article-title>. In: <person-group person-group-type="editor">
<name>
<surname>Feld</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Linnhoff-Popien</surname>
<given-names>C</given-names>
</name>
</person-group>, editors. <source>Quantum Technology and optimization problems</source>. <source>QTOP 2019. Lecture notes in computer science</source>. <publisher-loc>Cham</publisher-loc>: <publisher-name>Springer</publisher-name> (<year>2019</year>). p. <fpage>145</fpage>&#x2013;<lpage>56</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-030-14082-3_13</pub-id>
</citation>
</ref>
<ref id="B33">
<label>33.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kirkpatrick</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Gelatt</surname>
<given-names>CD</given-names>
</name>
<name>
<surname>Vecchi</surname>
<given-names>MP</given-names>
</name>
</person-group>. <article-title>Optimization by simulated annealing</article-title>. <source>Science</source> (<year>1986</year>) <volume>220</volume>:<fpage>671</fpage>&#x2013;<lpage>80</lpage>. <pub-id pub-id-type="doi">10.1126/science.220.4598.671</pub-id>
</citation>
</ref>
<ref id="B34">
<label>34.</label>
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kimura</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Nishimori</surname>
<given-names>H</given-names>
</name>
</person-group>. <article-title>Rigorous convergence condition for quantum annealing</article-title>. <source>J Phys A: Math Theor</source> (<year>2022</year>) <volume>55</volume>:<fpage>435302</fpage>. <pub-id pub-id-type="doi">10.1088/1751-8121/ac9dce</pub-id>
</citation>
</ref>
</ref-list>
</back>
</article>