CLIENTS & PARTNERS

Client work and technology relationships, in context

Choosing a delivery partner means understanding the work behind the name. Explore nCircle Tech clients and partners, and the technical collaborations that support engineering and design workflows.

DIFFERENT RELATIONSHIPS, DIFFERENT EVIDENCE

A client project, an integration and a partnership aren't the same thing

DIFFERENT RELATIONSHIPS, DIFFERENT EVIDENCE
Why it matters
01

A client project, a software integration and a formal partner designation are not the same thing.

02

This page connects relationship context with relevant work so you can evaluate nCircle Tech customer projects without relying on a logo alone.

ENGINEERING SOFTWARE COLLABORATION

Work with engineering software organizations

The examples concern activities such as product features, software integrations and development-team collaboration.
AEC TECHNOLOGY INTEGRATION EXPERIENCE

Two detailed project accounts

HDCC: Connecting Construction and Financial Information

HDCC: Connecting Construction and Financial Information

The ACC–CMiC project describes connecting construction and financial information for Hawaiian Dredging Construction Company.

faciliCAD: Modernizing a Drawing-Linked Facility Platform

faciliCAD: Modernizing a Drawing-Linked Facility Platform

The faciliCAD story describes modernizing a drawing-linked facility-software platform.

Read those project accounts alongside the relationship information. The client context, delivered functionality and intended users help distinguish experience that directly matches your requirement from experience that is technically related.

A CAD BIM DEVELOPMENT PARTNER, SCOPED TO THE SPECIFICS

An integration example isn't a vendor endorsement

01

Engineering software ecosystems involve application interfaces, development toolkits and product-specific constraints.

An integration example can show how a technology was used within a particular project, but it does not automatically establish a formal vendor endorsement.

02

For a proposed engagement, discuss the exact application, version, license and operation involved.

Current partner credentials and implementation scope should be confirmed as part of that discussion.

BEYOND THE PROGRAMMING ENVIRONMENT

Evidence of understanding the engineering process

Look for evidence of understanding the engineering process, not only the programming environment.

Ask how requirements were clarified, how users reviewed outputs and how the team worked with the customer's existing systems.

The most relevant reference is one that helps answer a decision you need to make. That may concern an ongoing product team, a defined software feature or a workflow connecting several applications.

WHAT CAN AND CAN'T BE SHARED

Confidentiality and permission determine what's disclosed

01

Name your question

Tell us which aspect of delivery you want to understand and why it matters to your project.

Delivery aspect
Project relevance
02

Public examples

We can discuss available public examples and whether additional reference material can be shared.

Public examples
Additional material
03

Permission decides

Customer confidentiality and permission determine what can be disclosed.

Confidentiality
Customer permission
04

No private access

This page does not promise access to private customer systems, named contacts or unpublished project information.

Private systems
Named contacts
Unpublished work
RELATED PAGES

Where to go next

QUESTIONS YOU MAY HAVE

Frequently asked questions

No. Customer experience, past collaboration and formal partner status should be identified separately.

Evaluate the experience that matters to your team

Share your technical environment and the delivery questions you need answered. We can direct the conversation toward relevant public work and appropriate evidence.