Establish master process flow templates before migration
Due to fundamental changes in process definitions between V7 and FactoryLogix, you must establish one or more new master process flow templates in FactoryLogix (also known as process templates or process definition templates) before migrating data from V7. A FactoryLogix process flow template is similar to a V7 master factory model, but it does not reference the physical resources in your factory such as lines and process points. During the migration, your newly-created process flow template will serve as the “target” when you migrate an existing V7 project based on a factory model to FactoryLogix.
| Note | ||||
|---|---|---|---|---|
| ||||
To learn how to create new process flow templates, see the topic Create a process, step, or operation template. |
Differences between FactoryLogix and V7 processes and routings
There are significant differences between how processes and routings are designed in FactoryLogix versus the older V7 system, specifically:
- A FactoryLogix process definition provides a clear separation of the process from the physical routing, whereas a V7 factory model combines these concepts into a single definition.
This fundamental change in process definitions means that there is no straightforward way to automatically map V7 process revisions based on V7 factory models directly to FactoryLogix process definitions. Instead, a mapping/translation tool helps you map V7 model points to their FactoryLogix equivalents. - When a new assembly or process is created in the FactoryLogix NPI client application, you are given the option to base it on any process revision in your V7 assembly tree.
When you select an existing V7 revision, the process migration wizard starts in FactoryLogix NPI and guides you through the migration process step-by-step. You are prompted to select a FactoryLogix process template, then mapping options are displayed, allowing you to map existing V7 model points to their FactoryLogix equivalents (operations). After you establish the desired mappings, you can reuse them whenever you migrate a V7 revision based on the same Factory Model to FactoryLogix.
What data is imported from V7?
When you import V7 process revisions into FactoryLogix, the following data is imported:
- ECAD and Gerber data
- BOM information
- BOM level AML, AVL, and Alternate Part information
- Component assignments
- Visual aids
- Embedded OLE objects (see OLE object translation for more information).
- Attached documents
- Notes (Notes are converted to a linked rich text document independent from the Visual Aid.)
OLE object translation (V7 visual aids)
Visual aids you designed using the V7 CircuitCAM product may contain both linked and embedded OLE objects (for example, embedded MS Word, Excel, or PDF documents). General support for OLE has been discontinued by Microsoft, and OLE is not supported by the FactoryLogix platform. As a result, alternative approaches to OLE are offered within FactoryLogix.
During the V7 to FactoryLogix visual aid conversion process, OLE objects will be converted to an alternative form as described in the following table.
V7 OLE Type | V7 OLE View Format | Converted FactoryLogix Format |
Embedded | Icon | Embedded document independent from visual aid |
Linked | Icon | Linked document independent from visual aid |
Embedded | In-place displayed | Flattened vector-based picture inside visual aid and embedded document independent from visual aid |
Linked | In-place displayed | Flattened vector-based picture inside visual aid and linked document independent from visual aid |
Embedded or Linked | Video object | Embedded document independent from visual aid (original video format of OLE object) |
In-place displayed OLE objects in V7 are converted into a simple picture in FactoryLogix. The OLE data source behind the in-place object will also carry over to FactoryLogix as an embedded document independent of the visual aid.
Smart Text mapping
The following Smart Text fields will map over to FactoryLogix during the migration process:
- Assembly Number
- Assembly Revision
- Customer
- Description
- Process Revision
- Modified Date
- Model Point
- Current Date
- Page Number
- Total Pages
- Job Name
Frequently-asked questions (FAQs)
| Question | Answer |
|---|---|
| What happens when a model point with part assignments is mapped to an inherited operation, when at the same time another model point with part assignments is mapped to the operation where the inheritance is coming from? | The operation where the inheritance is coming from will override the part assignments from the other mapped model point. |
| Will historical data such as WIP and defect information carry over during the V7 migration process? | No historical data is carried over during the migration process, only work instruction related information and documentation will carry over. |
| When selecting to import a CPF file, I see this error: “There was an error loading the requested CPF file.” What should I do? | This error indicates that the user logged into the workstation doesn't have full Administrator privileges. Relaunching FactoryLogix NPI with Administrator privileges will resolve this error. |
| I mapped a non-filtered model point to an operation in FactoryLogix. Why doesn't the operation show any part assignments? | Only model points that have direct part assignments will have their part assignments carry over during the migration process. |
| When I import a single visual aid into a work instruction, why do I see the prompt: “Are you sure you want to remove active work instructions on the step’s activities? | This prompt is informing you that since the top-level step already contains data, “re-mapping” a new visual aid to the step will overwrite any data attached to that step and its activities. |