Home/About

About Symthosm

A company building safety-critical software tooling and advisory. The technical route starts in avionics and extends to rail, automotive and low-altitude aviation.

01 · COMPANY

Shanghai Symthosm Intelligent Technology Co., Ltd.

Symthosm works on one problem: every artifact and every change in a complex system must be identifiable, traceable and reproducible. The company focuses on safety-critical software across three lines — configuration management, the verification toolchain, and a partitioned operating system.

The commercial route is explicit: consulting builds trust, tooling generates cash flow, the platform builds the long-term moat. Not all core code is open; the open part builds reputation and an entry point into the industry.

ENTITY
Shanghai Symthosm Intelligent Technology Co., Ltd.
LOCATION
Pudong, Shanghai, China
FOCUS
Safety-critical toolchain, certification advisory, partitioned OS

Team background

Core members bring experience from Honeywell aviation programmes and the C919 airborne software project at AVIC/GE, plus Boeing and Airbus aircraft software testing; and from domestic rail control systems and first-generation optical access network equipment.

The team also contributes to the Ubuntu project and the Debian community, and the founder is an IEEE member. The full cycle — requirements, development, verification, authority review — is the same foundation for both tooling and advisory work.

DO-178C DAL A/B · ARINC 653 · EN 50128 · ISO 26262

02 · CREDENTIALS

Track record and community contributions, item by item

Technical judgement here comes from projects actually delivered, not from watching the industry. Each entry is checkable.

Track record
AreaContributionWho
Commercial aircraftParticipated in airborne software development for the C919, China's first domestically developed commercial jet, at the AVIC/GE C919 programme, covering requirements, development and certification flow. The programme owner remains the responsible programme entity.Founder
Optical accessParticipated in R&D related to China's first optical access network and first-generation optical transport equipment; this does not claim that the company independently developed the entire system.Founder
International programmesHoneywell A380 programme; Boeing and Airbus aircraft software testing and supportFounder
RailControl systems for several domestic urban rail lines: development, commissioning, operationsFounder
UbuntuUbuntu project contributor, systems and packagingTeam
DebianDebian community contributor, packaging and distribution processTeam
IEEEThe founder is an IEEE member. Individual professional membership does not imply IEEE certification or endorsement of the company.Founder

These entries describe engineering provenance and experience; they are not a certification claim. Project references defer to the project owners' public information.

03 · CAPABILITY

Four areas, each must land in documents and evidence

01ENGINEERING

Safety-critical software

Full-scope DO-178C and ARINC 653 work, C/C++ and kernel-level engineering.

02CERTIFICATION

Certification programmes

Complete documentation from requirements to certification, familiar with authority review and closure.

03TOOLING

Automated verification

WCET analysis, coverage, source-to-object consistency; the tools themselves organised to DO-330.

04COMMUNITY

Open source and research

Linux aerospace community participation, maintained projects, preprints — a searchable technical record.

Standards covered
StandardWhere it lands
DO-178CAirborne software lifecycle and §7 configuration management objectives, DAL A/B
DO-330Tool qualification level decisions, TOR and TOV&V organisation
ARINC 653 P4Partitioned kernel, major time frame, health monitoring
EN 50128Rail control software, SIL requirements
ISO 26262Automotive functional safety, ASIL verification activities

04 · ROADMAP

Get the local tool right first, then touch the server

2026 · now
Requirements and design baseline

Requirements baseline closed; architecture and detailed design in progress; domain model, evidence chain and command set converging.

M1–M2
Controlled repositories and acquisition

Platform permissions and immutability policy in place; fetch-to-SHA with three-level verification working.

M3–M4
Component freeze and system baseline

Four gates wired to CI; component freeze and system BOM closed; CCB approvals recorded.

M5–M6
Status accounting, bundles, qualification data

Environment configuration and build records connected; offline bundle verification complete; TQL-5 TOR and TOV&V evidence assembled.

Phase 2
Server-side component

The same kernel plus a platform component for server-side checks, automatic triggers and central audit — no rewritten domain logic.

Tell us where your programme stands

Whether you are setting up a system, choosing tooling, or stuck in certification, start with the situation. We give judgement, not a template.