{"action":"created","issue":{"url":"https://api.github.com/repos/valnet/valuenetwork/issues/400","labels_url":"https://api.github.com/repos/valnet/valuenetwork/issues/400/labels{/name}","comments_url":"https://api.github.com/repos/valnet/valuenetwork/issues/400/comments","events_url":"https://api.github.com/repos/valnet/valuenetwork/issues/400/events","html_url":"https://github.com/valnet/valuenetwork/issues/400","id":90670351,"number":400,"title":"Something inbetween Work Order and Project?","user":{"login":"fosterlynn","id":3776081,"avatar_url":"https://avatars.githubusercontent.com/u/3776081?v=3","gravatar_id":"","url":"https://api.github.com/users/fosterlynn","html_url":"https://github.com/fosterlynn","followers_url":"https://api.github.com/users/fosterlynn/followers","following_url":"https://api.github.com/users/fosterlynn/following{/other_user}","gists_url":"https://api.github.com/users/fosterlynn/gists{/gist_id}","starred_url":"https://api.github.com/users/fosterlynn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fosterlynn/subscriptions","organizations_url":"https://api.github.com/users/fosterlynn/orgs","repos_url":"https://api.github.com/users/fosterlynn/repos","events_url":"https://api.github.com/users/fosterlynn/events{/privacy}","received_events_url":"https://api.github.com/users/fosterlynn/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/valnet/valuenetwork/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-06-24T13:03:34Z","updated_at":"2015-12-07T00:13:13Z","closed_at":null,"body":"Do we need something between a Work Order and Project as an Agent?\r\n\r\nSensorica uses Project as something fairly ongoing, with some of its own governance (like value equation), roughly relating to a product line.  It has a strong organizational flavor, and we have slotted it as an Agent.\r\n\r\nMany people use the word \"project\" as something that produces a goal, has an end, and is not primarily organizational.  This is common in IT for example.  And it came up when discussion how to structure the NextEdge working group data.  This however might be larger and longer than a work order, and work orders are needed for smaller units of work.\r\n\r\nShould we add something else?  If so, how to model and how to represent in the UI?"},"comment":{"url":"https://api.github.com/repos/valnet/valuenetwork/issues/comments/162379229","html_url":"https://github.com/valnet/valuenetwork/issues/400#issuecomment-162379229","issue_url":"https://api.github.com/repos/valnet/valuenetwork/issues/400","id":162379229,"user":{"login":"TiberiusB","id":3913289,"avatar_url":"https://avatars.githubusercontent.com/u/3913289?v=3","gravatar_id":"","url":"https://api.github.com/users/TiberiusB","html_url":"https://github.com/TiberiusB","followers_url":"https://api.github.com/users/TiberiusB/followers","following_url":"https://api.github.com/users/TiberiusB/following{/other_user}","gists_url":"https://api.github.com/users/TiberiusB/gists{/gist_id}","starred_url":"https://api.github.com/users/TiberiusB/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TiberiusB/subscriptions","organizations_url":"https://api.github.com/users/TiberiusB/orgs","repos_url":"https://api.github.com/users/TiberiusB/repos","events_url":"https://api.github.com/users/TiberiusB/events{/privacy}","received_events_url":"https://api.github.com/users/TiberiusB/received_events","type":"User","site_admin":false},"created_at":"2015-12-07T00:13:13Z","updated_at":"2015-12-07T00:13:13Z","body":"SENSORICA uses \"project\" as a context of work, as defined by Bob at the beginning. I think is a good definition and it sticks with us. \r\nA project in SENSORICA, as Lynn mentioned above, is an activity that has a beginning and an end, which is usually a market exchange, or some inflow from outside, like funding (grant, sponsorship, ...). I guess the most generic criteria is whenever the network has an intake as a result of an activity, a sale or some sort of funding, we need a project. Some funding activity can already be  part of an existing project, in that case we simply create a process or a Workflow recipe for that same project. \r\nSENSORICA uses \"Building SENSORICA\" as a context of work, or project, for everything related to development or maintenance of the network. For example, if we have a fundraising activity for SENSORICA, we create a process or a Workflow recipe for the \"Building SENSORICA\" project. \r\nFrom my experience, I think processes do the in-between job... "}}