Help centre · 214 answers across 21 topics
Products, AI, implementation, security, pricing and real-world “what if” scenarios — answered plainly.
Who we are, who we work with and where to begin.
Trikaan builds AI-powered platforms — Anvaya, the ASTR AI suite and Seed Track — and the engineering services that connect them to your plants, machines, ERP and people.
Mid-to-large manufacturers and agri-businesses, typically ₹200 Cr and above, often with several plants, entities or field teams. We also work with growing companies that want to scale on the right foundation.
Eight: furniture & interiors, food & edible oils, agriculture & seeds, pharmaceuticals, chemicals, automotive & engineering, FMCG, and construction & infrastructure.
Anvaya runs your business operations end to end. ASTR is the AI layer — production, drawing, reporting and machine intelligence. Seed Track manages growers, fields, seed programmes and field visits. They work together or on their own.
Most customers start with a 2–4 week plant assessment or a focused pilot — for example drawing-to-BOM, AI reporting or field visits — and expand once value is proven.
No. Products and modules are switched on as you need them. Many customers start with one plant or one module.
Hennur Road, Bengaluru. Our teams travel to plants and sites across India and abroad for international programmes.
Use Book a Demo or the Contact page. We tailor the demo to your industry and use case.
Both. Products cover what is common across manufacturers; our engineering team builds and integrates what makes your business different.
Reference visits and calls can be arranged with customers who agree to host them, usually after a discovery call. [Confirm availability.]
Yes. We support overseas plants and entities with regional hosting, multi-currency and GDPR-aligned processing.
We bring ready platforms built for manufacturing, in-house PLC/SCADA and AI engineering, and senior people who stay involved through delivery.
Connected operations: purchase, inventory, production, sales, finance, HR and more.
Purchase and procurement, inventory and warehouse, production, quality, sales and dispatch, finance and ledgers, HR and attendance, support tickets, visitor management, storefront and more. [Confirm current module list.]
It covers ERP-style operations, but it can also sit alongside your existing ERP — handling production, quality, machines and intelligence while the ERP stays your system of record for finance.
Yes. Companies, plants, warehouses and cost centres are modelled from day one, with group-level reporting.
Anvaya supports Indian tax workflows and can connect to statutory portals. [Confirm specific integrations.]
Yes. Approvals, fields, checklists and pages can be configured — including with the page builder and flow configuration tools.
Yes. Shop-floor, warehouse and approval screens work on tablets and phones.
Yes, through portals for orders, dispatch status, documents and support. [Confirm portal scope.]
Yes — multi-currency transactions and reporting, and the interface can be offered in local languages for floor users. [Confirm languages.]
Stock by plant, warehouse, bin, batch and lot, with QR/barcode scanning, reorder levels and dead-stock alerts.
Yes. Material issued to job workers, contractor attendance and work orders are tracked end to end.
Yes. Configurable approval chains with maker-checker, and every change is recorded with user and time.
Yes. Masters, opening balances and history are migrated with reconciliation reports.
How the AI works, how accurate it is and who stays in control.
ASTR is Trikaan’s AI suite. It generates recipes, BOMs, plans and reports; reads drawings and documents; predicts failures and shortages; monitors machines; and runs agents that prepare work for approval.
No. Chat is one way to use it, but ASTR also produces documents, reads drawings, watches machine signals and runs multi-step agents.
Only within rules you set. Anything that changes recipes, plans, orders, prices or payments waits for a named person to approve.
Answers are grounded in your own records with links to the source rows, tested on your cases before go-live, and low-confidence outputs are flagged for review.
Every output is a draft until approved. Reviewers can edit or reject, the correction is logged, and that feedback improves future suggestions.
No. Your data is not used to train models for other customers.
Yes. ASTR respects user roles and plant permissions, and can be enabled, limited or switched off by module and role.
English and [list Indian languages]. [Confirm.]
No. ASTR runs inside Anvaya or Seed Track, or alongside your ERP through integrations.
A combination of large language models, vision models and forecasting models, chosen per task and governed by our AI controls. [Confirm model providers.]
Field apps work offline; AI features that need the cloud run when connected. Edge AI on plant gateways is in development.
Reporting and drawing reading are useful from the first week of a pilot. Predictions improve as more of your history is connected.
Yes. Every prompt, answer, approval and edit is logged with user and time.
Yes. AI can be enabled, limited or disabled by module and role.
Recipes, BOMs, costing, work orders, quality and maintenance.
Yes. It drafts recipes from your targets, available materials, lab results and past batches, and shows its reasoning for approval.
Yes — multi-level BOMs with alternates, scrap factors, versions and effective dates.
Standard, estimated and actual cost per product, batch and order, using your material prices, labour and overhead rates.
Yes. Work orders and job cards are generated from the plan and routed to the shop floor.
Yes — inspection plans, limits per stage, deviations, holds and batch release, with full genealogy.
Machine signals such as vibration and temperature are compared with OEM limits and failure history to flag likely failures days ahead.
Twelve phases from product design and recipe through planning, procurement, execution, quality, packing, dispatch, maintenance and insights.
Yes. Process (batch) industries like oils, food and chemicals, and discrete industries like furniture and engineering are both supported.
Yes. It builds production plans from orders, stock, capacity and shifts, and re-plans when something changes — for approval.
Yes. Input, output and loss are captured at each stage so yield variances can be traced to their cause.
Yes. Recipes and BOMs are versioned with approvals, effective dates and change history.
Yes — for example oil, meal and lecithin from one process, each with its own costing.
Yes, from machine signals or operator entries: availability, performance and quality per machine and shift.
Drawing reader, plan generator, BOM/BOQ, cutting lists and costing.
PDF drawings, scanned drawings, images and photos. CAD formats such as DWG/DXF [confirm supported formats].
Parts, dimensions, quantities, materials, notes and views — mapped to your item master.
Yes. The plan generator creates floor plans and layouts from a brief, for interiors, construction and other use cases.
Yes — bill of quantities grouped by trade, ready for estimation.
Yes. Panel and bar cutting lists are optimised to reduce waste, with board yield shown.
Typically minutes per drawing, compared with hours manually. [Confirm benchmark.]
Low-confidence dimensions or parts are highlighted for the estimator to confirm before the BOM is finalised.
Furniture and interiors, retail fixtures, construction, fabrication, sheet metal, engineering and more — 14 use cases in all.
Yes. Changes between revisions are highlighted and the BOM differences listed. [Confirm availability.]
Yes. Operations sequence and machine routing for each part, ready for the shop floor.
Yes. Extracted parts are matched to your item master and new items are flagged for creation.
Plain-language questions, instant reports, exports on any device.
Type or ask a question in plain language — for example “margin by product last quarter by plant” — and ASTR builds the report or chart.
Excel, PDF, CSV and shareable links, on desktop, tablet or phone.
Yes. Daily and weekly MIS can be delivered automatically to each role.
Every number links back to the underlying records, and ASTR only reads data you are allowed to see.
Yes — sales, stock, production, quality and finance can be combined in a single answer.
It can, for most operational reporting. It can also feed curated data into your existing BI platform.
Questions in [supported languages] are understood. [Confirm.]
Yes. Save it, schedule it, or share a link with colleagues who have access.
Yes — charts, tables and summaries, with drill-down from group to plant to record.
Yes. It highlights the main drivers — volume, price, mix or cost — behind a change.
3D/2D twins, live machine data, OEE and alarms.
Most modern PLCs and SCADA systems through standard protocols such as OPC UA, Modbus and MQTT. Legacy machines can be retrofitted with sensors.
No by default. Connections are read-only; any write-back is a separate, approved change.
Edge gateways sit in a DMZ, connect outbound only, and the OT network stays separated from IT and the internet.
Usually one industrial edge gateway per plant and network access to PLC/SCADA. We specify exact needs during the site survey.
Machines and lines in 3D and 2D with live status, OEE, alarms, OEM limits, energy and maintenance history.
The gateway buffers data locally and forwards it in order once the link is back — no gaps.
After the site survey, a typical plant connection takes [X] weeks depending on machines and protocols. [Confirm.]
Yes. Retrofit sensors for vibration, temperature, current and counts can be added to older machines.
No. We build the 3D/2D model from layouts, photos and a site walk. CAD files help if available.
Yes. Alerts for limits, stoppages and anomalies go to the right people by app, email or SMS. [Confirm channels.]
Website and mobile app for growers, fields, seed programmes and field visits.
Both. Managers use the web portal; field officers use the mobile app.
Yes. Onboarding, mapping, visits and photos work fully offline and sync when a network is available.
Three ways: walk the boundary with GPS, draw it on the map, or a hybrid of both.
Yes. Map areas can be downloaded in advance for offline use.
Officers capture grower details, land parcels, photos and consent on the device, in the local language.
Visits carry GPS location, timestamps and photos captured at the moment of the visit.
Yes — seed issue to growers, crop stages, inspections and lot traceability through to processing.
Common smartphones used by field teams. [Confirm minimum OS versions.]
It tracks quantities, quality and amounts due, and can integrate with your finance system for payment. [Confirm scope.]
Managers see visit locations and progress as data syncs, with route and visit history per officer.
Yes. Custom survey forms for crops, growers and villages, usable offline.
Yes. Area is calculated automatically from the mapped boundary.
The core app is designed for field staff. [Confirm any grower-facing features.]
Phases, gates, effort from your side and go-live.
An assessment takes 2–4 weeks, a pilot 8–14 weeks, and enterprise rollouts run in waves across plants. [Confirm typical timelines.]
A sponsor, a product owner, process owners for workshops and testing, IT for integration and security, and plant champions during go-live.
Go-lives are planned around your production calendar, with parallel runs where needed and a rollback plan.
Scope is baselined at design, changes go through a formal request with time and cost impact, and gates are signed by your team.
One lighthouse plant first, then a reusable template, then waves of similar plants with a fit-gap instead of a fresh design.
A value scorecard with baselines, targets, owners and data sources is agreed during assessment and reported monthly.
Data quality is profiled early; cleansing and migration are tracked as a workstream with rehearsals and reconciliation.
In phases. We prefer a pilot, then a template, then waves — never a risky big-bang across all plants.
A named engagement lead, supported by a solution architect and delivery team.
Yes — processes, configuration, integrations, runbooks and admin guides are handed over.
We plan go-lives around your production calendar and avoid peak periods unless you choose otherwise.
ERP, accounting, statutory portals, identity and machines.
Yes. We commonly keep the ERP as master for finance and items and sync production, consumption and quality data back by API. [Confirm named ERPs delivered.]
Yes. Capabilities are exposed through versioned, documented APIs, plus webhooks for events.
Yes, with SAML or OpenID Connect identity providers.
Yes — weighbridges, barcode and QR scanners, label printers and lab instruments, depending on device interfaces.
Integration queues hold messages and retry until delivered, with alerts if anything gets stuck.
Yes. With documentation, APIs and knowledge transfer, many customers co-develop with us.
Yes. Common accounting tools can be integrated by API or scheduled file exchange. [Confirm named tools.]
Yes, through APIs or our storefront and portal modules.
Where systems support it, yes — via APIs and events. Otherwise scheduled syncs are used.
Encryption, access control, OT security and incident response.
Encryption at rest and in transit, per-tenant isolation, role and plant permissions, audit trails, monitoring and tested backups.
Current status: [status]. We map controls to these frameworks and never claim a certification we do not hold.
Only for support, with your approval, time-limited and logged.
Yes, with notice and an agreed scope and window.
We contain it, notify your named contact with the facts, investigate, recover and share a written post-incident report.
Customer-managed keys are available for dedicated and customer-cloud deployments. [Confirm.]
Yes. Audit and access logs can be exported. [Confirm formats.]
Yes — enforced for admins and sensitive roles, and available for all users.
Automated scanning on every build and independent penetration tests [frequency].
Request the security pack — whitepaper, questionnaire answers, pen test summary and policies.
DPDP, GDPR, consent, rights and retention.
You do. You are the data fiduciary (controller); Trikaan processes data only on your instructions.
Yes. The platform provides notice and consent screens, rights handling, retention rules and breach support to help you meet your obligations. Not legal advice.
Yes. It covers roles, purpose, security, sub-processors, breach notification, audit support and deletion at exit.
Consent is captured on the device in the local language, with purpose shown and withdrawal recorded.
Yes. Records can be found across modules, exported, corrected or erased, respecting statutory retention.
Only if you configure that field. It is optional, masked on screen and access-restricted.
Hosting, AI model, messaging, maps, monitoring and support providers. The named list is shared on request. [Insert list.]
As long as you configure per record type, within statutory requirements; data is deleted at contract end after export.
Yes. [Name, privacy@ email].
Deployment options, residency, uptime and recovery.
India regions by default for Indian customers; other regions on request.
Yes — Trikaan cloud, a dedicated environment, your own AWS/Azure/Google Cloud account, on-premise or hybrid edge.
Depends on the service tier: [99.5% / 99.9% / 99.95%] targets, set in your contract.
RPO and RTO are set per tier, from [24 hours] down to [15 minutes / 1 hour], with tested restores.
Shared cloud receives rolling releases with notes; dedicated, customer-cloud and on-premise upgrades are scheduled with you.
Yes. The platform is containerised, so a move is planned and run as a migration.
AWS, Microsoft Azure and Google Cloud.
Yes, with incident history and planned maintenance. [Confirm URL.]
We do, under your access policies, unless you prefer your IT team to run it with our support.
How pricing works, contracts, payment terms and exit.
Three parts: platform subscription (by plant, module and user band), implementation services (fixed per phase or capacity-based), and optional managed services.
Yes. After a discovery call we share a budget range; the assessment turns it into a fixed proposal.
Subscriptions are usually annual; pilots can be shorter. [Confirm.]
Against signed milestones and gates, not hours logged.
Yes. We can work on your MSA and PO terms.
Success measures are agreed upfront. If they are missed we review the causes together and agree remedies before any rollout commitment.
Exit terms, data export and transition support are agreed upfront. [Confirm commercial terms.]
Prices are quoted exclusive of GST, with GST-compliant e-invoices.
We offer guided demos and paid pilots on your data rather than an unsupported trial. [Confirm trial terms.]
Field users in Seed Track are priced in bands. [Confirm.]
Many customers treat it as a capital project; confirm with your auditors. We provide detailed invoices.
Multi-year agreements can include price protection. [Confirm.]
Help desk, response times, training and adoption.
Raise a ticket in the platform or by email; critical issues follow a defined escalation path.
By severity — for example P1 first response in [15 minutes] on critical plans. [Confirm per support plan.]
Yes, on enhanced and critical support tiers.
Role-based, task-focused sessions in local languages, in-app guidance and plant champions on every shift.
Yes. Our team supports every shift during go-live and hypercare.
Yes. We train your admins to manage users, roles, masters and configuration.
Yes — for new joiners, new features and after process changes.
Yes — guides and videos by role and module. [Confirm.]
With release notes, staging tests and, for dedicated environments, your approval.
Custom apps, digitisation, migration and industry solutions.
Yes — custom applications, portals and mobile apps, built on the same standards as our products.
Ownership is defined in the agreement; our standard approach gives you full rights to use, and the documentation to maintain, what we build.
Yes. Workflow digitisation is one of our most common starting points.
Yes, with profiling, cleansing, rehearsed migrations and reconciliation reports.
Yes — manufacturing, agri & seed, and construction & interiors solutions, plus planning, quality, inventory, procurement and costing services.
Yes. Capacity-based teams can work as an extension of your IT or digital team.
Yes, after a technical assessment and structured handover.
Site-to-site VPN, remote access, OT segmentation and monitoring.
Yes — site-to-site VPN or SD-WAN between plants, warehouses, head office and cloud, with failover between internet lines.
Through an approved, time-limited and recorded access path instead of unmanaged remote-desktop tools.
No. We observe first, design off-line and make changes site by site in maintenance windows with rollback ready.
Not necessarily. We audit and reuse existing equipment first.
Yes, through our managed detection and response tier.
Yes — external and internal vulnerability assessment, penetration testing and a prioritised fix plan.
Yes. Assessment, remediation and evidence for questionnaires.
What value to expect and how it is measured.
Common gains are faster estimation and planning, fewer BOM and costing errors, less unplanned downtime and hours of MIS saved each month. [Add verified figures.]
It depends on scope and baseline; the assessment produces a measured business case with payback for your plants.
Baselines are measured before go-live and compared monthly against agreed targets in the value scorecard.
Typically yield, downtime, inventory days, cost accuracy, cycle time, rejection rate, reporting effort and field productivity.
Yes — try the value estimator on the Pricing page; it shows every assumption.
Phones, tablets, browsers and shop-floor hardware.
Current versions of Chrome, Edge, Safari and Firefox.
We specify suitable hardware and can source it, or work with devices you already own.
Yes, with quick sign-in by PIN or badge so each entry is still traceable to a person.
Yes, with device policies, IP allow-lists and mobile device management.
Yes. Screens are optimised for slow networks, and field apps work fully offline.
What happens when things don’t go to plan.
Shop-floor entries queue locally and edge gateways buffer machine data; everything syncs in order when the link returns.
The app keeps working offline with encrypted local storage and syncs with conflict review when back in range.
The planner agent proposes a revised schedule across lines, the maintenance agent raises a work order, and the plant head approves.
Nothing runs until a named approver accepts it. Reviewers edit or reject, and the correction is logged and learned from.
Access is revoked centrally, roles are reassigned, and documentation and trained champions keep knowledge in the team.
Every key role has a named backup, decisions are recorded, and documentation is maintained continuously.
It is added as a new entity or plant using the rollout template — not a re-implementation.
Integration contracts are versioned and tested on every build; we adapt connectors to the new system.
Batch genealogy links the complaint to raw-material lots, machines, people and quality checks in minutes.
Immutable, cross-region backups and point-in-time restore let us recover to a point before the attack, following tested runbooks.
We provide the security pack, questionnaire responses and a call with our security lead.
You receive a full export in open formats with documentation and transition support, followed by certified deletion.
The adoption dashboard shows usage by plant and role; champions, refresher training and design fixes target the gaps.
Changes go through change control with clear impact on time and cost, approved before work starts.
Common masters and reporting, with plant-level workflows and checklists configured separately.
Incoming inspection flags it, affected lots are held, and supplier quality history is updated for the next purchase decision.
ASTR highlights the gaps for the estimator to confirm before the BOM or quote is finalised.
GPS and timestamps reveal it; the visit is flagged for review on the portal.
Edge gateways on UPS keep buffering; entries resume and sync automatically when power returns.
Ask ASTR Reporting in plain language — no report development needed in most cases.
Working with or at Trikaan.
Yes — across engineering, AI, industrial automation, design, delivery and sales. See the Careers page for open roles.
Yes — a six-month programme with real customer work, a mentor and plant or field visits.
Yes. Reach the partnerships team through the Contact page.
Yes. Send your RFP to info@trikaan.com; we assign a bid lead and respond to your timeline.
On the Careers page, filtered by team.
Some delivery and sales roles are based near customer locations. [Confirm.]
A real person replies within one business day.