Category:104 Scope - Revision history

Hoskir at 17:54, 12 December 2024

2024-12-12T17:54:54Z

← Older revision		Revision as of 12:54, 12 December 2024
Line 26:		Line 26:
	This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].		This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].

	[[Category:~~100 General~~]]		[[Category:100_GENERAL]]

Hoskir: linked to cat 100

2024-11-26T20:28:47Z

linked to cat 100

← Older revision		Revision as of 15:28, 26 November 2024
Line 25:		Line 25:

	This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].		This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].

			[[Category:100 General]]

Hoskir: updated per RR3774

2023-09-21T21:24:44Z

updated per RR3774

← Older revision		Revision as of 16:24, 21 September 2023
Line 18:		Line 18:
	MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.		MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.

	The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.		The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks, [[907.9_Safety_Assessment_For_Every_Roadway_(SAFER)\|project safety assessment]] and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.

	When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.		When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.

Smithk: Per TP, clarified guidance

2020-05-27T19:41:28Z

Per TP, clarified guidance

← Older revision		Revision as of 14:41, 27 May 2020
Line 16:		Line 16:
	[[104.2 Project Scoping\|A project's scope]] can be defined as the set of design parameters that precisely satisfy the purpose and need of the project. A poorly identified scope that is broader than the purpose and need will result in an unnecessarily high project budget and lengthy schedule, while a scope that falls short will yield a project that accomplishes little of significance. Further, a construction program based on poorly scoped projects will eventually fragment, whether by expanding the scope to meet the need during the design process or through field adjustment to correct errors and additional needs during construction.		[[104.2 Project Scoping\|A project's scope]] can be defined as the set of design parameters that precisely satisfy the purpose and need of the project. A poorly identified scope that is broader than the purpose and need will result in an unnecessarily high project budget and lengthy schedule, while a scope that falls short will yield a project that accomplishes little of significance. Further, a construction program based on poorly scoped projects will eventually fragment, whether by expanding the scope to meet the need during the design process or through field adjustment to correct errors and additional needs during construction.

	~~When~~ transportation needs ~~arise~~, planning ~~staff will~~ prioritize ~~them and present them~~ to the ~~project manager, marking the commencement of~~ [[:Category:138 Project Development Chronology\|project development]]. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.		MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.

	The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.		The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.

	When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is ~~dependant~~ upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.		When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.

	MoDOT also encourages contractor participation in cost-saving techniques. This article contains [[104.13 Construction Inspection Guidance for Sec 104\|construction inspection guidance]] for [[:Category:130 Value Engineering\|value engineering]] involving monetary incentives for contractors.		MoDOT also encourages contractor participation in cost-saving techniques. This article contains [[104.13 Construction Inspection Guidance for Sec 104\|construction inspection guidance]] for [[:Category:130 Value Engineering\|value engineering]] involving monetary incentives for contractors.

	This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].		This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].

Smithk at 21:15, 30 January 2019

2019-01-30T21:15:25Z

← Older revision		Revision as of 16:15, 30 January 2019
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[~~http~~://modot.org/~~plansandprojects/construction_program/STIP2016~~-~~2020/index.htm~~ MoDOT's STIP website]		\|[https://www.modot.org/statewide-transportation-improvement-program-stip MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

Smithk: updated link

2015-07-07T12:54:28Z

updated link

← Older revision		Revision as of 07:54, 7 July 2015
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[http://~~www.~~modot.org/plansandprojects/construction_program/~~STIP2015~~-~~2019~~/index.htm MoDOT's STIP website]		\|[http://modot.org/plansandprojects/construction_program/STIP2016-2020/index.htm MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

Smithk: Updated link

2014-08-08T15:06:44Z

Updated link

← Older revision		Revision as of 10:06, 8 August 2014
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[http://www.modot.org/plansandprojects/construction_program/~~STIP2013~~-~~2017~~/ MoDOT's STIP website]		\|[http://www.modot.org/plansandprojects/construction_program/STIP2015-2019/index.htm MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

Smithk: Updated STIP link

2012-07-11T18:17:05Z

Updated STIP link

← Older revision		Revision as of 13:17, 11 July 2012
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[http://www.modot.~~mo.gov~~/plansandprojects/construction_program/STIP2013-2017/~~index.htm~~ MoDOT's STIP website]		\|[http://www.modot.org/plansandprojects/construction_program/STIP2013-2017/ MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

Smithk: Updated STIP link

2012-07-11T18:12:50Z

Updated STIP link

← Older revision		Revision as of 13:12, 11 July 2012
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[http://www.modot.mo.gov/plansandprojects/construction_program/~~STIP2012~~-~~2016~~/ MoDOT's STIP website]		\|[http://www.modot.mo.gov/plansandprojects/construction_program/STIP2013-2017/index.htm MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

Smithk: Updated STIP link

2011-07-13T18:05:20Z

Updated STIP link

← Older revision		Revision as of 13:05, 13 July 2011
Line 8:		Line 8:
	\|'''Related Information'''		\|'''Related Information'''
	\|-		\|-
	\|[http://www.modot.~~org~~/plansandprojects/construction_program/~~STIP2011~~-~~2015~~/~~index.htm~~ MoDOT's STIP website]		\|[http://www.modot.mo.gov/plansandprojects/construction_program/STIP2012-2016/ MoDOT's STIP website]
	\|}		\|}
	\|}		\|}

← Older revision		Revision as of 16:24, 21 September 2023
Line 18:		Line 18:
	MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.		MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.

	The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.		The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks, [[907.9_Safety_Assessment_For_Every_Roadway_(SAFER)\|project safety assessment]] and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.

	When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.		When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.

← Older revision		Revision as of 14:41, 27 May 2020
Line 16:		Line 16:
	[[104.2 Project Scoping\|A project's scope]] can be defined as the set of design parameters that precisely satisfy the purpose and need of the project. A poorly identified scope that is broader than the purpose and need will result in an unnecessarily high project budget and lengthy schedule, while a scope that falls short will yield a project that accomplishes little of significance. Further, a construction program based on poorly scoped projects will eventually fragment, whether by expanding the scope to meet the need during the design process or through field adjustment to correct errors and additional needs during construction.		[[104.2 Project Scoping\|A project's scope]] can be defined as the set of design parameters that precisely satisfy the purpose and need of the project. A poorly identified scope that is broader than the purpose and need will result in an unnecessarily high project budget and lengthy schedule, while a scope that falls short will yield a project that accomplishes little of significance. Further, a construction program based on poorly scoped projects will eventually fragment, whether by expanding the scope to meet the need during the design process or through field adjustment to correct errors and additional needs during construction.

	~~When~~ transportation needs ~~arise~~, planning ~~staff will~~ prioritize ~~them and present them~~ to the ~~project manager, marking the commencement of~~ [[:Category:138 Project Development Chronology\|project development]]. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.		MoDOT works closely with our customers to identify transportation needs, including those projects that help maintain our transportation systems. MoDOT works with our planning partners to help identify and prioritize the needs in each region. MoDOT then works within the current fiscal constraints to bring these needs forward into the [[:Category:138 Project Development Chronology\|project development]] process. Typically needs are assigned to Project Managers to establish a purpose and need and set the scope of work. The project manager will then assemble the core team and begin to analyze the need in search of a solution. As development proceeds, more and more aspects of the project will become apparent and the core team, acting through the project manager, will adjust the scope accordingly.

	The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.		The complete project scoping process involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting [[104.3 Timeline\|the timeline]] and delivery schedule of the project. The [[104.1 Core Team\|core team]] will use available data, meetings, field checks and [[104.8 Public Involvement in Project Scoping\|public input]] to accomplish these tasks.

	When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is ~~dependant~~ upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.		When the appropriate level of confidence in the scope has been reached there is a point of concurrence where the proposed scope is submitted for [[104.10 Management Concurrence\|management concurrence]] as to whether or not it addresses the original need. The level of concurrence sought is dependent upon the nature and complexity of the project. Right of way and construction funds, as well as the delivery date, will only be publicly committed to a project subsequent to this approval and after having gone through the project prioritization process.

	MoDOT also encourages contractor participation in cost-saving techniques. This article contains [[104.13 Construction Inspection Guidance for Sec 104\|construction inspection guidance]] for [[:Category:130 Value Engineering\|value engineering]] involving monetary incentives for contractors.		MoDOT also encourages contractor participation in cost-saving techniques. This article contains [[104.13 Construction Inspection Guidance for Sec 104\|construction inspection guidance]] for [[:Category:130 Value Engineering\|value engineering]] involving monetary incentives for contractors.

	This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].		This article also provides guidelines for [[104.4 Completion of Scoping\|completion of scoping]], [[104.5 Items to be Considered and Addressed\|items to be considered and addressed]], [[104.6 Project Scoping Checklists\|project scoping checklists]], [[104.9 Environmental Considerations\|environmental considerations]], [[104.11 Project Scoping Documentation\|project scoping documentation]] and [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|scope changes]].