RTU-14
Daikin Rebel DPS012DEMO-01 / Roof zone A5
Current conditionNeeds attention
FIELD MANUAL 01 / SOURCE-VERIFIED INTELLIGENCE
Every answer starts with the right equipment.
Red to Green keeps the selected manual, asset history, site map, and next best action in one evidence-first field view.
Page-level citations Offline-ready workflow
Illustrative demo data - no live customer data
ASK AI
RTU-14Diagnose with the source in view.
Why is RTU-14 short cycling after startup?
SOURCE-GROUNDED NEXT STEPThe source points to a condenser-side airflow or fan-proving issue.
Verify condenser fansConfirm both fans start and operate as specified.
2
Inspect coil airflowCheck for blocked fins, debris, and recirculation.
3
Compare the pressure tableUse the OEM table for current outdoor conditions.
IDENTIFY THE ASSETFIND THE SOURCEMAP THE SITECLOSE THE ORDERIDENTIFY THE ASSETFIND THE SOURCE
17,608Viewable manuals and diagrams in the public library
805Manufacturer records in the catalog
Page-levelCitations keep supported answers traceable
OfflinePrepared references for low-connectivity work
LIVING FIELD DEMO
Ask a real question. Watch the answer earn its source.
Choose a service call and run the example. The demo shows how asset context, selected manuals, page-level evidence, and field checks come together.
Pre-populated demonstration dataFIELD INTELLIGENCE
INTERACTIVE EXAMPLE / NO LIVE CUSTOMER DATA DEMO-01 / Roof zone A5 RTU-14
Why does RTU-14 trip on E24 shortly after startup?
Fault E24 recorded twice after a morning restart.
Match asset
Search library
Verify page
Build answer
“High-pressure protection”
Rebel Service and Maintenance ManualRev. 08 / Page 148
TOP MATCHRebel Service and Maintenance ManualHigh-pressure protection
Before resetting high-pressure protection, inspect condenser airflow, prove fan operation, and compare discharge pressure with the table for current outdoor conditions.
Supporting passage selected for the responseAI-ASSISTED RESPONSESource fit: Direct
ANSWER READYThe source points to a condenser-side airflow or fan-proving issue before refrigerant charge should be evaluated.
1
Confirm both condenser fans start and rotate correctly.
2
Inspect the coil and surrounding area for airflow restrictions.
3
Record discharge pressure and compare it with the cited table.
De-energize the unit before physical inspection and follow the site lockout procedure.
CITED SOURCERebel Service and Maintenance Manual / High-pressure protection / p. 148
Answer ready. The source and field checks are visible.
Example responses are illustrative and use demonstration content. Technicians must follow the applicable manufacturer instructions, site procedures, and safety requirements.
ONE FIELD VIEW
The context follows the work.
Red to Green is organized around how a real service call moves, not around disconnected documents and systems.
01 · IDENTIFY
Start with the real asset.
Capture the nameplate, fault, model, and site so the answer begins with the equipment in front of the technician.
02 · DIAGNOSE
Work from the source.
Turn manuals and service records into clear checks with citations back to the exact technical page.
03 · COORDINATE
Keep the site in view.
Connect every unit to its physical location, operating state, manuals, and service history.
04 · RESOLVE
Close the service loop.
Carry the diagnosis into a work order and preserve the verified fix for the next call.
THE OPERATING RHYTHM
Red is a condition.
Green is a verified outcome.
See the fault
Capture the condition, code, nameplate, and operating context.
Find the route
Use site-scoped guidance and page-level evidence to choose the next check.
Prove the fix
Verify operation and attach the resolution to the asset history.
FIELD SYSTEM · 01BUILT FOR THE CALL IN FRONT OF YOU
Technical trust, without the document hunt.
Keep the source, site, asset, and last known fix together so the next decision is fast and defensible.
- Cited answers from the selected manual library
- Site-scoped equipment and service history
- Field packets that stay useful offline
COMMERCIAL EVIDENCE PLAN
A pilot built to produce evidence.
Every paid pilot starts with a customer baseline and ends with a review the customer team can use in its buying decision. Names, quotes, and results appear only with written approval.
See the 45-day pilot planTime to the correct manual sectionMeasured
Technician activation and repeat useMeasured
Answer helpfulness on real callsMeasured
Resolved cases with cited evidenceMeasured
Callback and repeat-visit exposureMeasured
QUESTIONS / ANSWERED
Questions buyers ask before the next step.
Straight answers about fit, coverage, rollout, and technical trust.
01Is Field Intelligence a CMMS?
No. Field Intelligence supports the technical work between a service problem and the applicable procedure. It works beside a CMMS or field-service system without replacing scheduling, inventory, purchasing, payroll, or invoicing.
02What manuals and manufacturers are covered?
The public library is refreshed from the live catalog and spans manuals and diagrams from many commercial-equipment manufacturers. Coverage still varies by model and document type, so every supported response shows the source it used and makes an exact-model gap visible.
03What happens when the exact model manual is unavailable?
The answer basis should make the limitation visible. A technician can review the closest supporting source, avoid treating it as an exact-model procedure, and request the missing document for the library or configured site packet.
04Can technicians verify the source behind an answer?
Yes. Page-level citations, the manual title, and the supporting passage stay attached to supported responses so the technician can inspect the source before acting.
05Can we upload private manuals and site documents?
Commercial plans can include private manuals, asset lists, plans, and service material. Organization and site permissions keep customer-specific material scoped to the authorized team.
06What is included in the one-time commissioning fee?
Standard commissioning includes asset import, document matching, up to three plan layers, a configured offline packet, validation, and two training sessions. Dirty source data, custom integrations, extensive drawing work, and additional plan layers are scoped separately.
READY FOR THE NEXT CALL