GITNUXSOFTWARE ADVICE
Manufacturing EngineeringTop 10 Best Daily Production Report Software of 2026
Ranked roundup of daily production report software for plant teams, comparing Qlik Sense, Tableau, and Power BI with MachineMetrics and Sight Machine.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
MachineMetrics is the best fit for operations teams that need repeatable daily production reporting from instrumented equipment, while MRPeasy works best when plant teams want operationally sourced daily reporting with shift handoff exports, and if you can’t clear the budget tier, Wrapbook is a strong low-cost option for production payroll-backed daily cost reporting.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
MachineMetrics
Event-based production reporting that aggregates machine downtime and shift timing into daily output without spreadsheet rebuilds.
Best for: Fits when operations teams need repeatable daily production reporting from instrumented equipment.
Sight Machine
Editor pickEvent-driven visibility that refreshes daily reporting from live production measurements, not manual aggregation.
Best for: Fits when plant teams need event-driven daily reporting tied to MES execution data and governed access.
MRPeasy
Editor pickWork-order anchored daily report generation connects production execution data to supervisor-ready PDF and CSV outputs.
Best for: Fits when plant teams need operationally sourced daily production reporting and document exports for shift handoffs.
Comparison Table
MachineMetrics
enterpriseReal-time machine monitoring and production reporting platform for discrete manufacturers.
Event-based production reporting that aggregates machine downtime and shift timing into daily output without spreadsheet rebuilds.
MachineMetrics focuses on production reporting built from machine and work order signals, not manual spreadsheet entry. Daily call sheet style reporting is produced by aggregating timestamps, downtime events, and throughput counters into consistent daily views. Report contents can be configured around the operational questions plant leaders track each day, including what ran, what stopped, and when shifts changed.
A tradeoff is that reports depend on upstream instrumentation and event tagging quality, which means weak sensor coverage and inconsistent downtime codes reduce report trust. MachineMetrics fits best when manufacturing execution and maintenance telemetry already exist, and when teams need repeatable reporting across many lines each day without rebuilding logic.
- +Automates daily reporting from machine event streams and timestamps
- +Supports recurring shift-based aggregation for consistent daily views
- +Integrations and API enable connecting plant systems and outputs
- +Line-level context reduces manual reconciliation work
- –Report quality depends on accurate downtime tagging upstream
- –Setup requires aligning shop-floor identifiers across systems
- –Advanced report customization can take multiple configuration cycles
- –Offline-first capture is limited when field connectivity is unstable
Plant operations leaders
Daily view of line downtime
Faster daily production reviews
Maintenance operations
Trace downtime to asset history
Quicker root-cause triage
Show 2 more scenarios
Manufacturing data teams
Automate report delivery to systems
Reduced manual data handling
Uses the API and integrations to feed daily production results into downstream tooling and exports.
Shift supervisors
Wrap-time reconciliation by shift
Fewer end-of-shift discrepancies
Summarizes what ran, what stopped, and when shifts changed inside a daily shift-based report.
Best for: Fits when operations teams need repeatable daily production reporting from instrumented equipment.
Sight Machine
enterpriseManufacturing data platform enabling daily production performance analysis and reporting.
Event-driven visibility that refreshes daily reporting from live production measurements, not manual aggregation.
Sight Machine fits plant operations teams that need repeatable daily production reporting tied to execution data, not static spreadsheets. Core capabilities center on monitoring production activities, calculating performance metrics from operational signals, and publishing report outputs that can be scheduled or triggered by events. Integration depth shows up through connected data flows from manufacturing systems and the ability to map plant concepts to reporting views and measures.
A key tradeoff is that report design depends on integrating and modeling the required production signals, which adds upfront configuration compared with tools that only format user-entered timesheets. Sight Machine is best used when daily reporting must reconcile actuals versus planned performance across lines or sites, and when exception handling needs to route to responsible teams with audit-ready traces.
- +Connects operational execution signals to daily performance metrics
- +Supports automated report refresh based on production events
- +Provides admin visibility with audit logging and access controls
- +Extensibility through integration and custom report logic
- –Requires integration and mapping work to align plant data to reporting
- –Report templates take time to standardize across multiple sites
Plant operations analysts
Daily performance review by line
Faster variance identification
Manufacturing engineering
Exception tracking for downtime causes
Quicker corrective action
Show 1 more scenario
Site leadership
Multi-site KPI governance
Higher reporting trust
Enforce RBAC and audit log coverage so leadership reviews consistent metrics across plants.
Best for: Fits when plant teams need event-driven daily reporting tied to MES execution data and governed access.
MRPeasy
SMBCloud-based MRP system for small manufacturers with production planning and daily reporting modules.
Work-order anchored daily report generation connects production execution data to supervisor-ready PDF and CSV outputs.
MRPeasy fits daily production reporting when teams need a repeatable record of what ran, who worked, and what changed during the day. It supports crew list import workflows and daily reconciliation style reporting that can reflect actuals versus planned quantities and timing fields. Daily outputs can be exported for circulation through CSV and PDF generation, which keeps reporting usable for teams that do not rely on a BI viewer.
A tradeoff is that the reporting experience depends on how well production data is modeled in MRPeasy, since late rework of templates can require re-mapping fields across work orders and time entries. MRPeasy works best when reporting is driven from operational objects like work orders and time entries and then pushed into daily PDFs and spreadsheets for supervisors and payroll handoff.
- +Daily report outputs tie to operational execution records and reduce copy-paste between tools
- +Exports via CSV and PDF support handoff to supervisors and payroll workflows
- +Recurring report generation supports consistent end-of-day reporting cycles
- +Crew list import reduces manual entry for time and participation tracking
- –Template changes can be disruptive when production fields and time entries are already in use
- –Less suited for ad hoc analytics compared with BI-first tools
- –Automation coverage centers on report cycles rather than deep dashboard interactivity
- –Complex governance needs may require disciplined permission practices
Plant operations coordinators
Daily work status and output reporting
Faster end-of-day reporting
Crew time admin
Crew participation and time entry capture
Cleaner time recordkeeping
Show 2 more scenarios
Operations analysts
Actuals versus planned reporting extracts
More consistent variance tracking
Daily exports compare realized fields against planned work order targets for ongoing variance review.
Payroll and HR coordinators
Timecard export for downstream processing
Reduced manual data re-entry
Daily time-related exports provide structured inputs for payroll pipelines that consume spreadsheets and PDFs.
Best for: Fits when plant teams need operationally sourced daily production reporting and document exports for shift handoffs.
Tulip
enterpriseOperations platform supporting daily production tracking and reporting for manufacturers.
Offline sync for mobile capture keeps daily reporting on schedule when field connectivity drops.
Tulip turns daily production reporting into a configurable workflow built from templates and on-device capture. Teams can generate production report templates with logic, validations, and step-by-step tasks that mirror floor reality.
- +Logic-driven production report workflows reduce manual data cleanup
- +Offline capture keeps daily reporting usable during connectivity gaps
- +Export to CSV supports quick downstream handling in standard tools
- +API and webhooks support integration with external systems
- –Building complex reporting layouts takes time for template designers
- –Field-level governance depends on project structure and user permissions
- –PDF report generation is not the core automation focus for every workflow
- –Offline conflict handling requires attention to device sync behavior
Best for: Fits when operations teams need mobile-first daily production reports with offline capture and controlled workflow logic.
Wrapbook
vertical specialistProduction payroll and accounting platform for film and TV with timecard and daily cost reporting.
Wrapbook’s wrap time reconciliation links field capture to daily report totals, minimizing separate spreadsheet reconciliation steps.
Wrapbook generates daily production reports by collecting set activity in structured forms and reconciling wrap and timesheet data into a printable workflow. The tool supports crew timesheets, daily call sheets, and PDF report generation with status tracking across multiple departments.
- +End-to-end daily report workflow from capture through PDF output
- +Crew timesheet and wrap time reconciliation are built around the same process
- +Extras voucher handling reduces separate spreadsheet tracking
- +Crew list import supports faster onboarding for production changes
- –Department-specific fields can require template tuning to match existing report formats
- –Live reporting depth depends on how teams structure entries in Wrapbook
Best for: Fits when plant and operations teams need repeatable daily production reporting with wrap reconciliation and exports.
Odoo Manufacturing
enterpriseOpen-source ERP manufacturing module with production order tracking and daily reporting dashboards.
Work order and routing-linked production reporting derives daily actuals from operation-level progress inside Odoo’s manufacturing flow.
Odoo Manufacturing connects shop-floor work orders to production reporting through Odoo’s manufacturing and inventory data model, which makes daily output traceable against planned operations. Daily production reports are produced from work order progress, recorded consumption, and routing steps so supervisors can reconcile actuals to planned quantities without rebuilding templates in a separate system.
- +Work order progress ties directly to daily production output and consumption
- +Routing step tracking supports operation-by-operation daily reporting
- +Automations trigger report-related updates as work orders change state
- +Extensible fields let plants add extra shop-floor attributes to reports
- –Daily report formatting depends on Odoo report configuration and templates
- –Consistent data entry is required to keep daily actuals reliable across shifts
Best for: Fits when plants want daily production reporting tied to work orders, inventory moves, and routing steps in one system.
Raken
vertical specialistField reporting app for construction daily reports, production logs, and crew documentation.
Daily production report templates that enforce consistent jobsite data capture across crews.
Raken is built for collecting daily jobsite production data and turning it into structured reports for crews and operations teams. The system centers on field capture with templates for items like crew rosters, tasks, and progress details, then outputs consistent daily production reporting without manual reformatting.
- +Field capture workflows keep daily production reporting consistent across crews
- +Templates reduce rework when generating repeatable production report formats
- +Integrations and exports help move report data into planning and time systems
- +Role-based access supports controlled visibility across job teams
- –Template setup can take multiple iterations to match plant-specific reporting rules
- –Custom reporting beyond standard outputs can require process workarounds
- –Offline sync needs explicit handling for remote shifts without connectivity
- –High-volume daily logging can create reporting bottlenecks at aggregation time
Best for: Fits when plant and ops teams need mobile daily production reporting with consistent templates and export-ready records.
Epicor ERP
enterpriseEnterprise ERP for manufacturers with MES-grade shop floor data collection and daily production reporting.
Work order and labor transactions feed daily operational reporting, letting the daily report track execution status without manual rekeying.
Epicor ERP is an end-to-end ERP suite that can generate daily production reporting from shop-floor transactions rather than treating reporting as a separate app. It supports manufacturing execution workflows tied to inventory, work orders, and labor records, so daily production reports can reflect actuals as operations update records.
- +Production metrics can be driven by work order and inventory transaction data
- +Configurable reports support recurring daily production report outputs
- +ERP labor records enable daily hours views tied to execution activity
- +Extensibility supports automation and external integration into the reporting workflow
- –Daily production report templates typically require ongoing configuration effort
- –Advanced reporting often depends on the broader Epicor ERP setup and data discipline
- –User experience can feel ERP-centric versus purpose-built production call sheets
- –Report customization complexity increases with multi-site operational variations
Best for: Fits when manufacturing teams need daily production reporting backed by ERP execution and labor records across sites.
NetSuite
enterpriseOracle cloud ERP with a manufacturing module that supports work order and production reporting.
Saved Searches plus NetSuite REST and SOAP APIs to build controlled daily extract pipelines from operational records.
NetSuite is used to generate daily production reporting by pulling operational inputs into financial and operational workflows that support audit trails. Core capabilities include ERP-led data capture, scripted automation for nightly reconciliations, and API access for pushing daily call sheet and crew timesheet data into reporting outputs.
- +Strong API surface for integrating daily production inputs into NetSuite records
- +Automation scripts support repeatable nightly calculations and wrap time reconciliation
- +Role-based access controls limit who can view and export crew and schedule data
- +Saved searches provide governed CSV exports for report distribution
- –No purpose-built production report template editor for shot-level views
- –Daily reporting setup can require model and workflow design effort in NetSuite
- –Complex reporting often depends on custom scripting and saved search tuning
- –Batch data loads can add latency for time-sensitive call time tracking changes
Best for: Fits when operations teams need governed reporting tied to ERP records and daily export workflows.
ERPAG
SMBCloud manufacturing ERP with work order and production tracking for daily production reports.
Template-driven daily reporting with built-in operational signoff steps for shift-to-shift accountability.
ERPAG is a daily production report workflow tool built for plant and operations teams that need recurring shift reporting and structured signoff. It focuses on report templates, task checklists, and exporting report outputs for downstream payroll and operations tracking.
- +Configurable daily report templates for repeatable shift submissions
- +Structured form inputs reduce missing fields in daily logs
- +Export-oriented outputs help standardize handoff to other systems
- +Clear approval steps support consistent operational signoff
- –Automation depth for cross-module workflows is limited
- –API and integration documentation is not detailed enough for complex data syncing
- –Role governance controls are not granular for multi-team plant hierarchies
- –Offline sync for field capture is not positioned as a core capability
Best for: Fits when plant teams need consistent daily production report templates and dependable export workflows.
Conclusion
After evaluating 10 daily production report software, MachineMetrics stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Daily Production Report Software
Daily production report software turns shop-floor execution into repeatable daily output, so plant and operations teams can compare actuals across shifts without spreadsheet rebuilds. This guide covers MachineMetrics, Sight Machine, Tableau, and Power BI, plus eight additional tools used for daily reporting from work orders, field capture, and ERP labor transactions.
The coverage focuses on how daily reporting is generated from events or work records, how exports like CSV or PDF fit shift handoffs, and how automation and integration surfaces reduce manual rekeying. The narrative also tracks where governance and configuration control matter, because daily templates often fail when identifiers or field definitions drift across sites.
Daily Production Report Software for event-driven, shift-based plant output reporting
Daily production report software produces shift-to-shift reporting that aggregates production activity into a daily output view using machine event streams, MES execution signals, work order progress, or ERP transaction data. MachineMetrics emphasizes event-based production reporting that aggregates machine downtime and shift timing into daily output without spreadsheet rebuilds. Sight Machine emphasizes event-driven visibility that refreshes daily reporting from live production measurements rather than manual aggregation.
Most implementations expect daily output to stay consistent across crews, so tools either standardize report templates or derive totals from structured execution records. Some products treat daily reports as an extension of shop-floor event capture, while others treat them as export-first documents tied to work orders, reconciliation workflows, or ERP calculations. Across the set, the buying decision hinges on whether daily reporting can be regenerated from instrumented identifiers and execution events with controlled refresh behavior.
Daily Production Report Software selection criteria that affect shift handoffs
Daily production reports succeed when the daily totals can be regenerated from instrumented identifiers and execution records, not when teams manually rebuild spreadsheets each shift. MachineMetrics and Sight Machine both generate daily reporting from event timing and execution signals so refresh behavior stays repeatable.
Export reliability also drives operational adoption, because shift handoffs often depend on PDF and CSV outputs and on wrap time reconciliation that prevents separate spreadsheet cleanup. MRPeasy and Wrapbook both connect shift outputs to supervisor-ready exports and reconciliation, while ERP-focused tools like NetSuite and Epicor ERP push this work into ERP records and automation.
Event-based daily aggregation from machine or MES execution signals
MachineMetrics aggregates machine downtime and shift timing into daily output using event streams and timestamps so daily totals rebuild without spreadsheet work. Sight Machine refreshes daily reporting from live production measurements tied to MES execution data.
Work-order anchored reporting with structured exports for shift handoffs
MRPeasy generates work-order anchored daily report outputs and exports to PDF and CSV for supervisor shift handoffs. Wrapbook links wrap time reconciliation to daily report totals and produces an end-to-end workflow through PDF output.
Template-driven daily capture that enforces consistent jobsite fields
Raken uses daily production report templates to enforce consistent jobsite data capture across crews and to keep export-ready records. ERPAG uses configurable daily report templates with structured signoff steps to reduce missing fields in daily logs.
Governed reporting pipelines and automation using ERP APIs and scripts
NetSuite provides saved searches plus REST and SOAP APIs so teams can build controlled daily extract pipelines from operational records. Epicor ERP feeds daily operational reporting from work order and labor transactions so the daily report can track execution status without manual rekeying.
Mobile capture behavior when connectivity drops during the shift
Tulip supports offline sync for mobile capture so daily reports stay usable during connectivity gaps and controlled workflow logic reduces manual cleanup. Wrapbook and Raken focus on end-to-end daily report workflows with capture and exports that depend on how teams structure daily entries.
How to choose Daily Production Report Software by regeneration logic and workflow control
The first fork is whether the daily report totals should be regenerated from event timing and production measurements or from work-order progress and ERP transactions. MachineMetrics and Sight Machine treat daily reporting as a function of production events, while Odoo Manufacturing and Epicor ERP treat daily actuals as a function of operation progress and labor transactions.
The second fork is whether the daily report is primarily a structured capture workflow with template governance or primarily a reporting extraction pipeline into an analytics layer. Tulip and Raken emphasize controlled mobile capture and template logic, while NetSuite and the ERP-connected tools emphasize building recurring extracts and calculations through APIs and automation scripts.
Choose the daily totals regeneration source: event stream versus work records
If daily output must aggregate machine downtime and shift timing from event streams without spreadsheet rebuilds, select MachineMetrics or Sight Machine. If daily output must derive actuals from work order progress and routing steps inside a manufacturing workflow, select Odoo Manufacturing or Epicor ERP.
Match export and handoff workflow to supervisor requirements
If shift handoffs require document exports that tie directly to operational execution records, select MRPeasy for PDF and CSV outputs. If reconciliation between field capture and daily totals is a recurring pain point, select Wrapbook because it links wrap time reconciliation to daily report totals.
Decide how report consistency is enforced: templates versus execution-led refresh
If crews need consistent jobsite data capture across templates, select Raken or ERPAG because templates and structured inputs reduce missing fields. If consistency must come from governed refresh behavior driven by event timing and production measurements, select Sight Machine or MachineMetrics.
Validate integration and mapping workload before standardizing templates
If plant data must be aligned to reporting identifiers and report templates take time to standardize across multiple sites, Sight Machine is likely to require integration and mapping work. If reporting quality depends on accurate downtime tagging upstream and alignment of shop-floor identifiers, MachineMetrics will also require disciplined upstream identifiers.
Plan for offline and mobile capture coverage during the shift
If daily reporting must keep working during connectivity drops, select Tulip because offline sync for mobile capture keeps reporting usable and workflow logic reduces cleanup. If the operation expects template-driven daily capture and repeatable exports but can tolerate connectivity-dependent workflows, select Raken or Wrapbook.
Who Daily Production Report Software fits based on plant workflow and data source
Daily production report software fits teams that need shift-to-shift comparability and repeatable generation of daily output from production activity. The match depends on whether the shop floor is instrumented for event streams, whether daily reporting is derived from work order progress, or whether daily capture is driven by crew templates and mobile offline use.
Different tools also assume different governance models, since template standardization can be disruptive when production fields are already in use, and event-based reporting can degrade when downtime tagging upstream is inaccurate.
Operations teams running instrumented equipment with event timing available
MachineMetrics and Sight Machine aggregate downtime and shift timing from machine or MES execution signals so daily output can rebuild without spreadsheet rebuilds.
Manufacturing plants that manage daily execution through work orders, routing, and inventory moves
Odoo Manufacturing and Epicor ERP derive daily actuals from operation progress and labor transactions so daily reporting stays tied to work order and routing steps.
Plants that require supervisor-ready daily outputs via PDF and CSV tied to execution records
MRPeasy generates work-order anchored daily reports with CSV and PDF exports that reduce copy-paste between tools and can align better with shift handoffs.
Site teams that need wrap time reconciliation to prevent separate spreadsheet cleanup
Wrapbook connects wrap time reconciliation to daily report totals so the same workflow produces both captured inputs and daily totals.
Contractor and field crews that need consistent daily reporting templates across jobsites
Raken and ERPAG enforce daily production report templates and structured signoff steps so crews generate export-ready records with fewer missing fields.
Common pitfalls when implementing Daily Production Report Software
Daily production report implementations fail when report generation depends on inconsistent identifiers, when template changes disrupt ongoing time entry workflows, or when daily refresh pipelines are designed without validation of upstream execution quality. Teams also misjudge the effort needed to standardize templates across sites or to configure report formatting in ERP systems.
These pitfalls show up differently by product class, so the mitigation depends on whether the organization is adopting event-driven daily aggregation, work-order reporting, or template-driven crew capture.
Standardizing report templates before aligning machine or shop-floor identifiers used for event-based aggregation
MachineMetrics depends on accurate downtime tagging upstream and alignment of shop-floor identifiers across systems, so identifiers must be corrected before daily reporting quality is expected to hold. Sight Machine also requires integration and mapping work to align plant data to reporting, so mapping gaps will surface as inconsistent refresh outputs.
Treating template-driven capture as a one-time setup when report fields already exist in shift routines
MRPeasy notes that template changes can be disruptive when production fields and time entries are already in use, so field mapping should be planned as a controlled change process. Raken also warns that template setup can take multiple iterations to match plant-specific reporting rules.
Building daily reconciliation into a separate spreadsheet when the tool already ties capture to daily totals
Wrapbook is built so wrap time reconciliation links field capture to daily report totals, so separate reconciliation steps undermine its end-to-end workflow. If wrap reconciliation is essential, choosing a tool without that linkage forces ongoing manual correction work.
Assuming ERP-connected reporting will work without ongoing configuration and data discipline
Odoo Manufacturing says consistent data entry is required to keep daily actuals reliable across shifts because daily report formatting depends on Odoo report configuration. Epicor ERP similarly notes that daily production report templates typically require ongoing configuration effort and advanced reporting depends on broader Epicor ERP setup.
Overlooking offline behavior and governance gaps in mobile workflows
Tulip explicitly offers offline sync for mobile capture to keep reporting usable during connectivity drops, so skipping that capability invites gaps in daily logs. Raken and Wrapbook depend on how teams structure entries and templates, so governance gaps can still create uneven report outputs.
How We Selected and Ranked These Tools
We evaluated each tool against event-driven versus work-order anchored daily regeneration, because daily output must be rebuilt consistently across shifts. We weighted features at 40%, and ease and value each at 30% to reflect how much workflow wiring and operational discipline the daily reporting process demands.
MachineMetrics separated itself by aggregating machine downtime and shift timing from event streams into daily output without requiring spreadsheet rebuilds, and it also supports recurring shift-based aggregation for consistent daily views. We also scored implementation risk from the provided constraints, because MachineMetrics report quality depends on accurate downtime tagging upstream and aligning shop-floor identifiers across systems.
Frequently Asked Questions About Daily Production Report Software
How do event-driven systems change daily production reporting versus template-only workflows?
Which tools support automation for recurring report generation and scheduled delivery?
How do APIs and integrations differ between manufacturing data systems and ERP ecosystems?
What setup tasks are required to ensure report data stays consistent across shifts and departments?
When teams need offline field capture, which daily production report tools handle later sync?
What security controls matter most for multi-site production reporting, and which tools cover them natively?
How is data migration handled when moving from spreadsheets to structured daily reports?
Which tools are better for work-order anchored daily reporting with actuals vs planned quantities?
What breaks if wrap time reconciliation or shift timing inputs are incomplete?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
- Manufacturing EngineeringTop 10 Best Production Reporting Software of 2026
- Sales EnablementTop 10 Best Daily Sales Report Software of 2026
- Mining Natural ResourcesTop 10 Best Daily Drilling Report Software of 2026
- Business FinanceTop 10 Best Daily Activity Report Software of 2026
- Data Science AnalyticsTop 10 Best Report Generation Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Manufacturing Engineering alternatives
See side-by-side comparisons of manufacturing engineering tools and pick the right one for your stack.
Compare manufacturing engineering tools→