OSS FIXED ASSETS RMO & SERVICES FULFILLMENT MANAGEMENT SYSTEM (ASP.NET) Version: ASP.NET (3.0) Updated: 1Q/2008, v3g1r3 Reference: 371/86

Transcription

1 OSS FIXED ASSETS RMO & SERVICES FULFILLMENT MANAGEMENT SYSTEM (ASP.NET) APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS & DESCRIPTIONS Version: ASP.NET (3.0) Updated: 1Q/2008, v3g1r3 Reference: 371/86 1

2 CONTENT DESCRIPTIONS 1. TECHNICAL SPECIFICATIONS 1.1 PROGRAMMING CODES 1.2 DATABASE 1.3 APPLICATION SOFTWARE ARCHITECTURE 2. APPLICATION INTRODUCTION, ARCHITECTURAL TOPOLOGY, SPECIFICATIONS, FEATURES AND SCREEN SHOTS DESCRIPTION 2.1 Introduction & Business Applications 2.2 Application Architecture & Topology 2.3 Application Feature Description 2.4 Application Software Screen Shots 2.5 Hardware Deployment based on HA (High Availability) 2.6 Hardware Deployment for Voluminous Concurrent Log-ins 2.7 Overall Diagram of Combined Application and Hardware 3. OSS APPLICATION SERVER AS MIDDLEWARE 3.1 INTRODUCTION TO OSS APPLICATION SERVER System Security Identify Authentication & Parameters Value-based Policies State-based Policies Authentication Authorization Audit Trail & Track Data Protection: RSA Encryption Access Control Module- File Access Right to Application Components LDAP (Lightweight Directory Access Protocol) and Active Directory Enterprise Content Management - Optional Taxonomy/ Metadata Management Federated Search Engine Digital Right Management Revocation of User Account Module Web Services on Scheduled Data Migration and Integration Optional Report Portal Module Optional Business Intelligence Module - Optional OSS APPLICATION SERVER SCREEN SHOT EXAMPLES

3 1. TECHNICAL SPECIFICATIONS 1.1 PROGRAMMING TOOLS The App s source codes were written in: A. Microsoft Visual Studio.NET (ASP.NET & VB.NET), B. Infragistics.NET and C. AJAX. 1.2 DATABASE & MIDDLEWARE CONNECTING STRING The App was pre-built with an objected oriented DATA ACCESS LAYER (DAL) middleware, which supports the underlying App to be flexibly connected to any RDMS database that clients prefer, from MS SQL to Oracle 11g to IBM DB APPLICATION SOFTWARE S ARCHITECTURE The App s core architectures are adherent to two major platforms as below: A. N-Tier: The App s code-structure is written in N-Tier where its source codes can be logically spread over multiple physical servers. Its spread-over capability is inherently providing the App with true failover, HA (High Availability) and Scalability capabilities. For details of the said cluster-server configuration, please refer to [Section 2.2] below. B. SOA (Services Orient Architecture, details are at Section 2.2): Since the App s main codes can be spread over to different logical layers of servers, the main codes then are grouped into two sub-modules again as below: i. App s codes- the core Application that provides the functionalities to the end-users, and ii. Central Utility Codes which provides the System Administrators the central governance, regulation and management on users login behavior. The co-relationship between the two is illustrated in [Diagram 2.2] below. The SOA centralized utility host provides many powerful services that greatly enhances the security, robustness and versatility of the core Application. Some of the prominent are Single Sign-In, Identity Management, Audit Trace, RSA Encryption, Messaging Orient Middleware (such as SMS/ Alert Messaging Services) and other. 3

4 2. APPLICATION INTRODUCTION, ARCHITECTURAL TOPOLOGY, SPECIFICATIONS, FEATURES AND SCREEN SHOTS DESCRIPTION 2.1 INTRODUCTION & BUSINESS APPLICATIONS The App is an amalgamation of two separate Applications of: I. OSS FIXED ASSETS & RMO (REPAIR, MAINTENANCE & OVERHAOL) (ASP.NET), and II. OSS SERVICES FULFILLMENT SYSTEM (ASP.NET). The App was created due to over the years, we have been listening from enterprisegrade corporations (in particular large construction companies) who have sizable assets that require an Application that can meet these two business requirements: A. ASSIGN MAINTENANCE TASK FOR KEEPING ASSET HUMMING- They require a sophisticated Service Fulfillment System as work flow tool to assign either internal technicians or external subcontractors to maintain the base asset class; and B. SHARPEN ASSET S UTLIZATION- It is en economic trend that enterprisecorporations with sizable assets, want to charge their assets as rental fees to their business divisions which use them. This is to discourage idle usage on the asset part while the division unit is holding the asset; simultaneously with the same token, this measure promotes greater efficiency in assets utilization for maximum profits. 4

5 2.2 APPLICATION ARCHITECTURE & TOPOLOGY The App s N-Tier topology is illustrated at [Diagram 2.2] below. As the App is N-Tier based structurally, it means that its body of codes can be logically spread across the different types of servers (Web, Application and Database) as indicated below, where it inherently provides Failover, High Availability and Scalability to clients who deploy the said solution. In short, it means the App is best suited for enterprise corporations which have large loads of login users that values 24/7. Diagram 2.2: N-Tier Topology Internal Users External Users Web Tier OSS Enterprise Service Portal / or Client Existing Fixed IP Webpage System Security : OSS Single Sign-In, Access Control Manager & Session Manager Application Tier OSS Administration Module [Dictionary] Application Components OSS FIXED ASSETS MODULE RMO MODULES SERVICE FULFILLMENT OSS Application Server (ASP.NET) Authentication Authorization RSA Encryption Audit Trail API LDAP Optional Archival Alert Management Work Flow Business Intelligence 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 [SAN/ NSA/Tape] 5

6 2.3 APPLICATION FEATURE & DESCRIPTIONS FEATURE SPECIFICATION DESCRIPTION As explanation in Section 2.1 above, the App is an amalgamation of two application softwares, the following Feature Specifications will split into two for ease of understanding. You however are advised that they are working closely together as one, due to by combining they now have a central Dictionary (or Master Files) to define all the common classes, such as Currency Converter, Customer, Spare Parts, and others. In addition, there are two main feature improvements in the combined App, where we had added the Project and Purchase Order (PO) as classes to compliment the said Application. A. DICTIONARY B. FIXED ASSET MODULE C. RMO (REPAIR, MAINTENANCE & OVERHAUL) MODULE D. SERVICE FULFILLMENT MODULE E. PROJECT LINKAGE F. PURCHASE ORDER, AND G. BUSINESS INTELLIGENCE (BI) DRILL-DOWN, OPTIONAL DICTIONARY The Master-Fill now combined and provides central common re-usable classes for FIXED ASSET RMO and SERVICE FULFILLMENT SYSTEM, such as Currency (Exchange Rate) Fixer, Category Differentiators, Customer, Supplier (of Spare Parts), Product (or Parts), Module and Others. FIXED ASSET MODULE 1. Definition, Creation, Amendment, Save, Export and Print 2. Activity History Module 3. Depreciation Module (Purchase Date & Purchase Agreement) 4. Residual Value Module 5. Legal Ownership & Transfer Title History Module 6. Category Definition 7. Supplier Profile Definition 8. Linkage to Accounting Module RMO (REPAIR, MAINTENANCE & OVERHAUL) MODULE The module basically is a PREVENTIVE MAINTENANCE PORTAL, where it enables users to plan, execute, record and analyses the spend dollar on overall asset class: 1. Planned (Date, Time, Spare Parts and Man-power) 2. Actual Utilizations (Date, Time, Spare Parts & Manpower) 3. RSPC (Repair Service Purchase Confirmation) 4. Service & Part Confirmation 6

7 4. Reports 5. Prompt Alert based on (Day/Week/Month) SERVICE FULFILLMENT MODULE The module is work flow tool where it permits the Service Team Manager to receive Service Request (SR) online and convert them into separate Work Order (or some instances, called Job Sheet) where he can assign to internal technicians or external subcontractors for service, repair, maintenance and overhaul. Since repair service is to involve spare parts, this module s working relationship involves the Inventory Department, and thus activities of GRN (Good Receipt Note), Release of Inventory (or some called SIV) and Balance of Stock Count. RENTAL PORTAL 1. General: Client Details and Third Party Service Provider Status 2. Contract & Documentation Module PROJECT LINKAGE 2.1 Contract Number 2.2 Contract Duration 2.3 Contract Option 2.4 Contract Value 2.5 Contract Deposit 2.6 Payment Details & History Sub-Module As explained before, it is a daunting task for enterprise-corporations which have sizable assets to allocate precise spend expense to asset, as in a single service, an asset class involves multiple asset parts. Due to this reason, the App has now built in a Project features (and thus Global Cost Code ) to precisely tag the expenses spent (such as Purchase Order s) into a Project, where Project can be further grain-refined into different Global Cost Code, for cost analysis and prudent planning purposes. RENEWAL SERVICES PORTAL The Renewal functionality is basically to fulfill the regulatory compliances, where for certain assets (such as heavy tower crane, high-speed life and others) are subject to annual government stipulated inspection and renewal processes. Some of them are: Insurance Sub-Module Warranty Sub-Module Licensing Sub-Module 7

8 CUSTODIAN & CUSTODY MODULE This module is used for keeping track of the status who the owner and where the location the said Asset is tagged to. It basically is a tracking tool for asset s where-about and who-is-havingit-now. 1. Multiple Warehouse Definition 2. Sub Units Definition on Warehouse A. No of units, Warehouse B. Row No (within Warehouse) C. Height No (within Row No) D. Bin No (cross section of Row and Height No) 3. Custodian of Asset (I/C & Employee History) 4. Custody Location DASHBOARD ANALYSIS MODULE (Optional) 1. Trend Analysis Module 2. Alert Management Module 3. New Service Trigger (After Trend Analysis) Module 4. Report Portal Module SEARCH MODULE 1. Asset Code 2. Asset Name 3. Asset Acquisition and Disposal Dates 4. Asset Status SPARE PART (INVENTORY) & PURCHASING MANAGEMENTS (Optional) 1. Purchase Requisite (PR) 2. PR Approval Process 3. Purchase Order 4. Good Receipt Note 5. Packing List & Invoice 6. Spare Inventory & Re-Order Mechanism ASSET UTILIZATION RATIO (AUR) CHARTS 1. Reservation Date 2. Reservation Type 3. Date Adjustment due to Regular RMO Services 4. Actual Client s Up-use Date & Time 8

9 5. Unit Net Revenue (after deducting operating cost & services) Per Client Type Accounts 6. Nett Utilization Ratio 9

10 2.4 APPLICATION SOFTWARE SCREEN SHOT EXAMPLES The App is comprised of two main modules Fixed Asset RMO and Service Fulfillment, where for ease of understanding, we break the screen-shot illustrations in group-a (for Fixed Asset RMO) and Group-B (Service Fulfillment System): A1. LOGIN PAGE: This screen displays the general logon page which requires userid and Password. A2. FIXED ASSET MODULE: The screen illustrates user can create, edit and delete asset unit. All the Fixed Asset submodules are contained here. 10

11 A3. FIXED ASSET S TABS OF FUNCTIONALITIES: The screen below illustrates the App provides various tab functions to define the said underlying asset, such as the General Information, Past Purchase Information, Custody History, Internal Cost Set-up, RSPC (Repair Service Purchase Confirmation), Disposal and Rental. You can assign Bar Code or RFID to the asset. A4. TRANSFER ASSET INFORMATION FROM PURCHASE ORDER (PO): As the PO is the first document that dealt with Asset, this feature is to allow direct Asset information be transferred from PO to Fixed Asset Module by eliminating the re-typing. 11

12 A5. CUSTODY HISTORY: The screen below illustrates the Custody Record on the fixed asset. This basically is a repository to keep track of which party is holding on the fixed asset. The Custody functions support Project based cost allocation. A6. REPAIR COST & ACCUMULATION (RSPC stands for Repair Service Purchase Confirmation): The screen shows the App is capable to archive, store and tally all the repair costs, per fixed asset, at a single view. 12

13 A7. FIXED ASSET S RENTAL AGREEMENT: This screen depicts, if the asset owner is the leaser (such as car leasing companies), the built-in Rental Agreement Portal to define the term & conditions for lessee who will lease the fixed asset for long term contract purpose. The box is to achieve and store all the Rental record for this particular asset. A8. RENEWAL PORTAL: This screen depicts the Renewal Portal which provides the users the capabilities to define, create, view history and amend the Renewal on Insurance, Warranty and Licensing. 13

14 A9. RENEWAL S EDIT FUNCTION: This screen below illustrates the typical renewal features, such as Renewal for Insurance, Government Annual License Renewal and Annual Inspection Certificate Renewal. A10. SERVICE SCHEDULE: This screen illustrates the Service Schedule where the authorized users to plan and execute service (maintenance) schedules for selective (or all) assets, from the beginning of fiscal year. 14

15 A11. SERVICE SCHEDULE S EDIT FUNCTION: The screen below illustrates the typical functions available for Service (Maintenance) Schedule s EDIT function. 15

16 A12. Further from EDIT function, the following screen will be displayed where user is to check which maintenance items where they are sent for maintenance activities. 16

17 B1. SERVICES MANAGEMENT (ASP.NET VERSION): The following screen shots are to depict the Service Fulfillment Module, where we marked them as B-XX for ease of understanding. B2. SERVICES MANAGEMENT (ASP.NET VERSION): This screen shot illustrates the Details of Job Sheet (or Work Order) that received by end-users. You can create a new Work Order (or Job Sheet) by clicking here. 17

18 B3. The following screen shot depict the creation of new Job Sheet (Work Order), upon the received of Request for Services: 18

19 B4. SERVICES MANAGEMENT (ASP.NET VERSION): This screen shot illustrates the case was passed down to assigned technician who is about to carry out the repair, services or overhaul by requesting for new spare parts. The option of [Void Warranty] is provided in the event the body sustained compromised damages. B5. SERVICES MANAGEMENT (ASP.NET VERSION): This screen shot illustrates Inventory Releases from Stock Room, upon the request from Technician at the Job Service stage. 19

20 B6. SERVICES MANAGEMENT (ASP.NET VERSION): This screen shot illustrates the Service of RMO has been completed and now it is pending to be released to Customer Services (CS). B7. SERVICES MANAGEMENT (ASP.NET VERSION): This screen shot illustrates the Add-Call feature where the CS can record down all the correspondences or call history to the customers, upon customer s pick up. 20

21 B8. CUSTOMER ANALYSIS: This page illustrate the analysis reporting on all customer status. 21

22 B9. BUSINESS INTELLIGENCE S DRILL-DOWN (OPTIONAL): The screen illustration below depicts an optional BI where it provides quick snap of business insight in graphical drilldown. Some of the frequently cited insights are asset s utilization ratio, average downtime per asset class, average replacement cost per asset class and others. 22

23 2.5 HARDWARE DEPLOYMENT BASED ON HA (High Availability) DIAGRAM 2.5 As the App s underlying codes were designed in N-tier (Diagram 2.2), it supports for layer-spread location at Cluster-Server deployment as indicated in [Diagram 2.5] below. 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 concept of High Availability is relied on each class of hardware is equipped in a pair. This is to ensure any one fails (for whatever reason), the other one will be activated within seconds and the operations will be automatically switched over (or failover) to the live one. The HA design, as depicted below, is capable to support approximate 100 concurrent users at any given time. PROPOSED HARDWARE CONFIGURATION FOR BASIC REDUNDANCY The Basic Hardware Configuration is to provide 50 Concurrent Users, which comprises 2 Units [Web-cum- Application Servers] and 2 units [Database Servers]. 2 units [Web-cum- Application Servers] Operating System 1. MS Windows Server 2008 (Enterprise Edition) FIREWALL SET ROUTER SETS OSS Application Software + Business Logic Database Server Active Node DATA BACK-UP INTERNET 1 ` 2 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 23

24 2.6 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS DIAGRAM 2.6 If clients intend to scale up [from Diagram 2.5 s] to accommodate larger logins loads, the N-Tier design is capable to equipping client to do so by simply adding new physical servers to the existing configuration, without the need to altering the underlying App s source codes, into [Diagram 2.6] below. This scaled-up design, as shown below, is capable to support up to 1,000 concurrent users at any given time. 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 FIREWALL SET ROUTER SETS Database Server Active Node DATA BACK-UP ` INTERNET Increase up to 32 web servers Passive Node Operating System: 1. MS Windows Server 2008 (Enterprise Edition) Database Independence Client can choose any: IBM DB2, - Oracle 10 g or - Microsoft SQL SWITCH-1 SWITCH-2 24

25 2.7 OVERALL DIAGRAM OF COMBINED APPLICATION SOFTWARE AND HARDWARE DIAGRAM 2.7 The following diagram (DIAGRAM 2.7) depicts the co-relationship between hardware and application software, when they are deployed in Cluster-Server Environment. 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 25

26 3. OSS APPLICATION SERVER (ASP.NET) - MIDDLEWARE 3.1 INTRODUCTION OF OSS APPLICATION SERVER (ASP.NET) Clients can enhance the variety of capabilities of the said App with OSS APPLICATION SERVER (ASP.NET/2.0), which provides superior central control and management oversight. OSS APPLICATION SERVER was designed in SOA architecture and whose underlying utility services, as listed below: System Security Identify Authentication & Parameters Authentication Authorization Audit Trail & Track Data Protection: RSA Encryption Access Right Control Module LDAP (Lightweight Directory Access Protocol) and Active Directory Single Sign-In Alert Gateway Services (SMS/ ) Quantitative Control for Global Setting Services Revocation of User Account Module 26

27 3.2 OSS APPLICATION SERVER SCREEN SHOT EXAMPLES 1. System Security & Identity Management Panel: It provides consistency to System Administrator to set, regulate, govern, configure and manage login behavior, in accordance with stipulated corporate governances. These include setting policies of: 01. Value-based Policies such as minimum lengths and the presence of a minimum number f special characters; and 02. State-based Policies such as expiration and maximum number of re-tries before being block out from access. 27

28 2. Audit Trail Module The App Server provides detailed traceability records on each user s login activities (etc, access, view, edit, save, delete, import/export, print and others), in terms of Date, Time, Action and Fields. 3. LDAP (Lightweight Directory Application Protocol). OSS App Server has a built-in LDAP-connector which it supports client to copy, comply and role-play consistency with the overall HQ stipulated Directory, User Login ID and Password. 28

29 4. File-Access Right Allocation Management The App Server provides Role based Access Rights to each user. 5 Application Software Feature-Access Right Allocation. This class-specific (Object Oriented) feature allow System Administrator to allocate Access Right of each Application Software s component in accordance to each users roles and responsibilities. 29

30 [OPEN SPECTRUM SOLUTION] 1. 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; 2. For most updated information on the said application, please contract your nearest OSS authorized resellers or logon to for contact; and 3. For reporting of error and mistakes at the above article s, please send your message to 30