Solicitation TIRNO-09-R-00012_Amendment 0001.doc

SOLICITATION NUMBER: TIRNO-09-R-00012

AMENDMENT NUMBER: 0001

1. SECTION B.1 – GENERAL (Ref # 4) This section has been amended to reflect the 10 year period of performance.

2.

SECTION B.2 - CONTRACT PRINCIPAL TASK (Ref # 12) ** For proposal preparation, see Section J, Attachment J.5, Labor Categories and Hours, for specific hours, and Section J, Attachment J.1.1 for sample pricing schedules. Fixed fee will be used for evaluation purposes only and may be set at the contract level. Fee and profit will be negotiated at the task order level. If a fixed fee is proposed for evaluation purposes and agreed to in a resulting contract, it will serve as a reference point and may be negotiated up or down prior to final issuance of the task order depending upon the complexity of the requirement. The offeror shall also provide a detailed cost breakdown for the base and all option years in accordance with the cost instructions in Section L.

3.

SECTION B.2.1 - LABOR CATEGORY RATE TABLE (Ref #’s 23; 24) and

SECTION C.9 – TASK ORDER LABOR CATEGORY DESCRIPTIONS

(Ref #’s 40; 45; 56; 58; 63; 68; 79)

(a) The table and description list has been amended to include a labor category for Junior IT Administrative Specialist.

(b) The labor category descriptions for IT Specialist, Junior IT Specialist, Senior IT Specialist, Senior IT Technician, Senior Business Process Reengineering Specialist, and Business Process Reengineering Specialist have been amended to reflect differentiating qualifications and responsibilities.

(c) The labor category for Information Engineer has been amended as follows;

Establishes and satisfies complex system-wide information security and non security requirements based upon the analysis of user, policy, regulatory, and resource demands. Supports customers at the highest levels in the development and implementation of doctrine and policies. Provides leadership and guidance in the development, design and application of solutions implemented by more junior staff members. Coordinates with senior representatives within the customer organizations to establish and define programs, resources and risks. Applies expertise to government and commercial common user systems, as well as to dedicated special purpose systems requiring specialized security features and procedures. Examples could include classified intelligence, access control, biometrics, intrusion detection, and command and control-related networks and smart card technologies. Provides guidance and direction to other professionals, acts in a consulting and/or advisory capacity; coordinates resolution of highly complex problems and tasks, possesses ability to meet and operate under deadlines.

4.

C.7 - CORPORATE LEVEL MANAGEMENT (Ref #’s 37; 54)

G.9 - KEY PERSONNEL (Ref #’s 94)

L.12.4.2 – KEY PERSONNEL (Ref # 72) The offeror shall submit corporate level (contract level) key personnel résumés only.

5.

Section F.8 - TIPSS-4 TASK ORDER (TO) STATUS REPORTS (Ref #’s 87; 92)

The references have been amended to reflect the correct subparagraphs as follows:

(a) TIPSS-4 requires standard Task Order Status Reports for all task orders administered by the IRS. The type of status report may vary by the type of task order issued. The status report type will be identified upon task order award. The TO Status Report shall be at the task order level unless a lower Work Breakdown Structure (WBS) level of reporting is explicitly required and stated in the Task Order RTCP. Subparagraphs F.8.1 and F.8.2 describe the types of reports required for each task order type.

6. Section F.5 - DELIVERABLES (Ref # 88) Subparagraph (b) has been amended to read:

(b) For purposes of delivery, all deliverables shall be made by 4:00 p.m. local time (Washington, DC) at destination, Monday through Friday, unless stated otherwise in the task order.

7. Section F.4 - SUBMISSION OF CORPORATE REPORTS (Ref # 91) This section has been amended to reflect calendar and not federal business days.

8. Section H.4 – EARNED VALUE MANAGEMENT (EVM) COMPLIANCE

(Ref #’s 102; 103)

(a) Subcontractors will certify that its system is compliant with EVMS. The prime and subcontractor EVM systems are different. In accordance with FAR Part 34.201 (d) EVMS requirements will be applied to subcontractors using the same rules as applied to the prime contractor.

(b) The Department of Treasury Guide and IRS Policy & Procedure 34.2 have been included in Section J (See J.13 and J.13.1).

9.

Section H.25 – ACCESS TO GOVERNMENT PROPERTIES AND FACILITIES

(Ref # 106)

This section has been amended to reflect that up to two contract-level key management personnel with be given access badges.

10. Section H.2 – INFORMATION TECHNOLOGY ACCESSIBILITY SECTION 508

(Ref #’s 111; 112)

(a) This section has been amended to reflect the correct attachment. See below:

In accordance with 36 CFR 1194, Subpart D, the electronic information technology (EIT) products and product support services furnished in performance of this contract shall be documented to indicate the current conformance level with Section 508 of the Rehabilitation Act of 1973, per the 1998 Amendments, and the Architectural and Transportation Barriers Compliance Board’s Electronic and Information Technology Accessibility Standards. At no time during the performance of the award shall the level of conformance go below the level of conformance in place at the time of award. At no additional cost, the contractor shall provide information, documentation, and support relative to the supplies and services as described in Section J, Attachment 7. The contractor shall maintain this detailed listing of compliant products for the full contract term, including all forms of extensions, and shall ensure that it is current within five calendar days after award and within three calendar days of changes in products being utilized as follows.

(b) The standards and clauses referenced in Section H.2 through H.4 will be checked at the task order level.

11.

H.29 - HISTORICALLY BLACK COLLEGES/UNIVERSITIES (HBCUs)/MINORITY INSTITUTIONS (MIs) (Ref # 123) See amended text below:

Contractors are encouraged to establish and maintain an agreement (i.e., a teaming or subcontracting arrangement) with HBCUs and MIs throughout the life of the contract. If contractors have existing arrangements with HBCUs/MIs, then as long as those arrangements cover the minimum requirements addressed in J.11, the existing arrangement will be accepted. Contractors are encouraged to use various HBCUs and MIs when developing solutions in response to customer requirements. The CO will perform an annual review of each contractor’s agreement(s) with HBCUs and MIs. If there is a change in the agreement(s) for any reason, the contractor shall notify the CO by providing a copy of the new agreement within 30 days of such change.

12.

H-31 – LIMITATIONS ON SUBCONTRACTING PLANS (Ref #105) This section has been amended to state that FAR clause 52.219 only applies to HUBZone Small Business firms bidding as prime contractors under the ITS RFP and electing the Price Evaluation Preference for evaluation purposes.

13.

J-5 – LABOR CATEGORIES AND HOURS

(Ref #’s 131; 136; 138; 140; 142; 143; 148; 151; 152; 153; 158; 160; 166; 169; 175; 178; 183; 184; 191)

This attachment has been removed and replaced with the following spreadsheet J.5 ITS.xls. This spreadsheet contains a complete listing of labor categories and hours for the base year and all option years. Please be advised that the labor hours are estimates for pricing evaluation purposes only. The Government does not guarantee they will order labor hours in the amounts stated in the spreadsheet J.5 ITS.xls.

14.

J.6 - IRS CAPABILITY MATURITY MODEL (CMMI®) REQUIREMENTS

(Ref # 171)

In section J.6.2 - DATA SUBMISSION REQUIREMENTS, the statement has been amended to read, " The appraisal(s) submitted shall be dated within the 36 months from the first day of the on-site period to the proposal due date."

15.

J.15 - REQUEST FOR PROPOSAL QUESTIONS AND COMMENTS

(Ref # 132) This section has been amended to reflect the correct attachment - Attachment J.15 ITS.xls.

16.

J.11 - HBCUs/MIs (SECTION H.29) (Ref #’s 162 ; 163 ; 164)

(a) The text that reads: “Is company a separate entity or division?” has been removed from this section.

(b) The numbering scheme in this section has been amended.

(c) The questions referenced in Section J.11; e thru r refers to HBCUs.

17.

Section J.13 THE DEPARTMENT OF TREASURY EARNED VALUE MANAGEMENT GUIDE VERSION 2.0

This attachment is added to the solicitation.

18.

Section J.14 NATIONAL DEFENSE INDUSTRIAL ASSOCIATION (NDIA) EARNED

VALUE MANAGEMENT SYSTEMS INTENT GUIDE

This attachment is added to the solicitation.

19.

L.12.4.2 – TAB B – KEY PERSONNEL (SUB -FACTOR 2)

(Ref #’s 223; 224)

a. The individual whose résumé is being submitted does have to sign their own résumé. “Higher Authority” would be anyone who is above the individual listed in the résumé, i.e. the individual's first or second line supervisor. In cases where the CEO/Owner is listed as Key Personnel another company official such as the CIO or CFO may sign. “Corporate Level” refers to the key personnel listed in the résumé.

b. It was not the intent of the Government to have the résumé requirements vary between the ITS and SB solicitations. This section has been amended.

20.

L.21 - RETURN OF OFFERS & Standard Form (SF) #33

(Ref #’s 228; 304; 318; 322; 324)

(a) The proposal due date and time has been revised – September 10, 2009; 2:00PM EST.

(b) The acceptance period is 240 days. The SF 33 had been amended to reflect this omission.

21.

L.11.4.2 - IRSAP 1052.239-9004 INSTRUCTIONS TO OFFERORS – SOFTWARE DEVELOPMENT PREREQUISITE (Jan 2007)

(Ref #’s 256; 273)

(a) If an appraisal team member does not have a copy of the appropriate certificate, the offeror can use the release in Attachment J.6.1 to give permission to SEI to validate the training requirement for the team.

(b) The statement for section L.11.4.2.f has been amended to read, "Project profile(s) for each project evaluated in the SCAMPI(s), ARC Class A, including the following attributes: project description, application domain, software size, life cycle, project schedule, current phase of the project, and staffing profile;"

22.

L.12.5

– EARNED VALUE MANAGEMENT SYSTEm (FACTOR 4)

(Ref # 262) The Department of Treasury Guide has set thresholds to assist each offeror’s understanding at which criterion it will be able to meet (Full or Core).

23.

L.9.1 - INSTRUCTIONS FOR PROPOSAL SUBMISSION

(Ref # 325) This section has been amended to state “envelopes” instead of “folders”.

24.

L.9.2 - FORMAT, ORGANIZATION, AND CONTENT OF FILES

(Ref # 327) This section has been amended to the state the following:

Each volume shall be submitted in separate loose-leaf binder(s). For each proposal package, the following information must be cited on the outside of each box and on the spine and cover of each binder:

· Solicitation Number:

· Offeror's Name

· Box __ of __ boxes (Applicable only to the shipping boxes)

· Volume Number (Applicable only to the spine and cover of each binder.)

Each proposal volume shall include an index of that volume's contents that identifies major paragraphs and subparagraphs by number and descriptive title, as well as the corresponding page numbers. Each section’s title must correspond with the title given by the Government.

25.

L.13.2 - TAB B – eSRS DOCUMENTATION (FACTOR 2, SUB-FACTOR 4)

(Ref #’s 328; 345; 347) The section has been amended to state “Sub-factor 4” instead of “Sub-factor 2”.

26.

M.4 - EVALUATION CRITERIA

Factor 3 Management Approach, Sub-factor1: Organizational Structure: The second sentence has been amended to read, “Additionally, the Government will evaluate the offeror’s subcontract management plan to determine the offeror’s ability to meet solicitation requirements.”

PAGE