TMAN System Conceptualization

http://apps.topcoder.com/wiki/display/docs/TMAN+System+Conceptualization

Territory Manager II is a Visual Basic 6.0 application (server and client) and is used by Service Support Representatives (SSRs), their Managers, National Parts Administration center (NPAC) users etc. to manage their Availability, Analyzing Availability, Reconciliation of Parts, Submission of count of Parts, submitting action items against TMTA reports. All the data that is needed to run the application is maintained in TMAN server as flat files. The TMAN Client application get this server data through replication process and it is stored locally in MS Access database. The client fetches the information stored in Access backend and displays the user’s Availability and Partrec/TMTA reports. After user has processed the availability and reports files, he can replicate the local user data to the server. The server application which is running on the server processes the user data and sends those to downstream systems. For Example – The completed inventory count is sent to PIMS parts accounting downstream system, The availability updates are sent to the CROSS system.

The purpose of this project is to rewrite the application to leverage more current technologies that can be supported in the IBM. This will be web based solution.

Expected benefits out of the new system:

1. Doesn’t use outdates technologies like VB6, MS Access
2. Doesn’t use unsecure file transfer (ftp)
3. Have good notification system incase of any system interface connection issues or component failure.

Expectation from the proposed solution:

1. We are looking for web based solution.
2. The solution should interact and exchange files with downstream and upstream systems.
3. There are around 4000 client users in US and CA. Server should be able to handle traffic from 4000 concurrent connections.
4. The new system should be supported in IBM.  (refer -  Conceptualization_Company_standards-TMAN.doc)
5. The Client application should follow IBM standards (refer -  Conceptualization_Company_standards-TMAN.doc)
6. Provide pros and cons of all technologies mentioned in the proposal.

Final Submission Guidelines

Event will have 2 phase - Milestone and Final deliverable

Meeting Topcoder deliverables/outputs.

Final Event deliverable.

• Conceptualization Document
• UML model with high-level use case diagrams