{"action":"opened","issue":{"url":"https://api.github.com/repos/open-contracting/standard/issues/373","repository_url":"https://api.github.com/repos/open-contracting/standard","labels_url":"https://api.github.com/repos/open-contracting/standard/issues/373/labels{/name}","comments_url":"https://api.github.com/repos/open-contracting/standard/issues/373/comments","events_url":"https://api.github.com/repos/open-contracting/standard/issues/373/events","html_url":"https://github.com/open-contracting/standard/issues/373","id":177657689,"number":373,"title":"Milestones","user":{"login":"timgdavies","id":342624,"avatar_url":"https://avatars.githubusercontent.com/u/342624?v=3","gravatar_id":"","url":"https://api.github.com/users/timgdavies","html_url":"https://github.com/timgdavies","followers_url":"https://api.github.com/users/timgdavies/followers","following_url":"https://api.github.com/users/timgdavies/following{/other_user}","gists_url":"https://api.github.com/users/timgdavies/gists{/gist_id}","starred_url":"https://api.github.com/users/timgdavies/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timgdavies/subscriptions","organizations_url":"https://api.github.com/users/timgdavies/orgs","repos_url":"https://api.github.com/users/timgdavies/repos","events_url":"https://api.github.com/users/timgdavies/events{/privacy}","received_events_url":"https://api.github.com/users/timgdavies/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/open-contracting/standard/labels/2%20-%20Proposal","name":"2 - Proposal","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/open-contracting/standard/milestones/5","html_url":"https://github.com/open-contracting/standard/milestones/Version%201.1","labels_url":"https://api.github.com/repos/open-contracting/standard/milestones/5/labels","id":1231433,"number":5,"title":"Version 1.1","description":"Issues for consideration for Version 1.1","creator":{"login":"timgdavies","id":342624,"avatar_url":"https://avatars.githubusercontent.com/u/342624?v=3","gravatar_id":"","url":"https://api.github.com/users/timgdavies","html_url":"https://github.com/timgdavies","followers_url":"https://api.github.com/users/timgdavies/followers","following_url":"https://api.github.com/users/timgdavies/following{/other_user}","gists_url":"https://api.github.com/users/timgdavies/gists{/gist_id}","starred_url":"https://api.github.com/users/timgdavies/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timgdavies/subscriptions","organizations_url":"https://api.github.com/users/timgdavies/orgs","repos_url":"https://api.github.com/users/timgdavies/repos","events_url":"https://api.github.com/users/timgdavies/events{/privacy}","received_events_url":"https://api.github.com/users/timgdavies/received_events","type":"User","site_admin":false},"open_issues":83,"closed_issues":23,"state":"open","created_at":"2015-07-29T12:19:44Z","updated_at":"2016-09-18T15:20:41Z","due_on":"2016-09-29T23:00:00Z","closed_at":null},"comments":0,"created_at":"2016-09-18T15:20:41Z","updated_at":"2016-09-18T15:20:41Z","closed_at":null,"body":"This issue is under consideration for the 1.1 milestone. \r\n\r\nThis builds on prior discussions in #227\r\n\r\n### The issue\r\n\r\nThe milestones block in OCDS was developed to provide a flexible space to capture date and process-related information that is not otherwise standardised. \r\n\r\nHowever, to date it has not been widely used, and it is not currently possible to distinguish between the different kinds of milestones that may exist during a procurement process. \r\n\r\nFor example, is a milestone a delivery requirement of providers? Or a description of key deadlines during an engagement process during planning. \r\n\r\n## The proposal\r\n\r\nWe will introduce a milestone type field to:\r\n\r\n* Enable consuming applications to distinguish between the different kinds of milestones, whichever block they appear in;\r\n* Allow publishers to be clearer about the kinds of milestones they are publishing;\r\n\r\nThe proposed codelist for this is:\r\n\r\n\r\n| Code | Title | Description |\r\n|------|-------|-------------|\r\n| planning | Planning milesones | For events during the planning phase of a process. |\r\n| engagement | Engagement milestones | For engagement milestones, such as a public hearing |\r\n| adjudication | Adjudication milestones | For adjudication milestones, such as the meeting date of a committee. |\r\n| delivery | Delivery milestones | For delivery milestones, such as the date when a good or service should be provided. |\r\n| reporting | Reporting milestones | For reporting milestones, such as when key reports should be provided. |\r\n\r\nWe will update the milestoneStatus code list to include an extra entry for **scheduled** milestones, and will add definitions, giving a codelist of:\r\n\r\n| Code | Title | Description |\r\n|------|-------|-------------|\r\n| scheduled | Scheduled | This milestone has been scheduled for the date in milestone.dueDate. Progress towards the milestone has not yet been evaluated as of milestone.dateModified |\r\n| met | Met | This milestone has been achieved. The data on which it was met should be placed in the milestone.dateMet field |\r\n| notMet | Not Met | This milestone had not been met at the date it was last reviewed (see milestone.dateModified). |\r\n| partiallyMet | Partially Met | This milestone was judged to have been partially met at the date it was last reviewed (see milestone.dateModified)\r\n\r\nWe will add a ```milestone.dateMet``` field so that the data a milestone was met on can be explicitly declared.\r\n\r\nIn issue #355 we are also proposing deprecating milestone documents from core. This would be re-introduced in an extension, but to simplify the standard, we would not ask for documents attached to individual milestones. \r\n\r\n## Questions\r\n\r\n```dateMet``` does not follow our usual pattern of using 'Date' as the suffix rather than prefix. However, it feels more natural than ```metDate```. Views on terminology here are welcome. \r\n\r\n(dateModified is an existing exception to the pattern, as we follow common terminology in use in other standards for this). \r\n\r\nShould we also consider adding a ```code``` field to milestones that would allow explicit cross-referencing between milestones in tender, award and contract - and that would allow cross-referencing to codelists of more detailed milestones for particular countries? \r\n\r\n(For example, there could be a code for the 'bid opening date' so that all EU contracts can clearly indicate this). \r\n\r\nShould we consider adding a ```report``` field for free-text information reporting on the milestones progress?\r\n\r\n\r\n## Worked example\r\n\r\nIn the example below, a publisher is providing anticipated dates of the committee meeting in the tender block, along with details of when they took place. In the award they are specifying agreed delivery deadlines and reporting deadlines.\r\n\r\n```json\r\n{\r\n\"uri\":\"http://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json\",\r\n\"publishedDate\":\"2010-05-10T09:30:00Z\",\r\n\"publisher\": {\r\n        \"scheme\": \"GB-COH\",\r\n        \"uid\": \"09506232\",\r\n        \"name\": \"Open Data Services Co-operative Limited\",\r\n        \"uri\": \"http://standard.open-contracting.org/examples/\"\r\n    },\r\n\"license\":\"http://opendatacommons.org/licenses/pddl/1.0/\",\r\n\"publicationPolicy\":\"https://github.com/open-contracting/sample-data/\",\r\n\"releases\":[{\r\n        \"language\": \"en\",\r\n        \"ocid\": \"ocds-213czf-000-00001\",\r\n        \"id\": \"ocds-213czf-000-00001-04-award\",\r\n        \"date\": \"2010-05-10T09:30:00Z\",\r\n        \"tag\": [\"award\"],\r\n        \"initiationType\": \"tender\",\r\n        \"entities\": {\r\n          \"...\":\"...\"\r\n        },\r\n        \"buyer\": {\r\n            \"id\":\"GB-LAC-E09000003\",\r\n            \"name\": \"London Borough of Barnet\",\r\n        },\r\n        \"tender\": {\r\n            \"id\": \"ocds-213czf-000-00001-01-tender\",\r\n            \"title\": \"Planned cycle lane improvements\",\r\n            \"description\": \"Tenders solicited for work to build new cycle lanes in the centre of town.\",\r\n            \"status\": \"active\",\r\n            \"items\": [\r\n                {\r\n                    \"id\": \"0001\",\r\n                    \"description\": \"string\",\r\n                    \"classification\": {\r\n                        \"scheme\": \"CPV\",\r\n                        \"id\": \"45233130\",\r\n                        \"description\": \"Construction work for highways\",\r\n                        \"uri\": \"http://cpv.data.ac.uk/code-45233130\"\r\n                    },\r\n                    \"additionalClassifications\": [\r\n                        {\r\n                            \"scheme\": \"CPV\",\r\n                            \"id\": \"45233162-2\",\r\n                            \"description\": \"Cycle path construction work\",\r\n                            \"uri\": \"http://cpv.data.ac.uk/code-45233162.html\"\r\n                        }\r\n                    ],\r\n                    \"quantity\": 8,\r\n                    \"unit\": {\r\n                        \"name\": \"Miles\",\r\n                        \"value\": {\r\n                            \"amount\": 120000,\r\n                            \"currency\": \"GBP\"\r\n                        }\r\n                    }\r\n                }\r\n            ],\r\n            \"minValue\": {\r\n                \"amount\": 600000,\r\n                \"currency\": \"GBP\"\r\n            },\r\n            \"value\": {\r\n                \"amount\": 1100000,\r\n                \"currency\": \"GBP\"\r\n            },\r\n            \"procurementMethod\": \"open\",\r\n            \"procurementMethodRationale\": \"An open competitive tender is required by EU Rules\",\r\n            \"awardCriteria\": \"bestProposal\",\r\n            \"awardCriteriaDetails\": \"The best proposal, subject to value for money requirements, will be accepted.\",\r\n            \"submissionMethod\": [ \"electronicSubmission\" ],\r\n            \"submissionMethodDetails\": \"Submit through the online portal at http://example.com/submissions/ocds-213czf-000-00001-01/\",\r\n            \"enquiryPeriod\": {\r\n                    \"startDate\": \"2010-03-01T09:00:00Z\",\r\n                    \"endDate\": \"2010-03-14T17:30:00Z\"\r\n            },\r\n            \"hasEnquiries\": false,\r\n            \"tenderPeriod\": {\r\n                \"startDate\": \"2010-03-01T09:00:00Z\",\r\n                \"endDate\": \"2010-04-01T18:00:00Z\"\r\n                \r\n            },\r\n            \"awardPeriod\": {\r\n                \"startDate\": \"2010-06-01T00:00:00Z\",\r\n                \"endDate\": \"2011-08-01T23:59:59Z\"\r\n            },\r\n            \"milestones\": [{\r\n                \"id\": \"0001\",\r\n                \"type\":\"adjudication\",\r\n                \"title\": \"Bid Opening \",\r\n                \"description\": \"The data when the bid will be openned.\",\r\n                \"dueDate\": \"2010-04-01T18:00:00Z\",\r\n                \"status\":\"met\",\r\n                \"dateMet\": \"2010-04-01T18:00:00Z\",\r\n                \"dateModified\":\"2010-04-01T18:00:00Z\"\r\n\r\n            },\r\n            {\r\n                \"id\": \"0002\",\r\n                \"type\":\"adjudication\",\r\n                \"title\": \"Review Committee Meeting \",\r\n                \"description\": \"The date when the review committee will meet to assess bids.\",\r\n                \"dueDate\": \"2010-04-05T15:00:00Z\",\r\n                \"status\":\"met\",\r\n                \"dateMet\": \"2010-04-05T16:00:00Z\",\r\n                \"dateModified\":\"2010-04-01T18:00:00Z\"\r\n              }]\r\n        },\r\n        \"awards\": [\r\n               {\r\n                   \"id\": \"ocds-213czf-000-00001-award-01\",\r\n                   \"title\": \"Award of contract to build new cycle lanes in the centre of town.\",\r\n                   \"description\": \"AnyCorp Ltd has been awarded the contract to build new cycle lanes in the centre of town.\",\r\n                   \"status\": \"pending\",\r\n                   \"date\": \"2010-05-10T09:30:00Z\",\r\n                   \"value\": {\r\n                       \"amount\": 11000000,\r\n                       \"currency\": \"GBP\"\r\n                   },\r\n                   \"suppliers\": [\r\n                       {\r\n                           \"id\":\"GB-COH-1234567844\",\r\n                           \"name\": \"AnyCorp Cycle Provision\",\r\n                       }\r\n                   ],\r\n                   \"items\": \"...\",\r\n                   \"contractPeriod\": {\r\n                       \"startDate\": \"2010-07-01T00:00:00Z\",\r\n                       \"endDate\": \"2011-08-01T23:59:00Z\"\r\n                   },\r\n                   \"milestones\": [\r\n                      {\r\n                        \"id\":\"0003\",\r\n                        \"type\":\"delivery\",\r\n                        \"title\":\"Building work started\",\r\n                        \"description\":\"Building work should start by this date.\",\r\n                        \"dueDate\":\"2010-10-01T00:00:00Z\",\r\n                        \"status\":\"planned\",\r\n                        \"dateModified\":\"2010-05-10T09:30:00Z\"\r\n                      },\r\n                      {\r\n                        \"id\":\"0004\",\r\n                        \"type\":\"delivery\",\r\n                        \"title\":\"Building work complete\",\r\n                        \"description\":\"Building work should be complete by this date.\",\r\n                        \"dueDate\":\"2011-06-01T00:00:00Z\",\r\n                        \"status\":\"planned\",\r\n                        \"dateModified\":\"2010-05-10T09:30:00Z\"\r\n                      },\r\n                      {\r\n                        \"id\":\"0005\",\r\n                        \"type\":\"reporting\",\r\n                        \"title\":\"Project initiation report\",\r\n                        \"description\":\"A report on project initiation should be provided by the end of 2010\",\r\n                        \"dueDate\":\"2010-12-12T00:00:00Z\",\r\n                        \"status\":\"planned\",\r\n                        \"dateModified\":\"2010-05-10T09:30:00Z\"\r\n                      },\r\n                      {\r\n                        \"id\":\"0006\",\r\n                        \"type\":\"reporting\",\r\n                        \"title\":\"Mid-term project report\",\r\n                        \"description\":\"A mid-term project report should be provided by March 2011\",\r\n                        \"dueDate\":\"2011-03-31T00:00:00Z\",\r\n                        \"status\":\"planned\",\r\n                        \"dateModified\":\"2010-05-10T09:30:00Z\"\r\n                      },\r\n                      {\r\n                        \"id\":\"0007\",\r\n                        \"type\":\"reporting\",\r\n                        \"title\":\"Final project report\",\r\n                        \"description\":\"The final project report should be provided by the end of the project.\",\r\n                        \"dueDate\":\"2011-08-01T23:59:00Z\",\r\n                        \"status\":\"planned\",\r\n                        \"dateModified\":\"2010-05-10T09:30:00Z\"\r\n                      }\r\n                   ]\r\n                }\r\n           ]\r\n\r\n    }]\r\n}\r\n```\r\n\r\n\r\n## Additional implications\r\n\r\nTo the best of our knowledge, few procurement systems have very detailed structured information on them on milestones, particularly delivery and reporting milestones. As a result, inclusion of delivery and reporting milestone blocks in the standard for tender and award is driven by user needs, more than existing data supply.\r\n\r\nThis means we that inclusion of this updated milestone block in the standard constitutes encouragement for improvements in the collection and management of this kind of information.\r\n\r\nWe should develop some interface guidance on:\r\n\r\n(a) Collecting milestone information;\r\n\r\n(b) Displaying milestone information;\r\n\r\nTo ensure that publishers and users have a clear understanding of the capababilities, and the limitations, of the milestone block.\r\n\r\n## Engagement\r\n\r\nPlease indicate support or opposition for this proposal using the +1 / -1 buttons or a comment. If opposing the proposal, please give clear justifications, and where possible, make an alternative proposals.\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"timgdavies"}}