Home First "IoT and VR for business" meetup took place

First "IoT and VR for business" meetup took place

About Us

Published by admin

20 February 2019

109

On February 15, first IoT and VR Meetup for business took place in JET BI laboratory in BSUIR.

Students and employees of JET BI gathered to talk about the application of IoT and VR technologies on the example of real cases.

Julia Solomenko, Project Manager at JET BI, told how to reduce drivers' time to search for a parking space using Parking Cloud solution, and demonstrated smart sensors that are used to operate parking.

Maria Liferova, Project Manager at JET BI, and Nikolay Lasch, JET BI Salesforce Developer, talked about the project Smart Workspace. Thanks to the use of autonomous and energy-efficient motion sensors, the solution saves costs for office space and equipment due to their efficient use.

The founder of GKeyLab, Kirill Krasnogir and experts from JET BI, Maria Boiko and Denis Shpilevsky presented joint solution VR CRM in Real Estate. The idea of the project is to analyze consumer’s behavior and predict demand in real estate using VR glasses and neuro sensors. The speakers touched on both success and difficulties they had to deal with while working on the project. Everyone, who was interested, had a live-demo using VR glasses and learnt how the seen information was interpreted in Salesforce CRM.

Thanks to everyone who took part in IoT and VR for business meetup! Keep reading our news to learn the latest trends of IoT and VR technologies from JET BI team!

Gallery

Question to the expert

VR Salesforce Salesforce Custom Development IoT

We have available resources to start working on your project within 5 business days

1 UX Designer

1 Admin

2 QA engineers

1 Consultant

Related Articles

All articles

Is Salesforce Winning the Public Sector Race?

An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.

Why Your Salesforce Flows Are Agentforce's Biggest Problem

This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.

How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything

This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.