ISO 26262
Functional safety
ISO 26262-aware hardware partitioning, including ASIL decomposition such as ASIL B(D) + ASIL B(D), agreed with your functional-safety manager.
Industries
From EV battery management systems to ADAS sensor fusion hardware, we design automotive-grade electronics designed to ISO 26262, AEC-Q and ISO 16750 requirements, built with AEC-Q-qualified components.
What we build
Custom BMS PCB design with AEC-Q-qualified components: cell voltage/temperature monitoring, active/passive balancing, SOC/SOH estimation, isolation fault detection, and CAN FD communication for EV and hybrid applications.
Hardware platforms for radar, LiDAR, and camera sensor fusion. Real-time object detection processing boards with automotive-grade Ethernet, GMSL2 interfaces, and ISO 26262-aware hardware partitioning agreed with your functional-safety manager.
Vehicle-to-everything hardware supporting C-V2X (LTE-V2X PC5, 5G-V2X) and, for EU ITS-G5 deployments, IEEE 802.11p, with GNSS modules. Designed for V2V, V2I and V2P applications to ISO 26262 requirements for the ASIL allocated by your safety concept.
SWC development and BSW/RTE configuration on your licensed AUTOSAR Classic stack, and SOME/IP service integration for AUTOSAR Adaptive platforms.
Multi-layer PCB design with AEC-Q100/Q101/Q200-qualified parts for the required temperature grade (e.g. Grade 1: –40 °C to +125 °C), automotive-grade laminates, IPC-6012DA fabrication requirements, vibration/shock design to ISO 16750, and conformal coating for harsh environments.
Hardware design and firmware for CAN FD, LIN 2.x, FlexRay, and 100BASE-T1/1000BASE-T1 Automotive Ethernet network nodes, gateways, and diagnostic interfaces.
Applications
Standards
Functional safety
ISO 26262-aware hardware partitioning, including ASIL decomposition such as ASIL B(D) + ASIL B(D), agreed with your functional-safety manager.
Component qualification
We select AEC-Q100 (ICs), AEC-Q101 (discretes) and AEC-Q200 (passives) qualified parts for the required temperature grade, e.g. Grade 1: –40 °C to +125 °C.
Environment and EMC
Designed to ISO 16750 electrical, mechanical and climatic load requirements and CISPR 25 emission limits, verified at accredited test labs.
Cybersecurity and software updates
Threat analysis and risk assessment (TARA), secure boot and authenticated OTA updates, with evidence for the vehicle maker's cybersecurity and software-update management systems.
India homologation
Designs prepared for Indian homologation testing at ARAI or ICAT: EMC (AIS-004 Part 3) and traction-battery safety (AIS-038 Rev 2 for M/N vehicles, AIS-156 for L-category vehicles).
ECU software integration
SWC development and BSW/RTE configuration on your licensed AUTOSAR Classic stack; SOME/IP integration for Adaptive platforms.
In-vehicle networks
In-vehicle network hardware and firmware for CAN FD, LIN, FlexRay and 100BASE-T1/1000BASE-T1 Automotive Ethernet.
Validation
Hardware- and software-in-the-loop testing and validation support.
How we work
Requirements analysis, technical feasibility and component availability, including the functional-safety partitioning.
Detailed system design and AEC-Q qualified component selection, with design review, signal-integrity and power analysis.
Prototype hardware fabrication and firmware development, with code reviews and hardware verification.
Functional, environmental and regulatory testing, with HILS/SILS testing and validation support.
Proof
Connected Fleet
Logistics and transportation company
FAQ
Yes. We develop software components (SWCs) and configure the BSW and RTE on your licensed AUTOSAR Classic stack, and integrate SOME/IP services on AUTOSAR Adaptive platforms. The AUTOSAR stack itself is licensed from a commercial vendor by you or your Tier 1.
Prototype delivery typically takes 8-14 weeks depending on complexity. Production-intent designs with full automotive qualification can take 6-12 months, including testing and iteration cycles.
Yes. We select AEC-Q100 (ICs), AEC-Q101 (discretes) and AEC-Q200 (passives) qualified parts for the required temperature grade (e.g. Grade 1: –40 °C to +125 °C) and specify automotive-grade laminates and IPC-6012 Class 3 with the automotive addendum (IPC-6012DA) on the fabrication drawing.
We design full BMS hardware including cell voltage monitoring, state-of-charge estimation, active/passive balancing circuits, isolation monitoring, and CAN FD, LIN and isoSPI/daisy-chain cell-monitor links.
Yes. We design hardware and develop firmware for CAN FD, LIN, FlexRay, Automotive Ethernet (100BASE-T1), and MOST bus systems.
Each project is quoted as a fixed-scope proposal: a statement of work with milestones, deliverables and pricing, sent within 3–5 business days of the discovery call. The price depends on the requirements, how mature the design is, technical complexity, the number of prototype iterations and the validation scope. Longer engagements can also run as a retainer or a hybrid of both. For budgeting before you contact us, our hardware development cost benchmarks and the PCB design, firmware and IoT cost guides give indicative ranges with their assumptions stated. They are planning ranges, not quotes.
It depends on the scope and on what already exists when we start. As planning ranges from our cost benchmarks: a single PCB layout takes 2–6 weeks per board and embedded firmware 4–16 weeks. A connected (IoT) product takes 3–12 months from concept to a production-ready design, and a regulated medical device 12–24 months to a 510(k) submission-ready package; from idea to mass production, a typical connected product takes 9–18 months. The proposal sets out a dated milestone plan, and you receive weekly progress updates during the project.
You do. Our contracts assign the intellectual property in the project work product (schematics, PCB design files, firmware source code and documentation) to you on payment, and we hand over the source files, not only fabrication outputs or compiled binaries. The exact terms are set out in the signed agreement for each engagement.
Yes. We sign a mutual NDA before any technical discussion of your project. Send your standard NDA or use ours; we return it signed within one business day.
Yes. We are based in Hyderabad, India, and work with product teams in India, the United States, the United Kingdom, Germany, Japan, Australia, the Middle East and other markets. Our office hours are 10:30–19:00 India Standard Time (UTC+5:30), Monday to Saturday, and we schedule design reviews across time zones, typically from US Pacific to Central European time. Japan is 3.5 hours ahead of India, so our first four hours overlap the Japanese afternoon. Prototypes and documentation ship by international courier such as DHL or FedEx. Our hardware outsourcing guide covers what to agree before an international project starts.
Yes. We prepare the manufacturing release package — fabrication and assembly drawings, the BOM with approved manufacturers, programming files and test specifications — and hand it over to the contract manufacturer (EMS) you choose. If you have not chosen one, we help you evaluate candidates through technical capability assessments and a pilot build. See manufacturing support.
No. Rapid Circuitry does not hold ISO 9001, ISO 13485 or other certificates. Our processes are aligned with ISO 9001:2015, and we design products to the requirements of the standards that apply to them — for example IEC 60601-1 and IEC 62304 for medical devices (with design documentation structured so your ISO 13485 quality system can absorb it) and IEC 61000 for EMC — and we specify IPC-A-610 workmanship classes for assembly. We prepare the product and its documentation for certification testing at accredited laboratories; the certificate or approval is issued for your product by the laboratory, notified body or regulator.
A short, non-confidential description of the product and what it must do (sensors, connectivity, on-device processing), the target production volume and unit cost, the markets and regulations it must meet (for example FDA, CE or FCC), your timeline, and what already exists: a concept, a proof of concept, schematics, PCB files or firmware. After the NDA, the next step is a 30-minute discovery call with the engineers who would work on the project, followed by the fixed-scope proposal. Send a project brief to begin.
Explore