MODIFICATION
D -- Admendment 1 - Admin. -Second SOW, SOW not revised
- Notice Date
- 3/20/2008
- Notice Type
- Modification
- Contracting Office
- Environmental Protection Agency, Administrative Contract Service Center, 1200 Pennsylvania Avenue, Nw, Washington, DC 20460
- ZIP Code
- 20460
- Solicitation Number
- RFQ-DC-08-00124
- Response Due
- 4/7/2008
- Archive Date
- 5/7/2008
- Point of Contact
- Point of Contact, Donna Blanding, Purchasing Agent, Phone (202) 564-1130
- E-Mail Address
-
Email your questions to U.S. Environmental Protection Agency
(blanding.donna@epa.gov)
- Description
- NAICS Code: 541512 STATEMENT OF WORK - BUSINESS PROCESS AND APPLICATION REENGINEERING The Office of Administration has developed a WEB-based portal, Office of Administration Information System (OASIS), for all Specialized Amoderate@ applications with vital information which requires that data be carefully stored, but accessible. Moderate applications must be given Special Handling to minimize opportunity for of harm resulting from loss, misuse, unauthorized access or information modification. The intent is to reengineer business processes and implement these changes into the system for better flow of application use. DESCRIPTION: The Contractor shall provide business process reengineering and system development life cycle support for the Office of Administration Services Information System (OASIS). OASIS is a secure portal that provides EPA employees access to eighteen OARM/OA custom applications. The work required under this Task includes: analysis of the existing OASIS custom application and to document the As-Is state; status and workflows. Then make determination for the To-Be state; with GAP Analysis to identify alternatives for achieving the To-Be state; with design of the new applications. The Contractor shall develop new workflow processes for each OASIS application. The new workflow processes must provide process improvements and eliminate redundant steps. The period of performance shall be for six months from date of award. This requirement also has a 6-month option period. OASIS TECHNICAL OVERVIEW: OASIS is a custom in house written application, developed in ColdFusion MX8 as the front end and Oracle 10g database. The application is accessed by over 500 users on a daily basis. All code in this effort will be written by the EPA in house IT staff. OASIS currently has three environments, production, development and test. The servers in each environment are Dell Power Edge servers. Below is a list of subtasks and the work that is required for each. Subtask 1 - Analyze and Evaluate As-Is Business Processes for OASIS Applications The Contractor shall conduct an independent review and or audit of the business processes and applications that comprise OASIS. The goal of this review is to assess current business processes, workflow, and to document the As-Is state. The Contractor will interview OASIS users to assess and document current business processes and workflows. The goal of this review is to assemble all information necessary to document the As-Is state. Deliverable: Current State Assessment Report Subtask 2 - Document To-Be Environment and Alternatives The Contractor shall conduct interviews with existing users of the OASIS applications and OARM/OA management to identify expected (desired) business and operational goals. For new OASIS applications, the users will be interviewed and all requirements are gathered to ensure a detailed workflow process is mapped before software design shall start. The Contractor shall describe how the business processes can be improved and simplified, and how the users' roles can be managed to deliver the functionality required in a more streamlined manner. The Contractor shall identify how to better address the users' needs and how to simplify their processing activities. The Contractor shall recommend a data infrastructure that supports integrated, online information and services center, which serves as a single point of access to all of the OARM/OA activities within a Portal environment. The structure of this environment shall be expandable, and `capable of supporting the addition of future applications. The environment shall be consistent with the OARM/OA web, security and privacy policies. The Contractor shall provide a To-Be process model describing the above environment, and the reengineering and redesign requirements necessary to achieve it. For each application, the Contractor will develop a requirements specification that addresses functional, operational and system performance considerations. For the OASIS portal and each application, the Contractor will identify the operational rules that define system security requirements including access and roles, and how the business processes can be improved and simplified. In combination, the To-Be requirements for each application and the OASIS portal will comprise the To-Be state. Deliverable: Future State Summary Report Deliverable: Future State design with new requirements for workflows Subtask 3 - System Reengineering and Design Implementation Following approval from OARM/OA management, the Contractor shall perform system engineering and design activities to implement the To-Be environment. This will include definitions, integrated system design, database design and other design activities. This effort will also address system conversion activities. All system design must be done using EPA approved software products and all implementations must comply with established agency standards. The portal and supporting applications will be designed to achieve a common, standard "look and feel," with a central system of role based security that supports the users and the OARM/OA IT Team. The portal will be engineered to permit the IT Team to add new applications, and include features such as help desk tools, email communications and user-oriented Help systems. Administrative functionality should be designed to simplify system maintenance processes and to leverage and optimize existing resources. This includes providing users with tools to manage and process their data more efficiently. Deliverable: Functional OASIS Portal and Applications (Readiness Plan) Subtask 4 - Testing Activities The Contractor shall coordinate OASIS testing activities to validate system performance. This will include the development of scripts to support detail end-to-end testing. System Integration Testing will be conducted by the Contractor & EPA team. User Acceptance Testing will be coordinated by the contractor and executed by EPA personnel. The Contractor shall remediate any changes or updates identified during testing. Change Requests (CRs) will be generated during testing to identify system problems and enhancements. The Contractor shall manage the CR process and ensure that all required corrections or changes are implemented and re-tested. A test plan and acceptance criteria will be developed and delivered to the Contract Officer Representative (COR). Deliverables: OASIS Portal and Application Test And Acceptance Plan including Test Scripts Test Analysis Report Subtask5 - Training The Contractor shall develop specific training materials to support the implementation of the new portal and applications. The Contractor shall evaluate training alternatives including: computer-based training (CBT), online or bubble help, classroom training sessions, "webinar" delivery and other alternatives. The Contracting Officer's Representative (COR) will review and approve the training delivery strategy prior to action by the Contractor. Deliverable: Training Plan and Products Subtask 6 - OASIS Implementation Following successful Testing and Training, the Contractor shall coordinate implementation of the new OASIS portal and applications with the OARM/OA IT group. Coordination with this group is essential to ensure the timely retirement of existing systems, conversion of existing application data, and, the implementation of the new portal and applications. Deliverable: To-Be State For OASIS Applications and Implementation Plan Subtask 7 - Other Deliverables In addition to the Deliverables associated with each subtask above, the Contractor shall be required to provide the COR with a Status Report for the period ending the 15th and the end of each month. The Status Report will be due within 3 business days following these dates and will address progress since the previous report. These Status Report shall be delivered to the COR in writing unless other arrangements are made between the Contractor and the COR. Cost Reporting - to include staff hours and funds expended during the prior month-end and inception-to-date; Accomplishments during the period; Project Risks and Contingencies; and, Upcoming schedule - initiatives or delivery items. User Guides Help Features ACCEPTANCE CRITERIA Delivery and product acceptance will be performed by the COR and will be based on meeting the criteria established for each deliverable. SECURITY CONTROLS The Contractor will be required to complete National Agency Check and Inquiry (NACI) paperwork within 10 working days of receiving the signed Task Order. OASIS Customer Application description Summary: 1. The Change Request application is design for requesting the following information electronically. 1. New employee PC setup 2. LAN IDs 3. Lotus Notes ID 4. Printer setup (Local and or Network) 5. PC moves, adds, changes and deletes 2. The COOP Action Tracking Systems (CATS) is design to track COOP actions. The OARM COOP staff has access to this application to make updates and view actions that are assigned. Actions are tracked by Org, Assign Date, Requestor and Priority. 3. The Print Job Tracker is design for EPA Print shop to track bulk printing and invoicing. 4. The Mail Center Application provides a mean to track two types of mail. 1. Critical Mail Tracking 2. Integrated Mail Management Critical Mail Management The tracking of critical mail is of great important to EPA and EPA tracks these critical items based on the following requirements. 1. Carrier 2. Mail Delivered Log 3. Mail received daily log 4. Mail received by carrier 5. Mail assigned to an EPA Massager 6. Mail not signed for 7. Mail delivery details 8. Mail delivered to an assignee Integrated Mail Management The Integrated Mail Management module has several sub-modules for tracking EPA internal mail deliveries. The first module Data Management which supports: Group Changes, Employees,Headquarters, Nationwide,All locations,Individual that have left EPA (Separated), 5. The Administration module provides a means to update address, locations, carrier and information. 6. The Warehouse Management Modules is an online inventory tracking system design to track items that are stored at the warehouse 7. This module is used to track all help desk request for support calls. Calls are tracked by individual names, location, and problem type. 8. The COOP Contact List is an online tool for making updates to the actual COOP list. This information is converted into an ICON and placed on each COOP Staff members Blackberry. 9. The credential Badging System was design to be an online system for all ten regions and headquarters. The credential badging systems will help each regional security rep submit, track and received approved credentials from headquarters. The following features are available in the credential badge system. 1.The ability to capture a digital photo and upload the photo for a credential badge 2.The ability to capture a digital signature and upload the photo for a credential badge 3.The ability for each region to submit a request for a new credential electronically. 4.The ability for headquarters to process any region's credential electronically. 10. The Parking and Transit Subsidy System was developed to track EPA employees parking and transit. The transit module tracks Smart benefits, Metro checks, enrollments and disbursements. 11. The Driver Tracking Module was developed to track EPA vehicle mileage, gas and driver assignments. Each vehicle is tracked and driver is tracked based on pickup assignment and or vehicle check-out and usage. 12. The Combinations, Locks, Incidents, and Keys & Safe (CLIKS) was developed to track all keys, locks and safes within EPA Headquarters. This part of the physical security to ensure each room and the keys are assigned and not duplicated. 13. The Fitness Center Management Module tracks EPA employee that use the fitness center and their pay history. Each time a person visit the fitness center they must sign into the fitness center module. By doing this we have a record of each visit. 14. The Action Tracking System was designed based on requirements for an online tracking system with the ability to re-assign actions down to the staff level. The Director and or their administrative assistance can assign an action to one or multiply division heads. The division head can take the action or re-assign it to one of their staff members. Staff members can not re-assign an action; they can only complete the action.
- Record
- SN01537896-W 20080322/080320234158 (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 |