104.11 Project Scoping Documentation - Revision history

Hallej1: add SAFER tool

2022-07-06T15:10:36Z

add SAFER tool

← Older revision		Revision as of 10:10, 6 July 2022
Line 6:		Line 6:
	\|-		\|-
	\|[[media:104.11 Completed SIMS form 2012 secure.pdf\|completed SIMS form]]		\|[[media:104.11 Completed SIMS form 2012 secure.pdf\|completed SIMS form]]
			\|-
			\|[[media:SAFER_Document.pdf\|SAFER tool]]
	\|}		\|}

Smithk: Updated figure for security

2021-03-01T20:28:51Z

Updated figure for security

← Older revision		Revision as of 15:28, 1 March 2021
Line 5:		Line 5:
	\|[http://stipprod/stip/tp1000cw SIMS form]		\|[http://stipprod/stip/tp1000cw SIMS form]
	\|-		\|-
	\|[[media:104.11 Completed SIMS form 2012.pdf\|completed SIMS form]]		\|[[media:104.11 Completed SIMS form 2012 secure.pdf\|completed SIMS form]]
	\|}		\|}

	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 2012.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 2012 secure.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

	Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Design Liaison Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.		Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Design Liaison Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

Smithk at 18:54, 5 December 2018

2018-12-05T18:54:27Z

← Older revision		Revision as of 13:54, 5 December 2018
Line 8:		Line 8:
	\|}		\|}

	~~[[image:104.11.jpg\|left\|250px]]~~
	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 2012.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 2012.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

Smithk: Updated completed SIMS form

2012-10-18T19:18:39Z

Updated completed SIMS form

← Older revision		Revision as of 14:18, 18 October 2012
Line 5:		Line 5:
	\|[http://stipprod/stip/tp1000cw SIMS form]		\|[http://stipprod/stip/tp1000cw SIMS form]
	\|-		\|-
	\|[[media:104.11 Completed SIMS form ~~887~~.pdf\|completed SIMS form]]		\|[[media:104.11 Completed SIMS form 2012.pdf\|completed SIMS form]]
	\|}		\|}

	[[image:104.11.jpg\|left\|250px]]		[[image:104.11.jpg\|left\|250px]]
	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form ~~887~~.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 2012.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

	Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Design Liaison Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.		Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Design Liaison Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

Smithk: Per Design, updated title

2012-04-19T13:57:46Z

Per Design, updated title

← Older revision		Revision as of 08:57, 19 April 2012
Line 11:		Line 11:
	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

	Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the ~~Technical Support~~ Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.		Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Design Liaison Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

	Projects that are classified as Major Projects or are funded from statewide funds will require the additional approval of Transportation Planning before the funds are added to the STIP.		Projects that are classified as Major Projects or are funded from statewide funds will require the additional approval of Transportation Planning before the funds are added to the STIP.

Smithk: minor clarification to differentiate EPG articles (that are referenced as "articles", not "sections") from specifications (that are referenced as "sections")

2010-03-31T14:04:01Z

minor clarification to differentiate EPG articles (that are referenced as "articles", not "sections") from specifications (that are referenced as "sections")

← Older revision		Revision as of 09:04, 31 March 2010
Line 9:		Line 9:

	[[image:104.11.jpg\|left\|250px]]		[[image:104.11.jpg\|left\|250px]]
	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|104.12, Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|EG 104.12 Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

	Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Technical Support Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.		Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Technical Support Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

Smithk: updated SIMS link

2009-07-07T18:14:42Z

updated SIMS link

← Older revision		Revision as of 13:14, 7 July 2009
Line 3:		Line 3:
	\|'''Figures'''		\|'''Figures'''
	\|-		\|-
	\|[http://~~aixwas1~~/stip/tp1000cw SIMS form]		\|[http://stipprod/stip/tp1000cw SIMS form]
	\|-		\|-
	\|[[media:104.11 Completed SIMS form 887.pdf\|completed SIMS form]]		\|[[media:104.11 Completed SIMS form 887.pdf\|completed SIMS form]]
Line 9:		Line 9:

	[[image:104.11.jpg\|left\|250px]]		[[image:104.11.jpg\|left\|250px]]
	Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|104.12, Scope Changes]]. The [http://~~aixwas1~~/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.		Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf\|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)\|104.12, Scope Changes]]. The [http://stipprod/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

	Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Technical Support Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.		Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Technical Support Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

Smithk: minor clarifications from Planning about SIMS approval and a newer SIMS example

2008-01-18T15:30:07Z

minor clarifications from Planning about SIMS approval and a newer SIMS example

New page

{|style="padding: 0.3em; margin-left:15px; border:1px solid #a9a9a9; text-align:center; font-size: 95%; background:#f5f5f5" width="160px" align="right"
|-
|'''Figures'''
|-
|[http://aixwas1/stip/tp1000cw SIMS form]
|-
|[[media:104.11 Completed SIMS form 887.pdf|completed SIMS form]]
|}

[[image:104.11.jpg|left|250px]]
Documentation of the recommended solution to a given need and the concurrence of MoDOT management in the project’s scope is documented through [[media:104.11 Completed SIMS form 887.pdf|a completed SIMS form]]. Subsequent changes to the project scope and/or estimate must be documented and approved through the project scope change process discussed in [[104.12 Scope Changes (Scope, Estimate or Fiscal Year)|104.12, Scope Changes]]. The [http://aixwas1/stip/tp1000cw SIMS form] submitted for the inclusion of any right of way funds or construction funds in the STIP must contain a detailed description of the recommended solution to a given need. A box is included on the SIMS form that will allow the project manager to include project specific details about the proposed solution. The details of the project’s scope, any reasons needed to support the choice of those details and the project’s budget and delivery schedule must be included on the SIMS form.

Once the SIMS form is submitted to Transportation Planning for approval and subsequent inclusion in the STIP, an automatically generated email will be sent to the District Engineer (or designee) for approval, and to the Technical Support Engineer and district planners for informational purposes. After considering the various input received, the District Engineer (or designee) will either log into SIMS and approve the change electronically or will email a reply to all concurring with the project’s scope.

Projects that are classified as Major Projects or are funded from statewide funds will require the additional approval of Transportation Planning before the funds are added to the STIP.

If the District Engineer and/or Transportation Planning, as applicable, do not concur with the project’s scope, the SIMS form will not be accepted and the project will require more discussion by the District Engineer and/or Transportation Planning.

Should the District Engineer choose to respond by email, the district planner will scan the email and uploaded them to SIMS. Once that email is uploaded, Transportation Planning will approve or reject the project scope in SIMS on behalf of the District Engineer.

[[category:104_Scope]]