Who uses Arpelier, and for what?
Arpelier can support education, research, and technical communication whenever a fabrication sequence needs to be connected with the structure it creates. The examples below are possible workflows grounded in the current editor, step navigation, 3D and cross-section views, splits, capture, Gallery, and project-sharing features.
Last reviewed
Education, training, and knowledge transfer
These workflows can help close the gap between knowing the name of a process and understanding how it changes a structure.
Students learning process–structure relationships
- Who: students encountering semiconductor or microfabrication processes and learners preparing for related roles.
- Problem: unit-process diagrams can make it hard to see how separate steps accumulate into one device.
- Workflow: open the Simple MOSFET official example and other examples, move through their steps and time dots, and compare 3D structures with cross-sections.
- Outcome: connect deposition, patterning, removal, and material change with the geometry they produce.
Educators preparing teaching content
- Who: instructors preparing lectures, assignments, demonstrations, or semiconductor workforce training.
- Problem: repeatedly drawing process-dependent structures takes time and can separate the image from its fabrication sequence.
- Workflow: prepare a process flow, select useful stages and cross-sections, capture views, or arrange a short Gallery sequence.
- Outcome: present the structure together with the steps that formed it in one explanatory sequence.
Onboarding new researchers and engineers
- Who: research and engineering teams onboarding new colleagues or passing on process and device knowledge.
- Problem: documents and verbal explanations can omit the context behind a stack, mask choice, or important structural decision.
- Workflow: organize the flow as a project, retain useful intermediate structures, and arrange explanatory scenes for review.
- Outcome: create a shared visual reference that new colleagues can question and experienced colleagues can explain.
Research, process integration, and structural review
Arpelier can help frame process order, stack relationships, and structural variables before quantitative validation begins.
Early process and structure exploration
- Who: researchers and engineers shaping an early device structure or process-integration concept.
- Problem: text and sketches alone may not reveal whether the intended stack, formation order, or alternative architecture is coherent.
- Workflow: arrange supported operations and parameters, materials, and masks, then revise the flow while inspecting each structural stage.
- Outcome: identify structural questions, missing steps, and alternatives before committing to a more detailed analysis workflow.
Process-integration order and mask-to-3D relationships
- Who: process and device researchers reviewing a sequence of layers and patterning operations.
- Problem: it can be difficult to explain how two-dimensional mask geometry and process order become a three-dimensional stack and cross-section.
- Workflow: follow mask-dependent steps, rotate the structure at relevant stages, and inspect cross-sections along different axes.
- Outcome: review which masks and steps form a particular layer, opening, line, or connection in the structural model.
Process splits and scoping variables before DOE
- Who: researchers and engineers defining which process conditions or experimental variants deserve comparison.
- Problem: before a DOE or detailed simulation, the structural variables and regions of interest may still be too broad.
- Workflow: create a baseline and splits, vary supported process parameters, and compare the resulting stages in 3D and cross-section.
- Outcome: organize the structural variables and comparison scope for later experiments or analysis. Arpelier does not run a statistical DOE or predict fabrication results.
Pre-TCAD problem framing and structural hypotheses
- Who: someone preparing detailed physical simulation, an experiment, or a review of a possible failure or degradation mechanism.
- Problem: the structure of interest, its process causes, and the hypothesis to test need to be clear before quantitative setup is worthwhile.
- Workflow: inspect regions and geometric differences in a simplified process–structure model, then carry selected questions into professional TCAD, experiments, and process validation.
- Outcome: enter the next stage with a clearer structural scope and a more communicable hypothesis. Arpelier does not diagnose failures or validate degradation mechanisms.
Technical explanation, documentation, and collaboration
These cases call for sharing not only a final structure but also the flow and intermediate views that explain how it was formed.
Papers, conference presentations, and research documents
- Who: researchers preparing a paper, conference presentation, poster, technical report, or research proposal.
- Problem: a final device image often hides the process sequence that created important layers and features.
- Workflow: model the relevant structural sequence, capture selected views, and use Gallery or presentation output as supporting material.
- Outcome: prepare visual material that explains where a structure arises in the process flow.
Cross-functional, remote, and asynchronous review
- Who: teams reviewing a process concept across disciplines, departments, or locations.
- Problem: exchanging static images can leave reviewers with different stages, viewpoints, and feedback references.
- Workflow: save the project with an appropriate access setting, add collaborators when editing is needed, or share a link or QR code to the same flow, 3D structure, and cross-sections.
- Outcome: participants can inspect the project independently and continue the discussion against a shared visual reference.
Design-intent records and non-confidential communication
- Who: teams recording structural decisions or explaining a non-confidential concept to partners, customers, or external research groups.
- Problem: a result image rarely preserves why a sequence or geometry was chosen, and each audience may require a new explanation.
- Workflow: organize the flow, selected stages, cross-sections, and explanatory scenes, then use access-appropriate links, captures, or Gallery material.
- Outcome: communicate structural intent and prepare supporting material for a blog, video, or seminar. Sensitive information should be reviewed before it is placed in a project.
Inventions, patents, and external technical review
In patent-related work, Arpelier can serve only as supporting visual material for explaining structure and formation order, not as a legal-analysis system.
Invention disclosures and inventor–patent counsel communication
- Who: inventors preparing a disclosure and patent professionals who need to understand the technical concept.
- Problem: prose and rough sketches can leave different interpretations of layer relationships and formation order.
- Workflow: build a simplified representation of the essential structure and process sequence, then review the 3D view and relevant cross-sections together.
- Outcome: use a common visual reference to discuss the structure, formation sequence, and views that may need formal patent drawings.
Technical comparisons for patents, prior art, and external evaluation
- Who: researchers and technical teams explaining published technologies or preparing material for a research program, technology transfer, or external technical review.
- Problem: different documents use different drawings and terminology, making structural and process distinctions hard to explain on a common basis.
- Workflow: within the information that can be shared, reconstruct each structure and formation sequence as separate projects or scenes and compare equivalent 3D stages and cross-sections.
- Outcome: create a shared visual aid for technical differences. Arpelier does not determine patentability, novelty, inventive step, infringement, claim language, or legal scope.