resulting from this RFP. Work peformed must conform to project management, systems engineering methodology, and other IT standards in effect for HSD. ASPEN’s Current Functionality Summary of functional areas in ASPEN Benefit Issuance: Benefit Issuance provides mechanisms to deliver benefits to eligible recipients through multiple payment methods while maintaining a detailed benefit history. ASPEN supports the rapid delivery (i.e. near real time) of benefits depending on the Electronic Benefit Transfer (EBT) Contractor. Workers can research issuances by drilling-down to the individual level for each benefit month. Benefit Recovery: ASPEN functionality determines when benefits have been over-issued based on date and data dependent logic built in to the rules engine. When appropriate benefit recovery claims are generated for certification by field staff or sent as an alert to specialized staff, ASPEN will establish automated recoupment processing or repayment plans for the case. Case Maintenance: ASPEN provides functionality to support the many tasks that Workers have to perform throughout the lifecycle of a case. ASPEN tracks due dates, receipt of verifications, and historical records, and, based upon the data in the system, it will recalculate benefits. ASPEN also schedules appointments and provides calendaring with distinct options that can be modified at the worker level; in addition there are other options that are controlled at the supervisor level. Some of the key Case Maintenance features within ASPEN includes: recertification, provider management, mass change, and inquiry. Client correspondence: Notices, Forms, and Referrals are dynamically generated within ASPEN from a library of templates. Fields on the correspondences are populated with data entered or calculated in the system. Caseload Management: ASPEN functionality keeps staff informed of their workloads and facilitates management with automated caseload realignment and reminder capabilities. The caseload management feature is comprised of three major functions: task and reminder alerts, case transfers, and caseload reassignment. Eligibility Determination/Benefit Calculation (EDBC): This functionality is the focal point of the ASPEN system and supports the base business rules that determine the Client’s eligibility across all requested programs. EDBC is based on a Rules Engine that reads a series of Decision Tables based on program policies and procedures. Historic User and Data Maintenance: ASPEN allows for audit trails that create records of data changes and specific user actions. This information allows case data updates to be viewed for auditing and management purposes.
1.5 APPENDIX 1-E STAFF WORKSHEET FORM The purpose of this form is to identify how Offerors staffing model will be resourced over the term of the contract. The estimated number of staff for each identified staff position should be extended through the contract term. All staff will be considered full-time equivalents unless identified by half-time (.5) or quarter-time (.25). Example: if 2-1/2 System Managers will be on staff during first year, then indicate 2.5 in table. Add cells as required. Role NUMBER OF STAFF IN SFY1 NUMBER OF STAFF IN SFY2 NUMBER OF STAFF IN SFY3 NUMBER OF STAFF IN SFY4 NUMBER OF STAFF IN Optional SFY5 NUMBER OF STAFF IN Optional SFY6 NUMBER OF STAFF IN Optional SFY7 NUMBER OF STAFF IN Optional SFY8 [Continue listing as needed.] Total Positions * Key Staff
Configuration / Change Management (See Section B.12 for detailed tasks and activities) Follow the State’s established configuration management processes for all phases of the SDLC Maintain and regularly update the Configuration Management Plan to represent the most current processes and procedures Collaborate with the State to recommend and support the creation and implementation of improved Change management processes and Quality assurance checks Provide new configuration management processes for ASPEN (as directed by State management) to provide improved service delivery and a solid foundation for development, testing, training, and production in compliance with SUITE / SEM standards Design and implement new standards and processes to allow for requirements traceability and reduce the risk of negative cross-functional impact when application changes are delivered Review Change /Configuration management processes to verify compliance with SEM standards and improve processes such as: The ability to trace work requests to the original activities defining the software artifacts and system modifications related to incorrect functionality The ability to trace test scenarios to the development activities related to the components being tested