
Telecom
Full site lifecycle from naming to on-air, complaints and capacity requests, verified drive tests and SIGNAL pixel intelligence. Available as a ready package.
Platform
AnyWork is a process engine with modules around it. Your processes run in the engine. The modules hold the people, vehicles, files and sites those processes use. Our team sets it up with you.
How it fits
A driver returns a drill at the end of a shift. Here is what each part of AnyWork does with it.
At the end of the shift the driver scans the drill, notes a cracked handle, adds a photo and signs on the phone.
Damage was reported, so the store manager approves the return and a repair task opens with a 24 hour deadline.
The tool goes back into stock, the photo is filed, and the handover shows up on the driver and the van.
Who, when, the photo, the signature, the approval and the repair task. Anyone with access finds it in seconds.
AnyWork reads and writes into the systems you already run, so the stock count and the repair cost are not typed again.
Modules
Each module does one job. Your processes use them, so the work and the record stay together. Start with what you need and add more later.
Every process is a workflow and its pages. Our team draws the workflow in FlowCraft and builds the forms in FlexiPage. From then on the engine sends each step to the right person, watches the deadline and moves the case on. When your rules change, we change the flow.
FlowCraft: the tool handover request, from request to ERP update.
FlexiPage: the request form, with the Condition field selected and its properties on the right.
Process Monitor: every running case, its status and its owner.
The AnyWork Assistant takes a request in plain language, asks for what is missing and carries it out in AnyWork, within the user's permissions and the rules of the process. Invoices are read straight into the form, and Code Generator turns a business question into code. People check the result before anything moves on.
Screens from the AnyWork mobile app: the AI Assistant and a receipt read by Expense Claim AI. Sample data.
HR, finance, fleet and inventory each keep their own records. A leave request reads the balance from HR, a handover updates the vehicle, a purchase lands in finance. Nobody exports a file or types the same thing twice.
Fleets / Vehicles, with the ERP menu open: HR, finance, products, fleets and more.
HR / Employee: every person with project, title and status.
A photo from a handover, a signed contract, a survey report: each one is filed with its case, its person or its site. Access is set per category and per document, so people only see what they are allowed to.
Document Management: recent files on top, folders below.
Inside a folder: files with their tags, size and date.
Set the work hours and break rules once, with exceptions for teams that work different shifts. Check-ins come from the phone or from fingerprint readers and similar devices at the door. Leave requests go through approval and the balance updates on its own.
Attendance Devices: fingerprint readers and similar devices, with the people matched to each.
My ERP / Time Sheet: check-in, check-out and duration for each day.
My ERP / Leaves: leave requests and their status.
Phones and vehicle trackers report their position. Dispatchers see everyone on one map and give the next task to whoever is closest. Each tracker is tied to a plate and a driver, so a position always has a name.
Mobile Tracking: crews and vehicles on the map.
Fleets / Vehicle Tracking: each tracker with its plate, driver and last update.
Door, temperature, gas, water and motion sensors sit on the floor plan where they are installed, and every reading lands in the log. A sensor can start a workflow during the hours and days you choose, and the task is followed in the Process Monitor like any other case.
IoT: the office floor plan with every sensor where it is installed, and the sensor log below.
Process Monitor, filtered: the cooling checks the temperature sensor opened.
Each base station has one record: technology, bands, equipment, alarms and visits. Find a site on the map or in the list. Open actions link to the processes that close them, from a cooling check to a final survey.
Base Stations: every site on the map.
RF / Sites: technology, band, type and status for each site.
Screens from the AnyWork app, with sample data.
Deployment
You do not have to replace anything to start. Most teams begin with the first and move inward over time. Cloud or on-premise.
AnyWork sits above the systems you already run and reads and writes into them. Nothing is retired.
Fastest start. Lowest risk.
AnyWork takes one step of the chain end to end and owns the data for that step.
When one process is the bottleneck.
A modular ERP with the process engine on top. Records, work and reports in one system.
When you are replacing a legacy core.
People and IT
Your teams work from the phone or the desk. Your IT team decides where it runs and who gets in.
Android and iOS apps: tasks, timeline, documents, notes and notifications.
Hours are entered in the mobile app by work type and sub-type, with a short note.
Approve a step or move it on straight from the email.
By email, in the app and as push notifications, set per step.
English, German, Turkish and Arabic.
Run it in our cloud or on your own servers, including Red Hat OpenShift.
Single sign-on with LDAP or Active Directory, and optional two-step login with Google Authenticator.
Access is granted by role. Documents are permissioned per category and per file.
AnyWork connects to these systems today. If yours is not here, ask us.
iClockMore from AnyWork
Drive test samples grouped into pixels on the map, pass or fail per coverage type, with the weakest cells listed for every pixel.
Explore Signal+AnyRouteBuild routes for measurement teams on the map, share them in the formats the vehicles use, and follow progress on one screen.
Explore AnyRoute