AG-31ME-S-10-0004.pdf

�/��������01#2332�"34���52�26!�2�"34�!"5�72��5 !8!93/��������6�2�"��4�� �:232�"�����&���%�-��� �&���%&-%����99����� 3�! ��301;�6�����!99��� #3�!"5�6�"52�2�"3�6�"�!2"�5�2"���23�3�9262�!�2�"�

9�6!9��2#�0"�295�<�32�� =�9�6!��5�2"

6�<2�3��� ��0 "23�2">�����30<<92�3�� �3� :26�3�2"������6��509��8299�1�� �6�2:�5�!������<9!6��3<�62�2�5�2"� ��#��4�� �2���!"5�6! 2�54�2"�����

?�����!9�5����� 3�2"�� 2>2"!9�!"5�

��4�����

�� �������4��.+

A�

B

���B�, �,��������B

�*������*7 �B����������

%&����+��B�

���������������D$�'����������������D$�'����������������D$%'����������������D$

5�32>"!��5�<�2"��3$4�82��2"������2#��3<�62�2�5�2"�����36��509��

1=��������� � $�� �#�����5!����� � �6�2<��������� 3�3<�62�2�5�!1�:�4�����0 "23��!"=�� �!99�2��#3�0<�"�8�26��< 26�3�! ������ �5�!������< 26��3����<<�32����!6��2��#4�5�92:� �5�!�������

"�6�#<92!"6��82�������!1�:�4�����0"5� 32>"�5�!> ��34�2����23����� �23�!66�<��5�82��2"�EEEEEEEEEEEEEE�6!9�"5! �5!=3��('�6!9�"5! �5!=3�0"9�33�!�52��� �"��<� 2�5�23�2"3� ��5��

�$��� * �%��������'������0�����!

�� ������-��8! 5�8299�1��#!5���"���23� � #4�� ��"���!"5! 5� � #��(4�� �1=����� �!0��� 2F�5����262!9�8 2���"�"��26��

�����7��������

�&����������7

����� ����������+ 7��

�%���������&���6$���%'����������'���6$���

�**$)*+&),��&-)$.��"*/+0��1*/�2#&&!

*/� *!$$*� ����"+#0*&'� �"0/+)3*&)��4�4���

�����5������ � � !&-)$.4("*/+067-84 0-"43& %9���

C���

� �:2�03��52�2�"�23�0"03!19�

��� ��������$�11�2��+!�3.345�� � �36 21�5�1=�,����-� �$�&���%��6$��

1���

�9

�9� 9��99

���� �� 6���� ��7

;�< ;:< ;�< ;�< ;�< ;2<

���������$#+%$!.��&8"*+&)��&-$,����2���

��������� ���������������������2����

��������2�:,��$0*+)"*+&) ���������$!+&-�&@��$!@&!(")8$,�

�������!&A$8*��")"3$!� $)+&!� &@*7"!$��)3+)$$!�������������

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)3+)$$!������������������������������������9��

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

�������$8/��!+*$!��-+*&!�����������������������������������

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������9��

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!���������������������������

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,� ���������&)*+) $-�444

�<�"3� �5�1=�,��

���� �� 6���� ��7

9�����2 )8*+&)"#� '$8+"#+0*��������������������������������

��������;0$$�'"!"4��4�4�4��@&!�"�8&('#$*$�#+0*�&@ ��������!$B +!$-�0C+##0�")-�A&>�-$08!+'*+&)< ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������!"%$#���"##�*!"%$#�7+##�>$�!$+(> !0$-�+) ��������"88&!-")8$�7+*/�*/$�2$-$!"#��!"%$#��$3 #"*+&)�")- ��������'"!"��4�4�4�������!"%$#�2 )-04

���������$!+&-�&@��$!@&!(")8$,�

1������*/$!��+!$8*��&0*0�;���0<����*/+0�#+)$�+*$(�7+## ��������>$�")) "##.�@ )-$-�*&�8&%$!�*/$�8&0*�&@ ��������(+08$##")$& 0�$B +'($)*�0 8/�"0�&@@+8$�0 ''#+$0� ��������0$!%$!�'$!+'/$!"#0��8">#+)3��08"))$!0��8"($!"0�

���������$!+&-�&@��$!@&!(")8$,�

�������!&A$8*��")"3$!� $)+&!� &@*7"!$��)3+)$$!������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)3+)$$!������������������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

�������$8/��!+*$!��-+*&!����������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������� ���������&)*+) $-�444

�<�"3� �5�1=�,��

���� �� 6���� ��7

���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

9�����2 )8*+&)"#� '$8+"#+0*�������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������!"%$#���"##�*!"%$#�7+##�>$�!$+(> !0$-�+) ��������"88&!-")8$�7+*/�*/$�2$-$!"#��!"%$#��$3 #"*+&)�")- ��������'"!"��4�4�4�������!"%$#�2 )-04

���������$!+&-�&@��$!@&!(")8$,�

1������*/$!��+!$8*��&0*0�;���0<����*/+0�#+)$�+*$(�7+## ��������>$�")) "##.�@ )-$-�*&�8&%$!�*/$�8&0*�&@ ��������(+08$##")$& 0�$B +'($)*�0 8/�"0�&@@+8$�0 ''#+$0� ��������0$!%$!�'$!+'/$!"#0��8">#+)3��08"))$!0��8"($!"0� ��������$*84��; $$�'"!"3!"'/��4�4�4�<

���������$!+&-�&@��$!@&!(")8$,�

�������!&A$8*��")"3$!� $)+&!� &@*7"!$��)3+)$$!������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)3+)$$!������������������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

�������$8/��!+*$!��-+*&!����������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:��� ���������&)*+) $-�444

�<�"3� �5�1=�,��

���� �� 6���� ��7

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

9�����2 )8*+&)"#� '$8+"#+0*�������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������!"%$#���"##�*!"%$#�7+##�>$�!$+(> !0$-�+) ��������"88&!-")8$�7+*/�*/$�2$-$!"#��!"%$#��$3 #"*+&)�")- ��������'"!"��4�4�4�������!"%$#�2 )-04

���������$!+&-�&@��$!@&!(")8$,�

1������*/$!��+!$8*��&0*0�;���0<����*/+0�#+)$�+*$(�7+## ��������>$�")) "##.�@ )-$-�*&�8&%$!�*/$�8&0*�&@ ��������(+08$##")$& 0�$B +'($)*�0 8/�"0�&@@+8$�0 ''#+$0� ��������0$!%$!�'$!+'/$!"#0��8">#+)3��08"))$!0��8"($!"0� ��������$*84��; $$�'"!"3!"'/��4�4�4�<

���������$!+&-�&@��$!@&!(")8$,�

�������!&A$8*��")"3$!� $)+&!� &@*7"!$��)3+)$$!������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)3+)$$!������������������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

�������$8/��!+*$!��-+*&!����������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,� ���������&)*+) $-�444

�<�"3� �5�1=�,��

�9� � ���� �� 6���� ��7

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

9�����2 )8*+&)"#� '$8+"#+0*�������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������!"%$#���"##�*!"%$#�7+##�>$�!$+(> !0$-�+) ��������"88&!-")8$�7+*/�*/$�2$-$!"#��!"%$#��$3 #"*+&)�")- ��������'"!"��4�4�4�������!"%$#�2 )-04

���������$!+&-�&@��$!@&!(")8$,�

1������*/$!��+!$8*��&0*0�;���0<����*/+0�#+)$�+*$(�7+## ��������>$�")) "##.�@ )-$-�*&�8&%$!�*/$�8&0*�&@ ��������(+08$##")$& 0�$B +'($)*�0 8/�"0�&@@+8$�0 ''#+$0� ��������0$!%$!�'$!+'/$!"#0��8">#+)3��08"))$!0��8"($!"0� ��������$*84��; $$�'"!"3!"'/��4�4�4�<

���������$!+&-�&@��$!@&!(")8$,�

�������!&A$8*��")"3$!� $)+&!� &@*7"!$��)3+)$$!������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)3+)$$!������������������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

�������$8/��!+*$!��-+*&!����������������������������������� ���������&)*+) $-�444

�<�"3� �5�1=�,��

���� �� 6���� ��7

���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������9�� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������ .0*$(0��)"#.0*��!&3!"(($!��������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

9�����2 )8*+&)"#� '$8+"#+0*�������������������������������� ���������!&- 8*� $!%+8$��&-$,��:���

���������$!+&-�&@��$!@&!(")8$,�

������!"%$#���"##�*!"%$#�7+##�>$�!$+(> !0$-�+) ��������"88&!-")8$�7+*/�*/$�2$-$!"#��!"%$#��$3 #"*+&)�")- ��������'"!"��4�4�4�������!"%$#�2 )-04

���������$!+&-�&@��$!@&!(")8$,�

1������*/$!��+!$8*��&0*0�;���0<����*/+0�#+)$�+*$(�7+## ��������>$�")) "##.�@ )-$-�*&�8&%$!�*/$�8&0*�&@ ��������(+08$##")$& 0�$B +'($)*�0 8/�"0�&@@+8$�0 ''#+$0� ��������0$!%$!�'$!+'/$!"#0��8">#+)3��08"))$!0��8"($!"0� ��������$*84��; $$�'"!"3!"'/��4�4�4�<

���������$!+&-�&@��$!@&!(")8$,�

�<�"3� �5�1=�,��

AG-31ME-S-10-0004 8

SECTION C – STATEMENT OF WORK

USDA Rural Development Geospatial Systems and Related Applications

GENERAL

The purpose of this solicitation/contract is to obtain technical support services to provide maintenance support and enhancement development to Rural Development geospatial initiatives and related automation initiatives within Rural Development.

C.1 BACKGROUND

Rural Development currently manages a $111.3 billion dollar loan portfolio consisting of more than 644,000 loans or loan guarantees through a network of 47 State Offices and approximately 700 field service centers covering 50 States, plus the Pacific Trust Territories, Puerto Rico, and the US Virgin Islands. The rural development headquarters/National Office is located in Washington, D.C. and in St. Louis, MO.

Some rural development geospatial needs have been met with such initiatives as creating program eligibility layers and providing a service to broadband applicants to draw a map of their proposed service.

However the needs are expanding greatly with recent legislation such as the Farm Bill and the American Recovery and Reinvestment Act (ARRA). New programs have been created, many programs received substantial ARRA funding, and transparency reporting are contributing to rural development’s immediate need to expand its geospatial capabilities.

C.2 OBJECTIVE

The objective is to obtain the support services of a company with extensive knowledge of geospatial development and systems support.

C.3 SCOPE

The scope of this contract is to provide analysis, development and support for enterprise class Geospatial information management solutions. Geospatial solutions include maps, charts, and technology, global position system (GPS), geographic information system (GIS), Geospatial Service-Oriented Architecture (SOA) Development, internet based mapping solutions, mapping, geodatabases and geo-coding. The recommended skill categories required to be performed include: project manager, analysts, geospatial specialists, and other services of an architectural or engineering nature in support of the requirements identified in Section C, Statement of Work.

This effort addresses geospatial and geographic information system application services development to satisfy business requirements. It encompasses the entire range of applications development practices and lifecycle approaches, and represents an investment in the enterprise capability maturity model relative service functionality.

We have multiple tools and technologies currently being used in the support of our current geospatial initiatives including ArcGIS, ArcObjects, ArcSDE, ArcGIS Engine, ArcGIS Server, MySQL, SQL Server, Oracle, Informix, HTML, AJAX, XML, XSLT, Java, JavaScript, C/C++, C#, Python, PHP 5.0, VB.NET, VB6, VBA, KML, Google Maps Applications.

C.4 DESCRIPTION OF SERVICES

C.4.1 TASK ORDER FOR SERVICES

AG-31ME-S-10-0004 9

The services listed below are funded annually and pursuant to the availability of funds. The contractor shall provide the necessary labor, skill mix, and project management to address the requirements below as they relate to exhibit III.

C.4.1.1 SYSTEMS MAINTENANCE SUPPORT

(a) The Contractor SHALL respond to work order requests otherwise known as Requests for Automation (RFA) received by the COR or their designated representative (see Exhibit I). Work ordered on a Request for Automation (RFA) will be designated routine, emergency, major systems, and minor systems based upon the following criteria:

Routine, services required that are non-critical in nature.

Emergency system problems (system completely down).

Major system problems (more than 2 areas of system down).

Minor system problems (1 area down/system reporting inaccurately).

(b) Hourly status updates for other than routine work shall be provided to the Contracting

Officer’s Representative (COR) until the problem(s) is resolved.

(c) Contractors SHALL adhere to the following response times according to the identified level of urgency:

ROUTINE: within twenty-four (24) hours;

EMERGENCY: within two (2) hours;

MAJOR SYSTEM PROBLEMS: within four (4) hours;

MINOR SYSTEM PROBLEMS: within six (6) hours

Response time is defined as acknowledgement to the COR of receipt and agreement of information provided on the RFA. Completion of the tasks shall be as defined on the RFA.

C.4.1.2 SERVER CONFIGURATION

The Contractor shall maintain a server configuration guide for all geospatial systems on the site. Maintain and recommend adjustments to server databases as necessary and make adjustments to databases sizes and server resources to allow for additional database space as necessary.

C.4.1.3 REPORTS

The Contractor shall provide Monthly Status Reports showing a complete list of all Requests for Automation, Problem Reports and special activities including the creation of special reports or congressional inquiries completed during the month. Reports are due by the third work day of the following month.

C.4.1.4 UNSCHEDULED/EMERGENCY SOFTWARE UPDATES/MAINTENANCE

Services include unforeseen support upgrades to operating systems required by NITC/ITS, new versions of vendor software, unscheduled software enhancements to support such needs as disaster funding, and emergency software modifications as dictated by legislature, or our user community.

Priority of these efforts will be determined by the Rural Development project managers through the COTR.

Authorization will be provided by the Contracting Officer Technical Representative (COTR).

C.4.1.5 ODC/TRAVEL FUNDS

The contractor will be required to travel under this contract. Travel expenses shall be kept to a minimum

AG-31ME-S-10-0004 10

and shall be approved in advance by the COR. Lodging and per diem will be reimbursed in accordance with Federal Travel Regulations (FTR). Local travel (within a 50 mile radius of contractor's office) will not be reimbursed and should be included in the contractor’s proposal. A Travel Expense Voucher, Exhibit III shall be submitted to the COR for review and approval for each traveler no later than the 10 business days after travel is completed.

The maintenance and enhancement support of Rural Development Geospatial Systems may require the procurement of additional software applications to maintain the operational integrity of the applications and meet the user requirements in the Production environment.

Upon authorization and direction by the COR, perform market research, obtain multiple cost estimates, and procure, at the best value to the Government, new software required in the performance of this contract.

The contractor may also be required to purchase miscellaneous equipment – such as office supplies, server peripherals, cabling, scanners, cameras, etc. The original invoice for these purchases shall accompany contractor's invoice. The contractor shall not purchase any miscellaneous equipment, software, or supplies without prior approval from the COR.

Failure to obtain COR approval will result in the contractor not being reimbursed for the purchase.

Estimated travel expected will be 10 round trips annually usually from St. Louis Mo to Washington DC.

C.4.2 TASK ORDERS FOR REQUESTS FOR AUTOMATION (RFA)

The Government will issue a RFA (Exhibit I) to require the contractor to perform any of the work elements referenced below through individually funded Task Orders. The Contractor shall provide the necessary labor and skill mix and project management to satisfy all Task Order requirements.

C.4.2.1 THE TASK ORDERS MAY REQUIRE ONE OR MORE OF THE FOLLOWING

WORK ELEMENTS:

Analyze functional requirements Develop feasible solutions and plans Develop functional specifications Develop and refine Project Work Plans Develop and Confirm Project Estimates Design and Develop prototypes Conduct Joint Application Design Meetings Produce Design Specifications for Customer Signoff Identify, Build, and Test Common Components Identify Reuse Opportunities and consume Component interfaces when possible Design and Develop Web Applications Design and Develop Geospatial Web Applications Develop Data Structure Diagram (DSD) Develop/Generate Target Databases and Geo-databases Develop Geospatial Service-Oriented Architecture (SOA) Design and Develop Interfaces to Legacy Systems Tune for Performance Create Detailed Test Plans Conduct Unit, System, and Integration Testing Enhance Data Models Prepare Cutover Plans Perform Post Implementation Review

C.4.2.2 THE CONTRACTOR SHALL RESPOND TO ONE OR MORE OF THE

ELEMENTS LISTED ABOVE AS REQUIRED UNDER EACH TASK

Each Task Order may require one or more of the work elements referenced at Section C.4.2.1. The

AG-31ME-S-10-0004 11

contractor shall provide the necessary labor and skill mix and project management as required to:

Provide a recommendation prior to design and development of a solution on existing and new applications to meet user requirements. Additionally, provide GIS application development of ArcGIS extensions, and ArcServer development, deployment, and maintenance. Ability to develop functional applications from use case descriptions writes and debugs code, create application user documentation, and maintain web applications and software releases.

C.4.2.3 THE CONTRACTOR SHALL RESPOND TO EACH ORDER WITH THE

APPROPRIATE LABOR CATEGORY MIX TO SUCCESFFULLY ACCOMPLISH THE

REQUIREMENTS OF THE STATEMENT OF WORK IDENTIFIED IN EACH TASK

ORDER

Project Manager: Manage system development projects. Work with customers to understand business requirements. Coordinate activities of the project team to ensure success of systems integration projects.

Serve as single point of contact for customers for project schedules, project documentation, project activities, pricing and invoices, and other issue resolution. Develop functional requirements and create functional specifications as needed. Implement a comprehensive project methodology and operating procedure for application development projects. Perform Quality Assurance checks on project deliverables. Ensure project deadlines and milestones are met.

Systems Engineer II: Survey technical infrastructures and make recommendations regarding enterprise-wide systems and network architectures to meet organization-wide requirements. Coordinate the delivery, installation, and configuration of hardware, operating systems, software and network components for enterprise-wide systems.

Perform requirements studies for Geospatial Information Management Systems. Design and help install and configure Geospatial Information Management Systems. Provide first line of support maintenance services for Geospatial Information Management Systems including all hardware and software components.

Technical Writer: Develop user, reference and procedure manuals for computer systems. Design and maintain written style guides and templates for various documents. Assist in the development of functional specification documents. Follow a comprehensive development methodology and project practices.

Provide management reports and updates on project status.

Functional Specialist: Possess demonstrated knowledge in designated field or discipline. Possesses significant experience providing solutions to an organization’s challenges through the application of knowledge gained through similar prior engagements. Participates in the development of solutions by leveraging knowledge of the designated field or discipline. Contributes to the implementation of strategy and helps assess the impact of industry trends, policies, and/or standard methodologies. Directs the activities of other staff as necessary on activities related to the field or discipline.

Systems Analyst/Programmer II: Coordinate with internal and external customers to gain an understanding of their business requirements. Analyze and define customers’ functional requirements and create functional specifications design documents. Develop and document the technical systems design for applications. Supervise development and testing of application program modules. Develop, test, and document complex application program modules. Provide management reports and updates on project status. Install and set-up applications, tools, and project-related technologies. Perform as project team leader on system implementation projects.

Systems Analyst/Programmer I: Work with customers and project team members to understand business requirements. Assist in the development of functional requirements and creation of functional specifications. Assist in the development and documentation of technical system design for applications.

Perform logical database normalization and design. Design, develop, test, and document application program modules. Meet project deadlines for assigned tasks.

AG-31ME-S-10-0004 12

The Contractor shall provide the skilled personnel necessary to successfully meet the government’s requirements. The government reserves the right to accept or reject personnel based on individual resumes and contract requirements.

Further, the government reserves the right to review the resumes of any proposed individual for work under this contract. Should the continued assignment to this contract of any person in the Contractor's organization be deemed by the government to conflict with the interest of the government, the Contractor shall be required to remove that person from the assignment and replace him/her with an individual of comparable or better qualifications, approved by the COTR.

The Contractor and its employees shall conduct only business covered by this contract during periods paid for by the government and will not conduct any other business on government premises. Contractor personnel will abide by the normal rules and regulations applicable to the government premises on which they work, including any applicable safety and security regulations.

All staff employed by the Contractor on this contract must meet the minimum experience requirements for the appropriate skill category.

Because of the need for unique experience for this solicitation/contract, contract personnel shall have the following minimum experience: a) experience using the tool sets inherent of this solicitation/contract requirements, b) the ability to work as a team leader on separate and distinct projects at the same time, c) the ability to work on numerous projects simultaneously. The contractor shall provide courtesy copies of resumes detailing work experience and references for each employee assigned to perform on the task.

C.5 ORDERING

Work for enhancements shall be ordered using Request for Automation (RFA), Exhibit I. The form shall describe the task required and the required/estimated completion date. -The contractor has 3 business days to respond to a request for automation and reject the work requested. If the contractor objects to the work identified in the request for automation, a notice responding to the rejection shall be submitted in writing to the COR. Failure to respond to a request for automation will be considered as acceptance on behalf of the contractor. If an agreement can not be reached, the COR shall notify the Contracting Officer for resolution.

C.6 DELIVERABLES

The Contractor shall provide all deliverables as required and identified in each Task Order. Examples of possible deliverables include the following:

Work Plans White Papers Scope Documents Implementation Plans Test Plans Cost/Benefit Analyses Draft standards, processes, procedures Standard Operating Procedures

Deliverables for all task orders shall include monthly status reports that indicate a complete list of all consulting actions, problems, and activities completed during the month. The status reports are due on or before the third work day of the following month.

C.7 PERIOD OF PERFORMANCE

Base Period – 15 February 2010 thru 14 February 2011 or 12 months from the date of award.

AG-31ME-S-10-0004 13

Option Period I – 15 February 2011 thru 14 February 2012 Option Period II – 15 February 2012 thru 14 February 2013 Option Period III – 15 February 2013 thru 14 February 2014 Option Period IV – 15 February 2014 thru 14 February 2015

C.8 PLACE OF PERFORMANCE

The Contractor shall perform all work at Government facilities unless otherwise negotiated. Subject to security regulations, the Government will provide the contractor with access to the facility to perform work in accordance with this contract. The contractor’s staff shall be physically located at the USDA, Rural Development Washington DC office and at the St. Louis metropolitan office to ensure immediate on-site response is available as necessary for provided services. The exact location will be identified at the Task Order level.

C.9 HOURS OF WORK

The hours of work shall be Monday through Friday, between 7 a.m. and 5 p.m., excluding Federal Holidays and closings, unless otherwise noted in the task order. Hours may need to be adjusted on occasion to provide specific support coverage, as needed, to address major system/application releases and/or other pressing contingencies.

C.10 KEY PERSONNEL

See paragraph H.4 (Key Personnel).

C.12 GOVERNMENT FURNISHED PROPERTY

Each contractor will be provided with a desk and chair, telephone, and a desktop computer with all necessary software and development tools to include: ArcGIS, ArcObjects, ArcSDE, ArcGIS Engine, ArcGIS Server, MySQL, SQL Server, Oracle, Informix, HTML, AJAX, XML, XSLT, Java, JavaScript, C/C++, C#, Python, PHP 5.0, VB.NET, VB6, VBA, KML and any others necessary to perform the tasks included in this contract. All work to be performed on site that requires access to the Rural Development and USDA networks must be accessed from a government furnished computer. A fax machine, printers, and copiers will be provided to be used in support of their assigned tasks subject to FAR 52.245-1 (Government Property).

C.14 PAYMENT PROCEDURES

a. Invoices: The Contractor shall submit an invoice monthly for services provided during the month. Invoices may be submitted electronically to the CO. The offeror shall include the payment address in their proposal, if it is different from that shown for the Offeror IAW paragraph G.2, INVOICE

AND PAYMENT PROVISIONS.

b. Travel expenses/cost shall be reported on the Travel Expense Voucher, Attachment J2.

Receipts for expenses, e.g., tickets, hotel lodging, etc. shall be attached thereto. Travel cost shall be cost reimbursable for actual cost, not exceeding the limitations set forth in the Federal Travel Regulations

(FTR).

c. The Contractor will be authorized under this contract to purchase miscellaneous equipment, supplies, postage, and commercial software as required and approved by the COR. The General & Administrative Fee on purchases for this contract shall be considered as an ODC. The Government will reimburse the contractor for these purchases. The original invoice for these purchases shall accompany contractor’s invoice. Contractors shall not purchase any miscellaneous items without prior approval from the COR/COTR. Failure to obtain the COR’s/COTR’s approval will result in the contractor not being reimbursed for the purchase.

AG-31ME-S-10-0004 14

d. To assist the USDA, Rural Development in making timely payments the invoice shall include at a minimum:

i. Name and address of the Contractor (mailing address for check)

ii. Contract Number; Purchase Order Number; Task Order Number

iii. Invoice Number, date and Vendor Express Number (VXP), if any

iv. Total amount due under the Invoice

v. Total amount per contract line item by ordering entity

C.15 SECURITY REQUIREMENTS

The Contractor shall provide personnel who already have a current National Agency Check with Inquiries Credit (NACIC) background investigation. U.S. citizenship or Permanent Resident status shall be required for all personnel working on-site.

C.15.1 BACKGROUND INVESTIGATION REQUIREMENTS

Prior to beginning any work on this contract, all identified Contractor employee(s) shall undergo a security screening. All Contractor employees are, at a minimum, subject to a minimum background investigation (MBI) conducted by the Government. Security clearances above the MBI may be required at the specific TO level. Contractor employees who undergo Minimum Background Investigation checks which reveal the following may be unacceptable under this contract: conviction of a felony, a crime of violence or a serious misdemeanor, or a record of arrests for continuing offenses. Should the results of any background investigation included any of the above items, the Contractor shall agree to remove the person assigned within one business day of official notification by the Government and provide a replacement within ten business days. New hires or substitution of personnel are subject to the Minimum Background Investigation requirement.

a. The software systems under this contract may contain financial data subject to privacy laws and regulations. The Contractor shall be responsible for assuring that all personnel having access to Privacy Act data have a Minimum Background Investigation security clearance prior to access to the data. This includes personnel and technicians on or off-site in which access to the data is possible. Individuals with security clearances shall be responsible for ensuring that sensitive data is not transmitted to unauthorized parties.

b. Immediately upon contract award, the Contractor shall identify to the FEDSIM COR those individuals who have been cleared in accordance with security requirements identified in section C.15.1. The Government will provide the necessary background investigation request forms required for each individual identified for clearance. The forms required are:

1. Fingerprint Chart (2 sets required)

2. SF-171, Personal Qualifications Statement or a Resume

3. OF 306 – Declaration for Federal Employment

4. Fair Credit Reporting Release Form

Online access to SF-85P, Questionnaire for Public Trust Positions, will be provided by the Government when the FEDSIM COR provides the appropriate request to this office.

c. All forms must be typed, or printed neatly in ink. Once the required documents have been completed, including the online SF-85P, the applicant must take the package to the location specified in the particular task order. The applicant will be required to setup an appointment to ensure the proper individual is available to receive the completed package. TWO FORMS OF

IDENTIFICATION (SOURCE DOCUMENTS) WILL BE REQUIRED FOR VERIFICATION

PURPOSES.

AG-31ME-S-10-0004 15

If requested, the Contractor will make any appropriate corrections, and return the corrected forms within 3 working days after the request is received.

The contractor is responsible for all costs associated with obtaining background investigations and fingerprints. The estimated cost for performance of a background investigation will be supplied with the particular task order.

ii. Background investigations conducted by other Federal Government Agencies may be accepted.

The Contractor must provide proof of an acceptable background investigation to Rural Development Servicing Personnel Office. Determination of acceptability is at the discretion of Rural Development.

iii. The Government has the right to perform periodic on-site inspections of Contractor operations to ensure compliance with information protection requirements outlined in Federal Government regulations.

iv. The RD reserves the right, at anytime, to require replacement of Contractor personnel, if the individual does not meet the security requirements.

v. Prior to starting contractual work affected by the Privacy Act, the Contractor is responsible for providing proof of background clearance or submitting all required documents as identified in

(B) above to the Rural Development Servicing Personnel Office for all affected personnel.

C.16 FACILITY ACCESS REQUIREMENTS

Daily access to facilities will be required when performing work under this contract. Specific processes for obtaining required badges for Contractor personnel are discussed below. Contractor personnel who do not routinely work on the Government site and do not have a Contractor badge shall coordinate with the USDA CR prior to attending onsite meetings at USDA facilities. The following Government specific Agency security requirements must be followed to obtain facility access and obtain a Building Pass:

a. The Contractor shall ensure that each Contractor employee has been issued either a temporary or permanent badge (“badge”) from the Government. The Government may issue temporary or visitor badges for Contractor employees who are identified as having an infrequent or temporary legitimate business need for access to the Government site. The badge will serve to authorize the wearer to enter and leave the security area. The badge must be worn so as to be clearly visible at all time when on the work site. The badge will be retained by the individual as long as he is required continued admittance to the site.

b. Each Contractor employee shall be subject to Federal laws applicable to Government installations, e.g., a ticket issued by the Federal Protective Officers and possible tow-away of vehicle.

c. The Government reserves the right to exclude or remove from the site or building any employee of the

Contractor or Sub-Contractor whose background investigation indicates an undesirable history as discussed in Section 7.4 Security Requirements.

d. When the Government directs, the Contractor shall remove from performance on the contract any person who is identified as a potential threat to the health, safety, security, general well being, or operational mission of the USDA and its population.

C.17 REMOTE NETWORK ACCESS REQUIREMENTS

The Contractor shall comply with the USDA Office of the Chief Information Officer - Information Technology Network Access Security Policy:

AG-31ME-S-10-0004 16

a. All remote access will be through a virtual private network (VPN).

b. To protect against loss or theft, sensitive data stored on a laptop should be encrypted. The documents folder is encrypted on USDA issued laptops.

c. It is not normal policy to store sensitive date on portable computers. If the data is being accessed from a system that is secured, then the data should remain on that protected system.

d. Also when transmitting sensitive information through email it should be win-zipped and password protected.

e. If data is compromised, the Contractor shall comply with guidance provided in the Security Incident

Guide (Refer to List of Attachments, Attachment F).

C.18 HSPD-12 SECURITY OPERATING PROCEDURES

The Contractor shall comply with agency personal identity verification procedures identified in the contract that implement Homeland Security Presidential Directive - 12 (HSPD-12), Office of Management and Budget (OMB) guidance M-05-24, and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

The Contractor shall insert this clause in all subcontracts when the subcontractor is required to have physical access to a federally controlled facility or access to a Federal information system.

C.19 PHYSICAL SECURITY

The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of this contract. The Contractor shall implement procedures to ensure that appropriate administrative, technical, and physical safeguards are established to ensure the security and confidentiality of sensitive government information, data, and/or equipment. The Contractor’s procedures shall be consistent with Government and GSA policies, including GSA Order 2100.1, Information Technology Security Policy (or most current version), OMB Memorandums & Circulars, FISMA, the Computer Security Act of 1987, and the Privacy Act. In addition, during all activities and operations on Government premises the Contractor shall comply with the policies, rules, procedures and regulations governing the conduct of personnel or protection of Government facilities and data as expressed by GSA, written or oral.

C.20 SENSITIVE INFORMATION STORAGE AND DISCLOSURE

Sensitive But Unclassified (SBU) information, data, and/or equipment shall only be disclosed to authorized personnel on a Need-To-Know basis. The Contractor shall ensure that appropriate administrative, technical, and physical safeguards are established to ensure the security and confidentiality of this information, data, and/or equipment is properly protected. When no longer required, this information, data, and/or equipment shall be returned to the Government. The Government will determine the destiny of such information, data, and/or equipment. If the Government determines that such information, data, and/or equipment is to be destroyed, the destruction shall be accomplished by burning; shredding, or any other method that precludes the reconstruction of the material but only after direction by the Government. All sensitive information contained on Contractor computers shall be either degaussed or shall use the NIST 800-88 (Guidelines for Media Sanitization) but only after coordination with the Government.

C.21 PROTECTION OF INFORMATION

The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of work under this contract. The Contractor shall also protect all Government data, equipment, etc.

by treating the information as sensitive. All information about the systems gathered or created under this task order should be considered as SBU information. It is anticipated that this information will be gathered, created and stored within the primary work location. If Contractor personnel must remove any information from the primary work area they shall protect it to the same extent they would their proprietary data and/or company trade secrets. The use of any information that is subject to the Privacy Act will be utilized in full

AG-31ME-S-10-0004 17

accordance with all rules of conduct as applicable to Privacy Act Information.

C.22 UNAUTHORIZED REPRODUCTION

All files, records, papers, or machine-readable materials created or revised using equipment or materials provided under this contract are the property of the United States Government. The Contractor shall not replicate or reproduce information unless specifically approved in writing by the Contracting Officer or the COR. The Contractor shall adhere to all rules, regulations, and procedures relating to security and confidentiality for work performed and any information handled in the course of this work.

C.23 COMPLIANCE WITH SOFTWARE LICENSES AND PROCEDURES

If Contractor-furnished equipment and material are used, the Contractor shall be responsible for ensuring that only commercial, duly licensed software is used. Under no circumstances may "bootleg”, "pirated," or other unofficial copies of software be installed on equipment. Within one working day of any written request from the GSA Contracting Officer, the Contractor shall furnish proof of legitimate purchase, or license, of the software used.

C.24 INTELLECTUAL PROPERTY RIGHTS

The existence of any patent, patent application or other intellectual property right that encumbers any deliverable shall be disclosed in writing in the cover letter that accompanies the delivery. If no such disclosures are provided, it is assumed that the no intellectual property rights apply.

C.25 CERTIFICATION AND ACCREDITATION (C&A)

The contractor shall comply with Rural Development System Development Life Cycle process to include but not limited to change control and system development procedures.

https://rd.sc.egov.usda.gov/teamrd/rdom/cio/dcio/mass/pmo/Systems%20Development%20Life%20Cycle/ Forms/AllItems.aspx

C.26 DISASTER RECOVERY PLANNING

The Contractor may be required to work in the arena of disaster recovery and continuity of operation.

These duties include complying with NIST 800-34 Contingency Planning Guide for Information Technology Systems, USDA departmental manual (DM 3570-001 Disaster Recovery and Business Resumption Plans) and RD or other USDA Agency recovery plans for application/system recovery. This includes, but is not limited to the development of application recovery steps; testing, validating, reviewing recovered applications; and maintaining RD or other USDA Agency applications in the event of a disaster.

Disaster and recovery of applications processes will be implemented in the event of actual emergencies, i.e.

tornados, terrorist attacks, etc. or in simulations; i.e. exercises (tabletops or functional). Personnel assigned these duties will be listed on a call tree with the potential to be called 24/7.

C.27 LOGICAL ACCESS CONTROL

Prior to accessing USDA information systems Contractor personnel shall review and acknowledge the "User Agreement/Rules of Behavior" and the “Acceptable Use Policy”. Once all the RD or other USDA Agency required logical access documents and handbooks have been reviewed Contractor personnel shall sign the User agreement and have the form filed with the COR.

C.28 INCIDENT RESPONSE

A security incident is classified as any event that violates laws, regulations or security policies. Contractors and Contractor Partners shall comply and respond in accordance with the USDA Incident Response Procedures DM3505-01.

AG-31ME-S-10-0004 18

C.29 COMPUTER SECURITY AWARENESS TRAINING

Prior to accessing USDA information systems Contract personnel shall ensure that the annual Security Awareness Training has been completed or is scheduled to be completed. If applicable, it may be required for Contractor personnel to complete specialized training. This training will be completed on an annual basis if required.

C.30 COMPLIANCE WITH SECURE CODING

The contractor shall be responsible for verifying that all members of the developer team have been successfully trained in secure programming techniques. Pre-contract award, the Vendor shall document the process including training courses that their application developers have taken prior to developing applications. Pre-contract award, the Vendor shall certify to the Purchaser that only application developers who have received appropriate level of formal training on secure application development and passed a competency test proving mastery of the techniques needed to find and eliminate the Top 25 Most Dangerous Security Errors (published at http://cwe.mitre.org/top25/) shall be involved in the developing or testing code under the Contract.

Prior to delivery of any software provided under this contract, Vendor shall test the software source code using a static testing program and perform a dynamic vulnerability test looking for the presence of any of the Top 25 Most Dangerous Security Errors (published at http://cwe.mitre.org/top25/) and provide the results of the test in writing with a summary showing how many of those errors were found. Vendor agrees that if any such errors are found, vendor is responsible for correcting them prior to delivery or to pay for a third party chosen by the government, to correct the flaws.

Federal Desktop Core Configuration (FDCC) Compliance

Reference OMB Memorandum and the FAR

For all software developed and/or delivered under this contract (termed “the software,” that will or can reasonably be expected to operate on computers using Microsoft Windows operating system, the provider certifies that;

a) The software is fully functional and operates correctly as intended on systems using the Federal Desktop Core Configuration (FDCC).

b) The standard installation, operation, maintenance, update, and/or patching of the software will not alter the configuration settings from the approved FDCC configuration.

c) The software, if designed for normal end users, shall run in the standard user context without elevated system administration privileges."

The provider further agrees that, in the event the software is found to be in conflict with the provider’s certifications, that the provider will correct the discrepancy within seven days of receiving written or electronic notice of the discrepancy, or will pay the cost of having a third party selected by the government correct the discrepancy.C.331 Network Access Security Policy

a. General Policy Statement (1). This policy establishes requirements for the secure access and transmission of data on all

USDA Office of the Chief Information Officer (OCIO), Information Technology Services (ITS) networks to prevent unauthorized use or misuse of Federal Government information.

b. Policy Detail

These standards shall be followed:

AG-31ME-S-10-0004 19

(1). External Connections:

(a). All servers, network devices, or appliances hosting information or resources accessed from the Internet shall be placed in a protected web farm which is separated from the internet and separated from the OCIO-ITS network by a firewall.

(b). Firewalls, Intrusion Detection and Prevention Systems and router-based controls, including Access Control Lists (ACL), shall be used to control, restrict, and monitor all network traffic to and from the OCIO-ITS networks.

(c). All network traffic between OCIO-ITS locations shall be transported on dedicated OCIO-ITS owned circuits or through a Virtual Private Network (VPN) connection meeting encryption levels set by OCIO-ITS security policies.

(d). No OCIO-ITS office shall have Internet connectivity through any service provider other than the connectivity provided by OCIO-ITS network operations.

(2). Warning Banners

(a). The following Warning Banner will appear prior to system/network logon in order to provide fair notice regarding proper use to all devices attempting to access OCIO- ITS systems and networks

(b). Warning Banner:

Unauthorized access to this United States Government Computer System and software is prohibited by Title 18, United States Code 1030. This statute states that:

Whoever knowingly, or intentionally accesses a computer without authorization or exceeds authorized access, and by means of such conduct, obtains, alters, damages, destroys, or discloses information or prevents authorized use of (data or a computer owned by or operated for) the Government of the United States shall be punished by a fine under this title or imprisonment for not more than 10 years, or both.

All activities on this system and network may be monitored, intercepted, recorded, read, copied, or captured in any manner and disclosed in any manner, by authorized personnel. THERE IS NO RIGHT OF PRIVACY IN THIS SYSTEM. System personnel may give to law enforcement officials any potential evidence of crime found on USDA computer systems. USE OF THIS SYSTEM BY ANY USER, AUTHORIZED OR UNAUTHORIZED, CONSTITUTES CONSENT TO THIS

MONITORING, INTERCEPTION, RECORDING, READING, COPYING OR

CAPTURING AND DISCLOSURE. REPORT UNAUTHORIZED USE TO AN

INFORMATION SYSTEMS SECURITY OFFICER.

(3). Remote Access

(a). General Access

1. Remote telecommunication access to Government computers presents special security concerns. A combination of physical controls, unique user identifiers, passwords, terminal identifiers, access control software, and strict adherence to security procedures is required to protect the information from unauthorized access.

2. Government-owned computer equipment, software, and communications are required for remote interaction to an OCIO-ITS network or computer system;

i.e. direct interface to a system.

3. Business partners accessing via remote connection to OCIO-ITS network or computer system must have authorization and approval from OCIO-ITS ISSPM.

AG-31ME-S-10-0004 20

4. Remote access privileges to any OCIO-ITS network shall meet USDA remote access and approval guidelines as described in DM3525-003: Telework & Remote Access Security, Part 3 or its replacement.

5. All connectivity established shall be based on the principle of least access in accordance with the approved business requirements and security review.

6. All remote access connections shall comply with OCIO-ITS Security Policy Manual Chapter Three: Authorization and Access Control…