Jakie są godziny otwarcia?

Poniedziałek 08:30 - 16:30 Wtorek 08:30 - 16:30 Środa 08:30 - 16:30 Czwartek 08:30 - 16:30 Piątek 08:30 - 16:30

Endego, Ulica Kołowa 8, EDISON, Kraków (2026)

28/04/2026

AI in vehicles is scaling faster than the systems around it.

And that’s where the real risk begins.

AI is no longer limited to ADAS.

It is entering core vehicle electronics - from energy management to driver interaction and control systems.

This shift changes more than functionality:

→ compute load increases dramatically

→ validation becomes exponentially more complex

→ cybersecurity exposure expands across the system

The challenge is not adopting AI.

It’s integrating it into systems that were not originally designed for this level of complexity.

At Endego, we support OEMs and Tier 1s in making this transition viable - not just possible.

We combine:

• embedded integration across domains

• performance and system-level validation

• architecture alignment for scalable compute

• cybersecurity-aware development approaches

Because AI is not a feature.

It is a system-level dependency.

And without disciplined system engineering, it becomes a source of instability instead of advantage.

The real question is:

Are your systems ready for AI or are you just adding AI to systems that are not ready for it?

21/04/2026

Machines are connected. But true industrial performance starts with system integration.

That’s exactly why we’re at HANNOVER MESSE this week.

As one of the leading events for industrial transformation, automation and smart manufacturing, it’s the right place to discuss what happens beyond individual technologies - when complex systems need to work together.

At Endego, we support industrial and automotive companies in solving integration challenges across:

• mechanical, electrical and thermal engineering

• system architecture and validation

• simulation and production readiness

• product engineering and industrial automation

Because scalability is not built by connecting components.

It is built by connecting systems.

Meet us at HANNOVER MESSE on April 21 - 22 and let’s talk about how to make your engineering setup ready for real industrial performance.

On-site:

👉 Damian Dziedzic

👉 Piotr Kędrak

👉 Jakub Szylar

15/04/2026

Machines are connected. Systems are not.

That’s the real bottleneck of industrial digitalization.

HANNOVER MESSE showcases the latest in smart factories, automation and scalability.

But the real challenge starts when these technologies need to work together:

→ fragmented architectures

→ disconnected engineering domains

→ late integration decisions

At Endego, we see this every day.

We support industrial and automotive clients as a system-level engineering partner, connecting:

• mechanical, electrical and thermal domains

• system architecture and integration

• validation, simulation and production readiness

• product engineering with automation and production systems

From concept & feasibility… through architecture definition and simulation - to production-ready systems and industrialization support.

Because real performance doesn’t come from individual components.

It comes from how the system works together.

We’ll be at HANNOVER MESSE (April 21–22).

Let’s talk about how to make your systems truly scalable.

09/04/2026

Is your wiring harness still designed too late?

In modern vehicle programs, the wiring harness used to follow architecture decisions.

That is no longer the case.

Electrification and zonal architectures are fundamentally redefining the role of harness engineering.

Weight reduction targets are becoming more aggressive.

High-voltage and 12V systems must coexist.

And electrical architectures are shifting toward distributed power and data zones.

The result?

The wiring harness is no longer just infrastructure.

It is a strategic element of vehicle architecture.

What changes in practice?

• routing must adapt to zonal layouts and shorter distribution paths

• shielding becomes critical due to HV systems and EMC requirements

• packaging constraints require early cross-domain alignment

• weight optimization becomes a system-level trade-off, not a local decision

In this environment, late-stage harness design leads to inefficiencies, rework, and avoidable costs.

From our experience at Endego, successful programs treat harness engineering as part of early architecture definition - not as a downstream activity.

This means integrating:

• routing strategies with vehicle layout decisions

• shielding concepts with system-level EMC requirements

• weight optimization with cross-domain engineering constraints

Because in electrified and zonal vehicles, harness design is no longer about connecting components.

It is about enabling the architecture.

The leadership question is no longer:

“How do we optimize the harness?”

But:

“How early do we integrate harness engineering into system design?”

Organizations that move harness engineering into the concept phase will reduce complexity, cost, and integration risk.

The others will manage consequences later.

02/04/2026

It finally feels like spring - a welcome moment to slow down a little, take a step back, and enjoy a short break from the everyday pace.

We hope this Easter time gives you the opportunity to recharge, spend some quality time with your loved ones, and simply reset before diving back into the weeks ahead with fresh energy and a clear mind.

Thanks for being with us - we really appreciate it 💛

30/03/2026

Great to be part of Industrial Spring at Targi Kielce this year!

During the event, Damian Dziedzic and Piotr Kędrak represented Endego, engaging with engineers, partners, and technology providers from across the manufacturing industry.

This year’s edition clearly showed:

👉 a strong focus on practical, implementable automation

👉 growing importance of digitalization in production environments

👉 increasing demand for flexible engineering support in ongoing projects

For Endego, it was a valuable opportunity to exchange insights, strengthen relationships, and better understand the evolving needs of the industry.

Thanks to everyone we had the chance to meet - it was great to exchange perspectives in person.

24/03/2026

Bus Front Underrun Protection Device is not what you expect it to be.

Let's analyze the difference between common industrial special vehicle & bus.

In heavy trucks, front underrun protection is usually a clearly defined component - a dedicated cross-member mounted to the frame.
In buses, however, the situation is often different.

This is the focus of UN ECE Regulation No. 93 (R93) - the homologation framework defining requirements for front underrun protection (FUP) and front underrun protective devices (FUPD).

In practice, for many buses the underrun protection is not a separate device.
Instead, the function of the FUPD is frequently fulfilled by the vehicle structure itself, most commonly the floor and the front structural members connected to it.

This means that during the R93 test, the loads are not absorbed by a dedicated bumper beam, but by the load-bearing structure of the vehicle.
As a result, the structural response depends on the global stiffness of the front body section rather than on a single component.

This is a fundamental difference compared to rear underrun protection under Regulation 58, where the RUPD is typically designed as a separate protective system with clearly defined geometry and mounting points.

From an engineering perspective, R93 for buses requires careful consideration of:

▪︎ load paths in the front body structure
▪︎ stiffness of the floor and lower frame members
▪︎ connections between longitudinal members, cross-members and pillars
▪︎ integration of the front module with the load-bearing structure

Even small design changes - such as front layout modifications, floor height adjustments or changes in structural joints - may significantly affect the ability of the vehicle to meet the required force levels.

In industrial development, Finite Element Analysis (FEA) has become an essential tool in R93 assessments:

▪︎ predicting global deformation of the front structure
▪︎ verifying force transfer into the floor and side members
▪︎ identifying local overstress in joints and attachments
▪︎ reducing the risk of failure during physical homologation tests

In front underrun protection for buses, compliance is rarely about a single beam.

The key is how the entire front structure - especially the floor - participates in absorbing the load.

If you work with bus structures or vehicle homologation: have you ever faced a case where the floor design decided the R93 result?

17/03/2026

Cybersecurity is moving from IT risk to product liability.
The EU Cyber Resilience Act makes that shift official.

Many organizations still treat the EU Cyber Resilience Act (CRA) as a future compliance exercise.

That is a dangerous assumption.

Because the CRA is not simply another regulatory framework.
It fundamentally changes where cybersecurity sits in product development.

For the first time, cybersecurity moves directly into product liability territory.
This means the question is no longer:

“Do we have cybersecurity documentation?”

The question becomes:

“Was cybersecurity embedded into the product architecture from the beginning?”

Under the Cyber Resilience Act, security cannot be addressed late in development through documentation, testing, or isolated countermeasures.
It must be designed into the system.

What does this change for engineering teams?
• cybersecurity must be integrated into system architecture decisions
• TARA analyses must be performed at both system and microcontroller level
• secure software development becomes a core engineering process
• validation strategies must include security verification from early phases

In other words, cybersecurity becomes a system engineering discipline.

From our experience at Endego, true compliance with ISO 21434 and the upcoming CRA requirements comes from a different approach:

• cybersecurity embedded directly into system architecture decisions
• security processes aligned with real engineering workflows
• teams that understand both regulatory requirements and the technology beneath them

In practice, this means working with ISO 21434–aligned processes, performing TARA at system and microcontroller level, designing secure architectures, and supporting secure software development from the earliest development phases.

Not because regulations demand it.

But because this is how robust and resilient products are built.
The organizations that will succeed in the next regulatory wave will not be the ones reacting fastest in 2026.

They will be the ones making the right architectural and organizational decisions today.

Because cyber resilience is no longer only a security topic.

It is a leadership topic.

11/03/2026

Modern rail programs rarely fail because of technology.

They fail because of interfaces.

Passenger information systems, predictive maintenance platforms, connectivity layers, cybersecurity requirements - modern rolling stock is becoming a complex digital system.

But many rail development processes are still structured for a different era.

The result?

System engineering is increasingly becoming the bottleneck.

Not because of lack of expertise - but because interface complexity is growing faster than integration discipline.

In modern rail programs, success is rarely limited by individual technologies.

It is limited by how well those technologies are connected.

What changes in digital rail platforms?

• More subsystems interacting across domains

• Higher dependency between hardware, software and network architecture

• Increasing safety and cybersecurity alignment requirements

• Validation strategies that must account for system behaviour — not only components

This shifts the center of gravity in engineering.

Requirements management becomes critical.

Interface governance becomes essential.

Validation planning must start earlier - at system level.

Rail transformation is often discussed in terms of digital technologies.

But the real challenge is integration.

From our experience at Endego, successful programs apply system engineering discipline closer to what we see in advanced automotive development: clear architecture ownership, structured requirements flow, and validation strategies aligned with system complexity.

Because in modern rail platforms, innovation does not fail at the component level.

It fails at the interfaces.

And interfaces are where system engineering matters most.

09/03/2026

When 40 tonnes stop in a fraction of a second. What protects the driver?

In heavy-duty vehicles, one of the most critical accident scenarios is a frontal impact. In such events, driver safety depends not only on restraint systems, but primarily on the structural integrity of the cab.

This is the Focus of UN ECE Regulation No. 29 (R29) - the homologation framework defining strength requirements for commercial vehicle cabs with regard to occupant protection.

R29 evaluates the ability of the cab structure to preserve a driver survival space under defined loading conditions.

The regulation includes three main structural tests:

▪︎ Test A - frontal pendulum impact (29.4 kJ for N1/N2 ≤7.5 t, 55 kJ for N3 vehicles), applied to cab-over-engine configurations

▪︎ Test B - A-pillar impact (29.4 kJ) simulating a 90° rollover scenario

▪︎ Test C - roof crush test, where the roof must withstand a static load up to 98 kN

The objective is consistent across all cases:

After the test sequence, the cab structure must not intrude into the defined driver survival space.

The structural response depends on multiple factors:

▪︎ vehicle mass and impact configuration

▪︎ stiffness distribution within the cab frame

▪︎ load path continuity between pillars, cross-members and floor structure

▪︎ joint performance and material plasticity behaviour

Even seemingly minor design modifications - such as changes in front-end packaging, mounting interfaces or material grades - can significantly influence structural performance during homologation testing.

In practice, Finite Element Analysis (FEA) has become essential in R29 development. It helps engineers:

▪︎ predict deformation modes under impact and roof loading

▪︎ identify high strain concentration zones early in development

▪︎ optimize stiffness-to-weight ratio within packaging constraints

▪︎ reduce the risk of late-stage physical test failures

But the hardest part of R29 development is often not the simulation itself.

It is convincing stakeholders early enough that a seemingly small design change may require a complete structural reassessment - or even a new homologation test.

In R29 assessments, compliance is not achieved by stiffness alone.

The key is a well-designed load path and controlled structural collapse.

If you work with cab structures or vehicle homologation:

what design decision turned out to be the most critical in your R29 development?

If you’d like to discuss R29 development or cab structural performance in more detail, feel free to reach out to Oskar Plata or Michal Gbyl.

03/03/2026

Most electrification strategies focus on battery capacity.

That’s a mistake.

In e-bus programs, long-term durability is rarely limited by the battery itself.

It is limited by thermal architecture.

High-voltage systems now operate under sustained thermal stress:

continuous current, fast charging, dense routing, compact packaging.

Heat does not cause immediate failure.

It causes gradual degradation.

Connector reliability drops.

Insulation ages faster.

Voltage stability fluctuates.

Operational costs rise - years into service.

Electrification is no longer just a powertrain transition.

It is a system-level thermal integration challenge.

And thermal architecture cannot be engineered in isolation.

It requires alignment between:

➡︎ HV and 12V systems

➡︎ routing strategies and packaging constraints

➡︎ shielding concepts and real operating loads

➡︎ simulation and real-world validation

At Endego, we support bus OEMs and suppliers in integrating thermal strategy at the architecture level - combining HV/12V system design, optimized routing, shielding expertise and simulation-backed packaging decisions.

Because durability is not validated at the end.

It is designed from the beginning.

The strategic question for leadership teams is not:

“How fast can we electrify?”

But:

“How resilient is our architecture under sustained thermal stress?”

If thermal integration is not part of your executive eMobility roadmap, you are managing symptoms - not risk.

02/03/2026

December 2027 is the compliance deadline.

September 11, 2026 is the real engineering milestone.

By then, organizations placing digital and connected products on the EU market must demonstrate measurable progress toward Cyber Resilience Act compliance - not plans, but implemented cybersecurity capabilities.

For CTOs and Engineering Leaders, this is not primarily a legal challenge.

It is an architecture, process, and lifecycle challenge.

The key question is no longer whether cybersecurity will be required, but whether it is structurally embedded in your product development model.

At Endego, we support organizations in translating CRA and ISO 21434 requirements into engineering reality:

✅ ISO 21434-aligned development processes, including TARA and MCU-level threat analysis

✅ Security-by-design system architectures (secure boot, HSM integration, SSL/TLS, AUTOSAR stack protection)

✅ Runtime protection mechanisms such as IDS/IPS and secure communication frameworks

✅ Secure OTA strategies enabling controlled updates and vulnerability response

✅ Risk-based vulnerability management aligned with Linux and embedded platform policies

In practice, CRA readiness depends on decisions made today at system and software architecture level - long before certification or audit phases begin.

Engineering leaders increasingly ask:

• Can our architecture demonstrate cybersecurity by design?

• Do we control risks across the full product lifecycle?

• Are security responsibilities integrated into development workflows?

• Can we provide technical evidence of compliance when audited?

CRA readiness depends on engineering decisions being made well before the 2026 checkpoint.

Our experts will be attending Embedded World, 10 - 12 March 2026, Nürnberg and are available to discuss practical approaches to CRA readiness - from architecture decisions to implementation strategies.

Let’s connect!

Endego

28/04/2026

21/04/2026

15/04/2026

09/04/2026

02/04/2026

30/03/2026

24/03/2026

17/03/2026

11/03/2026

09/03/2026

03/03/2026

02/03/2026

Adres

Godziny Otwarcia

Telefon

Strona Internetowa

Ostrzeżenia

Skontaktuj Się Z Firmę

Skróty

Udostępnij

Kategoria

Poniedziałek	08:30 - 16:30
Wtorek	08:30 - 16:30
Środa	08:30 - 16:30
Czwartek	08:30 - 16:30
Piątek	08:30 - 16:30