已安装设备库全新
销售并不止于交付。已安装设备库记录每位客户正在使用的内容：每一项资产及其序列号、安装日期、保修和完整的服务历史。售后不再取决于恰好经手的人：你打开客户档案，就能看到安装了什么、哪些仍在保修期内、哪些已经维护过。这成为续约、维保和新销售的切入点，全部与你 CRM 中已有的客户紧密相连。
- 每一项已安装资产都带序列号和安装日期。
- 保修管理：哪些仍在保修内，哪些已过期。
- 每项资产的服务历史，在支持时随手可查。
- The ticket points to the customer's equipment, the unit with its serial number, not just the model sold, and the equipment's history starts telling the service story.
- Downtime recorded by people, with availability, MTTR and MTBF over the window, and equipment with no downtime recorded read as unmeasured, never as 100%.
在 Sellio 中免费，你只需为机器付费
The installed base comes built in. It is included in the per-user plan; you can try everything free for 14 days.
无需翻找数据的支持
打开客户档案，就能看到安装了什么、保修和历史。支持又快又准地作出回应。
在恰当的时机续约
保修一目了然，你可以在期限到期前提出续约或维保合同。
从已有资产中挖掘新销售
了解客户已安装的内容，让升级和更换的对话不必从零开始。
An availability contract you can actually check
When the contract has a target, the unplanned availability over the window is compared with it and the verdict comes out of the same calculation. Without a target there is no invented verdict.
客户安装了什么一目了然：不再依赖销售人员的记忆。
保修尽在掌控：在客户询问之前你就知道哪些在保。
续约和维保的切入点：每项资产都是下一次商业对话。
No telemetry and no dressed-up figure: downtime is recorded by people or from the ticket, and the screen says so instead of dressing the number up.
每一项客户资产集中于一处
每一台已安装的设备或产品都记录了序列号和安装日期，并与客户档案关联。当客户来电时，你已经知道他们拥有什么，无需翻查旧邮件或丢失的电子表格。
你能持续追踪的保修
每项资产都带有保修期限，因此你能一眼看出哪些仍在保、哪些已过期。支持决策保持准确，合同续约在恰当的时机达成。
讲述资产故事的历史记录
每一次服务都记录在资产本身上，因此下一次维保从已发生的事情出发，而非从零开始。售后变成一段关系，而非重新来过。
The case is about this equipment
The customer calls saying the machine stopped and the next question is "which one?". On the ticket you pick the equipment from the customer's installed base, searching by serial number, which is how they identify it on the phone; only that customer's equipment can be linked, and a ticket with no customer offers no picker at all, and says why. A ticket is about one piece of equipment: an event that takes down ten machines is an incident, which already groups many tickets. Linking the same asset again repeats nothing; switching the asset undoes the previous link and records both sides in each equipment's history, because correcting a choice must not erase the trace that it existed. From then on the equipment's timeline tells the service story: case linked, unlinked and resolved sit next to the installation, the moves and the maintenance. The warranty (active, expiring, expired) and the service contract show up before you open your mouth to the customer, and moving the equipment records where it went, so the location history is the reading of those moves, not a field that forgets the past. On the account page and in the console, the account's equipment shows up with the risk of each unit.
Downtime, availability and life cycle
A contract promising 99% availability was a sentence; now it is a calculation. Downtime is opened and closed by people, or from the ticket, planned or unplanned: there is no telemetry and no machine signal here, and the screen says that out loud. The same equipment is never down twice at once, overlapping stoppages are merged before being added up (availability never goes negative), a stoppage that crosses the month counts in each month only that month's hours, and a stoppage in progress counts up to now, so the number does not improve on its own while the machine is down. Availability comes with the planned share separated from the unplanned one, because a maintenance window agreed with the customer is not a broken promise, and it is the unplanned share that is compared with the contract target. MTTR and MTBF stay empty without enough samples: an MTBF from a single failure is a guess dressed as a measurement. The life cycle has five states: active, in maintenance, in RMA, retired and written off; written off does not come back, because writing off is an accounting fact, and the way back is registering a new asset with the lineage of the old one. Replacing retires the old unit and creates the new one inheriting account, contract and location, with an event on each side pointing at the other. Criticality, age, repeated failures, coverage and measured availability add up to an explainable risk, and the engine states what it had to assume for lack of data. Next actions (end the downtime, close the open case, renew warranty or contract, schedule maintenance, propose a replacement) only appear when they can be acted on: maintenance is only suggested when you say how many months there are between services, and replacement only with a measured high risk, never by age alone.