SRCSGT | D | Farm Loan Program Information Delivery System (FLPIDS)

FBO DAILY ISSUE OF JULY 16, 2011 FBO #3521
SOURCES SOUGHT

D -- Farm Loan Program Information Delivery System (FLPIDS)

Notice Date: 7/14/2011
Notice Type: Sources Sought
NAICS: 541512 — Computer Systems Design Services
Contracting Office: Department of Agriculture, Farm Service Agency, Acquisition Management Division, Contracts Operations Branch, 1280 Maryland Avenue, SW, Portals Bldg., Room 508A, Washington, District of Columbia, 20250-0567
ZIP Code: 20250-0567
Solicitation Number: AG-3151-SS-11-FarmLoanProgramInformationDeliverySystem
Archive Date: 8/21/2011
Point of Contact: Jeffrey McRae, Phone: 2026904030, Billy Rowland, Phone: 202 720 9356
E-Mail Address: Jeffrey.Mcrae@wdc.usda.gov, billy.rowland@wdc.usda.gov
(Jeffrey.Mcrae@wdc.usda.gov, billy.rowland@wdc.usda.gov)
Small Business Set-Aside: N/A
Description: **This is a Sources Sought for SBA Certified Small Disadvantaged Businesses** Please respond with your corporate capabilities and any other relevant information that would allow USDA to determine your ability to perform the following type of requirement. C.1.1 Introduction and Background C.1.2. Introduction The Information Technology Division is responsible for the design and maintenance of information technology (IT) requirements to support the Farm Loan Program Information Delivery System (FLPIDS). The Farm Service Agency (FSA) of the U.S. Department of Agriculture (USDA) seeks a qualified contractor to develop and implement the next phases of the Direct Loan System (DLS) which is a component of FLPIDS. In addition, support is required to maintain other existing FLPIDS applications including the Farm Loan Program Risk Assessment (FLPRA) system and the Electronic Debt and Loan Restructuring System (eDALR$). C.1.3. Background As part of the Farm Service Agency's (FSA) vision to expand economic opportunity through innovation and promote agriculture production sustainability, Farm Loan Programs (FLP) provides direct and guaranteed loans to farmers and ranchers who cannot obtain financing through conventional lending institutions. To provide these programs most efficiently, the FLPIDS modernization effort wa initiated in 2003 to streamline and modernize FLP's inefficient, duplicative, and paper-based loan making and loan servicing processes and systems and support the United States Department of Agriculture's (USDA) Strategic Plan by deploying solutions that are customer focused, collaborative and results oriented. By reengineering redundant processes, centralizing and integrating data, and leveraging modern technology, FLPIDS will significantly enhance Service Centers' ability to provide customer focused program delivery with timely accurate loan closing, real-time payoff amounts and distressed borrower account assistance. The reengineering of FLP systems and migration off of the legacy systems has been on-going for several years. A majority of the functions related to direct loan making, loan servicing, farm business planning business processes and functions related to quality control assessment have already been reengineered and migrated to the web environment. The National Internal Review (NIR) system has been replaced by the reengineered Farm Loan Programs Risk Assessment (FLPRA) system. This system pulls data from other FLP applications and generates various management reports used to identify high risk lending States. Once a service center is reviewed and scored, the data is entered at the State level and the system tracks the scores assigned to Service Centers. Objective: Tasks under this PWS shall include limited FLPRA support encompassing modification to formulas, calculations, data-sharing between systems and maintenance. Components of the DLS include Loan Making (LM) Loan Servicing (LS), Specialized Servicing (SS), Customer Management (CM), Customer Profile (CP) and Transfers and Assumptions (T&A). DLS was implemented nationwide on May 7, 2007 with the LM component. The Phase II Part III of Loan Servicing requirements which include Customer History (CH) and Debt Restructure (DR) (a ten state pilot) is scheduled for implementation in September, 2011. Tasks under this PWS shall include development, testing, documentation, implementation and maintenance support of all functionality identified in the base and each option year of the contract. The Electronic Debt and Loan Restructuring System (eDALR$) is part of the FLPIDSinitiative. The eDALR$ application uses existing business services to retrieve and utilize data created by other FLPIDS and non-FLPIDS applications to accomplish its business processes. eDALR$ is an Intranet web-based program developed to assist authorized agency officials in determining and evaluating the effects of primary loan servicing in accordance with FSA Handbook 5-FLP. The eDALR$ completes a series of complex mathematical calculations based on information regarding the borrower's cash flow and loan status. This information is used to restructure the borrower's debt and maximize their repayment ability, while avoiding or minimizing loss to the Government. USDA e-Authentication (e-Auth) is the system used by USDA agencies to enable customers to obtain accounts that will allow them to access USDA Web applications and services via the Internet. This includes things such as submitting forms electronically, completing surveys online, and checking the status of your USDA accounts. The e-Auth is also the authentication method used to access FLPIDS applications by authorized users. Extensible Authorization Service (EAS) is used for implementing role based privileges in FLPIDS applications. All applications delivered by the Contractor must implement e-Auth and EAS to authenticate and apply role based privileges. C.1.4. Government Computing Environment The National Information Technology Center (NITC) in Kansas City, Missouri, provides mainframe and open systems platform services to USDA and other Federal Departments. The USDA environment is made up of two IBM z/10 model 2097-700's running the integrated facility for Linux (IFL) and one IBM z/10 model 2097-406 for general purpose processing. These platforms are divided into two (2) distinct logical partitions (LPARs) running z/OS 1.9 and ten (10) LINUX partitions running z/VM V5.4. Web Sphere, Web Server, and traditional processing are supported in this processing environment. Supporting peripheral equipment includes approximately 725 terabytes of multi-tier, enterprise-class disk on multiple, heterogeneous disk subsystems, and approximately 12 petabytes of physical and virtual tape volumes hosted across multiple automated physical and virtual tape libraries. NITC supports database management systems as follows: • IDMS Release 17 (service pack 17.1) • DB2 version 9 • Oracle RDBMS Oracle11iG Enterprise Edition Release - 11.2.0.1.0 (64 bit) • The screen interface access package is CICS Trans Action Server 2.2 • IBM's TCP/IP data communications protocol is used as the link between CICS and the databases • SQL Server 2005 and SQL Server 2008 The USDA's web farm currently supports Java and.Net applications. The Java applications are hosted on IBM WebSphere version 6 servers and the.Net applications are hosted on Microsoft IIS servers. The web farm's database environment currently utilizes SQL Server 2008 R2 on Intel based Windows servers for OLTP processes and Oracle 11g Solaris servers for OLAP/DSS processes. The USDA e-Authentication Service (E-Auth) provides authentication and authorization services for USDA Web-based applications. Authentication confirms a person's identity, based on the reliability of his or her credential. USDA agencies use the USDA E-Auth Service to implement authentication for all Web-based applications. Authentication is the process for confirming a person's identity, while authorization is the process for identifying the person's user permissions. The USDA E-Auth Service addresses coarse-grained authorization services based on user attributes and roles stored in the USDA E-Auth Service (e.g., the user is authorized to access the application if "agency = FNS"). Fine-grained authorization for web applications, usually business-specific information, should utilize the Extensible Authorization Service (EAS) provided by the USDA/FSA/ADPO. For Web applications, EAS is intended to work in concert with E-Auth to provide a comprehensive authentication/authorization solution. EAS provides the mapping from authenticated principals (provided by e-Authentication) to enterprise application roles and attribute data (provided by EAS). Applications can then take advantage of this mapping to make authorization decisions. Government standards for application security, privacy, accessibility and application auditing are detailed in Information Bulletins (Ibs), Departmental Memorandums (Memo), and legislative regulations. Applications hosted on the USDA/FSA web farm shall meet or exceed the standards defined by the Government. These include but are not limited to: • IB-0145 - Shared Service Standards • IB-0144 - Logging and Exception Handling Standards • IB-0143 - Change Management Process Improvements • IB-0141 - Application Diagnostic Standards • IB-0132 - JavaScript Usage • IB-0130 - Web Application Security Standards • IB-0121 - Stored Procedure Guideline • IB-137 - Reference Architecture 3.1 • Memorandum - Secure Coding Requirements • Memorandum - Implementation of Commonly Accepted Security Configurations for Windows Operating Systems. • Regulation - Section 508 Amendment to the Rehabilitation Act of 1973 C.1.5. Objectives The purpose of the ensuing contract is to continue streamlining and modernizing the FSA FLP inefficient, duplicative and paper-based loan making and loan servicing processes and systems and support the USDA Information Technology Strategic Plan by deploying solutions that are customer focused, collaborative and results oriented. FLPIDS sub systems within the scope of this PWS are: • Direct Loan System (DLS) o DLS when used in this document refers to both Loan Making and Loan ServicingElectronic Debt and Loan Restructuring System (eDALR$) • Farm Loan Program Risk Assessment (FLPRA) • FLPIDS Operation Data Store (ODS) The specific program objectives are described below: (1). Compliance with Federal Requirements: The contractor shall ensure that all software deliverables will comply with all relevant USDA and FSA government requirements including Enterprise Architecture, security, privacy, disaster recovery and others as stipulated in this document. (2). Leverage Modern Technology: The contractor shall leverage modern technology to reengineer existing COBOL legacy processes. Through this effort, the FLPIDS will significantly enhance the Service Centers, Finance Office and National Offices ability to provide customer focused program delivery with timely accurate customer service. (3). Requirements Analysis: The contractor shall perform all tasks necessary to review and complete analysis of the Requirements documents and functions of the legacy system as well as eliciting requirements from the business sponsors. The following activities are included: • Communicating with customers and users to determine what their requirements are. • Analyze requirements and provide developers and all other stakeholders with a clear understanding of the requirements. Requirements might be documented in various forms such as use cases, storyboards or requirements definitions. (4). Software Design Documents: The contractor shall create and maintain both a High Level Design Document (HLDD) and a Low Level Design Document (LLDD) also referred to as the "detailed" design. Included are: • Data Design - structures that reside within the software, attributes and relationships between data structures • Architecture Design - information flow and data flow diagrams • Interface Design - describe internal and external program interfaces • Procedural Design - structured programming concepts using graphical, tabular and textual notations. (5). Software Deliverables: The contractor shall describe their methodology and process to ensure that all software developed is efficient, of high quality and adequately tested. The contractor shall ensure that all software code developed is compliant with current and future FSA standards as published on the FSA SDLC website and in FSA Information Bulletins unless a waiver approved by the appropriate FSA leadership is completed. The development of FLPIDS will be implemented in phases or releases. The contractor shall formulate an optimal, low-risk incremental implementation plan, offering milestone-based demonstrable deliverables for each phase. The contractor shall demonstrate how it would implement (deliver, integrate and deploy) the configured solution. (6). Security: The contractor shall describe their methodology and process to ensure that all software developed is free of security vulnerabilities. Contractor shall ensure that all staff members contributing software code to the final software system are familiar with the security vulnerabilities identified in the OWASP top 10, SANS/MITRE CWE top 25 lists, and how to avoid exposing these vulnerabilities in the software code that they produce. References: *OWASP Top 10: http://www.owasp.org/index.php/OWASP_Top_Ten_Project * SANS/MITRE CWE Top 25: http://cwe.mitre.org/top25/index.html (7). 508 Compliance: In 1998 the US Congress amended the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities. Section 508 was enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals. The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. Under Section 508 must give disabled employees and members of the public access to information that is comparable to the access available to others. All services and products, to include systems and applications, developed and provided in response to the requirements identified in this document shall comply with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), and the Architectural and Transportation Barriers Compliance Board Electronic and IT (EIT) Accessibility Standards (36 CFR part 1194). Reference: Section 508 - http://www.ocio.usda.gov/508/index.html (8). Effective Performance Measurement: Effective Performance Measurement shall be put in place for segmental implementation phases, upgrades to system development life cycle, using industry best practices such as Work Breakdown Structure (WBS), Earned Value Management (EVM) and others. The contractor shall propose well-defined performance metrics and measurement methodology for supporting a performance-based contract structure which allows disincentives against milestone-based deliverables. Metrics will be used to measure and track schedules, budgets, defects, quality, earned value, cost to completion and risks, and to ensure that the end products satisfy the performance objectives. (9). Effective Project Management: The contractor shall provide effective management of the project schedule, performance, risks, warranties and data to produce upgraded FLPIDS systems that satisfy all functionality requirements. The contractor's proposal shall describe a proven, repeatable project management process that offers: a. Integrated Master Plan or Integrated Master Schedule, with clear milestones, which provide accurate and timely schedule and performance throughout the life cycle of the program. b. Project management by a certified Project Management Professional (PMP) c. Effective risk management system that mitigates program risks and provides for special emphasis on software development efforts through integration of metrics to monitor program status. d. Active participation by contractor's senior management in project administration and problem solving. e. Communications and change management processes that involve all key stakeholders. f. Sufficient rights for FSA in technical data and software such that FSA can maintain and modify the system using its personnel. g. Documented procedure for estimating costs and schedules to ensure consistency h. Well-established entry and exit criteria for each task (10). Knowledge Transfer: The contractor shall properly document delivered artifacts and openly engage in the Transfer of Knowledge to the government in all phases of the SDLC as defined in applicable CLIN's. (11). Training and C&A: The contractor shall develop training materials, work aids, and other support tools, and create Marketing Clip's for end-users and other stakeholders, throughout the life of the project. The contractor shall update the existing C&A (certification and accreditation) documentation to conform to the upgraded system. (12). Quality Assurance: The contractor shall develop and maintain a quality program to ensure that the FLPIDS software is produced in accordance with the requirements, the FSA IT environments and program constraints. It should also develop and implement procedures to properly maintain measuring system effectiveness to ensure appropriate corrective action for system failures. (13). Reports and Documentation: The contractor shall define, develop and deliver all reports necessary to support FLPIDS maintainability throughout its life-cycle. (14). Experience and Certifications: The contractor shall have at least one GISSP-Java certified developer dedicated to this project on staff at all times. (15). Transition and Project Closeout: The contractor's proposal shall include a sample transition plan that includes the phase-in and phase-out tasks the Offeror deems important. The contractor shall supply to the government, 30 calendar days prior to the completion of the contract the following information: • Complete backup of all contract and contract related data stored on each employee's hard drive along with any global data • List of all Government Furnished Equipment • List of all contractor employees with access badges, government facilities access and government site access issued under the terms and condition of the contract. Also include in the list the location, phone numbers and email addresses of these employees. • Description of pending actions and contract status. C.1.6. Scope The primary goal is to acquire information technology support services for continued development and enhancements of FLPIDS Production systems. The nature of work sought under this task order consists of contractor resources required for the continuation of the FLPIDS Project, discrete deliverable completion, and the finalization of the migration from the legacy systems. This work will include requirements gathering, design, prototyping, development, testing, and deployment process and require personnel with, but not limited to; Project Management, MS SQL2008, Oracle, SQL Server Integration Services (SSIS), Hyperion, Agile Process, TDD and Code Refactoring, UML Modeling, IDE (Eclipse), Maven, Continuous Integration Server (Hudson), WebSphere, JBoss, J2EE( JNDI, JMS, EJB (2.0 to 3.0), RMI etc), Web Services, Struts (1.0 to 2.2), Hibernate, Spring (Webflow, MVC, IoC, AOP, Transaction Management etc), JPA, Java (5.0 and 6.0), Javascripts, Network Security and Network Communication Protocols skills. Compliance with FSA's System Development Life Cycle (SDLC), Architecture and Management Center (AMC), Information Bulletin and development and configuration change control standards must be followed. The standards are publically available at http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=landing&topic=landing or can be provided to the contractor by the Contracting Officer Technical Representative (COTR) upon request. The Contractor shall provide maintenance support for all Production applications developed by the contractor for up to one year after production implementation. It is the intent of the government to transfer the maintenance functions from the contractor to the government. To that end the contractor will be required to provide analysis support and will review application modifications made by the government to ensure that those modifications integrate with the other applications within DLS. In addition to new DLS development, the base and all option periods shall include: Project Management Provide support including but not limited to: • Task Order Kick-off Meeting • Weekly progress reports to facilitate discussions in meetings • Monthly Status Reporting • Presentation materials as needed • Quality Assurance Surveillance Plan • Risk Management Plan • Project Plan (at least monthly and updated appropriately) • Communications Plan • Conflict of Interest Mitigation Plan (Integration Testing) • C & A Documentation Software Configuration Management: Provide support including but not limited to: • Maintain and update Configuration Management Plan • Change Control and Change Request Tracking • Maintain software repository (currently Subversion) and non-software deliverables in the FCAO SharePoint site • Create software package documentation needed for implementation • Configuration Management Audit Reports Testing and Problem Resolution: Software defects are defined as those items that do not work as designed and/or developed. Software defects can be identified by the FSA Testing and Certification Office (TCO) or by customers that use the software. All software defects require creation of a trouble ticket. Enhancements are defined as those items that work as designed but require modification or correction in order to function differently. Problems with the Production software are reported to the Information Technology Services (ITS) National Service Desk through FSA field officer personnel, the FSA State Coordinator or the FSA Business Sponsor. The service desk accepts problem via email and phone and a Remedy Service Desk ticket is created. If the problem requires a software fix, the FSA TCO will enter a ClearQuest Problem Report referencing the Service Desk ticket number. Problems are assigned a severity (critical, major, average, minor or enhancement) and a priority (emergency, urgent, routine or low). When problems are encountered during the testing of software for problem fixes, upgrades and enhancements, they are tested in the TCO environments and cannot be implemented to production with a severity of "Critical" or "Major". The Agency is currently using Remedy software to log problem tickets and Rational ClearQuest to log modifications to Production software. The vision is to handle all defects and enhancements using the HP Quality Center Migration (HPQC) however, all ClearQuest defects and enhancements are not migrated to HPQC at this time. The Contractor shall use the Agency repository that is available for tracking defects and enhancements until everything is migrated to the new platform. Travel Travel is anticipated and prior approval shall be coordinated with the COTR and Government Project Manager. Travel costs shall be invoiced after approved expenditures are accrued and in the month travel occurs. Travel costs will be invoiced In Accordance With (IAW) the Joint Federal Travel Regulations (JFTR). Travel should be estimated for 3 persons traveling to St. Louis approximately three times per year. The number and types of people shall be determined by the Contractor and based on the purpose of the travel. Maintenance Provide Tier 3 support for production FLPIDS applications that the contractor implements for a period of one year after the implementation. The Contractor shall provide this support during normal business hours, Monday through Friday, beginning at 6:00 AM Central Time. FSA's ultimate goal is for Government staff to maintain mature systems. Transfer of responsibility to the Government shall occur as this contract matures to facilitate this goal. Enhancements Provide analysis, design,developement, testing, implementation and documentation (including User Guides) support to modify existing production applications to include: • Implementation of modifications required to comply with directives received in Information Bulletins (IB's). • Implementation of new/revised functionality based on user needs. • Implementation of new/revised functionality required to comply with new legislation. • Implementation of FSA wide architectural changes The Contractor shall engage with the FCAO development team throughout the SDLC. In some cases, the development effort will be jointly with FCAO. All applications shall provide read/write authorization using EAS as identified by the Government Business Owner or other appropriate authority. If new EAS roles are required by the application, the Contractor shall assist the security group in identifying those new roles. All operational database modifications will be coordinated with the Database Management Office and the data warehouse team. No database modifications will be implemented to a production environment prior to those modifications and load jobs being added to the data warehouse. Direct Contractor interface with the Contracting Officer Technical Representative (COTR) is mandatory under this contract. The COTR shall be responsible for involving other Government subject matter experts. The Contractor shall take direction from the Contracting Officer only; however, day to day monitoring of contract performance shall be managed by the Government Project Manager and/or the COTR. When technical interchange meetings are scheduled, any actions resulting from such meetings that affect the contract's scope of work, the system's design, or administrative issues (including work schedules and/or resources) must be documented and reported to the COTR and /or the Contracting Officer (CO), as appropriate, for approval before being implemented by the Contractor. A Farm Credit Applications Office (FCAO) representative must be at all meetings. C.2 Performance Requirements (1) All software processes delivered under this PWS shall operate in the USDA computing environment, comply with the Government's release management environment, and meet technical architecture requirements. (2) The contractor shall leverage all common business services that are in place to the extent possible; EAS, SCIMS, MRT, FBP and e-Auth, versus custom building solutions. (3) The existing FLP web portal will continue to be used for accessing the Direct Loan System. (4) FSA has adopted a new software engineering approach, based on object-oriented methodology, design patterns, and layered application architecture. SDLC, FSA Reference Application Architecture addresses these standards and applies to work conducted as part of this task order. Copies will be provided upon request. All applications shall be developed and maintained following this engineering approach. (5) The Contractor shall follow the project management methodology and principles as outlined by the Project Management Institute (PMI). The Contractor shall provide project management deliverables as specified by the Office of the Chief Information Officers (OCIO) Enterprise IT Solutions that can be found at: http://www.ocio.usda.gov/nitc/profess_svcs_pms.html for each year of the contract. (6) Implementation consists of two steps. Step 1 is the documentation and turnover of all software required for that specific task to the Government Certification team. Step 2 is the installation of that software and all supporting processes into the Production environment by the Certification team. The Government definition of "final deliverable" for the tasks specified in this section is completion of step 2, successful installation of the software into the Production environment. The Contractor shall develop, deliver and update the following SDLC Artifacts: C.2.1 Requirements and Analysis Phase C.2.1.1 Vision Document - This documents the business overview, business problem, overview solution and scope. It identifies stakeholders, roles and responsibilities, needs and expectations and the Vision Document iteratively identifies features and priority. This document is meant to evolve as understanding of requirements, architecture, plans and technology change. The Vision Document sets the scope for the project. Any changes to scope throughout the product lifecycle should be documented as an addendum to the Vision Document. C.2.1.2 Project Level Glossary - Definition of common terms in the project domain unique to the specific project. Terms defined in the FSA Glossary (see SDLC website) do not need to be included. C.2.1.3 Business Process Model - A high level process diagram/model of the business process the software system to be developed is intended to automate. The business process model allows for the software system to be viewed in the context of the overarching business process itself. The model can be created using business process modeling notation, UML, Microsoft Visio, the Mega suite of Enterprise Architecture tools, or another appropriate modeling or diagramming tool. C.2.1.4 Use Case Documentation - Defines the actor, pre and post conditions, basic flow and alternate flow of all system events. Diagrams may also be required. C.2.1.5 Business Rules - This identifies all actions and direct objects from the Use Case documentation, i.e. information, criteria, selection. For each action and direct object, the constraint details and other information should be captured. C.2.1.6 Navigation Map/Storyboard - This document presents a graphical depiction of how navigation within the application will move the user to various User Interface elements within the application. It is used to review the intended UI with business users and others to verify that it meets requirements and that all use cases have been interpreted correctly. C.2.2 High Level Design C.2.2.1 Design Model and Specification - Documents/diagrams that identify conceptual components and specify their behavior to help produce a logical model of the system. C.2.2.2 Diagram user to system and system to system API's C.2.2.3 Test Strategy document - This document should define the scope and general direction of the testeffort, describing the important issues needing to be covered in the test plan and test scripts. C.2.2.4 Prototype (screen mockups) C.2.2.5 Architectural Decisions document as requested by management - This will validate and document critical design decisions that denote long-term effects on the system. C.2.3 Detailed Design C.2.3.1 Web Screen data element definitions to include database source to target mapping C.2.3.2 Test Plan and test cases - Test cases should include a description of the objective of the test and a description of the condition(s) that will be exercised during the test. Test cases should include pre-conditions, testing inputs, observation points, control points, expected results and post conditions. Test Plan and test cases should include a walkthrough with identified stakeholders. C.2.3.3 Deployment Plan - Documents how and when the deployment unit (EAR file, JAR file, etc.) will be made available. C.2.3.4 Integration Build Plan - Documents how the deployment unit (EAR, JAR, etc) will be delivered, installed and accessed. C.2.4 Construction Phase C.2.4.1 Source code C.2.4.2 Developer Guide - Documents how to setup a new developer's workstation, access requirements, how to check out, build, test, debug and deploy code to integration environment. C.2.4.3 Implementation Plan - Documents the set of tasks necessary to install, test, and verify the developed product(s) perform as expected in the target environment. This document should contain sufficient instructions, including the documentation required to configure the server and to understand installation requirements. C.2.4.4 End User Documentation and Release Notes - This will be determined at the time the project specific task is assigned to the contractor. C.2.4.5 Automated unit and integration tests - The Contractor shall: • Implement the PMO's automated testing process and technologies while constructing the application. • Perform and document automated testing to remove the potential for human error. • Formalize and document Source Code Management processes to ensure repeatability of functional tests. C.2.4.6 Use Quality Reports, providing transparency of an application's condition to development leads and management. C.2.4.7 Develop, document, and deliver software using the automated testing process and technologies demonstrating at least 75% of internal code coverage. All deliverables shall include the following objectives: • Technical assistance and knowledge transfer during all phases of the SDLC (FSA's ultimate goal is for Government staff to maintain mature systems. Transfer of responsibility to the Government shall occur as this contract matures to facilitate this goal). • Technical Review and Code Walk-through (all new development) • User Review and Logic Walk-through (all new development) • User Walk-through of Developed Application (all new development) • Software Configuration Management (all development tasks) • • Support to maintain customer transaction authority in EAS for all new Production implementations. • Data base management and design tasks supporting approved software changes • Training Clips for new functionality added to the system • Problem resolution in support of Testing and resolution of Production problem tickets • Planned pilot and national implementations • Application Security All deliverables shall be provided to the Government Project Manager and the COTR electronically to be posted to the FCAO SharePoint site or other common repository on or before the contractual delivery date. Invoices shall not be posted to the share point site. C.3 Description of Firm-Fixed Price Services (Base Year 09/24/11 - 09/23/12) C.3.1 Project Management Support (CLIN 0001) C.3.1.1 Kick-off Meeting C.3.1.2 Detailed Project Plans (using MS Project 7, at least monthly and updated as appropriate. Any changes to agreed upon deliverable due dates shall require FCAO approval) C.3.1.3 Presentation materials, as required for multi-media presentations C.3.1.4 Quality Assurance Surveillance Plan C.3.1.5 Risk Management Plan (Risk Analysis) C.3.1.6 Schedule Management Plan C.3.1.7 Communications Plan C.3.1.8 Assist in meeting Federal Information Systems Management Act (FISMA) requirements (Certification & Accreditation) C.3.1.9 Monthly Status Reports (including risks and issues log) C.3.1.10 Track and report all active projects including providing raw data to generate Earned Value Management statistics C.3.1.11 Participate in evaluation meetings with FCAO to review project deliverables, status and progress for each initiative C.3.1.12 Comply with USDA requirements for e-Authentication C.3.1.13 Comply with USDA Security and Building Access Requirements C.3.2 Configuration Management Support (CLIN 0002) C.3.2.1 Develop/maintain Traceability Matrix C.3.2.2 Maintain Configuration Management Plan (CMP) C.3.2.3 Manage Change Control Process C.3.2.4 Track and control Change Requests C.3.2.5 Maintain non-software deliverables in the FCAO SharePoint site and software in Subversion C.3.2.6 Configuration Management Audit Reports C.3.2.7 Manage and track artifacts C.3.2.8 Manage deliverables and signoff C.3.2.9 Develop/maintain Detailed Implementation Plans C.3.3 Finance Office Only Functionality for Production Loan Making Transactions (CLIN 0003) Develop "Finance Office" only functionality for "Loan Making" transactions that are already implemented in DLS: • Obligation (1A transaction) • Check Request (1C transaction) • De-obligation (1D transaction) • Loan Closing (1F transaction) C.3.3.1 Develop user requirements (reference C.2.1) C.3.3.2 Design of Transactions (reference C.2.2 and C.2.3) C.3.3.3 Construction of Finance Office Only Transactions (including Developer Guide reference C.2.4) C.3.3.4 Problem resolution in support of Acceptance Testing and Rollout C.3.3.5 Create Training and/or Marketing Materials C.3.3.6 Implementation and Warranty C.3.3.7 Knowledge Transfer C.3.4 Design and Implementation of Finance Office only Transactions (CLIN 0004) The Finance Office only Transactions are: • Check Cancellation (1E) • Cancellation of Loan and/or Check (1J) • Loan/Grant Cancellation - Obligation and Check (1Y) • Split /Combine Loans (8H) Develop "Finance Office" only functionality for "Loan Servicing" transactions currently in PLAS and not DLS: C.3.4.1 Develop User Requirements (reference C.2.1) C.3.4.2 Design of Transactions (reference C.2.2 and C.2.3) C.3.4.3 Construction of Finance Office only Transactions (including Developer Guide reference C.2.4) C.3.4.4 Problem resolution in support of Acceptance Testing and Rollout C.3.4.5 Create Training and Marketing Materials C.3.4.6 Implementation and Warranty C.3.4.7 Knowledge Transfer C.3.5 Design and Implement Statistical Transactions (CLIN 0005) Develop the transactions required to correct statistical data, collateral codes, annual installments and loan numbers. Documentation that identifies the source data will be provided by the Government. The Statistical Transactions are:  Correction of Statistical Information (1T)  Change in Collateral Code (5M)  Change in Loan Number (4F)  Change in Statistical Codes (5N)  Correction of Annual Installments (4L) C.3.5.1 Develop User Requirements (reference C.2.1) C.3.5.2 Design of Transactions (reference C.2.2 and C.2.3) C.3.5.3 Construction of Transactions (including Developer Guide reference C.2.4) C.3.5.4 Problem resolution in support of Acceptance Testing and Rollout C.3.5.5 Create Training and Marketing Materials C.3.5.6 Implementation and Warranty C.3.5.7 Knowledge Transfer C.3.6 Provide Tier-3 Production Support (CLIN 0006) Provide Tier 3 support for production FLPIDS applications for the first year after implementation. The base year will also include the national implementation of the Debt Restructure Application that will be implemented as a state pilot in September 2011. This implementation will entail an "authority" modification only to include additional states that are not part of the pilot. The Contractor shall provide this support during normal business days (Monday through Friday) beginning at 6:00 AM, Central Time. All applications implemented within the contract period shall be supported including analysis, design, programming, testing, implementation and documentation for the complete development effort. C.3.6.1 Maintenance and Support of FLPIDS Production Operations C.3.6.2 Provide a Change Management Plan C.3.6.3 Provide Monthly report on Technical Support C.3.7 Provide Support for Stress Lab Testing (CLIN 0007) C.3.7.1 Deployment and Configuration of Application in Stress Lab C.3.7.2 Identification of System Workload Model (including Production, load estimates) C.3.7.3 Identify Load Test Cases C.3.8 Provide Support for Training Environment (CLIN 0008) C.3.8.1 Create Training Clips C.3.8.2 Assist in Loading Environment C.3.8.3 Provide support to Training Environment (DLS and eDALR$) C.3.9 Develop Loan Status Web Pages (CLIN 0009) Currently the PLAS system has status pages that display loan information. Status pages that show loan information are needed in DLS. The estimated number of pages to be developed is four to six. A Joint Application Design JAD session will be required. C.3.9.1 Develop User Requirements of Loan Status pages (reference C.2.1) C.3.9.2 Design of Loan Status pages (reference C.2.2 and C.2.3) C.3.9.3 Construction (reference C.2.4) C.3.9.4 Problem resolution in support of Acceptance Testing and Rollout C.3.9.5 Implementation and Warranty C.3.9.6 Knowledge Transfer C.3.10 Provide Integration Testing Support (CLIN 0010) The testing life cycle parallels the system development lifecycle. For every phase in the system development lifecycle, there is a corresponding testing activity. Testing relative to the system development life cycle (SDLC) prevents defects from migrating from one phase of the SDLC to the next. Defects migrate to subsequent stages, for example, if there is an error in requirements. Undiscovered, that error will be compounded during the design, then during coding. The correction not only has to include all affected products in the current phase, but all affected products from prior phases. The Government lacks sufficient resources to complete all of the testing for this requirement. With the volume of transactions to be developed, integration testing support is required to ascertain software delivered to TCO is relatively defect-free. This includes new development as well as enhancements. The following assumptions, constraints and contingencies apply: • The person writing Test Scripts shall not be the executor of a Test Script • The test data is a reasonable facsimile of the actual production environment • All test scripts shall be approved by the Government before test execution • All testing processes performed by the Contractor shall be completed and reviewed by the Government before approval of the final test package. • Test cases shall be included with Test Scripts The Contractor shall propose a mitigation strategy for each potential risk (low, medium and high) associated with this CLIN. C.3.10.1 Identification of test data that meets the criteria described in the test plan. C.3.10.2 Perform test and document results to include submission of problem reports. C.3.10.3 Create and maintain test documentation for Government review. C.3.11 Design and Implement Finance office functionality for the existing 8R Limited Resource Interest Rate transaction (CLIN 0011) C.3.11.1 Develop User Requirements (reference C.2.1) C.3.11.2 Design of Transaction (reference C.2.2 and C.2.3) C.3.11.3 Construction of Finance Office only Transaction (including Developer Guide reference C.2.4) C.3.11.4 Problem resolution in support of Acceptance Testing and Rollout C.3.11.5 Create Training and Marketing Materials C.3.11.6 Implementation and Warranty C.3.11.7 Knowledge Transfer C.3.12 Mapping Document of Production Web Screen Data (CLIN 0012) A document that maps Production web screen data elements to the Operational Database shall be developed and maintained. The document shall be stored and maintained in SharePoint or other Government designated repository. C.3.12.1 Analysis of Production screens C.3.12.2 Create Excel Spreadsheet by screen similar to existing mapping documents C.4 Description of Labor-hour Service (Base Year 09/24/11 - 09/23/12) C.4.1 Travel (CLIN 0013) Compliance with Government regulations and fees C.4.2 Enhancements (CLIN 0014) C.4.2.1 Document Enhancement Requirements in Clear Quest (or other Agency repository) C.4.2.2 Provide Time and Material Estimate (number of hours) C.4.2.3 Analysis of Government approved enhancement (reference C.2.1) C.4.2.4 Create/modify Design artifacts (reference C.2.2 and C.2.3) C.4.2.5 Construction of enhancement (reference C.2.4) C.4.2.6 Create/modify Training and Marketing Materials C.4.2.7 Problem resolution in support of acceptance testing C.4.2.8 Implementation into Production C.4.2.9 Knowledge Transfer Enhancements to existing DLS and FLPRA Production applications as follows: 1. Implementation of modifications required to comply with directives received in Information Bulletins (IB's). 2. Implementation of new/revised functionality based on user needs. 3. Implementation of new/revised functionality required to comply with new legislation. 4. Modifications to all enhanced application documentation including User and Developer Guides Enhanced software must maintain previously provided functionality including all interfaces and links to other applications. The government will provide instructions for each enhancement or document requested. The number of enhancements will be no greater than forty (40). The scope and size will be limited to what has historically been requested and provided. Historically, each task averaged 100 support hours with combined labor categories (i.e. Sr. Systems Architect, Jr. Systems Architect, Information Technology Specialist etc.) C.5 Description of Firm-Fixed Price Services (Option Year 1 09/24/12 - 09/23/13) C.5.1 Project Management Support (CLIN 1001) C.5.1.1 Detailed Project Plans (using MS Project 7, at least monthly and updated as appropriate. Any changes to agreed upon deliverable due dates shall require FCAO approval) C.5.1.2 Presentation materials, as required for multi-media presentations C.5.1.3 Risk Management Plan (Risk Analysis) C.5.1.4 Schedule Management Plan C.5.1.5 Communications Plan C.5.1.6 Assist in meeting Federal Information Systems Management Act (FISMA) requirements (Certification & Accreditation) C.5.1.7 Status Reports ( monthly including risks and issues log) C.5.1.8 Track and report all active projects including providing raw data to generate Earned Value Management statistics C.5.1.9 Participate in evaluation meetings with FCAO to review project deliverables, status and progress for each initiative C.5.1.10 Comply with USDA requirements for e-Authentication C.5.1. 11 Comply with USDA Security and Building Access Requirements C.5.2 Configuration Management Support (CLIN 1002) C.5.2.1 Develop/maintain Traceability Matrix C.5.2.2 Maintain Configuration Management Plan (CMP) C.5.2.3 Manage Change Control Process C.5.2.4 Track and control Change Requests C.5.2.5 Maintain non-software deliverables in the FCAO SharePoint site and software in Subversion C.5.2.6 Configuration Management Audit Reports C.5.2.7 Manage and track artifacts C.5.2.8 Manage deliverables and signoff C.5.2.9 Develop/maintain Detailed Implementation Plans C.5.3 Design and Implement Debt Settlement Transactions (CLIN 1003) Develop the transactions required to settle delinquent debt (i.e. foreclosures and write-offs). The Debt Settlement Transactions are: • Debt Settlement (3K) • Debt Settlement Reversal (3K) • Notice of Judgment (3B) • Notice of Judgment Reversal(3B) • Notice of 3rd Party Judgment (3T) • Notice of 3rd Party Judgment Reversal (3T) C.5.3.1 Develop User Requirements (reference C.2.1) C.5.3.2 Design of Transactions (reference C.2.2 and C.2.3) C.5.3.3 Construction of Transactions (including Developer Guide reference C.2.4) C.5.3.4 Problem resolution in support of Acceptance Testing and Rollout C.5.3.5 Create Training and Marketing Materials C.5.3.6 Implementation and Warranty C.5.3.7 Knowledge Transfer C.5.4 Design and Implement Statistical Transactions (CLIN 1004) Develop the transactions required to modify statistical codes on the legacy FLP system. The Statistical Transactions are:  Case Reclassification (5A/5B)  Change Purchase Code (5J)  Change Kind Code (5C) C.5.4.1 Develop User Requirements (reference C.2.1) C.5.4.2 Design of Transactions (reference C.2.2 and C.2.3) C.5.4.3 Construction of Transactions (including Developer Guide reference C.2.4) C.5.4.4 Problem resolution in support of Acceptance Testing and Rollout C.5.4.5 Create Training and Marketing Materials C.5.4.6 Implementation and Warranty C.5.4.7 Knowledge Transfer C.5.5 Design and Implement Debt Restructure Transaction (DRT) Reversals (CLIN 1005) Develop the transactions required to reverse/reapply transactions processing the debt restructure process. The DRT Reversal Transactions are: • Reverse/Reapply New Rates and Terms (1M) • Equity Receivable Suspension/Amortized Reversal/Reapplication (3O) • Amortization of Equity Receivable Suspension Reversal/Reapplication (3O) • Net Recovery Buyout Reversal/Reapplication (3Q) • Shared Appreciation Write-down Reversal/Reapplication (3R) • Equity Receivable Reversal/Reapplication (3V) • Reverse/Reapply Loan Deferral (5W) • Reverse/Reapply Cancel Installment Set-Aside (5T) • Reverse/Reapply Loan Deferral Expiration/Cancellation (5X) C.5.5.1 Develop User Requirements (reference C.2.1) C.5.5.2 Design of DRT Reversal Transactions (reference C.2.2 and C.2.3) C.5.5.3 Construction of DRT Reversal Transactions (including Developer Guide reference C.2.4) C.5.5.4 Problem resolution in support of Acceptance Testing and Rollout C.5.5.5 Create Training and Marketing Materials C.5.5.6 Implementation and Warranty C.5.5.7 Knowledge Transfer C.5.6 Develop Statistical Status Web Pages (CLIN 1006) Currently the PLAS system has status pages that display statistical information. These status pages are needed in DLS. The estimated number of pages to be developed is no more than six. A JAD session will be required. C.5.6.1 Develop User Requirements (reference C.2.1) C.5.6.2 Design Statistical Status Pages (reference C.2.2 and C.2.3) C.5.6.3 Construction of Statistical Status Pages (reference C.2.4) C.5.6.4 Problem resolution in support of Acceptance Testing and Rollout C.5.6.5 Create Training and Marketing Materials C.5.6.6 Implementation and Warranty C.5.6.7 Knowledge Transfer C.5.7 Mapping Document of Production Web Screen Data (CLIN 1007) A document that maps Production web screen data elements to the Operational Database shall be developed and maintained. The document shall be stored and maintained in SharePoint or other Government designated repository. C.5.7.1 Analysis of Production screens C.5.7.2 Create Excel Spreadsheet by screen similar to existing mapping documents C.5.8 Provide Tier-3 Production Support (CLIN 1008) Provide Tier 3 support for production FLPIDS applications for the first year (i.e. the base year) after implementation. The Contractor shall provide this support during normal business days (Monday through Friday) beginning at 6:00 am,Central Time. All applications implemented within the contract period shall be supported including analysis, design, programming, testing, implementation and documentation for the complete development effort. C.5.8.1 Maintenance and Support of FLPIDS Production Operations C.5.8.2 Provide a Change Management Plan C.5.8.3 Provide Monthly report on Technical Support C.5.9 Provide Support for Training Environment (CLIN 1009) C.5.9.1 Create Training Clips C.5.9.2 Assist in Loading Environment C.5.9.3 Provide support to Training Environment (DLS and eDALR$) C.5.10 Provide Integration Testing Support (CLIN 1010) With the volume of transactions to be developed, testing support is required to ascertain software delivered to TCO is relatively defect-free. This includes new development as well as enhancements. C.5.10.1 Identification of test data that meets the criteria described in the test plan. C.5.10.2 Perform test and document results to include submission of problem reports. C.5.10.3 Create and maintain test documentation for Government review. C.6 Description of Labor-hour Service (Option Year 1 09/24/12 - 09/23/13) C.6.1 Travel (CLIN 1011) Compliance with Government regulations and fees C.6.2 Enhancements (CLIN 1012) C.6.2.1 Document Enhancement Requirements in Clear Quest (or other Agency repository) C.6.2.2 Provide Time and Material Estimate (number of hours) C.6.2.3 Analysis of Government approved enhancement (reference C.2.1) C.6.2.4 Create/modify Design artifacts (reference C.2.2 and C.2.3) C.6.2.5 Construction of enhancement (reference C.2.4) C.6.2.6 Create/modify Training and Marketing Materials C.6.2.7 Problem resolution in support of acceptance testing C.6.2.8 Implementation into Production C.6.2.9 Knowledge Transfer Enhancements to existing DLS and FLPRA Production applications as follows: 1. Implementation of modifications required to comply with directives received in Information Bulletins (IB's). 2. Implementation of new/revised functionality based on user needs. 3. Implementation of new/revised functionality required to comply with new legislation. 4. Modifications to all enhanced application documentation including User and Developer Guides Enhanced software must maintain previously provided functionality including all interfaces and links to other applications. The government will provide instructions for each enhancement or document requested. The number of enhancements will be no greater than forty (40). The scope and size will be limited to what has historically been requested and provided. Historically, each task averaged 100 support hours with combined labor categories (i.e. Sr. Systems Architect, Jr. Systems Architect, Information Technology Specialist etc.) C.7 Description of Firm-Fixed Price Services (Option Year 2 09/24/13 - 09/23/14) C.7.1 Project Management Support (CLIN 2001) C.7.1.1 Detailed Project Plans (using MS Project 7, at least monthly and updated as appropriate. Any changes to agreed upon deliverable due dates shall require FCAO approval) C.7.1.2 Presentation materials, as required for multi-media presentations C.7.1.3 Risk Management Plan (Risk Analysis) C.7.1.4 Schedule Management Plan C.7.1.5 Communications Plan C.7.1.6 Assist in meeting Federal Information Systems Management Act (FISMA) requirements (Certification & Accreditation) C.7.1.7 Status Reports (monthly including risks and issues log) C.7.1.8 Track and report all active projects including providing raw data to generate Earned Value Management statistics C.7.1.9 Participate in evaluation meetings with FCAO to review project deliverables, status and progress for each initiative C.7.1.10 Comply with USDA requirements for e-Authentication C.7.1.11 Comply with USDA Security and Building Access Requirements C.7.2 Configuration Management Support (CLIN 2002) C.7.2.1 Develop/maintain Traceability Matrix C.7.2.2 Maintain Configuration Management Plan (CMP) C.7.2.3 Manage Change Control Process C.7.2.4 Track and control Change Requests C.7.2.5 Maintain non-software deliverables in the FCAO SharePoint site and software in Subversion C.7.2.6 Configuration Management Audit Reports C.7.2.7 Manage and track artifacts C.7.2.8 Manage deliverables and signoff C.7.2.9 Develop/maintain Detailed Implementation Plans C.7.3 Design and Implement Property Maintenance Transactions (CLIN 2003) Develop the transactions required to acquire foreclosed property and to manage that property. The Property Maintenance Transactions are: • Property Acquisition (3E) • Property Acquisition Reversal (3E) • Acquired Property Maintenance (5L) • Cash Sale (1H) • Cash Sale Reversal (1H) • Lease of Real Property (1S) • Lease of Real Property Reversal (1S) • Subdivision (8P) • Subdivision Reversal (8P) • Suspend Code (9E) • Mail Code Change (9G) • Conservation Easement (3Y) • Conservation Easement Reversal (3Y) • Write-off Lease Account (3L) • Write-off Lease Account Reversal (3L) Documentation that identifies the source data will be provided by the Government. A JAD session will be required. C.7.3.1 Develop User Requirements (reference C.2.1) C.7.3.2 Design of Transactions (reference C.2.2 and C.2.3) C.7.3.3 Construction of Transactions (including Developer Guide reference C.2.4) C.7.3.4 Problem resolution in support of Acceptance Testing and Rollout C.7.3.5 Create Training and Marketing Materials C.7.3.6 Implementation and Warranty C.7.3.7 Knowledge Transfer C.7.4 Design and Implementation of Finance Office only Cash Transactions (CLIN 2004) The Finance Office only Cash Transactions are: • Reversal/Reapplication of Payment Same Borrower (2F) • Reversal/Reapplication of Payment Different Borrower (2U) • Reapplication to Correct Payment Type (2Z) • Noncash Credit Administrative Adjustment (3G) • Noncash Credit Administrative Adjustment Reversal (3G) Develop "Finance Office" only functionality for "Loan Servicing" transactions currently in PLAS and not DLS: C.7.4.1 Develop User Requirements (reference C.2.1) C.7.4.2 Design of Finance Office only Transactions (reference C.2.2 and C.2.3) C.7.4.3 Construction of Finance Office only Transactions (including Developer Guide reference C.2.4) C.7.4.4 Problem resolution in support of Acceptance Testing and Rollout C.7.4.5 Create Training and Marketing Materials C.7.4.6 Implementation and Warranty C.7.4.7 Knowledge Transfer C.7.5 Design and Implementation of Finance Office only Statistical Transaction (CLIN 2005) The Finance Office only Statistical Transaction is: • Establish Suspend Code (5E) Develop "Finance Office" only functionality for "Loan Servicing" transactions currently in PLAS and not DLS: C.7.5.1 Develop User Requirements (reference C.2.1) C.7.5.2 Design of Finance Office only Transactions (reference C.2.2 and C.2.3) C.7.5.3 Construction of Finance Office only Transactions (including Developer Guide reference C.2.4) C.7.5.4 Problem resolution in support of Acceptance Testing and Rollout C.7.5.5 Create Training and Marketing Materials C.7.5.6 Implementation and Warranty C.7.5.7 Knowledge Transfer C.7.6 Design and Implementation of Finance Office only Loan Adjustment Transactions (CLIN 2006) The Finance Office only Loan Adjustment Transactions are: • Maturing of Account (4M) • Schedule Status Adjustments (4P) Develop "Finance Office" only functionality for "Loan Servicing" transactions currently in PLAS and not DLS: C.7.6.1 Develop User Requirements (reference C.2.1) C.7.6.2 Design of Finance Office only Transactions (reference C.2.2 and C.2.3) C.7.6.3 Construction of Finance Office only Transactions (including Developer Guide reference C.2.4) C.7.6.4 Problem resolution in support of Acceptance Testing and Rollout C.7.6.5 Create Training and Marketing Materials C.7.6.6 Implementation and Warranty C.7.6.7 Knowledge Transfer C.7.7 Provide Integration Testing Support (CLIN 2007) With the volume of transactions to be developed, testing support is required to ascertain software delivered to TCO is relatively defect-free. This includes new development as well as enhancements. The Contractor shall propose a mitigation strategy for each potential risk (low, medium and high) associated with this CLIN as outlined in C.3.10. C.7.7.1 Identification of test data that meets the criteria described in the test plan. C.7.7.2 Perform test and document results to include submission of problem reports. C.7.7.3 Create and maintain test documentation for Government review. C.7.8 Provide Tier-3 Production Support (CLIN 2008) Provide Tier 3 support for production FLPIDS applications for the first year after implementation. The Contractor shall provide this support during normal business days (Monday through Friday) beginning at 6:00 am, Central Time. All applications implemented within the contract period shall be supported including analysis, design, programming, testing, implementation and documentation for the complete development effort. C.7.8.1 Maintenance and Support of FLPIDS Production Operations C.7.8.2 Provide a Change Management Plan C.7.8.3 Provide Monthly report on Technical Support C.7.9 Provide Support for Training Environment (CLIN 2009) C.7.9.1 Create Training Clips C.7.9.2 Assist in Loading Environment C.7.9.3 Provide support to Training Environment (DLS and eDALR$) C.7.10 Mapping Document of Production Web Screen Data (CLIN 2010) A document that maps Production web screen data elements to the Operational Database shall be developed and maintained. The document shall be stored and maintained in SharePoint or other Government designated repository. C.7.10.1 Analysis of Production screens C.7.10.2 Create Excel Spreadsheet by screen similar to existing mapping documents C.8 Description of Labor-hour Service (Option Year 2 09/24/13 - 09/23/14) C.8.10 Travel (CLIN 2011) Compliance with Government regulations and fees C.8.11 Enhancements (CLIN 2012) C.8.11.1 Document Enhancement Requirements in Clear Quest (or other Agency repository)C.8.11.2 Provide Time and Material Estimate (number of hours) C.8.11.3 Analysis of Government approved enhancement (reference C.2.1) C.8.11.4 Create/modify Design artifacts (reference C.2.2 and C.2.3) C.8.11.5 Construction of enhancement (reference C.2.4) C.8.11.6 Create/modify Training and Marketing Materials C.8.11.7 Problem resolution in support of acceptance testing C.8.11.8 Implementation into Production C.8.11.9 Knowledge Transfer Enhancements to existing DLS and eDALR$ Production applications as follows: 1. Implementation of modifications required to comply with directives received in Information Bulletins (IB's). 2. Implementation of new/revised functionality based on user needs. 3. Implementation of new/revised functionality required to comply with new legislation. 4. Modifications to all enhanced application documentation including User and Developer Guides Enhanced software must maintain previously provided functionality including all interfaces and links to other applications. The government will provide instructions for each enhancement or document requested. The number of enhancements will be no greater than forty (40). The scope and size will be limited to what has historically been requested and provided. Historically, each task averaged 100 support hours with combined labor categories (i.e. Sr. Systems Architect, Jr. Systems Architect, Information Technology Specialist etc.) C.9 Description of Firm-Fixed Price Services (Option Year 3 09/24/14 - 09/23/15) C.9.1 Project Management Support (CLIN 3001) C.9.1.1 Detailed Project Plans (using MS Project 7, at least monthly and updated as appropriate. Any changes to agreed upon deliverable due dates shall require FCAO approval) C.9.1.2 Presentation materials, as required for multi-media presentations C.9.1.3 Risk Management Plan (Risk Analysis) C.9.1.4 Schedule Management Plan C.9.1.5 Communications Plan C.9.1.6 Assist in meeting Federal Information Systems Management Act (FISMA) requirements (Certification & Accreditation) C.9.1.7 Status Reports (monthly including risks and issues log) C.9.1.8 Track and report all active projects including providing raw data to generate Earned Value Management statistics C.9.1.9 Participate in evaluation meetings with FCAO to review project deliverables, status and progress for each initiative C.9.1.10 Comply with USDA requirements for e-Authentication C.9.1.11 Comply with USDA Security and Building Access Requirements C.9.2 Configuration Management Support (CLIN 3002) C.9.2.1 Develop/maintain Traceability Matrix C.9.2.2 Maintain Configuration Management Plan (CMP) C.9.2.3 Manage Change Control Process C.9.2.4 Track and control Change Requests C.9.2.5 Maintain Clear Case and SharePoint Statistics C.9.2.6 Configuration Management Audit Reports C.9.2.7 Manage and track artifacts C.9.2.8 Manage deliverables and signoff C.9.2.9 Develop/maintain Detailed Implementation Plans C.9.3 Design and Implementation of Finance Office only Miscellaneous Transactions (CLIN 3003) The Finance Office only Transactions are: • Miscellaneous Adjustment (4S) • Reopen Closed Property/Lease Account (4K) • Default Charge (1R) • Default Credit (3C) • Loan Charge Adjustment (1W) • Insurance Charge (1P) • Employee Defalcation (3F) • Noncash Credit - 3rd Party Judgment (3P) Develop "Finance Office" only functionality for "Loan Servicing" transactions currently in PLAS and not DLS: C.9.3.1 Develop User Requirements (reference C.2.1) C.9.3.2 Design of Finance Office only Transactions (reference C.2.2 and C.2.3) C.9.3.3 Construction of Finance Office only Transactions (including Developer Guide reference C.2.4) C.9.3.4 Problem resolution in support of Acceptance Testing and Rollout C.9.3.5 Create Training and Marketing Materials C.9.3.6 Implementation and Warranty C.9.3.7 Knowledge Transfer C.9.4 Provide Integration Testing Support (CLIN 3004) With the volume of transactions to be developed, testing support is required to ascertain software delivered to TCO is relatively defect-free. This includes new development as well as enhancements. The Contractor shall propose a mitigation strategy for each potential risk (low, medium and high) associated with this CLIN as outlined in C.3.10. C.9.4.1 Identification of test data that meets the criteria described in the test plan. C.9.4.2 Perform test and document results to include submission of problem reports. C.9.4.3 Create and maintain test documentation for Government review. C.9.5 Mapping Document of Production Web Screen Data (CLIN 3005) A document that maps Production web screen data elements to the Operational Database shall be developed and maintained. The document shall be stored and maintained in SharePoint or other Government designated repository. C.9.5.1 Analysis of Production screens C.9.5.2 Create Excel Spreadsheet by screen similar to existing mapping documents C.9.6 Provide Tier-3 Production Support (CLIN 3006) Provide Tier 3 support for production FLPIDS applications for the first year after implementation. The Contractor shall provide this support during normal business days (Monday through Friday) beginning at 6:00 am, Central Time. All applications implemented within the contract period shall be supported including analysis, design, programming, testing, implementation and documentation for the complete development effort. C.9.6.1 Maintenance and Support of FLPIDS Production Operations C.9.6.2 Provide a Change Management Plan C.9.6.3 Provide Monthly report on Technical Support C.9.7 Provide Support for Training Environment (CLIN 3007) C.9.7.1 Create Training Clips C.9.7.2 Assist in Loading Environment C.9.7.3 Provide support to Training Environment (DLS and eDALR$) C.10 Description of Labor-hour Service (Option Year 3 09/24/14 - 09/23/15) C.10.1 Travel (CLIN 3008) Compliance with Government regulations and fees C.10.2 Enhancements (CLIN 309) C.10.2.1 Document Enhancement Requirements in Clear Quest (or other Agency repository) C.10.2.2 Provide Time and Material Estimate (number of hours) C.10.2.3 Analysis of Government approved enhancement (reference C.2.1) C.10.2.4 Create/modify Design artifacts (reference C.2.2 and C.2.3) C.10.2.5 Construction of enhancement (reference C.2.4) C.10.2.6 Create/modify Training and Marketing Materials C.10.2.7 Problem resolution in support of acceptance testing C.10.2.8 Implementation into Production C.10.2.9 Knowledge Transfer Enhancements to existing DLS and eDALR$ Production applications as follows: 1. Implementation of modifications required to comply with directives received in Information Bulletins (IB's). 2. Implementation of new/revised functionality based on user needs. 3. Implementation of new/revised functionality required to comply with new legislation. 4. Modifications to all enhanced application documentation including User and Developer Guides Enhanced software must maintain previously provided functionality including all interfaces and links to other applications. The government will provide instructions for each enhancement or document requested. The number of enhancements will be no greater than forty (40). The scope and size will be limited to what has historically been requested and provided. Historically, each task averaged 100 support hours with combined labor categories (i.e. Sr. Systems Architect, Jr. Systems Architect, Information Technology Specialist etc.) C.10.3 Perform Analysis of the PLAS batch subsystems (CLIN 3010) Analyze the existing PLAS subsystems and create high-level design documentation required to replace the existing Cobol batch processes of that system. There are approximately 120-130 subsystems to be replaced. The design shall include design for new batch processes or conversion of the existing batch processes to online update(s). The design shall include recommended alternatives for the replacement of PLAS. The design alternatives shall utilize the DLS for data entry. C.10.3.1 Design Alternatives C.11 Description of Firm-Fixed Price Services (Option Year 4 09/24/15 - 09/23/16) C.11.1 Project Management Support (CLIN 4001) C.11.1.1 Detailed Project Plans (using MS Project 7, at least monthly and updated as appropriate. Any changes to agreed upon deliverable due dates shall require FCAO approval) C.11.1.2 Presentation materials, as required for multi-media presentations C.11.1.3 Risk Management Plan (Risk Analysis) C.11.1.4 Schedule Management Plan C.11.15 Communications Plan C.11.1.6 Assist in meeting Federal Information Systems Management Act (FISMA) requirements (Certification & Accreditation) C.11.1.7 Status Reports ( monthly including risks and issues log) C.11.1.8 Track and report all active projects including providing raw data to generate Earned Value Management statistics C.11.1.9 Participate in evaluation meetings with FCAO to review project deliverables, status and progress for each initiative C.11.1.10 Comply with USDA requirements for e-Authentication C.11.1.11 Comply with USDA Security and Building Access Requirements C.11.2 Configuration Management Support (CLIN 4002) C.11.2.1 Develop/maintain Traceability Matrix C.11.2.2 Maintain Configuration Management Plan (CMP) C.11.2.3 Manage Change Control Process C.11.2.4 Track and control Change Requests C.11.2.5 Maintain non-software deliverables in the FCAO SharePoint site and software in Subversion C.11.2.6 Configuration Management Audit Reports C.11.2.7 Manage and track artifacts C.11.2.8 Manage deliverables and signoff C.11.2.9 Develop/maintain Detailed Implementation Plans C.11.3 Provide Tier-3 Production Support (CLIN 4003) Provide Tier 3 support for production FLPIDS applications for the first year after implementation. The Contractor shall provide this support during normal business days (Monday through Friday) beginning at 6:00 AM, Central Time. All applications implemented within the contract period shall be supported including analysis, design, programming, testing, implementation and documentation for the complete development effort. C.11.3.1 Maintenance and Support of FLPIDS Production Operations C.11.3.2 Provide a Change Management Plan C.11.3.3 Provide Monthly report on Technical Support C.12 Description of Labor-hour Service (Option Year 4 09/24/15 - 09/23/16) C.12.1 Travel (CLIN 4004) Compliance with Government regulations and fees C.12.2 Enhancements (CLIN 4005) C.12.2.1 Document Enhancement Requirements in Clear Quest (or other Agency repository) C.12.2.2 Provide Time and Material Estimate (number of hours) C.12.2.3 Analysis of Government approved enhancement (reference C.2.1) C.12.2.4 Create/modify Design artifacts (reference C.2.2 and C.2.3) C.12.2.5 Construction of enhancement (reference C.2.4) C.12.2.6 Create/modify Training and Marketing Materials C.12.2.7 Problem resolution in support of acceptance testing C.12.2.8 Implementation into Production C.12.2.9 Knowledge Transfer Enhancements to existing DLS and FLPRA Production applications as follows: 1. Implementation of modifications required to comply with directives received in Information Bulletins (IB's). 2. Implementation of new/revised functionality based on user needs. 3. Implementation of new/revised functionality required to comply with new legislation. 4. Modifications to all enhanced application documentation including User and Developer Guides Enhanced software must maintain previously provided functionality including all interfaces and links to other applications. The government will provide instructions for each enhancement or document requested. The number of enhancements will be no greater than forty (40). The scope and size will be limited to what has historically been requested and provided. Historically, each task averaged 100 support hours with combined labor categories (i.e. Sr. Systems Architect, Jr. Systems Architect, Information Technology Specialist etc.) C.12.3 Create a Detailed Design Document of the PLAS processes that remain to be developed in DLS (CLIN 4006) Create and finalize design documentation to replace the PLAS using as a foundation, the design alternative chosen from CLIN 3003. If a COTS package is chosen as the design alternative, the Contractor shall design the necessary modifications to that COTS replacement to provide the all of the functionality currently provided by the PLAS. C.12.3.1 Detailed Design Document C.13 Deliverables Deliverable Description Due Date C.3.1.1 Kickoff Meeting Briefing No later than (NLT) seven days of the period of performance (POP) start date C.3.1.2 Detailed Project Plan NLT ten working days after the POP start date and updated monthly. All changes to deliverable due dates require FCAO approval. C.3.1.4 Quality Assurance Surveillance Plan NLT 30 days of the POP start date. C.3.1.5 Risk Management Plan NLT 30 days of the POP start date. C.3.1.7 Communications Plan No later than (NLT) seven days of the period of performance (POP) start date C.3.1.9 Status Reports Monthly - NLT the seventh work day following the end of the month. C.3.2.1 Traceability Matrix NLT ten working days after the POP start date and updated monthly C.3.2.2 Configuration Management Plan Update and maintain as needed to comply with C& A schedules C.3.2.9 Detailed Implementation Plans NLT 3 weeks in advance of scheduled implementation. C.3.3.1 Requirements Documentation (USE cases and other SDLC artifacts) 1A, 1C, 1D, 1F In accordance with project schedule as agreed to by the Government and the Contractor. C.3.3.2 Design Documentation FO only transactions: 1A, 1C, 1D, 1F In accordance with project schedule as agreed to by the Government and the Contractor. C.3.3.3 Construction FO only transactions: 1A, 1C, 1D, 1F In accordance with project schedule as agreed to by the Government and the Contractor. C.3.3.5 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.3.3.6 Implementation and warranty 1A, 1C, 1D, 1F In accordance with project schedule as agreed to by the Government and the Contractor. C.3.4.1 User Requirements transactions: 1E, 1J, 1Y, 8H In accordance with project schedule as agreed to by the Government and the Contractor. C.3.4.2 Design transactions: 1E, 1J, 1Y, 8H In accordance with project schedule as agreed to by the Government and the Contractor. C.3.4.3 Construction transactions: 1E, 1J, 1Y, 8H In accordance with project schedule as agreed to by the Government and the Contractor. C.3.4.5 Create Training and Marketing materials In accordance with project schedule as agreed to by the Government and the Contractor. C.3.4.6 Implementation and warranty 1E, 1J, 1Y, 8H In accordance with project schedule as agreed to by the Government and the Contractor. C.3.5.1 Develop user requirements transactions: 1T, 5M, 4F, 5N 4L In accordance with project schedule as agreed to by the Government and the Contractor. C.3.5.2 Designof Transactions: 1T, 5M, 4F, 5N 4L In accordance with project schedule as agreed to by the Government and the Contractor. C.3.5.3 Construction of Transactions: 1T, 5M, 4F, 5N 4L In accordance with project schedule as agreed to by the Government and the Contractor. C.3.5.5 Create Training and Marketing materials In accordance with project schedule as agreed to by the Government and the Contractor. C.3.5.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.3.6.1 Tier-3 Production Support as listed in the Monthly Status Report. In accordance with project schedule as agreed to by the Government and the Contractor. C.3.7 Support for Stress Lab Testing In accordance with project schedule as agreed to by the Government and the Contractor. C.3.8.3 Support for Training Environment In accordance with project schedule as agreed to by the Government and the Contractor. C.3.9.1 Develop user requirements for status pages In accordance with project schedule as agreed to by the Government and the Contractor. C.3.9.2 Design documents for status pages In accordance with project schedule as agreed to by the Government and the Contractor. C.3.9.3 Construction of status pages In accordance with project schedule as agreed to by the Government and the Contractor. C.3.9.5 Implementation and warranty of status pages In accordance with project schedule as agreed to by the Government and the Contractor. C.3.10.2 Perform Testing - document results In accordance with project schedule as agreed to by the Government and the Contractor. C.3.10.3 Test Documentation In accordance with project schedule as agreed to by the Government and the Contractor. C.3.11.1 Develop user requirements for transaction: 8R In accordance with project schedule as agreed to by the Government and the Contractor. C.3.11.2 Design documents for transaction 8R In accordance with project schedule as agreed to by the Government and the Contractor. C.3.12.2 Mapping Document of Production Web Screens In accordance with project schedule as agreed to by the Government and the Contractor. C.4.2.4 Create/modify design artifacts for enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.4.2.5 Construction of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.4.2.6 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.4.2.8 Implementation and warranty of enhancements to Production In accordance with project schedule as agreed to by the Government and the Contractor. C.5.1.1 Detailed Project Plan NLT ten working days after the POP start date and updated monthly as required. All changes to deliverable due dates require FCAO approval. C.5.1.3 Risk Management Plan NLT 30 days of the POP start date. C.5.1.5 Communications Plan No later than (NLT) seven days of the period of performance (POP) start date C.5.1.7 Status Reports Monthly - NLT the seventh work day following the end of the month. C.5.2.1 Traceability Matrix NLT ten working days after the POP start date and updated monthly C.5.2.2 Configuration Management Plan Update and maintain as needed to comply with C& A schedules C.5.2.9 Detailed Implementation Plans NLT 3 weeks in advance of scheduled implementation. C.5.3.1 User Requirements 3K, 3B, 3T In accordance with project schedule as agreed to by the Government and the Contractor. C.5.3.2 Design Documents Transactions: 3K, 3B, 3T In accordance with project schedule as agreed to by the Government and the Contractor. C.5.3.3 Construction of Transactions: 3K, 3B, 3T In accordance with project schedule as agreed to by the Government and the Contractor. C.5.3.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.5.3.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.5.4.1 User Requirements 5A/5B, 5J, 5C In accordance with project schedule as agreed to by the Government and the Contractor. C.5.4.2 Design Documents for transactions: 5A/5B, 5J, 5C In accordance with project schedule as agreed to by the Government and the Contractor. C.5.4.3 Construction of transactions: 5A/5B, 5J, 5C In accordance with project schedule as agreed to by the Government and the Contractor. C.5.4.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.5.4.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.5.5.1 User Requirements for Transactions: 1M, 3O, 3Q, 3R, 3V, 5W, 5T, 5X In accordance with project schedule as agreed to by the Government and the Contractor. C.5.5.2 Design Documents for Transactions: 1M, 3O, 3Q, 3R, 3V, 5W, 5T, 5X In accordance with project schedule as agreed to by the Government and the Contractor. C.5.5.3 Construction of Transactions: 1M, 3O, 3Q, 3R, 3V, 5W, 5T, 5X In accordance with project schedule as agreed to by the Government and the Contractor. C.5.5.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.5.5.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.5.6.1 User Requirements Statistical Information Status Pages In accordance with project schedule as agreed to by the Government and the Contractor. C.5.6.2 Design Documents for Statistical Information Status Pages In accordance with project schedule as agreed to by the Government and the Contractor. C.5.6.3 Construction of Statistical Information Status Pages In accordance with project schedule as agreed to by the Government and the Contractor. C.5.6.5 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.5.6.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.5.7.1 Analysis of Production Web Screens In accordance with project schedule as agreed to by the Government and the Contractor. C.5.7.2 Mapping Document - Create Excel Spreadsheet of production web screens In accordance with project schedule as agreed to by the Government and the Contractor. C.5.8 Tier-3 Production Support as listed in the Monthly Status Report. In accordance with project schedule as agreed to by the Government and the Contractor. C.5.9.1 Create Training Clips In accordance with project schedule as agreed to by the Government and the Contractor. C.5.10.1 Identify Test Data In accordance with project schedule as agreed to by the Government and the Contractor. C.5.10.2 Perform tests and document results In accordance with project schedule as agreed to by the Government and the Contractor. C.6. 2.4 Create/modify design artifacts for enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.6.2.5 Construction of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.6.2.6 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.6.2.8 Implementation of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.7.1.1 Detailed Project Plan NLT ten working days after the POP start date and updated monthly. All changes to deliverable due dates require FCAO approval. C.7.1.3 Risk Management Plan NLT 30 days of the POP start date. C.7.1.5 Communications Plan No later than (NLT) seven days of the period of performance (POP) start date C.7.1.7 Status Reports Monthly - NLT the seventh work day following the end of the month. C.7.2.1 Traceability Matrix NLT ten working days after the POP start date and updated monthly C.7.2.2 Configuration Management Plan Update and maintain as needed to comply with C& A schedules C.7.2.9 Detailed Implementation Plans NLT 3 weeks in advance of scheduled implementation. C.7.3.1 User Requirements for Transactions: 3E, 5L,1H, 1S, 8P, 9E, 9G, 3Y, 3L In accordance with project schedule as agreed to by the Government and the Contractor. C.7.3.2 Design Documents for Transactions: 3E, 5L,1H, 1S, 8P, 9E, 9G, 3Y, 3L In accordance with project schedule as agreed to by the Government and the Contractor. C.7.3.3 Construction of Transactions: 3E, 5L,1H, 1S, 8P, 9E, 9G, 3Y, 3L In accordance with project schedule as agreed to by the Government and the Contractor. C.7.3.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.7.3.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.7.4.1 User Requirements for Transactions: 2F, 2U, 2Z, 3G, In accordance with project schedule as agreed to by the Government and the Contractor. C.7.4.2 Design Documents for Transactions: 2F, 2U, 2Z, 3G, In accordance with project schedule as agreed to by the Government and the Contractor. C.7.4.3 Construction of Transactions: 2F, 2U, 2Z, 3G, In accordance with project schedule as agreed to by the Government and the Contractor. C.7.4.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.7.4.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.7.5.1 User Requirements for Transaction 5E In accordance with project schedule as agreed to by the Government and the Contractor. C.7.5.2 Design Documents for Transaction 5E In accordance with project schedule as agreed to by the Government and the Contractor. C.7.5.3 Construction of Transaction 5E In accordance with project schedule as agreed to by the Government and the Contractor. C.7.5.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.7.5.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.7.6.1 User Requirements for Transactions: 4M, 4P In accordance with project schedule as agreed to by the Government and the Contractor. C.7.6.2 Design Documents for Transactions: 4M, 4P In accordance with project schedule as agreed to by the Government and the Contractor. C.7.6.3 Construction of Transactions: 4M, 4P In accordance with project schedule as agreed to by the Government and the Contractor. C.7.6.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.7.6.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.7.7.1 Identify Test Cases In accordance with project schedule as agreed to by the Government and the Contractor. C.7.7.2 Perform testing In accordance with project schedule as agreed to by the Government and the Contractor. C.7.8 Tier-3 Production Support as listed in the Monthly Status Report. In accordance with project schedule as agreed to by the Government and the Contractor. C.7.9.1 Create Training Clips In accordance with project schedule as agreed to by the Government and the Contractor. C.7.9.3 Support for Training Environment In accordance with project schedule as agreed to by the Government and the Contractor. C.7.10.1 Analysis of Production Screens In accordance with project schedule as agreed to by the Government and the Contractor. C.7.10.2 Mapping Document Create Excel Spreadsheet of production web screens In accordance with project schedule as agreed to by the Government and the Contractor. C.8.11.5 Construction of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.8.11.6 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.8.11.8 Implementation of enhancements into production In accordance with project schedule as agreed to by the Government and the Contractor. C.9.1.1 Detailed Project Plan NLT ten working days after the POP start date and updated monthly. All changes to deliverable due dates require FCAO approval. C.9.1.3 Risk Management Plan NLT 30 days of the POP start date. C.9.1.5 Communications Plan No later than (NLT) seven days of the period of performance (POP) start date C.9.1.7 Status Reports Monthly - NLT the seventh work day, following the end of the month. C.9.2.1 Traceability Matrix NLT ten working days after the POP start date and updated monthly C.9.2.2 Configuration Management Plan Update and maintain as needed to comply with C& A schedules C.9.2.9 Detailed Implementation Plans NLT 3 weeks in advance of scheduled implementation. C.9.3.1 User Requirements for Transactions: 4S, 4K, 1R, 3C, 1W, 1P, 3H, 3Q, 3F, 3P In accordance with project schedule as agreed to by the Government and the Contractor. C.9.3.2 Design Documents for Transactions: 4S, 4K, 1R, 3C, 1W, 1P, 3H, 3Q, 3F, 3P In accordance with project schedule as agreed to by the Government and the Contractor. C.9.3.3 Construction of Transactions: 4S, 4K, 1R, 3C, 1W, 1P, 3H, 3Q, 3F, 3P In accordance with project schedule as agreed to by the Government and the Contractor. C.9.3.5 Create Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.9.3.6 Implementation and Warranty In accordance with project schedule as agreed to by the Government and the Contractor. C.9.4.1 Identify Test Cases In accordance with project schedule as agreed to by the Government and the Contractor. C.9.4.2 Perform testing In accordance with project schedule as agreed to by the Government and the Contractor. C.9.5 Mapping Document - production web screens In accordance with project schedule as agreed to by the Government and the Contractor. C.9.76 Tier-3 Production Support as listed in the Monthly Status Report. In accordance with project schedule as agreed to by the Government and the Contractor. C.9.7.1 Create Training Clips In accordance with project schedule as agreed to by the Government and the Contractor. C.9.7.3 Support for Training Environment In accordance with project schedule as agreed to by the Government and the Contractor. C.9.2.5 Construction of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.9.2.6 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.9.2.8 Implementation of enhancements into Production In accordance with project schedule as agreed to by the Government and the Contractor. C.10.3.1 Design alternatives for PLAS batch subsystems In accordance with project schedule as agreed to by the Government and the Contractor. C.11.1.1 Detailed Project Plan NLT ten working days after the POP start date and updated monthly as required. All changes to deliverable due dates require FCAO approval. C.11.1.3 Risk Management Plan NLT 30 days of the POP start date. C.11.1.5 Communications Plan No later than (NLT) seven days of the period of performance (POP) start date C.11.1.7 Status Reports Monthly - NLT the seventh work day, following the end of the month. C.11.2.1 Traceability Matrix NLT ten working days after the POP start date and updated monthly C.11.2.2 Configuration Management Plan Update and maintain as needed to comply with C& A schedules C.11.2.9 Detailed Implementation Plans NLT 3 weeks in advance of scheduled implementation. C.11.3.1 Tier-3 Production Support as listed in the Monthly Status Report. In accordance with project schedule as agreed to by the Government and the Contractor. C.12.2.5 Construction of enhancements In accordance with project schedule as agreed to by the Government and the Contractor. C.12.2.6 Training and Marketing Materials In accordance with project schedule as agreed to by the Government and the Contractor. C.12.2.8 Implementation into Production In accordance with project schedule as agreed to by the Government and the Contractor. C.12.3.1 Design alternatives for PLAS batch subsystems In accordance with project schedule as agreed to by the Government and the Contractor. C.14 Identification Standards All Contract employees will require a LincPass based on the requirements set forth by HSPD-12, FIPS PUB 201-1, OMB Memorandum M-05-24. Effective September 8, 2009, all contractors are required to use the E-Verify system to verify their employees' eligibility to work in the United States (if applicable). More information on the program is available on the E-Verify Web site at www.dhs.gov/e-verify E-Verify customer support is also available by calling toll free (888) 464-4218. C.15 Operating Constraints The following restraints must be taken into consideration and included as part of the contract Performance Work Statement: Contractor support will be required during FSA primary service hours Monday through Friday from 6:00 am to 6:00 pm Central Time. Normal tour of duty will be 40 hours per week. Technical support is provided by telephone, e-mail, Microsoft NetMeeting, and in person depending on the problem and location. The support identified in this contract will be considered third level (tier 3) contact for the customer. Earned Value Management (EVM), applicable to this requirement, is a project management tool that effectively integrates the project scope of work with schedule and cost elements for optimum project planning and control. The qualities and operating characteristics of earned value management systems are described in American National Standards Institute (ANSI)/Electronic Industries Alliance Standard - 748-1998, Earned Value Management System (EVMS), approved May 19, 1998. Information on earned value management systems is available http://www.acq.osd.mil/pm. The Contractor shall use EVMS to manage this project and report project status. The Contractor shall provide updates to this information monthly with formal deliverables updating the overall project plan as needed. The USDA Office of the Chief Information Officer (OCIO) web site contains a template that may be used in establishing a project plan to use for EVMS reporting table at http:www.ocio.usda.gov/irm/cap plan/worklenz project.html. The Contractor shall ensure all processes fully comply with Section 508 of the Rehabilitation Act, Information Technology Accessibility. (SDLC, The Rehabilitation Act of 1973, Section 508). Contractor must be fully staffed prior to contract commencement. Contract personnel must have a favorable Low Risk security clearance prior to being given access into the Government facility and/or IT Computer Systems. The contractor shall have workers complete the Security Awareness Training off-site by first registering for an eAuth ID at the following website: http://www.eauth.egov.usda.gov/ Once the eAuth ID has been obtained, the contractor employee must register and complete the Security Awareness Training at the following website: http://www.aglearn.usda.gov/ The Contractor shall contact the following individual to set-up fingerprinting: Kansas City, MO location: Carmen Pitts, OD/EPD, phone: 816-926-6612 - Office Email: Carmen.pitts@kcc.usda.gov St. Louis, MO location: Not available at this time. The contractor shall execute non-disclosure agreements when it works with sensitive or proprietary information from other employees, contractors, firms not having Government contracts, academic institutions and other non-profits. The Contractor shall agree not to discuss with, disclose, release, reproduce or otherwise provide or make available the data, or any portion thereof to any other Government or non-government employee, person or organization unless that other employee, person or organization has signed a non-disclosure statement. Work on this project requires that personnel have access to Privacy Information. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations. This is not a Request for Proposal (RFP). This is a Sources Sought only to ascertain the market availability of firms that are SBA Certified Small Disadvantaged Businesses only and can provide the support outlined which falls under NAICS 541512.
Web Link: FBO.gov Permalink
(https://www.fbo.gov/spg/USDA/FSA/MSD/AG-3151-SS-11-FarmLoanProgramInformationDeliverySystem/listing.html)
Place of Performance: Address: USDA/FSA/ITSD/FCAO, 6501 Beacon Drive, Kansas City, Missouri, 64133, United States; Zip Code: 64133
Record: SN02499410-W 20110716/110714235709-6c3f3c8da08baf90e1f0516164f7b7af (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

D -- Farm Loan Program Information Delivery System (FLPIDS)