A designer creates a CAD model.

An engineer defines dimensions and tolerances.

The file is sent to a manufacturer.

Several days or weeks later, that digital model becomes a physical aluminum, engineering-plastic, or composite component.

The transition may look simple:

CAD → CNC → Part

In reality, there are several important engineering stages between those steps.

Understanding this workflow can help developers, product designers, hardware startups, and mechanical engineers communicate more effectively with manufacturing suppliers.

1. It Starts With the CAD Model

Computer-Aided Design, or CAD, provides the geometric definition of a component.

A CAD model may contain information about:

• Overall geometry

• Holes

• Pockets

• Curves

• Surfaces

• Threads

• Interfaces

• Assembly relationships

However, geometry alone does not always provide enough information to manufacture the component correctly.

A manufacturer may also need:

• Material specification

• Tolerances

• Surface requirements

• Thread specifications

• Quantity

• Heat treatment

• Surface finishing

• Inspection requirements

This is why a 3D model is often accompanied by a 2D engineering drawing.

2. STEP, IGES, STL, DXF and DWG Are Not the Same Thing

Different file formats serve different manufacturing purposes.

STEP

STEP files are widely used for transferring solid CAD models between engineering systems.

Typical extension:

.step
.stp

They are often suitable for CNC machining because they preserve accurate geometric surfaces and solid-model information.

IGES

Typical extension:

.iges
.igs

IGES is another neutral CAD exchange format.

It is commonly used for exchanging curves and surfaces between different CAD systems.

STL

Typical extension:

.stl

STL represents a model as a triangular mesh.

It is extremely common in 3D printing.

For precision CNC machining, however, manufacturers frequently prefer formats such as STEP because a solid CAD model generally preserves engineering geometry more cleanly than a tessellated mesh.

DXF

Typical extension:

.dxf

DXF is commonly used for 2D geometry.

Applications include:

• Laser cutting

• Waterjet cutting

• Sheet processing

• CNC routing

• Profile machining

DWG

DWG is another common CAD drawing format, particularly for 2D engineering documentation.

The correct format depends on the manufacturing process.

3. The RFQ Package

Once the design is ready, the customer sends an RFQ package.

RFQ means:

Request for Quotation

A useful manufacturing RFQ usually contains more than a CAD file.

For example:

3D Model: STEP
Drawing: PDF
Material: 6061-T6 Aluminum
Quantity: 500 pcs
Finish: Black Anodizing
Tolerance: ±0.05 mm where specified
Inspection: Critical dimensions report

The better the RFQ information, the easier it is for the manufacturer to evaluate the project accurately.

4. Design Review Comes Before Machining

Manufacturing does not normally begin immediately after receiving the CAD file.

An engineering review comes first.

The manufacturer may check:

• Can the geometry be machined?

• Are the tolerances realistic?

• Can available tooling reach all features?

• Are there extremely deep pockets?

• Are internal corners too sharp?

• Are wall thicknesses sufficient?

• Will the part deform during machining?

• Does the surface finish affect dimensions?

• Is a custom fixture required?

This process is often called:

DFM — Design for Manufacturability

The purpose is not necessarily to redesign the product.

The purpose is to identify manufacturing risks before production starts.

5. Geometry Does Not Equal Manufacturing Intent

Consider a simple hole.

A CAD model may show:

Ø10 mm

But the manufacturer may still need to know:

• Is it a clearance hole?

• Is it reamed?

• Is it threaded?

• What tolerance is required?

• What surface quality is required?

• Is its position critical?

The CAD geometry describes what the part looks like.

The engineering drawing often explains how accurately certain features need to be produced.

That difference is important.

6. Process Planning

After the design review, manufacturing engineers determine how the part should be made.

This may include decisions about:

• Raw material size

• Machine type

• Number of machining operations

• Fixture strategy

• Tool selection

• Workholding

• Inspection stages

• Finishing sequence

For a CNC-machined component, the process could look like:

Raw Material
     ↓
Operation 1
     ↓
Reposition / Fixture
     ↓
Operation 2
     ↓
Deburring
     ↓
Surface Finishing
     ↓
Inspection

Complex components may require several setups.

7. CAM Converts Geometry Into Toolpaths

CAD defines the geometry.

CAM defines how the cutting tool moves.

CAM stands for:

Computer-Aided Manufacturing

The engineer imports the CAD geometry into CAM software and generates machining operations.

Typical operations include:

• Facing

• Pocketing

• Contouring

• Drilling

• Boring

• Thread milling

• 3D surface machining

The CAM system creates toolpaths based on factors such as:

Tool diameter
Spindle speed
Feed rate
Depth of cut
Material
Machine capability

The output is then post-processed into machine-readable CNC instructions.

8. Toolpath Simulation

Before actual cutting begins, the machining program can be simulated.

Simulation helps identify potential problems such as:

• Tool collisions

• Fixture collisions

• Excessive tool engagement

• Unmachined areas

• Incorrect cutting sequence

• Tool reach limitations

Finding an error virtually is much cheaper than finding it after damaging material, tooling, or a machine.

9. CNC Machining

Once the process is verified, production begins.

The workpiece is loaded into the machine.

The CNC machine follows the programmed toolpath.

But machining is not simply a fully automatic process.

Operators and manufacturing engineers still monitor:

• Tool wear

• Workpiece position

• Coolant

• Cutting stability

• Dimensions

• Surface finish

• Fixture condition

The digital workflow controls the process, while physical production still requires experienced manufacturing decisions.

10. Inspection Brings the Process Back Into the Digital World

After machining, the part must be checked against the engineering requirements.

Inspection tools may include:

• Calipers

• Micrometers

• Height gauges

• Gauges

• Optical measurement systems

• Coordinate Measuring Machines

A Coordinate Measuring Machine, or CMM, can compare physical coordinates on the manufactured component against the intended geometry.

The manufacturing loop therefore becomes:

Digital Design
      ↓
Manufacturing
      ↓
Physical Part
      ↓
Measurement
      ↓
Digital Inspection Data

This feedback loop is one of the foundations of modern precision manufacturing.

11. Why Tolerances Matter

Suppose a design contains twenty dimensions.

Not every dimension necessarily needs the same precision.

A tolerance of:

±0.01 mm

may require more careful machining and inspection than:

±0.20 mm

Applying extremely tight tolerances everywhere can increase:

• Machining time

• Inspection time

• Scrap risk

• Tooling requirements

• Overall cost

Good engineering drawings identify which dimensions are genuinely critical.

12. Surface Finishing Happens After Machining

Manufacturing often continues after CNC machining.

Depending on the material, additional processes may include:

• Anodizing

• Powder coating

• Painting

• Polishing

• Sandblasting

• Plating

• Heat treatment

The order matters.

Some finishing processes can affect dimensions or surface characteristics.

Therefore the manufacturing plan must consider the complete production chain rather than CNC machining alone.

13. Composite Manufacturing Uses a Different Digital-to-Physical Workflow

Not every component is produced through subtractive machining.

Carbon fiber composite manufacturing may involve:

CAD Geometry
      ↓
Mold Design
      ↓
Tooling
      ↓
Material Cutting
      ↓
Carbon Fiber Layup
      ↓
Vacuum / Pressure
      ↓
Curing
      ↓
Trimming / CNC Finishing
      ↓
Inspection

This illustrates an important point:

The digital design remains central, but the physical manufacturing route depends heavily on the material and component.

A carbon fiber component may require mold development, laminate planning, curing, trimming, and secondary machining.

14. Hybrid Manufacturing Workflows

Many modern components require several different manufacturing technologies.

For example:

Composite Molding
      +
CNC Trimming
      +
Metal Inserts
      +
Surface Finishing
      +
Assembly

This is why manufacturing suppliers are increasingly expected to understand workflows rather than isolated machines.

A customer does not necessarily care whether a component requires three machines or seven processes.

They care whether the final component meets the drawing.

15. Why Manufacturing Feedback Matters Early

A common mistake in hardware development is waiting until the design is finished before speaking to a manufacturer.

Early engineering feedback can sometimes identify:

• Expensive geometry

• Difficult tolerances

• Problematic material choices

• Unnecessary machining

• Tool-access problems

• Mold-release problems

• Assembly risks

Changing a CAD feature before tooling starts is usually easier than correcting it after production has begun.

16. What Manufacturers Need From Customers

A good manufacturing request should ideally answer six questions.

What?

Provide the CAD model and drawing.

What material?

Specify the required material grade.

How many?

Provide prototype and expected production quantities.

How accurate?

Define tolerances and critical dimensions.

What finish?

Specify surface treatment or appearance requirements.

How should it be inspected?

Identify critical inspection requirements.

These details help turn a CAD file into a manufacturable production plan.

17. Digital Manufacturing Is Really a Communication System

It is tempting to think about manufacturing as:

Upload File → Receive Part

But precision manufacturing is better understood as a communication system between:

• Designer

• CAD software

• Manufacturing engineer

• CAM software

• Machine

• Operator

• Quality engineer

• Measurement system

Each stage translates information into another form.

A manufacturing company such as CarbonFactorys works with drawing-based custom composite and machining projects where digital engineering data provides the starting point for manufacturing planning.

The quality of that information directly affects the efficiency of the downstream process.

18. The Future Is More Connected

Digital manufacturing workflows are becoming increasingly connected.

CAD systems can feed directly into:

• CAM

• Manufacturing planning

• Quality systems

• Production tracking

• Inspection databases

Eventually, a product can develop a complete digital history:

CAD Revision
     ↓
Material Batch
     ↓
Manufacturing Program
     ↓
Production Record
     ↓
Inspection Report
     ↓
Finished Component

This traceability becomes particularly valuable in engineering applications where repeatability matters.

Final Thoughts

The journey from CAD to CNC is not simply a file conversion process.

It is a chain of engineering decisions.

CAD defines geometry.

Drawings define requirements.

Manufacturing engineers define the process.

CAM defines machine movement.

CNC equipment creates the physical part.

Inspection verifies whether the result matches the original engineering intent.

Understanding this workflow helps designers create more manufacturable products and communicate more effectively with suppliers.

The most successful manufacturing projects begin long before the machine starts cutting.

They begin with good engineering information.

But behind that single tap is a small system connecting physical hardware, NFC data, web infrastructure, databases, and user experience design.

For developers, the interesting part is not only the NFC chip itself. It is how a static physical object can act as an entry point to a dynamic digital identity.

This article breaks down the architecture behind a modern NFC business card system.

1. The Physical Layer: NFC Tag and Antenna

A typical NFC business card contains two important components:

• An NFC integrated circuit

• An NFC antenna

In most business-card applications, the NFC tag is passive.

That means it does not require a battery.

When an NFC-enabled smartphone approaches the card, the phone generates an electromagnetic field that provides enough energy for the tag to respond.

The amount of information stored on the tag is usually quite small.

For example, the NFC tag may only contain:

https://example.com/n/7Df92K

That URL becomes the bridge between the physical card and the digital platform.

2. NDEF: The Data Format Behind the Tap

One of the most important concepts in NFC development is NDEF.

NDEF stands for:

NFC Data Exchange Format

It is a standardized format used to organize data stored on NFC tags.

An NDEF message may contain one or multiple records.

Common record types include:

• URI records

• Text records

• MIME records

• Application-specific records

For an NFC business card, a URI record is usually enough.

Conceptually, the flow looks like this:

Physical NFC Card
        ↓
NDEF Message
        ↓
URI Record
        ↓
https://example.com/n/7Df92K

Once the phone recognizes the URI, the operating system can offer the user the option to open it.

At that point, NFC has completed its job.

Everything after that happens on the web.

3. Why the NFC Tag Should Not Store the Entire Profile

It might seem logical to store all contact information directly inside the NFC tag.

For example:

Name: Alex Chen
Company: Example Inc.
Phone: +1...
Email: alex@example.com
LinkedIn: ...

Technically, some contact information can be stored directly.

However, a dynamic URL-based architecture is usually much more flexible.

Instead of storing the profile itself, the NFC card stores an identifier or redirect URL.

For example:

https://example.com/n/7Df92K

The server then determines which profile belongs to that identifier.

This creates a major advantage:

The physical card does not need to change when the person's information changes.

The user can update:

• Phone number

• Job title

• Company

• Website

• Social profiles

• Portfolio

• Contact links

without rewriting or replacing the NFC card.

4. A Simple NFC Business Card Architecture

A basic architecture might look like this:

NFC Card
   ↓
NDEF URI
   ↓
Redirect Endpoint
   ↓
Profile Database
   ↓
Digital Business Card
   ↓
Contact / Social / Website Actions

Each layer has a specific responsibility.

NFC Card

Stores the URL or unique identifier.

Redirect Endpoint

Receives the request and resolves the card ID.

Example:

GET /n/7Df92K

Database

Maps that identifier to a specific user or organization.

Example:

7Df92K → user_1842

Profile Page

Displays the current information associated with that user.

This separation makes the system much easier to maintain.

5. Example Data Model

A very simple database structure could look like this:

users
-----
id
name
company
title
phone
email
website
linkedin
avatar

cards
-----
id
card_uid
user_id
status
created_at

redirects
---------
card_uid
destination
last_updated

A request such as:

/n/7Df92K

can be resolved by:

1. Finding the card.

2. Confirming that the card is active.

3. Finding the associated user.

4. Loading the profile.

5. Rendering the digital business card.

This architecture also makes it possible to support multiple cards for one person.

6. Dynamic Redirects Make the System More Powerful

One of the most useful features of a smart NFC system is the redirect layer.

Instead of writing:

https://linkedin.com/in/example-user

directly to the NFC chip, write:

https://example.com/n/7Df92K

The backend can then redirect the user to LinkedIn.

Later, the owner may decide to redirect the same card to:

https://example.com/alex

or:

https://company.com/team/alex

The physical NFC card remains unchanged.

This makes the card programmable from the server side.

7. Adding Analytics

Once the NFC interaction passes through your own endpoint, analytics become possible.

For example, the system could record:

card_id
timestamp
device_type
referrer
country
destination

This allows businesses to answer questions such as:

• How many times was the card tapped?

• Which cards are used most frequently?

• Which events generated the most interactions?

• Which team members receive the most profile visits?

However, analytics should be implemented with appropriate privacy controls and in compliance with applicable privacy requirements.

Not every NFC interaction needs to become an invasive tracking system.

8. Card Activation

For larger deployments, NFC cards can also support an activation workflow.

A manufacturer or platform provider may produce hundreds or thousands of cards before knowing which employee will receive each one.

The card could initially point to:

https://example.com/activate/7Df92K

The user signs in, claims the card, and associates it with their account.

After activation:

7Df92K → user_1842

The same physical card now becomes part of that person's digital identity.

9. Enterprise Use Cases

Once NFC business cards are connected to a backend platform, the use case extends beyond individual networking.

Organizations can build:

Team Management

Administrators can create and manage employee profiles.

Standardized Branding

Every employee profile can use the same company layout.

CRM Integration

A tap can lead to a contact form connected to a CRM.

Employee Offboarding

If an employee leaves the company, the card can be disabled or reassigned.

Event Campaigns

Different cards can be linked to different exhibitions, campaigns, or landing pages.

API Integration

Organizations can synchronize employee information with internal systems.

At this point, the NFC card becomes more than a digital replacement for paper.

It becomes a physical interface to a business information system.

10. NFC vs QR Code Architecture

From a backend perspective, NFC and QR codes can use almost exactly the same infrastructure.

Both can point to:

https://example.com/n/7Df92K

The primary difference is how the user reaches the URL.

QR Code

Camera
  ↓
QR Detection
  ↓
URL
  ↓
Web Application

NFC

NFC Reader
  ↓
NDEF URI
  ↓
URL
  ↓
Web Application

Because both methods ultimately reach the same server endpoint, many smart business cards include both technologies.

NFC provides tap interaction.

QR provides a visual fallback.

11. Security Considerations

An NFC business card should not be treated as an authentication device by default.

If the card only contains a public URL, anyone capable of reading or copying that URL may be able to access the same destination.

Developers should therefore consider several principles.

Use HTTPS

All profile and management pages should use encrypted HTTPS connections.

Keep Sensitive Data Off the Tag

Do not store confidential business information directly inside a publicly readable NFC record.

Secure the Administration Panel

Updating the destination of an NFC card should require proper authentication.

Validate Important Actions Server-Side

Do not assume that an NFC tap proves the identity of the person holding the card.

Support Card Revocation

If a card is lost, organizations should be able to deactivate or reassign it.

12. The Physical Material Also Matters

Software developers often see the NFC tag as an isolated component.

Real-world product development is more complicated.

The NFC antenna exists inside a physical product, and the surrounding material can affect antenna behavior and reading performance.

That matters when NFC is integrated into premium materials such as metal or carbon fiber.

For example, carbon fiber NFC business cards combine a physical composite structure with an embedded NFC system.

This means the product needs to be designed as both:

• A physical object

• A digital interface

The appearance, material structure, antenna placement, and user interaction all need to work together.

13. Physical Product + Digital Identity

This is where smart cards become interesting from a product-development perspective.

The complete system is not simply:

NFC Chip

It is:

Physical Material
      +
NFC Hardware
      +
NDEF Data
      +
Web Application
      +
Digital Identity

Companies such as Mastermate are exploring this combination by integrating NFC functionality into premium carbon fiber card products.

The important engineering principle is broader than business cards:

A physical product can become a persistent interface to software.

14. Final Architecture

A scalable NFC business card platform might eventually look like this:

Physical NFC Card
        ↓
NDEF URI
        ↓
Short URL / Card ID
        ↓
API Gateway
        ↓
Card Resolution Service
        ↓
User Database
        ↓
Digital Profile
        ↓
Analytics / CRM / Contact Actions

The physical card remains simple.

The backend provides flexibility.

That separation is what makes the system scalable.

Final Thoughts

NFC business cards demonstrate a useful pattern in connected product design.

Keep the physical layer simple.

Store a stable identifier.

Move frequently changing information into software.

A tiny NFC tag can then provide access to a continuously evolving digital identity platform.

From a developer's perspective, the NFC chip is only the beginning.

The real opportunities exist in what happens after the tap.

An NFC pet memorial card provides a bridge between a physical keepsake and a digital remembrance page. Instead of storing an entire collection of media on the card itself, the NFC chip usually contains a small piece of structured data—most commonly a secure web address. Tapping the card with a compatible smartphone opens a page where visitors can view photographs, videos, dates, stories and messages.

Although the interaction feels simple, building a reliable NFC memorial experience requires thoughtful decisions about data structure, mobile design, privacy and long-term maintenance.

What an NFC memorial card actually stores

Most NFC memorial cards use a passive NFC tag. A passive tag does not require a battery. It receives enough energy from the smartphone’s NFC field to transmit the small amount of data stored in its memory.

That data is commonly written using the NFC Data Exchange Format, or NDEF. An NDEF record can contain several types of information, including:

A web address A short text record Contact information An application link A unique identifier used by a web service

For a digital memorial, a URL is generally the most practical option. The card might contain an address such as:

https://petmemoshop.com/memorial/companion-1ae0d3

The photos and videos are not stored inside the NFC chip. They remain on the website or its connected storage service. This separation is important because NFC tags have limited memory, while an online memorial page can be updated over time without replacing the physical card.

The interaction flow

A typical NFC memorial experience follows a short sequence:

A person holds an NFC-compatible phone near the card. The phone reads the NDEF record stored on the chip. The operating system recognizes the record as a web address. The browser opens the linked memorial page. The visitor sees the pet’s story, photographs, videos and remembrance messages.

This flow should work without requiring a dedicated mobile application. Removing the application-installation step makes the memorial easier to access for relatives and friends who may only visit the page once.

A printed QR code can also be added as a fallback. NFC offers a more natural tap interaction, while the QR code helps users whose phones do not support NFC or have the feature disabled.

Designing the digital memorial page

The web page is the central part of the experience. A decorative card may create the first impression, but the page determines whether the memories remain readable, organized and emotionally appropriate.

A well-designed memorial page might include:

The pet’s name and portrait Birth and remembrance dates A short life story A photo gallery Selected video memories Messages from family members A favorite quote or remembrance text Optional links to charitable causes

Mobile performance is especially important because most visitors arrive directly from a phone. Images should be compressed carefully, videos should load only when requested, and important content should appear before decorative elements.

The design should also avoid overwhelming the visitor. A memorial page benefits from generous spacing, readable typography and restrained animation. Technology should make the memory easier to reach, not distract from it.

Separating the physical identifier from the page address

Writing a permanent public page address directly to the NFC tag is simple, but it can create a maintenance problem. If the website structure changes later, the encoded address may stop working.

A more resilient architecture uses a stable identifier:

https://example.com/m/8f4k2p

The server maps that identifier to the current memorial page. If the page is moved or rebuilt, the mapping can be updated without rewriting or replacing the NFC card.

This redirect layer also makes it possible to migrate content to new infrastructure while keeping existing cards functional. However, the redirect service itself becomes critical infrastructure and should be backed up and monitored.

Editable and locked NFC records

During setup, the NFC record usually remains writable so the correct destination can be tested. After verification, the tag may be locked to prevent accidental or unauthorized rewriting.

Locking is typically permanent, so it should only happen after checking:

The full destination URL HTTPS availability Mobile compatibility Redirect behavior Ownership of the linked domain The recovery plan if the page location changes

For projects that need future flexibility, keeping the tag pointed to a stable redirect address is safer than repeatedly changing the NFC record.

Privacy and access control

A pet memorial page may contain family photographs, personal messages or information about the pet owner. Public visibility should therefore be a deliberate choice rather than a default assumption.

Possible access models include:

Public memorial

Anyone with the link can view the page. This is appropriate when the owner wants to share the pet’s story openly.

Unlisted memorial

The page is not intended to appear in site navigation or search results, but anyone with the NFC card or direct link can access it. This improves discretion but should not be treated as strong security.

Password-protected memorial

Visitors must enter a password before viewing the content. This provides more control, although it adds friction to the tapping experience.

Sensitive personal details—such as home addresses, private phone numbers or unnecessary location information—should not be published. Owners should also understand who can edit the page and how they can request its deletion or export.

Material and antenna considerations

NFC performance depends on the relationship between the chip, antenna, surrounding material and smartphone.

Some materials can interfere with the antenna’s electromagnetic field. Metal-backed keepsakes generally require an NFC tag designed for use on metal or an appropriate isolation layer. Carbon-fiber constructions can also affect radio performance, so antenna placement and real-device testing are important when NFC is integrated into a carbon-fiber memorial card.

A finished design should be tested with multiple iPhone and Android models. The position where users should tap can be indicated subtly on the card to reduce failed scans.

Planning for long-term preservation

A physical memorial may be kept for decades. The biggest technical risk is therefore not necessarily the NFC chip—it is the continued availability of the domain, hosting account and digital files.

A durable system should include:

Regular database and media backups Domain-renewal protection Exportable photographs and text Stable URL management A documented recovery procedure Clear ownership and account-transfer options Monitoring for broken links and unavailable media

Families should ideally retain copies of the original photographs and videos. An online memorial is a meaningful access point, but it should not be the only copy of irreplaceable files.

A human interface supported by simple technology

The strongest NFC memorial experiences do not feel like demonstrations of technology. The chip performs one small task: it helps someone reach a memory with a tap.

Projects such as the NFC pet memorial cards developed by PetMemoShop illustrate how a physical card can serve as a lasting entry point to photographs, stories and personal tributes. The useful part is not NFC alone, but the combination of a durable object, a stable digital identity and a thoughtfully maintained web page.

When these elements are designed together, an NFC memorial card becomes more than a link. It becomes a quiet interface between something a family can hold and the memories they want to preserve.