Vantaa, FL-1610,
Finland
Are Oy Technographics
Are Oy Technographics, Software Purchases, AI and Digital Transformation Initiatives
Discover the latest software purchases and digital transformation initiatives being undertaken by Are Oy and its business and technology executives. Each quarter our research team identifies on-prem and cloud applications that are being used by the 3500 Are Oy employees from the public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources.
During our research, we have identified that Are Oy has purchased the following applications: Microsoft 365 for Collaboration in 2019, Atlassian Jira Service Desk for IT Service Management in 2020, Basware Source to Pay for Source to Pay in 2014 and the related IT decision-makers and key stakeholders.
Our database provides customer insight and contextual information on which enterprise applications and software systems Are Oy is running and its propensity to invest more and deepen its relationship with Microsoft , Atlassian , BasWare or identify new suppliers as part of their overall Digital and IT transformation projects to stay competitive, fend off threats from disruptive forces, or comply with internal mandates to improve overall enterprise efficiency.
We have been analyzing Are Oy revenues, which have grown to $486.0 million in 2024, plus its IT budget and roadmap, cloud software purchases, aggregating massive amounts of data points that form the basis of our forecast assumptions for Are Oy intention to invest in emerging technologies such as AI, Machine Learning, IoT, Blockchain, Autonomous Database or in cloud-based ERP, HCM, CRM, EPM, Procurement or Treasury applications.
Are Oy Tech Stack and Enterprise Applications
Are Oy Collaboration
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Microsoft | Legacy | Microsoft 365 | Collaboration | Collaboration | n/a | 2019 | 2019 |
In 2019, Are Oy implemented Microsoft 365. The Microsoft 365 deployment serves as the company’s primary Collaboration platform and its usage is observable on Are Oy's public website, aligning the application with enterprise communication and document workflows.
The implementation encompasses core Microsoft 365 capabilities typical for Collaboration deployments, including Exchange Online email and calendaring, Microsoft Teams for chat and meetings, SharePoint and OneDrive for document management and intranet content, and Azure Active Directory based identity and access controls. Administration is managed through a centralized Microsoft 365 tenant model and the Microsoft 365 admin center, enabling policy configuration, role based access, and platform governance across the organization in Finland. Functional coverage focuses on project teams, corporate communications, and document lifecycle management, with standard Microsoft 365 security and compliance controls applied as part of the configuration.
|
Are Oy ITSM
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Atlassian | Legacy | Atlassian Jira Service Desk | IT Service Management | ITSM | n/a | 2020 | 2020 |
In 2020, Are Oy implemented Atlassian Jira Service Desk to provide a centralized IT Service Management capability for its construction and real estate operations. The deployment is explicitly used on the corporate website, positioning Atlassian Jira Service Desk as the primary web-facing service portal for incoming service requests and incident reports, and tying the application name directly to the IT Service Management function.
The Atlassian Jira Service Desk implementation focuses on core IT Service Management modules, including ticketing, incident and service request workflows, SLA configuration, automated routing and a searchable knowledge base for self service. Configuration work emphasized request categorization, templated request types and workflow states to streamline request fulfillment and incident response within the service desk application.
Operationally the implementation provides a single web entry point hosted on the company website to capture external requests and to channel internal support activity into the Atlassian Jira Service Desk queue. Governance changes centered on formalizing ticket lifecycle rules, role based access controls, approval workflows and reporting for IT and customer facing service functions, aligning Are Oy, Atlassian Jira Service Desk, IT Service Management and business service operations.
|
Are Oy Procurement
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| BasWare | Legacy | Basware Source to Pay | Source to Pay | Procurement | n/a | 2014 | 2014 |
In 2014, Are Oy implemented Basware Source to Pay to consolidate purchase to pay operations for the technical building services business it acquired from Lemminkäinen. The Basware Source to Pay deployment was positioned inside the Source to Pay category to standardize invoice intake and matching workflows across the acquired units.
The implementation covered core purchase to pay capabilities, explicitly supporting invoice processing and matching that leveraged existing Basware IP 5.1 functionality previously used for invoice handling. Configuration work focused on preserving invoice ingestion rules, matching logic, and workflow-based approval routing, applying Source to Pay control patterns such as purchase order reconciliation, supplier invoice validation, and approval workflow automation to link procurement and accounts payable activities.
Integrations and operational continuity were managed by retaining the interface inherited from Lemminkäinen, maintaining existing invoice flows into Are Oy finance processes. Operational ownership rested with procurement, accounts payable, and finance teams within the technical building services unit, and rollout activities concentrated on consolidating P2P process execution under the Basware Source to Pay implementation.
|
|
|
|
|
Supplier Relationship Management | Procurement |
|
2014 | 2014 |
|
Are Oy PaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Apps Development | PaaS |
|
2019 | 2019 |
|
|
|
|
|
Transactional Email | PaaS |
|
2016 | 2016 |
|
Are Oy IaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Application Hosting and Computing Services | IaaS |
|
2015 | 2015 |
|
IT Decision Makers and Key Stakeholders at Are Oy
| First Name | Last Name | Title | Function | Department | Phone | |
|---|---|---|---|---|---|---|
| No data found | ||||||
Apps Being Evaluated by Are Oy Executives
| Date | Company | Status | Vendor | Product | Category | Market |
|---|---|---|---|---|---|---|
| No data found | ||||||