THE
OPERATING
MANUAL.
EVERYTHING YOUR TEAM NEEDS TO UNDERSTAND, DEPLOY, AND OPERATE ARIA — THE BUSINESS MANAGEMENT PLATFORM BUILT FOR OWNERSHIP, NOT SUBSCRIPTION.
DOC_INDEX
ONE REFERENCE. EVERY AUDIENCE. NO GAPS.
VERSION
1.0.4
LICENSE
PERPETUAL
MODULES
5
DEPLOY
ON-PREM
DOCS_PRINCIPLE
IF YOU OWN THE SYSTEM, YOU SHOULD UNDERSTAND THE SYSTEM.
01 / PRODUCT_OVERVIEW
WHAT ARIA IS.
ARIA IS A MODULAR, INTEGRATED BUSINESS MANAGEMENT PLATFORM DESIGNED FOR MANUFACTURING, LOGISTICS, AND OPERATIONS-INTENSIVE MSMEs.
IT UNIFIES FIVE OPERATIONAL SYSTEMS — INVENTORY, ASSET MANAGEMENT, MANUFACTURING EXECUTION, CRM, AND HRMS — UNDER A SINGLE DATA MODEL, A SINGLE DEPLOYMENT, AND A SINGLE PERPETUAL LICENSE. IT IS NOT A SaaS APPLICATION. IT IS NOT HOSTED BY PIVOTR. IT RUNS ON INFRASTRUCTURE THE CUSTOMER OWNS.
CORE_PROBLEM_01
DATA FRAGMENTATION.
FINANCE LIVES IN ONE TOOL, OPERATIONS IN ANOTHER, AND MACHINE EVENTS NEVER REACH THE BUSINESS RECORD CLEANLY. TEAMS SPEND TIME RECONCILING, NOT OPERATING.
CORE_PROBLEM_02
SUBSCRIPTION DRAG.
EVERY NEW USER, LOCATION, OR PROCESS EXPANSION BECOMES A BILLING EVENT. GROWTH GENERATES RECURRING COST RATHER THAN OPERATING LEVERAGE.
CORE_PROBLEM_03
VENDOR DEPENDENCY.
BUSINESS-CRITICAL SYSTEMS RUN ON SOMEONE ELSE'S TIMELINE, INFRASTRUCTURE, AND ACCESS MODEL. UPDATE WINDOWS, DATA RESIDENCY, AND SYSTEM ACCESS ARE OUTSIDE THE CUSTOMER'S CONTROL.
ARIA_RESPONSE
UNIFIED DATA. PERPETUAL OWNERSHIP. CLIENT-CONTROLLED INFRASTRUCTURE.
ARIA CLOSES ALL THREE GAPS SIMULTANEOUSLY.
CORE_PHILOSOPHY
OWNERSHIP IS
THE BASELINE.
MOST BUSINESS SOFTWARE ASKS COMPANIES TO TRADE AUTONOMY FOR CONVENIENCE. PIVOTR REJECTS THIS AS A FALSE CHOICE. CONTROL OVER DATA, DEPLOYMENT LOCATION, UPDATE TIMING, AND ACCESS POLICY ARE NOT EXTRAS — THEY ARE HOW SOFTWARE SHOULD WORK.
TARGET_AUDIENCE
WHO ARIA IS BUILT FOR.
FOUNDER / MD
TOTAL COST OF OWNERSHIP. LONG-TERM VENDOR RISK.
OPERATIONS HEAD
REAL-TIME VISIBILITY. PRODUCTION ACCURACY.
IT HEAD / SYSADMIN
DEPLOYMENT MODEL. DATA LOCATION. ACCESS CONTROL.
FINANCE LEAD
CAPEX VS OPEX. LICENSE CLARITY. COST PREDICTABILITY.
SEGMENT
INDIAN MSMEs IN MANUFACTURING, LOGISTICS, AND INDUSTRIAL OPERATIONS.
COMPANIES WITH PHYSICAL ASSETS — MACHINES, INVENTORY, FACILITIES — THAT NEED OPERATIONAL SOFTWARE CLOSE TO THOSE ASSETS. BEYOND SPREADSHEETS, NOT YET AT ENTERPRISE SCALE.
02 / SYSTEM_ARCHITECTURE
THREE LAYERS.
ONE OPERATING CORE.
ARIA IS BUILT ON A THREE-LAYER ARCHITECTURE WHERE ERP WORKFLOWS, AI ASSISTANCE, AND INDUSTRIAL SIGNALS SHARE A SINGLE DATA MODEL INSIDE THE CLIENT'S OWN ENVIRONMENT.
LAYER_01
CORE ERP LAYER.
FINANCE, INVENTORY, OPERATIONS, AND REPORTING WORKFLOWS — RUNNING INSIDE THE CLIENT'S ENVIRONMENT. THIS IS THE TRANSACTIONAL BACKBONE: PURCHASE ORDERS, GOODS RECEIPTS, WORK ORDERS, SALES RECORDS, PAYROLL, AND ASSET REGISTERS ALL LIVE HERE.
LAYER_02
INTELLIGENCE LAYER.
AI-ASSISTED TASKS FOR DATA ENTRY, REVIEW ROUTING, AND DECISION SUPPORT — OPERATING ON THE CLIENT'S OWN DATA PERIMETER, NOT A SHARED SaaS STACK. AI RUNS WHERE YOUR DATA LIVES.
LAYER_03
SIGNAL LAYER.
IIoT INPUTS FROM MACHINES, SENSORS, AND METERS — TRIGGERING BUSINESS RECORDS, ALERTS, AND AUDIT TRAILS IN REAL TIME. SIGNALS CAN CREATE INVENTORY ADJUSTMENTS, MAINTENANCE TICKETS, AND PRODUCTION RECORDS WITHOUT MANUAL ENTRY.
03 / MODULE_REFERENCE
FIVE MODULES.
ONE DATA BACKBONE.
ALL MODULES SHARE A SINGLE DATABASE. NO INTEGRATION MIDDLEWARE. NO DUPLICATE RECORDS. NO MODULE UPSELLS — EVERY MODULE IS INCLUDED IN THE BASE LICENSE.
FLAGSHIP_MODULE
INVENTORY MANAGEMENT.
THE CORE OF ARIA. DESIGNED TO CLOSE THE MOST COMMON SOURCE OF OPERATIONAL LOSS: INACCURATE, FRAGMENTED, OR DELAYED STOCK VISIBILITY.
BUSINESS_OUTCOME
ELIMINATES PHANTOM STOCK AT THE SOURCE.
REDUCES PROCUREMENT WASTE. ENABLES FULL TRACEABILITY FOR COMPLIANCE AND RECALL READINESS. THE INVENTORY RECORD MATCHES PHYSICAL REALITY — NOT LAST SHIFT'S MANUAL COUNT.
BUSINESS_OUTCOME
PREVENTS SURPRISE BREAKDOWNS. MOVES MAINTENANCE FROM REACTIVE TO PREDICTIVE.
KEEPS FINANCE AND OPERATIONS ALIGNED ON ASSET VALUE. IIoT CONDITION DATA — VIBRATION, TEMPERATURE, RUN HOURS — TRIGGERS WORK ORDERS BEFORE THE FAILURE HAPPENS.
LIFECYCLE_MODULE
ASSET MANAGEMENT.
EVERY MACHINE, VEHICLE, TOOL, AND PIECE OF INFRASTRUCTURE — TRACKED FROM ACQUISITION THROUGH DISPOSAL.
PRODUCTION_MODULE
MANUFACTURING EXECUTION.
CONNECTS THE PRODUCTION FLOOR DIRECTLY TO THE BUSINESS RECORD. NOT A STANDALONE SCADA LAYER — PRODUCTION MANAGEMENT THAT LIVES INSIDE THE ERP.
BUSINESS_OUTCOME
WHAT HAPPENS ON THE FLOOR BECOMES PART OF THE OPERATING RECORD IN REAL TIME.
ELIMINATES THE LAG BETWEEN FLOOR EVENTS AND BUSINESS VISIBILITY. OEE, YIELD, AND CYCLE DATA WITHOUT CLIPBOARDS.
BUSINESS_OUTCOME
SALES TEAMS OPERATE FROM THE SAME SYSTEM AS OPERATIONS AND FINANCE.
NO SEPARATE CRM DETACHED FROM THE BUSINESS RECORD. AVAILABILITY, RECEIVABLES, AND CUSTOMER HISTORY IN ONE PLACE.
RELATIONSHIP_MODULE
CRM.
BUILT FOR B2B SALES CYCLES WHERE RELATIONSHIPS DRIVE REVENUE AND ORDERS ARE SPECIFIC, NOT TRANSACTIONAL.
WORKFORCE_MODULE
HRMS.
WORKFORCE DATA TREATED AS OPERATIONAL DATA — BECAUSE IN MANUFACTURING, IT IS. ATTENDANCE AND CAPACITY DIRECTLY INFORM PRODUCTION PLANNING.
BUSINESS_OUTCOME
OPERATIONS AND HR STOP OPERATING IN SEPARATE SYSTEMS.
SHIFT SCHEDULES, SKILL AVAILABILITY, AND ATTENDANCE RECORDS FEED DIRECTLY INTO PRODUCTION PLANNING AND MACHINE ALLOCATION.
04 / DEPLOYMENT_&_OPERATIONS
DEPLOY WHERE
THE BUSINESS LIVES.
ARIA SUPPORTS THREE DEPLOYMENT PATTERNS. THE CLIENT CHOOSES THE MODEL THAT FITS THEIR INFRASTRUCTURE REALITY, LATENCY REQUIREMENTS, AND DATA RESIDENCY POLICY.
MODEL_01
ON-PREMISE INSTALLATION.
RUN ON LOCAL SERVERS INSIDE THE FACILITY. MAXIMUM LATENCY CONTROL, SIMPLEST DATA RESIDENCY, DIRECT ACCESS FROM THE SHOP FLOOR.
MODEL_02
PRIVATE CLOUD TENANT.
DEPLOY INSIDE A VPC OR DEDICATED PRIVATE CLOUD ACCOUNT THE CLIENT OWNS, WITH ISOLATED NETWORKS, STORAGE, AND SECURITY POLICY.
MODEL_03
HYBRID EDGE MODEL.
PROCESS MACHINE EVENTS LOCALLY AT THE EDGE, SYNCHRONIZE BUSINESS WORKFLOWS TO A CENTRAL INSTANCE. MACHINE DATA DOES NOT DEPEND ON NETWORK UPTIME.
WHAT THE
CLIENT CONTROLS.
NETWORK POLICY & PRIVATE ZONES
DEFINE NETWORK SEGMENTATION, FIREWALL RULES, AND PRIVATE NETWORK ZONES. ARIA OPERATES WITHIN THE CLIENT'S EXISTING NETWORK POLICY.
STORAGE & BACKUP SCHEDULE
CHOOSE STORAGE LOCATION, BACKUP FREQUENCY, RETENTION POLICY, AND RECOVERY PATHS. ALL DATA STAYS WITHIN THE CLIENT PERIMETER.
ROLE-BASED ACCESS PATHS
EXPLICIT PERMISSIONS PER ROLE. NO SHARED TENANT INFRASTRUCTURE. NO MULTI-TENANT VULNERABILITY SURFACE.
UPDATE & PATCH TIMING
NO FORCED VENDOR UPDATE WINDOWS. CLIENTS CHOOSE WHEN TO APPLY PATCHES AND SCHEDULE UPGRADE WINDOWS AROUND THEIR OPERATIONS.
SYSTEM
ADMINISTRATION.
ARIA IS DESIGNED TO BE OPERATED BY THE CLIENT'S OWN IT TEAM OR A DESIGNATED ADMINISTRATOR — NOT BY PIVOTR. THE FOLLOWING AREAS ARE UNDER CLIENT CONTROL FROM DAY ONE.
SECURITY_MODEL
YOUR PERIMETER.
YOUR RULES.
KEY_DISTINCTION
ARIA DOES NOT HOST YOUR DATA. PIVOTR DOES NOT ACCESS YOUR SYSTEM.
ONCE DEPLOYED, THE SYSTEM OPERATES ENTIRELY WITHIN THE CLIENT'S INFRASTRUCTURE AND AUTHORITY. SUPPORT IS PROVIDED ON REQUEST, NOT THROUGH STANDING ACCESS.
05 / GETTING_STARTED
FROM LICENSE
TO GO-LIVE.
THE PATH FROM PURCHASE TO PRODUCTION IS DESIGNED TO BE CLEAR, SEQUENTIAL, AND COMPLETABLE WITHOUT SPECIALIZED IMPLEMENTATION PARTNERS.
ACQUIRE THE LICENSE.
PURCHASE THE PERPETUAL LICENSE (₹49,999). ALL FIVE MODULES INCLUDED. NO PER-USER FEES. NO ADD-ON CHARGES. YEAR 1 SECURITY PATCHES INCLUDED.
PREPARE THE ENVIRONMENT.
CHOOSE YOUR DEPLOYMENT MODEL (ON-PREM, PRIVATE CLOUD, OR HYBRID EDGE). PROVISION THE HOST. CONFIGURE NETWORKING AND STORAGE.
INSTALL AND CONFIGURE.
DEPLOY ARIA TO YOUR ENVIRONMENT. CREATE INITIAL ADMIN USER. SET UP ENTITIES, WAREHOUSES, AND CORE BUSINESS CONFIGURATION.
CONFIGURE MODULES.
ACTIVATE AND CONFIGURE THE MODULES YOUR OPERATIONS NEED. START WITH INVENTORY (RECOMMENDED). ADD MES, ASSETS, CRM, AND HRMS AS YOUR WORKFLOWS REQUIRE.
CONNECT SIGNALS (OPTIONAL).
MAP IIoT DEVICES AND SENSORS TO BUSINESS RECORDS. CONFIGURE ADAPTERS FOR MODBUS, MQTT, OR REST INPUTS. DEFINE THRESHOLD RULES AND ROUTING.
GO LIVE AND OPERATE.
ONBOARD USERS AND ROLES. VALIDATE WORKFLOWS. MOVE TO PRODUCTION. YOUR TEAM OWNS THE SYSTEM FROM THIS POINT FORWARD.
ADOPTION_NOTE
START WITH WHAT MATTERS MOST. ADD DEPTH OVER TIME.
ARIA IS MODULAR — NOT IN THE SENSE OF UPSELLS, BUT IN THE SENSE OF OPERATIONAL PRIORITY. MOST CLIENTS START WITH INVENTORY MANAGEMENT AND EXPAND AS PROCESSES STABILIZE. EVERY MODULE ADDS DEPTH, NOT SYSTEM COMPLEXITY.
START WITH
INVENTORY
ADD WHEN READY
MES
CONNECT
IIoT
UNIFY
CRM + HR
YEAR_1_SUPPORT
SECURITY AND STABILITY PATCHES INCLUDED IN YEAR 1.
AFTER YEAR 1, AN OPTIONAL ANNUAL MAINTENANCE CONTRACT (AMC) IS AVAILABLE FOR EXTENDED SUPPORT AND CONTINUITY. THE LICENSE ITSELF NEVER EXPIRES.
QUICK_REFERENCE
WHY ARIA
EXISTS.
01
PERPETUAL LICENSE
PAY ONCE. OWN IT PERMANENTLY. NO SUBSCRIPTION TREADMILL.
02
CLIENT INFRA
RUNS ON YOUR HARDWARE OR PRIVATE CLOUD. NOT ON PIVOTR'S SERVERS.
03
SINGLE DATA MODEL
ALL FIVE MODULES SHARE ONE DATABASE. NO MIDDLEWARE.
04
IIoT NATIVE
SENSOR SIGNALS WERE PART OF THE ARCHITECTURE FROM DAY ONE.
05
NO PER-USER FEES
ADD TEAM MEMBERS, NOT BILLING LINES.
06
NO MODULE UPSELLS
ALL FIVE MODULES INCLUDED IN THE BASE PRICE.
07
AI ON YOUR DATA
AI ASSISTANCE ON YOUR OWN DATA PERIMETER, NOT A SHARED STACK.
08
DATA SOVEREIGNTY
OPERATIONAL DATA STAYS ON INFRASTRUCTURE YOU APPROVE.
09
UPDATE CONTROL
CHOOSE YOUR OWN PATCH AND UPGRADE WINDOWS.
10
MODULAR TODAY
START WITH WHAT YOU NEED. UNIFIED ALWAYS.
PRODUCT SUITE
DETAILED LOOK AT EACH MODULE, KEY CAPABILITIES, AND HOW THEY WORK TOGETHER.
→ VIEW PRODUCT
ARCHITECTURE
THREE-LAYER OPERATING CORE: ERP WORKFLOWS, AI INTELLIGENCE, AND IIoT SIGNALS.
→ VIEW ARCHITECTURE
IIoT ADAPTERS
MODBUS, MQTT, REST INGESTION, EDGE PROCESSING, AND SIGNAL ROUTING.
→ VIEW IIoT REFERENCE
SECURITY ENCLAVE
ACCESS CONTROL, NETWORK ZONES, AUDIT TRAILS, AND PATCH SOVEREIGNTY.
→ VIEW SECURITY
CONTACT / DEPLOYMENT_CONSULT
PLAN YOUR
ARIA ROLLOUT.
Share your current setup and deployment goals. We will respond with licensing clarity, infrastructure fit, and practical next steps for your team.
CHANNEL: TECHNICAL + COMMERCIAL HANDOFF
DEPLOYMENT MODES: ON-PREM / PRIVATE CLOUD