Fast-Track Releases

Simplify your releases, catch risks earlier, and avoid testing as you fly with Sift’s rule making capabilities.

Sift’s “Rules” feature makes it easy to automate data review checks for each subsystem of your machine, making software releases painless, efficient, and straightforward. With an integrated rules approach to development and test, you can release with peace of mind, knowing that all performance has been tracked and measured.

Get a demo
  1. Implement this practice during the R&D phase, while building out each subsystem of your machine.
  2. Collect a list of the conditions you typically review.
  3. Open Sift.
  4. Go to the rules tab to add a new rule for each condition.
  5. As you integrate your system, this set of rules will run along with the collection of rules created by other subsystems. This coordinated approach allows each hardware component to be correctly evaluated during vehicle integration and test campaigns.
  6. For a complete list of instructions and technical docs, have a look here.

Integrating Sift’s Rules for predictable releases

Sift is a telemetry stack that offers transformative data review tools for machine creators to innovate and scale at speed. Built to maximize your time and reduce risk, Sift’s Rules feature simplifies releases and makes them almost painless.

By implementing a set of rules early on in your R&D process, you’ll capture every detail and nuance of your system — making your final test and integration campaign predictable and successful.

How does it work?

Creating these rules for your system takes very little time when considering the big picture, and pays dividends throughout the hardware development lifecycle. In fact, you only need to create a set of rules once in order for them to work effectively throughout your entire system. Some configs and thresholds may require changes as you move through phases, but with Sift those kinds of alterations are easy to make. It all lives under the “Rules” tab, where you can add and change things quickly and easily.

Observing and recording how your hardware performs against your rules will give your team granular understanding of your components' performance. Plus, you won’t have to manually review data for every release -- if your changes pass your configured rules, you can be confident that your updates will perform as expected. With automated data review, you can speed up your release tempo, and drastically reduce the possibility of being forced back to square one right before launch. And when it’s finally time to operate your hardware, you’ll have a more complete and detailed set of rules, avoiding “test as you fly” exceptions and saving yourself the headache of creating a new set of thresholds and limits for your vehicle after the fact.

This is how Sift changes the way you think about the release process, taking what was once a dreaded chore and turning it into a painless, risk-finding operation. Instead of surfacing risks late in the game, you can discover them earlier in your process — making them cheaper and easier to troubleshoot. With automated reviews that alert your team when something needs your attention, Sift can help you solve problems as early as the design phase.

This integrated approach gives your team more bandwidth to focus on their core engineering challenges, while increasing collaboration and reducing frustration. Your rules will run along with those created by other subsystems, thus promoting engineers' autonomy without friction. If you have questions when developing your rules, our customer success team customer success team can help you determine ever-present rules that won’t become stale, so that your people can implement better throughout the entire engineering workflow.

Stay on schedule for your mission and make releases confidently with a telemetry stack that’s built to give you continuous and accurate feedback.

Commonly asked questions

Won’t it be more work to create rules?

You’ll automatically recoup the time it takes to add rules into your system during your run for record or final test and integration campaign. Rules only need to be created once to work throughout the system or engineering workflow.

How do I keep my rules from going stale?

Our customer success team can help you determine how to identify ever-present rules that will stand up throughout the engineering workflow. While the configs or thresholds may need to be altered as you move through phases — such as engineering to production — Sift makes it easier to alter and update your rules as needed.

Can’t we just add these rules when everything is done and we’re in production?

Waiting until everything is finished to add your rules will result in the following missed opportunities:

- Your rules may not capture all of the nuance of your system, since the person who designed it may not work at your company anymore.

   - People will implement better and more detailed instrumentation in bit sized sub-systems rather than instrumenting the entire vehicle after the fact.

       - You can get to production a lot faster if you don’t have to manually review data every release.

Need more?