Difference between revisions of "PFS Wiki Proposal/Requirements"
From Organic Design wiki
(Added additional requirements) |
m |
||
Line 1: | Line 1: | ||
+ | To create a document that will be of interest to PFS we must provide a solution that is at least able to replicate the functionality that we already have inhouse. Current functionality is listed below. | ||
+ | |||
#File Transfer Area | #File Transfer Area | ||
http://pfsbbs.pfs.com | http://pfsbbs.pfs.com |
Revision as of 00:52, 12 December 2006
To create a document that will be of interest to PFS we must provide a solution that is at least able to replicate the functionality that we already have inhouse. Current functionality is listed below.
- File Transfer Area
PFS currently maintains a separate site for clients to upload and download files. This is primarily used for obtaining copies of client databases and for PFS to upload fixes to clients.
- Deficiencies
- File Continuation
- This site is extremely old. If the connection drops then the file upload/download has to be restarted from the beginning. There is no upload/download continuation.
- Login IDs
- The site requires a separate login ID and password from any other PFS system.
- Client Support Center
This site is used as the primary site for communications between PFS and clients. This site contains the following facilities:
- News and Message Center - PFS to post messages to clients within specific regions, plus bulletins and important events for all clients
- Calendar of Events - A calendar to advise of events such as training, releases, conferences etc.
- Support Incidents - Clients can post issues and view updates by PFS on this area (backend system for this functionality is ONYX)
- Knowledge Base - Documentation repository area
- Account Information - User account information and change password area
- User Forums - An area for users to ask questions of each other and PFS staff (moderated by PFS staff)