OSS TENDER PORTAL MANAGEMENT SYSTEM (ASP.NET)

OSS TENDER PORTAL MANAGEMENT SYSTEM (ASP.NET) APPLICATION SPECIFICATIONS, FEATURES DESCRIPTIONS SCREEN SHOT ILLUSTRATION Version: ASP.NET (2) Updated: 3Q/2007, v-2 Reference: Middleware 0445/86

1. TECHNICAL SPECIFICATIONS 1.1 PROGRAMMING TOOL 1.2 DATABASE 1.3 ARCHITECTURAL PLATFORM 2. APPLICATION SOFTWARE ARCHITECTURE 3. APP S INTRODUCTION, FEATURE SPECIFICATIONS & ILLUSTRATIONS 3.1 APP S INTRODUCTION 3.2 APPLICATION S MODULAL FEATURE SPECIFICATIONS 3.3 APP S SCREEN SHOT ILLUSTRATIONS 4. HARDWARE DEPLOYMENT FOR SCALABILITY & HIGH AVAILABILITY 4.1 BASE SCALABILITY 4.2 ULTIMATUM SCALABILITY 4.3 CO-HABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE 5. OSS APPLICATION SERVER AS MIDDLEWARE

1. TECHNICAL SPECIFICATIONS 1.1 PROGRAMMING TOOLS The App s source codes were written in: A. Microsoft Visual Studio.NET (ASP.NET & VB.NET) 3.0, B. INFRAGISTICS.NET and C. AJAX. 1.2 DATABASE The App is pre-built with a Data Access Layer (DAL) middleware, which permits clients to deploy it with any preferred RDMS Database (from MS SQL to Oracle 11g to DB2). 1.3 APP S ARCHITECTURAL PLATFORM The application s core architectural platform is adhered to: A. SOA (Services Orient Architecture) The App s centralized utility services from Single Sign-In to Identity Management to LDAP Compliance to Encryption are designed in SOA (Service Oriented Architecture). B. N-TIER: The core App is designed N-Tier which it permits clients to scale up the App s deployment (or accommodating large concurrent users logins) without painstakingly re-write the base codes. For details, please see {Section 2.5 to 2.7}. C. WEB SERVICES Interface (SOAP Protocol): The App was pre-built with Web Services layer (http/xml, based on SOAP protocol) which permits clients to data-exchange the App s with third-party Applications with ease.

2. APPLICATION SOFTWARE ARCHITECTURE 2.1 APPLICATION ARCHITECTURE The App s architectural platform is adhered to N-tier. In a nutshell, the App s underlying codes can be spread across different layers of hardware (Web, Application and Database Servers), to achieve the Failover redundancy and thus Scalability. The diagram design is meant for those business organizations whose concurrent loads are large (say, more than 500 named users) while the system configuration is capable to meet the required 3- second elapsed time of Consistent Performance, in addition to standard Scalability and Failover. Internal Users External Users Web OSS Enterprise Service Portal / or Client Existing Fixed IP Webpage System Security : OSS Single Sign-In, Access Control Manager & Session Manager Application r OSS Administration Module Application Components TENDER PORTAL AUCTION PORTAL Other Applications OSS Application Server Authentication Authorization RSA Encryption Audit Trail API LDAP Optional Archival Alert Management Work Flow OSS Data Access Layer (DAL) Database Tier Microsoft SQL Oracle IBM DB2 Other RDBMS Optional: Second Data Centre For Back- Up + Recovery Back-up Software : External Data Storage Device

3. APP S FEATURE DESCRIPTIONS, FEATURE SPECIFICATIONS & ILLUSTRATIONS 3.1 APP S INTRODUCTION OSS TENDER PORTAL SYSTEM (ASP.NET) is a complete web-enabled application that is designed for enterprises to manage, govern and direct its diverse divisions in a centralized procurement department, to achieve economic of scales and cost containment policies. The App is part of the full life cycle of the SPEND Application Suite, whose whole related Apps are briefly described as below: A. MATERIAL REQUISITION, APPROVAL & PURCHASE ORDER MODULE ; B. TENDER PORTAL- whose purpose is to manage those low volume transactions but high-value added purchases; C. AUCTION PORTAL Highly specialized purchase-need based on invited bidder/ vendors process D. CONSIGNMENT PROGRAM Vendor s self-voluntary refilling system based on actual client s monthly consumption volume. 3.2 BRIEF FEATURE DESCRIPTIONS GENERAL FEATURES A. Home B. About Us C. Trading Partners Directory D. Buyer Agencies E. Online FAQ F. Useful Link G. Contact Us LOGIN & EXTERNAL VENDOR PORTAL & SELF-SERVICES A. General Administration B. Registration and Renewal C. Sign-In with SSL encryption D. My Profile Update, Edit, Assignment E. Assign New User_Name and Password CENTRALIZED PROCUREMENT SYSTEM A. Branch Network Pre-requisite Order & Order-Purchase s Approval B. Centralized HQ Budget Approval and Bulk Purchase Order Consolidation C. Online Order Posting & Vendor Invitation to participate thru Email/ SMS or matching process D. Integration with Centralized Accounting System BUSINESS OPPORTUNITIES FOR VENDORS

A. Tenderer & Quotation B. Invitation C. Qualification D. Request for Information E. Auction F. Bookmark RESPONSES A. Tender & Quotations B. Qualifications TRANSACTION HISTORY A. Overall Tenderer s Past Transaction as Dashboard View B. Past Quotation & Per Project C. Received Letter of Award (LA) D. Bond s Term & Conditions E. Payment Receipt & Matching Invoice Records PAST OPPORTUNITIES A. Tender & Quotation B. Qualifications C. Request for Information D. Auction PERIOD CONTRACT A. Invoice B. Credit Notes C. Payment Status D. Rate our Website

3.3 APP S SCREEN SHOT ILLUSTRATIONS I. OSS TENDER PORTAL SYSTEM the general layout s design. The information provided at the portal are: 1.1 Trading Partner A. Register Now (for new trading partners) B. Sign-In C. My Profile Edit, Update and Certified with audited financial reports for certain threshold (range) auction and tenders; D. My Tender History 1.2 Business Opportunity A. Tender & Quotation B. Auctions (Invited Only) C. Vendor Pre-qualification Process D. Request for Information E. Threshold Limit of Tender/Quotation Submission 1.3 Past Opportunity A. Award Information B. Attached Information C. Re-tender/Quotation Process with selected vendors 1.4 Procurement Policy and Information 1.5 News A. Online Subscription B. RSS (Optional)

C. Forum/ Blogs (Optional) D. Wiki (Optional) 1.6 Contact Us A. Contact Information B. Tender Questionnaires Submission Panel prior to Tender Briefing C. Site Visit Information 1.7 Optional: OSS Enterprise Financial Management System (ASP.NET) 1.8 Optional: SOA (Service Orient Architecture) s Application Program Interfaces II. TRADING PARTNER S LOGIN PANEL: This display shows the trading partners, who participate in the tender/quotation process, are required to login to access purchase opportunities online. From the successful logon, the trading partners can download the tender/quotation requirement information, acknowledge the deadline of submission and register for alert for requirement-changes (if any) via email and SMS. Also, this page provides the history of transactions such as purchase opportunity s prevailing status (closed/ open/ no-award / cancelled), award information at a single snap glance.

III. TENDER/QUOTATION OPPORTUNITY INFORMATION PANEL This page displays all the tender/ quotation requirements from the corporate customers where the login trading partners can sort by trading category to participate in. The tender/ quotation tabulated list-up provides general information such as the specified department who calls for the tender/ quotation, deadline of submission, trader s eligibility and criteria of submission, contact information, mode of tender/quotation submission (online, hard-copy or both) and tender briefing venue/time/date. IV. PAST OPPORTUNITY AT A SNAP-SHOT: This page displays the information on the past opportunities on a snap-shot. The information available are, awarded vendor name and address, awarded amount, awarded specification and attachments. As the display page is lengthy, we provided the screen shots in three (3) section as below: A. Tabulated Past Opportunities

B. Detailed Breakdown of Information C. Awarded Information- Vendor name, amount, awarded date and attached conditions.

V. SPEND ANALYSIS: The screen below depicts System Administrator who can provides detailed drill-down for spend analysis.

4. HARDWARE DEPLOYMENT BASED ON HA (High Availability) 4.1 BASE FAILOVER CONFIGURATION As the Application was designed in N-tier, its underlying code components can be spread over layered based hardware, as shown diagram below, to support Cluster-Server Environment. The clear purposes of deploying it in Cluster-Server environment are to achieve the following: A. High Availability (or Failover Switch over) B. Scalability, and C. Consistent Performance (or 3 second elapse time on each web transaction s response) The base Failover, as per illustrated in [DIAGRAM 4.1], can be configured via two (2) Web Servers, two (2) Application Servers, 2 Database Servers, two (2) Gigabit Switches and two (2) Local Data Backup Storages (SAN/NAS). The concept of High Availability is relied on each class of hardware is equipped in a pair. This is to ensure any one about to fail (for whatever reason), its operations will be automatically switched over (or failover) to the live one. [DIAGRAM 4.1] BASE HARDWARE CONFIGURATION The Base Redundancy Hardware Configuration can consist of 2 Web Servers, 2 Application Servers and 2 Database Servers. 2 units [App Servers] Operating System 1. MS Windows Server 2008 (Enterprise Edition) 2. MS Application Centre 2000 FIREWALL SET ROUTER SETS 2 units [Web Servers] OSS Application Software + Business Logic Database Server Active Node DATA BACK-UP INTERNET 1 3 ` 2 4 Passive Node Operating System: 1. MS Windows Server 2008 (Enterprise Edition) 2. Database Independence Client can choose any: - IBM DB2, - Oracle 10 g or - Microsoft SQL 2005 SWITCH-1 SWITCH-2

4.2 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS The base High Availability (HA) hardware configuration, as depicted in [Section 4, DIAGRAM 4.1], can be further scaled up to support more than 500 concurrent users, if the underlying business warrants such higher loads. To achieve higher scalability, the base in [Section 4.1] can be enhanced thru adding up to 32 Web servers, 12 Application Servers and 2 Database Servers at single location as depicted in [Diagram 4.2] below. This scaled-up design is capable to support up to 5,000 concurrent users at any given time. For even higher scalability (more than 5,000 concurrent loads), we suggest the grid computing system by deploying Oracle 11g. [DIAGRAM 4.2] Ultimate Hardware Scalability: The N-Tier Platform will allows client to scale up to 32 Web Servers and 12 Application Servers as indicated below Up to 32 units of Web Servers with Network Load Balancing Operating System 1. MS Windows Server 2008 (Web Edition) with Network Load Balancing 1 Up to 12 units of Application Servers with Component Load Balancing Operating System 1. MS Windows Server 2008 (Enterprise Edition) 2. MS Application Centre 2000 OSS Application Software + Business Logic 2 3 1 2 FIREWALL SET ROUTER SETS 4 5 6 3 4 Database Server Active Node DATA BACK-UP ` INTERNET 7 8 5 6 Increase up to 32 web servers 9 7 8 9 Passive Node Operating System: 1. MS Windows Server 2008 (Enterprise Edition) 10 2. Database Independence Client can choose any: 30 11 12 - IBM DB2, - Oracle 10 g or - Microsoft SQL 2005 31 32 SWITCH-1 SWITCH-2

4.3 OVERALL DIAGRAM OF COMBINED APPLICATION SOFTWARE AND HARDWARE The following diagram (DIAGRAM 4.3) depicts the co-relationship between hardware and application software, when they are deployed in Cluster-Server Environment. DIAGRAM 4.3 TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT & CONFIGURATION End-Users ` END-USERS Web Servers System Security: Access Control Manager & Session Control Application Server Application Software-1 Application Software-2 Application Software-3 Application Infrastructure Building Block: Access Control, Encryption, Audit Track, Single-Sign_In, SMS, Report Portal & Others Database Server Switch-1 Switch-2 Data Access Layer (DAL) Database Active Node Passive Node SAN/NAS BACK-UP

5. OSS APPLICATION SERVER (ASP.NET) - MIDDLEWARE 5.1 INTRODUCTION OF OSS APPLICATION SERVER (ASP.NET) AS MIDDLEWARE You can enhance the core App with the (optional) middleware, OSS APPLICATION SERVER (ASP.NET), which provides System Administrators various central management tools to ensure users are adhered to corporate governance, security & risk control, encryption protection and identity management. In addition, the App Server acts as middleware, which provides the ready-made web services (SOAP, based on XML/http)for client to help connect and data-exchange with third parties Applications. The following provides a brief introduction on the essential services that provided by the App Server s application: A. System Security Identify Authentication & Parameters A.1 Value-based Policies A.2 State-based Policies B. Authentication C. Authorization D. Audit Trail & Track E. Data Protection: RSA Encryption F. Access Control Module- File Access Right to Application Components G. LDAP (Lightweight Directory Access Protocol) and Active Directory H. Revocation of User Account Module I. Report Portal Module

5.2 OSS APPLICATION SERVER SCREEN SHOT ILLUSTRATIONS A. SYSTEM SECURITY The Global Parameter Setting allows System Administrator to remotely configure various log-in parameters for all users, prior to the deployment of the core App. B. SYSTEM AUDIT TRAIL It allows System Administrator to keep tracks each user s log-in activities (access, view, data entry, edit, print and others). The system tabulates each user s activities in dashboard analysis platform (such as Date, Time, Action, Field he/she accessed).

C. SYSTER USER-ACCESS RIGHT ALLOCATION The system assigns specific access rights on each module, in accordance to the user s role and responsibility as defined in corporate hierarchy. D. SYSTEM ENCRYPTION & FILE ACCESS RIGHT This class-specific (Object Oriented) feature allow system administrator to allocate Access Right in check-box whose features will be accorded to approved users.

[OPEN SPECTRUM SOLUTION] The above information is correct at the time of this article went to print and release on the OSS website. OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles; For most updated information on the said application, please contract your nearest OSS authorized resellers or logon to www.open-spec.com for contact; and For reporting of error and mistakes at the above article s, please send your message to Documentation@open-spec.com.