Access Official Technical PDF

Share Summary:LinkedInEmail

Acer’s 2017 annual report describes a strategic shift from a primarily hardware-focused business toward a model combining hardware, software and services. For industrial automation professionals, the company’s Acer IoT strategy is relevant as an example of how an ICT provider sought to connect devices with cloud capabilities, applications and partner-delivered services. The report does not present a complete industrial control offering; instead, it outlines business priorities and initiatives that intersect with connected infrastructure, data services and smart transportation.

From products to integrated services

A central theme in Acer’s strategy was moving beyond the sale of individual devices. The company aimed to integrate hardware, software, cloud technology and services into solutions shaped around user needs. Its annual report also described an “Internet of Beings” concept: an ambition to provide life-enhancing services rather than simply deliver “things.”

For automation decision-makers, the broader point is about solution architecture and business models. A connected device has greater potential when it is part of a service that also accounts for applications, data handling and ongoing operations. Acer’s stated direction was to combine these elements while working with partners, rather than treating each product or technology as a standalone business.

The report’s organizational structure reflected this direction. Acer identified separate business areas for IT products, server products, e-business and BYOC (Build Your Own Cloud) smart products. Its e-business function included enterprise software development, systems integration and operation services, as well as mobile applications and vertical solutions. BYOC was described as covering cloud-connected devices and services, with access to software, platform and infrastructure offerings.

Acer IoT strategy: cloud and partner ecosystems

Acer’s 2018 business plan emphasized integrating new businesses with cloud technology and IoT. The company described cooperation with alliance partners and the development of service-integration solutions as part of its approach. It also identified a shift toward cross-platform cloud integration in the IoT sector, noting that cloud service providers needed partners across different fields to develop new services.

This model has practical relevance for system integrators and operations leaders evaluating connected projects. A deployment may involve equipment, connectivity, cloud resources, software and service providers, each with different responsibilities. The report’s emphasis on partner strengths and an ecosystem points to the coordination challenge: organizations must align the capabilities and commercial interests of the parties involved to deliver a coherent service.

Acer also connected cloud technology and big-data analysis with AI development. Its BYOC business description referred to an AI development platform for data scientists, including pre-built frameworks, models, datasets and resource management. The report establishes this as a business capability area, but does not specify industrial use cases, supported protocols or performance characteristics. Those details would need to be assessed separately for any automation project.

Smart transportation as a connected-services example

One of the report’s clearest examples of an IoT-related application was Acer ITS’s roadside smart parking meter solution. Acer reported that the solution received the Global ICT Excellence Award at WCIT 2018. The report also listed smart parking among the smart transportation solutions unveiled in 2017.

This example illustrates the company’s stated interest in applying connected technology to a service environment. It is not evidence of a particular factory automation deployment, but it shows how Acer positioned IoT-related capabilities beyond conventional computing products. The annual report also mentioned an intelligent mixology robot solution, the Acer MixBot, as another new-business initiative.

For industrial teams, these examples are best treated as signals of strategic direction rather than specifications for procurement. When considering a connected solution, technical evaluation still needs to establish how devices communicate, where data is processed, how systems integrate with existing infrastructure and who is responsible for ongoing operation. The annual report does not provide those implementation details for the initiatives it describes.

Implications for automation decision-makers

Acer’s approach highlights several considerations that apply when assessing IoT and cloud-enabled services in industrial environments:

  • Define the service outcome. Start with the operational or user need, then determine which combination of devices, software and services is required.
  • Map partner responsibilities. A multi-party ecosystem can bring together complementary capabilities, but project teams should clarify ownership, integration duties and service boundaries.
  • Evaluate the data and cloud model. Identify how data is collected and used, and assess the relevant platform and service requirements. The report outlines Acer’s cloud direction but does not provide project-specific architecture.
  • Address security and compliance. Acer’s business plan explicitly called for respect for international privacy and information-security laws, particularly in emerging areas such as AI and virtual reality. Industrial teams should apply appropriate requirements to their own systems and data.
  • Keep the product mix adaptable. Acer noted that product strategy and mix needed to respond quickly to changing market needs. In automation, that reinforces the importance of matching solutions to actual requirements rather than assuming one configuration suits every application.

Conclusion

Acer’s 2017 annual report presents a company seeking to combine devices, software, cloud technology and services, with partnerships playing a central role in its IoT direction. Its smart transportation initiatives and AI platform plans demonstrate areas of activity, while the report leaves technical deployment details unspecified. For industrial automation professionals, the practical takeaway is to evaluate connected offerings as complete service arrangements: confirm the operational purpose, integration approach, data responsibilities, security requirements and partner roles before deciding whether a solution fits the plant or infrastructure environment.

Access Official Technical PDF

About The Author