TWIN_VALLEY_IDA_Comment_Matrix_(003).pdf

COMMENTS MATRIX FOR NRCS-NM ISSUANCES: USDA-NRCS TWIN VALLEY (IDA) SITE VISIT 08/30/2016

(Please read instructions on back before completing form.)

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/ R/ P

SD FORM 818, JAN 09 PREVIOUS EDITION IS OBSOLETE

Bidder Comment: Does any part of the packet have to be mailed e.g. is a copy of the bid bond in PDF adequate?

Resolution: No, the entire bid packet needs to be submitted by email to steven.alves@wdc.usda.gov

Bidder Comment:: What is the extent of the tree removal on the Monson Property?

Resolution: All the trees within the property/easement boundary with the exceptions of the Aspen Areas shown on page 13 of 20 in the Scott Monson plan, shall be removed, ground, mulched, chopped or burned as described in the specifications. When the work is complete. The only trees standing will be in the Aspen areas and the rest of the site will be left in a condition suitable for mowing and haying.

pg 12 of 20, 3rd bullet under the Tree Removal/Brush Control: states—Tree Removal/brush management shall be considered successfully completed when al trees, brush, and stumpage are removed to ground level

Bidder Comment: Who is responsible for staking out the property for work limits and construction? NRCS can provide the contractor with GIS/GPS surfaces and points

Resolution: The NRCS inspector or COR will stake out the work limits prior to construction start, if staking or flagging is destroyed or removed by the contractor during construction. The Contractor is responsible for re-staking/reflagging.

Govt Comment: solicitation to be amended for different grass types.

Resolution: see amendment 0001 revised plans

Bidder Comment:

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/

Resolution:

INSTRUCTIONS FOR COMPLETING SD FORM 818

COORDINATING OSD COMPONENT: Use this form to provide consolidated critical and substantive comments to the OSD Component that originated the issuance. Complete the classification header and footer, columns 1 through 5, and the first two entries in column 6. REVIEW THE COMMENTS, RESOLVE ANY CONFLICTING VIEWS, AND CONFIRM THAT THE COMPLETED MATRIX ACCURATELY REPRESENTS YOUR COMPONENT’S POSITION. Upload the form to the DoD Directives Program Portal IN MICROSOFT WORD FORMAT, with a scanned copy of the sign SD Form 106, “DoD Directives Program Coordination Record,” or coordination memorandum.

ORIGINATING OSD COMPONENT: Use this form to consolidate comments from all coordinators and to record adjudication of the comments. (To add comments from an SD 818 submitted by a coordinator, use the “Copy” and “Paste” tools on the Microsoft Word Standard Toolbar.) When consolidating comments, place them in the order of the pages/paragraphs they apply to (e.g., all comments from all coordinators that apply to page 1, paragraph 1.a., should be grouped together as the initial entries; all comments that apply to page 1, paragraph 1.b., should be grouped together next, and so on). Complete column 7 and the third entry in column 6. Adjust the classification header and footer and columns 1 and 2 as appropriate.

CLASSIFICATION – Enter the highest classification of the comments. If all are unclassified, mark the header and footer accordingly and ignore the column.

COLUMN 1 – Enter the number of the comment. Enter comments in the order of the pages/paragraphs they apply to.

COLUMN 2 – Enter the classification of the comment. If all comments are unclassified, mark the header and footer accordingly and ignore the column.

COLUMN 3 – Enter the appropriate information.

COLUMN 4 – Enter the appropriate information.

COLUMN 5 – Enter the appropriate information.

COLUMN 6 – Enter the comment type. Place only one comment per row. Do NOT include administrative comments concerning non-substantive aspects of an issuance, such as dates of references, organizational symbols, and/or grammatical errors.

(C) CRITICAL: When a Component has one or more critical comments, that Component’s coordination shall reflect a nonconcur. THE JUSTIFICATION FOR CRITICAL COMMENTS

MUST IDENTIFY:

– Violations of the law or contradictions of Executive Branch policy or of policy established in DoD issuances. The GC, DoD, or his or her representative shall identify legal objections as critical comments.

– Unnecessary risks to safety, life, limb, or DoD materiel; waste or abuse of DoD appropriations; or imposition of an unreasonable burden on a Component’s resources.

(S) SUBSTANTIVE: Substantive comments are made when a section in the issuance appears to be or is potentially unnecessary, incorrect, misleading, confusing, or inconsistent with other sections, or when a Component disagrees with the proposed responsibilities, requirements, and/or procedures. A substantive comment is usually not sufficient justification for a Component to nonconcur on an issuance. Several substantive comments when taken together may be grounds for a nonconcurrence.

COLUMN 7 – COORDINATING COMPONENT: Enter the comment in the area provided. Enter your justification for the comment and your requested or recommended changes in the area provided.

YOU MUST PROVIDE CONVINCING SUPPORT FOR CRITICAL COMMENTS IN THE JUSTIFICATION.

– ORIGINATING COMPONENT: Enter your justification for disposition of the comment in the area provided. Include any related communications with the coordinating Component. You must provide convincing support for rejecting critical comments.

COLUMN 8 – Enter whether you accepted (A), rejected (R), or partially accepted (P) the comment. Your justification for disposition of the comment in column 6 must be consistent with this entry.

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/