Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 14806
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Project Management Software

AgentH22

The company I work for does not create many designs.  We do however have two seats of OrCad capture and PCB designer. Currently, designs are stashed on the network in some folder.  If the PCB guy dies or quits, It'll be hard to find his design files. We make many more mechanical assemblies than electrical and use Autodesk inventor as the solid modeling and drafting software and use Autodesk Vault as the project management and revision control software. 

Supposedly we can stick the any file type we want into a folder in Vault, but having native support would be ideal. Does anyone know if a Vault Plugin was created for Orcad files? 

Or... can anyone recommend a software for managing the PCB designs and versions?  I'm talking about Product Lifecycle Management software. Software that does version control, engineering change management, 

I do already know about OrCAD Data management. If this is what you were going to recommend, would it be overkill for just two seats of Orcad? 

Thanks in advance. 

Parents
  • Robert Finley

    I don't think I would ever design without a repo to avoid losing work.  Unless everything was stored on a ($$$$) NetApp server with hourly snapshots.

    I really like GIT.  It's easy to use GitHub.coim as your repo server.   But, SVN works great too.  These are usually thought of as "coder" repositories.  But, there's exponentially larger numbers of coders than cad designers.  This means there's a number of paid and "free"(if you want to share your data with the world, like GitHub.  I pay because I don't.) cloud services to use as your repo, or you can set one up for yourself.

    If you're new to all this, code repo systems come in two separate packages.   The UI front end (I love Atlassians free SourceTree tool) usually installs or recommends a good client-side package that is the underlying mechanism.

    These will bring you sorrow and joy as you miraculously pull yourself from the brink of disaster (schematic changes, software issues, disk crash). 

    Just have to understand that Forking makes life interesting (preserve your current file tree and create a separate working copy of everything with the option of merging everything back together into the main thread at some point).

    Anguish and sorrow can come from modifying a cad file before checking to see if anyone else made and committed their change.  You are now blocked.  These systems won't allow you to "commit" your changes unless you applied these edits to the latest file in the repository.  If the other person is willing to trash their changes, you pull their change, then overwrite it with the renamed copy of your version of that file.  Then the system will let you push or commit.

Reply
  • Robert Finley

    I don't think I would ever design without a repo to avoid losing work.  Unless everything was stored on a ($$$$) NetApp server with hourly snapshots.

    I really like GIT.  It's easy to use GitHub.coim as your repo server.   But, SVN works great too.  These are usually thought of as "coder" repositories.  But, there's exponentially larger numbers of coders than cad designers.  This means there's a number of paid and "free"(if you want to share your data with the world, like GitHub.  I pay because I don't.) cloud services to use as your repo, or you can set one up for yourself.

    If you're new to all this, code repo systems come in two separate packages.   The UI front end (I love Atlassians free SourceTree tool) usually installs or recommends a good client-side package that is the underlying mechanism.

    These will bring you sorrow and joy as you miraculously pull yourself from the brink of disaster (schematic changes, software issues, disk crash). 

    Just have to understand that Forking makes life interesting (preserve your current file tree and create a separate working copy of everything with the option of merging everything back together into the main thread at some point).

    Anguish and sorrow can come from modifying a cad file before checking to see if anyone else made and committed their change.  You are now blocked.  These systems won't allow you to "commit" your changes unless you applied these edits to the latest file in the repository.  If the other person is willing to trash their changes, you pull their change, then overwrite it with the renamed copy of your version of that file.  Then the system will let you push or commit.

Children
  • AgentH22
    in reply to Robert Finley
    Robert Finley said:
    Anguish and sorrow can come from modifying a cad file before checking to see if anyone else made and committed their change.  You are now blocked.  These systems won't allow you to "commit" your changes unless you applied these edits to the latest file in the repository.  If the other person is willing to trash their changes, you pull their change, then overwrite it with the renamed copy of your version of that file.  Then the system will let you push or commit.

    Does the repo software, SourceTree in your case, not make it obvious that another user is working on design? I now understand that it is a distributed version control system... this makes me wonder how the server (GitHub) knows if the local file on someone's computer is being worked on.  It seems like centralized version control systems like Autodesk's Vault, know if someone is working on a file since they have it checked out. 

    But good info. I have never looked at GitHub before, even though it's hard to go on the internet and not know of it's existence. 

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.