The Skayl Product Line

CinC is the runtime. PHENOM is the optional companion.

CinC is where the integration happens. It accepts data and integration models from any source – your own MBSE tooling, third-party modelers, or PHENOM. PHENOM is the modeling platform we built to feed CinC efficiently when you don't already have one.

CinC · The Product

Configurable Infrastructure Capability

The runtime that turns integration into infrastructure.

CinC is the configurable integration platform that sits between mission systems as a model-driven layer. It mediates data, protocols, and semantics across heterogeneous components – without modifying OEM software, without bespoke glue code, and without forcing programs into recertification cycles.

CinC operates at the semantic layer, not just the transport layer. State and semantic alignment live in the infrastructure. That's what makes integration scale linearly – and what makes the methodology deterministic enough to bid as fixed-price.

CinC is a standalone product. It accepts data and integration models from any source – including customer-owned MBSE tooling and third-party modelers. PHENOM is one path to feed CinC. It is not the only one.

CinC delivers

  • Integration without modifying OEM software or application code
  • Recertification scoped to the change, not the platform
  • MOSA, SOSA, FACE, CMOSS, OMS/UCI, UDDL aligned
  • Data-centric – scales linearly with the number of systems
  • Deterministic methodology suitable for fixed-bid contracts
  • Accepts models from any source – PHENOM, your MBSE tooling, or third-party modelers
  • Customer-operable after initial setup

How CinC Works

A distributed runtime – embedded in every system.

Each mission system runs its own embedded CinC. The CinCs communicate peer-to-peer across the network. Change a configuration; the network adapts. No rebuild, no recompile, no full recertification cycle.

The Old Way

Custom bridges between every pair of systems.

10 CUSTOM BRIDGES

  • Custom code for every connection
  • Recompile on every change
  • Full recertification each cycle
  • Complexity grows as O(n³)

With CinC

Each system runs its own embedded CinC.

  • CinC embedded in every system
  • CinCs communicate peer-to-peer
  • No recompile when configuration changes
  • Delta-certify only what changed

The Principle

The integration is the configuration – not the code. Load a new config, and the network adapts.

– How it works · three steps

01

Define the integration

A data and integration model – produced by any MBSE tool – describes what data flows where, with full semantic meaning.

02

Load the configuration

Each embedded CinC reads its configuration at runtime. No rebuild. No recompile. Existing baselines stay untouched.

03

CinCs communicate

The runtime translates and routes data across the network – any platform, any protocol, semantically aligned end-to-end.

PHENOM · The Optional Companion

Model-Based Engineering, Built to Feed CinC

The fastest path from a system architecture to a CinC-ready model – for customers who want one.

PHENOM is the collaborative modeling platform Skayl built for teams that don't already have an MBSE capability – or want one purpose-built for integration architecture. Architects develop, validate, and track data, integration, and deployment models inside PHENOM. The output drops directly into CinC with no translation step.

PHENOM enforces FACE™ conformance natively and uses Skayl's FACE Conformant Domain-Specific Data Model (DSDM) as a foundation. It's a productivity layer – not a prerequisite. Customers who already have working modeling tooling can skip it entirely; CinC will accept their output the same way.

How PHENOM Works

  • Ingest documents & models
  • Extract semantic meaning
  • Build machine-readable DSDM
  • Generate configs

Human documentation → machine-readable models → CinC-ready output

Two Paths to CinC

Bring your own models. Or use PHENOM.

CinC is the destination. How you get there is your call. Customers with mature MBSE capabilities feed CinC from their existing toolchain. Customers without one can adopt PHENOM as the productivity layer Skayl built for the job. Either path lands at the same runtime.

Built On

MOSA·SOSA™·FACE™·CMOSS·OMS / UCI·UDDL·DO-178 Pathway

See it in your environment.

Tailored briefings for government program offices, defense primes, and systems integrators.