How to post a good question

The same question, asked two different ways, gets two completely different answers. This page is the short version of what works.

The community is full of engineers willing to help — but they help fastest when they don't have to guess what you're actually asking.

Before you post — search first

Use the search bar at the top of every page. There's a real chance the problem you hit was hit by someone else last month. If you find a related thread that doesn't quite cover your case, comment on it rather than opening a new one. Cross-pollination beats duplication.

A good question, in 5 parts

A question that gets answered usually has these 5 parts:

1. A specific title — describes the problem in one line. Not *"Help with

Smart 3D" but "Smart 3D V14 bulkload fails with ColumnSize too small on import of HS_S3DAssy.xls"*.

1. What you're trying to do — the goal. Two sentences.
2. What you tried — what you actually did, in enough detail that someone

else could repeat it.

1. What went wrong — the exact error message, copy-pasted verbatim

(not paraphrased), in a code block. Screenshots welcome but the text is what makes it searchable.

1. Your setup — version of the software, OS, install type (project /

workgroup / network), anything else specific to your environment.

If those 5 are in the post, you're 90% of the way there.

Pick the right category

Every question has three category levels, all required:

• L1 (Tool) — Smart 3D, SmartPlant P&ID, CADWorx, Plant 3D, etc.
• L2 (Category) — Modelling, Administration, Catalog & Reference Data,

Customization, Licensing, etc.

• L3 (Sub-category) — Piping, Equipment, Structure, etc.

If you're not sure where it belongs, pick the closest match. "Other" is a real option at any level — use it when nothing else fits, not as a way to skip thinking. Moderators may reclassify mis-filed posts.

Use the OLD product names

Engineers search Google with the OLD names: "Smart 3D bulkload error", "SmartPlant P&ID OPC". So this forum uses those names too. Octave renamed everything in March 2026 (Smart 3D → Forte 3D, SmartPlant P&ID → Facets P&ID, CADWorx → 3DWorx etc.), but writing "How do I fix my Forte 3D bulkload?" won't get found by anyone Googling the problem.

Use: Smart 3D, SmartPlant P&ID (SPPID), CADWorx, Smart Electrical, Smart Instrumentation, Smart Licensing. Don't use as the primary: Forte 3D, Facets P&ID, 3DWorx, etc.

The first mention of a product in a long question can include the rebrand parenthetically — "Smart 3D (now branded Octave Forte 3D) on V14…" — once, not six times.

Show code, paths, registry keys — verbatim

Engineers want copy-pasteable fragments, not paraphrases.

```` This block is what the editor's "Insert code" button produces:

Dim oPipe As IJDPipingNetSystem Set oPipe = oTrans.CreateNew("PipeRun", oResMgr)

````

Inline, single backticks: \`IMathServices.GetOrientedRangeBox\`.

For SQL, registry paths, file paths, XML config — same treatment. Don't re-type from memory; paste the actual thing.

Screenshots — yes, but text first

Screenshots help, especially for UI dialogs and 3D errors. Upload them via the image icon in the editor toolbar. But also paste the error message text — search engines (and the search bar at the top of this page) can't read images.

One problem per question

If you have three problems, post three questions. A 4-paragraph mega-question covering "five things that aren't working in my Smart 3D project" is unanswerable — no one can give you a complete answer, and partial answers get buried in a thread that nobody can navigate.

What to do AFTER you post

• Don't bump. Don't reply "Anyone?" after 6 hours. The community is

global; someone in a different timezone might still be reading.

• Accept the answer that helped you by clicking the ✓ next to it. That's

the most important signal you can leave behind — it tells future readers "this one worked", and it rewards the answerer's karma.

• Edit your own question if you find more information later (a fix, a

workaround, the root cause). Keep the thread useful for the next person.

• Don't delete a question that already has answers. Even if you've moved

on, the thread might be exactly what someone else needs in 6 months.

What we don't allow

For the full list, read the Code of Conduct. The short version: no piracy, no vendor trash-talk, no spam, no leaking your customer's confidential data, be civil.

If something here is unclear, ask in the General Engineering Workflows category and the moderators will improve this page.

Last updated: 2026-05-14