1. Tell Us About the Problem
Describe the issue, concern, objective, or decision — with a specified technical requirement if you have one, or simply with the problem or goal.
Customer consultation
You may already have a preferred study method, model, software platform, or analytical approach — or you may simply want to explore the best way forward.
The method follows the problem — not the other way around.
GR will discuss the proposed approach, methods, models, tools, assumptions, and expected outputs with you before proceeding. Depending on your preference, we can keep you informed at the level of technical detail that is most useful to you throughout the engagement.
Tell us about a problem you are facing, a decision you need to make, a reliability or operational concern, a system limitation, an improvement you are considering, a risk or uncertainty you want to understand, or an outcome you would like to achieve.
Start with your problem, goal, concern, or decision. We will first understand your system, issue, desired outcome, constraints, available information, and any preferred methods or tools. Where appropriate, we can work within customer standards, platforms, and methodologies. We will then discuss whether GR can help and, if so, work with you to define or refine scope, data requirements, methods, assumptions, outputs, and next steps. Technical detail can be provided at the level most useful to your team.
Engagement process
Describe the issue, concern, objective, or decision — with a specified technical requirement if you have one, or simply with the problem or goal.
GR domain specialists may ask about the system or facility, operating environment, current problem, desired outcome, constraints, available information, preferred methods or tools, previous studies if relevant, timing or decision requirements, and the level of technical participation that is most useful to your team.
After an initial discussion, we will tell you whether we believe GR can add value. If additional specialist expertise is required, we will identify that as part of the discussion. GR works within its areas of expertise and may collaborate with qualified specialists where a problem requires additional disciplines.
If GR can help, we discuss scope, required data, models and analytical methods, assumptions, technical tools, deliverables, schedule, collaboration, and documentation — including customer-preferred approaches where appropriate. Technical detail can be provided at the level most useful to your team.
The method follows the problem — not the other way around.
Inquiry
An initial inquiry does not commit you to a study. Start with your problem, goal, concern, or decision. You may already have a preferred approach, or you may simply want to explore the best way forward.
Direct contact
Email or call us if you would rather discuss the issue directly.
Examples
These examples are starting points, not a menu you must choose from. If your issue is different, still tell us about it.
Expectations
Technical transparency
Once the problem and objectives are understood, GR will discuss the proposed approach, methods, models, tools, assumptions, limitations, and expected outputs with you before proceeding. Technical detail can be provided at the level most useful to your team throughout the engagement.