Globema

Globema Hello there! 👋 Here at Globema, we are crazy about maps and networks! 👩‍💻

Besides documents, your archive may also be quietly storing costs. 💸Physical space, filing, copying, maintenance, and al...
06/08/2026

Besides documents, your archive may also be quietly storing costs. 💸

Physical space, filing, copying, maintenance, and all those hours spent searching for the one document that’s never where it should be.

Individually, these costs may seem manageable. Together, they can turn a traditional archive into an expensive business barrier.

In the final post of our ROI of Document Digitization series, we’re looking beyond the filing cabinet to explore how digital transformation can reduce the cost and complexity of document management.

With iDoc Archive, documents become part of an intelligent, searchable digital environment instead of just another collection of files.

That means:

🔍 Faster access through full-text, attribute, object, and document search

📦 Less reliance on physical storage and manual filing

📊 Easier reporting, analysis, and audit preparation

🔗 Integration with ERP, CRM, GIS, BI, and other business systems

⏱️ More time for valuable work and less time spent digging through folders

You get an archive that doesn’t just take up space but actively supports your business processes.

Swipe through the carousel to discover the hidden costs of traditional archiving. And contact us to see how iDoc Archive can help turn your document storage into a smarter business resource! 📃💡

What does it take to manage thousands of kilometers of critical infrastructure without losing sight of a single asset?Pi...
05/08/2026

What does it take to manage thousands of kilometers of critical infrastructure without losing sight of a single asset?

Pipelines, storage facilities, fiber-optic infrastructure, and energy networks scattered across an entire country require reliable data and complete visibility. 🛢️🗺️

When information is spread around different systems and documents, maintenance, outage response, and investment planning become much more difficult.

Digital Twins give gas and oil operators a comprehensive, up-to-date view of their network assets, equipment, and technical documentation. They help predict outages, optimize operations, and make informed decisions about maintenance, modernization, and expansion.

Let’s look at a real-world example: PERN, a key operator of Poland’s energy infrastructure.

In 2009, PERN partnered with us to implement SeZaM, a network inventory and asset management system built on the GE Smallworld platform. It integrates digital models of pipeline, fiber-optic, and internal energy infrastructure within a single database.

The results are:

✔️ Centralized, reliable data
Easy access to current network and asset information in a spatial context.

✔️ Integrated operations
Data from systems such as SAP and SCADA is available in one place.

✔️ More effective maintenance
Better support for inspections, diagnostics, modernization, and outage management.

✔️ Connected fieldwork
GeoTask delivers optimized assignments to field teams and sends collected data back to SeZaM.

✔️ Specialized network analyses
Support for pipeline capacity management, anomaly analysis, and precise fuel-volume calculations.

Developed gradually in the Pay-As-You-Go model, SeZaM has evolved alongside PERN’s changing business needs and become a critical tool for its operations.

Want to see how integrated network models can support your infrastructure? Read the full PERN case study or contact us to discuss your needs! ➡️ https://bit.ly/4xrol57

And just like that, this is the final post in our Digital Twins Across Industries series. Which industry or use case did you find most interesting? 🤩

ETL, ELT, Zero-ETL… one letter can change your entire data strategy.Choosing an integration approach can have some serio...
04/08/2026

ETL, ELT, Zero-ETL… one letter can change your entire data strategy.
Choosing an integration approach can have some serious business consequences. Pick the wrong one, and you could end up with slow processes, unnecessary costs, or data that isn’t ready when your teams need it.

The truth is, there’s no universal “best” strategy.
The right choice depends on your data sources, processing speed, available resources, and (most importantly) what your organization wants to achieve.

Should you:

⚙️ Transform before loading with ETL for greater quality and consistency?

⚙️ Load first with ELT for faster imports and more flexibility?

⚙️ Query data at the source with Zero-ETL to reduce data movement?

⚙️ Use an integration platform to automate workflows without building everything from scratch?

⚙️ Or keep exporting spreadsheets manually? (Spoiler: probably not that one. 😉)

The goal is to find the approach that turns your data into reliable, accessible, and genuinely useful information.

Swipe through the carousel for a practical breakdown of the most common data integration strategies and where each one fits.

Want to explore the topic in more detail? Download our e-book, Data and System Integration: The Key to Business Success 👉 https://bit.ly/3NLjASh

Your engineers shouldn’t spend BEAD season counting cables in a spreadsheet. They have bigger problems to solve.Permitti...
30/07/2026

Your engineers shouldn’t spend BEAD season counting cables in a spreadsheet. They have bigger problems to solve.

Permitting delays, workforce shortages, material constraints... Routes that look perfect on a map, until someone discovers a railway, bridge, or very inconvenient gap in the pole line. 😶

Those are the challenges that need human expertise.

Repetitive calculations, manual drafting, equipment counts, and preliminary Bills of Materials? Not so much.

In our recent webinar with the Fiber Broadband Association, Winning the BEAD Race: Automated Fiber Design and Integrated Network Inventory for Faster FTTH Deployments, we explored how operators can accelerate fiber projects without asking already-stretched engineering teams to somehow find more hours in the day.

Automated fiber design can quickly turn project boundaries, address points, network structures, and engineering rules into a preliminary FTTH design. Engineers can then evaluate the results, apply their field knowledge, adjust the design, and make confident decisions. 🌐🦾

Automation isn’t replacing engineers, instead, it frees them to focus on the problems only they can solve. The machine handles the math, your experts handle the real world.

This is the first post in our three-part series unpacking the webinar’s biggest takeaways. Next time, we're gonna tell you how rapid design iterations help operators compare scenarios and make smarter network decisions.

And if you can’t wait to learn more, watch the full webinar recording! 👉 https://bit.ly/webinar-winning-the-bead-race

When listing a commercial property for lease, don’t just share the square meters and postcode. Everything around it matt...
29/07/2026

When listing a commercial property for lease, don’t just share the square meters and postcode. Everything around it matters, too.

For leasing teams managing properties across multiple locations, finding the right space for a client can be difficult when key location data is scattered or missing.

🚌 Is the building easy to reach by public transport?

🍽 Where will employees grab lunch?

⏱ How long will their commute take?

🏬 What about nearby services, and even air quality?

Now, commercial real estate teams can combine property data with its geographic context.

Geospatial information allows them to:

🔹 Quickly filter locations according to a client’s priorities

🔹 Compare access to transport, restaurants, shops, and services

🔹 Analyze commute times for different modes of transportation

🔹 Identify areas with high property availability

🔹 Present the building and its surroundings visually, not just describe them

That way, they can spend less time searching through disconnected data and have more confidence that the proposed location actually fits the customer’s needs.

Clients are choosing the daily experience of everyone who will work there and a map can reveal what a spreadsheet never will. If you want to explore how, get in touch with us! 🗺🦾

Close on a map doesn’t always mean close in real life. 🗺️❌A neat circle on a map can look convincing… until a bridge, on...
23/07/2026

Close on a map doesn’t always mean close in real life. 🗺️❌

A neat circle on a map can look convincing… until a bridge, one-way street, traffic jam, or a closed road turns 5 km into 25 minutes.

That’s a real struggle for teams building location-based products:

You don’t just need to know what’s close.
You need to know what’s actually reachable.

Because when distance-based assumptions go wrong, the impact is very real:

→ delivery zones that look good on paper but break SLAs

→ properties that seem “near the office” but fail the commute test

→ stores placed in areas that don’t serve the expected customers

→ fleets that appear well distributed but still leave users waiting

→ service areas that make sense on a slide, not on the road

But with Google Maps Platform’s Isochrones API, instead of asking:
👉 “How far is this from here?”
You can ask:
👉 “What can someone reach in 15, 30, or 45 minutes?”

The result is not a simple radius. It’s a travel-time area based on how people actually move through the road network by car, bike, or on foot, with routing constraints and traffic-aware options where needed.

For businesses, that means better decisions:

✅ more realistic delivery promises

✅ smarter real estate search experiences

✅ clearer store and branch catchment areas

✅ better fleet and micromobility planning

✅ service coverage that reflects reality, not geometry

If you’re wondering how this could work in your product or operations, that’s exactly the kind of question we like. Let's talk! 😎

Every telecom operator knows the moment:👷‍♂️ A technician arrives on-site.📱 The PNI says one thing.⚙️ The node says some...
22/07/2026

Every telecom operator knows the moment:

👷‍♂️ A technician arrives on-site.
📱 The PNI says one thing.
⚙️ The node says something else entirely. 😨
A previous crew made changes, but the system never got the memo.

Cue the classic field operations routine: checking, calling, guessing, delaying, documenting later… and hoping the next team doesn’t walk into the same surprise.

The real problem usually isn’t the inventory system itself. It’s the missing loop between network records and field reality.

That gap gets expensive fast:

❌ emergency tickets that disrupt planned schedules

❌ offline work in ducts, basements, and enclosed nodes

❌ subcontractor updates living outside the operator’s main workflow

❌ longer MTTR and higher SLA risk

❌ inventory data that slowly loses credibility

But when you integrate Smallworld PNI with GeoTask, you stop treating field operations and network inventory as two separate worlds.
The integration connects them in one operational flow:

✅ Work orders from Smallworld go straight into GeoTask

✅ Dispatching considers skills, availability, equipment, and location

✅ Emergency tasks trigger route recalculation

✅ Technicians get network context, visit history, and location data in the mobile app

✅ Offline updates sync automatically when connectivity returns

✅ Subcontractor work stays visible, controlled, and traceable

✅ Every field change can be linked to a crew and work order

At PLAY, one of Poland’s leading telecom operators, GeoTask integrated with Smallworld PNI helped reduce the time from ticket creation to technician dispatch to just a few minutes. AND it improved visibility across nationwide field operations!

Want to see how GeoTask could work with your Smallworld PNI setup, subcontractor model, and outage workflows? Shoot us a message and let's walk through it in a tailored demo. 🦾

FME 2026.2 is here! this update feels less like “new buttons in familiar places” and more like a serious productivity up...
21/07/2026

FME 2026.2 is here! this update feels less like “new buttons in familiar places” and more like a serious productivity upgrade for data integration teams, GIS specialists, and IT admins. 🦾

Building complex workflows is powerful but it often mean you got to juggle custom REST integrations, nested transformers, JSON syntax errors, field data scattered across multiple apps, and security settings. 🤯

In FME 2026.2, Safe Software tackles exactly those pain points:

🤖 AI agents can now talk to FME Flow more easily
With FME Flow acting as an MCP server, AI assistants like Claude, Copilot, or internal OpenAI-based tools can trigger FME workspaces without teams having to build custom REST integrations from scratch.

🔄 Loops finally live where they should: on the canvas
Native looping in FME Form means fewer complicated workarounds with Custom Transformers or WorkspaceRunner patterns. Iterative logic becomes easier to design, test, and maintain.

👷‍♂️ Field teams get an upgrade with FME Realize
Photos? Sure. But now also video, audio, and LiDAR scans collected directly from mobile devices and sent to the cloud for automated processing in FME Flow. That means one field interface instead of a small army of apps.

💻 JSON becomes a real destination format
With JSONObjectBuilder and JSONAppender, creating complex JSON payloads becomes more structured and reliable.

🛡 Security management gets cleaner
New predefined Security Tiers help admins align environments with corporate IT standards faster, while reducing the risk of misconfiguration. Especially useful when “audit-ready” is not optional.

And that’s not all, because this update also brings:

✔️ SFTP directory monitoring,
✔️ real-time parameter validation,
✔️ better restore options,
✔️ improved filtering in FME Flow,
✔️ new transformer updates,
✔️ pgvector support in PostgreSQL,
✔️ Google Cloud ADC authentication,
✔️ native Databricks geometry types,
✔️ CityGML 3 appearance support

All this make this release a very practical step forward, so that you've got more automation, fewer fragile workarounds, cleaner integrations, and better security. And a smoother path from data chaos to data that actually works for your business! 🚀

If you’re planning an upgrade to FME 2026.2 (or wondering how these changes could impact your organization) as an official FME VAR, Globema can help you map the safest and smartest way forward

When your team is stuck manually retyping data from piles of paper documents, fatigue is eventually going to win. A slip...
20/07/2026

When your team is stuck manually retyping data from piles of paper documents, fatigue is eventually going to win. A slipped decimal point here or a flipped contract date there may seem harmless at first.

But those tiny mistakes quickly snowball into flawed reports, missed payment deadlines, and compliance issues. ❌

You shouldn't have to second-guess the numbers driving your biggest business decisions.

In part three of our ROI of Document Digitization series, we’re talking about something just as important as speed: flawless accuracy.

AI takes over the tedious data extraction. It doesn’t get tired, it doesn’t need a coffee break, and it can even accurately interpret complex contexts and messy handwriting.

Here is what happens when you remove human error from the equation:

📊 You get clean, reliable databases so you can finally trust your reporting.

🛡️ You gain total control over contract statuses, payment amounts, and critical deadlines.

🧠 Your team can stop acting as proofreaders and actually focus on strategy.

When you truly trust your data, you can finally trust your decisions.

Swipe through our carousel to see how eliminating manual errors changes the game for your business. And if you're ready to stop second-guessing your data, shoot us a message. 🚀

How many times a week does someone on your team manually export a CSV from one app, just to import it into another? 🤦‍♂️...
16/07/2026

How many times a week does someone on your team manually export a CSV from one app, just to import it into another? 🤦‍♂️

The promise of data integration is supposed to end that misery. You just link your systems, data syncs perfectly in the background, and your business runs like a well-oiled machine.

In reality, it’s usually a tangled web of undocumented legacy systems, a mess of different formats (JSON, XML, CSV), and "jealous" software vendors that refuse to let their products play nice with third-party tools.

Add in the inevitable human errors from manual data entry, and your dream project can quickly hit a brick wall. ⛔️

We see organizations struggle with this all the time. But avoiding integration isn't the answer. You just have to do it strategically.

The secret to a successful integration isn't trying to force every single app into one rigid format or trying to integrate everything at once. It’s about building a resilient, scalable process. When you use vendor-neutral tools, automate data cleansing right at the input stage, and take a phased approach, you stop fighting your IT architecture and start actually leveraging your data.

We’ve mapped out the 5 biggest traps organizations fall into when integrating their systems, and exactly what you need to do to bypass them.

Swipe through our graphics to see what you're up against and how to fix it.

And if you want the complete step-by-step blueprint, it's all in our e-book: "Data and System Integration: The Key to Business Success".

Grab your free copy from the link 👉 https://bit.ly/3NLjASh

Adres

Wita Stwosza 22
Mokotów
02-661

Godziny Otwarcia

Poniedziałek 08:00 - 17:00
Wtorek 08:00 - 17:00
Środa 08:00 - 17:00
Czwartek 08:00 - 17:00
Piątek 08:00 - 17:00

Telefon

+48228487313

Ostrzeżenia

Bądź na bieżąco i daj nam wysłać e-mail, gdy Globema umieści wiadomości i promocje. Twój adres e-mail nie zostanie wykorzystany do żadnego innego celu i możesz zrezygnować z subskrypcji w dowolnym momencie.

Skontaktuj Się Z Firmę

Wyślij wiadomość do Globema:

Skróty

Udostępnij