Difference between revisions of "Help Article"
m (→EPG Approval Process: Updated Engineering Policy Revision Request Form link) |
|||
| Line 62: | Line 62: | ||
==EPG Approval Process== | ==EPG Approval Process== | ||
| − | Revisions to engineering policy are proposed using the [ | + | Revisions to engineering policy are proposed using the [https://modotgov.sharepoint.com/sites/DE/Lists/EPGResponse/NewForm.aspx?ID=1 Engineering Policy Revision Request Form]. Revisions to forms used in the EPG are also proposed by using the Engineering Policy Revision Request Form. |
'''Any other standard affected by a proposed EPG revision?''' | '''Any other standard affected by a proposed EPG revision?''' | ||
Revision as of 08:57, 8 November 2021
| Engineering Policy Revision Request Form |
| Form to Propose Level 1, 2 and 3 Revisions for the EPG and other MoDOT Standards |
The Engineering Policy Guide (EPG) contains MoDOT policy, procedure and guidance for the planning, design, construction and maintenance of roadway and related facilities. It also includes specific technical topics of right of way, bridge, traffic and materials. These articles are numbered to reflect as closely as possible the pay items and divisions from Missouri Standard Specifications for Highway Construction.
The EPG is not a contract document and EPG articles are referenced as EPG XXX.X or "articles" - not "sections" - to avoid confusion with MoDOT specifications. Where a conflict exists between the EPG and a contract, the contract document rules. References and links to the Missouri Standard Specifications are given as "Sec XXX.XX" or "Section XXX.XX of the Standard Specifications." References and links to the Missouri Standard Plans for Highway Construction are "Standard Plan XXX.XX".
Contents
Organization
Articles are grouped into the specification book’s divisions (for example, the EPG articles in EPG 100 General mirror Division 100 specifications, articles in EPG 300 Bases mirror Division 300 specifications, etc.). Many articles have been subdivided into additional articles. For example, the reader may notice that EPG 903.6 Warning Signs and other EPG 903 articles are listed at the bottom of EPG 903 Highway Signing.
While every effort has been made to base the article numbers on MoDOT pay items and specifications, not all articles in the EPG are reflected in the pay items and specifications. For example, many EPG “100 General” articles are important to the design and construction of roadway facilities but do not directly correspond to specific pay items. Some of these are:
Similar examples are to be found in the EPG 200, EPG 300, etc. articles.
How best to view the articles
The articles are best viewed on your computer monitor with the following settings:
| 17-in. Monitors: | ||||
| Wide Screen Monitors: |
How to Easily Select and Print an Entire Article or a Portion of an Article
- 1) Highlight the selected article or portion of article
- 2) Click “File”
- 3) Click “Print Preview”
- 4) Select “As selected on screen”
- 5) Should your selection include a large table or figure that creates an undesirable appearance, you may want to click the “Shrink To Fit” tab and perhaps select “85%”.
- 6) Print the selection.
EPG Approval Process
Revisions to engineering policy are proposed using the Engineering Policy Revision Request Form. Revisions to forms used in the EPG are also proposed by using the Engineering Policy Revision Request Form.
Any other standard affected by a proposed EPG revision?
Provide electronic files of all the revisions to other MoDOT standards (other EPG articles, any Standard Plans, specifications, JSPs, etc.) impacted by the EPG proposal. Word files in revision mode are required for textual changes. Dgn files are preferred for Standard Plan revisions although a redlined hard copy showing the proposed changes is also acceptable.
Completing the Engineering Policy Revision Request Form
Every submittal must document, along with the actual proposed textual revision to the EPG:
- Contact. The name of the sponsor from within the division proposing the revision is required. The contact is the person most knowledgeable or central to the proposal.
- Summarize. Provide the reason why the idea should be carried out (why it is necessary or its benefit). This justification may be critical in the decision to approve the proposal or not.
- Fiscal Impact. Provide a dollar estimate for the proposal’s costs or savings to MoDOT. Include necessary calculations (initial savings or life cycle savings, for example) or assertions to accurately convey the proposal’s financial impact. The fiscal impact must be a numeric dollar value.
- External Involvement. Provide a summary of efforts undertaken during the development of the item to engage affected industry groups and the FHWA. Provide specific examples of who was involved and how the involvement occurred. This is not applicable to every submittal, but is critical for the determination of the associated approval level for borderline items.
The Engineering Policy Revision Request Form also requires the date, issue name and a listing of all affected publications. (For instance, should a proposal for EPG 606.1 also require revisions to Sec 606 and Std. Plan 606.30, the section and standard plan as well as their proposed revisions would be specified along with the proposed revisions to the EPG article.)
It is also optional to enter information about whether the proposal involves an Administrative Rule or LPA guidance, the submitter's tracking number (if any) and the submitter's desired effective letting date.
After the proposed EPG revision is submitted
Submittals are evaluated and processed on a quarterly schedule. Final decisions on proposed ballots are submitted to the Policy and Innovations Engineer for disposition. The Assistant Chief Engineer submits the final decision on Level 2 revisions and the Chief Engineer submits the final decision on Level 3 revisions. Proposed revisions will be categorized by the Policy and Innovations Engineer based on the following guidelines:
| Tips on Text |
| While Engineering Policy Services edits all submittals, a few grammatical guidelines for the EPG include: |
| Assure/Ensure/Insure: The word “assure” is a personal guarantee based on reputation. “Ensure” is used when the party is to make certain of something or to be careful. “Insure” refers to actions protected by insurance, and indicates that money is involved. |
| Dimensions: Typically use “high”, “wide” and “long” instead of “in height”, “in width” and “in length”. |
| Farther/Further: Use “farther” to express a physical distance, such as 10 miles farther, and “further” for a non-physical dimension, such as further thought. |
| Fewer/less: Use “few” or “fewer” for something comprised of a small number of countable components (such as fewer dollars, fewer gallons of water, etc.). Use “less” for amounts that are not being counted (less money, less water, etc.). |
| Gender: Minimize the use of “he/she”, “he and she” and “she or he”. |
| High/Tall: Use “high” to express a lofty position, such as the clouds are high. Use “tall” to express a great vertical dimension, such as the tall post. |
| Until: Do not use "til". |
Level 1 Approval. If, upon submittal in the Engineering Policy Revision Request Form, a proposed revision is determined to be a routine technical matter, an errata correction or a clarification, it can be approved by the Policy and Innovations Engineer without comment from the district engineers, the division engineers or the Chief Engineer. The EPG will be revised as necessary.
Level 2 Approval. If, upon submittal in the Engineering Policy Revision Request Form, a proposed revision is determined to be a moderate technical change, if it requires specific expertise (e.g. structural design, etc.) or if it impacts more than one division, the proposal is processed as a Level 2 Ballot item. The District Engineers and Division Directors/Engineers are provided 10 business days to provide their comments to the Assistant Chief Engineer who will consider the idea before providing a decision to the Policy and Innovations Engineer. The Federal Highway Administration is given 10 working days to provide comment or concurrence with the Policy and Innovations Engineer. Upon approval any associated documents and the EPG will be revised as necessary.
Level 3 Approval. If, upon submittal in the Engineering Policy Revision Request Form, a proposed revision is determined to be a complex technical change, contentious, has high cost or impacts MoDOT's external conduct of business, the proposal is processed as a Level 3 Ballot item. The District Engineers and select Division Directors/Engineers are provided 10 business days to provide their comments to the Chief Engineer who will consider the idea before providing their decision to the Policy and Innovations Engineer. The Federal Highway Administration is provided 10 business days to provide comment or concur with the proposal. Upon approval, any associated documents and the EPG will be revised as necessary.
Changes to the Standard Specification, Standard Drawings, Pay Items and significant changes to JSPs are documented by Design Standards Letters and posted both internally and externally.
EPG Ballot Cycles
.
| 2022 Engineering Policy Services Ballot Schedule | ||||
|---|---|---|---|---|
| Engineering Policy Revision Requests Due to CO Engineering Policy Services | Ballot Items Due to Asst. Chief Engineer | Ballot Items Due to FHWA | Publish Revisions | Effective Date |
| June 21, 2021 | June 25, 2021 | June 25, 2021 | July 19, 2021 | October 1, 2021 |
| September 17, 2021 | September 24, 2021 | September 24, 2021 | October 18, 2021 | January 1, 2022 |
| December 17, 2021 | December 24, 2021 | December 24, 2021 | January 18, 2022 | April 1, 2022 |
| March 18, 2022 | March 25, 2022 | March 25, 2022 | April 18, 2022 | July 1, 2022 |
| June 17, 2022 | June 24, 2022 | June 24, 2022 | July 18, 2022 | October 1, 2022 |
| September 16, 2022 | September 23, 2022 | September 23, 2022 | October 17, 2022 | January 1, 2023 |
Division Contacts
Since the divisions provide authoritative input, consulting with their liaisons or contacts may provide the help you require or receive your input. Below is a listing of divisional personnel with whom the Engineering Policy staff works and who may be helpful to you:
- Bridge: Darren Kemna
- Chief Counsel's Office: Terri Parker
- Construction and Materials:
- Chemical Laboratory: Todd Bennett
- Construction Engineering: Dennis Brucks, Randy Hitt, John Donahue
- Geotechnical Engineering: Lydia Brownell
- Physical Laboratory: Brett Trautman
- Design: Shelie Daniel, Tim Schroeder, Dave Simmons
- Bid & Contract Services: Danica Stovall-Taylor
- CADD Services: Steve Atkinson
- Environmental Compliance: Melissa Scheperle
- Historic Preservation: Mike Meinkoth
- LPA: Laura Ellen
- Right of Way: Mendy Sundermeyer, Greg Wood
- Highway Safety & Traffic: Lisa Vieth
- Safety Engineering: Ray Shank
- Signals: Ashley Buechter, Lisa Vieth
- Signs: Tom Honich, Cayci Reinkemeyer
- Work Zones: Dan Smith
- Maintenance: Paul Denkler
- Multimodal: Michelle Kratzer, Jenni Hosey
- Aviation: Amy Ludwig
- Freight & Waterways: Cheryl Ball
- Railroads: Troy Hughes
- Transit: Joni Roeseler
- Planning: Eric Curtit
FHWA Contacts
Below is a listing of FHWA personnel with whom the Engineering Policy staff works and who may be helpful to you:
- ADA: Lauren Paulwell
- Bridge: Scott Stotlemeyer
- Construction and Materials: Dawn Perkins
- Design: Brian Nevins, Kevin Irving (KC & NW), Felix Gonzalez (NE & SE), Dawn Perkins (SL), Charles Pursley (CD & SW)
- Environmental: Raegan Ball and Taylor Peters
- Pavements: Mike McGee
- Right of Way: Michael Latuszek
- Safety and Traffic Control: John Miller
- Transportation and Planning: Brad McMahon and Steven Minor
