Service built around the equipment on the farm.
ASQ connects customers, dairy equipment, compatible components and service contracts. The office and the field team can work from the same installation context.
Explore the service workflowOne customer may operate several farms, barns and different types of equipment. ASQ keeps those levels separate, so components and maintenance can be discussed in the right context.
Customer and contact details connect the service records to the owner of the farms and equipment.
Each farm belongs to a customer and brings its barns and installed equipment into one location record.
The barn identifies where equipment is installed, so service planning refers to the right part of the farm.
Milking, feeding, cooling and robotic systems have their own components, maintenance needs and service records.
Select compatible parts for a specific installed system, review quantities and plan consumable deliveries. Favourites and visual identification support repeated selection, while replacement intervals connect the list to the maintenance plan.
Turn the agreed service scope into quotations, signed agreements and renewal records. Maintenance schedules, service protocols and PDF or TXT exports keep the planned work connected to the documents used by the office and field team.
The desktop client keeps essential service data available offline and synchronises the workspace after reconnection.
The customer register supports record creation, search and editing, Excel import and active or inactive status. Validation checks the data that links the customer to farms and installed systems.
The desktop workspace connects equipment configuration, maintenance plans and service documents. Administration views cover customer access, data publication and installed-equipment statistics.
A service specialist needs to establish which installation and subsystems are on the farm before choosing maintenance work.
The equipment hierarchy connects installed systems to technical details, subsystem configuration and component replacement settings in the desktop workspace.
Technical parameters describe the selected installation before its subsystems and components are configured.
Subsystem settings keep the equipment hierarchy connected to the configuration of each installed unit.
Component and replacement details give the service specialist a reference for maintaining the selected system.
The equipment record needs the correct components and quantities so that subsequent service planning refers to the actual configuration.
Component editing, subsystem selection and validation views let the specialist review and adjust those choices within the equipment record.
Component selection and quantity fields define the recorded composition of the installation being serviced.
Additional subsystem components extend the equipment record while preserving its connection to the parent installation.
Validation identifies incomplete component selections before the specialist continues with the equipment configuration.
A maintenance plan needs to account for both replacement materials and recurring tasks for the selected equipment.
Parts, consumables and task lists include quantities and service intervals, allowing the team to prepare the recurring maintenance scope together.
Materials are configured as part of the service scope, connecting the parts list to the planned maintenance.
Recurring tasks and their intervals describe what needs to be done and how often the equipment requires attention.
The task list provides a combined view of the maintenance work before service documents are prepared.
A standard maintenance list may need additional articles and contract settings to describe the service being prepared for a customer.
Additional-part selection and service-contract configuration keep those adjustments within the same service-planning workflow.
A service discussion needs to relate recorded liner measurements to replacement settings and a report that can be reviewed.
Liner Guide presents measurements, distribution and comparison charts alongside replacement frequency, carrying the recorded information into the report.
The distribution chart makes measurement differences visible before the team reviews replacement settings.
Configuration and replacement frequency connect the measured condition with the planned service interval.
The report keeps measurements available as a document the specialist can review during the service workflow.
The comparison chart sits alongside the recorded measurements in a report for reviewing the service assessment.
Planned service work needs a date, a reviewed task checklist and the documents used by the service team and customer.
Date selection, service protocols, confirmation and quotation-copy preparation connect the planned work with its document output.
The protocol brings the selected tasks into a checklist the team can review as one service document.
The confirmation step asks the specialist to review the requested action on the service protocol before proceeding.
Quotation-copy preparation connects the service offer with the document copies needed for the next step.
A field-service team needs to find the right customer and farm, then work with the contact details and systems belonging to that record.
The customer register connects contact editing with farm and installation selection, establishing the context for the service workspace.
Field work needs an explicit selection of farm access and a visible way to follow synchronisation of the working data.
Farm-access selection, synchronisation progress and confirmation expose the steps used to update the service workspace for online and offline work.
A service manager needs to know which team member covers each customer and set the access appropriate to that responsibility.
Team and customer views expose coverage, while member selection and permission-level controls support configuring access to the working records.
The customer list shows which working records are associated with the selected team member.
Customer-access settings connect working records with the people responsible for servicing them.
Permission-level selection lets the manager configure access for the selected team member.
Member selection identifies whose customer coverage and access settings are being reviewed.
Central administrators need to publish service data and inspect customer and equipment statistics within the selected country and language context.
The central web application combines publication settings with configurable tables, filters and charts for reviewing the selected data scope.
Shared statistics bring customer and installed-equipment records into a central overview.
Chart settings let the administrator adjust the statistical view to the scope being examined.
The table and chart offer complementary views of the selected customer and equipment statistics.
The equipment chart gives administrators a visual overview of the installed base in the selected scope.
Central Web App, Authentication Proxy App (APA), a JavaFX desktop client and a web application make up the system.
The desktop client uses JavaFX 21. A separate web application is also part of the project.
Central Web App and Authentication Proxy App (APA) are the named application components. The server stack uses Java 21/25, WildFly 36.0.1 and REST.
MS SQL Server 2012 stores application data. Liquibase manages changes to the database schema.
The team used NetBeans and IntelliJ IDEA for development, Maven 3.6.3 for builds, Git and GitLab for source control, and WiX Toolset for installation packages.
Show us one installed system, its component list and a typical service document. We will map the office and field workflow, including the information that must remain available without a connection.
Discuss your service platform
