A test is only as useful as the results it produces. Comprehensive National Instruments’ TestStand sequences may generate reports that are hundreds of pages long. This blog examines the default NI TestStand reports and demonstrate several simple steps G Systems has perfected to convert your encyclopedic report into something concise and easy-to-read.
Aerospace and defense test is a complicated business. A lot goes into ensuring helicopters stay in the air, spacecraft stay pressurized, and passenger airplanes land safely every time. It’s a business full of complex elements—custom test fixtures, multiple technical compliance guidelines, and a ton of customer requirements. After more than two decades of designing hundreds of aerospace and defense test systems at G Systems, we have learned a thing or two about what it takes to design a successful mission-critical system… and seen some key design mistakes that nearly guarantee failure when designing aerospace and defense applications.
As the year comes to a close and we reflect on 2016, we are proud of the collaboration and hard work we’ve put in to ensuring our customers’ success and continuing G Systems tradition of excellence. We are ending 2016 on track for another year of strong financial results, our customer and partner relationships continue to thrive, and we’ve seen significant industry recognition – both locally and nationally – for our leadership, record-breaking growth, technical expertise, and strategic partnerships.
After reading through Ralph Hutson’s blog about whether to make or buy your next test system, you may have decided you want to hire G Systems to design and build your test system. To take that step, you need to provide the test requirements; however, you may not be familiar with how to write requirements. It's likely that you typically define the test requirements in-house as you design your test system. So, what should you consider when writing your requirements?