From Ascgroup

 SeeSOR.NET User Centric Enterprise Architecture:

The graphic below depicts how the SeeSOR.NET users exist within the enterprise.

- Users can be either Service Providers, Service Receivers, or both simultaneously populating and sharing common data (most efficient use of QA/QC resources). Management can review trends and performance metrics to collaboratively design adjustments to improve quality and follow-up on the effectiveness of the changes.

- Users can use both the SeeSOR.NET and/or SeeSOR desktop (Web Application and/or Client-Server Application) to access the SeeSOR database. The desktop and web versions of SeeSOR offer there own advantages since both take advantage of the technology they are based upon.

Basic Deployment Architecture:

SeeSOR.NET can be deployed as HTTP or HTTPS for enhanced security.

SeeSOR Architecture Narrative

SeeSOR is a robust, large solution for housing multiple service contract projects’ PWS and Quality Management data.

The data is stored within SeeSOR and accessible via a client/server connected to a networked database or in the case of SeeSOR.NET a web front-end. The front end for SeeSOR.NET is web-based, while the VBA version is desktop-based. Client/server SeeSOR and SeeSOR.NET both share the same database so it is possible to simultaneously use client/server SeeSOR and SeeSOR.NET.

SeeSOR.NET currently works with Internet Explorer 7 or greater, Safari and Mozilla Firefox.

The SeeSOR architecture is scalable and extensible. Future components will be added to SeeSOR as update modules. This is achieved using the modular architecture we designed to allow scaling of the application.

Role based user privileges are assigned with logon/password assignments through the SeeSOR interface.

Communications:

1. SeeSOR uses TCP/IP protocols and needs port 1433 open to connect to the SQL Server.

2. The web server is IIS.

3. Communications can be http or https

4. SeeSOR’s front-end has the capability to tie into LDAP and authenticate using ports 389 and 636. But there are some norms that a customer should follow for proper operations.

Databases:

For .NET: Microsoft SQLServer 2005, Microsoft SQL Server 2008 and Microsoft SQLServer 2005 Express.

For SeeSOR 3.5.4: Microsoft SQLServer 2005, 2000, Microsoft Access.

SeeSOR can integrate with Outlook or any application with a database structure and most easily with SQL Server based applications.

Reports:

Data can be easily exported out of SeeSOR. SeeSOR contains push button export capability to PDF, MS Work and MS Excel. Client/server version of SeeSOR can export to virtually all licensed applications that may be found on a client computer.

Users can create ad hoc reports. With the client/server SeeSOR there is the flexibility to create custom reports that can be saved for personal and shared use using Crystal Reports (users do not need to have Crystal Reports to view custom reports). Reports can be created using “.NET” report designing capability.

Recommendations regarding the Hosting Server(s)

DATABASE: The SeeSOR hosting server will need to have with SQL Server 2000, 2005 or SQLEXPRESS 2005. Each database (project or contract) typically will not grow bigger than 10GB to 20 GB over a five years (each contract being monitored is a separate database).

ATTACHMENTS: In addition to server space for the SeeSOR application there needs to be space for attachments. Attachments could include documents, spreadsheets, photos, videos, etc. Space required for a large complex project is about 5GB over the first 5 years. This storage space requirement could vary if photos or videos are frequently used.

Plans should be made for additional projects in the future that would create the need to start hosting additional databases.

Users interact with the database completely through the SeeSOR application, including all user related administration issues. Standard back end services such as scheduled backup of the database and periodic maintenance of log files, etc. is required of the hosting service.