The Thermo Scientific™ Niton™ Apollo™ handheld LIBS analyzer gives users confidence when engaging in Quality Control (QC) and Positive Material Identification (PMI).

SMAC electric gage actuators provide gaging solutions with consistent, fast and precise control of the process.

Our Introduction to Surface Roughness Measurement guidebook is an excellent initiation to noncontact surface roughness measurement. It offers practical information on various topics to help make roughness measurement easy and efficient.

Starrett is offering a comprehensive white paper that discusses why traditional approaches to measurement data collection are inefficient and error-prone without the ability to support IoT/ Industry 4.0. 

High temperatures in industrial settings are a leading cause of downtime. Controlling units and microprocessors age quickly under heat pressure, which means that generated heat must be removed efficiently or heat damage will occur.

It is impossible to overestimate the critical nature of keen and constant visual inspection in any production process. That’s why an advanced vision system is vital for any of today’s advanced production lines – as well as for “yesterday’s” older and more issue-prone lines. 

Quality is a non-negotiable point in manufacturing, especially when it comes to aerospace and defense parts.

This white paper explores how the automation of operations such as quality inspection and metrology – previously reserved for larger companies with hefty budgets – has changed dramatically with the advent of collaborative robots.

To help quality professionals understand how their processes and approaches compare to those of other companies and the future outlook, ENGINE interviewed quality and environmental health and safety (EHS) professionals to develop the present "2021 Quality Management Trends Report," commissioned by Veeva.

Orthopedic implants must function flawlessly even under the most demanding physiological conditions in the human body. Download the white paper here.

A Nikon Metrology XT H 225 ST computed tomography imaging system at the University of Arkansas is enabling non-destructive, 2D and 3D study of the inside as well as the outside of a wide variety of objects. Download the white paper to read more.

Explore the quality gates for the metal manufacturing process and the plastic manufacturing process in this whitepaper.

Overall Equipment Effectiveness (OEE) continues to gain in popularity as manufacturing teams seek to quantify plant and machine-level performance to find ways each area can be improved and keep production lines running at peak efficiency.

MA micro automation will be under operation of JR Automation.
The acquisition expands JR Automation's reach into global automation markets in medical, advanced battery and other fields.

White Egrets Canvas Enhanced by Lee Bogle is a(n) Limited Edition. The Edition is Limited to Limited Edition of 300 pcs

White Roses by Lee Bogle is a(n) Limited Edition. The Edition is Limited to Limited Edition of 195 pcs

White Rabbit by Daniel Arriaga is a(n) Limited Edition. The Edition is Limited to pcs

White Lilies in Soho by Brian Davis is a(n) Limited Edition. The Edition is Limited to Limited Edition of 295 pcs

White Radiant Roses by Brian Davis is a(n) Limited Edition. The Edition is Limited to Limited Edition of 195 pcs

Solitary White Iris by Brian Davis is a(n) Limited Edition. The Edition is Limited to 95 pcs

White and Magenta Orchids by Brian Davis is a(n) Limited Edition. The Edition is Limited to 50 pcs

White Roses Aglow by Brian Davis is a(n) Limited Edition. The Edition is Limited to 5 pcs

Last weekend a Lockheed Martin [LMT] Patriot Advanced Capability (PAC)-3 missile successfully intercepted a tactical ballistic missile (TBM) while integrated with RTX [RTX] Lower Tier Air and Missile Defense Sensor […]

The donation from Bradford White will help Mel Trotter Ministries meet the needs of struggling families and individuals in the Grand Rapids, Michigan, area through its annual Thanksgiving Day meal and turkey distribution.

The air365 Max with HeatForce heat pump can operate at 100% heating capacity with outdoor temperatures as low as -13°F and at 90% capacity down to -22°F.

As refrigerant regulations grow more stringent, manufacturers are beginning to offer new refrigeration architectures that utilize low-GWP refrigerants.

Sales of VRF systems continue to rise unabated, leading many to predict their shipments will increase by double digits annually for the foreseeable future.

Access Inc. will be the new manufacturers' representative for Hitachi VRF systems and SmartFlex™ systems in eastern Michigan and Northwest Ohio

This is the first of a series of Episodes on Software Architecture. Alex, Michael and Markus talk about rather fundamental topics in this episode, we'll go into much more detail in subsequent episodes in that series. Topics in this episode include:

• What is architecture, how is it different from design
• what different kinds of architecture are there in addition to software architecture
• the role of the architect, do we have one or more?
• architecture in agile software development
• tasks of the architect
• architect vs. the technical project lead
• architecture and project politics
• architecture requirements, estimating, team assembling

In this Episode, Michael and Markus continue the discussion about the fundamentals of software architecture (we're doing it without Alex, because it is really hard to find a suitable time for all of us on the phone :-)). We talk about the various quality attributes (such as performance, scalability, maintainability and many more) and how they relate to each other.

SOA (Service Oriented Architecture) appears to be just another hype - after all we have been building distributed systems for quite a while now. But the real value of SOA is non-technical. In this episode Eberhard and Markus discuss the advantages and disadvantages, what SOA actually is and how it compares to other approaches that have been tried out before.

In this third Episode on software architecture, Michael and Markus talk about the basic tools that an architect uses when architecting systems. These tools include things like separation, abstraction, compression and sharing. We also relate these tools to the quality attributes we introduced in previous archtecture episodes.

In this, as well as in the next episode Eberhard and Markus continue their discussion about SOA (the episode got too long, so we had to split it into two ... SOA 2a and SOA 2b). In this episode, we talk about the various perspectives on SOA (CBD, EAI, BPM), about fundamental requirements towards an SOA, and we discuss the role of models in defining sustainable architectures. We also discuss how a programming model based on the described approach typically looks like. We then discuss a number of issues any large-scale SOA faces (and for which the SOA paradigm does not really provide an out-of-the-box solution: In this episode we discuss data type ownership and (weak) typing of data types.

This is the second snippet of the SOA 2 double-episode. Eberhard and Markus continue the discussion with the issue of service reuse and a couple of development process issues. We also look at the duality between infrastructure development and application development in the context of an SOA. We then discuss the great spaghetti misunderstanding :-). We conclude this episode with a look at how to integrate BPM into the conceptual SOA framework we've built up to now, and we'll also briefly skim over a number of technologies related to SOA. Note that this episode, as well as the last one, is based on a set of slides; these can be downloaded from here. This episode covers slides 39 through 74.

In this episode Markus and our Guest Andy Longshaw talk about enterprise architecture. More specifically, we talk about some of the patterns in Andy Longshaw's and Paul Dyson's book Architecting Enterprise Solutions: Patterns for High-Capability Internet-based Systems. These includes things like replication, load balancing, monitoring and application management.

This is the fourth and final episode on the fundamentals of Software Architecture. We talk mainly about architectural styles and patterns, as introduced in the POSA 1 Book. We also discuss a little bit the process of actually using those patterns for architecting systems.

In this episode we talk about the relationship between software architecture and the business. Based on his book, Beyond Software Architecture we discuss how things such as branding, licensing, updating or different deployment scenarios influence the technical architecture of a system. We also discuss issues such as portability that add a huge amount of complexity, although from a business perspective it often does not make much sense. In the second part of the interview we discuss how the technical team and the business team can improve the way they work together. We look at some of the games (such as Buy a Feature or Give them a Hot Tub) from his new book Innovation Games, which discusses how to use collaborative play to be more creative and innovative in product creation.

Enterprise Architecture is already common practice in most Fortune 100 companies. As the topic is comparably young, knowledge about it is not so widespread in the Software Architects Community, who deals mostly with project architectures. In this episode Alex speaks with Wolfgang Keller who has practical experience as an enterprise architect and has written a book on the topic. He is a Partner with BusinessGlue Consulting. They are specializing in the relationship between EAM and SOA. This episode gives a rough overview what Enterprise Architecture actually is touches the standards in the field and also gives hints on the practical work of Enterprise Architects.

In this episode, Markus talks to Rebecca Wirfs-Brock on what she has learned from architecture reviews. This is a very complement to the earlier episode on architecture evaluation.

In this episode we talk with Klaus Marquardt about building systems out of plugins. After briefly introducing the concept of a plugin in contrast to modules and related software engineering concepts, we discuss different views on plugins and different ways of working with plugins for developing software. We are looking at plugins for embedded systems as well as large business systems, at how plugins change the working mode and team organization, and discuss the possibilities of why and when to use plugins for implementing software systems.

In this episode we discuss with Randy Shoup, Distinguished Architect at eBay, about architectural pinciples and patterns used for building the highly scalable eBay infrastructure. The discussion is structured into four main ideas: partition everything, use asynchrony everywhere, automate everything, and design the system keeping in mind that everything fails at some point in a large distributed system.

During Evolution of a software system, it becomes more and more difficult to understand the originally planned software architecture. Often an architectural degeneration happens because of various reasons during the development phases. In this session we will be looking how to avoid such architectural decay and degeneration and how continuous monitoring can improve the situation (and avoid architectural violations). In addition we will look at "refactoring in the large" and how refactoring can be simulated. A new family of "lint like tools for software architectures" is currently emerging in the marketplace I will show some examples and how they scale and support you in real world projects.

This is a discussion with Eoin Woods about his collection of top 10 software architecture mistakes. Looking at things that don't work is always a good way to learn what you should actually do.

This is another episode recorded at OOP 2009, thanks to SIGS Datacom and programme chair Frances Paulisch for making this possible. Here is the abstract from the conference program: Many software systems have fragile architectures that are based on brittle assumptions or rigid architectures that reduce options and make change difficult. On the one hand, an architecture needs to be fit for the present day, suitable for immediate use, and on the other it needs to accommodate the future, absorbing reasonable uncertainty. However, an approach that is overly focused on today's needs and nothing more can create an inflexible architecture. An approach that becomes obsessed with possible future changes creates an overly complex architecture that is unfit for both today's and tomorrow's needs. Both approaches encourage an early descent into legacy for a system. The considerations presented in this talk reflect an approach that is more about thinking in the continuous present tense than just the present or the future tense. This includes principles from lean thinking, practices common in agile processes and techniques for loosely coupled design.

This time we have John Wiegand on the mic for an episode on architectures and agile software development. We talk about the role of architectures in an agile world and why architectures change and need to change over time. We discuss the characteristics of those living architectures, using the Eclipse and the Jazz projects as examples, and the surrounding development methods for such environments.

In this episode, Robert talks with Nati Shalom about the emergence of large-system architectures consisting of a grid of high-memory nodes.

Micro services is an emerging trend in software architecture that focuses on small, lightweight applications as a means to avoid large, unmaintainable, monolithic systems. This approach allows for individual technology stacks for each component and more resilient systems. Micro services uses well-known communication schemes such as REST but also require new technologies for the implementation. […]

Gernot Starke talks about arc42: an open-source set of templates he developed to document software architecture based on his practical experience with real projects. Also Gernot and host Eberhard then discuss how documenting architecture fits into agile processes and how to find the right amount of documentation for a system. They walk through the different parts of the arc42 templates covering requirements and the context of the system and the solution structure, including building blocks, runtime, and deployment. They discuss tooling, versioning, testing documentation, and how to keep documentation up to date.