html5-img
1 / 25

NSSP Guidance for the 2010 Standards

NSSP Guidance for the 2010 Standards. 2010 Concept for Specification Format. A section in the 2010 Standards is assigned to the same subject matter regardless of whether the verbiage is a standard specification, a revised standard specification (RSS), or a special provision (SSP or NSSP).

kishi
Download Presentation

NSSP Guidance for the 2010 Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NSSP Guidance for the 2010 Standards

  2. 2010 Concept for Specification Format A section in the 2010 Standards is assigned to the same subject matter regardless of whether the verbiage is a standard specification, a revised standard specification (RSS), or a special provision (SSP or NSSP). (Note: You cannot have a special provision for a section if the section does not exist in the Standard Specifications.) Example: Section 48-2.01C(2) is assigned to falsework shop drawings. The following is a portion of this section in the Standard Specifications:

  3. 2010 Concept for Specification Format (cont.) The following is an RSS for section 48-2.01C(2): The following is the SSP for section 48-2.01C(2):

  4. Terms in this Document introduction: The statement that deletes, replaces, or adds the verbiage that follows to a section. A special provision can have more than one introduction. (See the Specification Style Guide for more details.) NSSP: Nonstandard special provision as defined in section 6.9 of the RTL Guide. reserved section: Section 1-1.01 states, “Sections are reserved in the Standard Specifications for correlation of special provisions and revised standard specifications with the Standard Specifications and for future expansion of the Standard Specifications.” section: Any section in the Standard Specifications, RSSs, or special provisions. A section can be on outline levels 1 through 6 (e.g., 12, 12-3, 12-3.17)

  5. Excerpt from the Specification Style Guide: • “For an NSSP, follow the guidance for an SSP (delete, replace, or add to a standard specification section). If the NSSP does not delete, replace, or add to a section, add the NSSP after the last number in a section and use the section number one level higher than the added section for the NSSP introduction.”

  6. Steps for NSSP Development Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity.

  7. Steps for NSSP Development (cont.) Example: The subject is MBGR. Therefore, section 83-1.02B is the correct section. Section 83-1.02A is the general section that applies to this section. The following is a portion of section 83-1.02A of the Standard Specifications.

  8. Steps for NSSP Development (cont.) NSSP verbiage is added to the SSP for section 83-1.02B as shown below. The general section that applies (i.e., section 83-1.02A) states to galvanize steel parts and hardware under section 75-1.05. If a requirement in ASTM A 1057 conflicts with section 75-1.05, then the NSSP must clarify the ambiguity.

  9. Steps for NSSP Development (cont.) Adding the verbiage “The 5th paragraph of section 83-1.02A does not apply.” to the NSSP clarifies the ambiguity. Note: In this example, we want the steel parts and hardware to be galvanized under ASTM A 1057 and we do not want section 75-1.05 to apply. If the intent was to have portions of section 75-1.05 apply in addition to ASTM A 1057, then we would have had to specify this in the NSSP.

  10. Steps for NSSP Development (cont.) Another option to clarify the ambiguity is to create an NSSP for section 83-1.02A and include an introduction to delete the 5th paragraph of that section, but this option is not recommended because by doing this, all other railings need not be galvanized. Note: Be careful when using an introduction to delete verbiage from the Standard Specifications because a deletion applies to the whole Contract, including any cross-references made to the section. In this example, the deletion of this paragraph affects all railings because this verbiage is in the general section.

  11. Steps for NSSP Development (cont.) Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. Use the 2010 SSP index to check if a section has an SSP assigned. --If the section has an assigned SSP, you must use another section for your subject.

  12. Steps for NSSP Development (cont.) Example: Section 57-2.04 is a reserved section in the Standard Specifications: However, section 57-2.04 already has an SSP assigned, as shown below: Therefore, use another section for your subject.

  13. Steps for NSSP Development (cont.) Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. Use the 2010 SSP index to check if a section has an SSP assigned. --If the section has an assigned SSP, you must use another section for your subject. --If the section does not have an SSP, create an NSSP document with the following file naming convention: <section no.>_Nmm-dd-yy.docx.

  14. Steps for NSSP Development (cont.) Example: Section 80-4 is a reserved section in the Standard Specifications: Section 80-4 does not have an SSP assigned, therefore, this section can be used for your subject. Use the naming convention: <section no.>_Nmm-dd-yy.docx.

  15. Steps for NSSP Development (cont.) Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. --If the section has an assigned SSP, you must use another section for your subject. --If the section does not have an SSP, create an NSSP document with the following file naming convention: <section no.>_Nmm-dd-yy.docx. Check if verbiage needs to be deleted in the Standard Specifications. If so, create an introduction to cover this.

  16. Steps for NSSP Development (cont.) Example: Introduction to delete verbiage from the Standard Specifications.

  17. Steps for NSSP Development (cont.) • Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. • 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. • --If the section has an assigned SSP, you must use another section for your subject. • --If the section does not have an SSP, create an NSSP document with the following file naming convention: <section no.>_Nmm-dd-yy.docx. • Check if verbiage needs to be deleted in the Standard Specifications. If so, create an introduction to cover this. • Check if the NSSP verbiage replaces verbiage in the Standard Specifications. If so, create an introduction in the NSSP to cover this. Insert the NSSP verbiage underneath the introduction.

  18. Steps for NSSP Development (cont.) Example: The 2nd paragraph of section 12-3.12C of the Standard Specifications: Introduction in the SSP to replace verbiage in the Standard Specifications: NSSP verbiage

  19. Steps for NSSP Development (cont.) • Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. • 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. • --If the section has an assigned SSP, you must use another section for your subject. • --If the section does not have an SSP, create an NSSP document with the following file naming convention: <section no.>_Nmm-dd-yy.docx. • Check if verbiage needs to be deleted in the Standard Specifications. If so, create an introduction to cover this. • Check if the NSSP verbiage replaces verbiage in the Standard Specifications. If so, create an introduction in the NSSP to cover this. Insert the NSSP verbiage underneath the introduction. • If the NSSP verbiage adds verbiage to a section of the Standard Specifications, create an introduction in the NSSP to cover this. Insert the NSSP verbiage underneath the introduction.

  20. Steps for NSSP Development (cont.) Example: Introduction to add verbiage in the Standard Specifications. NSSP verbiage Note: In this example, use the existing introduction in the SSP and put NSSP verbiage underneath it.

  21. Steps for NSSP Development (cont.) • Determine which section the NSSP belongs in. The general section applies to the NSSP. Make sure the NSSP does not contain a specification that makes any general specification ambiguous. If it does, add a clause to the NSSP to clarify the ambiguity. • 2. You may use a reserved section (e.g., 83-2.02G Reserved) for an NSSP, but check to make sure the section does not already have an SSP assigned to it. • --If the section has an assigned SSP, you must use another section for your subject. • --If the section does not have an SSP, create an NSSP document with the following file naming convention: <section no.>_Nmm-dd-yy.docx. • Check if verbiage needs to be deleted in the Standard Specifications. If so, create an introduction to cover this. • Check if the NSSP verbiage replaces verbiage in the Standard Specifications. If so, create an introduction in the NSSP to cover this. Insert the NSSP verbiage underneath the introduction. • If the NSSP verbiage adds verbiage to a section of the Standard Specifications, create an introduction in the NSSP to cover this. Insert the NSSP verbiage underneath the introduction. • If the NSSP does not revise a section (i.e., the section does not exist in the Standard Specifications), add the NSSP after the last number in the section. The introduction for the NSSP needs to reference the section number one outline level higher than the added section.

  22. Steps for NSSP Development (cont.) Example: Section 12-3.17 in the Standard Specifications is the last section in section 12-3: An NSSP for portable radar trailer would be part of section 12-3 since it is a device for traffic handling. Since this NSSP does not have a dedicated section within section 12-3, assign the number after the last number in that section (i.e., 12-3.18), as follows: Section 12-3 is the section number one outline level higher than section 12-3.18.

  23. Rules for NSSP Development Comply with the Specification Style Guide. Do not rely on the governing ranking of Contract parts (i.e., hierarchy) as specified in section 5-1.02. Example: Let’s go back to the example for section 12-3.12C. This is a portion of section 12-3.12C of the Standard Specifications:

  24. Rules for NSSP Development (cont.) Incorrect NSSP development: Adding the verbiage (in blue) below to section 12-3.12C would be a conflict with the 2nd paragraph of section 12-3.12C of the Standard Specifications:

  25. Rules for NSSP Development (cont.) Correct NSSP development: Replacing the 2nd paragraph of section 12-3.12C of the Standard Specifications with the NSSP verbiage (in blue) below is correct.

More Related