Word by wangnianwu

VIEWS: 0 PAGES: 30

									                     AOSOS Planning Budget – PY 2004




                America’s One Stop Operating System
                         Planning Budget PY 2004




Revision Date: 6/17/04
Document Version: V3.1


                                                              Document Version 3.1
                                   Page 1 of 30                            6/17/04
                                        e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                              AOSOS Planning Budget – PY 2004

                                                       Table of Contents



Revision History .................................................................................................................... 3
Introduction ........................................................................................................................... 4
Assumptions ......................................................................................................................... 5
Out of Scope Activities * ....................................................................................................... 6
AJBSC AOSOS Organization Chart...................................................................................... 7
Job Descriptions ............................................................................................................... 887
Budget Information ..................................................................................................... 131312
   AOSOS Proposed Budget Worksheet PY 2003....................................................................... 171715
   AOSOS Planning Budget PY 2003 Staffing Levels .................................................................. 181816
Maintenance and Support Activities ** ........................................................................ 191917
Hardware Lifecycle Costs ........................................................................................... 232321
Support and Implementation Activities ........................................................................ 242422
Appendix A - Interested State WBS ............................................................................ 252523
Appendix B - Policies and Procedures ........................................................................ 282826
   AOSOS Standard Change Control Process ............................................................................ 282826
   AOSOS Standard Change Control Process Diagram ............................................................... 282826
   AOSOS Fast Track Change Control Process .......................................................................... 282826
   AOSOS Fast Track Process Diagram .................................................................................... 282826
   AOSOS Bug Procedure ........................................................................................................ 282826
   AOSOS Bug Procedure Diagram ........................................................................................... 282826
Appendix C - Maintenance and Support Observations ............................................... 292927




                                                                                             Document Version 3.1
                                                                  Page 2 of 30                            6/17/04
                                                                       e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                      AOSOS Planning Budget – PY 2004

                                           Revision History
 Document   Revision Date
  Version                         Author                         Revision Comments
V1.0        4/07/03         J. Novak             Initial Draft
V2.0        5/02/03         J. Novak             Final Revision. Removed Draft Watermark.
V3.0        5/22/04         M. Bloss             Initial Draft PY2004
V3.1        6/17/04         M. Bloss             Final Draft PY2004




                                                                            Document Version 3.1
                                                 Page 3 of 30                            6/17/04
                                                      e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

                                              Introduction
America’s Job Bank Service Center (AJBSC) is pleased to present this planning budget/work plan to the
AOSOS Consortium. This proposal represents our best effort at estimating operational costs for PY years
2004 and 2005 and projected revenue based on information provided by the Consortium. The actual
planning budget may vary from this version as we have the opportunity to meet with the AOSOS
Consortium and determine the desired services to be provided by AJBSC.

Our basic planning assumptions for this document focus on identifying baseline Maintenance and Support
Costs required to make certain that the AOSOS software continues to be operational. Funds are also
identified for administrative costs to allow the consortium to function effectively. Any major enhancement
or new functionality will be treated as a new development project. As a separate project it will be scoped,
estimated, and supported by a new Statement of Work.

After the AOSOS Consortium approves a planning budget/work plan, the AJBSC will work with the
Consortium to execute the plan effectively.

The definition of the mix of maintenance and support activities and code enhancements to be included in
an individual code build will follow the procedures developed by AJBSC and approved by the AOSOS
Consortium.




                                                                               Document Version 3.1
                                                    Page 4 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                    AOSOS Planning Budget – PY 2004

                                          Assumptions



   Resolution of critical customer support issues will have priority over new functionality.
   Functionality will be integrated into the application as resources permit. This is very vague, but was
    used last year. If the code builds and patches include the functionality prioritized by the
    Consortium, it might be better to remove this statement and reference functionality in the statement
    below.
   Effective July 1, 2003, staff resources will be leveled and held constant through June 2005
   A cadre of critical core staff will be maintained to ensure continued support for the application
   Not all staff will be dedicated full time to the AOSOS project, and there will be times when fractional
    staff will be unavailable while they are working on other projects.
   Carry-In from PY 2002 was $1,042,000.
   Carry-In from PY 2003 is estimated to be $2,600,000.
   $300,000 will be set aside beginning PY 2002 for hardware replacement and will be held in reserve
    until needed.
   $300,000 will be set aside beginning PY 2002 for contingency and will be held in reserve until
    needed.
   Based on costs associated with the PY 2003 operation, $2,000,000 is being set as the baseline
    cost for maintenance and support activities to keep AOSOS operational in the initial seven member
    states.
   AJBSC will participate in all Steering and Scope Committee conference calls.
   Signed subscription agreements from all States to be received by AJBSC by July 1, 2004.
   States will continue to become more self-sufficient and use their own (and pooled state) resources
    for the resolution of state specific system administration and database issues.
   Code builds will be limited to no more than two releases per program year and will incorporate the
    functionality prioritized and accepted by the Consortium. The number of patches will be
    determined by the Scope and Steering Committee.
   Consortium States to receive build support for no more than two hardware environments.
   Desk level user training materials to be the responsibility of Consortium States.
   Legacy to Current Version conversion routines will not be done with each new build, but will only
    be created when there is a specific need.
   AOSOS Consortium State representatives will be active and available as necessary. This includes,
    but is not limited to:
         o Providing members and leadership in workgroups and committees
         o Identifying proposed or passed legislation and assessing the impact on the application
         o Identifying business and subject matter experts and supporting documentation for
              enhancements
         o Resolving issues as necessary
         o Developing testing and acceptance criteria
         o Providing project approvals




                                                                           Document Version 3.1
                                                Page 5 of 30                            6/17/04
                                                     e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                   AOSOS Planning Budget – PY 2004

                                Out of Scope Activities *




   Interested State Support - see appendix A for a Work Breakdown Structure (WBS) of these
    activities
   Proposal development for states investigating AOSOS
   New State Implementation Support for states not yet members of the AOSOS Consortium
   Marketing activities
         o Trade shows
         o Product demonstrations
         o Participating in Consortium Marketing Conference Calls

*Can be made available on a fee basis




                                                                        Document Version 3.1
                                             Page 6 of 30                            6/17/04
                                                  e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

                                AJBSC AOSOS Organization Chart
Don Sutherland is in the Project Director’s Office. I thought he was a member of the Consortium. As
Project Office employee, Consortium voting seems like a conflict of interest.

The same amounts of money are being spent on maintenance and support this year as last, but there are
changes in staffing levels. Do these reflect needs/deficiencies that were identified during the past year? Or
is it just more of an organizational change (ie: QA is under the QA Manager and the Project manager?)


QA Manager and QA tester have been reduced from 3.0 to 1.95 FTE
Project Manager increased from .5 to .75
Technical and QA Programmer are new for this year --- does this QA person do some of the tasks of the
previous QA under Martin?
Business Analyst decreased from 1.5 to 1
Programmers reduced from 4.5 to 4
System Administrator is new,
Implementation Support and Operations were removed – who takes over their responsibilities?




                                                                               Document Version 3.1
                                                    Page 7 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
         AOSOS Planning Budget – PY 2004

                   AOSOS Project Director's
                           Office
                      Mike Bloss / Don
                         Sutherland
                            (0.3)




                                                    AOSOS Project
  QA Manager                                          Manager
  Martin Stout                                       Nancy Scott-
     (0.3)                                             Horan
                                                        (0.75)


                                                        Lead
    Quality
                                                     Programmer
Assurance Tester
                                                        (0.5)
     (1.65)



                                Technical Liaison                   Programmers
                                     (0.5)                              (4.0)




                                QA Programmer                       Data Architect
                                     (1.0)                              (0.5)



                                                                      System
                                Business Analyst
                                                                    Administrator
                                      (1.0)
                                                                       (0.5)



                                                                         DBA
                                                                        (0.25)




                                                         Document Version 3.1
                              Page 8 of 30                            6/17/04
                                   e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                         AOSOS Planning Budget – PY 2004

Job Descriptions
    System Administrator and Lead Programmer are not defined, but are on the
                               preceding Chart.
Project Manager:

This position is responsible for and must have a thorough understanding of the overall definition, planning,
execution, monitoring and closeout of each AOSOS project/release. This individual must oversee the
development, installation and acceptance of AOSOS projects and releases. This individual must
coordinate with their subordinate Managers to complete the delivery of each tested application release.
This person must ensure customer satisfaction by managing the details of overall project schedules and
deliverables. This individual also coordinates all phases of the project life cycle with project staff to ensure
the completion of projects on schedule and within budget constraints. The individual in this position must
have an understanding of the needs of the project users. While this individual is not expected to be the
business knowledge expert for the programs supported by AOSOS, the position requires that the individual
become familiar with the legislation and rules and determine who the appropriate business knowledge
experts are. This individual must also understand the skills and abilities of the staff reporting to them.

The individual in this position must provide insight into the maintenance needs of the AOSOS project as
well as support customer questions and complaints. This individual must assist in the problem resolution of
AOSOS application issues, if necessary. The person in this position must also recognize areas of needed
improvement and design new processes or procedures to correct or improve those areas.



Quality Assurance Manager:

This position is responsible for and must have a thorough understanding of the AOSOS application and
quality control/assurance methodologies.

The individual in this position manages a team of AOSOS testers who are the first line support for
application testing, verification and problem reporting/tracking. This position must have a thorough
understanding of how the AOSOS application interfaces with other systems. The person in this position
must also understand how the application is being utilized by the AOSOS Consortium States.

This position provides insight into the AOSOS application maintenance and conversion needs, and must
lead problem resolution of AOSOS application issues.


Quality Assurance Tester:

Under the supervision of the Quality Assurance Manager, the individuals in these positions are the first line
of support for application testing, verification and problem reporting/tracking. These positions must have a
thorough understanding of how the AOSOS application functions and how it interfaces with other systems.
These individuals must also understand how the application is being utilized by the AOSOS Consortium
States. These individuals may also field questions that are generated by users calling the 1-800 number or
sent to the OSOSCSC e-mail adress.
                                                                                Document Version 3.1
                                                     Page 9 of 30                            6/17/04
                                                          e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004




QA Programmer:

The individuals in these positions debug software products through the use of systematic tests to develop,
apply and maintain quality standards for projects. These staff members must develop and execute software
test plans, as well as maintain documentation of test results to assist in debugging and modification of
software. These individuals must also analyze test results to ensure existing functionality and recommends
corrective action. The individuals in these positions must also consult with other project staff in the
resolution of problems. These individuals may analyze and write test standards and procedures.



Business Analyst:

Under the general supervision of the Project Manager, the individuals in this position are responsible for
coordinating the planning, execution and monitoring of the various sub-projects delivered within each
release of the AOSOS application. These individuals provide technical assistance in identifying, evaluating
and developing systems and procedures that are cost effective and meet user requirements. This staff also
configures system settings and options; plans and executes unit, integration and acceptance testing; and
creates specifications for systems to meet business requirements. The individuals in this position must
work with the identified business knowledge expert as well as all users supporting the sub-project to
understand their needs. Staff in these positions must provide guidance to the user and other project staff to
insure work progresses within the limitations of the AOSOS project's schedule and scope and must also
maintain a strong bond of communication with users and other project staff. These individuals are also
expected to lead cross-functional linked teams to address business or systems issues.

These individuals must monitor the delivery of many sub-project deliverables to insure they meet the
expected quality and must also coordinate the validation and acceptance of many other sub-project
deliverables to insure that our user community's expectations have been met.

The individuals in this position must assist in problem resolution of AOSOS application issues, if necessary
and must also recognize areas of needed improvement and suggest new or improved processes or
procedures. These individuals may, based on level of need, perform work in areas such as customer
support, quality assurance, batch processing maintenance, and the care and maintenance of the
application.




                                                                               Document Version 3.1
                                                   Page 10 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                         AOSOS Planning Budget – PY 2004


Technical Support Liaison:

The individual in this position acts as liaison between the Consortium States and AJBSC to identify,
manage, schedule and track installation of new code and code patches to both test and production sties.
This person will respond to and resolve all field problems regarding hardware and software.

The individual in this position must have an extensive understanding of the technical aspects of the OSOS
application and infrastructure. This employee must work with project technical staff to provide answers and
advice on a large range of topics brought up by the technical representatives from each of the OSOS
Consortium States.

The individual in this position also assists with customer questions, concerns and complaints concerning
the OSOS application. This individual must work with the available resources appropriate to resolve the
OSOS customer concerns.

The individual in this position must cover some areas of responsibility for the following positions in the
event of the incumbent's absence;, OSOS Project Manager, AJBSC Quality Assurance Manager, and
subordinates.


Programmer:

Using experience with a variety of network technologies, individuals in this position develop applications,
using but not limited to C, C++ Java, XML, HTML, CGI, ASP, SQL, Perl, and Python, incorporating
database interactions and data modeling tools. Individuals in this position build applications using Internet
and Linux or Windows Development tools and must provide written design documents, test plans and test
results. These individuals must manage, develop, integrate and implement related applications
components, including front-end development, server-side development and database integration. These
individuals play a direct role in programming, maintenance, technical support, documentation and
administration of the applications. These individuals may research, track and gain understanding of new
web technologies to provide technical leadership in developing service applications and analyzing business
requirements as they pertain to Internet-related systems. Staff in this position may also, based on level of
expertise, function as a lead programmer, and coordinate the activities of other less senior programmers.


Database Administrator:

The individuals in this position plan computerized databases, including base definition, structure,
documentation, long-range requirements, operational guidelines and security. These individuals ensure
accuracy and completeness of data in master files and various support tools, such as base dictionaries,
and establish and maintain security and integrity controls. These staff members formulate and monitor
policies, procedures and standards relating to database management. These individuals are also expected
to propose and implement enhancements that will improve the performance and reliability of the system.


                                                                                 Document Version 3.1
                                                     Page 11 of 30                            6/17/04
                                                           e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

Data Architect:

The individuals in this position establish database management systems, standards, guidelines and quality
assurance for database deliverables, such as conceptual design, logical database, capacity planning,
external data interface specification, data loading plan, data maintenance plan and security policy. These
individuals will also document and communicate database design, and evaluate and install database
management systems. These staff members code complex programs and derive logical processes on
technical platforms as well as build windows, screens and reports and assist in the design of user interface
and business application prototypes. These individuals are expected to provide expertise in devising,
negotiating and defending the tables and fields provided in the database. These individuals adapt business
requirements, developed by modeling/development staff and systems engineers, and develop the data,
database specifications, and table and element attributes for an application. At more experienced levels,
the individuals in this position may help to develop an understanding of client's original data and storage
mechanisms. These individuals are required to determine appropriateness of data for storage and optimum
storage organization as well as determine how tables relate to each other and how fields interact within the
tables for a relational model.




                                                                               Document Version 3.1
                                                   Page 12 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                      AOSOS Planning Budget – PY 2004

                                    Budget Information




                                                                                       Document Version 3.1
                                                             Page 13 of 30                           6/17/04
                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning Budget 2004
v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1.doc
                                       AOSOS Planning Budget – PY 2004


                                                          Revenue

  5,000,000
                       $4,500,000




  4,000,000                                      $3,500,000




  3,000,000

                                                                                               $2,100,000
                                                                                $1,800,000

  2,000,000



  1,000,000



           0
                        PY02                       PY03                           PY04            PY05


                                                              State   Federal




What does NOA mean? Notice of Award? New Obligation Authority?
                                                                                                       Document Version 3.1
                                                                             Page 14 of 30                           6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning Budget 2004
                v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1.doc
                                  AOSOS Planning Budget – PY 2004

                                       Operational Planning Budget

7,000,000
               $6,218,000

6,000,000

                                     $4,555,000                            $4,597,187
5,000,000
                                                        $4,439,187


4,000,000


3,000,000


2,000,000


1,000,000


       0
            PY02               PY03                PY04                 PY05
                NOA              Carry In          Operational Budget          Carry Out




                                                                                                   Document Version 3.1
                                                                         Page 15 of 30                           6/17/04
                                                     e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning Budget 2004
            v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1.doc
                                   AOSOS Planning Budget – PY 2004


                                 Operational Budget by Category of Expense

6,000,000

                   $5,176,000

5,000,000



4,000,000



3,000,000


                                                                             $1,942,000                   $1,942,000
                                              $1,902,813
2,000,000



1,000,000



       0
                    PY02                       PY03                           PY04                          PY05

                                Maint & Support            New Development                New Hardwware
                                HW / SW Maintenance        Administration                 Other




                                                                                                   Document Version 3.1
                                                                         Page 16 of 30                           6/17/04
                                                     e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning Budget 2004
            v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1_NevadaComments.docAOSOS Planning Budget 2004 v3.1.doc
                       AOSOS Planning Budget – PY 2004

                          AOSOS Proposed Budget Worksheet PY 2003
Add note on this page indicating that enhancements will come out of reserve $$

                                             PY 2002       PY 2003       PY 2004       PY 2005
                                             Dollars       Dollars       Dollars       Dollars
          Revenue
          Estimated Revenue                                  3,500,000     1,800,000     2,100,000
          Carry-In                                           1,055,000     2,639,187     2,497,187
          Total Estimated Revenue                            4,555,000     4,452,187     4,610,187

          Planning Budget
          Administration                                        75,000        75,000        75,000
          M&S (including NYSDOL staff)                       1,384,000     1,694,000     1,694,000
          New Development                                      293,813             0             0
          HW/SW Maint / VPN / Trvl                             150,000       173,000       173,000
          Marketing                                                  0             0             0
          Capital Expenditures                                       0             0             0
          Total Planned Expenses                             1,902,813     1,942,000     1,942,000

          Carry Out                            1,042,000     2,639,187     2,497,187     2,655,187

          Reserves
          Subscription Fee paid in advance                                   300,000
          Hardware Replacement                   300,000       300,000       300,000       300,000
          Contingency                            300,000       300,000       300,000       300,000
          Total Reserves                         600,000       600,000       900,000       600,000




                                                                          Document Version 3.1
                                              Page 17 of 30                            6/17/04
                                                    e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
      AOSOS Planning Budget – PY 2004

         AOSOS Planning Budget PY 2004 Staffing Levels



Project Manager(s) (NYSDOL)           1.05    140,000
Technical Laison                      0.50     98,000
QA Manager (NYSDOL)                   0.30     40,000
QA Programmer                         1.00    150,000
Lead Programmer                       0.50     95,000
Business Analyst                      1.00    190,000
Programmers                           4.00    680,000
Quality Assurance (NYSDOL)            1.65     75,000
Data Architect                        0.50     95,000
Data Base Administrator               0.25     46,000
System Admin                          0.50     85,000

                                     11.25   1,694,000




                                                          Document Version 3.1
                              Page 18 of 30                            6/17/04
                                    e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                       AOSOS Planning Budget – PY 2004

                             Maintenance and Support Activities **
Add monthly reports to Maintenance and Support activities or wherever it makes the most sense.

    Customer/Technical Support

    1. Provide Customer support for issues that cannot be resolved by a States’ helpdesk. Provide 1-800
       number support in the event of a catastrophic code failure. Support will be provided Monday -
       Friday from 8:00 am to 5:00 PM (eastern time).
    2. Provide Hardware/Operating System support for issues that cannot be resolved by a State’s
       helpdesk.
    3. Answer questions beyond the customer’s knowledge on requirements, batch processes,
       application, API process, reports, implementation, error logs, etc.
           a. Requirements
                      i. Research documentation for specific requests on requirements.
                     ii. Write up potential problems that are discovered through questions or verify that a
                         problem is not an issue by referencing the requirements.
                    iii. Clarification on misunderstandings of requirements.
           b. Batch Processes
           c. Application Support
                      i. Clarify misunderstandings in how the application should work.
                     ii. Maintain appropriate documentation.
           d. API Process
                      i. Address specific questions about API functionality.
           e. Reports
                      i. Review potential bugs in a report identified by member states.
           f. Implementation
                      i. Review and respond to build questions including: sequence of events or missed
                         steps.
                     ii. Documentation clarification on implementation documents.
                    iii. Running reports questions.
                    iv. Hardware configuration problems.
                     v. Provide just-in-time conference call, with supporting documentation to explain the
                         details each release and the conversion requirements.
                    vi. Plan, manage and test the procedures for the OSOS application releases, patches
                         and 3rd party upgrades on internal test platforms.
                   vii. Documents, distributes and reviews step-by-step procedures for application
                         releases, patches and 3rd party upgrades.
                   viii. Create and distribute/post source code deliverables.

            g. Error Logs

    4. Help users maintain data integrity
           a. Scripts may sometimes be written to correct state specific problems, which includes:
                    i. Documentation how to run.
                   ii. Answering questions.
                  iii. Conference calls.

                                                                              Document Version 3.1
                                                  Page 19 of 30                            6/17/04
                                                        e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004


Maintaining Batch Processes and overall consistency with other systems:
   1. Review each major and patch release for potential changes in the following batch processes based
        on changes within a bug or Change Control Request. The impact to each of the following systems
        is reviewed and estimated. Documentation updates are made to reflect the changes.
             a. Data Exchange (Inbound/Outbound)
             b. IVR
             c. Wage Data Interface
             d. API Process
             e. Fiscal Interface
             f. DART Extract Process
             g. TAPR Extract Process
             h. Mandated Domain updates
             i. 21/28 Month batch process


Implementation Support (for States in production) - Support will be provided in accordance to the
consortium agreed upon schedule on a first request first served basis with priority going to production sites
first followed by consortium state test sites.

    1. Support State Builds
           a. Pre-build conference calls with states.
           b. Document the build process.
           c. Monitor progress during state builds (test/prod).
           d. Maintain email chain with state staff during state builds.
           e. Keep statistics on state builds.
           f. Help state support staff, troubleshoot in the event of a problem occurring.
    2. Internal Builds
           a. Build internal QA sites.
           b. Build Demo, RVL, RVS sites.
           c. Run reports for all the internal servers.
           d. Upgrade 3rd party software for all internal servers.
           e. Monitor hardware.
           f. Work with DBA staff for schema updates.
    3. Hardware Support
           a. Answer state specific AOSOS hardware questions.
           b. Maintain hardware diagrams and configuration information.
           c. Make hardware upgrade recommendations.
    4. Production State Conversion Support (if required by a schema change)
           a. Current states (upgrade conversion)
                      i. Release scripts and documentation.
                     ii. Conference calls to support upgrade conversion process.
                    iii. Answer questions before, during and after states perform the upgrade.
                    iv. Respond to problems that occur.
                     v. Follow up steps support.
    5. Updating Build scripts on every release.
                                                                                Document Version 3.1
                                                    Page 20 of 30                            6/17/04
                                                          e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                         AOSOS Planning Budget – PY 2004

   6.    Maintain the AOSOS Info site and State’s FTP sites
   7.    Develop and distribute technical documentation.
   8.    Provide off hours support for production sites for non-application release activities.
   9.    Provide application release support for State’s test platforms.
   10.   Provide application release support for States’ production platforms.
   11.   Posting of new source code to proper FTP sites.


System Maintenance and Support

   1. Monitor system for 3rd party updates including Solaris, Oracle, IE, etc.
           a. Monitor websites/newsgroups for version updates.
           b. Verify critical nature of updates.
           c. Schedule upgrades.
           d. Compile/test upgrades.
   2. Designing and coding application changes for 3rd party upgrades.
   3. Fixing bugs that are critical to the application running properly
   4. System Performance Issues
   5. AOSOS Information Site changes
           a. Documentation repository maintained for all OSOS documents which include:
                    i. READMEs (Release Notes)
                   ii. Implementation Documentation
                  iii. Business Requirements
                  iv. Change Control documents
                   v. AJBSC and State specific documentation
   6. Reviewing and updating business requirements as needed.
   7. Reviewing and updating user documentation as needed.
   8. Research of technical feasibility for customer requested solutions.
   9. Hardware lifecycle planning.


Bug Maintenance - Testing will be done in conjunction with States on the Demo, RVL and RVS sites. Bugs
will be addressed in priority order as determined by the Scope Committee as resources permit.

   1.    Review, recreate, and regress customer bugs.
   2.    Review submitted proposals.
   3.    Estimate work effort for bugs/CCRs.
   4.    Develop issues and coordinate resolutions.
   5.    Design solutions.
   6.    Write code for bugs/CCRs.
   7.    Perform Quality Assurance testing for all code changes.
             a. Plan, manage, coordinate and system test code corrections.
             b. Assist and facilitate user acceptance testing of code corrections.
             c. Review and distribute documentation.
             d. Perform pre-release unit, load, stress, and integration testing.
             e. Manage, coordinate and track AOSOS code enhancement errors.
             f. Assist and facilitate user acceptance testing of code enhancements.
                                                                                 Document Version 3.1
                                                     Page 21 of 30                            6/17/04
                                                           e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                       AOSOS Planning Budget – PY 2004

   8.    Update user documentation for bugs/CCRs.
   9.    Update business requirements for bugs/CCRs.
   10.   Schedule releases.
   11.   Maintain scope for releases.

Project Management - Standard Project Management processes will be provided..

   1. Provide Project Management in the following areas:
          a. Initiation – Definition of scope and schedule for project.
          b. Planning – Elaboration of project schedules, development of business rules, and planning
              of user acceptance.
          c. Execution – Development of application.
          d. Monitoring – Oversight of quality assurance, schedule control and user acceptance.
          e. Closing – Compilation of lessons learned and archival of project documents.


**Unless otherwise noted above, our target is that all requests will be acknowledged within 24
hours and either be answered or given an estimated date of resolution within 3 to 5 business days
of receipt.




                                                                            Document Version 3.1
                                                Page 22 of 30                            6/17/04
                                                      e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

                                      Hardware Lifecycle Costs

This includes hardware and support costs for new hardware. Not included are possible changes to
Oracle license costs.

Platform Replacement Plan as of April 2003
Purchasing all of the equipment at once, including three years of Silver Support.

Hardware:

        4 V880           $157,520
        7 V240           $ 53,795
        1 v100           $ 2,985
        Sub-Total        $214,300

Support:

        4 V880           $22,548
        7 V240           $29,988
        1 v100           $ 1,584
        Sub-Total        $54,120


1-Year Plan Total (includes 3 years support) - $268,420
                                                     =====




                                                                               Document Version 3.1
                                                   Page 23 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

                              Support and Implementation Activities
These activities will be recorded by AJBSC and reported back to the Consortium States as part of a
Monthly Report of Services.

As long as there is a monthly report of services, the detail included in last year’s plan would not need to
be in the Plan. (Last year listed customer service issues which was a sample of the issues resolved or
addressed)




                                                                               Document Version 3.1
                                                   Page 24 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                        AOSOS Planning Budget – PY 2004

                                Appendix A - Interested State WBS
This appendix will be removed per June 24 Steering meeting

An “Interested State” is defined as any State who has expressed interest in receiving detailed information
on the implementation and use of AOSOS for their State. Representatives of “Interested States” are not
AOSOS Consortium members.

Critical project team members include individuals in the America’s Job Bank Service Center/OSOS team,
the Interested State and other Consortium States.

The work breakdown structure (WBS) defined within this document represents the suggested approach to a
State Interested in developing a One-Stop Feasibility Study. This WBS is intended to be a high-level
review of the tasks that need to be completed. Bolded tasks are those that are either in part or entirely the
responsibility of the AJBSC to complete. It is estimated that representatives of AJBSC would commit a
minimum of 570 hours in the completion of this effort.

AJBSC - Director                                        25
AJBSC - Project Manager                                 75
AJBSC - Implementation Manager                         175
AJBSC - Quality Assurance Manager                       10
AJBSC - Business Analysis                               40
AJBSC - Architect                                       45
AJBSC - Implementation Support                         110
AJBSC - Marketing                                       70
AJBSC - Lead Programmer                                 20
Total                                                  570

These estimates were arrived at using the Interested State Project template. Since the durations of many
tasks will be at the discretion of the Interested State, the total activity effort could exceed documented
estimates.

The actual duration of a specific project will be decided by the time in which the Interested State wants to
complete their One-Stop Feasibility Study. While it is hopeful that States are able to make their One-Stop
decision quickly, a short project schedule would have a major impact on limited consortium resources.
Conversely resource estimates for long project schedules may be underestimated as there will be a loss of
continuity and the possible need to repeat major tasks.


                                  Interested State Support WBS – High Level
                  Project Title - Conduct One-Stop Feasibility (Benefit – Cost) Study


1. Evaluate Benefits
   1.1. Research One-Stop application options
   1.2. Review application(s)
       1.2.1. Attend AOSOS Demonstration

                                                                               Document Version 3.1
                                                   Page 25 of 30                            6/17/04
                                                         e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                       AOSOS Planning Budget – PY 2004

     1.3. Review documentation for application(s)
     1.4. Determine the ability of each application to meet State’s needs
         1.4.1. Evaluate ability of the application to be customized
         1.4.2. Address application functionality questions as they arise
         1.4.3. Evaluate State’s use of AOSOS application
     1.5. Define State benefits
2.   Finalize/document benefit analysis
3.   Develop fact finding questionnaire
4.   Complete questionnaire
5.   Address questionnaire issues as they arise
6.   Submit completed questionnaire
7.   Evaluate Costs
     7.1. Define Hardware/Software Specifications
         7.1.1. Determine Server requirements
              7.1.1.1. Provide recommended Server configuration
              7.1.1.2. Assess Server sizing requirements
              7.1.1.3. Evaluate growth requirements
              7.1.1.4. Design Server configuration
              7.1.1.5. Inventory State’s available Hardware
              7.1.1.6. Determine Server Location
              7.1.1.7. Address Server questions as they arise
              7.1.1.8. Perform Hardware Gap analysis
         7.1.2. Determine Desktops Specifications
              7.1.2.1. Provide Desktop minimum specifications required for AOSOS
              7.1.2.2. Inventory State’s current Desktop Configuration
              7.1.2.3. Address Desktop questions as they arise
              7.1.2.4. Perform Desktop Gap analysis
         7.1.3. Determine software licensing Specifications
              7.1.3.1. Provide AOSOS software utilization
              7.1.3.2. Inventory State software licenses
              7.1.3.3. Address software questions as they arise
              7.1.3.4. Perform Software Gap analysis
     7.2. Define required Skills
         7.2.1. Provide recommended skill set to support AOSOS
         7.2.2. Access State skill set
         7.2.3. Address skills questions as they arise
         7.2.4. Perform Skills Gap analysis
     7.3. Define Network Configuration
         7.3.1. Provide Network infrastructure recommendation
         7.3.2. Identify existing bandwidth utilization
         7.3.3. Inventory States Network infrastructure
         7.3.4. Address Network questions as they arise
         7.3.5. Perform Network Gap analysis



                                                                           Document Version 3.1
                                               Page 26 of 30                            6/17/04
                                                     e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                      AOSOS Planning Budget – PY 2004

    7.4. Define Conversion Methodology
        7.4.1. Provide data conversion specifications
        7.4.2. Inventory current One-Stop legacy data
        7.4.3. Address conversion questions as they arise
        7.4.4. Identify desired data conversion strategy
    7.5. Define Hardware/Network Support
        7.5.1. Provide Hardware/Network support options
        7.5.2. Address support questions as they arise
        7.5.3. Identify most desirable support scenario(s)
    7.6. Define Contractual method
        7.6.1. Provide Contractual options
        7.6.2. Address contractual questions as they arise
        7.6.3. Identify most desirable contract method(s)
8. Formulate/document cost estimate(s)/analysis
9. Evaluate Benefit and Cost analysis
10. Document State Decision




                                                                           Document Version 3.1
                                               Page 27 of 30                            6/17/04
                                                     e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                       AOSOS Planning Budget – PY 2004

                             Appendix B - Policies and Procedures

           Please refer to the Consortium Operational
                 Procedures for this information

So long as either the Operating Procedures or the Service Level Agreement are accepted by the
Consortium and the items referenced are in the accepted document, reference in the Plan is acceptable




                              AOSOS Standard Change Control Process

                         AOSOS Standard Change Control Process Diagram

                             AOSOS Fast Track Change Control Process

                                 AOSOS Fast Track Process Diagram
                                        AOSOS Bug Procedure

                                   AOSOS Bug Procedure Diagram




                                                                             Document Version 3.1
                                                 Page 28 of 30                            6/17/04
                                                       e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                          AOSOS Planning Budget – PY 2004

                      Appendix C - Maintenance and Support Observations


Findings

Typically it can be expected that 33% of the overall cost of the application will be devoted to development,
with the remaining 66% devoted to maintenance and enhancements.

Average development organizations spend 40% of the total maintenance and enhancement budget on
enhancements and 60% on maintenance activities. This used to be based on a 7-10 year useful life, but
now that timeframe is being squeezed to approximately 5 years.


Not sure I understand this finding. I would think enhancements would be included in development .




Assumptions

         Application is up and running
         Application has a useful life of 10 years
         Application has been in use for 2 years
         Application has a useful remaining life of 8 years



Metrics

We have an application that cost $20 million (33% of overall cost) to build

Using the above metrics, that means that another $40 million (66% of overall cost) should be spent over the
following 10 years (or $4 million per year.) We are at year three in the life cycle of the application.

Using the above metrics the following budget assumptions apply for years 3 through 10:

         Estimated Budget Needs                    $4,000,000 (100%)
         Estimated Enhancement Activities          $1,600,000 (40%)
         Estimated Maintenance Activities          $2,400,000 (60%)

Costs for the following are in addition to the above estimates

         Hardware Maintenance
         Hardware lifecycle replacement

                                                                                 Document Version 3.1
                                                     Page 29 of 30                            6/17/04
                                                           e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning
                      AOSOS Planning Budget – PY 2004

      Software license maintenance
      Circuit Costs
      Other Associated Indirect Costs

*Based on conversations with Matthew Hotle - Sector Chief of Research – Infrastructure,
Architecture and Development – Gartner Consulting

Should there be a reference to the Statements of Work?




                                                                         Document Version 3.1
                                             Page 30 of 30                            6/17/04
                                                   e4959320-6218-4bea-ac57-964035800b51.docAOSOS Planning

								
To top