Skip to main content

Onboarding with your forward-deployed engineer

A forward-deployed engineer from Constellation works through setup with you until your results reach your mission control system (MCS). The steps are the ones the Get set up checklist on the Integrations tab tracks, each ticked off from what the API reports, so you and your engineer see the same progress.

Write to contact@constellation.space to start, or with any question along the way. Accounts do not store a named engineer yet, so the checklist shows that address too.

The five steps​

The checklist, Get set up, heads the Integrations tab's Flow pane until every step is done, then it goes. A step made on another tab links to it; the rest are made on Integrations, in the group named below.

  1. Your own fleet loaded, on Fleet: done when your network config holds your satellites and ground stations; the demo fleet does not count, alone or beside your own. Pick them from the public asset catalog, then add the radio values only you know. Your engineer reviews the issues your network config reports. See Planned fleet and Network config.
  2. A live key, on API and MCP: done when the workspace has a live key that has not expired. Create a key opens New key, which asks what the key is for and ticks its scopes. Create one for each integration, with only the scopes it needs, so you can revoke one without breaking the others. See Authentication.
  3. Telemetry coming in, on Data in: done when a link of your own has reported in the last five minutes; the demo fleet's simulated telemetry does not count. Send each link's records while it is in view, with the fleet agent or POST /telemetry. See Data in.
  4. A workflow saved, on Automations: done when you have saved at least one. Start from a template, such as pass-yield, and save it. A test run over the window set in the builder's Price stage, the next 24 hours unless you change it, checks it without sending anything; see the Builder guide. A free audit of a week of pass logs shows what your passes delivered against what they could have.
  5. Results going out, on Results out: done when a bridge has checked in or a destination is active. Install the connector for your MCS until its bridge checks in, or set up a destination for Amazon S3, Grafana Cloud or a webhook. See Connectors and Results out.

Before recommendations reach your MCS​

Run your workflows on trial first: a trial records what each recommendation would have sent, and sends nothing. When the trial results look right, add an approval step so every recommendation waits for a person. See Recommendations and delivery and From trial to sending.

On an Enterprise deployment​

Your company has its own API host and Platform site. Your Constellation contact confirms both addresses, gives you your code name and team password, and enables features for your deployment. The steps above are the same; the differences are in Constellation for Enterprise.