Altium Concord Pro, in conjunction with Altium Designer, brings support for Managed Projects. Managed Projects target the development stage of the project lifecycle, simplifying the creation and ongoing workflow for version controlled projects. Centralized storage under the control of Concord Pro also enables this feature to be a foundation for other collaborative services.
Some key benefits to using Managed Projects are:
- Simplified storage. No need to make decisions about storage locations. Backup and other basic services are taken care of.
- Foundation for collaborative features.
- Enforced version control.
- Beneficiary of a dedicated commenting system.
- Notifications and status. Document status including local modifications is visible to entire design teams.
- Concurrent PCB design works without any complex setup.
Management is performed through the Projects page of Concord Pro's browser interface. New Managed Projects can be created through this interface, or through the Create Project dialog in Altium Designer. Alternatively, an existing, non-managed project, can be quickly made available to Concord Pro.
You can also access a manufacturing orientated CAD-centric view of the project, which offers Design, Manufacturing and BOM view options:
- Design - display and navigate source project design documents, view design object properties and place review comments. This view uses the Web Review interface. This view is for the latest version of the source project data, rather than a specified release from that project, and so could be considered to be a work-in-progress (WIP) view. You can view the base design, or any defined variant thereof.
- Manufacturing - view the releases for the project. Access is provided for opening a release, which will be presented on a separate tab through a Manufacturing Portal. From this portal you can view and navigate the released Assembly and Fabrication data, inspect the BOM, and ultimately download the data into a manufacturing Build Package.
- BOM - view the source project's Bill Of Materials information.
Reusable Design Circuitry
Being able to re-use design content is something that all product development companies want, and can greatly benefit from. Not only does reuse save time, being able to easily re-use a section of a previous design means that all the qualification and testing of that part of the design is done. Design reuse is much more than copy and paste though, true reuse requires the content to be locked down so you're guaranteed that it is the same as before. No quick edits to change the color of a component or a tweak to a resistor value, working with reusable content must be like working with off-the-shelf components; place the content, wire it in, and it works just like it did last time.
Altium Designer, in conjunction with Altium Concord Pro, caters for the ability to create Managed Schematic Sheets (often termed Managed Sheets) in that Concord Pro instance. Such Items can be created directly from within Concord Pro. Once a Managed Schematic Sheet Item has been created (and data released into a revision of it), and its lifecycle state set to a level that the organization views as ready for use at the design level, it can be reused in future board-level design projects.
A managed sheet is a standard Altium Designer schematic sheet containing components and wiring, that has been stored in Concord Pro so it can be re-used in other designs. It is edited like any other schematic sheet. The managed sheet concept is not limited to a single schematic sheet, you can place a managed sheet in your design that is at the top of a tree of other managed sheets.
The decision to move from device sheets to managed sheets comes when there is a desire to make the transition from re-useable content to managed re-useable content - that is, when there is a desire or need to be able to control the release, revision status and lifecycle state of that design content.
By making it managed content you can be sure that the revision of a managed sheet that you use in a design can be easily identified and traced back to its source whenever needed. And because it is managed content it can be revised and updated when needed; and the usage relationships can all be traced, both down to the components on that sheet, and up to the designs that use that sheet. This ensures you have all the information needed to decide if that revised sheet must be pushed through to existing designs, or if a particular design must continue to use the previous revision.
Altium Designer, with its unified design approach, has traditionally used a component model that extends across all aspects of the electronics design process. However, to seamlessly fit the process of electronics design into the encapsulating product development process as a whole, this model needs to evolve - extending to cover other aspects including other design processes (in particular MCAD and Industrial Design), as well as business processes (such as procurement and manufacturing) that intersect with the product development process. This evolved object model is known as the Unified Component Model.
This component model effectively maps the concept of a design component - in the traditional electronics design arena - to the component as seen by the rest of the organization in the bigger 'product arena'. A truly 'Unified Component' model that not only represents the component in the different design domains (Schematic Capture, PCB Layout, Simulation) but also facilitates choices of the desired physical components - real-world manufactured parts - at design-time, offering a significant improvement in terms of procurement cost and time, when manufacturing the assembled product.
Under this modeling paradigm, the design component, as seen by the designer, is separated from the Manufacturer and/or Vendor parts. This information is not defined as part of the component. Instead, Part Choices are used to map the design component to one or more Manufacturer Parts, listed in a Part Catalog, which in turn can be mapped to one or more Vendor parts, allowing the designer to state up-front, what real parts can be used for any given design component used in a design.
These components, along with their part choices, are stored in Concord Pro. A managed component (as it is then referred) is stored as a series of revisions of a uniquely-identifiable Component Item. Each revision is lifecycle-managed, providing collections of certified components, authorized to be re-instantiated into new design projects, manufactured into prototypes, or used for production runs. In short, a catalog of components implemented through server-based 'libraries'.
- Company-certified design components - components are released into a managed content server for re-instantiation into a design project. Revision-controlled and lifecycle-managed, a company can authorize the 'set' of components that can be formally used by their designers.
- Design-time choice of physical components - for any given managed component, you can choose which Manufacturer Parts can be used to implement that component when assembling the board.
- Real-time supply-chain information - fed back from the aggregate parts database of the Altium Parts Provider (which itself interfaces to, and gathers the parts from, enabled Suppliers), to let the designer know the current costing and availability of the chosen parts, and from all vendors that sell those chosen parts (as defined in Concord Pro's local Part Catalog).
- Use of Component Templates - apply parameter and component taxonomy based templates, so each new component type automatically has the correct BOM-compliant parameter set, in addition to automating the correct naming, revision and lifecycle schemes.
- Where-used Component Traceability - managed components can be traced all the way through usages: if a part goes obsolete, you can explore which designs it was used in to know which ones need to be updated. If a symbol or footprint has an error, you can see all the components that use that symbol and footprint, so you can go ahead and fix them.
- Component Lifecycle Validation - if a component is in an “end of life”, “obsolete”, or “abandoned” state, you will be warned before trying to manufacture boards that use it.
- Direct Component Editing - if a managed component needs to be edited, you can open it for editing directly from within your managed content server. A temporary instance of the Component Editor allows you to edit all aspects of that component, including modifying its referenced domain models, without a file-based document in sight.
Altium Designer, in conjunction with Altium Concord Pro, caters for the ability to create and manage a variety of templates for use in and by, your board design projects. The following template types are supported:
Once a template has been released to Concord Pro, and its lifecycle state set to a level that the organization views as ready for use at the design level, that template can be reused in future board-level design projects.
You even have the opportunity to create managed Project Templates. Such templates stored in Concord Pro can include the common document and file types that make up a project, as well as additional reference documentation and configuration files.
Board Design Release
Altium Designer provides powerful, high-integrity board design release management. The board design release process is automated, enabling you to release your board design projects without the risks associated with manual release procedures. When a particular project is released, a snapshot of the design source is taken and archived along with any generated output - which represents a tangible product that is made from that design project and sold by the company. Release data is stored in revisions of the relevant project-related Item in Concord Pro:
- PCB Project Design Item - the snapshot of the design, including all source documents. Released into a separate Item in the server, allowing you to keep your valuable IP aside from the generated fabrication and assembly data needed by external parties to build the product.
- PCB Fabrication Data Item - the data set required by the fabrication house for manufacture of the bare board.
- PCB Assembly Data Item - the data set required by the assembly house in order to populate the bare board with specified components, in accordance with a Bill of Materials. A unique Item is used for the base (fully populated) design, and each defined variant for the design (assembled variants).
The overall result is the highest-integrity board design release management possible. Not only is your actual design project tightly monitored, backed-up, and managed in a version-controlled Design Repository, but also too, the releases of its data in a similar manner within the target server - robust, safe, secure.
- Integration with version control. If your project is under version control, then the system requires all files to be checked in and up to date before releasing. This ensures that no "private copy" of an essential design document is ever allowed to sit on an engineer's hard drive - with the potential of becoming lost. This simple rule can save hours down the track in costly searching for the right set of design documents that were used to generate a released product.
- 'One-shot releasing'. The system only allows you to release once to any given revision of a targeted Item. In fact, a successful release results in committing (storing) the release data in the referenced Item Revision, then closes that revision. No further data can be generated and released into that same revision.
- Automated and repeatable design release process. One-touch releasing - no manual stages or risks. From taking the snapshot of the design files, through validation, and output generation, there is no interaction. If a part of the process fails, the release fails. Simple as that. And you get to review all generated data before final committal of the release data into the Item Revision in the target server.
- Ability to validate the design as an integral part of the design release process. The release process works from a 'locked down' snapshot of the design source (including dependencies) and pre-release validation is almost sure to have been performed prior to initiating release. But for additional peace of mind and to ensure the integrity of the design data, you can optionally add validation checks into the release process 'flow', through appropriately-configured Output Job Configurations. Standard ERC checking for the source schematics and DRC checking of the PCB, but also the ability to check that the source project and PCB are in-sync, and comparison of footprints on the board against their source library to ensure they are up-to-date, and matched. The release will fail if any validation checks are not passed successfully.
- All generated data files from the design release process can be optionally prefixed with the Item ID and the Item Revision ID, ensuring there can be no ambiguity as to which revision of which Item the data is to be used to build.
- Publishing. Offering the ability to publish release data directly from a managed content server to a shared storage medium, such as Amazon S3, FTP servers, Box.com, or a simple network-based folder. This facilitates easy sharing of server data in a secured way, without providing outside parties access to that server.
The Project Releaser
The release process itself is performed using Altium Designer's Project Releaser, the user-interface to which is provided courtesy of a dedicated view - the Release view.
The Project Releaser caters for all types of PCB project - unmanaged/non-version-controlled, under external VCS control, or managed through a managed content server - by offering two modes of operation:
- Online Mode - releasing all generated data to revisions of Items in Concord Pro. You don't even have to remember to increment Item Revisions, it is all handled for you.
- Offline Mode - releasing all generated data into a folder-based structure, which can be optionally wrapped up in a single Zip file.
With the Release view in
Online Mode, the release process is a staged flow, with the entries on the left-hand side of the view showing you at-a-glance, which stage you are currently at:
- Configure Server Release - this stage of the release process is where you specify the type(s) of data that you wish to generate (Source Data (always generated), Fabrication Data, Assembly Data (for base design and each detected variant)).
- Validate Project - this next stage of the release process is run automatically when one or more Validation-type reports are detected in assigned OutJob file(s). All defined validation output generators, defined in an Output Job file assigned to the data item being released, are run.
- Generate Data - this next stage of the release process is run automatically. This is where all other outputs - defined in the OutJob file(s) assigned to the included Data Items - are run, to generate the data to be released into the relevant target items in the server.
- Review Data - with all validation checks passed, and output data generated, this stage of the release process allows you to review the generated data.
- Upload Data - after confirming the release in the previous stage, this next stage is automatically entered. It simply presents progress of data upload into the revisions of the relevant data Items in the target Concord Pro instance.
- Execution Report - this is the final stage of the process, providing a summary of the release. Navigation links are provided to quickly browse to the generated Item Revisions in the Explorer panel.
With the Project Releaser, you'll be able to generate your manufacturing data with simplified ease, and with the highest integrity. And you'll also be able to survey the fruits of that generation before you commit to finalizing the release (viewing Gerbers/ODB++ data in the CAM Editor for example), ensuring that the data you have generated is exactly the data required to get your board manufactured on time, first time.
Publication of Released Data
For released data generated from a board design project (PCB Fabrication Data, PCB Assembly Data, and PCB Project Design Items only), you have the ability to directly publish that data from your managed content server, or Output Job, to a storage space, such as Box.com, Amazon S3, an FTP server, or a simple folder location on a shared network. In terms of distribution and collaboration, this provides an unparalleled advantage in a world where the collective members of the overall 'product team' - the design team, the manufacturing team and all others involved in the process of getting a product from thought to reality - are often dispersed around the globe.
Publishing is a matter of defining a Publishing Destination and then uploading the released data for the required Item Revision to that destination. From the manufacturing plant in China, to the design teams in Kiev, Stanstead Abbotts, and San Diego, and to the Project Director in-flight somewhere across the Pacific, everyone that needs to know about the new release can be invited with a link to the published folder - shared (and controlled) access to view, discuss, and utilize the data with which to build the Item.