[{"data":1,"prerenderedAt":2049},["ShallowReactive",2],{"handbook-\u002Fhandbook\u002Fengineering\u002Fproduct\u002Findustrial-ai-use-case-demos\u002F":3,"handbook-nav":1176},{"id":4,"title":5,"body":6,"description":17,"extension":1169,"meta":1170,"navigation":1171,"path":1172,"seo":1173,"stem":1174,"__hash__":1175},"handbook\u002Fhandbook\u002Fengineering\u002Fproduct\u002Findustrial-ai-use-case-demos.md","Industrial AI Use Case Demos",{"type":7,"value":8,"toc":1146},"minimark",[9,14,18,21,41,46,51,54,57,61,115,119,144,148,151,154,174,178,183,190,194,217,221,224,228,231,235,238,241,269,272,328,332,337,341,444,449,469,474,528,533,547,552,566,571,585,591,595,600,604,718,723,740,744,811,816,827,831,845,850,854,859,863,971,975,992,996,1105,1109,1123,1127,1141],[10,11,13],"h1",{"id":12},"industrial-ai-use-case-demos","Industrial AI use case demos",[15,16,17],"p",{},"As a manufacturing iPaaS provider, AI and feature development needs to be constantly tested in scenarios as close as possible to real world usage. This helps quicker iteration on our AI application-building capabilities, and shows external stakeholders and future customers the capabilities FlowFuse has and the pace of our development.",[15,19,20],{},"The demos focus on three industrial AI use cases: production optimisation, AI context orchestration, and smart alerting. Two outputs are required from this program:",[22,23,24,33],"ol",{},[25,26,27,28,32],"li",{},"Footage as ",[29,30,31],"em",{},"input"," for cleanly recorded demo's we can put in front of prospects and users, showing the platform being used end to end.",[25,34,35,36,40],{},"GitHub issues for ",[37,38,39],"strong",{},"every"," point of friction found. With it, the AI engineering team can rank what to fix now, next month, and later.",[42,43,45],"h2",{"id":44},"recording-and-filming","Recording and Filming",[47,48,50],"h3",{"id":49},"what-is-being-demod","What is being demo'd",[15,52,53],{},"First and foremost, the product is being tested, not the person filming. The demo tests how long it takes one person, using AI and the platform as they exist today, to go from an empty team to a working use case, running against real equipment.",[15,55,56],{},"Secondly, the demo builds one of the use cases described later on this page. It takes one hour and the recording is a point-to-point representation: no editing, one take. A demo takes an hour, unless the complete result was achieved sooner. If the full demo cannot be built in an hour, that is a valid result, as it shows where time can be gained.",[47,58,60],{"id":59},"rules-for-the-demo","Rules for the demo",[22,62,63,66,69,109,112],{},[25,64,65],{},"One take. No pauses, no second take when things go south. The product fails if\u002Fwhen things go wrong; that's not the recorder's fault, it shows what went right and wrong.",[25,67,68],{},"Start from the empty team, on camera. Show it is empty.",[25,70,71,72],{},"Use only what's available to customers too.\n",[73,74,75,95],"ul",{},[25,76,77,78],{},"Yes:\n",[73,79,80,83,86,89,92],{},[25,81,82],{},"Blueprints",[25,84,85],{},"FlowFuse Expert \u002F third-party MCP",[25,87,88],{},"FlowFuse LLM and MCP nodes",[25,90,91],{},"Docs",[25,93,94],{},"Google \u002F ChatGPT",[25,96,97,98],{},"No:\n",[73,99,100,103,106],{},[25,101,102],{},"Pre-made flows \u002F snapshots",[25,104,105],{},"Content you have access to but new users don't",[25,107,108],{},"Slack hotline to other engineers during the demo",[25,110,111],{},"Narrate what you want to achieve, think, hope to get as a result. Verbalize details you read and pick up on, or details you wanted to see\u002Fread but are missing.",[25,113,114],{},"When you leave the product — opening the docs, a Google search, initiating a terminal SSH session, or so — record these too.",[47,116,118],{"id":117},"setup-the-demo","Setup the demo",[22,120,121,124,127,130],{},[25,122,123],{},"Install OBS, ensure you can record your screen and audio (see also OBS settings below).",[25,125,126],{},"Turn on \"Do Not Disturb\". Ensure your notifications are off, chat and mail closed, no customer names, tokens, or credentials visible at any point. Nothing is edited afterwards, so anything on screen is published.",[25,128,129],{},"A fresh team, empty, on the tier a customer would have, with the certified nodes each use case needs available to it. No pre-existing instances, no library content you made earlier.",[25,131,132,133],{},"A data source ready, as listed under the use case you are building. Do not use random or simulated values — step through the hard part of connecting to the data source. Use real hardware with protocols like:\n",[22,134,135,138,141],{},[25,136,137],{},"Modbus TCP",[25,139,140],{},"OPC-UA",[25,142,143],{},"MQTT + legacy protocol",[47,145,147],{"id":146},"obs-settings","OBS settings",[15,149,150],{},"OBS is open source video\u002Faudio capture software that's great for this demo. Record at least your screen and audio; having your webcam recording would be appreciated.",[15,152,153],{},"The settings to work with:",[73,155,156,159,162,165,168,171],{},[25,157,158],{},"1920x1080, 30 fps, full screen capture of the display you will work on.",[25,160,161],{},"Recording format MKV, remux to MP4 afterwards.",[25,163,164],{},"Quality: CRF 20 or 6000 kbps, hardware encoder if available.",[25,166,167],{},"Microphone on a separate audio track. Narration is required.",[25,169,170],{},"Check free disk space is above 20 GB before starting.",[25,172,173],{},"Record, do not stream.",[47,175,177],{"id":176},"post-demo-action-items","Post-demo action items",[179,180,182],"h4",{"id":181},"github-issues","GitHub issues",[15,184,185,186,189],{},"The list of blockers you ran into, or items to smooth over, should each have an attached issue. Many issues are likely already reported and being scheduled — search for those issues and leave a comment ",[29,187,188],{},"for each demo you ran into this issue"," so engineers can resolve it. Keep a list of the issues.",[179,191,193],{"id":192},"upload-the-recording","Upload the recording",[22,195,196,208,211,214],{},[25,197,198,199,203,204,207],{},"Remux to MP4. Name it ",[200,201,202],"code",{},"DEMO_\u003Cusecase>_\u003Cyourname>_\u003CYYYYMMDD>.mp4",", for example ",[200,205,206],{},"DEMO_smart-alerting_jane_20261012.mp4",".",[25,209,210],{},"Upload the raw file to our internal Google Drive. Do not edit or trim.",[25,212,213],{},"Clean up the team, and other created assets that were part of the demo.",[25,215,216],{},"Post the list of issues in a text file next to the demo.",[179,218,220],{"id":219},"iterate-on-this-page","Iterate on this page",[15,222,223],{},"Help other team members by answering any questions you had to figure out yourself to complete your demo, and add them to the handbook. Update the script where possible, and where you can make it more realistic.",[179,225,227],{"id":226},"ping-zj","Ping ZJ",[15,229,230],{},"ZJ will review each demo, and the issues we ran into. Point him to the directory where your recording is. If there's a blocker or must-fix item, let him know directly so it can be actioned prior to watching the full demo.",[42,232,234],{"id":233},"use-cases-to-build","Use cases to build",[15,236,237],{},"Each demo builds one of the following use cases. They are stretch goals: you will probably not deliver the full spec in an hour, and where you stop is part of the result. If you record more than one demo, cover all three use cases before you record a second demo of the same one.",[15,239,240],{},"Every use case is written the same way:",[73,242,243,249,255],{},[25,244,245,248],{},[37,246,247],{},"The story:"," who has the problem, and the moment it hurts. Narrate from that person's point of view, because that is what a prospect watching the footage will relate to.",[25,250,251,254],{},[37,252,253],{},"FlowFuse on show:"," the platform features the story should exercise. Tick them off as you go. A feature you meant to use but could not is a GitHub issue.",[25,256,257,260,261,264,265,268],{},[37,258,259],{},"What to build",", ",[37,262,263],{},"the hour"," and ",[37,266,267],{},"done looks like:"," the spec, a suggested pace, and the moment that proves it worked.",[15,270,271],{},"The three use cases share a shape on purpose: an edge instance next to the equipment, a hub instance with FlowFuse Tables as the application's memory, and AI that works through the same permissions as everyone else. Across all three, a viewer should see Edge, Hub, Tables, MCP and FlowFuse Expert working together, not as separate features.",[273,274,275,291],"table",{},[276,277,278],"thead",{},[279,280,281,285,288],"tr",{},[282,283,284],"th",{},"Use case",[282,286,287],{},"What it proves",[282,289,290],{},"FlowFuse at its centre",[292,293,294,306,317],"tbody",{},[279,295,296,300,303],{},[297,298,299],"td",{},"Production optimisation",[297,301,302],{},"AI can tune a physical process and save money, with a person approving every change",[297,304,305],{},"Edge instances, Modbus, Team MQTT Broker, FlowFuse Tables, LLM nodes, device groups",[279,307,308,311,314],{},[297,309,310],{},"AI context orchestration",[297,312,313],{},"Data nobody can reach becomes tools any approved agent can use",[297,315,316],{},"FlowFuse MCP server, MCP nodes, FlowFuse Tables, Insights mode, DevOps Pipelines",[279,318,319,322,325],{},[297,320,321],{},"Smart alerting",[297,323,324],{},"An alert arrives with enough context to act on straight away, and nothing is lost at shift change",[297,326,327],{},"FlowFuse Tables, LLM nodes, Slack, Dashboard, MCP nodes",[47,329,331],{"id":330},"production-optimisation-wells-and-pumping","Production optimisation: wells and pumping",[15,333,334,336],{},[37,335,247],{}," A production engineer looks after 40 rod-pumped wells spread over a field with patchy cellular coverage. Every pump runs at the speed it was set to months ago. Some are pumping off, wasting power and hammering their rods. Others are running too slowly and leaving oil in the ground. She finds out which is which by driving out to each pad. The demo shows her doing it from a dashboard instead: the platform spots the problem wells, AI recommends a new setting, she approves it, and the change reaches the pump controller. The same pattern applies to any pumping station, such as water, wastewater or transfer pumps.",[15,338,339],{},[37,340,253],{},[273,342,343,353],{},[276,344,345],{},[279,346,347,350],{},[282,348,349],{},"Step",[282,351,352],{},"Feature",[292,354,355,369,381,396,408,420,428,436],{},[279,356,357,360],{},[297,358,359],{},"Read the pump controller or drive",[297,361,362,363,368],{},"Edge instance on a gateway at the pad, ",[364,365,367],"a",{"href":366},"\u002Fdocs\u002Fflowfuse-nodes\u002Fedge\u002Fmodbus\u002F","Modbus"," certified node",[279,370,371,374],{},[297,372,373],{},"Survive the cellular link dropping",[297,375,376,380],{},[364,377,379],{"href":378},"\u002Fblueprints\u002Fgetting-started\u002Fstore-and-forward\u002F","Store and forward"," blueprint on the edge instance",[279,382,383,386],{},[297,384,385],{},"Move data from pads to the field view",[297,387,388,392,393],{},[364,389,391],{"href":390},"\u002Fdocs\u002Fuser\u002Fteambroker\u002F","Team MQTT Broker"," with the FlowFuse MQTT nodes, topics as ",[200,394,395],{},"field\u002Fpad\u002Fwell\u002Fmeasurement",[279,397,398,401],{},[297,399,400],{},"Keep well tests, settings history and approvals",[297,402,403,407],{},[364,404,406],{"href":405},"\u002Fdocs\u002Fuser\u002Fff-tables\u002F","FlowFuse Tables"," on the hub instance, queried with the Query node",[279,409,410,413],{},[297,411,412],{},"Classify the well and recommend a setting",[297,414,415,419],{},[364,416,418],{"href":417},"\u002Fdocs\u002Fflowfuse-nodes\u002Fai\u002Fllm-nodes\u002F","LLM nodes"," on the hub instance",[279,421,422,425],{},[297,423,424],{},"Give each engineer their own wells",[297,426,427],{},"Dashboard with personalised multi-user views",[279,429,430,433],{},[297,431,432],{},"Roll the improved edge flow to every pad",[297,434,435],{},"Device groups and a DevOps Pipeline, with a snapshot before the change",[279,437,438,441],{},[297,439,440],{},"Build faster",[297,442,443],{},"FlowFuse Expert in the editor, for the Modbus mapping, the SQL and the dashboard",[15,445,446],{},[37,447,448],{},"Sources:",[73,450,451,454,457,460,463,466],{},[25,452,453],{},"A rod pump controller or VSD (variable speed drive) over Modbus TCP or RTU: strokes per minute or drive frequency, motor current, motor power, runtime, and run\u002Fstop state.",[25,455,456],{},"The surface dynamometer card from the rod pump controller: load against rod position for each stroke. This is the richest single signal on a rod-pumped well.",[25,458,459],{},"For ESPs (electric submersible pumps): intake pressure, discharge pressure, motor temperature and vibration from the downhole gauge, read through the drive.",[25,461,462],{},"Tubing and casing pressure, and a flow meter or the latest well test for production rate.",[25,464,465],{},"Oil price and power tariff as configuration.",[25,467,468],{},"For the demo: real field hardware is rarely available, so use a pump bench, with a VSD driving a pump over Modbus TCP and real pressure and flow transmitters. The rule on real data still applies: a bench you can throttle beats a simulator.",[15,470,471],{},[37,472,473],{},"What to build:",[73,475,476,482,505,514,522],{},[25,477,478,481],{},[37,479,480],{},"Edge flow, per pad:"," poll the controller, compute pump fillage and energy per stroke locally, buffer when the link is down, and publish to the Team MQTT Broker. Accept a setpoint over MQTT and write it to the controller's holding register, only if it is inside limits configured on the edge. The edge enforces the safe range itself, whatever the hub sends.",[25,483,484,487,488,260,491,260,494,260,497,500,501,504],{},[37,485,486],{},"Tables schema on the hub:"," ",[200,489,490],{},"wells",[200,492,493],{},"well_tests",[200,495,496],{},"readings_hourly",[200,498,499],{},"recommendations"," (well, current and proposed setting, reason, expected effect, status) and ",[200,502,503],{},"setpoint_changes"," (who approved, when, and the before and after values). Use Expert to generate the SQL.",[25,506,507,510,511,513],{},[37,508,509],{},"AI in the loop:"," every hour, an LLM node receives each well's summary: fillage trend, card features such as peak and minimum load, current, rate against potential, and energy per barrel. It returns a classification (normal, fluid pound, gas interference, worn pump or unknown), a recommended setting, the expected effect, and the evidence it used. The response is parsed into the ",[200,512,499],{}," table, never acted on directly.",[25,515,516,519,520,207],{},[37,517,518],{},"Approval:"," the engineer approves, edits or rejects each recommendation on the dashboard. Approval publishes the setpoint to the pad, and the write, the person and the values are stored in ",[200,521,503],{},[25,523,524,527],{},[37,525,526],{},"Verification:"," 24 hours after a change, compare the measured effect with the prediction and write both to the recommendation.",[15,529,530],{},[37,531,532],{},"Dashboard:",[73,534,535,538,541,544],{},[25,536,537],{},"Field view: every well with its state (producing, down or pumped off), rate against potential, and deferred production today in barrels and in money.",[25,539,540],{},"Well view: rate, runtime percentage, fillage and kWh per barrel against the last 7 days, and the latest dynamometer card drawn over the well's reference card.",[25,542,543],{},"Recommendations queue: pending changes, ranked by money at stake, each with approve, edit and reject.",[25,545,546],{},"Two rankings side by side: wells by deferred production, and wells by energy per barrel. The two lists differ, and both matter.",[15,548,549],{},[37,550,551],{},"Alerting:",[73,553,554,557,560,563],{},[25,555,556],{},"Well down unexpectedly: notify the field operator immediately, with the last card and 30 minutes of motor current attached.",[25,558,559],{},"Pad gateway offline: covered by FlowFuse instance monitoring and email alerts. Show it once, by pulling the network cable on camera.",[25,561,562],{},"Fillage below the threshold for 3 consecutive strokes or more: raise a recommendation, not an alarm.",[25,564,565],{},"Motor current or temperature trending up over 24 hours at an unchanged setting: notify maintenance. This is early wear, not a production problem.",[15,567,568],{},[37,569,570],{},"The hour:",[73,572,573,576,579,582],{},[25,574,575],{},"0–15 min: edge instance on the gateway, Modbus connected, readings on MQTT.",[25,577,578],{},"15–30 min: hub instance, Tables schema, field and well dashboards.",[25,580,581],{},"30–45 min: LLM recommendation loop and the approval flow.",[25,583,584],{},"45–60 min: approve a change on camera and watch the bench respond, then push an edge flow update through the pipeline to the device group.",[15,586,587,590],{},[37,588,589],{},"Done looks like:"," A recommendation made by AI, approved by a person, written to the drive through the edge, with the pump's response visible on the dashboard and the whole trail in FlowFuse Tables.",[47,592,594],{"id":593},"ai-context-orchestration-turning-data-into-mcp","AI context orchestration: turning data into MCP",[15,596,597,599],{},[37,598,247],{}," A reliability engineer at a plant has approval to use Claude or Copilot, but it knows nothing about the plant. The answer to \"why did line 2 keep stopping last week?\" is spread across a PLC, a SQL historian, CSV exports from a legacy MES dropped on a file share, and a PDF fault code manual. Nobody has joined these, and IT will not open the historian to an AI tool. The demo shows the engineer using that same approved agent, connected to FlowFuse, to build a governed context layer. The agent then answers the question, and so can any other approved agent.",[15,601,602],{},[37,603,253],{},[273,605,606,614],{},[276,607,608],{},[279,609,610,612],{},[282,611,349],{},[282,613,352],{},[292,615,616,628,636,651,661,674,686,694,702,710],{},[279,617,618,621],{},[297,619,620],{},"Agent builds the integration flows",[297,622,623,627],{},[364,624,626],{"href":625},"\u002Fdocs\u002Fuser\u002Fmcp\u002F","FlowFuse MCP server",": an external agent (Claude, Copilot, ChatGPT) with a team grant builds and deploys the flows",[279,629,630,633],{},[297,631,632],{},"Access is limited to what was granted",[297,634,635],{},"The consent screen: specific teams only, and an expiry. Show it on camera",[279,637,638,641],{},[297,639,640],{},"Reach the live device",[297,642,643,647,648,650],{},[364,644,646],{"href":645},"\u002Fdocs\u002Fflowfuse-nodes\u002Fedge\u002Fopcua\u002F","OPC UA"," or ",[364,649,367],{"href":366}," certified nodes on an edge instance",[279,652,653,656],{},[297,654,655],{},"Curate the context",[297,657,658,660],{},[364,659,406],{"href":405},": asset model, fault codes, cleaned MES records, and document chunks",[279,662,663,666],{},[297,664,665],{},"Parse the manuals",[297,667,668,669,673],{},"The ",[364,670,672],{"href":671},"\u002Fblueprints\u002Fai\u002Frag-chat-agent\u002F","RAG chat agent"," blueprint pattern, with chunks stored in Tables",[279,675,676,679],{},[297,677,678],{},"Expose the context",[297,680,681,685],{},[364,682,684],{"href":683},"\u002Fdocs\u002Fflowfuse-nodes\u002Fmcp\u002F","MCP nodes",": MCP Tool, MCP Resource, MCP Prompt and MCP Response",[279,687,688,691],{},[297,689,690],{},"Secure the endpoint",[297,692,693],{},"FlowFuse User Authentication on the instance, with a token for the agent",[279,695,696,699],{},[297,697,698],{},"Ask from inside FlowFuse",[297,700,701],{},"FlowFuse Expert in Insights mode (beta), connected to the same MCP server",[279,703,704,707],{},[297,705,706],{},"Promote from test to production",[297,708,709],{},"A DevOps Pipeline from a dev instance to a production instance, with snapshots",[279,711,712,715],{},[297,713,714],{},"Prove what happened",[297,716,717],{},"The team audit log, showing each action the agent took",[15,719,720],{},[37,721,722],{},"Sources (use at least three, of different kinds):",[73,724,725,728,731,734,737],{},[25,726,727],{},"A live device over OPC UA or Modbus.",[25,729,730],{},"A SQL database or historian, queried read-only.",[25,732,733],{},"Files: CSV or Excel exports from a legacy system.",[25,735,736],{},"Documents: SOPs, maintenance manuals or fault code tables as PDF or text.",[25,738,739],{},"A REST API from an ERP, MES or CMMS.",[15,741,742],{},[37,743,473],{},[73,745,746,752,773,787,793,799,805],{},[25,747,748,751],{},[37,749,750],{},"Let the agent do the building."," Connect your approved agent to the FlowFuse MCP server, grant it one team, and ask it to create the application and instances and build the ingestion flows. Step in with the editor and Expert where it gets stuck. Where it got stuck is a finding.",[25,753,754,487,757,760,761,764,765,768,769,772],{},[37,755,756],{},"Tables as the context store:",[200,758,759],{},"assets"," (site, line, machine, tag names, units), ",[200,762,763],{},"fault_codes"," (code, meaning, recommended action, source document and page), ",[200,766,767],{},"downtime_events"," cleaned from the MES exports, and ",[200,770,771],{},"doc_chunks"," for the manuals. Joining and cleaning happens once here, not every time the agent asks.",[25,774,775,778,779,782,783,786],{},[37,776,777],{},"Tools for questions, not for sources."," One MCP Tool node per question an engineer actually asks. ",[200,780,781],{},"get_downtime_by_line(line, start, end)"," beats ",[200,784,785],{},"run_sql(query)",". Each tool has a clear name, a description written for the agent, a typed input schema, and output with units, timestamps and asset names.",[25,788,789,792],{},[37,790,791],{},"An MCP Resource for the asset model",", so the agent can resolve \"line 2\" to the right machines and tags without guessing.",[25,794,795,798],{},[37,796,797],{},"An MCP Prompt"," that packages a common job, such as \"investigate a downtime spike\", which steps through the right tools in order.",[25,800,801,804],{},[37,802,803],{},"Read-only by default."," If a tool writes, name it for what it writes and require confirmation.",[25,806,807,810],{},[37,808,809],{},"Promote it."," Build on a dev instance, then push through a DevOps Pipeline to production, so the MCP server the agents use in production is the one you tested.",[15,812,813],{},[37,814,815],{},"Evaluation:",[73,817,818,821,824],{},[25,819,820],{},"Before you start, write down five questions with known answers, at least two of which need more than one source. For example: \"Which line had the most downtime last week, and what does the manual say about its most frequent fault code?\"",[25,822,823],{},"At the end, ask all five on camera, in Insights mode and in the external agent. For each answer record correct, partly correct or wrong, and which tools were called.",[25,825,826],{},"Open the audit log and show what the agent did during the build.",[15,828,829],{},[37,830,570],{},[73,832,833,836,839,842],{},[25,834,835],{},"0–10 min: connect the external agent to FlowFuse on camera, including the consent screen.",[25,837,838],{},"10–35 min: the agent builds the ingestion flows and the Tables schema, with you stepping in where needed.",[25,840,841],{},"35–50 min: MCP tools, resource and prompt, with authentication switched on.",[25,843,844],{},"50–60 min: the five questions in both agents, then the audit log.",[15,846,847,849],{},[37,848,589],{}," Two different agents answer the same cross-source question correctly from the same MCP server, the tool calls are visible, and the audit log shows how it was built.",[47,851,853],{"id":852},"smart-alerting-alerts-people-can-act-on","Smart alerting: alerts people can act on",[15,855,856,858],{},[37,857,247],{}," It is 02:40 on night shift and the filler on line 3 has alarmed for the fourth time. The engineer on call gets the same message as always: a tag name and a value. They cannot tell whether it is the same fault as last Tuesday, whether anyone changed anything, or who fixed it last time. By morning three people have looked at it, the day shift knows nothing about it, and it happens again at 09:15. The demo shows the same fault arriving in Slack as one incident, addressed to the engineer by name, with its context, a probable cause, and what fixed it last time. It gets resolved, and the resolution feeds the next incident and the shift report.",[15,860,861],{},[37,862,253],{},[273,864,865,873],{},[276,866,867],{},[279,868,869,871],{},[282,870,349],{},[282,872,352],{},[292,874,875,890,900,908,918,928,936,943,955,963],{},[279,876,877,880],{},[297,878,879],{},"Collect alarms and process values",[297,881,882,883,647,885,887,888],{},"Edge instance with ",[364,884,646],{"href":645},[364,886,367],{"href":366},", publishing to the ",[364,889,391],{"href":390},[279,891,892,895],{},[297,893,894],{},"Store every alarm, incident, resolution and report",[297,896,897,899],{},[364,898,406],{"href":405}," on the hub instance, as the system of record for alerting",[279,901,902,905],{},[297,903,904],{},"Find similar past incidents",[297,906,907],{},"The Query node against Tables, with SQL generated by Expert",[279,909,910,913],{},[297,911,912],{},"Draft the probable cause",[297,914,915,917],{},[364,916,418],{"href":417},", grounded in what the Query node returned",[279,919,920,923],{},[297,921,922],{},"Find the right procedure",[297,924,925,927],{},[364,926,672],{"href":671}," blueprint pattern over the SOPs",[279,929,930,933],{},[297,931,932],{},"Greet the engineer in Slack",[297,934,935],{},"A Slack app posting from the flow, mentioning the assigned engineer, with buttons that call back into an HTTP endpoint on the instance",[279,937,938,941],{},[297,939,940],{},"Incident console and \"my incidents\"",[297,942,427],{},[279,944,945,948],{},[297,946,947],{},"Shift report",[297,949,950,954],{},[364,951,953],{"href":952},"\u002Fblueprints\u002Fmanufacturing\u002Fpdf-report-generator\u002F","PDF report generator"," blueprint",[279,956,957,960],{},[297,958,959],{},"Ask about the night",[297,961,962],{},"MCP nodes exposing incidents from Tables, queried in Insights mode (beta) or an external agent",[279,964,965,968],{},[297,966,967],{},"Watch the watcher",[297,969,970],{},"FlowFuse instance monitoring and email alerts on the alerting instance itself",[15,972,973],{},[37,974,448],{},[73,976,977,980,983,986,989],{},[25,978,979],{},"Alarms and process values from a PLC or SCADA over OPC UA, Modbus or MQTT.",[25,981,982],{},"Work orders from a CMMS, if you have access to one.",[25,984,985],{},"SOPs and troubleshooting guides as documents.",[25,987,988],{},"The shift roster, as a table in Tables, with each engineer's Slack user ID.",[25,990,991],{},"A Slack workspace where you can install an app. Use a demo workspace, not the company one, so nothing private appears on camera.",[15,993,994],{},[37,995,473],{},[73,997,998,1027,1035,1041,1047,1056,1062,1068,1074,1083,1092],{},[25,999,1000,487,1003,1006,1007,1010,1011,1014,1015,1018,1019,1022,1023,1026],{},[37,1001,1002],{},"Tables schema:",[200,1004,1005],{},"alarm_events"," (every raw alarm), ",[200,1008,1009],{},"incidents"," (grouped alarms, severity, owner, state, and times raised, acknowledged and resolved), ",[200,1012,1013],{},"incident_context"," (attached trends, the matching SOP section, and similar past incidents), ",[200,1016,1017],{},"resolutions"," (confirmed cause and the action taken), ",[200,1020,1021],{},"shift_roster"," (engineer, assets, shift times, Slack user ID) and ",[200,1024,1025],{},"shift_reports",". Store the Slack message ID on each incident so every update lands in the same thread.",[25,1028,1029,1032,1033,207],{},[37,1030,1031],{},"Grouping:"," related alarms within a short window become one incident with one notification, not one message per tag. Chattering alarms are suppressed, but still counted in ",[200,1034,1005],{},[25,1036,1037,1040],{},[37,1038,1039],{},"Enrichment:"," each incident gets the last 30 minutes of related trends, the matching SOP section, and the three most similar past incidents with their resolutions, found with a SQL query on asset, alarm and time of day.",[25,1042,1043,1046],{},[37,1044,1045],{},"Probable cause:"," an LLM node receives only that assembled context and returns a ranked list of likely causes, each with its evidence. It is labelled as a probable cause, never stated as fact, and \"not enough information\" is an acceptable answer.",[25,1048,1049,1052,1053,1055],{},[37,1050,1051],{},"The Slack greeting:"," the incident goes to whoever is on shift for that asset in ",[200,1054,1021],{},", as a Slack message that greets them by name and hands them the problem: what happened and where, how long it has been going on, the probable cause with its evidence, what fixed the most similar past incident and who fixed it, the SOP section to follow, and a link to the incident view on the dashboard. For example: \"@Sam, the filler on line 3 has stopped 4 times since 02:10 on a low-pressure alarm. Most likely cause: a blocked supply filter. Pressure dropped before each stop, and the same fault on 14 Sep was cleared by replacing the filter (Priya). SOP 7.2 covers it.\"",[25,1057,1058,1061],{},[37,1059,1060],{},"Act from Slack:"," the message has Acknowledge, Resolve and \"Not me\" buttons. Slack calls an HTTP In endpoint on the instance, which checks Slack's request signature before it changes anything in Tables. \"Not me\" hands the incident to the next engineer on the roster for that asset. Resolve asks for the confirmed cause and the action taken, so resolution capture happens where the engineer already is.",[25,1063,1064,1067],{},[37,1065,1066],{},"One thread per incident:"," new alarms in the same incident, escalations and the resolution are posted as replies in the incident's thread, not as new messages.",[25,1069,1070,1073],{},[37,1071,1072],{},"Escalation:"," if nobody acknowledges within a configured time, the flow mentions the shift lead in the thread, then the next level. Escalation stops as soon as the incident is resolved.",[25,1075,1076,1079,1080,1082],{},[37,1077,1078],{},"Resolution capture:"," closing an incident requires confirming or correcting the cause and saying what was done. That row in ",[200,1081,1017],{}," is what makes the next similar incident faster, so show the second occurrence finding the first.",[25,1084,1085,1088,1089,1091],{},[37,1086,1087],{},"Shift report:"," at shift end, an LLM node summarises incidents raised and resolved, what is still open and who owns it, and what the next shift should watch. Every line links back to an incident. It is stored in ",[200,1090,1025],{},", rendered to PDF, and posted to the team's Slack channel at handover, with open incidents linked to their threads.",[25,1093,1094,1097,1098,260,1100,264,1102,1104],{},[37,1095,1096],{},"Ask the night:"," expose ",[200,1099,1009],{},[200,1101,1017],{},[200,1103,1025],{}," as MCP tools, so the incoming supervisor can ask \"what happened on nights, and is anything still open on line 3?\"",[15,1106,1107],{},[37,1108,532],{},[73,1110,1111,1114,1117,1120],{},[25,1112,1113],{},"Open incidents with severity, age, owner and acknowledgement state, and a \"my incidents\" view per logged-in user.",[25,1115,1116],{},"Incident view: timeline, attached trends, probable causes with evidence, and similar past incidents with how they were fixed.",[25,1118,1119],{},"Alarm health: alarms per operator per hour, the 10 most frequent alarms, and chattering alarms. Industry guidance such as ISA-18.2 treats more than a handful of alarms per operator per hour as a flood, so show where the demo stands against that.",[25,1121,1122],{},"Time to acknowledge and time to resolve, per shift.",[15,1124,1125],{},[37,1126,570],{},[73,1128,1129,1132,1135,1138],{},[25,1130,1131],{},"0–15 min: edge instance, alarm collection, Tables schema.",[25,1133,1134],{},"15–35 min: grouping, enrichment and the probable cause.",[25,1136,1137],{},"35–50 min: the Slack greeting, then acknowledge and resolve from Slack on camera, ideally on a phone.",[25,1139,1140],{},"50–60 min: trigger the same fault again and show the first incident being found, then generate the shift report and ask about it through MCP.",[15,1142,1143,1145],{},[37,1144,589],{}," A real fault reaches the assigned engineer in Slack as one message, by name, with context and a probable cause. They resolve it from Slack and the resolution is captured. The repeat fault finds that resolution, and the whole sequence appears in the shift report.",{"title":1147,"searchDepth":1148,"depth":1148,"links":1149},"",4,[1150,1164],{"id":44,"depth":1151,"text":45,"children":1152},2,[1153,1155,1156,1157,1158],{"id":49,"depth":1154,"text":50},3,{"id":59,"depth":1154,"text":60},{"id":117,"depth":1154,"text":118},{"id":146,"depth":1154,"text":147},{"id":176,"depth":1154,"text":177,"children":1159},[1160,1161,1162,1163],{"id":181,"depth":1148,"text":182},{"id":192,"depth":1148,"text":193},{"id":219,"depth":1148,"text":220},{"id":226,"depth":1148,"text":227},{"id":233,"depth":1151,"text":234,"children":1165},[1166,1167,1168],{"id":330,"depth":1154,"text":331},{"id":593,"depth":1154,"text":594},{"id":852,"depth":1154,"text":853},"md",{},null,"\u002Fhandbook\u002Fengineering\u002Fproduct\u002Findustrial-ai-use-case-demos",{"title":5,"description":17},"handbook\u002Fengineering\u002Fproduct\u002Findustrial-ai-use-case-demos","XPMPD_5ElYbV3Hm6U8awa1xmFVP2alXlP3BVc-abYOw",[1177],{"title":1178,"path":1179,"stem":1180,"children":1181},"Handbook","\u002Fhandbook","handbook",[1182,1184,1310,1342,1571,1660,1722,1864,1869],{"title":1178,"path":1179,"stem":1183},"handbook\u002Findex",{"title":1185,"group":1185,"icon":1186,"order":1187,"path":1188,"stem":1189,"children":1190},"Company","i-lucide-building-2",1,"\u002Fhandbook\u002Fcompany","handbook\u002Fcompany\u002Findex",[1191,1192,1196,1200,1204,1223,1227,1231,1235,1302,1306],{"title":1185,"path":1188,"stem":1189},{"title":1193,"path":1194,"stem":1195},"Board & Investors","\u002Fhandbook\u002Fcompany\u002Fboard","handbook\u002Fcompany\u002Fboard",{"title":1197,"path":1198,"stem":1199},"Communications","\u002Fhandbook\u002Fcompany\u002Fcommunication","handbook\u002Fcompany\u002Fcommunication",{"title":1201,"path":1202,"stem":1203},"Decision making and project management","\u002Fhandbook\u002Fcompany\u002Fdecisions","handbook\u002Fcompany\u002Fdecisions",{"title":1205,"icon":1206,"path":1207,"stem":1208,"children":1209},"Guides","i-lucide-book-open","\u002Fhandbook\u002Fcompany\u002Fguides","handbook\u002Fcompany\u002Fguides\u002Findex",[1210,1211,1215,1219],{"title":1205,"path":1207,"stem":1208},{"title":1212,"path":1213,"stem":1214},"Editing the Handbook","\u002Fhandbook\u002Fcompany\u002Fguides\u002Fgit","handbook\u002Fcompany\u002Fguides\u002Fgit",{"title":1216,"path":1217,"stem":1218},"Google Workspace","\u002Fhandbook\u002Fcompany\u002Fguides\u002Fgworkspace","handbook\u002Fcompany\u002Fguides\u002Fgworkspace",{"title":1220,"path":1221,"stem":1222},"Markdown Guide","\u002Fhandbook\u002Fcompany\u002Fguides\u002Fmarkdown","handbook\u002Fcompany\u002Fguides\u002Fmarkdown",{"title":1224,"path":1225,"stem":1226},"Organizational Structure","\u002Fhandbook\u002Fcompany\u002Forganizational-structure","handbook\u002Fcompany\u002Forganizational-structure",{"title":1228,"path":1229,"stem":1230},"Principles","\u002Fhandbook\u002Fcompany\u002Fprinciples","handbook\u002Fcompany\u002Fprinciples",{"title":1232,"path":1233,"stem":1234},"Remote Work","\u002Fhandbook\u002Fcompany\u002Fremote","handbook\u002Fcompany\u002Fremote",{"title":1236,"icon":1237,"path":1238,"stem":1239,"children":1240},"Security","i-lucide-shield","\u002Fhandbook\u002Fcompany\u002Fsecurity","handbook\u002Fcompany\u002Fsecurity\u002Findex",[1241,1242,1246,1250,1254,1258,1262,1266,1270,1274,1278,1282,1286,1290,1294,1298],{"title":1236,"path":1238,"stem":1239},{"title":1243,"path":1244,"stem":1245},"Access Control Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Faccess-control","handbook\u002Fcompany\u002Fsecurity\u002Faccess-control",{"title":1247,"path":1248,"stem":1249},"AI Development and Customer Data Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fai-development-and-customer-data","handbook\u002Fcompany\u002Fsecurity\u002Fai-development-and-customer-data",{"title":1251,"path":1252,"stem":1253},"Asset Management Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fasset-management","handbook\u002Fcompany\u002Fsecurity\u002Fasset-management",{"title":1255,"path":1256,"stem":1257},"Business Continuity & Disaster Recovery Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fbusiness-continuity","handbook\u002Fcompany\u002Fsecurity\u002Fbusiness-continuity",{"title":1259,"path":1260,"stem":1261},"Hardware Security Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fcomputer-security","handbook\u002Fcompany\u002Fsecurity\u002Fcomputer-security",{"title":1263,"path":1264,"stem":1265},"Cryptography Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fcryptography","handbook\u002Fcompany\u002Fsecurity\u002Fcryptography",{"title":1267,"path":1268,"stem":1269},"Data Management Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fdata-management","handbook\u002Fcompany\u002Fsecurity\u002Fdata-management",{"title":1271,"path":1272,"stem":1273},"Human Resources Security Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fhuman-resources","handbook\u002Fcompany\u002Fsecurity\u002Fhuman-resources",{"title":1275,"path":1276,"stem":1277},"Incident Response Plan","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fincident-response","handbook\u002Fcompany\u002Fsecurity\u002Fincident-response",{"title":1279,"path":1280,"stem":1281},"Information Security Policy and Acceptable Use Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Finformation-security","handbook\u002Fcompany\u002Fsecurity\u002Finformation-security",{"title":1283,"path":1284,"stem":1285},"Information Security Roles and Responsibilities","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Finformation-security-roles","handbook\u002Fcompany\u002Fsecurity\u002Finformation-security-roles",{"title":1287,"path":1288,"stem":1289},"Operations Security Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Foperations-security","handbook\u002Fcompany\u002Fsecurity\u002Foperations-security",{"title":1291,"path":1292,"stem":1293},"Risk Management Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Frisk-management","handbook\u002Fcompany\u002Fsecurity\u002Frisk-management",{"title":1295,"path":1296,"stem":1297},"Secure Development Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fsecure-development","handbook\u002Fcompany\u002Fsecurity\u002Fsecure-development",{"title":1299,"path":1300,"stem":1301},"Third-Party Risk Management Policy","\u002Fhandbook\u002Fcompany\u002Fsecurity\u002Fthird-party-risk-management","handbook\u002Fcompany\u002Fsecurity\u002Fthird-party-risk-management",{"title":1303,"path":1304,"stem":1305},"Strategy","\u002Fhandbook\u002Fcompany\u002Fstrategy","handbook\u002Fcompany\u002Fstrategy",{"title":1307,"path":1308,"stem":1309},"Values","\u002Fhandbook\u002Fcompany\u002Fvalues","handbook\u002Fcompany\u002Fvalues",{"title":1311,"group":1312,"icon":1313,"order":1148,"path":1314,"stem":1315,"children":1316},"Design","Engineering & Design Practices","i-lucide-pen-tool","\u002Fhandbook\u002Fdesign","handbook\u002Fdesign\u002Findex",[1317,1318,1322,1326,1330,1334,1338],{"title":1311,"path":1314,"stem":1315},{"title":1319,"path":1320,"stem":1321},"Art Requests","\u002Fhandbook\u002Fdesign\u002Fart-requests","handbook\u002Fdesign\u002Fart-requests",{"title":1323,"path":1324,"stem":1325},"Branding","\u002Fhandbook\u002Fdesign\u002Fbranding","handbook\u002Fdesign\u002Fbranding",{"title":1327,"path":1328,"stem":1329},"Design Thinking","\u002Fhandbook\u002Fdesign\u002Fdesign-thinking","handbook\u002Fdesign\u002Fdesign-thinking",{"title":1331,"path":1332,"stem":1333},"Process","\u002Fhandbook\u002Fdesign\u002Fprocess","handbook\u002Fdesign\u002Fprocess",{"title":1335,"path":1336,"stem":1337},"Tools","\u002Fhandbook\u002Fdesign\u002Ftools","handbook\u002Fdesign\u002Ftools",{"title":1339,"path":1340,"stem":1341},"Video","\u002Fhandbook\u002Fdesign\u002Fvideos","handbook\u002Fdesign\u002Fvideos",{"title":1343,"group":1312,"icon":1344,"order":1154,"path":1345,"stem":1346,"children":1347},"Engineering","i-lucide-code-2","\u002Fhandbook\u002Fengineering","handbook\u002Fengineering\u002Findex",[1348,1349,1352,1367,1371,1375,1379,1413,1456,1460,1518,1522,1549,1553,1568],{"title":1343,"path":1345,"stem":1346},{"title":82,"path":1350,"stem":1351},"\u002Fhandbook\u002Fengineering\u002Fblueprints","handbook\u002Fengineering\u002Fblueprints",{"title":1353,"icon":1354,"path":1355,"stem":1356,"children":1357},"Contributing","i-lucide-git-pull-request","\u002Fhandbook\u002Fengineering\u002Fcontributing","handbook\u002Fengineering\u002Fcontributing\u002Findex",[1358,1359,1363],{"title":1353,"path":1355,"stem":1356},{"title":1360,"path":1361,"stem":1362},"FF Tables","\u002Fhandbook\u002Fengineering\u002Fcontributing\u002Fff-tables","handbook\u002Fengineering\u002Fcontributing\u002Fff-tables",{"title":1364,"path":1365,"stem":1366},"Team NPM Registry","\u002Fhandbook\u002Fengineering\u002Fcontributing\u002Fteam-npm-registry","handbook\u002Fengineering\u002Fcontributing\u002Fteam-npm-registry",{"title":1368,"path":1369,"stem":1370},"Node-RED Dashboard","\u002Fhandbook\u002Fengineering\u002Fdashboard","handbook\u002Fengineering\u002Fdashboard",{"title":1372,"path":1373,"stem":1374},"Dependency Updates","\u002Fhandbook\u002Fengineering\u002Fdependency-updates","handbook\u002Fengineering\u002Fdependency-updates",{"title":1376,"path":1377,"stem":1378},"Feature Flags in PostHog","\u002Fhandbook\u002Fengineering\u002Ffeature-flags","handbook\u002Fengineering\u002Ffeature-flags",{"title":1380,"icon":1381,"path":1382,"stem":1383,"children":1384},"Front End","i-lucide-layout-dashboard","\u002Fhandbook\u002Fengineering\u002Ffrontend","handbook\u002Fengineering\u002Ffrontend\u002Findex",[1385,1386,1390,1394,1398,1402],{"title":1380,"path":1382,"stem":1383},{"title":1387,"path":1388,"stem":1389},"Data Attributes","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Fdata-attributes","handbook\u002Fengineering\u002Ffrontend\u002Fdata-attributes",{"title":1391,"path":1392,"stem":1393},"Front-End Layouts","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Flayouts","handbook\u002Fengineering\u002Ffrontend\u002Flayouts",{"title":1395,"path":1396,"stem":1397},"Front-End Services","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Fservices","handbook\u002Fengineering\u002Ffrontend\u002Fservices",{"title":1399,"path":1400,"stem":1401},"Front-End Testing","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Ftesting","handbook\u002Fengineering\u002Ffrontend\u002Ftesting",{"title":1403,"icon":1404,"path":1405,"stem":1406,"children":1407},"UI Conventions and Style Guide","i-lucide-palette","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Fui-conventions","handbook\u002Fengineering\u002Ffrontend\u002Fui-conventions\u002Findex",[1408,1409],{"title":1403,"path":1405,"stem":1406},{"title":1410,"path":1411,"stem":1412},"Feature Flags","\u002Fhandbook\u002Fengineering\u002Ffrontend\u002Fui-conventions\u002Ffeature-flags","handbook\u002Fengineering\u002Ffrontend\u002Fui-conventions\u002Ffeature-flags",{"title":1414,"icon":1415,"path":1416,"stem":1417,"children":1418},"Platform Ops","i-lucide-server","\u002Fhandbook\u002Fengineering\u002Fops","handbook\u002Fengineering\u002Fops\u002Findex",[1419,1420,1424,1428,1432,1436,1440,1444,1448,1452],{"title":1414,"path":1416,"stem":1417},{"title":1421,"path":1422,"stem":1423},"Certified Nodes","\u002Fhandbook\u002Fengineering\u002Fops\u002Fcertified-nodes","handbook\u002Fengineering\u002Fops\u002Fcertified-nodes",{"title":1425,"path":1426,"stem":1427},"FlowFuse Dedicated","\u002Fhandbook\u002Fengineering\u002Fops\u002Fdedicated","handbook\u002Fengineering\u002Fops\u002Fdedicated",{"title":1429,"path":1430,"stem":1431},"Deployment","\u002Fhandbook\u002Fengineering\u002Fops\u002Fdeployment","handbook\u002Fengineering\u002Fops\u002Fdeployment",{"title":1433,"path":1434,"stem":1435},"Incident Response","\u002Fhandbook\u002Fengineering\u002Fops\u002Fincident-response","handbook\u002Fengineering\u002Fops\u002Fincident-response",{"title":1437,"path":1438,"stem":1439},"Observability","\u002Fhandbook\u002Fengineering\u002Fops\u002Fobservability","handbook\u002Fengineering\u002Fops\u002Fobservability",{"title":1441,"path":1442,"stem":1443},"Production Environment","\u002Fhandbook\u002Fengineering\u002Fops\u002Fproduction","handbook\u002Fengineering\u002Fops\u002Fproduction",{"title":1445,"path":1446,"stem":1447},"Update Stacks on Production","\u002Fhandbook\u002Fengineering\u002Fops\u002Fproduction-stack-update","handbook\u002Fengineering\u002Fops\u002Fproduction-stack-update",{"title":1449,"path":1450,"stem":1451},"Self Hosted Assistant","\u002Fhandbook\u002Fengineering\u002Fops\u002Fself-hosted-assistant","handbook\u002Fengineering\u002Fops\u002Fself-hosted-assistant",{"title":1453,"path":1454,"stem":1455},"Staging Environment","\u002Fhandbook\u002Fengineering\u002Fops\u002Fstaging","handbook\u002Fengineering\u002Fops\u002Fstaging",{"title":1457,"path":1458,"stem":1459},"Packaging Guidelines","\u002Fhandbook\u002Fengineering\u002Fpackaging","handbook\u002Fengineering\u002Fpackaging",{"title":1461,"icon":1462,"path":1463,"stem":1464,"children":1465},"Product","i-lucide-package","\u002Fhandbook\u002Fengineering\u002Fproduct","handbook\u002Fengineering\u002Fproduct\u002Findex",[1466,1467,1471,1475,1479,1480,1484,1488,1495,1499,1502,1506,1510,1514],{"title":1461,"path":1463,"stem":1464},{"title":1468,"path":1469,"stem":1470},"Feature Catalog","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Ffeatures","handbook\u002Fengineering\u002Fproduct\u002Ffeatures",{"title":1472,"path":1473,"stem":1474},"Feedback","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Ffeedback","handbook\u002Fengineering\u002Fproduct\u002Ffeedback",{"title":1476,"path":1477,"stem":1478},"Glossary","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fglossary","handbook\u002Fengineering\u002Fproduct\u002Fglossary",{"title":5,"path":1172,"stem":1174},{"title":1481,"path":1482,"stem":1483},"Methodology","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fmethodology","handbook\u002Fengineering\u002Fproduct\u002Fmethodology",{"title":1485,"path":1486,"stem":1487},"Metrics","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fmetrics","handbook\u002Fengineering\u002Fproduct\u002Fmetrics",{"title":1489,"path":1490,"stem":1491,"children":1492,"icon":1494},"Personas","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fpersonas","handbook\u002Fengineering\u002Fproduct\u002Fpersonas\u002Findex",[1493],{"title":1489,"path":1490,"stem":1491},"i-lucide-user-circle",{"title":1496,"path":1497,"stem":1498},"Pricing Principles","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fpricing","handbook\u002Fengineering\u002Fproduct\u002Fpricing",{"title":1228,"path":1500,"stem":1501},"\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fprinciples","handbook\u002Fengineering\u002Fproduct\u002Fprinciples",{"title":1503,"path":1504,"stem":1505},"Product Swimlanes","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fproduct-swimlanes","handbook\u002Fengineering\u002Fproduct\u002Fproduct-swimlanes",{"title":1507,"path":1508,"stem":1509},"Product Growth","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Ftelemetry","handbook\u002Fengineering\u002Fproduct\u002Ftelemetry",{"title":1511,"path":1512,"stem":1513},"Versioning","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fversioning","handbook\u002Fengineering\u002Fproduct\u002Fversioning",{"title":1515,"path":1516,"stem":1517},"Market Segments","\u002Fhandbook\u002Fengineering\u002Fproduct\u002Fverticals","handbook\u002Fengineering\u002Fproduct\u002Fverticals",{"title":1519,"path":1520,"stem":1521},"Project Management","\u002Fhandbook\u002Fengineering\u002Fproject-management","handbook\u002Fengineering\u002Fproject-management",{"title":1523,"icon":1524,"path":1525,"stem":1526,"children":1527},"Releases","i-lucide-rocket","\u002Fhandbook\u002Fengineering\u002Freleases","handbook\u002Fengineering\u002Freleases\u002Findex",[1528,1529,1533,1537,1541,1545],{"title":1523,"path":1525,"stem":1526},{"title":1530,"path":1531,"stem":1532},"Dashboard 2.0 Releases","\u002Fhandbook\u002Fengineering\u002Freleases\u002Fdashboard-2","handbook\u002Fengineering\u002Freleases\u002Fdashboard-2",{"title":1534,"path":1535,"stem":1536},"Release Process - Digital Ocean","\u002Fhandbook\u002Fengineering\u002Freleases\u002Fdigital-ocean","handbook\u002Fengineering\u002Freleases\u002Fdigital-ocean",{"title":1538,"path":1539,"stem":1540},"Release Process","\u002Fhandbook\u002Fengineering\u002Freleases\u002Fprocess","handbook\u002Fengineering\u002Freleases\u002Fprocess",{"title":1542,"path":1543,"stem":1544},"Release Blogs","\u002Fhandbook\u002Fengineering\u002Freleases\u002Frelease-blogs","handbook\u002Fengineering\u002Freleases\u002Frelease-blogs",{"title":1546,"path":1547,"stem":1548},"Changelog Posts","\u002Fhandbook\u002Fengineering\u002Freleases\u002Fwriting-changelog","handbook\u002Fengineering\u002Freleases\u002Fwriting-changelog",{"title":1550,"path":1551,"stem":1552},"Security Policy","\u002Fhandbook\u002Fengineering\u002Fsecurity","handbook\u002Fengineering\u002Fsecurity",{"title":1554,"path":1555,"stem":1556,"children":1557,"icon":1567},"Support","\u002Fhandbook\u002Fengineering\u002Fsupport","handbook\u002Fengineering\u002Fsupport\u002Findex",[1558,1559,1563],{"title":1554,"path":1555,"stem":1556},{"title":1560,"path":1561,"stem":1562},"Triage Duty","\u002Fhandbook\u002Fengineering\u002Fsupport\u002Ftriage","handbook\u002Fengineering\u002Fsupport\u002Ftriage",{"title":1564,"path":1565,"stem":1566},"Troubleshooting","\u002Fhandbook\u002Fengineering\u002Fsupport\u002Ftroubleshooting","handbook\u002Fengineering\u002Fsupport\u002Ftroubleshooting","i-lucide-life-buoy",{"title":1335,"path":1569,"stem":1570},"\u002Fhandbook\u002Fengineering\u002Ftools","handbook\u002Fengineering\u002Ftools",{"title":1572,"group":1573,"icon":1574,"order":1575,"path":1576,"stem":1577,"children":1578},"Marketing","Marketing department","i-lucide-megaphone",6,"\u002Fhandbook\u002Fmarketing","handbook\u002Fmarketing\u002Findex",[1579,1580,1586,1590,1605,1624,1628,1632,1636,1640,1644,1648,1652,1656],{"title":1572,"path":1576,"stem":1577},{"title":1581,"path":1582,"stem":1583,"children":1584},"Account-Based Marketing","\u002Fhandbook\u002Fmarketing\u002Faccount-based-marketing","handbook\u002Fmarketing\u002Faccount-based-marketing\u002Findex",[1585],{"title":1581,"path":1582,"stem":1583},{"title":1587,"path":1588,"stem":1589},"Brand Voice","\u002Fhandbook\u002Fmarketing\u002Fbrand-voice","handbook\u002Fmarketing\u002Fbrand-voice",{"title":1591,"icon":1592,"path":1593,"stem":1594,"children":1595},"Community","i-lucide-users-2","\u002Fhandbook\u002Fmarketing\u002Fcommunity","handbook\u002Fmarketing\u002Fcommunity\u002Findex",[1596,1597,1601],{"title":1591,"path":1593,"stem":1594},{"title":1598,"path":1599,"stem":1600},"Community Guidelines","\u002Fhandbook\u002Fmarketing\u002Fcommunity\u002Fcommunity-guidelines","handbook\u002Fmarketing\u002Fcommunity\u002Fcommunity-guidelines",{"title":1602,"path":1603,"stem":1604},"Forums And Support","\u002Fhandbook\u002Fmarketing\u002Fcommunity\u002Fforums-and-support","handbook\u002Fmarketing\u002Fcommunity\u002Fforums-and-support",{"title":1606,"icon":1607,"path":1608,"stem":1609,"children":1610,"order":1187},"Content Strategy","i-lucide-file-text","\u002Fhandbook\u002Fmarketing\u002Fcontent-strategy","handbook\u002Fmarketing\u002Fcontent-strategy\u002Findex",[1611,1612,1616,1620],{"title":1606,"path":1608,"stem":1609,"order":1187},{"title":1613,"path":1614,"stem":1615},"Blog","\u002Fhandbook\u002Fmarketing\u002Fcontent-strategy\u002Fblog","handbook\u002Fmarketing\u002Fcontent-strategy\u002Fblog",{"title":1617,"path":1618,"stem":1619},"Customer Stories","\u002Fhandbook\u002Fmarketing\u002Fcontent-strategy\u002Fcustomer-stories","handbook\u002Fmarketing\u002Fcontent-strategy\u002Fcustomer-stories",{"title":1621,"path":1622,"stem":1623},"Webinars","\u002Fhandbook\u002Fmarketing\u002Fcontent-strategy\u002Fwebinars","handbook\u002Fmarketing\u002Fcontent-strategy\u002Fwebinars",{"title":1625,"path":1626,"stem":1627},"Events","\u002Fhandbook\u002Fmarketing\u002Fevents","handbook\u002Fmarketing\u002Fevents",{"title":1629,"path":1630,"stem":1631},"How we work","\u002Fhandbook\u002Fmarketing\u002Fhow-we-work","handbook\u002Fmarketing\u002Fhow-we-work",{"title":1633,"path":1634,"stem":1635},"Lead Activation","\u002Fhandbook\u002Fmarketing\u002Flead-activation","handbook\u002Fmarketing\u002Flead-activation",{"title":1637,"path":1638,"stem":1639},"Lead Generation","\u002Fhandbook\u002Fmarketing\u002Fleads","handbook\u002Fmarketing\u002Fleads",{"title":1641,"path":1642,"stem":1643},"Company Messaging","\u002Fhandbook\u002Fmarketing\u002Fmessaging","handbook\u002Fmarketing\u002Fmessaging",{"title":1645,"path":1646,"stem":1647},"Marketing Programs","\u002Fhandbook\u002Fmarketing\u002Fprograms","handbook\u002Fmarketing\u002Fprograms",{"title":1649,"path":1650,"stem":1651},"Sales Development Representative (SDR)","\u002Fhandbook\u002Fmarketing\u002Fsdr","handbook\u002Fmarketing\u002Fsdr",{"title":1653,"path":1654,"stem":1655},"Social Media","\u002Fhandbook\u002Fmarketing\u002Fsocial-media","handbook\u002Fmarketing\u002Fsocial-media",{"title":1657,"path":1658,"stem":1659},"Website","\u002Fhandbook\u002Fmarketing\u002Fwebsite","handbook\u002Fmarketing\u002Fwebsite",{"title":1661,"group":1185,"icon":1662,"order":1151,"path":1663,"stem":1664,"children":1665},"Operations","i-lucide-settings-2","\u002Fhandbook\u002Foperations","handbook\u002Foperations\u002Findex",[1666,1667,1671,1675,1679,1702,1706,1710,1714,1718],{"title":1661,"path":1663,"stem":1664},{"title":1668,"path":1669,"stem":1670},"Accounting","\u002Fhandbook\u002Foperations\u002Faccounting","handbook\u002Foperations\u002Faccounting",{"title":1672,"path":1673,"stem":1674},"Accounts","\u002Fhandbook\u002Foperations\u002Faccounts","handbook\u002Foperations\u002Faccounts",{"title":1676,"path":1677,"stem":1678},"Billing","\u002Fhandbook\u002Foperations\u002Fbilling","handbook\u002Foperations\u002Fbilling",{"title":1680,"icon":1681,"path":1682,"stem":1683,"children":1684},"CEO Ops","i-lucide-briefcase","\u002Fhandbook\u002Foperations\u002Fceo-ops","handbook\u002Foperations\u002Fceo-ops\u002Findex",[1685,1686,1690,1694,1698],{"title":1680,"path":1682,"stem":1683},{"title":1687,"path":1688,"stem":1689},"Calendar Management","\u002Fhandbook\u002Foperations\u002Fceo-ops\u002Fcalendar-management","handbook\u002Foperations\u002Fceo-ops\u002Fcalendar-management",{"title":1691,"path":1692,"stem":1693},"Inbox Management","\u002Fhandbook\u002Foperations\u002Fceo-ops\u002Finbox-management","handbook\u002Foperations\u002Fceo-ops\u002Finbox-management",{"title":1695,"path":1696,"stem":1697},"Task Management","\u002Fhandbook\u002Foperations\u002Fceo-ops\u002Ftask-managment","handbook\u002Foperations\u002Fceo-ops\u002Ftask-managment",{"title":1699,"path":1700,"stem":1701},"Travel Booking","\u002Fhandbook\u002Foperations\u002Fceo-ops\u002Ftravel-booking","handbook\u002Foperations\u002Fceo-ops\u002Ftravel-booking",{"title":1703,"path":1704,"stem":1705},"Change Control","\u002Fhandbook\u002Foperations\u002Fchange","handbook\u002Foperations\u002Fchange",{"title":1707,"path":1708,"stem":1709},"Commission Payment","\u002Fhandbook\u002Foperations\u002Fcommission-payment","handbook\u002Foperations\u002Fcommission-payment",{"title":1711,"path":1712,"stem":1713},"Data at FlowFuse","\u002Fhandbook\u002Foperations\u002Fdata","handbook\u002Foperations\u002Fdata",{"title":1715,"path":1716,"stem":1717},"Signatures","\u002Fhandbook\u002Foperations\u002Fsignatures","handbook\u002Foperations\u002Fsignatures",{"title":1719,"path":1720,"stem":1721},"Vendors","\u002Fhandbook\u002Foperations\u002Fvendors","handbook\u002Foperations\u002Fvendors",{"title":1723,"group":1724,"icon":1725,"order":1726,"path":1727,"stem":1728,"children":1729},"People Ops","Internal Operations","i-lucide-users",5,"\u002Fhandbook\u002Fpeopleops","handbook\u002Fpeopleops\u002Findex",[1730,1731,1735,1739,1743,1747,1751,1774,1840,1844,1848,1852,1856,1860],{"title":1723,"path":1727,"stem":1728},{"title":1732,"path":1733,"stem":1734},"Coaching Plans","\u002Fhandbook\u002Fpeopleops\u002Fcoaching-plans","handbook\u002Fpeopleops\u002Fcoaching-plans",{"title":1736,"path":1737,"stem":1738},"Code of Conduct","\u002Fhandbook\u002Fpeopleops\u002Fcode-of-conduct","handbook\u002Fpeopleops\u002Fcode-of-conduct",{"title":1740,"path":1741,"stem":1742},"Compensation","\u002Fhandbook\u002Fpeopleops\u002Fcompensation","handbook\u002Fpeopleops\u002Fcompensation",{"title":1744,"path":1745,"stem":1746},"Compliance & Regulatory","\u002Fhandbook\u002Fpeopleops\u002Fcompliance","handbook\u002Fpeopleops\u002Fcompliance",{"title":1748,"path":1749,"stem":1750},"Expenses","\u002Fhandbook\u002Fpeopleops\u002Fexpenses","handbook\u002Fpeopleops\u002Fexpenses",{"title":1752,"icon":1753,"path":1754,"stem":1755,"children":1756},"Hiring","i-lucide-user-plus","\u002Fhandbook\u002Fpeopleops\u002Fhiring","handbook\u002Fpeopleops\u002Fhiring\u002Findex",[1757,1758,1762,1766,1770],{"title":1752,"path":1754,"stem":1755},{"title":1759,"path":1760,"stem":1761},"GitHub Navigation","\u002Fhandbook\u002Fpeopleops\u002Fhiring\u002Fgithub-navigation","handbook\u002Fpeopleops\u002Fhiring\u002Fgithub-navigation",{"title":1763,"path":1764,"stem":1765},"Working with Recruiters","\u002Fhandbook\u002Fpeopleops\u002Fhiring\u002Frecruiters","handbook\u002Fpeopleops\u002Fhiring\u002Frecruiters",{"title":1767,"path":1768,"stem":1769},"Screening Call","\u002Fhandbook\u002Fpeopleops\u002Fhiring\u002Fscreening-call","handbook\u002Fpeopleops\u002Fhiring\u002Fscreening-call",{"title":1771,"path":1772,"stem":1773},"STAR Questions","\u002Fhandbook\u002Fpeopleops\u002Fhiring\u002Fstar-questions","handbook\u002Fpeopleops\u002Fhiring\u002Fstar-questions",{"title":1775,"icon":1776,"path":1777,"stem":1778,"children":1779},"Job Descriptions","i-lucide-file-badge","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Findex",[1780,1781,1785,1789,1793,1797,1801,1805,1809,1813,1817,1821,1825,1829,1832,1836],{"title":1775,"path":1777,"stem":1778},{"title":1782,"path":1783,"stem":1784},"Account Executive","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Faccount-executive","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Faccount-executive",{"title":1786,"path":1787,"stem":1788},"CEO","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fceo","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fceo",{"title":1790,"path":1791,"stem":1792},"Chief of Staff","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fchief-of-staff","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fchief-of-staff",{"title":1794,"path":1795,"stem":1796},"CTO","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fcto","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fcto",{"title":1798,"path":1799,"stem":1800},"Engineering Levels","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fengineering-levels","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fengineering-levels",{"title":1802,"path":1803,"stem":1804},"Engineering Manager","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fengineering-manager","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fengineering-manager",{"title":1806,"path":1807,"stem":1808},"Fullstack Engineer","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Ffullstack-engineer","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Ffullstack-engineer",{"title":1810,"path":1811,"stem":1812},"Fullstack Engineer (AI-Focused)","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Ffullstack-engineer-ai","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Ffullstack-engineer-ai",{"title":1814,"path":1815,"stem":1816},"Head of Marketing","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fhead-of-marketing","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fhead-of-marketing",{"title":1818,"path":1819,"stem":1820},"Lead Product Manager","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Flead-product-manager","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Flead-product-manager",{"title":1822,"path":1823,"stem":1824},"Product Manager","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fproduct-manager","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fproduct-manager",{"title":1826,"path":1827,"stem":1828},"Product Marketer","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fproduct-marketer","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fproduct-marketer",{"title":1649,"path":1830,"stem":1831},"\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fsales-development-representative","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fsales-development-representative",{"title":1833,"path":1834,"stem":1835},"Solutions Engineer","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fsolutions-engineer","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fsolutions-engineer",{"title":1837,"path":1838,"stem":1839},"VP of Sales","\u002Fhandbook\u002Fpeopleops\u002Fjob-descriptions\u002Fvp-sales","handbook\u002Fpeopleops\u002Fjob-descriptions\u002Fvp-sales",{"title":1841,"path":1842,"stem":1843},"Holiday & Leave","\u002Fhandbook\u002Fpeopleops\u002Fleave","handbook\u002Fpeopleops\u002Fleave",{"title":1845,"path":1846,"stem":1847},"PeopleOps Policies","\u002Fhandbook\u002Fpeopleops\u002Forganization","handbook\u002Fpeopleops\u002Forganization",{"title":1849,"path":1850,"stem":1851},"Performance review","\u002Fhandbook\u002Fpeopleops\u002Fperformance-review","handbook\u002Fpeopleops\u002Fperformance-review",{"title":1853,"path":1854,"stem":1855},"Summit","\u002Fhandbook\u002Fpeopleops\u002Fsummit","handbook\u002Fpeopleops\u002Fsummit",{"title":1857,"path":1858,"stem":1859},"Travel","\u002Fhandbook\u002Fpeopleops\u002Ftravel","handbook\u002Fpeopleops\u002Ftravel",{"title":1861,"path":1862,"stem":1863},"U.S. Compliance Policies","\u002Fhandbook\u002Fpeopleops\u002Fus-compliance","handbook\u002Fpeopleops\u002Fus-compliance",{"title":1865,"path":1866,"stem":1867,"group":1178,"order":1868},"Recent Updates","\u002Fhandbook\u002Frecent-changes","handbook\u002Frecent-changes",0,{"title":1870,"group":1870,"icon":1871,"order":1872,"path":1873,"stem":1874,"children":1875},"Commercial Organization","i-lucide-trending-up",7,"\u002Fhandbook\u002Fsales","handbook\u002Fsales\u002Findex",[1876,1877,1885,1890,1894,1900,1905,1910,1915,1920,1925,1930,1954,1959,1963,1985,1991,1996,2004,2008,2012,2017,2021,2025,2029,2034,2039,2044],{"title":1870,"path":1873,"stem":1874},{"title":1878,"path":1879,"stem":1880,"children":1881,"order":1883,"icon":1884},"Sales Compensation Plan","\u002Fhandbook\u002Fsales\u002Fcommission-plan","handbook\u002Fsales\u002Fcommission-plan\u002Findex",[1882],{"title":1878,"path":1879,"stem":1880},22,"i-lucide-dollar-sign",{"title":1886,"path":1887,"stem":1888,"order":1889},"Customer Journey Alignment","\u002Fhandbook\u002Fsales\u002Fcustomer-journey","handbook\u002Fsales\u002Fcustomer-journey",10,{"title":1891,"path":1892,"stem":1893,"order":1154},"Customer Success","\u002Fhandbook\u002Fsales\u002Fcustomer-success","handbook\u002Fsales\u002Fcustomer-success",{"title":1895,"path":1896,"stem":1897,"order":1898,"icon":1899},"Demo Apps","\u002Fhandbook\u002Fsales\u002Fdemo-apps","handbook\u002Fsales\u002Fdemo-apps",13.7,"i-lucide-layout-grid",{"title":1901,"path":1902,"stem":1903,"order":1904},"Edge Connectivity Sales Process","\u002Fhandbook\u002Fsales\u002Fedge-connect-process","handbook\u002Fsales\u002Fedge-connect-process",19,{"title":1906,"path":1907,"stem":1908,"order":1909},"Engagements & Pricing","\u002Fhandbook\u002Fsales\u002Fengagements","handbook\u002Fsales\u002Fengagements",14,{"title":1911,"path":1912,"stem":1913,"order":1914,"icon":1415},"FlowFuse Trial Environment","\u002Fhandbook\u002Fsales\u002Fflowfuse-trial-environment","handbook\u002Fsales\u002Fflowfuse-trial-environment",13.6,{"title":1916,"path":1917,"stem":1918,"order":1919},"Forecast Review","\u002Fhandbook\u002Fsales\u002Fforecast-review","handbook\u002Fsales\u002Fforecast-review",15,{"title":1921,"path":1922,"stem":1923,"order":1924},"HubSpot","\u002Fhandbook\u002Fsales\u002Fhubspot","handbook\u002Fsales\u002Fhubspot",16,{"title":1926,"path":1927,"stem":1928,"order":1929},"Legal","\u002Fhandbook\u002Fsales\u002Flegal","handbook\u002Fsales\u002Flegal",21,{"title":1931,"order":1932,"icon":1933,"path":1934,"stem":1935,"children":1936},"Sales Meetings",13,"i-lucide-calendar","\u002Fhandbook\u002Fsales\u002Fmeetings","handbook\u002Fsales\u002Fmeetings\u002Findex",[1937,1938,1942,1946,1950],{"title":1931,"path":1934,"stem":1935},{"title":1939,"path":1940,"stem":1941,"order":1151},"Demo","\u002Fhandbook\u002Fsales\u002Fmeetings\u002Fdemo","handbook\u002Fsales\u002Fmeetings\u002Fdemo",{"title":1943,"path":1944,"stem":1945,"order":1187},"Discovery Meeting","\u002Fhandbook\u002Fsales\u002Fmeetings\u002Fdiscovery","handbook\u002Fsales\u002Fmeetings\u002Fdiscovery",{"title":1947,"path":1948,"stem":1949,"order":1148},"Proof of Value","\u002Fhandbook\u002Fsales\u002Fmeetings\u002Fpov","handbook\u002Fsales\u002Fmeetings\u002Fpov",{"title":1951,"path":1952,"stem":1953,"order":1154},"Solution","\u002Fhandbook\u002Fsales\u002Fmeetings\u002Fsolution","handbook\u002Fsales\u002Fmeetings\u002Fsolution",{"title":1955,"path":1956,"stem":1957,"order":1958},"Onboarding & Development","\u002Fhandbook\u002Fsales\u002Fonboarding","handbook\u002Fsales\u002Fonboarding",11,{"title":1960,"path":1961,"stem":1962,"order":1575},"Commercial Team Operating Principles","\u002Fhandbook\u002Fsales\u002Foperating-principles","handbook\u002Fsales\u002Foperating-principles",{"title":1964,"order":1726,"icon":1965,"path":1966,"stem":1967,"children":1968},"Partnerships","i-lucide-handshake","\u002Fhandbook\u002Fsales\u002Fpartnerships","handbook\u002Fsales\u002Fpartnerships\u002Findex",[1969,1970,1974],{"title":1964,"path":1966,"stem":1967},{"title":1971,"path":1972,"stem":1973,"order":1151},"Channel Partners","\u002Fhandbook\u002Fsales\u002Fpartnerships\u002Fchannel-partners","handbook\u002Fsales\u002Fpartnerships\u002Fchannel-partners",{"title":1975,"path":1976,"stem":1977,"children":1978,"order":1187,"icon":1984},"Hardware Partners","\u002Fhandbook\u002Fsales\u002Fpartnerships\u002Fhardware-partners","handbook\u002Fsales\u002Fpartnerships\u002Fhardware-partners\u002Findex",[1979,1980],{"title":1975,"path":1976,"stem":1977},{"title":1981,"path":1982,"stem":1983,"order":1187},"Hardware Partner Workbook","\u002Fhandbook\u002Fsales\u002Fpartnerships\u002Fhardware-partners\u002Fworkbook","handbook\u002Fsales\u002Fpartnerships\u002Fhardware-partners\u002Fworkbook","i-lucide-cpu",{"title":1986,"path":1987,"stem":1988,"order":1989,"icon":1990},"PoV Workbook","\u002Fhandbook\u002Fsales\u002Fpov-workbook","handbook\u002Fsales\u002Fpov-workbook",13.5,"i-lucide-clipboard-list",{"title":1992,"path":1993,"stem":1994,"order":1995},"Pricing Decks","\u002Fhandbook\u002Fsales\u002Fpricing-decks","handbook\u002Fsales\u002Fpricing-decks",18,{"title":1997,"path":1998,"stem":1999,"children":2000,"order":2002,"icon":2003},"Processes","\u002Fhandbook\u002Fsales\u002Fprocesses","handbook\u002Fsales\u002Fprocesses\u002Findex",[2001],{"title":1997,"path":1998,"stem":1999},12,"i-lucide-workflow",{"title":2005,"path":2006,"stem":2007,"order":1148},"Professional Services","\u002Fhandbook\u002Fsales\u002Fprofessional-services","handbook\u002Fsales\u002Fprofessional-services",{"title":2009,"path":2010,"stem":2011,"order":1872},"Sales Regions","\u002Fhandbook\u002Fsales\u002Fregions","handbook\u002Fsales\u002Fregions",{"title":2013,"path":2014,"stem":2015,"order":2016},"Sales Deck","\u002Fhandbook\u002Fsales\u002Fsales-deck","handbook\u002Fsales\u002Fsales-deck",17,{"title":2018,"path":2019,"stem":2020},"Weekly Sales Digest","\u002Fhandbook\u002Fsales\u002Fsales-digest","handbook\u002Fsales\u002Fsales-digest",{"title":2022,"path":2023,"stem":2024,"order":1187},"Sales","\u002Fhandbook\u002Fsales\u002Fsales-team","handbook\u002Fsales\u002Fsales-team",{"title":2026,"path":2027,"stem":2028,"order":1151},"Solution Engineering","\u002Fhandbook\u002Fsales\u002Fsolution-engineering","handbook\u002Fsales\u002Fsolution-engineering",{"title":2030,"path":2031,"stem":2032,"order":2033},"Subscription Agreement 1.5","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.5","handbook\u002Fsales\u002Fsubscription-agreement-1.5",23,{"title":2035,"path":2036,"stem":2037,"order":2038},"Subscription Agreement 1.6","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.6","handbook\u002Fsales\u002Fsubscription-agreement-1.6",24,{"title":2040,"path":2041,"stem":2042,"order":2043},"Systems & Tools","\u002Fhandbook\u002Fsales\u002Ftools","handbook\u002Fsales\u002Ftools",8,{"title":2045,"path":2046,"stem":2047,"order":2048},"Working Norms","\u002Fhandbook\u002Fsales\u002Fworking-norms","handbook\u002Fsales\u002Fworking-norms",9,1790722488826]