Embedded Systems, Risk and Two IT Business Models
Embedded systems, physical risk, safety and security; product and service business models. Open notes →
A chronological course in embedded software engineering: from engineering business and customer discovery to requirements, system architecture and delivery.
Embedded systems, physical risk, safety and security; product and service business models. Open notes →
Engineering roles, software, electronics, mechanics, procurement and manufacturing. Open notes →
How a company builds credibility and turns professional contacts into leads. Open notes →
Follow-up meetings, RFI, RFQ, RFC and a structured proposal. Open notes →
Standards, verification, scope, estimation and commercial engagement models. Open notes →
Discovery, stakeholder needs, requirements and the first system architecture. Open notes →
Prepare a consistent identity, contact card and focused technical one-pager. Open notes →
Review team materials, corporate roles and the architecture, PoC and MVP of a proposal. Open notes →
Role-play customer conversations, lead qualification and follow-up preparation. Open notes →
Post-conference reporting, follow-up invitations, meeting team, interactive client presentation and the transition to technical discovery. Open notes →
Customer meeting role-play: tailored presentation, team roles, discovery questions, RFI, delivery planning and IP rights. Read notes →
Second follow-up with experts, meeting roles, RFI, RFC and the proposal, how much to disclose, versioning, RFQ and team estimates. Read notes →
Phases with gates, the cone of uncertainty, Fixed Price versus Time & Material, capped T&M and combined models. Read notes →
HARA for the PoC, FP for in-house engineering and T&M for vendors, assembly levels and a 29-step EPIC 1 plan with gates. Read notes →
Gantt, PERT, risks and Monte Carlo, team cost, price by phase and full timing for a cell with CV+AI, Jetson and ROS 2. Read notes →