Analyze data.
Information from different areas becomes the basis for a joint evaluation.
Understanding data.
Recognize connections.
OS Logging further develops the existing alarm evaluation: into a common view of logs from OS products, servers, networks and third-party systems. With diagrams, event relationships and planned management reports.
Reporting already in operation · Broader logging platform in development.The data at a glance.
Data distribution
420DATA SETS7 days
All categories · 420 records
Development over time
7 daysAll records in the selected period.
44Mon
58Tue
72Wed
54Thu
65Fri
78Sat
49Sun
Day of the weekSUM 420
Categories in detail
Select time period and categories. The diagrams adapt to your selection.
ILLUSTRATIVE FEATURE PREVIEWAnalysis & Possibilities ↓Data analysis · Evaluations · Diagrams
OS LOGGING / MORE THAN ONE PROTOCOLLots of data.
Lots of data.
An understandable picture.
Individual entries only tell part of the story. OS Logging focuses on the evaluation: What happens frequently? How do the values change? Which patterns become visible?
Data becomes diagrams. Diagrams become an overview.
DATA
ANALYSISOVERVIEW
ANALYSISThe evaluation
makes the difference.
Understanding distributions.
Pie charts show which categories have what share of the whole.
Recognize developments.
Progress displays make changes visible over a period of time.
Compare categories.
Bar charts help to quickly classify magnitudes and differences.
Discover connections.
The joint observation helps to recognize patterns in the data.
Gain an overview.
Condensed evaluations make extensive data sets easier to understand.
An event.
The complete picture.
Alarm system, network, telephony and OS Board each tell a part. OS Logging is intended to connect the appropriate entries via identifier, object and time window into a comprehensible process.
INTERACTIVE CONCEPT EXAMPLEFour systems · one event
Alarm system
An event begins. The source provides timing, identifier and context.
Illustrative flow to explain the concept. No live data.
Many entrances.
Understandable answers.
Connect sources
OS products, alarm systems, servers, networks and third-party systems are planned. REST, webhooks, syslog, agents and file imports are intended to bring your data together.
Investigate events
Filter by source, time period, severity or range. The goal: to get from the diagram to the event to the original log entry.
Provide reports
Event reports and regular management reports with volume, trends and response times are planned. As a PDF or scheduled via email.
Reporting from practice.
The existing alarm evaluation processes REA/NFS events from Ascom Unite. This includes the alarm overview, a response timeline, device availability, key figures and charts.
More sources. More insight.
The expansion to include general log sources, cross-system correlation and management reports is the target image of OS Logging. Interfaces, storage and access rights are tailored to the application.
OS LOGGING / ONE LOG FOR EVERYTHINGThe whole process
The whole process
auswerten.
AQURA logs, OS Board events and other connected sources provide a common view of operations. The question determines which data is merged.
Calls & response times.
Evaluate alarm volumes and response times by ward or time period and compare developments.
Service & room change.
Consider the throughput times of the hotel industry and cleaning as well as technical tickets in context.
Devices & Availability.
Classify the availability of the end devices in addition to the process data.
Quality & Planning.
Use key figures and processes as a basis for quality reports and personnel planning. The preview above only shows sample data.
YOUR DATA. YOUR QUESTIONS.What would you like
What would you like
from your data?
We will show you OS Logging personally and discuss which data and evaluations are relevant for your use.
Continue to discover the product world.
THE NEXT STEP BEGINS WITH A CONVERSATION.OS BOARD / PRODUCTS HOUSE
What do you have
in mind?
An idea, a challenge, a concrete project.
We listen and think along.