The GPower value
You are naturally the masters of your own domain, whether that domain be building wind turbines, producing pumps, or designing the most efficient fuel cells.
Ensure your testing success
One of the phases your project moves through is testing. While you know everything about your domain, you probably only do testing occasionally. We do testing all the time, year round. Having GPower by your side when you plan for and execute the test phase will ensure your success.
Build a simulator
At the beginning of your product development cycle you identify activities such as education of commissioning crews, design and verification of the control strategy, and early customer feedback. Kinds of tasks that you need your finished product to execute. In such cases you can simulate your product. You know your product, we are experts at building simulators.
Scale from prototype to production
Your prototype machine with an overabundance of sensors, manual switches, and expensive instruments is ready to be turned into a finished product. We are experts in IO and the computers that operate it, and so can build you a control system for your prototype that can be shrunk in cost as production volume increases.
Manage your production: lower cost and increased quality
A common situation: The test development process has become impractical and dicey. The small team has grown big, the “two variants” have multiplied many times. Copies of copies of test code, hand tuned configuration files, test stations updated with USB-sticks, re-testing and widening of validation limits become solutions to dropping yields. We feel your pain, and have become experts in test development, variant management, deployment strategies, reporting, process control, and test maintenance. Our experience is your value.
GPower might be the most valuable asset you acquire for your project.
GPower project trademarks
Project plans and estimates are typically quite optimistic. We humans tend to focus on things we know and ignore things we don't know, and we aren't comfortable envisioning anything outside the sunshine scenario.
We at GPower can't foresee everything either of course, but we like "realistic" much better than "optimistic" in our project plans.
Implementation of a typical application involves hardware selection (sensors, cables, acquisition devices, computers, network components, and HMI) and then build of custom software to make all that hardware solve the project requirements.
We have identified several project elements often overlooked or ignored in estimates. Considering these up front instead of banging into them when you least need to provides a much truer project estimate. These are trademarks of a GPower project:
Guaranteeing proper performance and timing
Choice of hardware platform, process modularization, decoupling and parallelization - in short the system architecture - are the most defining factors of final application performance. We have the broad experience necessary to do this properly, for instance integrating deterministic solutions where necessary.
Implementing synchronization and stuff...
Synchronization by wired electrical signals is most common, but sometimes you need networked IEEE-1588 or even wireless GPS synchronization for instance. Synchronization is just one technology feature that might be surprisingly complex to implement. Others to consider could be logging, runtime parameter accessibility, storage management, file formats, power-up state, failure modes etc.
Creating all the interfaces
Your new application needs to connect to existing hardware and software systems. Are all necessary interfaces created? Are the protocols even defined?
Separating the controller from its UI
Or perhaps we should call it MVC (Model-View-Controller). Names and implementation details vary, but the essence is that we aim at separating "the executing part" from "the ways we can view or manipulate it". One case of what we don't want is test validation inside a TestStand operator interface for instance. Unfortunately that was not a random example.
Implementing auxiliary features
There is sometimes a big gap between "the finished system" and "the operational system". We must consider localization, user management, help and wizard features, package management, deployment, versioning, variant management, and adaptive user interfaces to name a few elements.
Ensuring your ownership
GPower is in the business of delivering value to you. We want you to return to us for more business because you want to, not because you have to. This means we are focused on your ability to take complete ownership of the finished system without you being tied to external consultants for all eternity. Please help us help you by allowing time for making the proper installers, the necessary documentation, and by making you a product of sufficient quality, such that you are able to maintain this system yourself. Even if you decide to call on GPower to make v2.0, sufficient quality of v1.0 will make v2.0 better and less expensive.
"Our local supplier is half your price". No, he really isn't, he will just only deliver half of what you need...