Overview of Am.Net

• Developed using Microsoft .Net. development tools and third party .Net based development products

• A “Windows Forms” application – web enabled but not browser based

• Client computer requirements are comparable to Am4 – runs faster on faster hardware 

Overview of Am.Net

• Requires Windows 2000 or higher OS

• Compatible with Vista, but we are still tweaking the Vista client installation

• The Am.Net Server must be running IIS, at least 2GB of server memory is recommended (especially for large states)

Overview of Am.Net

• Uses the same SQL Server database as Am4. Currently SQL Server Versions 7, 2000 and 2005 are supported

Installation Process

• Am.Net server is configured

• Am.Net program files are copied to the local Am.Net Server

• SQL Server is updated to load Am.Net stored procedures and a few Am.Net specific tables

Installation Process

• Clients must have the .Net Framework: this is a standard Microsoft “Windows Update” item and is included in Vista

• Prior Am.Net releases were version 1.1 of the Framework. Release 15 due in late June will be in version 2.0

• A small file is installed on each client. For states that allow remote access there is a separate install file for local versus remote access

Installation Process

• New releases of Am.Net are loaded on the server and the clients are updated automatically

• State specific report formats (confirmations, dues invoices, acknowledgements, etc.) are added

•

This presentation will include reviews of the following topics:

• The development timeline

• The release process

• The development process

• Work completed to-date

• Significant items not yet completed

• Installation at Societies

AM.Net Development Timeline

• What is contained in the timeline?

• Where can timeline be found?

• What does the timeline look like?

• Where are we currently on the timeline.

What is contained in the timeline?

• The AM.Net “Timeline” is a breakdown of the entire AM system into its smallest components (i.e., each report, process, and maintenance screen)

• The Timeline gives an estimate of how long it will take to re-program each component from AM4 (FoxPro) to AM.Net (.NET)

• The Timeline shows the estimated month of completion.

• The Timeline is updated periodically to show the development status of each component.

Where can the timeline be found?• Go to the CDS web site @ www\cds-am.net

What does the timeline look like?• The Timeline is a standard PDF document.

Where are we currently?Original Timeline as of Nov, 2005

Additional Items Requested

Heavy AM4 Support

Revised Timeline as of July, 2006

System Software Upgrades

Where we should be currently

Where we actually are currently

Responding to AM.Net Feedback

Advisory Board Overview

• Advises CDS about any changing needs and priorities of the Societies so the timeline can be adjusted according.

• Monitors CDS’ progress on the timeline and reports to the Societies.

The Release Process

• Timeline is managed by breaking it down into discrete “Releases”

• The contents of each release are defined dynamically at the time the release is established

• Releases are timed for every 4-6 weeks

• Currently working on Release 15, which should be ready by the end of June

Development Process• Items are selected from timeline for next

release• Requirements are written for each item• Meeting is held to hash out design details• Developers write and pre-test program• Program is reviewed by alpha-tester• Developers fix any alpha bugs found• Program is reviewed by beta-tester• Developers fix any beta bugs found• Item is certified for inclusion in next release

Project Management Software

• For more info, go to: www\axosoft.com

OnTime 2007 – Sample Screen

Recap of Work Completed

To-Date

File Maintenance

• Names

• Firms

• Committees

• Events

• Products

Search Functions

• Incremental search

• Credit card search

• Phone number search

• E-Mail search

• Check number search

Transaction Processing

• DUES: Annual/Monthly/Individual Posting, Invoicing, Adjustments, Payments, Refunds

• EVENTS: Registrations, Payments, Sessions, Cancellations, Transfers, Refunds

• PRODUCTS: Sales, Refunds

• PEER REVIEW: Payments/Adjustments, Refunds

• MISC. CASH RECEIPTS

Cash Batch Processing

• Batch Totals Maintenance

• Cash Batch Entry – all modules supported

• Close Open Batch

• Redistribute Prior Payment

Money-on-Account

• Various processing programs

Data Analysisand

Review

• Names View

• Events View

Reporting

• Selection Criteria

• Report Wizard

• Various reports – mostly concentrated in Dues, Events, Names and Firms

Significant ItemsLeft to Complete

• ACCOUNTING FUNCTIONS:– A/P and General Ledger

• MINOR MODULE FUNCTIONS:– Media Relations, Lobbying, Job Referral

and Volunteers

• VARIOUS TRANSACTION POSTINGS:– Peer Review Annual billing, Products

Adjustments, etc.

• LOTS OF REPORTS

Installation at Societies• 19 states currently have Am.Net installed:

– AL, AR, CO, FL, IL, KY, MD, MI, MN, NH, OK, OR, PA, PR, TN, TX, UT, VA, WA

• 8 states (DC, HI, KS, MS, MT, SC, SD, WV) have not implemented SQL Server, which is required prior to Am.Net installation. All of these states should be able to use SQL Server 2005 Express, with no license fee.

• CDS would like for all states to migrate to SQL Server 2005 by mid 2008, sooner if possible.