Instructions for Use (IFU)

The AiAmbA AI Factory is a natural-language communication bridge between people and machines, designed and manufactured by AiVibe as the OEM. It consists of:

• AiAmbA edge devices such as the compact AiAmbA N Series 150, with built-in networking, which connect to a machine's controller (for example PLC, CNC or robot controllers) on the factory network;
• the AiCippY app (mobile) through which authorised operators chat with their machines by text or voice;
• cloud AI agents that interpret requests, read telemetry and documents, and prepare proposed actions for human confirmation; and
• a desktop commissioning tool used only by verified AiAmbA engineers.

The AI Factory helps people understand and operate equipment faster. It does not replace the machine's control system, its safety systems, the manufacturer's instructions or the judgement of a qualified person.

Depending on the deployment a customer chooses, the bridge uses one or more of the following agent technologies. Each is used only as a language and reasoning layer; none of them is given direct control of a machine.

Third-party models, agents and cloud services are provided under their providers' own terms. Naming them does not imply that Google, NVIDIA, Amazon Web Services or any other provider endorses, certifies or is responsible for the AiAmbA AI Factory.

Within the public beta, the AiAmbA AI Factory is intended for:

• Reading and explaining machine status, alarms and production telemetry in plain language (English first).
• Finding and citing information in documents a customer has uploaded (manuals, drawings, NC programs, SOPs).
• Preparing change requests for parameters that a verified AiAmbA engineer has explicitly commissioned, which a trained operator must review and confirm before anything is sent.
• Supervised pilots and evaluation of natural-language interaction with industrial machines and controllers (PLCs, CNC and robot controllers).

Intended users: business and professional users only — trained, certified machine operators, maintenance and process engineers, and (for the limited medical-device conditions below) qualified clinical or biomedical engineers, each supported by a verified AiAmbA engineer. The beta is not offered to consumers.

Intended environment: supervised industrial pilot installations where the machine remains fully operable and safe through its own local controls.

Do not use the AiAmbA AI Factory for any of the following:

• Diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of any disease, injury or disability, or any other medical purpose. The public beta is not cleared or approved for any medical use.
• Controlling, adjusting or commanding any life-supporting or life-sustaining equipment, or any medical device while it is connected to or in use on a patient (for example ventilators, infusion pumps, anaesthesia, dialysis, defibrillators, imaging or radiotherapy equipment).
• Any safety function. The AI bridge does not replace emergency stops, interlocks, guards, light curtains, safety PLCs or lockout/tagout. A software "stop" request is not a safety-rated stop.
• Unattended, autonomous or closed-loop operation without a trained person present at the machine.
• Use by anyone without valid certification and hands-on training for the specific machine or device, or without the support of a verified AiAmbA engineer.
• Lockout/tagout, energy isolation, or work inside a machine's hazard zone based on information from the AI.
• Hazardous (explosive) atmospheres or other environments the edge device is not rated for.
• Overriding, bypassing or contradicting the original equipment manufacturer's instructions for use. The machine maker's IFU always takes priority.
• Entering patient-identifiable or other special-category health data into the public beta.

Some machines are medical devices with their own controllers. Connecting any software to such a device can change its intended purpose, its regulatory status and the safety of patients and users. The public beta is not cleared or approved as a medical device or as an accessory to one, so:

• Sending instructions (commands) to a medical device is outside the intended purpose of the beta and is not recommended. It must never be attempted by anyone who does not hold the device manufacturer's certification and hands-on training for that model.
• Software that drives or influences a medical device is regulated together with that device (for example under the EU MDR and by the U.S. FDA). Using the bridge to control a medical device would therefore be use outside its intended purpose and outside its regulatory status.
• Any interaction with a medical device's controller is limited to non-clinical technical work — for example reading service status or diagnostic codes in a workshop — with the device disconnected from any patient. Clinical use is prohibited.
• A connection may be made only with the written authorisation of the device's legal manufacturer and the healthcare organisation's clinical/biomedical engineering function, after a documented risk assessment (for example to ISO 14971 and IEC 80001-1).
• Only people who hold the manufacturer's certification and hands-on training for that exact device model may be involved, together with a verified AiAmbA engineer.
• The device manufacturer's IFU, service manual and the healthcare organisation's procedures always take priority over anything the AI says.

• Operators must hold current certification and hands-on training for the specific machine or device, be authorised by their employer, and complete AiAmbA AI Factory beta onboarding.
• Verified AiAmbA engineers are AiVibe AI Factory engineers with product-handling expertise who are named to you in writing by AiVibe. Before allowing anyone to commission or service an installation, confirm their identity at support@aivibe.in. AiVibe never asks for passwords or one-time codes.
• Commissioning, parameter mapping and any change to enabled write parameters may be done only by a verified AiAmbA engineer together with the customer's responsible engineer.

1. 1

   Ask in plain language

   The operator asks a question by text or voice in the AiCippY app, e.g. "Why did spindle 2 alarm at 10:40?"

2. 2

   Agent reads, never guesses silently

   The agent reads live telemetry from the AiAmbA edge device and the customer's own documents, and answers with its sources. Unsupported controller dialects, macros or cycles are reported as unsupported rather than interpreted.

3. 3

   Changes are only proposed

   Agents cannot write to a machine directly. A change becomes a proposal tied to one organisation, one operator, one device and one exact value — shown as ACTION CONFIRMATION REQUIRED.

4. 4

   Human confirmation within 60 seconds

   The operator must review the device, parameter and value and confirm (slide-to-confirm) within 60 seconds. Each confirmation can be used once. Unconfirmed or foreign approvals are rejected.

5. 5

   Commissioned bounds re-checked

   Only parameters a verified AiAmbA engineer has enabled — with a minimum, maximum and verified address — can be requested. Everything else is denied by default.

6. 6

   Expiry, no silent retries

   A queued command expires after 30 seconds. A command sent without a receipt is not retried automatically.

7. 7

   Verified only on read-back

   A change is shown as verified only when the machine reports back the requested value. Always confirm on the machine's own HMI.

Beta limitation: availability of write functions depends on commissioning, and some controller protocols and write paths are not yet enabled in the public beta. Treat every capability as limited until a verified AiAmbA engineer confirms it for your installation in writing.

• The machine's own emergency stop, guards and interlocks are working and within reach.
• You hold current certification and hands-on training for this specific machine or device.
• A verified AiAmbA engineer has commissioned this installation and is reachable during use.
• The commissioned parameter map still matches the machine — re-verify after any retrofit, firmware update, controller replacement or program change.
• The AiCippY app and AiAmbA device firmware are the versions supplied for the beta, and the app shows the device as connected.
• Nobody is inside the machine's hazard zone, and the machine can be operated safely locally if the network or cloud is unavailable.

If any item cannot be confirmed, do not use the AI bridge with that machine.

WARNING — could result in death or serious injury. CAUTION — could result in minor injury or damage to equipment, product or data.

• WARNING: AI output can be wrong, incomplete or out of date. Check every answer against the machine's HMI, the manufacturer's documentation and your own professional judgement before acting.
• WARNING: Never use the AI bridge in an emergency. Use the machine's hardwired emergency stop.
• WARNING: Never confirm an action you did not request, do not fully understand, or that names a different device or value than you expect.
• WARNING: Never give an instruction to a medical device that is connected to or in use on a patient, and never without the manufacturer's certification and training for that device. See section 5.
• CAUTION: Network or cloud interruptions can delay or drop messages. Do not depend on the bridge for time-critical actions.
• CAUTION: Speech recognition can mishear in noisy areas. Always read the confirmation screen before confirming.
• CAUTION: Use only your own account. Never share sign-in credentials or confirm actions on someone else's behalf.
• CAUTION: Install, power and mount the AiAmbA edge device only as instructed by the verified AiAmbA engineer, within the environmental limits supplied for your installation.

1. Identify the device, configure the factory network and the controller address, and label the device.
2. Connect read-only first. Map only the signals needed, using the actual machine's verified memory map — never a generic or example register map.
3. Enable a write parameter only when the customer's responsible engineer approves it, with an explicit minimum, maximum and verified address. Everything not enabled stays denied.
4. Test each enabled parameter at the machine with the operator present, and record the read-back.
5. Record the commissioning in a signed checklist; the customer keeps a copy.

• Sign-in uses AiVibe's enterprise identity service with Google sign-in, and every user acts under their own account. Each organisation's data, devices and conversations are isolated from every other organisation's.
• Communications are logged for audit and safety review; credentials, approval tokens and raw voice audio are excluded from those logs.
• Keep the AiCippY app, operating system and AiAmbA firmware at the versions supplied, place edge devices on a segmented factory network, and remove access for people who leave.
• Do not upload patient-identifiable or other special-category health data to the public beta. Personal data is handled as described in our Privacy Policy; privacy requests: privacy@aivibe.in.
• Report suspected security issues immediately to support@aivibe.in.

This notice summarises AiVibe's position for the public beta. It is not legal advice. Customers remain responsible for meeting the laws that apply to their own machines, devices, workplaces and data.

AiVibe uses the following standards as references when designing the beta and when advising customers on safe integration. Listing a standard is not a claim that the beta conforms to it, except where stated.

• ISO 12100 — machinery risk assessment and risk reduction
• ISO 13849-1 / IEC 62061 — safety-related parts of control systems (safety functions stay outside the AI bridge)
• IEC 61508 — functional safety of electrical/electronic/programmable systems
• ISO 10218-1/-2 — industrial robot safety
• IEC 62443 — security for industrial automation and control systems
• ISO 14971 — risk management for medical devices
• IEC 80001-1 — risk management for IT networks that incorporate medical devices
• IEC 62304 / IEC 81001-5-1 — medical device software life cycle and security
• ISO/IEC 27001 — information security management (AiVibe is ISO/IEC 27001:2022 certified)
• ISO/IEC 42001 — AI management systems

1. Stop using the AI bridge and bring the machine to a safe state using its own controls.
2. Do not try to reproduce the problem on a live machine.
3. Inform your verified AiAmbA engineer and email support@aivibe.in with the date, time, device label and what happened.
4. If a medical device was involved, also report to its manufacturer and, where required, to the competent authority (EU national competent authority, the MHRA Yellow Card scheme in the UK, or FDA MedWatch in the USA).

The AiAmbA AI Factory public beta — hardware, software, AI agents, outputs and documentation — is provided "as is" and "as available", without warranty or guarantee of any kind, whether express, implied or statutory, including any warranty of merchantability, fitness for a particular purpose, accuracy, availability, uninterrupted or error-free operation, or non-infringement. AiVibe does not guarantee any result, output, production outcome or saving.

To the maximum extent permitted by law, AiVibe Software Services Private Limited, AIVEDHA INC and their affiliates, directors, employees and partners are not liable for any indirect, incidental, special, consequential or punitive loss, or for loss of production, profit, data, equipment or goodwill, arising from use of or reliance on the beta. Features may change, be suspended or be withdrawn at any time.

Nothing in this notice excludes or limits liability that cannot be excluded or limited under applicable law, such as liability for death or personal injury caused by negligence, liability for fraud, or mandatory product-liability law.

This notice, the public beta and every dispute or claim arising from or connected with them, anywhere in the world, are governed by the laws of India. The courts at Chennai, Tamil Nadu, India (including the High Court of Judicature at Madras) have exclusive jurisdiction, and users in the European Union, the United Kingdom, the United States and all other countries submit to that jurisdiction.

Use of the public beta requires acceptance of this notice and our Terms & Conditions during onboarding. Where a mandatory law of a user's country gives rights that cannot be waived by contract, those rights are not affected.

Legal notices: legal@aivibe.in. See also our Terms & Conditions.

The latest version of this document is always at www.aivibe.in/regulatory/ifu. Printed copies are uncontrolled. If a translation differs from this English version, the English version applies.

AiAmbA, AiCippY and AiVibe are trademarks of AiVibe Software Services Private Limited. Google, Gemini and Google Cloud are trademarks of Google LLC; NVIDIA, NeMo and Isaac are trademarks of NVIDIA Corporation; Amazon Web Services, AWS and Amazon Bedrock are trademarks of Amazon.com, Inc. or its affiliates. Other names are the property of their respective owners.