Many companies have treated EMC (electromagnetic compatibility), RF (radio frequency), and wireless compliance as simply a technical testing requirement to perform after developing their connected products. That is why, when a finished product appears functional and ready for production, some companies face an additional obstacle between the completed product stage and the market stage. That obstacle is compliance.
Connected-product companies can face significant commercialisation and time-to-market risk if their compliance planning is poor during their product development stage. The result of this could lead to product redesigns, delayed launches, additional testing, and potentially higher product development costs.
For this reason, compliance planning and considerations should not be left until the final stages of bringing a product to market. Instead, there should be more considerations made for compliance throughout the entire development process to avoid these additional costs.
A Product Can Be Technically Ready but Commercially Unready
There is a difference between a finished product and a market-ready product. Unfortunately, there continues to be a disconnect between completing product development and actually making a product ready to enter the marketplace. When companies don’t realise this, they are liable to face higher costs later.
Modern connected products are not just simple electronic devices. Each one is likely to have a series of sophisticated technical components, such as sensors, processors, Wi-Fi, power systems, cellular connectivity, and Bluetooth. A compliance consideration must be made for every technology introduced into a connected product.
So, what happens when considering compliance only after the product is finished? The reality is that it is extremely difficult to make even a minor change after finishing the product because all the components are installed and designs have been made. Making one little change will likely require new designs and components, which is where the high costs come into play.
The Hidden Cost of Discovering Compliance Problems Late
Many potential business consequences can occur from late-stage problems. These consequences include the following:
- Additional Engineering Work – If a finished product doesn’t meet particular compliance requirements, engineers may have to do additional engineering work to make the product compliant.
- Hardware or PCB Redesigns – A compliance issue may require a complete hardware or PCB (printed circuit board) redesign. That could require significant additional design work since these designs are often made in the early stages of development.
- New Prototypes – Engineering teams may be forced to build entirely new prototypes to meet compliance standards.
- Component Changes – Some compliance problems may be attributed to one or more components. If a component needs to be replaced, it could cause consequences for other parts of the product design.
- Repeat Laboratory Testing – Additional laboratory testing must take place whenever design changes are made to the product.
- Certification Delays – A product can take longer to receive certification as compliance issues remain unresolved.
- Missed Manufacturing or Launch Schedules – A company will likely be unable to meet its manufacturing and launch schedules if it discovers compliance issues too late in the development process.
- Delayed Revenue – A company won’t generate revenue from its product right away due to the delays caused by late-stage compliance.
All these business consequences cost time, resources, and money. Therefore, compliance needs to be both an engineering concern and a business concern throughout the product development process.
Why EMC Becomes More Complex in Connected Products
EMC, otherwise known as electromagnetic compatibility, refers to the ability for electronic devices to properly function in their intended environments without being impacted by electromagnetic interference. Today’s sophisticated connected products make EMC even more complex due to all the advanced processors, power systems, sensors, and circuits in them.
Failing to address EMC in the early development stages can lead to interference and immunity challenges after the final product is made. Considering EMC requirements during the early product design stage can give engineering teams an opportunity to account for potential EMC issues earlier rather than later.
EMC Testing is a supportive technical resource that allows engineers to evaluate the electromagnetic performance of their designs in the early stages. That way, if changes have to be made, they won’t cost as much time or money as they would later on.
Wireless Connectivity Creates Another Layer of Risk
We now live in the age of wireless connectivity. Most connected devices now have Wi-Fi, Bluetooth, cellular, IoT, and/or other radio technologies. Each one of these technologies introduces additional radio frequency (RF) and regulatory considerations and risks.
For instance, if a product development or engineering team were to change antennas, radio modules, enclosures, or other design elements late in their product’s development, it could have a major impact on the testing and compliance process.
Consistent RF and Wireless Testing throughout the development process is the best way to avoid timely and costly compliance issues regarding these wireless components.
When Compliance Becomes a Commercialisation Risk
The commercialisation risk is an even bigger reason to take compliance seriously. After all, a company’s entire revenue and profitability revolve around releasing and selling their products in the marketplace. Any costs or delays in this effort will impact the company’s business performance and ultimately threaten its sustainability to continue operating.
Companies shouldn’t delay compliance testing, or else it could impact the following:
- Product launch dates
- Manufacturing schedules
- Distribution agreements
- Customer commitments
- Market-entry plans
- Development budgets
- Revenue forecasts
A delay doesn’t necessarily mean that a connected product will fail commercially, but it can bring additional time and costs before the product launch. Compliance planning should therefore be considered as part of the product planning process to avoid these costs.
Higher-Stakes Products Require Even Earlier Planning
The consequences of compliance problems are particularly important for higher-stakes products, such as connected medical devices. It is an example of a product category where electromagnetic performance and regulatory considerations are vital because of their importance to end users.
However, the objective is not simply to ensure that a medical device performs as it was intended. Product teams also need to understand all relevant compliance considerations and how their product interacts with its electromagnetic environment. Medical Device EMC Testing in the early development stages can help teams gain this kind of technical insight and knowledge before the product ends up in its final stages.
Moving Compliance Earlier in the Product Lifecycle
Product teams need to plan for compliance earlier rather than later. They can do this by making the following considerations in the early stages:
- Identifying intended markets early
- Understanding applicable standards and requirements
- Reviewing compliance implications during design
- Considering pre-compliance testing where appropriate
- Assessing wireless technologies and components before finalising the product
- Maintaining appropriate technical documentation
- Allowing realistic time for testing and potential remediation
- Involving compliance expertise before the final prototype
Compliance as Part of a Product Strategy
As more products become connected, the boundary between product engineering, regulatory compliance, and commercial strategy is becoming increasingly blurred. Companies that incorporate compliance considerations earlier in development may be better positioned to identify problems before they become expensive late-stage obstacles.
For companies with connected products, the question is no longer simply whether a product works or not. It is whether the product has been designed from the beginning with a realistic path, starting from the prototype stage to the market stage.